• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [BACKUP] Sprint FG11 stock-rooted+

Ralkkai said:
so with the whole FG11 baseband upgrade literally being a copy/paste job then that means all you'd have to work on as far as your option 1 and 2 goes is to just get an image of 2.3.6 with root flashable and tack on the FG11 file to your guide, right?
Click to expand...

That's one way. Another is that I could do something similar to what I did to make the CWMKeeper, and include the file for the baseband, so that when you flash a zip, it installs the baseband update for you. The only problem there is that then the part of saving the previous baseband as a backup gets skipped, unless I include instructions to do that first, or can find a way to include a routine to do so in the zip....
 
xaelith said:
That's one way. Another is that I could do something similar to what I did to make the CWMKeeper, and include the file for the baseband, so that when you flash a zip, it installs the baseband update for you. The only problem there is that then the part of saving the previous baseband as a backup gets skipped, unless I include instructions to do that first, or can find a way to include a routine to do so in the zip....
Click to expand...

The only problem with including instructions to make a back up first for the baseband is someone would either:

1. Do a cwm backup thinking it would backup the baseband or
2. Just skip it all together.

If there is anyway to include it in the routine, I believe that would be best.

I have said it once and I will say it again. You guys rock. Learning to do these things takes time, knowledge, and guts. I have nothing but the upmost respect for all of you.
 
for the baseband update when u ship out v3, you could just include the FG11 zip with a batch file that runs the copy/paste script that way the folks who aren't so savvy will be able to do it hassle-free
 
niteNarmor said:
The only problem with including instructions to make a back up first for the baseband is someone would either:

1. Do a cwm backup thinking it would backup the baseband or
2. Just skip it all together.
Click to expand...

I plan on being very careful and detailed, explaining that making a backup of the baseband is NOT the same as a nandroid/CWM backup, but you're right. Some people still have problems reading ALL of the directions, much less following them correctly. :D

Ralkkai said:
for the baseband update when u ship out v3, you could just include the FG11 zip with a batch file that runs the copy/paste script that way the folks who aren't so savvy will be able to do it hassle-free
Click to expand...
niteNarmor said:
If there is anyway to include it in the routine, I believe that would be best.
Click to expand...

I don't want to give too much away just yet, but this is the direction I'm leaning with V3. I have some things I still need to read up on and look into, but I believe the next release will be a two-part installation.

niteNarmor said:
I have said it once and I will say it again. You guys rock. Learning to do these things takes time, knowledge, and guts. I have nothing but the upmost respect for all of you.
Click to expand...

Thank you, kind sir. :) I still feel I have a LOOOOOOOOOOONNG way to go before I can consider myself a dev, but I like to believe that I'm making progress. If I haven't changed devices before then, my ultimate goal is to be able to help in some way with CM7/9 for the Ultra. Only time will tell. ;)
 
I'm reposting the baseband zip just for relevance. so this isn't my work and all that jazz. credit goes to PH8AL i think...let me know if that's incorrect

https://dl.dropbox.com/u/77410396/basebandFG11.zip

below is a bash script to install the new baseband over the old one and make a backup to /sdcard etc...basically just like the directions to upgrade to new baseband but automated.

https://dl.dropbox.com/u/77410396/basebandFG11.sh

steps to install:
1. put both files in /sdcard
2. run basebandFG11.sh

it seems like it ends up hanging when trying to run the the script but after i try to do something else it ends up rebooting and creates a baseband.bak file just like in the other thread. since i am on FG11 it hasn't been fully tested yet but i ran it twice and everything seemed right. but yeah, here's my attempt to give back to the community, even if it isn't rocket surgery. if you wanna use this in your installation method/process feel free.
i guess i should also note i did this per niteNarmor's concern of people getting confused as he mentined in #102
 
I updated my baseband successfully. I took some speed tests before and after.
Before:
20120823223953.png


After:
20120823223927.png
 
almost that was nite but I do share the same concern.

I have always been a bit divided on this though.
I prefer to do all of these tasks individually. Yes it is more work but if something goes sides ways you have limited the possible causes. It also teaches a much deeper understanding of the mechanics involved. My opinion is you shouldn't be doing any of this if you are not willing to learn the fundamentals of it.

But years of experience with noobs in a jam over their heads Ive learned that most will opt for the quick route and then complain and complain and complain. So when you are trying to share your work with the public you have to idiot proof the process just for good name alone because they aren't going to blame their own lack of understanding and effort. If that were the case we wouldn't need all bright red warnings and disclaimers every where.

Ralkkai off to do some reading about this method and prolly going to poke around in that .sh file. Understanding the TE method gives me a side by side comparison Im not going to miss.
 
But I can flash my old one back right?
Using that terminal emulator thing felt like I was walking at the top(roof) side of a 4 story building :S
 
Ralkkai off to do some reading about this method and prolly going to poke around in that .sh file. Understanding the TE method gives me a side by side comparison Im not going to miss.
Click to expand...

poke around all you want lol im no pro at this and all i did was basically copy the command lines over from the terminal emulator method.
 
DMajor239 said:
But I can flash my old one back right?
Using that terminal emulator thing felt like I was walking at the top(roof) side of a 4 story building :S
Click to expand...

what i did was i found the baseband.bak after i installed FG11 and renamed it back to mmcblk0p6 just in case i needed it back in a hurry. so if i wanted to bump backto the previous baseband all i need to do is drop or copy/paste that file back into /dev/block and it should replace the one with FG11, thus after reboot being back on the old baseband...kinda sounds complicated but im bad at explaining things too
 
Ralkkai said:
what i did was i found the baseband.bak after i installed FG11 and renamed it back to mmcblk0p6 just in case i needed it back in a hurry. so if i wanted to bump backto the previous baseband all i need to do is drop or copy/paste that file back into /dev/block and it should replace the one with FG11, thus after reboot being back on the old baseband...kinda sounds complicated but im bad at explaining things too
Click to expand...

Sounds about right.

I did a speed test of my own and I saw better numbers then I have ever seen. Hmmmmmm.

:/

Sent from my SPH-M930 using Tapatalk 2
 
i wonder if it has something to do with the actual towers....different cell towers in different areas or something....maybe lol
 
PH8AL said:
just a thought.

Did you clear the cache by a battery pull/hard boot. It would sort itself out after awhile but Im assuming you tested right after the change. Just a normal reboot wouldn't do it.
Click to expand...


I will pull of the battery right now. Also I did try updating my prl and still got the same results.
 
Ralkkai said:
i wonder if it has something to do with the actual towers....different cell towers in different areas or something....maybe lol
Click to expand...

Might be the different cell towers. Cause I get lower speeds at home then when I'm at work or out on the road.

Sent from my SPH-M930 using Tapatalk 2
 
niteNarmor said:
Might be the different cell towers. Cause I get lower speeds at home then when I'm at work or out on the road.

Sent from my SPH-M930 using Tapatalk 2
Click to expand...


That could be true. I live in swfl and didn't know how to change the towers thingy in the app to Miami or Orlando. So I just stuck with what SpeedTest gave me.
I pulled the battery off and still get low speeds =(
Ima downgrade 2morro. But for now ima sleep cus I got school tomorrow.
 
DMajor239 said:
I will pull of the battery right now. Also I did try updating my prl and still got the same results.
Click to expand...
hold a button and make sure to give it plenty of time to clear all the juice from the board.

This is my go to solution works on anything with cache memory.
 
Im looking now for something the equivalent of windows ipconfig/flush to run in terminal emulator before the reboot but all Im finding is the linux equivalent doesn't work on android and the hardboot is the only way.

This might not be the problem but its what comes to mind first from the randomness of it. Definitely is the first thing to tick off the list..
Don't know the time out on this or the size of the cache designated to this. To many variables. It my self perpetuate as well so wouldn't go away.
 
Currently that is a reported bug with android. So far, there is no known fix for it. The best way I know how is to turn the network radio off. Pull battery till it drain completely (believe 2 minutes is the key). Reboot, turn radio back on. Usually that clears any radio problem I have unless I'm the one that screwed it up on the first place. But as far as a flush, no known cure.

Sent from my SPH-M930 using Tapatalk 2
 
I found an A2sd command that will flush the dalvik cache but I don't think thats where it is.

cwm can do this but for that much trouble you can just do the hardboot.

Plus I don't think you could run them together. You would have to do the swap reboot and then back into TE to wipe.

So yeah Im going to say that idea is bust.

something for xaelith though.

su

a2sd sysinfo

exit

displays partion and system info but also saves a complete profile of your system to this location

/data/dtsysdump.txt
 
niteNarmor said:
Currently that is a reported bug with android. So far, there is no known fix for it. The best way I know how is to turn the network radio off. Pull battery till it drain completely (believe 2 minutes is the key). Reboot, turn radio back on. Usually that clears any radio problem I have unless I'm the one that screwed it up on the first place. But as far as a flush, no known cure.

Sent from my SPH-M930 using Tapatalk 2
Click to expand...
The bold confused me..please explain
 
You must log in or register to reply here.
Back
Top Bottom