Results 1 to 25 of 51
- 05-18-2011, 11:26 AM
Thread Author #1
- 05-18-2011, 12:31 PM #2
- 05-18-2011, 12:53 PM #3
There is a reason i did not do this in the first place. Although this is a simple solution to the problem its an dangerous one at the moment. Because we do not know how this will effect future updates miss matching firmware usually results in update failure so if our basebands do not match our builds and the updates search for this then it may cause a failure..Then the arguement can be made that we can always make another odin package for those who went this route. But again what if they change the radios (because now we need to worry about the LTE one aswell) and the kernel will only work with the new radio. This is my major concern with odin packages until we get an official version. Also in the past when working with the continuum i found that sometime thing go wrong with a flash and it may disable the radio leaving your baseband as unknown. Again we do not have a flashable version of the radio to safeguard us from this.This is why imnuts mentioned to use the odin method only for backing up.
Was all of this considered? - 05-18-2011, 12:55 PM #4
Worked like a charm! It took all of 5 minutes and the majority of that was just downloading drivers/ODIN!
Thanks so much, donation coming soon! This makes life much easier for those of us who didn't have a choice or like me...were dumb...and downloaded the update immediately! - 05-18-2011, 12:58 PM #5Thanked by:
- 05-18-2011, 01:10 PM
Thread Author #6
It crossed my mind. All this is is a dump of ED1 I made and then packaged into a flashable ODIN. When you use this to downgrade you instantly get a popup stating there is an upgrade available (to ED2.) I have a feeling this will in no way effect future updates coming from verizon. Thanks for your concern.
- 05-18-2011, 01:37 PM #7
- 05-18-2011, 01:40 PM
Thread Author #8
- 05-18-2011, 01:41 PM #9
- 05-18-2011, 01:45 PM #10
Edit, I see someone else is having the same problem. I'd like to add:
I have a "gadget serial" in device manager that has an exclamation point next to it. Do the standard Samsung drivers work on this or do we need something else?
I used the drivers that were for rooting that were the Samsung package. - 05-18-2011, 01:46 PM #11
- 05-18-2011, 01:47 PM #12
- 05-18-2011, 01:52 PM #13
- 05-18-2011, 01:58 PM #14
- 05-18-2011, 02:30 PM #15
- 05-18-2011, 04:49 PM #16
- 05-18-2011, 07:35 PM #17
I have provided Drivers and troubleshooting tips in the OP. - 05-19-2011, 07:54 AM #18
After going back to ED1, I accidentally allowed the phone to download the ED2 file. The phone hasn't installed it yet. Does anyone know where is the ED2 file located and what is it named? Can I delete the file to prevent it from being installed or should I just let it install and then use ODIN to go back to rooted ED1?
- 05-19-2011, 08:51 AM #19
- 05-19-2011, 11:35 AM #20
It's probably on the sdcard in the update.zip format (I did the downgrade, and when it booted into recovery it found the update file)
Just don't apply the update, and go through your build.prop and replace all instances of ED1 with ED2 and the messages should stop (they did for me)
Now I'm just patiently awaiting the devs to find a way to root ED2 - 05-19-2011, 12:38 PM #21
- 05-19-2011, 12:50 PM #22
- 05-19-2011, 01:13 PM #23
- 05-19-2011, 01:26 PM #24
- 05-19-2011, 01:47 PM #25
Thank you gentlemen

Sent from my SCH-I510 using Tapatalk



Reply




































