Thought I'd better post this before everyone flashes these sbfs and looses downgradability (is that a word?)
So as you may have worked out this process is if you have never flashed a non downgradable .sbf i.e you have never flashed 2.51 eclair or the 2.2 GB/US 2.2 froyo. If you flashed these then this won't work for you and youve lost downgrability.
Follow the process below, This works with the TMobile US and The GB 3.4.2 Firmwares.
It may seem long winded, but it is the only way to get it running with everything working ok and still downgradable/able to flash other .sbf, most notably the cam flash working 100% - fully sync'd and no greeny blue tinge to it.
Need the Chinese 2.2 release – Download Here
Need the system.img nandroid and boot/devtree.sbf – Download here
Also now added the GB system image+md5 - the one that racca added in the original thread. Download hear
• Flash the Chinese .sbf by RSD lite
• Once booted root via superoneclick http://bit.ly/gUzV19 then reboot (make site debugging on)
• Install Clockworkmod recovery app http://bit.ly/dOdhKc , open app, install recovery and then boot into recovery (make sure debugging is off whenever you boot into recovery
• Wipe data/cache in recovery
• Flash the Tmob 3.42 system image(pre rooted) via advanced restore (folder need to be put in goapkrev/backup folder)
• Once restored pull battery, put battery back in while holding up to get into bootloader
• Flash the boot/devtree.sbf once its rebooted after this you are done.
If you want to use the GB release then just restore the system.img from the GB release.
Enjoy and don't get locked in peoples.
Thanks to adlx whom I enjoyed working with to figure this out - team effort! +as always Sorensiim for the hosting!
I don't think you actually need to flash anything other than boot/devtree.
I tried TMO with uk2.51 and it was just fine.
And if someone followed your post exactly as it is now. Chances are they'd
get their phone bricked (since many are already on 2.51).
Easy to fix for sure, but since it is most likely meant for less experienced
users, we really don't want that, right?
BTW
Thanks for writing it up.
Quick question for you Higgsy...
On one of the original T-Mobile Froyo threads, you posted update files to bypass the Motoblur Setup ("Skip_Blur_adlx-signed" worked fantastically...much thanks!).
Are those modifications included in these posted files already?
EDIT: Went ahead and tried it both with and without the update. Answer is that you cannot skip Moto Setup with this install; however, the Skip_Blue_adlx-signed update will allow you to if the update is applied before leaving recovery.
EDIT: Credit goes to adlx, as it was his file (mis-remembered...should have known better from the file name though). Using Higgsy's instructions and links and adlx's update, I now have a working working US 3.42 with the Motoblur setup bypassed. Thanks to all those who made that possible.
sorry to bother, but as I am now having the green light problem after flashing the "flash fix" several weeks ago, can I get the normal flash back using this method?
and thank you for your work....
conradlyn said:
sorry to bother, but as I am now having the green light problem after flashing the "flash fix" several weeks ago, can I get the normal flash back using this method?
and thank you for your work....
Click to expand...
Click to collapse
No you can't. Nandroid backup and/or SBF won't do anything on that front.
As I am on the UK sbf, this will not be of much use to me. Thankfully, I have no issues with that sbf, so I do not need this.
That said, thank you from those who do.
racca said:
No you can't. Nandroid backup and/or SBF won't do anything on that front.
Click to expand...
Click to collapse
what do you mean by "on that front"?
means that fix package consists some fundamental codes that had thoroughly change the hardware control? and nandroid backup as well as SBF could not overwrite that part?
Forgot to put in the post this is if you have not flashed a non downgradable .sbf before, although I would have thought people would be able to work that out by the nature of the thread.
This will work and will fix you cam flash if you are coming from 2.21+2.35 Eclair ROMs or 2.2 Chinese ROM where you haven't flashed a non downgradable .sbf
Higgsy said:
If you want to use the GB release then just restore the system.img from the GB release.
Click to expand...
Click to collapse
Can you provide a link to that image?
Raccroc said:
Quick question for you Higgsy...
On one of the original T-Mobile Froyo threads, you posted update files to bypass the Motoblur Setup ("Skip_Blur_adlx-signed" worked fantastically...much thanks!).
Are those modifications included in these posted files already?
EDIT: Went ahead and tried it both with and without the update. Answer is that you cannot skip Moto Setup with this install; however, the Skip_Blue_adlx-signed update will allow you to if the update is applied before leaving recovery.
Click to expand...
Click to collapse
I never posted that! and I never used that fix! On the US 3.4.2 you can't skip setup, on the GB 3.4.2 you can skip set up.
conradlyn said:
sorry to bother, but as I am now having the green light problem after flashing the "flash fix" several weeks ago, can I get the normal flash back using this method?
and thank you for your work....
Click to expand...
Click to collapse
If you never installed a non downgradable sbf as per the updated op then yes.
racca said:
No you can't. Nandroid backup and/or SBF won't do anything on that front.
Click to expand...
Click to collapse
appriciate you helping people mate, but let me answer the questions that people have on a procedure that I have written #justsayin
Raccroc said:
On one of the original T-Mobile Froyo threads, you posted update files to bypass the Motoblur Setup ("Skip_Blur_adlx-signed" worked fantastically...much thanks!).
Are those modifications included in these posted files already?
EDIT: Went ahead and tried it both with and without the update. Answer is that you cannot skip Moto Setup with this install; however, the Skip_Blue_adlx-signed update will allow you to if the update is applied before leaving recovery.
Click to expand...
Click to collapse
I think I did post this Skip_Blur_adlx-signed, as I'm adlx lol (although I'm registred here as adlxdum). And yes, it has to be flashed RIEGHT AFTER restoring the nandroid, as I stated. (I can't find the post...)
EDIT: was http://forum.xda-developers.com/showpost.php?p=10930470&postcount=149
Thanks mate, my DEFY is perfect now.
Muznyu said:
Thanks mate, my DEFY is perfect now.
Click to expand...
Click to collapse
Whoop!!!!!!!!!!!!!!!!!!!!!!
Higgsy said:
If you never installed a non downgradable sbf as per the updated op then yes.
Click to expand...
Click to collapse
too bad that you didn't mention this when the post was originally created. when i see this answer, my defy has already been stuffed with 2.2 GB.
conradlyn said:
too bad that you didn't mention this when post was originally created. when i see this answer, my defy has already been stuffed with 2.2 GB.
Click to expand...
Click to collapse
My advice to anyone when something new comes out (not that its any consolation I'm sorry) is to sit back and watch how things pan out, rather than jumping in.
Higgsy said:
My advice to anyone when something new comes out (not that its any consolation I'm sorry) is to sit back and watch how things pan out, rather than jumping in.
Click to expand...
Click to collapse
i also tried to hold on to this rule even before i bought my defy, but just can't reject the temptation of new ROMs...
you couldn't imagine how much i hate myself now, damn!
i could only pray for a real fix on the flash light by great guys like you, Higgsy
Higgsy said:
appriciate you helping people mate, but let me answer the questions that people have on a procedure that I have written #justsayin
Click to expand...
Click to collapse
I might have misread the question
What I meant was that this is not likely to fix the green light problem,
which is not what's asked obviously.
racca said:
I might have misread the question
What I meant was that this is not likely to fix the green light problem,
which is not what's asked obviously.
Click to expand...
Click to collapse
It does fix the green light problem, I wouldn't have posted it if I hadn't spent hors testing to find a fix for the problem lol
Higgsy said:
It does fix the green light problem, I wouldn't have posted it if I hadn't spent hors testing to find a fix for the problem lol
Click to expand...
Click to collapse
man, it is astonishing to see that it does fix, it seems that the green light indeed could be fix. but how?
is it only can be done by your operation procedure, or some independent files could be ported and flashed to fix?
Thanks a lot Higgsy. I'll try your turorial. Could I translate your topic to put it on a French forum ? (i'll put a link to the original thread)
Related
Here you folks go. Off of my phone to you. http://www.multiupload.com/YOXKQ18YW0. You Must have 2.1 with the 3.6 Update. I would recommend making a backup before applying. Use at your own use. If you get a Status 7 error, see my thread in the General forum on how I resolved it. Have Fun!
how is it? faster than 2.1?
Oh yeah. More bloatware, but that's easy to remove. Internet speed is faster. Phone is more responsive. Nice to have the Hotspot feature now. Overall a worthy upgrade. Now to wait for 2.3
can i use this update for my finland rom 3.42? or this is just for TMo version?
runeblade said:
Here you folks go. Off of my phone to you. http://www.multiupload.com/YOXKQ18YW0. You Must have 2.1 with the 3.6 Update. I would recommend making a backup before applying. Use at your own use. If you get a Status 7 error, see my thread in the General forum on how I resolved it. Have Fun!
Click to expand...
Click to collapse
Would you happen to have original t-mobile 2.1 in sbf format?
Unfortunately no-one has one for the US. I'm guessing you updated to the leaked version? The good news is that if my suspicion is correct a nandroid backup of this should play fine with the updated firmware. If you look at the difference its minor. 34.4.9 vs 34.4.4. I have not yet had the time to make one yet. I'll try to do so tonight.
What did you have to do with the update.zip in order to upgrade your defy? I'm on 2.1 with the 3.6 update, I'm rooted with superoneclick, and I have it copied to the root of my sd. Did you use clockworkmod recovery?
nanek921 said:
What did you have to do with the update.zip in order to upgrade your defy? I'm on 2.1 with the 3.6 update, I'm rooted with superoneclick, and I have it copied to the root of my sd. Did you use clockworkmod recovery?
Click to expand...
Click to collapse
Its an update zip file signed by company so you should enter stock recovery by power+vol down and then select update from zip.
hmm... how about flash 3.4.2-107 TMobile US Blur with RSDlite and then
update.zp?
Just tried it. No go.
It checks for the right build fingerprint before it continues. You need to have 6.36.0 or it aborts.
The Nandroid backup theory mught be the one that works...
no clue said:
hmm... how about flash 3.4.2-107 TMobile US Blur with RSDlite and then
update.zp?
Click to expand...
Click to collapse
Beach_Head said:
Just tried it. No go.
It checks for the right build fingerprint before it continues. You need to have 6.36.0 or it aborts.
The Nandroid backup theory mught be the one that works...
Click to expand...
Click to collapse
Thanks for the update.
...... I just want something official now
( I am on official Chinese 2.21 build 1.11, it is fast, specially when you skip Blur registration. But, just in case I need my phone service by t-mobile .... )
The leaked T-Mobile SBF was fast too.
But yeah, an official one would be better.
If the Nandroid method doesn't work, I hope someone posts an SBF soon...
no clue said:
Thanks for the update.
...... I just want something official now
( I am on official Chinese 2.21 build 1.11, it is fast, specially when you skip Blur registration. But, just in case I need my phone service by t-mobile .... )
Click to expand...
Click to collapse
As for right build fingerprint, yes you are right. It is picky as hell. In the other thread I also mentioned that it is checking for apps. For example, I have Blockbuster disabled....it checked for it, didn't find it, and failed. I spent over 4 hours last night getting this to a point that it would work. Way Way too much hassle. Unfortunately I don't think I'm going to get to do a backup tonight. Was up way too late last night/this morning working on this and put in a 12 hour day. As soon as I get a breather I will. Sorry.
No worries!
Is there any way to edit the build.prop file so that I can get the update to work?
runeblade said:
As for right build fingerprint, yes you are right. It is picky as hell. In the other thread I also mentioned that it is checking for apps. For example, I have Blockbuster disabled....it checked for it, didn't find it, and failed. I spent over 4 hours last night getting this to a point that it would work. Way Way too much hassle. Unfortunately I don't think I'm going to get to do a backup tonight. Was up way too late last night/this morning working on this and put in a 12 hour day. As soon as I get a breather I will. Sorry.
Click to expand...
Click to collapse
Unfortunately I don't have an un-updated Defy in front of me to pull the strings. I'll look at one of the ones at work tomorrow. If you read the error though it should tell you exactly what it is looking for. Mine did. Aslo try deleting the logwrapper. The was one of the holdups on mine.
I have the string. I'm just wondering if it would work if I do edit it...
Where do I locate logwrapper?
runeblade said:
Unfortunately I don't have an un-updated Defy in front of me to pull the strings. I'll look at one of the ones at work tomorrow. If you read the error though it should tell you exactly what it is looking for. Mine did. Aslo try deleting the logwrapper. The was one of the holdups on mine.
Click to expand...
Click to collapse
I just loaded this update.zip on my fiance's Defy...didn't wipe data or cache, it's booting right now....stuck at the T-Mobile "Stick Together" screen, waiting for the initial long boot
EDIT: Booted, running 2.2.1 now! So far so good, it's a little slow but it would be while it catches up. I have an Atrix and it's almost the identical interface.
can you make a sbf file of entire build?
Nandriod back up please! im dying for it
zencoran said:
Nandriod back up please! im dying for it
Click to expand...
Click to collapse
just flash the update.zip...why bother with a nandroid?
I'm getting a critical error in RSDlite... B655 I believe. I've tried 3 different computers with the drivers and rsd setup correctly. I've flashed this same sbf multiple times before without fail. For some reason the phone is kicking this error and I can't get back to stock for warranty purposes. Does anyone have a Nandroid of their stock Cincinnati Bell 2.1 I can use to get back to stock so I can get it replaced under warranty? All I need is the boot and System images I believe. If anyone can help me out I would appreciate it. Thanks.
Check out Mioze7Ae's replies in this thread. You can also look here
3rdstring said:
Check out Mioze7Ae's replies in this thread. You can also look here
Click to expand...
Click to collapse
Thanks man, that should work. I'm after the barebones restore so the first link was perfect.
EricDET said:
Thanks man, that should work. I'm after the barebones restore so the first link was perfect.
Click to expand...
Click to collapse
If you are taking your phone in, don't forget to unroot and delete Superuser.apk
SOLVED - How to flash the Proper (Fixed) Stock Rooted Image
Description: This is 100% stock with just Superuser/su added and overwrites every partition to stock but keeps your personal data, apps, settings the same (just like the stock factory image).
Samsung Official USB Drivers - Link
ODIN v3.07 - Link
Proper Rooted Stock Image - Download or (Torrent Link) - MD5 = be4350a56e739eaf7a4184352d653a7b
1. Install USB drivers
2. Download ODIN v3.07
3. Backup your data
4. OPTIONAL: Do a factory reset (highly recommended if you have issues with your current ROM)
***WARNING: Step #4 will erase internal storage but not microSD card***
5. Download the above Proper Rooted Stock Image file and extract the tar file from inside it
6. Boot phone into ODIN mode (See here for how-to)
7. Flash the extracted tar file using ODIN v3.07
You should now have a like new condition stock image and rooted with all issues resolved.
Credit goes completely to mrRobinson for creating this image for us. Thank you sir. (Original Post) + (Details How It Was Made)
To Install Official CWM Recovery
1. After following above process, download "Rom Manager" from the Play Store
2. Open Rom Manager
3. Select "Flash ClockworkMod Recovery"
4. Select "Samsung Galaxy S3 (Verizon)" down at the bottom and let it flash
5. Once completed you can reboot to CWM by selecting "Reboot into Recovery" from Rom Manager
ORIGINAL REQUEST
After various testing, it seems many users are experiencing various issues with the rooted System.img provided by the OP in this thread. Many report findings of "Sprint related elements" as well as various keyboard issues and things not working as they should. I wish I had the knowledge myself but on behalf of the community, I'd like to request for someone with knowledge of this guide to remake the same rooted system.img as in the original but this time confirmed with using the original stock Verizon SCH-I535 image downloadable here.
I'm sure many of us here would highly appreciate this effort and we can also carry out further testing as many users reported that soon as they flash back to that stock image, their issues have disappeared and everything starts working properly.
I will quote another user in reference to this:
BungeBash said:
Just formatted back to stock until issues can be resolved. The stock image (which I'm told this root is + su) lost all Sprint instances and any strange extra options. Also the Keyboards are back to functioning. Not to be a conspiracy theorist, but I feel that the root image has more going on with it than what we are told.
Click to expand...
Click to collapse
Here's to hoping one of you knowledgeable developers are able to assist us with this request.
Click to expand...
Click to collapse
open1your1eyes0 said:
After various testing, it seems many users are experiencing various issues with the rooted System.img provided by the OP in this thread. Many report findings of "Sprint related elements" as well as various keyboard issues and things not working as they should. I wish I had the knowledge myself but on behalf of the community, I'd like to request for someone with knowledge of this guide to remake the same rooted system.img as in the original but this time confirmed with using the original stock Verizon SCH-I535 image downloadable here.
I'm sure many of us here would highly appreciate this effort and we can also carry out further testing as many users reported that soon as they flash back to that stock image, their issues have disappeared and everything starts working properly.
I will quote another user in reference to this:
Here's to hoping one of you knowledgeable developers are able to assist us with this request.
Click to expand...
Click to collapse
If you don't like it, dont flash it.
tonu42 said:
If you don't like it, dont flash it.
Click to expand...
Click to collapse
Hardly helpful for those who already flashed it... I just want it fixed, or a work around. If it's something as simple as uninstalling a few things, or replacing some databases, I'm fine with that. I just don't want to redo everything, and re-restore everything with Titanium Backup.
tonu42 said:
If you don't like it, dont flash it.
Click to expand...
Click to collapse
Not to be rude but we're not. That's why I'm making this request to remake with proper image. Because we are skeptical of the original one that was made. I PMed the OP of that thread and he claims to have used that image but in user's experience something is definitely different from stock, hence we're requesting a remake to test this.
open1your1eyes0 said:
Not to be rude but we're not. That's why I'm making this request to remake with proper image. Because we are skeptical of the original one that was made. I PMed the OP of that thread and he claims to have used that image but in user's experience something is definitely different from stock, hence we're requesting a remake to test this.
Click to expand...
Click to collapse
If you'd like, you can flash the stripped version, and I have a second zip that will restore all the stripped apps.
I did have some odd issues with SwiftKey crashing after flashing the image. Not sure if that has to do with it or not.
tonu42 said:
If you don't like it, dont flash it.
Click to expand...
Click to collapse
Useless post.
What would be useful is someone with the requisite knowledge being able to remake this exploit with the Verizon source in order to have maximum compatibility.
open1your1eyes0 said:
After various testing, it seems many users are experiencing various issues with the rooted System.img provided by the OP in this thread. Many report findings of "Sprint related elements" as well as various keyboard issues and things not working as they should. I wish I had the knowledge myself but on behalf of the community, I'd like to request for someone with knowledge of this guide to remake the same rooted system.img as in the original but this time confirmed with using the original stock Verizon SCH-I535 image downloadable here.
I'm sure many of us here would highly appreciate this effort and we can also carry out further testing as many users reported that soon as they flash back to that stock image, their issues have disappeared and everything starts working properly.
I will quote another user in reference to this:
Here's to hoping one of you knowledgeable developers are able to assist us with this request.
Click to expand...
Click to collapse
Are you talking about the system.img from invisibleks first image?
Link: http://forum.xda-developers.com/showpost.php?p=28402010&postcount=1
Or the stripped and rooted one?
Link: http://forum.xda-developers.com/showpost.php?p=28459565&postcount=1
I think the first one invisiblek made is pretty much what you are asking for. Remember, there's no SCH-I535 source code out there for people to build a system image from. These images are hacked system images from the stock image (found here: http://samsung-updates.com/device/?id=SCH-I535 ). One can't really "remake" the system image until we can fully bypass the encrypted and locked bootloader.
If you want to roll your own system image with the su binary and SuperUser you can follow the instructions here:
http://forum.xda-developers.com/showpost.php?p=27801304&postcount=1
They seem pretty straight forward.
However, I'm pretty sure that's what invisiblek did for his/her first rooted image (the one that isn't stripped).
Hope that helps. I can't do much of anything till my SGS3 arrives tomorrow.
ALQI
alquimista said:
Are you talking about the system.img from invisibleks first image?
Link: http://forum.xda-developers.com/showpost.php?p=28402010&postcount=1
Or the stripped and rooted one?
Link: http://forum.xda-developers.com/showpost.php?p=28459565&postcount=1
I think the first one invisiblek made is pretty much what you are asking for. Remember, there's no SCH-I535 source code out there for people to build a system image from. These images are hacked system images from the stock image (found here: http://samsung-updates.com/device/?id=SCH-I535 ). One can't really "remake" the system image until we can fully bypass the encrypted and locked bootloader.
If you want to roll your own system image with the su binary and SuperUser you can follow the instructions here:
http://forum.xda-developers.com/showpost.php?p=27801304&postcount=1
They seem pretty straight forward.
However, I'm pretty sure that's what invisiblek did for his/her first rooted image (the one that isn't stripped).
Hope that helps. I can't do much of anything till my SGS3 arrives tomorrow.
ALQI
Click to expand...
Click to collapse
The one in bold is what this request is about actually. Basically to remake that. Because the non-stripped rooted system.img that invisiblek is the one causing most issues for people and people have noted things in there that are not in the factory image. I tried to follow that guide myself but I must be missing something because most of those commands do not work for me. Mind you this is on a Windows PC.
I could do it, but it'd require more time than whats it worth. Sorry.
tonu42 said:
If you don't like it, dont flash it.
Click to expand...
Click to collapse
You are a WORM!!!!!!!
Sent from my Galaxy Nexus using xda app-developers app
tonu42 said:
I could do it, but it'd require more time than whats it worth. Sorry.
Click to expand...
Click to collapse
No worries. Very understandable as that guide is quite time consuming and not for everyone. Thanks for your support either way.
tonu42 said:
If you don't like it, dont flash it.
Click to expand...
Click to collapse
tonu42 said:
I could do it, but it'd require more time than whats it worth. Sorry.
Click to expand...
Click to collapse
Two completely pointless comments.
open1your1eyes0 said:
No worries. Very understandable as that guide is quite time consuming and not for everyone. Thanks for your support either way.
Click to expand...
Click to collapse
You sir are a better man than me for being so humble in response to these replies.
I'm assuming invisiblek DID in fact use the VZW image if the phone still had all the VZW nonsense in it (VZ Navigator, for example) as that would not be found in the Sprint image. Equally, if "all" he did was follow the steps in the link, then someone else doing the same is likely to produce the same result.
tonu42 said:
If you'd like, you can flash the stripped version, and I have a second zip that will restore all the stripped apps.
Click to expand...
Click to collapse
If you have these, have you posted them anywhere? That might have been a useful thing to do.
Here is all the removed apk's in a CWR zip.
http://www.mediafire.com/?6jv8wn9l5n0li9y
I actually saw that guide you posted about creating our own. I can try and whip something up tonight if I get some time. If not, tomorrow is my "Friday" at work, so I'll have time tomorrow evening for sure.
BungeBash said:
I actually saw that guide you posted about creating our own. I can try and whip something up tonight if I get some time. If not, tomorrow is my "Friday" at work, so I'll have time tomorrow evening for sure.
Click to expand...
Click to collapse
Thank you much sir. You assistance would be greatly appreciated.
Unfortunately I do not have a linux box so the guide does not work for me.
It's already been diff'd. There is no difference between the stock image and the rooted one here except for su and binaries:
http://rootzwiki.com/topic/29256-ro...erizon-galaxy-s-iii/page__st__110#entry793038
I'm guessing VZW has done more to the stock image on the phone than the stock one that is available for download, which is causing these differences.
Goose306 said:
It's already been diff'd. There is no difference between the stock image and the rooted one here except for su and binaries:
http://rootzwiki.com/topic/29256-ro...erizon-galaxy-s-iii/page__st__110#entry793038
I'm guessing VZW has done more to the stock image on the phone than the stock one that is available for download, which is causing these differences.
Click to expand...
Click to collapse
Considering I loaded the first root mod, then reverted to the image that it was created from and have 2 different setups I'd say two different files were used.
open1your1eyes0 said:
The one in bold is what this request is about actually. Basically to remake that. Because the non-stripped rooted system.img that invisiblek is the one causing most issues for people and people have noted things in there that are not in the factory image. I tried to follow that guide myself but I must be missing something because most of those commands do not work for me. Mind you this is on a Windows PC.
Click to expand...
Click to collapse
If its already been diff'd with the original, maybe the sammy-updates file ain't so good.
Hmm, I wonder if we dump the system.img from an untouched stock phone (like the one I get tomorrow), and inject that img with su, would that work out any better? I'll look into this tomorrow.
I'll also take a look at re-rolling the system.img from the sammy-updates files in the meantime.
I'll report back when and if I have a viable image.
~ALQI
alquimista said:
If its already been diff'd with the original, maybe the sammy-updates file ain't so good.
Hmm, I wonder if we dump the system.img from an untouched stock phone (like the one I get tomorrow), and inject that img with su, would that work out any better? I'll look into this tomorrow.
I'll also take a look at re-rolling the system.img from the sammy-updates files in the meantime.
I'll report back when and if I have a viable image.
~ALQI
Click to expand...
Click to collapse
According to users, flashing that sammy-update firmware got rid of all the issues and the Sprint related stuff. Just, FYI.
If anyone is up for the remake, you might want to try making it out of this one. Not sure if it's any different but it's from another well known Samsung firmware site.
Link to stock factory firmware
i want to root my phone but Sprint seems to have patch the root exploit, so i am thinking of doing a factory restore.
does anyone know what software version it will resort back to, currently i am on 2.3.4.
You will still be on 2.3.4 you need to search for the method then reds until your head hurts
[.-.]
http://forum.xda-developers.com/showthread.php?t=1357157
This root method works wonders nothing is more better then to learn to manually root your device. Of course you can use the tool provided in the, the development forums, but I personally enjoy learning to do things without the use of developed tools.
If you need help feel free to ask we are here to help ^_^
Good luck don't turn your device into a brick READ READ AND READ FOLLOW INSTRUCTIONS EXACTLY HOW THEY ARE YOU WILL BE A OK.
Sent from my PG06100 using xda app-developers app
x2phrack said:
i want to root my phone but Sprint seems to have patch the root exploit, so i am thinking of doing a factory restore.
does anyone know what software version it will resort back to, currently i am on 2.3.4.
Click to expand...
Click to collapse
Use the manual method by Indirect if you want to have more control over what you're doing (also does not void your warranty) and definitely read read read
I would recommend at least going through the whole "user" section of xda-university before even touching your phone, it has tons of useful information
turkbot said:
You will still be on 2.3.4 you need to search for the method then reds until your head hurts
[.-.]
Click to expand...
Click to collapse
Definitely, also just FYI but when you do a factory restore that simply wipes all app data (both user and system apps)
x2phrack said:
i want to root my phone but Sprint seems to have patch the root exploit, so i am thinking of doing a factory restore.
does anyone know what software version it will resort back to, currently i am on 2.3.4.
Click to expand...
Click to collapse
Best advice I can give you is to Read, Read, Read, and Read some more. Use the search function a ton, as it will help you to get used to resolving issues in the future. Because sometimes even when people are willing to help, answers are hard to come by. Also there are a few links you can check out in my Signature. The Shift community is one of the Best anywhere, so you picked the right device to learn Android with . Welcome to a great forum.
yes yes, i have rooted like 5 phones, but this one is stuck in a boot loop and trying to fix that
x2phrack said:
yes yes, i have rooted like 5 phones, but this one is stuck in a boot loop and trying to fix that
Click to expand...
Click to collapse
Were you rooting with Indirects method and it got stuck in a bootloop on the 4G screen? If so, thats supposed to happen, its not a bug
CNexus said:
Were you rooting with Indirects method and it got stuck in a bootloop on the 4G screen? If so, thats supposed to happen, its not a bug
Click to expand...
Click to collapse
Na i was using you shift rootility tutorial, but i screwed up and put the wrong PG06IMG.zip in the $path. there was 2 versions a 12.7MB and a 227MB one. i didn't realize that i needed to do the 227MB to downgrade first then after it's downgraded then use the 12.7MB one.
so i stopped mid way through and tried to boot normally, which sent me into a boot loop. doing a factory restore fixed the boot-loop and now i am starting over again.
BTW CNexus you have some dead links in your Tut.
You will be on older radios after rooting. Download the ZIP with the most recent radios, WiMAX, and touchscreen firmware from HERE or HERE.
Click to expand...
Click to collapse
Points to dead files / links
x2phrack said:
Na i was using you shift rootility tutorial, but i screwed up and put the wrong PG06IMG.zip in the $path. there was 2 versions a 12.7MB and a 227MB one. i didn't realize that i needed to do the 227MB to downgrade first then after it's downgraded then use the 12.7MB one.
so i stopped mid way through and tried to boot normally, which sent me into a boot loop. doing a factory restore fixed the boot-loop and now i am starting over again.
BTW CNexus you have some dead links in your Tut.
Points to dead files / links
Click to expand...
Click to collapse
Thanks for pointing that out! There are more recent links in the last 2 pages if you want to grab that file right now
EDIT: Links fixed, thanks again
CNexus said:
Thanks for pointing that out! There are more recent links in the last 2 pages if you want to grab that file right now
EDIT: Links fixed, thanks again
Click to expand...
Click to collapse
not a problem, so i should use the 12.7 zip after i have rooted the 2.2 before i use add the Cyanogen Rom or after?
x2phrack said:
not a problem, so i should use the 12.7 zip after i have rooted the 2.2 before i use add the Cyanogen Rom or after?
Click to expand...
Click to collapse
It doesn't matter, you can do it anytime after you have rooted (make sure you flash it in bootloader and not through recovery though)
This has been posted elsewhere but this is such an important and crucial file that I felt it deserved it's own thread, and maybe even a sticky in this section. Several people cannot get their fastboot working, or cannot get RSDlite to work with their phones and they have no other option besides using the recovery they've already flashed, to restore a nandroid of jellybean as came from sprint when the phone was stock. This opens up a wealth of other options that become available to them, there weren't before.
Especially with sbf.droid-developers.org having spotty downloads the past few days I am thankful for the following two files in fixing the phone I had that no longer worked.
kabaldan said:
I've uploaded the OpenRecovery nandroid of stock Sprint JB release here, some time ago:
http://d-h.st/N0p
Click to expand...
Click to collapse
arrrghhh said:
Weird, I never had an issue with downloading from there...
I'm uploading my copy. Give me a few mins.
Edit - Enjoy.
Click to expand...
Click to collapse
Thanks for sharing them.
just out of curiosity, is there some section of the formal update that should go somewhere nandroid backup cannot cover? for example, radio update or something?