Hey Everyone,
I woke up this morning to an Unauthorized Software message on my rooted Galaxy Note 2. I have been rooted for a long time now with no problems. I have not accepted any updates and have not made any recent changes to my device. I was using TWRP 2.6 and Jedi Rom when this message occurred. I tried flashing back to stock following the directions posted on the development forum but that doesn't seem to get the message to go away. I am not sure what else to do at this point to fix the issue. Any help would be appreciated.
comptech81 said:
Hey Everyone,
I woke up this morning to an Unauthorized Software message on my rooted Galaxy Note 2. I have been rooted for a long time now with no problems. I have not accepted any updates and have not made any recent changes to my device. I was using TWRP 2.6 and Jedi Rom when this message occurred. I tried flashing back to stock following the directions posted on the development forum but that doesn't seem to get the message to go away. I am not sure what else to do at this point to fix the issue. Any help would be appreciated.
Click to expand...
Click to collapse
You weren't unlocked when you flashed, that's why the message popped up. Go check out Droidstyles guide and if you can't get the message to go away using it try flashing one of the restore to stock roms with NAND erase checked.
Sent from my SCH-I605 using XDA Premium HD app
Still having problem
shangrila500 said:
You weren't unlocked when you flashed, that's why the message popped up. Go check out Droidstyles guide and if you can't get the message to go away using it try flashing one of the restore to stock roms with NAND erase checked.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
I followed Droidstyles guide and it didn't work. I also tried what you suggested with NAND erase checked and it did not work either. At a loss. I know my bootloader was unlocked. Something happened while I was sleeping last night that started this message.
Anyone else have any ideas?
comptech81 said:
I followed Droidstyles guide and it didn't work. I also tried what you suggested with NAND erase checked and it did not work either. At a loss. I know my bootloader was unlocked. Something happened while I was sleeping last night that started this message.
Click to expand...
Click to collapse
Anyone one else have any suggestions?
There is no way you got that message unless you were locked. Therefore, you tried flashing something while having a locked bootloader. I recommend looking at stickies. You'll find something
It might not be from a locked bootloader.
I know for a fact that there's something deep in the firmware that can do this.
When I was playing around with mine I hade it do this a few times. And I promise my bootloader is unlocked.
Infact right now I'm running on t mobile with cleanrom ACE and a custom kernel.
one of the things I know for sure that will give you that message is trying to run the wrong modem.
Check an be sure you didn't get a bad radio flash or something.
Still having trouble
krazzykiller said:
It might not be from a locked bootloader.
I know for a fact that there's something deep in the firmware that can do this.
When I was playing around with mine I hade it do this a few times. And I promise my bootloader is unlocked.
Infact right now I'm running on t mobile with cleanrom ACE and a custom kernel.
one of the things I know for sure that will give you that message is trying to run the wrong modem.
Check an be sure you didn't get a bad radio flash or something.
Click to expand...
Click to collapse
How would I know if I have a bad radio flash? I cant even get into the phone fully before it errors out and I have to power it down. I have tried several times to follow the directions on the forum and flash it back to stock. However, this does not seem to be working. I am certain my bootloader was unlocked. I have had the phone rooted for well over 6 months. Like I said, I went to bed and when I woke up in the morning it was showing this error message. The only thing that I have updated was super user app. But it doesn't make sense that it would be causing this. Especially now that I have flash back to stock. I cant attempt to re-root the phone either because that requires me to be able to get into the phone and turn on debugging mode.
This happened to me on my s3. I had to use odin and the unbrick files.
where did you find those guides, I have the same problem, lol cant find those guides and for some reason odin 3 wont inst on my pc...
comptech81 said:
Hey Everyone,
I woke up this morning to an Unauthorized Software message on my rooted Galaxy Note 2. I have been rooted for a long time now with no problems. I have not accepted any updates and have not made any recent changes to my device. I was using TWRP 2.6 and Jedi Rom when this message occurred. I tried flashing back to stock following the directions posted on the development forum but that doesn't seem to get the message to go away. I am not sure what else to do at this point to fix the issue. Any help would be appreciated.
Click to expand...
Click to collapse
ok so after 4 hrs got it to work.
here go to this http://forum.xda-developers.com/showthread.php?t=2040264 down load alternate restore. Once it down loads the file extension ends with XZ, which Odin said was not a PDA file.
It has an odd file extension .xz (perhaps meant to be .gz) so I told 7zip to extract it. resulting file ended in .tar.md5. Put that file on odins PDA section. Boot up your phone with volume down, home and power button pressed to boot up in odin, once it boot up connect to pc and press the volume botton up to start odin download on the phone. the select start on odin soft ware on pc, should fix your phone.
http://teapartysupporter.com/drupal/content/system-software-not-authorized-verizon-wireless
If none of this makes sense, pm me and we can go via skype and ill guide you or attempt to fix your phone.
Still having trouble
Dafonse said:
ok so after 4 hrs got it to work.
here go to this http://forum.xda-developers.com/showthread.php?t=2040264 down load alternate restore. Once it down loads the file extension ends with XZ, which Odin said was not a PDA file.
It has an odd file extension .xz (perhaps meant to be .gz) so I told 7zip to extract it. resulting file ended in .tar.md5. Put that file on odins PDA section. Boot up your phone with volume down, home and power button pressed to boot up in odin, once it boot up connect to pc and press the volume botton up to start odin download on the phone. the select start on odin soft ware on pc, should fix your phone.
http://teapartysupporter.com/drupal/content/system-software-not-authorized-verizon-wireless
If none of this makes sense, pm me and we can go via skype and ill guide you or attempt to fix your phone.
Click to expand...
Click to collapse
I am not having problems getting the install to work. My problem is that the install isn't removing the unauthorized software message I am getting.
comptech81 said:
I am not having problems getting the install to work. My problem is that the install isn't removing the unauthorized software message I am getting.
Click to expand...
Click to collapse
You are doing something wrong, either way this process is to revert your phone back to stock, from there you can root again. Theres no other way about it and is the only way I got my phone off that.
boot phone pressing vol key down, home and power.
connect to pc,
press vol key up
start odin
secondary file on pda
inst
phone back to stock.
If it doesnt work, I might have to see what you are doing via skype
secondary file ... http://www.androidfilehost.com/?fid=9390225151984927096 this one was the one that worked for me and many others.
---------- Post added at 02:32 AM ---------- Previous post was at 02:26 AM ----------
I also did something with oding that caused a failed that made my phone go from that screen to update fail message, maybe we can try that rout and then do the restore as a last thing.
Related
So I decided to root my Samsung S2 i7777. Had years of experience flashing HTC hero and Hp touchpad. Thought this might be straightforward as well. Proceeded to get ODIN and ATTGalaxyS2RootStockZedomaxKernel.tar. Flashed it and got pass. Phone proceeded to reboot and was stuck on the Exclamation mark. Tried restarting but no luck same thing. Initially had CWM coming in when I tried the Volume and Power button trick but could not do anything beyond that.
Then I decided that maybe my flash was not proper with that file so I took the siyah kernel and flashed that. This was a pass as well and then back to...the exclamation mark. Now, I cannot get CWM and retarating the phone with the USB connected lets me get into the Downloading window, but I cannot do anything beyond it.
What can I do? Do I need to flash a ROM- is that why I am stuck? How should I flash the ROM from ODIN- if I do get CWM back, can I put the ROM on the SD card and flash it using CWM?
Please help- I am getting stressed out and if I do recover from this, I am going to take a break from rooting :laugh:
g.kupster said:
So I decided to root my Samsung S2 i7777. Had years of experience flashing HTC hero and Hp touchpad. Thought this might be straightforward as well. Proceeded to get ODIN and ATTGalaxyS2RootStockZedomaxKernel.tar. Flashed it and got pass. Phone proceeded to reboot and was stuck on the Exclamation mark. Tried restarting but no luck same thing. Initially had CWM coming in when I tried the Volume and Power button trick but could not do anything beyond that.
Then I decided that maybe my flash was not proper with that file so I took the siyah kernel and flashed that. This was a pass as well and then back to...the exclamation mark. Now, I cannot get CWM and retarating the phone with the USB connected lets me get into the Downloading window, but I cannot do anything beyond it.
What can I do? Do I need to flash a ROM- is that why I am stuck? How should I flash the ROM from ODIN- if I do get CWM back, can I put the ROM on the SD card and flash it using CWM?
Please help- I am getting stressed out and if I do recover from this, I am going to take a break from rooting :laugh:
Click to expand...
Click to collapse
I think you should head over to the stickies and look for creepyncrawly's thread. It sounds like you should also be able to flash firmware through download mode if kernels are working. Also, stay away from galaxys2root and zedomax in the future
Sent from my SGH-I777 using Tapatalk 2
g.kupster said:
So I decided to root my Samsung S2 i7777. Had years of experience flashing HTC hero and Hp touchpad. Thought this might be straightforward as well. Proceeded to get ODIN and ATTGalaxyS2RootStockZedomaxKernel.tar. Flashed it and got pass. Phone proceeded to reboot and was stuck on the Exclamation mark. Tried restarting but no luck same thing. Initially had CWM coming in when I tried the Volume and Power button trick but could not do anything beyond that.
Then I decided that maybe my flash was not proper with that file so I took the siyah kernel and flashed that. This was a pass as well and then back to...the exclamation mark. Now, I cannot get CWM and retarating the phone with the USB connected lets me get into the Downloading window, but I cannot do anything beyond it.
What can I do? Do I need to flash a ROM- is that why I am stuck? How should I flash the ROM from ODIN- if I do get CWM back, can I put the ROM on the SD card and flash it using CWM?
Please help- I am getting stressed out and if I do recover from this, I am going to take a break from rooting :laugh:
Click to expand...
Click to collapse
You shouldn't take a break from rooting. You are just one of a very large group of people that have been blindsided by the galaxys2root website and its rogue developer zedomax. The firmware tools from that site have caused untold problems for people, similar to your problem.
To recover your phone, you need to first flash back to stock. Since you want to root the phone, and ultimately install custom firmware, you should first flash UCKH7 stock plus root package using the one-click downloader which you can get from the guide about how to flash custom binaries without incrementing the flash counter. The link for the guide is in my signature. Read the guide and follow it's directions. That should get you going again. If for some reason you have any trouble, post back here and we'll try to help you out.
Nick281051 said:
I think you should head over to the stickies and look for creepyncrawly's thread. It sounds like you should also be able to flash firmware through download mode if kernels are working. Also, stay away from galaxys2root and zedomax in the future
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Thanks I checked it out..seems like putting the Stock back on might help me. Just so that I understand this better before I do it, am I installing the UCLE5_Stock_Rooted.tar using ODIN and that is enough to get me through.
Thanks
creepyncrawly said:
You shouldn't take a break from rooting. You are just one of a very large group of people that have been blindsided by the galaxys2root website and its rogue developer zedomax. The firmware tools from that site have caused untold problems for people, similar to your problem.
To recover your phone, you need to first flash back to stock. Since you want to root the phone, and ultimately install custom firmware, you should first flash UCKH7 stock plus root package using the one-click downloader which you can get from the guide about how to flash custom binaries without incrementing the flash counter. The link for the guide is in my signature. Read the guide and follow it's directions. That should get you going again. If for some reason you have any trouble, post back here and we'll try to help you out.
Click to expand...
Click to collapse
Thanks for stopping by. I did not see your post when I posted my reply to the previous poster..I am so worried that I might screw it up more that I wanted to be doubly sure about this. from what I read, I am doing Step 2c as indicated below. Am I correct?
Thanks
2c.) How to root by flashing Entropy512's Return/Unbrick to Stock, Kernel + Rooted System Package with Modem using Odin3 One-Click Downloader (Windows)
UPDATE: I did download the "Odin3 One-Click Downloader Stock I-777 UCKH7 with Root no BL" package and extracted the file. Double clicked on it with the phone connected and all I see are the words I777- UCKH7 with Root with a lot of empty boxes below. Went to Odin and I see the phone connected (Com has yellow box) but nothing else is ticked off. Clicking Start does not do anything at all.
At my wits end- will not get any sleep tonite if I don't fix it.
Thanks in advance
I had a similar thing happen after trying to make a backup of the stock rom with Rom Manager (Yes, I know now, thanks much.)
If you keep trying new kernels/roms and it never clears up, you're pretty much stuck with wiping data. It won't wipe your sdcard, but more and more apps are sticking their data in the phone's memory rather than on the sdcard, so if you can get a backup at all, you really should.
Source: Was up until 2:30 the other night trying to make my phone work again. The above is a GUESS - it's probable I missed something that creepyncrawly wouldn't.
Ok more progress..turned off the phone and started 'I777UCKH7 OCD With Root.exe". Got the same window with lot of empty boxes. Had turned off the phone by this time and disconnected it. Now, I connected the phone and pressed the volume buttons. Phone goes into Download mode. Now, the Odin3 window has a Com port for the phone. Now I press start and it goes through a bunch of things before it declares "FAIL" in red. What do I do?
Evidently, the zedomax product you originally flashed, or perhaps the siyah kernel that you flashed second, has made some undesired modification. I'd like to know exactly which package you flashed for each one of these first before I suggest which way to start correcting the problem. Can you please post working links for each of the two downloads that you used? You should still be fine, and will be able to recover the phone.
creepyncrawly said:
Evidently, the zedomax product you originally flashed, or perhaps the siyah kernel that you flashed second, has made some undesired modification. I'd like to know exactly which package you flashed for each one of these first before I suggest which way to start correcting the problem. Can you please post working links for each of the two downloads that you used? You should still be fine, and will be able to recover the phone.
Click to expand...
Click to collapse
This stuff makes me so sad seeing these threads............ Thanx for helping him Creepy, ALWAYZ with 100% accurate info!!! Looks like this is the page he got the tar from in the zip on step 3 http://galaxys2root.com/galaxy-s2-root/how-to-root-att-galaxy-s2-sgh-i777/ Much respect Creepy.....
creepyncrawly said:
Evidently, the zedomax product you originally flashed, or perhaps the siyah kernel that you flashed second, has made some undesired modification. I'd like to know exactly which package you flashed for each one of these first before I suggest which way to start correcting the problem. Can you please post working links for each of the two downloads that you used? You should still be fine, and will be able to recover the phone.
Click to expand...
Click to collapse
The first one was http://galaxys2root.com/galaxy-s2-root/how-to-root-att-galaxy-s2-sgh-i777/
The second one was http://galaxys2root.com/galaxy-s2-root/how-to-root-ics-on-att-galaxy-s2-sgh-i777/
Now I know I need to stay away from galaxy2root. Thanks for looking at this. The status of the phone is I can go into Download mode by pressing volume buttons and connected to USB. ODIN can see the phone (COM is yellow with number). Nothing happens beyond that..
g.kupster said:
The first one was http://galaxys2root.com/galaxy-s2-root/how-to-root-att-galaxy-s2-sgh-i777/
The second one was http://galaxys2root.com/galaxy-s2-root/how-to-root-ics-on-att-galaxy-s2-sgh-i777/
Now I know I need to stay away from galaxy2root. Thanks for looking at this. The status of the phone is I can go into Download mode by pressing volume buttons and connected to USB. ODIN can see the phone (COM is yellow with number). Nothing happens beyond that..
Click to expand...
Click to collapse
The zedomax rooting kernel you flashed first is for Gingerbread version UCKH7, and was posted last October, shortly after the phone was released. If you had UCKH7 on the phone before you flashed that, it should have booted up fine. Most people I have heard about are able to use that rooting kernel successfully. So I need more information in order to be able to trouble shoot your situation.
First, are you sure your phone is SGH-I777, and not SGH-I727?
What firmware was installed on the phone before you flashed the zedomax kernel?
Has any other modification been done on the phone since or even before you had it?
The second kernel you flashed, the Siyah kernel, is an ICS kernel, version 3.4.2. The phone will not boot if the kernel and the system have different versions installed. So I need as much detailed information as possible so know what to do next.
creepyncrawly said:
The zedomax rooting kernel you flashed first is for Gingerbread version UCKH7, and was posted last October, shortly after the phone was released. If you had UCKH7 on the phone before you flashed that, it should have booted up fine. Most people I have heard about are able to use that rooting kernel successfully. So I need more information in order to be able to trouble shoot your situation.
First, are you sure your phone is SGH-I777, and not SGH-I727?
What firmware was installed on the phone before you flashed the zedomax kernel?
Has any other modification been done on the phone since or even before you had it?
The second kernel you flashed, the Siyah kernel, is an ICS kernel, version 3.4.2. The phone will not boot if the kernel and the system have different versions installed. So I need as much detailed information as possible so know what to do next.
Click to expand...
Click to collapse
The phone is SGH-I777 from AT&T. (I'll check the phone when I get home and reconfirm) The phone had the ICS installed (through the Kies update) before I (stupidly) tried the Zedomax Kernel. I just bought the phone new so no other modification had been done. After I had installed the Zedomax I had been able to see CWM if I did the power Volume trick but I cannot do it now since I installed the Siyah.
Hope that helps. Let me know if you need more info.
g.kupster said:
The phone is SGH-I777 from AT&T. (I'll check the phone when I get home and reconfirm) The phone had the ICS installed (through the Kies update) before I (stupidly) tried the Zedomax Kernel. I just bought the phone new so no other modification had been done. After I had installed the Zedomax I had been able to see CWM if I did the power Volume trick but I cannot do it now since I installed the Siyah.
Hope that helps. Let me know if you need more info.
Click to expand...
Click to collapse
OK. The phone was new, and most likely came with Gingerbread 2.3.6 UCKK6 installed. You updated it using kies to ICS 4.0.3 UCLE5. Just asking for your confirmation here.
Then you tried to root with zedomax kernel, which is a Gingerbread 2.3.4 UCKH7 kernel, which explains why it flashed successfully, but failed to boot, since you can't have a Gingerbread kernel and an ICS system together. You were able to boot into ClockworkMod Recovery in the kernel though. We can't blame this problem on zedomax. That kernel usually works ok. You started modifying your phone before you were familiar enough with the phone and it's firmware. The error of flashing a Gingerbread kernel onto an ICS system was yours.
Next you flashed the Siyah v3.4.2 ICS kernel. This kernel should be compatible with the UCLE5 system files that are on the phone. It seems to me that the phone should now boot, and I'm not really sure from this sequence what might have been altered that prevented the phone from booting and also prevented the Odin flash back to stock from succeeding. The only thing you have flashed so far is two kernels. No other partitions should have been touched.
What kind of error message do you get when you try to boot into recovery mode using vol+ vol- Pwr?
creepyncrawly said:
OK. The phone was new, and most likely came with Gingerbread 2.3.6 UCKK6 installed. You updated it using kies to ICS 4.0.3 UCLE5. Just asking for your confirmation here.
Then you tried to root with zedomax kernel, which is a Gingerbread 2.3.4 UCKH7 kernel, which explains why it flashed successfully, but failed to boot, since you can't have a Gingerbread kernel and an ICS system together. You were able to boot into ClockworkMod Recovery in the kernel though. We can't blame this problem on zedomax. That kernel usually works ok. You started modifying your phone before you were familiar enough with the phone and it's firmware. The error of flashing a Gingerbread kernel onto an ICS system was yours.
Next you flashed the Siyah v3.4.2 ICS kernel. This kernel should be compatible with the UCLE5 system files that are on the phone. It seems to me that the phone should now boot, and I'm not really sure from this sequence what might have been altered that prevented the phone from booting and also prevented the Odin flash back to stock from succeeding. The only thing you have flashed so far is two kernels. No other partitions should have been touched.
What kind of error message do you get when you try to boot into recovery mode using vol+ vol- Pwr?
Click to expand...
Click to collapse
That seems correct (with regards to the sequence of events of the phone).
The error message is just the words "SAMSUNG GALAXY SII GT1900"..with a huge exclamation at the bottom. It stays like that until I do a battery pull.
g.kupster said:
That seems correct (with regards to the sequence of events of the phone).
The error message is just the words "SAMSUNG GALAXY SII GT1900"..with a huge exclamation at the bottom. It stays like that until I do a battery pull.
Click to expand...
Click to collapse
Please verify this - the screen says "Samsung Galaxy SII GT-I9100" assuming yours was a typo. Yellow triangle with exclamation mark?
This is what you get when you try to boot the phone normally, and also when you try to enter recovery mode using the three button method, vol+ vol- and power?
creepyncrawly said:
Please verify this - the screen says "Samsung Galaxy SII GT-I9100" assuming yours was a typo. Yellow triangle with exclamation mark?
This is what you get when you try to boot the phone normally, and also when you try to enter recovery mode using the three button method, vol+ vol- and power?
Click to expand...
Click to collapse
Yes, that is correct. It was a typo. I get the exclamation mark when I do the normal boot. I am going to confirm this evening if I get the same error with the 3 button method.
g.kupster said:
Yes, that is correct. It was a typo. I get the exclamation mark when I do the normal boot. I am going to confirm this evening if I get the same error with the 3 button method.
Click to expand...
Click to collapse
Post the answer when you have your phone in hand and I'll suggest something to try.
creepyncrawly said:
Post the answer when you have your phone in hand and I'll suggest something to try.
Click to expand...
Click to collapse
Ok, I tried that just now and I got a message 'Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again'. There is an image of a cell phone and computer with an exclamation mark between them
g.kupster said:
Ok, I tried that just now and I got a message 'Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again'. There is an image of a cell phone and computer with an exclamation mark between them
Click to expand...
Click to collapse
I'm not working from first hand experience, but I'm fairly good at correlating information and making deductions. Something in the sequence of events doesn't add up to me. You're sure you have the I777? You pulled the battery and looked at the label?
At this point any suggestions that I can offer are based on educated speculation. The first thing to try would be to flash an ICS kernel using Odin, but you have already done that. I would suggest that you try that again, but discard the tar you already have and download the tar again, from here. That may be the same place you downloaded it before, not sure. Be sure to use the original USB cable that came with the phone.
Hey peeps
Ok I've been at this for two straight days now in order to try and unbrick this Telus Fascinate SGH-T959P
My buddy initially attempted to flash it with something and really messed it up to the point that even the battery wouldn't charge.
I don't even care if I get it to stock.. an amazing Rom/Kernel combo will also work.
So this is where I am today... and I have spent the last two days non-stop trying to fix this thing...I have been through sooo many forums posts and websites my brain is about to cook.
Software I am using
Odin v1.7 and v1.83.. I try to use the newest one.. just in case.
ADB / SDK installed and am able to push files across to the sdcard in my phone... everything seems good in that dept
Files that have got me to where I am today
T959TLJL3 Froyo original firmware (apparently)... but can not flash all of the files from the package ..zimage and a few others just fail to flash
s1_odin_20100512.pit file (Have atlas_v2.2.pit also but haven't had as much success with it)
SGH-T959-Stock_plus_voodoo_CwM_2.3.4v2
su-2.3.6.3-efgh-signed
I can successfully boot the phone into download mode every single time using the volume up and down while plugging in the usb cable
Also if i just hit the power button I get a Telus 4G / Samsung splash screen and then the phone boots into CwM Voodoo Recovery v3.0.2.8x (Orange??)
In the CwM recovery mode, I can now finally mount all partitions and it looks like things will flash.
Now that I've finally got this phone to this point, I don't want to mess it up.
I want to make sure I have the right files to complete this little project.
Need some direction from the pros.. Am I able to flash a custom rom now ? And if so, what one is best to use.
From this point how can I revert to stock? Do I have the right files ? And how since Odin fails to flash the ones I have.
I figured going to stock first was easier, then use Kies to update it.
Show me the way
Thanks.
jROC
Wow... I got it .. Finally... After I figure out exactly what I used for files.. I will let you know.
All I can tell you right now is that I was flashing a single files at a time then powering down and coming back into download mode to flash the next file.
Right now the phone is all booted up and Running Android v2.3.3 (GB LKG2) and even tho the phone is actually a T959P.. the boot screen shows up as a T959D. Interesting.
jroc99 said:
Wow... I got it .. Finally... After I figure out exactly what I used for files.. I will let you know.
All I can tell you right now is that I was flashing a single files at a time then powering down and coming back into download mode to flash the next file.
Right now the phone is all booted up and Running Android v2.3.3 (GB LKG2) and even tho the phone is actually a T959P.. the boot screen shows up as a T959D. Interesting.
Click to expand...
Click to collapse
Can you send me the T959P stock files please
robbylaw said:
Can you send me the T959P stock files please
Click to expand...
Click to collapse
No single file that I downloaded was able to flash the phone.
I ended up flashing individual files... and kinda had to mix and match, but was able to get the phone booting back into Android OS
However the phone was missing the EFS folder with IMEI info and such..
Still was not able to recover it 100%.
Message me with your email and I will try to send what I used.
jroc99 said:
No single file that I downloaded was able to flash the phone.
I ended up flashing individual files... and kinda had to mix and match, but was able to get the phone booting back into Android OS
However the phone was missing the EFS folder with IMEI info and such..
Still was not able to recover it 100%.
Message me with your email and I will try to send what I used.
Click to expand...
Click to collapse
i messaged you
Ok peeps... If anyone is looking for a firmware file to get their phone booting back into droid I have one that works.
Works on Telus T959P
I have dropbox setup and can share with you that way, just message me.
I need a copy
Sent from my GT-P5113 using xda app-developers app
I've been trying to unbrick an T959P as well, have it so i can also boot into CWM (from SGH-T959-Stock_plus_voodoo_CwM_2.3.4v2) but can never get it too boot into the OS. Tried several files to revert it back to stock but so far nothing has worked. Any hints would be appreciated, thanks in advance
To do it, get this file.
https://gofile.io/?c=tJd0Pd
Then get odin v1.85
https://gofile.io/?c=WHkZHO
Launch odin with admin powers (sudo/su for linux, or whatever).
Then click PDA and select the tar.md5 file and start.
Hopefully it soft bricked not hard bricked.
Fury_Phoenix said:
To do it, get this file.
https://gofile.io/?c=tJd0Pd
Then get odin v1.85
https://gofile.io/?c=WHkZHO
Launch odin with admin powers (sudo/su for linux, or whatever).
Then click PDA and select the tar.md5 file and start.
Hopefully it soft bricked not hard bricked.
Click to expand...
Click to collapse
I posted that in 2013 the device is long gone, thanks for the input though.
draekko said:
I posted that in 2013 the device is long gone, thanks for the input though.
Click to expand...
Click to collapse
Do you have twrp or cwm for the phone?
Fury_Phoenix said:
Do you have twrp or cwm for the phone?
Click to expand...
Click to collapse
I don't have the phone or any software related to that phone. That post was from 7 years ago.
Hello, I've been rooting my phones for a long time and have never had any issues with the phone bricking on me. I made some noobish mistakes when flashing illusion ROM and formatted the system partition and thats where everything went downhill. After that i could get into TWRP and I tried several different ROMS and nandroid backups and nothing would work, just kept giving me the Galaxy Note 2 start screen that wouldn't go away, I waited hours several times I tried this. I found out how to get back to stock with Odin so I tried that and finally got back to stock 4.1.2.
I then tried the casual root method and got partition errors and when I unplugged my phone and tried to boot it back up all I get is a yellow triangle saying that my phone is trying to run unauthorized software and to take it to my nearest Verizon store. I can boot into download mode still but now my computer(Windows 8) will not recognize my phone. It makes the connection sounds but it doesn't show up in my device list or in my device manager. From here I tried uninstalling and re-installing the Samsung drivers but to no avail it still doesn't recognize my phone. Neither my computer or Odin recognize it plugged in. Can someone please help me? give me anything else to try, please.
casual killed the odin driver...the same thread you restored to stock look at the bottom of the section for the link to restoring the odin driver.
Keep reading.... at least thats how I fixed my phone today. I didnt realize I needed to unlock the bootloader so I ended up with the unauthorized software yada yada yada.....lots of reading, youtube video research, xda posts, trial and errors and sheer luck not to brick it worse and I was back up and running in a few hours learning a lot on the way....dont give up!!!
Sent from my SCH-I605 using xda app-developers app
How did you fix your phone?
I got the message about unauthorized software on my i605 note2. When I boot into recovery, I get the message. If I boot into download mode, I can use odin. I tried in reroot with root66 (just grasping at straws) and it took it. Then, the minute I unplugged, boom, the message.
I tried note 2 toolbox and got now where.
I downloaded original firmware from Sammobile.com. I have to unzip it, then look for it with odin I guess.
Amy ideas? Help??
Sent from my SCH-I545 using xda app-developers app
---------- Post added at 04:55 PM ---------- Previous post was at 04:53 PM ----------
How did u get back to stock w odin?
I have the message when I boot into recovery. I can boot into download mode and odin sees my phone.
Sent from my SCH-I545 using xda app-developers app
ciniob said:
How did you fix your phone?
I got the message about unauthorized software on my i605 note2. When I boot into recovery, I get the message. If I boot into download mode, I can use odin. I tried in reroot with root66 (just grasping at straws) and it took it. Then, the minute I unplugged, boom, the message.
I tried note 2 toolbox and got now where.
I downloaded original firmware from Sammobile.com. I have to unzip it, then look for it with odin I guess.
Amy ideas? Help??
Sent from my SCH-I545 using xda app-developers app
---------- Post added at 04:55 PM ---------- Previous post was at 04:53 PM ----------
How did u get back to stock w odin?
I have the message when I boot into recovery. I can boot into download mode and odin sees my phone.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Stay away from that toolbox. Only use droidstyle's guide. Did you try the vramc3 file? That will make it completely stock again. Then use casual. Then flash roms again
Sent From My Sticky Note, Too?
How do I get Odin to recognize I605.zip file?
BoostedB18C said:
Stay away from that toolbox. Only use droidstyle's guide. Did you try the vramc3 file? That will make it completely stock again. Then use casual. Then flash roms again
Sent From My Sticky Note, Too?
Click to expand...
Click to collapse
I downloaded odin and unzipped it. I downloaded I605vramc3_I605VZ...zip.
I unzipped odin (I've used it before but I decided to unzip the latest copy just in case there were some upgrades...). I pressed "Pit" and looked for the file. I was unable to find it. So per the guide, I unzipped the .zip file with 7zip. Odin is still unable to find something that I can use. It's like Odin doesn't see the .zip or the unzipped .zip.
How do I get all those files that unzipped turned into something that Odin can find and that I can use?
I know Odin works. Grasping at straws I injected Root 66 into my note2. But of course that didn't remove the offending files so I still get the Unauthorized Software notice.
So in sum, can you tell me how to get Odin to locate the files I downloaded per the guide?
Thank you so much in advance for your patients. I'm not really new to this it's just that this is the first time that I've bricked my phone. Funny thing is the S4 took the goo manager just fine and then I was able to load TWRP onto the S4 with no problem.
I have not unlocked the S4 and I don't thing I unlocked the Note2. I know I used Easy Unlock on one of my phones but I think it was the Razr Maxx.
Anyway, the Note 2 was doing just fine until I tried to put TWRP on it. then I got the dreaded message.
Can't get Odin working
Bean running Beans v21 since it came out and loving it. Yesterday I installed the NBC Million Second Quiz app from the play store, and it froze my phone on a black screen....capacitive buttons would light up, and I could get the reboot menu, but selecting reboot did nothing. No worries -- I pulled the battery and restarted, and was stuck on boot animation. No worries -- booted into TWRP recovery, wiped cache and davlik. Reboot. Still stuck on boot animation. Now worried. Go back into TWRP and re-install Beans v21...It goes through Aroma, but stays on 0% installing forever. Now I figure that somehow the boot loader got re-locked, though can't imagine how that would happen. Boot into Bootloader, and it does say that it is the Samsung standard. Next I put it into download mode and ran CASUAL for 605. It takes, says it rewritten the bootloader, but when it tries to reboot the phone, I am again stuck on the boot animation forever. No problem -- now I should be able to go back into TWRP, wipe data, re-install a ROM since the phone is unlocked again, and move forward. But now when I go into recovery I no longer get TWRP..now I get the Verizon yellow triangle, I assume becuase CASUAL couldn't reboot to complete. I downloaded odin, the pit, and the 605 image and tried to restore to factory, but odin can't connect. I am guessing that this is because CASUAL replaced Odin.
I see a link to a youtube video, but can't open it from work.
So ... Can someone outline for me how to get odin to connect again after using CASUAL. Or, if there is a better next step, I'm all ears!
I am starting to think that someone at Verizon stumble across some way to slam that dreaded triagle onto our note2. Mine worked just fine until a few days ago when i tried to load twrp.
My counter shows 1 and my kernel shows custom (hence giving verizon a way out of the warranty). Funny thing though, i never opened the bootloader, i never re-rommed. I just rooted.
I am stuck. I can't get odin to see the original firmware i downloaded from this forum. I tried unzipping it w 7zip. I have the unzipped files but still odin can't see them.
What am i doing wrong here?
What does your counter show? Does it show a custom kernel ("yes" displayed when you open the note into downloadmode under kernel)?
Where did u c the video? Point me in that direction and I'll watch it for u and me and let u know.
Sent from my Nexus 10 using xda app-developers app
It WORKS!! My Note2 is back!!
ciniob said:
I am starting to think that someone at Verizon stumble across some way to slam that dreaded triagle onto our note2. Mine worked just fine until a few days ago when i tried to load twrp.
My counter shows 1 and my kernel shows custom (hence giving verizon a way out of the warranty). Funny thing though, i never opened the bootloader, i never re-rommed. I just rooted.
I am stuck. I can't get odin to see the original firmware i downloaded from this forum. I tried unzipping it w 7zip. I have the unzipped files but still odin can't see them.
What am i doing wrong here?
What does your counter show? Does it show a custom kernel ("yes" displayed when you open the note into downloadmode under kernel)?
Where did u c the video? Point me in that direction and I'll watch it for u and me and let u know.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
For those of you who have been following my saga. I have now recovered my Note2. I installed I605Vramc3 using Odin for the S3. I had to find the file that I downloaded (C:\Users\John\Desktop\KIES_HOME_I605VRAMC3_I605VZWAMC3_1098177_REV04_user_low_ship.tar.md5). I then copied that file into DESKTOP on my notebook. Now, I was able to point Odin in that direction. I plugged in my note while in Download mode, injected the file, and waited for the reboot. Botta bang, botta boom, the note rebooted with a flurry on downloaded new app updated.
The only problem I have is that I don't have root. Now I have to figure out how to inject root. But that's for another day!! As for now, I am up an running. I thought for sure I had a $600 paper weight.
The warning is gone and thank God it all works.
Thank you to everyone that participated in this saga. It's nice to know that I am not alone.
By the way, Casual repartitions your device. That may be why it failed for an earlier poster.
Update!
I just finished installing No You Verizon R515. My Baseband is I605VRAMC3. I am on 4.1.2. The instalation was a breeze. I am now safely backed up w TWRP.
Many thanks to Adam. Also thanks to Droidmotter video.
I am stoked I am so looking forward to going back into the Verizon store I went to for help and telling them I will not be spending $700 bones on a new note2!!
What kind of computer are you using?
Sent from my SCH-I605 using xda app-developers app
ciniob said:
I am starting to think that someone at Verizon stumble across some way to slam that dreaded triagle onto our note2. Mine worked just fine until a few days ago when i tried to load twrp.
My counter shows 1 and my kernel shows custom (hence giving verizon a way out of the warranty). Funny thing though, i never opened the bootloader, i never re-rommed. I just rooted.
I am stuck. I can't get odin to see the original firmware i downloaded from this forum. I tried unzipping it w 7zip. I have the unzipped files but still odin can't see them.
What am i doing wrong here?
What does your counter show? Does it show a custom kernel ("yes" displayed when you open the note into downloadmode under kernel)?
Where did u c the video? Point me in that direction and I'll watch it for u and me and let u know.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
I have had a rooted for for 3 years now. G Nexus and now note 2. Wiped....flashed....backed up....wiped and flashed again hundreds of times. 2 days ago I wiped and tried to flash a nightly and bam.... nothin. Went to nandroid back and nothing there! Re booted and got yellow triangle. Wouldnt let me even boit into odin. After hours of screwing around I threw it against a wall.....dunked it in the toilet.... poured gas on it and lit that mofo. Paid 99 bucks and had assurion send me a replacement. My wife said I better not root it! Have made it 24 hours so far. Dont think im gonna make it much longer..... m u s t r o o o o t!
jersey droid said:
My wife said I better not root it! Have made it 24 hours so far. Dont think im gonna make it much longer..... m u s t r o o o o t!
Click to expand...
Click to collapse
You..., must..., root. You..., will..., root. TWRP, Titanium backup, they are calling you from the path less traveled. You can not resist. Your wife does not understand. You..., will..., ROOT..., ROOt..., ROot..., Root..., root..., roo... , ro... , r...,
You now it was funny. When I finally recovered my note2, I paused to contemplate my success.
I spent a few minutes then reading the posts of those who unsuccessfully tried to root using Casual. All I could think of was the fact that after a week of not being able to use my Note, I was not going to risk it.
Besides, I have my rooted S3. I am running android apps on my BB Q10. Hell, I even have the Nexus 10 and the Ipad (and two ipods) (I devices jb'n of course).
Did I really want to take the time and risk the yellow triagle?
I rooted it. No hick ups what-so-ever.
You must root. You can't not root.
Sent from my SCH-I605 using xda app-developers app
BoostedB18C said:
Stay away from that toolbox. Only use droidstyle's guide. Did you try the vramc3 file? That will make it completely stock again. Then use casual. Then flash roms again
Sent From My Sticky Note, Too?
Click to expand...
Click to collapse
Vramc3 was the solution, well, almost... I couldn't get Odin to see the file. Fortunately I placed it in the desktop folder on my notebook, odin saw it and i'm up and running.
Thank you for your help.
Sent from my SCH-I605 using xda app-developers app
DaveKnowsAll said:
Bean running Beans v21 since it came out and loving it. Yesterday I installed the NBC Million Second Quiz app from the play store, and it froze my phone on a black screen....capacitive buttons would light up, and I could get the reboot menu, but selecting reboot did nothing. No worries -- I pulled the battery and restarted, and was stuck on boot animation. No worries -- booted into TWRP recovery, wiped cache and davlik. Reboot. Still stuck on boot animation. Now worried. Go back into TWRP and re-install Beans v21...It goes through Aroma, but stays on 0% installing forever. Now I figure that somehow the boot loader got re-locked, though can't imagine how that would happen. Boot into Bootloader, and it does say that it is the Samsung standard. Next I put it into download mode and ran CASUAL for 605. It takes, says it rewritten the bootloader, but when it tries to reboot the phone, I am again stuck on the boot animation forever. No problem -- now I should be able to go back into TWRP, wipe data, re-install a ROM since the phone is unlocked again, and move forward. But now when I go into recovery I no longer get TWRP..now I get the Verizon yellow triangle, I assume becuase CASUAL couldn't reboot to complete. I downloaded odin, the pit, and the 605 image and tried to restore to factory, but odin can't connect. I am guessing that this is because CASUAL replaced Odin.
I see a link to a youtube video, but can't open it from work.
So ... Can someone outline for me how to get odin to connect again after using CASUAL. Or, if there is a better next step, I'm all ears!
Click to expand...
Click to collapse
Follow up -- Simply put: Delete installed samsung drivers in applications and device manager (plug in the device so you can see them, then delete them) and then plug in the phone and allow it to re-install drivers from windows update (or you can download yourself, since windows update can take a long time).
Once I got connected, I was able to ODIN in a stock image -- couldn't use Route 66, as it still gave me the yellow triangle, but VRAMC3 stock worked. Then back to Casual, TWRP, and freedom once again.
So, this all started last year when i wanted to disable updates. For the life of me, i cant remember what i did but there have been no updates. Recently, I have been getting the OTA notification to update. So i did that and when it installs it gives an error at 26%. My phone is rooted and has USB debugging on so i put it in download mode and tried to use ODIN to update it with both the stock firmware and KitKat. they both failed. Today, I tried to do it again but added the file to BL instead of AP in ODIN. Now my phone gives the "Firmware upgrade encountered an issue" screen. I tried to use Kies to fix it but it doesnt connect when this screen is up. When i restart the phone in download mode, then my computer detects the device.
I have a ATT gs4 model SGH-I337
Please HELP!
tbsrules2 said:
So, this all started last year when i wanted to disable updates. For the life of me, i cant remember what i did but there have been no updates. Recently, I have been getting the OTA notification to update. So i did that and when it installs it gives an error at 26%. My phone is rooted and has USB debugging on so i put it in download mode and tried to use ODIN to update it with both the stock firmware and KitKat. they both failed. Today, I tried to do it again but added the file to BL instead of AP in ODIN. Now my phone gives the "Firmware upgrade encountered an issue" screen. I tried to use Kies to fix it but it doesnt connect when this screen is up. When i restart the phone in download mode, then my computer detects the device.
I have a ATT gs4 model SGH-I337
Please HELP!
Click to expand...
Click to collapse
flash a stock rom and then fastboot flash your stock recovery, then update your phone the update should be triggered in the stock recovery,with a custom recovery, it won't work
the only other easy way around this besides doing what I said is to look for a firmware thread for your device and flash the firmware as a op who has tested it states.
toolhas4degrees said:
flash a stock rom and then fastboot flash your stock recovery, then update your phone the update should be triggered in the stock recovery,with a custom recovery, it won't work
Click to expand...
Click to collapse
Thank you so much for your help! When i try to do this, i get an error. I received this error before as well when trying do this with both the update and the one that came stock. Please see attached image.
tbsrules2 said:
Thank you so much for your help! When i try to do this, i get an error. I received this error before as well when trying do this with both the update and the one that came stock. Please see attached image.
Click to expand...
Click to collapse
try this http://www.androidrootz.com/p/galaxy-s4-stock-firmwares.html
then use your previous unlock/root method after upgrading
toolhas4degrees said:
try this http://www.androidrootz.com/p/galaxy-s4-stock-firmwares.html
then use your previous unlock/root method after upgrading
Click to expand...
Click to collapse
So i did that but still got an error. I think that one of the reasons why it was messing up before is an issue with Kies blocking the port from opening. So i closed that out per the below thread.
http://forum.xda-developers.com/showthread.php?t=1622790
But it started and the status bar on my phone is now blue (which is what how this bigger issue started before) I found this other link that kind of fits whats going on. Should i just follow the PIT instructions from here and of course just restart my phone again?
http://www.droidviews.com/how-to-unbrick-your-bricked-samsung-galaxy-s4-gt-i9500-gt-i9505/
tbsrules2 said:
So i did that but still got an error. I think that one of the reasons why it was messing up before is an issue with Kies blocking the port from opening. So i closed that out per the below thread.
http://forum.xda-developers.com/showthread.php?t=1622790
But it started and the status bar on my phone is now blue (which is what how this bigger issue started before) I found this other link that kind of fits whats going on. Should i just follow the PIT instructions from here and of course just restart my phone again?
http://www.droidviews.com/how-to-unbrick-your-bricked-samsung-galaxy-s4-gt-i9500-gt-i9505/
Click to expand...
Click to collapse
I think you may want to pm the developer of kies to solve your issue, since I don't have your device, that's about as much help as I can be.
toolhas4degrees said:
I think you may want to pm the developer of kies to solve your issue, since I don't have your device, that's about as much help as I can be.
Click to expand...
Click to collapse
UPDATE: so my phone is actually booting now since i re-partitioned it. As i am trying to update to the latest firmware i am still getting an error.
What update were you on before you started? And there's a newer update or 2 past NB1 now.
Sent from my One using XDA Premium 4 mobile app
es0tericcha0s said:
What update were you on before you started? And there's a newer update or 2 past NB1 now.
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Im pretty sure i was at 4.3. So everything was working and then i found a random article saying that with the ALL_ATT_I337UCUFNB1_I337ATTFNB1_505595_REV06_user_low_ship_MULTI_CERT.tar.md5 update, you have to put in the PIT file again. So i did that and now my phone turns on and says custom, but then shuts off. I can go into download mode and recovery. I tried to factory reset everything but to no avail.
tbsrules2 said:
Im pretty sure i was at 4.3. So everything was working and then i found a random article saying that with the ALL_ATT_I337UCUFNB1_I337ATTFNB1_505595_REV06_user_low_ship_MULTI_CERT.tar.md5 update, you have to put in the PIT file again. So i did that and now my phone turns on and says custom, but then shuts off. I can go into download mode and recovery. I tried to factory reset everything but to no avail.
Click to expand...
Click to collapse
Hmm, the pit might be why you're having issues. Most updates don't need the separate pit file. If it's needed, it's often packaged in the main tar file. I would just redo the Odin flash without pit and factory reset afterwards.
es0tericcha0s said:
Hmm, the pit might be why you're having issues. Most updates don't need the separate pit file. If it's needed, it's often packaged in the main tar file. I would just redo the Odin flash without pit and factory reset afterwards.
Click to expand...
Click to collapse
When i try to do this, it says "Fail" is there a way that I can contact you directly?
Ill give whoever helps me with this $10 tonight via paypal
tbsrules2 said:
When i try to do this, it says "Fail" is there a way that I can contact you directly?
Ill give whoever helps me with this $10 tonight via paypal
Click to expand...
Click to collapse
What step does it fail at?
My contact info is in my signature.
es0tericcha0s said:
What step does it fail at?
My contact info is in my signature.
Click to expand...
Click to collapse
I private messaged you
I have a S4 i545 for Verizon. It was on 4.2.2 rooted and I upgraded using Fireflash with I545_OC1_Stock_DeOdexed_ROMwNK4_BL.zip. Everything seemed fine so I was using Titanium back up to remove the bloatware and then my battery died. When I charged it and booted up it got to the Verizon screen and hung there. I reset and tried several more times. I tried to use odin and flash a stock 4.2.2 ROM SCH-I545_VZW_1_20140330160240_yni63xq6zh and I also tried a 4.4.2 rom. Odin gave a an error and failed. I then tried going into the boot loader and flash the I545_OC1_Stock_DeOdexed_ROMwNK4_BL.zip also. Not sure if this was foolish or not but when I booted up I got to a black screen and there was a voice talking, maybe some sort of app that was running, but I couldn't do anything.
Right now when I turn on the phone it says firmware upgrade encountered an issue. Please select recovery mode in kies and try again. I tried connecting it to my computer and opening kies but it doesn't find it. If anyone can point me in the right direction on how to unbrick my S4 I would appreciate it. I know I screwed up.
as long as you can access ODIN you can unbrick. since your on 4.4.2 get the original rom and install. re root and install your rom of choice. from there if you have a previous backup in titanium you can restore
Sent from my LG-D415 using Tapatalk
I was on 4.2.2. I tried downloading the original ROM for this but it didn't work in Odin.
Problem is I can't get into download mode now, or recovery mode even. It's just at that screen I mentioned above. So Odin isn't recognizing my phone.
thats outside my knowledge base. sorry. good luck
Sent from my LG-D415 using Tapatalk
bump up
dr0832 said:
Problem is I can't get into download mode now, or recovery mode even. It's just at that screen I mentioned above. So Odin isn't recognizing my phone.
Click to expand...
Click to collapse
so if you hold down VOL- and power it doesn't go into download mode?
It won't be recognized in Odin until you get back to download mode. - in Odin then you'd want to flash the PIT file and the ROM you need.
The only other way to fix would be to get ahold of a copy of Verizon's Software Upgrade Assistant/Software Recovery Assistant, which looks like someone has uploaded here:
http://forum.xda-developers.com/showthread.php?t=2469615
The Software Recovery Assistant should fix it if nothing else does, I have used it before.
No when I turn it on it goes straight to the screen I mention with a yellow triangle and it does the same if I hold all the buttons down like you normally would to get in recovery.
I assume a battery pull didn't help. Since you have MDK, it MIGHT be worth it to get the JTAG dongle, which will boot the phone into download mode. It is about 3 bucks.
I tried installing in windows xp, windows 7 and windows 8 with no luck. I clicked the exe and it does nothing. I then tried installing on a MAC. It installed but when I went to run it the software opened for 1 second and then close with an error software closed unexpectedly. The I updated the software on the MAC and the software opened but the second I plugged in the phone it gave the same error. The MAC did find the phone though but windows did not.
bump
dr0832 said:
bump
Click to expand...
Click to collapse
Just plug the phone (on that screen) into your PC and see if it shows up in Odin.
If not, pull the battery, and hold the volume down and power buttons as you put the battery back in. Then choose Continue.
Did you read my post? I have done that. My phone is hard bricked. I can't get into recovery mode and therefore I can't get into download mode so therefore odin won't find my phone.
dr0832 said:
Did you read my post? I have done that. My phone is hard bricked. I can't get into recovery mode and therefore I can't get into download mode so therefore odin won't find my phone.
Click to expand...
Click to collapse
Which ROM did you flash, link?
Ahhh. The linked version of the Verizon Software Upgrade Assistant doesn't work. Sorry about that.
I just pulled the .iso from my S4 and posted it up, try this one: https://www.androidfilehost.com/?fid=24052804347780563
Per npjohnson advice I was able to get the phone into download mode. I misread your post at first so sorry about that. Now I need to figure out how to fix this. I flashed Lollipop originally so does that mean I can't actually go back to 4.2.2 using a stock ROM? Can someone point me to a ROM I should try to flash since the so called stock ROM's I have tried are failing in Odin.
I tried flashing this one:
http://stockroms.net/file/GalaxyS4/SCH-i545/VRUAMDK_NoWipe.tar.zip
It came from here:
http://galaxys4root.com/galaxy-s4-stock-firmware/
As for the Verizon assistant that was just posted it does not install just like the other. I click it and the screen flashed and then it does nothing.
dr0832 said:
Per npjohnson advice I was able to get the phone into download mode. I misread your post at first so sorry about that. Now I need to figure out how to fix this. I flashed Lollipop originally so does that mean I can't actually go back to 4.2.2 using a stock ROM? Can someone point me to a ROM I should try to flash since the so called stock ROM's I have tried are failing in Odin.
I tried flashing this one:
http://stockroms.net/file/GalaxyS4/SCH-i545/VRUAMDK_NoWipe.tar.zip
It came from here:
http://galaxys4root.com/galaxy-s4-stock-firmware/
As for the Verizon assistant that was just posted it does not install just like the other. I click it and the screen flashed and then it does nothing.
Click to expand...
Click to collapse
What lollipop did you flash originally? OTA?
I was rooted and then I flashed I545_OC1_Stock_DeOdexed_ROMwNK4_BL which I think is android 5.0.1. I used flashfire.
This was the thread I followed:
http://forum.xda-developers.com/gal...-to-update-to-i545oc1-5-0-1-keeproot-t3096558
Did the battery die on you? I think this is where you need the debrick image....
dr0832 said:
I was rooted and then I flashed I545_OC1_Stock_DeOdexed_ROMwNK4_BL which I think is android 5.0.1. I used flashfire.
This was the thread I followed:
http://forum.xda-developers.com/gal...-to-update-to-i545oc1-5-0-1-keeproot-t3096558
Click to expand...
Click to collapse
Probably should try the full factory image linked here: http://forum.xda-developers.com/gal...pment/odin-i545vrugoc1-factory-image-t3160125
That will put you on 5.0.1 OC1 including bootloader. You'll then root with Kingroot, use Super-sume to replace Kingroot with SuperSu and then you can use the NON-MDK ROM with FlashFire. (odex, or deodex if you want to use xposed modules.