***This will work on the T-Mobile US branded Vibrant and generic Galaxy S models***
***IMPORTANT: YOU PERFORM THIS AT YOUR OWN RISK, THIS MAY VOID YOUR WARRANTY, I NOR ANYONE ELSE IS RESPONSIBLE IF YOU BRICK YOUR DEVICE.***
***UPDATE: Now you can do this without ADB installed!
The following method should be relatively care-free but there is always a risk with activities like rooting a device or flashing a new firmware.
1. Download the attached zip and rename to: update.zip
2. On your device, navigate to Settings > Applications > USB settings and select Mass storage
3. Plug your device into your computer, select mount USB from your device's pull-down window
4. Copy the update.zip to the INTERNAL SD memory (~14gb on this drive, not the one w/ Avatar if you've still got the 2gb SD card in)
5. Turn your phone off.
6. Hold down volume up and volume down while powering on the phone, this should get you to a recovery menu, you may have to try this a few times.
7. In Recovery menu select 'Reinstall Packages' (use vol_down then power to select)
Phone will reboot
and you have
1. su+Superuser
2. busybox (/system/xbin/busybox)
Original credit goes to LeshaK at Samdroid, I modified the script within update.zip to work on the Vibrant.
Other credits to the fine folks in this thread that noted the vol up+down recovery menu.
I would link to the Samdroid forum but I can't...but check Samdroid > i9000 Development forum for the original post.
Intriguing may try this on Thursday
How easy is it to put back to stock for warranty purposes?
Thank you to the OP for posting this. Does it make sense to append the post with a quick guide to installing and getting ADB to work with Vibrant for those who have never done that? This would make it a truly complete guide to rooting Vibrant.
Thanks for this. I'm planning on getting an AT&T Captivate when it comes out. What would I have to change in your script to have it work on the Captivate? Would it just be a matter of changing the model names in the file updater-script? That seems to be the only file with an updated file date. TIA.
So with this root, will the normal Galaxy S custom rom (modaco) work on the vibrant? or does the rom need adjusting?
Thanks for this . Can't wait until Thursday!!
quickex99 said:
How easy is it to put back to stock for warranty purposes?
Click to expand...
Click to collapse
Not sure exactly, though you could easily delete the super user APK, that's the only real visible sign that this is installed. Doubt they'd check much further. The Samdroid forum post may have info on reverting to stock.
If anyone wants to take this and modify, it should work on the Captivate/Fascinate/Epic with a simple modification, add the model name for each device to this part of updater-script in the zip file:
Code:
assert(getprop("ro.product.device") == "GT-I5800" ||
getprop("ro.build.product") == "GT-I5800" ||
getprop("ro.product.device") == "GT-I9000" ||
getprop("ro.build.product") == "GT-I9000" ||
getprop("ro.product.device") == "SGH-T959" ||
getprop("ro.build.product") == "SGH-T959"
);
Does it make sense to append the post with a quick guide to installing and getting ADB to work with Vibrant for those who have never done that?
Click to expand...
Click to collapse
I'll leave that to someone else, I personally feel that if folks are in this 'development' section then they should be capable of installing and getting ADB running before they do something that could possibly harm their phone if they screw it up.
So with this root, will the normal Galaxy S custom rom (modaco) work on the vibrant? or does the rom need adjusting?
Click to expand...
Click to collapse
Honestly, no idea on this. I'm not willing to risk my Vibrant to this, I'll let someone else be a guinea pig. But I am interested to hear if the wireless hotspot feature can be added back, this is the only item I miss from the Vibrant.
I'm glad it's that easy, now what about wireless tether? It's something that I and others root for almost exclusively.
Has anyone successfully tried this yet?
Considering that the phone doesn't release until Thursday, I highly doubt it.
BigWorldJust said:
Considering that the phone doesn't release until Thursday, I highly doubt it.
Click to expand...
Click to collapse
Considering I have one sitting here in my hands, some people have access so a valid question
lp1527 said:
Considering I have one sitting here in my hands, some people have access so a valid question
Click to expand...
Click to collapse
So. Care to share the results with the people? How about some more info on speed, lag, firmware etc.
Sent from my Htcclay's SuperBad G1 using XDA App
Lag is still there, it's the reason I went for root in the first place, had to perform Paul's lag fix w/ the shipped software. With the lag fix and Launcher Pro this device is quite a joy.
Ship ROM is T959UVJFD.
once i installed the galaxy s drivers, it was REALLY painless and easy. i did it just for the wireless tethering.. and whatever other goodies I can find for this so far... really excited!
justadude said:
Lag is still there, it's the reason I went for root in the first place, had to perform Paul's lag fix w/ the shipped software. With the lag fix and Launcher Pro this device is quite a joy.
Ship ROM is T959UVJFD.
Click to expand...
Click to collapse
Can you elaborate? Do you still have the original shipped OS (Touchwiz and all pre-loaded apps, etc.)? Also, any kind of step-by-step you could provide?
Much appreciated and THANK you!
disturkis4u said:
once i installed the galaxy s drivers, it was REALLY painless and easy. i did it just for the wireless tethering.. and whatever other goodies I can find for this so far... really excited!
Click to expand...
Click to collapse
The wireless tethering is my main reason for rooting so I am very interested which tethering application you are using and which version. Also, where did you get the proper drivers for adb connection? The directions in the first post assume that everybody knows how to use adb which sadly is not the case with me. Any additional information will be greatly appreciated. Thank you in advance.
basataom said:
So with this root, will the normal Galaxy S custom rom (modaco) work on the vibrant? or does the rom need adjusting?
Click to expand...
Click to collapse
It would probably need some tweaking since the hardware is a bit different. (ei. the button layout)
Lmao, that's why I said highly unlikely, NOT impossible. SMH.
marsupial99 said:
The wireless tethering is my main reason for rooting so I am very interested which tethering application you are using and which version. Also, where did you get the proper drivers for adb connection? The directions in the first post assume that everybody knows how to use adb which sadly is not the case with me. Any additional information will be greatly appreciated. Thank you in advance.
Click to expand...
Click to collapse
I searched for "galaxy s usb driver" in xda and the first link was USB Driver for Galaxy S and Misc Info - xda-developers. There's a rapidshare and multiupload link for download also in that thread. (3rd post or something).
once you extract the usb drivers folders, go to the extracted folder, double click on "setup" and it will install the drivers for you. when you enable usb debugging on your vibrant and plug it in, windows should successfully install the usb drivers. then, go to command, and follow the instructions in the first post
edit: i'm using the app called Wireless Tether version 2.0.1 website is http://android-wifi-tether.googlecode.com
Related
unrEVOked had updated their recovery to v3.1 to solve the windows / connection problem. UnrEVOked will also be releasing S-OFF very soon.
Grab it here and enjoy!
http://www.unrevoked.com/recovery/
v3.1:
* Fixed “Communications with phone unexpectedly interrupted.” error occurring on Windows version.
* Updated to ClockworkMod Recovery 2.5.0.1
* Program sets su permissions even when su is present.
v3.0:
* Add support for Droid Eris.
* Add the ability to function even without root on all supported phones.
* Updated to ClockworkMod Recovery 2.0.2.4.
* Renamed to unrevoked3.
The FAQ:
http://unrevoked.com/rootwiki/doku.php/public/unrevoked2
For those who do not yet have it, the HDBOOT Driver:
http://www.unrevoked.com/rootwiki/doku.php?id=public:windows_hboot_driver_install
New ClockWorkMod Recovery of v2.5.0.5 can be custom flashed with v3.0 and under. This is NOT needed if you use unrEVOked v3.1 as it is built it:
1) Download
http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.0.5-inc.img
2) DO NOT PLUG IN YOUR PHONE
3) Run unrEVOked v3.1
4) Under FILE choose CUSTOM RECOVERY
5) Point to the img file
6) Plug in your phone
jdmba said:
Grab it here and enjoy!
http://www.unrevoked.com/#inc
v3.0:
* Add support for Droid Eris.
* Add the ability to function even without root on all supported phones.
* Updated to ClockworkMod Recovery 2.0.2.4.
* Renamed to unrevoked3.
Click to expand...
Click to collapse
On Behalf almost all of the Incredible users I say THANK YOU!
I am happy to have this right now as it appears I need to nab the OTA and reroot to avoid nag msg every 15 mins. I am sad that it was forced out by someone leaking info and files. I guess use it why we can before its patched in a week or 2.
Thank you VERY much for all the hard work placed in this and all of UnrEVOked's projects. It is VERY appreciated by many.
Im stuck on it asking for su support/permission.
great job. im glad to see this hit before i get my incredible. i didnt want to deal with that stupid SDcard timing bs
barry1685 said:
Im stuck on it asking for su support/permission.
Click to expand...
Click to collapse
help->about...
See if it shows 3.0. If not, redownload.
Shadowmite said:
help->about...
See if it shows 3.0. If not, redownload.
Click to expand...
Click to collapse
can i ask what cartoon your avatar is from? it looks familiar but i cant remember from where
jdmba said:
Grab it here and enjoy!
http://www.unrevoked.com/#inc
v3.0:
* Add support for Droid Eris.
* Add the ability to function even without root on all supported phones.
* Updated to ClockworkMod Recovery 2.0.2.4.
* Renamed to unrevoked3.
Click to expand...
Click to collapse
Thank You unrevoked. I am truely sorry that any of you who work so hard to bring all that you do to so many for free have to deal with some of the things I read on these forums.
I read the forums mostly these days but I have been around many years and involved in many things over this time. Some things remain the same! There are always some who pride themselves on ruining things for others. I guess this is just the way it goes.
The only thing I think I'd like to say to you all is there are many, myself included that do appricate you all and enjoy the fun you bring to so many. Chins up cause there are alot more of us than there are of the few.
in closing.. thank you for ALL you do for me and everyone else
Shadowmite said:
help->about...
See if it shows 3.0. If not, redownload.
Click to expand...
Click to collapse
Thanks man! NVM I found it!
This is awesome! I already had root, but used it to update recovery.
I did have to use sudo in Ubuntu (sudo ./reflash), just like the tool said I might have to.
Thank's unrEVOked. Your hard work and dedication is much appreciated.
Thank you so much!
Team Unrevoked,
Thanks so much for all of your hard work! It is very much appreciated!
Edit: I'm going to try it through my mac (to avoid the drivers) but want to make sure I have all the settingd correct. USB debugging on. Set phone to charge only. Anything else we need to set prior to using this?
is this the link?
http://www.unrevoked.com/recovery/
What is it supposed to do once it gets into HBOOT?
I'm stuck
I have pretty much no knowledge of rooting so I am following the unrevoked guide. I only just started and when I go through the device manager I don't see android 1.0 like the guide says in order to install the hboot drivers..
barry1685 said:
is this the link?
http://www.unrevoked.com/recovery/
Click to expand...
Click to collapse
yeas that is the correct link, I downloaded the linux version and it installed fine.
shoman24v said:
What is it supposed to do once it gets into HBOOT?
Click to expand...
Click to collapse
just let it run through, it will do everything on its own and you will end up at the recovery screen when it is done, and the tool on your desktop will say done.
Ok I'll just leave it. how long does it take? I do see android 1.0 in my device manager.
iedible23 said:
I have pretty much no knowledge of rooting so I am following the unrevoked guide. I only just started and when I go through the device manager I don't see android 1.0 like the guide says in order to install the hboot drivers..
Click to expand...
Click to collapse
you made sure that usb debugging is enabled? settings>applications>developement
if so, power off device hold vol down then press the power button, it will detect the phone and install drivers. once drivers are installed, reboot phone then try the tool.
shoman24v said:
Ok I'll just leave it. how long does it take? I do see android 1.0 in my device manager.
Click to expand...
Click to collapse
it shouldn't take very long, if it shows up as android 1.0 you need to have windows install the drivers, it should do it automatically but you may have to point it to the right ones.
nfcrockett said:
I've downloaded it 4x and still get v2.1
Click to expand...
Click to collapse
I had the same problem, I think Chrome was caching it for me. Once I opened firefox and downloaded it was fine.
I'm new and reading up on rooting, etc. There seems to many links around for ADB and Fastboot but some of the tutorials I have read mention that they "may" install CWR and Superuser also. I might have this wrong though. If I'm correct, does anyone have a link that includes them all? Thanks!
http://forum.xda-developers.com/showthread.php?t=1411193
please look before posting
Attackid1 said:
http://forum.xda-developers.com/showthread.php?t=1411193
please look before posting
Click to expand...
Click to collapse
That's exactly why I'm posting, because I have looked. That's one of the links I have. A link>link>link, etc. A final link to Fastboot + ADB.zip download here doesn't work, in fact, neither does the one for CWR here but the second two links to elsewhere, work.
Attackid1 said:
http://forum.xda-developers.com/showthread.php?t=1411193
please look before posting
Click to expand...
Click to collapse
DONT BE RUDE!
wptski said:
I'm new and reading up on rooting, etc. There seems to many links around for ADB and Fastboot but some of the tutorials I have read mention that they "may" install CWR and Superuser also. I might have this wrong though. If I'm correct, does anyone have a link that includes them all? Thanks!
Click to expand...
Click to collapse
Easy:
First, you sould root your s7. = Superuser.
Then flash CWM via Adb
Easy too:
Flash a Custom Room with Root = Superuser so you have everything.
Theres no package with all in it, or?
exebreez said:
DONT BE RUDE!
Easy:
First, you sould root your s7. = Superuser.
Then flash CWM via Adb
Easy too:
Flash a Custom Room with Root = Superuser so you have everything.
Theres no package with all in it, or?
Click to expand...
Click to collapse
That's one thing that's confusing! Do you have to root first before CWR? I've read so many How To's that my head is spinning as each one links to another and another and another. I don't want to brick my S7 either.
There a How To somewhere that sort-of states that if "whatever" isn't installed automatically, you'll have to download and install. After reading all these How To's and a few videos also with each not exactly the same, this doesn't seem real easy. Of course, I'm a sissy!
Yes, you need to root before installing CWR, otherwise its useless.
giveen said:
Yes, you need to root before installing CWR, otherwise its useless.
Click to expand...
Click to collapse
From my Streak 7 right now, otherwise I'd provide a link that states to install CWR first.
Why do you say that it's useless otherwise?
giveen said:
Yes, you need to root before installing CWR, otherwise its useless.
Click to expand...
Click to collapse
You dont need to root before installing CWM, in fact CWM is plenty useful even if you never root.
All you need is fastboot to install CWM.
TheManii said:
You dont need to root before installing CWM, in fact CWM is plenty useful even if you never root.
All you need is fastboot to install CWM.
Click to expand...
Click to collapse
But dont' you need the SU binaries installed to do such things as install custom ROMS?
SU can only be invoked while android is loaded. It requires android to be fully/nearly fully functional to work.
CWM bypasses anything on storage and directly reads/writes to it. It only requires that the NAND structure be correct (as in the partitions are in the right place and the bootloader is intact)
NVflash completely bypasses everything and only requires the device to be physically intact, it can load on a system with a completly blank/scrambled NAND.
There's a great deal of overlap between flash_image (which requires root) and CWM, but it's like popping in a rescue disk vs safe mode on windows, they do a lot of the same things but have different dependencies.
This is true for unprotected bootloaders like the S7 though. If your device has a protected bootloader/S-ON you do in fact need to be rooted to flash CWM.
On unprotected devices you can directly flash via fastboot and ignore any security in android proper.
TheManii:
Do you have any issues with the procedure provided in this link? http://forum.xda-developers.com/showthread.php?t=1411193
It's essentially correct
TheManii said:
It's essentially correct
Click to expand...
Click to collapse
Looking closely at the procedure, Drivers.zip isn't a file but a folder.
I've heard that some people have driver issues with the ones included in Fastboot+ADB.zip, but they're the stock ones from dell.
I'm not sure how directly installing the dell sync software would fix it as they're the same drivers. BUT I havnt had any issues with the ones in Fastboot+ADB.
Nor have I had anyone able to confirm it in a useful way that they dont work.
I first started to get an S7 directly from Dell to get the v3.2 HC but since their ETA was over a month away, I opted to get it elsewhere. It came with v2.2 and I OTA'd it to v3.2 on day one.
I "think" I installed some drivers to to use Dell Suite sync software but it would try to open but always with an error that closed it, so I gave up!
I have McAfee Security Suite, will that be a problem? Don't think it has a disable switch.
wptski said:
Looking closely at the procedure, Drivers.zip isn't a file but a folder.
Click to expand...
Click to collapse
On my streak there was literally a file called "Drivers.Zip" which is the file I'm referring to. This is NOT the same as the drivers folders in the Fastboot+ADB file. Most importantly it includes 64-bit versions of the drivers. My understanding is that any Streak that ships with Honeycomb has this file. If you got an OTA update or installed a Custom ROM, you would need to get the file elsewhere. I'd be happy to post the version I have, but wasn't sure what the redistribution license is for those...
Rooting Streak 7 - Error in Superuser7.zip
I tried to post in the development forum because I thought my problem belongs to that topic. But as a new user I wasn't allowed to do that.
I flashed the CWM following the Guide. (BTW: Thanks for the great guide). However, applying the superuser7.zip I receive following message:
Finding update package...
Opening update package...
Installing update...
E: Error /emmc/superuser.zip
(Status 0)
Installation aborted.
What is my failure?
Nuke67 said:
I tried to post in the development forum because I thought my problem belongs to that topic. But as a new user I wasn't allowed to do that.
What is my failure?
Click to expand...
Click to collapse
First, post in general for something like that
Root your device with Gingerbreak
Gingerbreak
And if youre asking because its for gingerbread, do it. It will work if you have froyo on your s7.
EwanG said:
On my streak there was literally a file called "Drivers.Zip" which is the file I'm referring to. This is NOT the same as the drivers folders in the Fastboot+ADB file. Most importantly it includes 64-bit versions of the drivers. My understanding is that any Streak that ships with Honeycomb has this file. If you got an OTA update or installed a Custom ROM, you would need to get the file elsewhere. I'd be happy to post the version I have, but wasn't sure what the redistribution license is for those...
Click to expand...
Click to collapse
My Drivers.zip folder contains: readme.txt, setup.exe, setup.msi and tetherxp.inf. All compressed files. What was in your driver.zip file?
exebreez said:
First, post in general for something like that
Root your device with Gingerbreak
Gingerbreak
And if youre asking because its for gingerbread, do it. It will work if you have froyo on your s7.
Click to expand...
Click to collapse
Gingerbreak doesn't work with honeycomb... I've truest and noting happens....
Sent from my Desire HD using XDA App
I heard something recently about fileshare sites being shut down...is that what I'm experiencing. Tried to download files from: http://forum.xda-developers.com/showthread.php?t=1359068 and none of the links work. Actually a couple did but said I could only download a file I uploaded myself. I tried downloading from another thread on this site and had the same problem. Any solutions/alternatives? How can I download from the link I posted above?
Thanks!
Firecracker_RC said:
I heard something recently about fileshare sites being shut down...is that what I'm experiencing. Tried to download files from: http://forum.xda-developers.com/showthread.php?t=1359068 and none of the links work. Actually a couple did but said I could only download a file I uploaded myself. I tried downloading from another thread on this site and had the same problem. Any solutions/alternatives? How can I download from the link I posted above?
Thanks!
Click to expand...
Click to collapse
I see a KJ4 link. Have you tried the KJ5 thread? It's the newest one for our 7310.
Hi nirogu325, thanks for replying. This is what I am trying to do:
-Enable adhoc connection so I can use my windows mobile phone as a hotspot for my tabl, and
-Enable USB charging for my tab in my car and elsewhere, not just wall jack.
Based on what I've read, I need busybox (Titanium back up says it's installed but when I downloaded an app called wifiadhocenabler, it says it is not installed. Installing it from the market says I need Nand Unlock and this is where I'm stuck at the moment. Do you know how to perform this on the P7310? Or an easier way to meet the objectives above?
Thanks again
Firecracker_RC said:
Hi nirogu325, thanks for replying. This is what I am trying to do:
-Enable adhoc connection so I can use my windows mobile phone as a hotspot for my tabl, and
-Enable USB charging for my tab in my car and elsewhere, not just wall jack.
Based on what I've read, I need busybox (Titanium back up says it's installed but when I downloaded an app called wifiadhocenabler, it says it is not installed. Installing it from the market says I need Nand Unlock and this is where I'm stuck at the moment. Do you know how to perform this on the P7310? Or an easier way to meet the objectives above?
Thanks again
Click to expand...
Click to collapse
I assume you're on a stock firmware. If I were you, I'd flash this specific version which is already rooted and has busybox as you can read in the OP. Also, flash the v2d version of the motley kernel and go here for the USB charging script and instructions on enabling. I know that last link is for the 10.1, but it is the one motley linked to in the v2b version changelog in his kernel thread.
After my soft brick yesterday, I used Odin to "install" the version you attached in your General Guide post P310XARKJ5_P7310UEKJ5_HOME.tar.md5). That's the one, right?
Anyway, the good news is, I decided to install BusyBox without doing the Nand Unlock (maybe it was already done?), and it worked! The wifiadhocenabler app works now and I have a connection to my wm phone! Yay! Before trying the app (for the sake of onlookers) I tried the other method with the wpa_supplicant, such as the one here: http://androidtablethacks.com/android-tablet-hacks/how-to-enable-adhoc-wifi-on-android-tablets/ and it did not work for me. The app did!
So now, I'll try the kernel you posted above and then the USB charging.
I'm going to look over your general guide to see if I can figure out how to flash. I'm guessing it's the same or similar to when I recovered my tab in Odin...?
Firecracker_RC said:
After my soft brick yesterday, I used Odin to "install" the version you attached in your General Guide post P310XARKJ5_P7310UEKJ5_HOME.tar.md5). That's the one, right?
Anyway, the good news is, I decided to install BusyBox without doing the Nand Unlock (maybe it was already done?), and it worked! The wifiadhocenabler app works now and I have a connection to my wm phone! Yay! Before trying the app (for the sake of onlookers) I tried the other method with the wpa_supplicant, such as the one here: http://androidtablethacks.com/android-tablet-hacks/how-to-enable-adhoc-wifi-on-android-tablets/ and it did not work for me. The app did!
So now, I'll try the kernel you posted above and then the USB charging.
I'm going to look over your general guide to see if I can figure out how to flash. I'm guessing it's the same or similar to when I recovered my tab in Odin...?
Click to expand...
Click to collapse
If you mean flashing a CWM package as the motley kernel, a file goes in the SDcard, you access the CWM Recovery and flash. That's a generic way BUT depending on what you will flash you may have to wipe. That's why I avoided altogether putting generic instructions regarding CWM packages in my guide (instructions may vary between ROM and kernels). Read your flashable package's thread carefully.
kind of like rooting? Yes, do I have to wipe to flash the motley kernel? I'm not seeing the flashable packages thread, can you point me to it?
Firecracker_RC said:
kind of like rooting? Yes, do I have to wipe to flash the motley kernel? I'm not seeing the flashable packages thread, can you point me to it?
Click to expand...
Click to collapse
No, lol. If you want to flash the motley kernel just follow that thread's instructions. I gave you the motley kernel thread link in a previous post. For kernels, no wipe is necessary, for ROMs, yes.
Ok, thank you. lol
Firecracker_RC said:
Ok, thank you. lol
Click to expand...
Click to collapse
You're welcome. Some people have the tendency NOT to wipe while flashing ROMs...yet complain later on the road. Always wipe when it comes to ROMs if you want to avoid issues. The only bugs you will experience are the ones that come with the ROM already. Better safe than sorry.
Ah, that leads me to wonder...When my tab was soft bricked and I used Odin3 and inserted the KJ5 file into the PDA section, and so on (I think that was flashing), was I supposed to do a wipe before I did that? If so, would it be better if I started from scratch again? ...hoping not, but better now than latter I'm thinking.
Firecracker_RC said:
Ah, that leads me to wonder...When my tab was soft bricked and I used Odin3 and inserted the KJ5 file into the PDA section, and so on (I think that was flashing), was I supposed to do a wipe before I did that? If so, would it be better if I started from scratch again? ...hoping not, but better now than latter I'm thinking.
Click to expand...
Click to collapse
No. ODIN clears everything (including kernels, ROMs and CWM Recoveries). Everything back to stock. I was just referring to flashing other custom ROMs (non-ODIN, i.e. CWM flashable) procedures. Stick to the thread instructions in your chosen ROM and you'll be fine. It's just that some don't follow instructions and due to that, they may experience weird bugs.
That's good news, and strange, because after I used Oden3 (in the way I previously described), all my apps and files were still in tact. Does it just affect the system and not the file memory?
P.S. Hey! I'm no longer a noob! lol I just noticed I am now a "Junior Member".
P.S.S. I'm now running my tablet off my wm hotspot while charging it on my pc! woohoo
Firecracker_RC said:
That's good news, and strange, because after I used Oden3 (in the way I previously described), all my apps and files were still in tact. Does it just affect the system and not the file memory?
P.S. Hey! I'm no longer a noob! lol I just noticed I am now a "Junior Member".
Click to expand...
Click to collapse
That is because you didn't check F.Reset Time on the left side of ODIN before flashing. It is advisable to make sure it is checked. Thanks, I'm gonna put that little but important detail in my guide (dunno how I missed that one ). I advise using Titanium Backup (for apps backup) and then ODIN. You might be fine as you are, but if you ever experience something weird then you know.
Firecracker_RC said:
P.S.S. I'm now running my tablet off my wm hotspot while charging it on my pc! woohoo
Click to expand...
Click to collapse
I'm glad you made it!
Thanks for your support. If I ever have some extra change and feel like making a donation, I'll keep you in mind! Hey, where's your donation link anyway? Better get one!
nirogu325 said:
That is because you didn't check F.Reset Time on the left side of ODIN before flashing. It is advisable to make sure it is checked. Thanks, I'm gonna put that little but important detail in my guide (dunno how I missed that one ). I advise using Titanium Backup (for apps backup) and then ODIN. You might be fine as you are, but if you ever experience something weird then you know.
Click to expand...
Click to collapse
My tablet is definitely a little laggy now, but that could be the 3.2 HC. Since I did not check that off, does it mean that it did not install on a clean wipe? I'm wondering if I should just do it while I remember the path to how I got where I'm at now. I doubt I'll remember everything down the road.
I have been making nandroid backups as well as titanium app backups.
Firecracker_RC said:
My tablet is definitely a little laggy now, but that could be the 3.2 HC. Since I did not check that off, does it mean that it did not install on a clean wipe? I'm wondering if I should just do it while I remember the path to how I got where I'm at now. I doubt I'll remember everything down the road.
I have been making nandroid backups as well as titanium app backups.
Click to expand...
Click to collapse
As for donations, nah it's ok, I am no developer. As for the suggestion, it was just that, a suggestion for next time. Keep that in mind. It will become a habit down the road.
Sent from my GT-P7310
nirogu325,
I'm back to do my clean wipe. I performed the wipe/data reset in nandroid and now it's saying there is an update from KJ5 to LA3. Do you still think the custom kj5 is better than the stock LA3? I'm wondering if I should just install the update, root, install the motley kernel and go from there...?
Hope you're well! I still think you should add a donate link...you don't have to be a developer, your assistance/guidance is equally helpful to the community.
While I'm waiting, I flashed http://forum.xda-developers.com/showthread.php?t=1375112 and then I noticed I have the old CMR so I downloaded your updated package: GTab89Files and I cannot paste a single file from that folder onto my tab. I can paste files from other folders, but this one I copy and when I go to paste the paste option is not enabled; if I drag I get a little red circle with a line through it. Any ideas as to why it's rejecting?
(Obvious Noob warning---) A friend helped me root my Thrill, install ClockworkMod Recovery, and then install CM7 on my Thrill. But I would like to try the LG GB release. Is it necessary to backtrack all the way back to stock to do this (i.e. reinstall the stock ROM, reinstall the stock recovery, unroot, etc.)?
My friend tried using the LG upgrade tool on his LG phone without going back to stock and ended up bricking it. He says that usually within a few days of release, a CMR compatible zip file (usually already rooted) appears here on XDA (I haven't seen it), which makes things easier (but obviously he didn't wait for it himself).
Will a zip be possible for the Thrill GB? (The file seems quite large (420MB), so I'm guessing there is a lot of media included.) Or should I just bite the bullet and backtrack?
Rick
Rick Tillery said:
(Obvious Noob warning---) A friend helped me root my Thrill, install ClockworkMod Recovery, and then install CM7 on my Thrill. But I would like to try the LG GB release. Is it necessary to backtrack all the way back to stock to do this (i.e. reinstall the stock ROM, reinstall the stock recovery, unroot, etc.)?
My friend tried using the LG upgrade tool on his LG phone without going back to stock and ended up bricking it. He says that usually within a few days of release, a CMR compatible zip file (usually already rooted) appears here on XDA (I haven't seen it), which makes things easier (but obviously he didn't wait for it himself).
Will a zip be possible for the Thrill GB? (The file seems quite large (420MB), so I'm guessing there is a lot of media included.) Or should I just bite the bullet and backtrack?
Rick
Click to expand...
Click to collapse
I'm assuming that the official update method was used.
Just use this method after downloading the update. No bricking.
SEE THREAD
The Dark Lestat said:
I'm assuming that the official update method was used.
Just use this method after downloading the update. No bricking.
SEE THREAD
Click to expand...
Click to collapse
Thank you for your help!
Rick
Trojan?
Sorry, but as a noob, I can't post in that other thread.
It seems that the shttp3.exe in the LG Flash Package triggers Symantec's trojan detection. Some searching seems to indicate (assuming I'm reading all the cryptic virus sites correctly) that there is something to this, although it seems that different scanners find different trojans/viruses (can't post the link, but Google for "shttp3.exe" and "trojan"). I also found that the web site for this utility is blocked at work, because it's a "malicious site."
Has anyone seen this? Has anyone been able to verify/refute this?
Rick
There is no virus, Lestat would never do that
Sent from my LG-P925 using XDA
Just my .02 .....Get rid of Symantec !! They are known for scaring people into a virus frenzy.. Yes, it is possible that it is seeing it as a potential virus because shttp is a workaround from the usual porting of windows ip services. ...
Correct me if i'm wrong somebody please !!
Get yourself Comodo and save your money...
Regards,
Dwayne
PS: somebody on here has written a script that just uses shttp temporarily while
your doing the flash procedure, and then reverts your host files back automatically after your done. You should try it.
dwaynedman said:
Just my .02 .....Get rid of Symantec !!
Click to expand...
Click to collapse
Symantec isn't really a choice on work PC.
Get yourself Comodo and save your money...
Click to expand...
Click to collapse
I'm sorry I can't give the link yet, but if you'll Google you'll see Comodo classifies shttp3.exe as "ApplicUnwnt.Win32.ServerWeb.SmallHTTP.~A" or "UnclassifiedMalware" (I guess depending on the version). A number of scanners find issues with shttp3.exe. I'm not saying it is infected, only that it is doing something suspicious.
Rick
Rick Tillery said:
Sorry, but as a noob, I can't post in that other thread.
It seems that the shttp3.exe in the LG Flash Package triggers Symantec's trojan detection. Some searching seems to indicate (assuming I'm reading all the cryptic virus sites correctly) that there is something to this, although it seems that different scanners find different trojans/viruses (can't post the link, but Google for "shttp3.exe" and "trojan"). I also found that the web site for this utility is blocked at work, because it's a "malicious site."
Has anyone seen this? Has anyone been able to verify/refute this?
Rick
Click to expand...
Click to collapse
shttp3.exe is in no way a virus. I've scanned with AVG and MalwareBytes Anti-Malware and they check out good.
Back to square one
OK, I seem to be stuck.
With paranoia in tow, I decided to take the long way back to stock. Unfortunately, when I tried to restore the backup of my stock image I made to SD card after installing CMR, the md5 checksum failed. I'm not sure what I can do about this.
So ok, I tried following the above link. The first step is to ensure the su binary is up-to-date. But when I tried this, I get a failure downloading the manifest. This is true for WiFi and HSPA+. I Googled and found a suggestion to delete the su binary. But that didn't help (I'm not sure how it would have helped anyway).
So back to the original question. Can I use the LG upgrade process to upgrade without going backwards (as you can see above, I can't) without bricking the phone? Can I start at step 3 in the link above and succeed?
Rick
The Dark Lestat said:
shttp3.exe is in no way a virus. I've scanned with AVG and MalwareBytes Anti-Malware and they check out good.
Click to expand...
Click to collapse
Thank you, sir. I hope it didn't seem accusing.
Rick
Rick Tillery said:
Thank you, sir. I hope it didn't seem accusing.
Rick
Click to expand...
Click to collapse
It's cool, my friend.
Sent from my Samsung Galaxy S II w/ CM9
Rick Tillery said:
OK, I seem to be stuck.
With paranoia in tow, I decided to take the long way back to stock. Unfortunately, when I tried to restore the backup of my stock image I made to SD card after installing CMR, the md5 checksum failed. I'm not sure what I can do about this.
So ok, I tried following the above link. The first step is to ensure the su binary is up-to-date. But when I tried this, I get a failure downloading the manifest. This is true for WiFi and HSPA+. I Googled and found a suggestion to delete the su binary. But that didn't help (I'm not sure how it would have helped anyway).
So back to the original question. Can I use the LG upgrade process to upgrade without going backwards (as you can see above, I can't) without bricking the phone? Can I start at step 3 in the link above and succeed?
Rick
Click to expand...
Click to collapse
Is it safe to ignore the su version update?
Short of this, can I override the MD5 checksum? I realize that image could be corrupt, but if I'm just going to replace it with the GB release, does that matter?
Rick
You should just put your phone in recovery mode and update through the tool
with your IMEI #. It will give you the latest update !
If you need some help on that I think Lestat or somebody has a write-up
on doing this.
Good luck,
Dwayne
dwaynedman said:
You should just put your phone in recovery mode and update through the tool
with your IMEI #. It will give you the latest update !
If you need some help on that I think Lestat or somebody has a write-up
on doing this.
Good luck,
Dwayne
Click to expand...
Click to collapse
Can you be a bit more specific?
1. By "recovery mode," do you mean into ClockworkMod Recovery, or I should revert to stock (I made a copy of it after I rooted the stock ROM, but before I installed CMR)?
2. By "the tool," do you mean the official LGMobile Software Update, or the LG Flash Package referenced in the link above?
3. By "latest update," do you mean the file directly from LG, or the copy (v20p) linked from the link above?
4. If the latter in both previous questions, which set of steps do I need to follow from the above link? Can I do only 3 (LG Flash Tool), or do I need to follow 1 (Recovery Manager), 2 (Returning to Stock), and 3?
My friend had a different LG phone, with ClockworkMod Recover and CM7 installed. He reverted the CM7 to stock, but did not replace CMR with the stock recovery. Then he used the official LG upgrade method and bricked his phone. I'm trying to avoid this.
Are you saying I don't have to worry about this on the LG Thrill 4G? Can I go straight from the current CMR+CM7 configuration to the LG GB release using the official LG process?
If you mean I should use a different process, can you point me to it? As I mentioned, I run into dead-ends using the method linked above. And I'm not even sure whether I should be doing steps 1, 2 and 3, or if I should just use step 3.
Any and all help is appreciated, but I guess I don't understand the shorthand you're using here, so if you could be a bit more specific, I wouldn't feel so lost.
Rick
Rick Tillery said:
Can you be a bit more specific?
1. By "recovery mode," do you mean into ClockworkMod Recovery, or I should revert to stock (I made a copy of it after I rooted the stock ROM, but before I installed CMR)?
2. By "the tool," do you mean the official LGMobile Software Update, or the LG Flash Package referenced in the link above?
3. By "latest update," do you mean the file directly from LG, or the copy (v20p) linked from the link above?
4. If the latter in both previous questions, which set of steps do I need to follow from the above link? Can I do only 3 (LG Flash Tool), or do I need to follow 1 (Recovery Manager), 2 (Returning to Stock), and 3?
My friend had a different LG phone, with ClockworkMod Recover and CM7 installed. He reverted the CM7 to stock, but did not replace CMR with the stock recovery. Then he used the official LG upgrade method and bricked his phone. I'm trying to avoid this.
Are you saying I don't have to worry about this on the LG Thrill 4G? Can I go straight from the current CMR+CM7 configuration to the LG GB release using the official LG process?
If you mean I should use a different process, can you point me to it? As I mentioned, I run into dead-ends using the method linked above. And I'm not even sure whether I should be doing steps 1, 2 and 3, or if I should just use step 3.
Any and all help is appreciated, but I guess I don't understand the shorthand you're using here, so if you could be a bit more specific, I wouldn't feel so lost.
Rick
Click to expand...
Click to collapse
Remove your battery and keep the phone unplugged
Launch the mobile updater tool
Hold the volume+ button plug the phone in and keep holding the volume+ till the computer downloads the drivers your phone is now in download mode
Once the phone is picked up go to customer support on the LG updater tool and click on recovery phone put your imie number in click check (make sure its the right model) an let the updater tool do its job. Once its done flashing launch into recovery volume- plus power plus 3D button do a complete wipe and factory reset and reboot your phone ... you'll lose cwm and root and be back to full stock
Sent from my LG-P925 using XDA
Bricked?
No joy. Following the steps, the upgrade stopped at 6%. Trying a number of times, it eventually forced me to exit the program (no more restarts). Rerunning the updater (and downloading the 420 MB image yet again on a VERY slow connection) I tried again and again, with different combinations of battery and plug order with power and volume buttons, but nothing worked. Checking elsewhere I found some issues had been reported with Windows Vista/7, so I tried on an XP machine. Now the "Start Updating" bar is red (it was always gray with W7). But now when I try to restore (or even update for that matter), it asks for my S/N (it never did that before) and then says it is "no longer able to upgrade." Reading around, it seems this is an indication of the device being bricked.
Rick
It sounds like you are very close to getting it working Rick.
My update did the same thing, looped over and over until it
finally kicked me out. Just plugging and unplugging the phone etc....
And when my update stuck at 6% the last time, i took my battery out and then in real quick and that seemed to work.
Does the phone still vibrate when you plug the usb cable into it while holding volume..? If it does then I highly doubt that your phone is bricked, just in a semi flashed state....No worries
Should Rick be trying to run LG Updater as administrator ? I didn't, but it might not hurt.
Regards & Luck,
Dwayne
http://forum.xda-developers.com/showthread.php?p=22417769
Have you tried this yet cause if you can get the LG logo to come up then you can reflash the phone and get it working send a pm to the dark lestat he may be able to team viewer you and help you out
Sent from my ****ty supported LG Thrill
dwaynedman said:
It sounds like you are very close to getting it working Rick.
Click to expand...
Click to collapse
I wouldn't have believed you early this morning, but now maybe...
My update did the same thing, looped over and over until it
finally kicked me out. Just plugging and unplugging the phone etc....
And when my update stuck at 6% the last time, i took my battery out and then in real quick and that seemed to work.
Click to expand...
Click to collapse
I tried a bunch of different combinations...none seemed to make the app happy. I finally punted Windows 7 and moved to an XP machine, only to get the "no longer able to update" message. At that point I assumed I was screwed (effectively bricked).
Does the phone still vibrate when you plug the usb cable into it while holding volume..? If it does then I highly doubt that your phone is bricked, just in a semi flashed state....No worries
Click to expand...
Click to collapse
It never really vibrated, but I was able to get back into CMR. Unfortunately NONE of my backups work at all. They all have MD5 checksum failures. I tried a trick I found online and got past that step, only to have it say a failure restoring /system. So much for CMR.
JReeher said:
http://forum.xda-developers.com/showthread.php?p=22417769
Have you tried this yet cause if you can get the LG logo to come up then you can reflash the phone and get it working send a pm to the dark lestat he may be able to team viewer you and help you out
Click to expand...
Click to collapse
Which step? As I mentioned above, I can't even get the first step of the first section (updating the su binary). And if I start at the 3rd section, Symantec prohibits me from using shttp3.exe (I tried to unquarantine it, but it gives a permission error, even as Administrator, when I try to run it), so I'll have to use a different machine.
I was able to reinstall the CM7 3/15 release, so that's something. I was going to restore the stock recovery backup I made, but even that doesn't seem to work. I'm having issue with backups :-(
Rick
i have never been able to restore a backup. i dont know why... but i have tried several times in several different instances.
---------- Post added at 11:56 AM ---------- Previous post was at 11:50 AM ----------
rick tillery, if you want to get your phone back to alive and well i'd suggest doing this:
http://forum.xda-developers.com/showthread.php?t=1558723&page=3
4th post i think
ROMS tested by me:
***************************************
These are the following KitKat based roms that worked really well with this approach:
1. CM 11 Nightly
2. PAC-MAN
3. Slimkat Weekly
I tried with both AT&T and T-Mobile variants, and didn't have to load Sprint specific kernel, the stock kernel came with those worked just fine. But if you get bootloops, go ahead and flash KToonz Sprint AOSP kernel.
IMPORTANT: The listed roms above have ability to detect device type and it will set appropriate settings meaning your default network mode with be CDMA, which you don't want to do that since u r running on unlocked GSM to begin with. So I learned that you can force GSM mode upon starting up by putting these two lines into build.prop:
telephony.lteOnGsmDevice=1
ro.telephony.default_network=9
*******************************************
So thanks to OP on this thread http://forum.xda-developers.com/showthread.php?t=2530610 for the instructions on how to get the SIM unlocking work.
I personally wanted to run pure AOSP on my GS4, but the problem is when I go AOSP, switching over to GSM works but I can't receive any phone calls. If I run stock, I can configure it to turn off roaming guard and whatnot, this is not the case for AOSP.
Therefore, here's how I get around it. WARNING: a little lengthy but it worked.
0. Backup your current Sprint AOSP now you'll need it later.
1. Download TMOBILE AOSP rom of your choice. I chose Gummy 4.4
2. Download Sprint AOSP of your choice (I'm on sprint). I chose Gummy 4.4
3. Once download completed, open the TMO zip and delete the boot.img because it contains the kernel for TMO which we don't want. Keep this window open.
I recommend NOT extracting it because you will have to reassemble later, just use a zip software that allows you to edit in place.
4. Open the Sprint AOSP, copy the boot.img over to TMO. Basically, we are replacing JUST the kernel for Sprint into TMO to make the phone boots.
5. Now we need to get rid of the assertion check for device type in the updater-script.
6. WIth TMO zip window still open, edit the file /META-INF/com/google/android/updater-script, and replace anything that said jfltetmo with jfltespr. UPDATE 3: If you see no "assert" lines described below in your updater-script, simply ignore this step.
From:
Code:
assert(getprop("ro.product.device") == "jfltetmo" || getprop("ro.build.product") == "jfltetmo" || abort("This package is for \"jfltetmo\" devices; this is a \"" + getprop("ro.product.device") + "\"."););
To:
Code:
assert(getprop("ro.product.device") == "jfltespr" || getprop("ro.build.product") == "jfltespr" || abort("This package is for \"jfltespr\" devices; this is a \"" + getprop("ro.product.device") + "\"."););
7. Save the changes, and upload the TMO to phone and flash. Now you are running completely under TMO settings and calls can be received.
8. Setup everything you need and NANDROID backup.
9. So with this approach, I tested switching back to CDMA, and the EXACT problem happens (can't receive calls). So move on to next step.
10.To switch back and forth, you just need to boot into recovery and wipe system and replace it with the targeted system you want to be on. For instance, if I am on TMO and want to switch to SPR, I reboot into recovery, wipe current TMO /system and restore SPR /system and reboot. This whole process should take about 3 minutes.
If anyone has any better approach, please share.
UPDATE: This approach also will solve my problem of using AOSP dialer. If I run Sprint ROM (CDMA), and switch over to GSM via Mobile Network (in Settings), then upon placing a call and hanging up will NOT hang up. The dialer on Sprint ROM will say the call has ended by it never did if you put it on speaker phone. So with this system switching, it also solves this problem.
UPDATE 2:
If you are in Asia using GS4, flashing Sprint S4 stock kernel will fix issues reported below:
Gummi (Won't mount my external SD card)
Omni (Won't mount my external SD card)
Cyanogenmod (Crashes, can't install apps, bunch of other problems)
AOKP (No wifi, crashes, etc.)
Go to Page 3 to find more info. >> http://forum.xda-developers.com/showpost.php?p=49724403&postcount=21
Ahh been looking everywhere for this so that's all it just change over the boot.img
Going to give it a try when I get home and in front of my lappy how's that gummy? 4.4
Sent from my SPH-L720 using xda app-developers app
---------- Post added at 02:08 AM ---------- Previous post was at 02:06 AM ----------
Okay see I unlocked my spr gs4 and am running T-Mobile.. Gsm soo I'm going to give this a go anyway
Sent from my SPH-L720 using xda app-developers app
wow this work like a charm. thank you very much
vboyz103 said:
So thanks to OP on this thread http://forum.xda-developers.com/showthread.php?t=2530610 for the instructions on how to get the SIM unlocking work.
I personally wanted to run pure AOSP on my GS4, but the problem is when I go AOSP, switching over to GSM works but I can't receive any phone calls. If I run stock, I can configure it to turn off roaming guard and whatnot, this is not the case for AOSP.
Therefore, here's how I get around it. WARNING: a little lengthy but it worked.
0. Backup your current Sprint AOSP now you'll need it later.
1. Download TMOBILE AOSP rom of your choice. I chose Gummy 4.4
2. Download Sprint AOSP of your choice (I'm on sprint). I chose Gummy 4.4
3. Once download completed, open the TMO zip and delete the boot.img because it contains the kernel for TMO which we don't want. Keep this window open.
I recommend NOT extracting it because you will have to reassemble later, just use a zip software that allows you to edit in place.
4. Open the Sprint AOSP, copy the boot.img over to TMO. Basically, we are replacing JUST the kernel for Sprint into TMO to make the phone boots.
5. Now we need to get rid of the assertion check for device type in the updater-script.
6. WIth TMO zip window still open, edit the file /META-INF/com/google/android/updater-script, and replace anything that said jfltetmo with jfltespr.
Code:
assert(getprop("ro.product.device") == "jfltespr" || getprop("ro.build.product") == "jfltespr" || abort("This package is for \"jfltespr\" devices; this is a \"" + getprop("ro.product.device") + "\"."););
7. Save the changes, and upload the TMO to phone and flash. Now you are running completely under TMO settings and calls can be received.
8. Setup everything you need and NANDROID backup.
9. So with this approach, I tested switching back to CDMA, and the EXACT problem happens (can't receive calls). So move on to next step.
10.To switch back and forth, you just need to boot into recovery and wipe system and replace it with the targeted system you want to be on. For instance, if I am on TMO and want to switch to SPR, I reboot into recovery, wipe current TMO /system and restore SPR /system and reboot. This whole process should take about 3 minutes.
If anyone has any better approach, please share.
Click to expand...
Click to collapse
where are the links to the t-mobile and sprint roms you used?
i am rooted with a custom recovery installed
do we need to be on any specific firmware to start the process?
i been going exactly through the same pain you have been
i been having to manually edit phone settings with *#0011# each time and it still isnt perfect
i mean it works ok but not like i want really.
your method is prob the most stable but is really just a work around for the real problem.
why dont our phones just read the sim cards correctly like a regular unlocked phone?
>>>>what happens if the firmware auto updates after it is installed?<<<<
en11gma said:
where are the links to the t-mobile and sprint roms you used?
i am rooted with a custom recovery installed
do we need to be on any specific firmware to start the process?
i been going exactly through the same pain you have been
i been having to manually edit phone settings with *#0011# each time and it still isnt perfect
i mean it works ok but not like i want really.
your method is prob the most stable but is really just a work around for the real problem.
why dont our phones just read the sim cards correctly like a regular unlocked phone?
>>>>what happens if the firmware auto updates after it is installed?<<<<
Click to expand...
Click to collapse
You can choose any ROM of your choice here over at TMOBILE forum http://forum.xda-developers.com/galaxy-s4-tmobile.
This is that kind of hoops we have to jump through because what we are doing is considered NON-STANDARD and therefore, UNSUPPORTED by carrier. That is the main reason why the carrier locked down the SIM card at first.
So for a little trouble of flashing back and forth, I think I can hang and to have an unlocked SIM like this save us $$. I'm thinking of ditching Sprint and go no-contract from here on on. This is the future of cell phones as it should be many places already done this.
vboyz103 said:
You can choose any ROM of your choice here over at TMOBILE forum http://forum.xda-developers.com/galaxy-s4-tmobile.
This is that kind of hoops we have to jump through because what we are doing is considered NON-STANDARD and therefore, UNSUPPORTED by carrier. That is the main reason why the carrier locked down the SIM card at first.
So for a little trouble of flashing back and forth, I think I can hang and to have an unlocked SIM like this save us $$. I'm thinking of ditching Sprint and go no-contract from here on on. This is the future of cell phones as it should be many places already done this.
Click to expand...
Click to collapse
you are acting like this phone the "cdma galaxy s4" is unique for wanting it to be an unlocked gsm phone.
not no more.
this is the standard
should be a distro for each phone just for this or an apk just for this
this is gonna be pretty regular to have all these radios built-in to a single chip or just a couple chips on the c/b in the phone.
hopefully some crews are working on this
i think they are in the roms that have HiAPN and MNE or MNC (i forget what it stands for) but basically it can read the iccid on the sim and read the apn and dload the prl automatically
some....alot of the roms dont have this but some do.
vboyz103 said:
So thanks to OP on this thread http://forum.xda-developers.com/showthread.php?t=2530610 for the instructions on how to get the SIM unlocking work.
I personally wanted to run pure AOSP on my GS4, but the problem is when I go AOSP, switching over to GSM works but I can't receive any phone calls. If I run stock, I can configure it to turn off roaming guard and whatnot, this is not the case for AOSP.
Therefore, here's how I get around it. WARNING: a little lengthy but it worked.
0. Backup your current Sprint AOSP now you'll need it later.
1. Download TMOBILE AOSP rom of your choice. I chose Gummy 4.4
2. Download Sprint AOSP of your choice (I'm on sprint). I chose Gummy 4.4
3. Once download completed, open the TMO zip and delete the boot.img because it contains the kernel for TMO which we don't want. Keep this window open.
I recommend NOT extracting it because you will have to reassemble later, just use a zip software that allows you to edit in place.
4. Open the Sprint AOSP, copy the boot.img over to TMO. Basically, we are replacing JUST the kernel for Sprint into TMO to make the phone boots.
5. Now we need to get rid of the assertion check for device type in the updater-script.
6. WIth TMO zip window still open, edit the file /META-INF/com/google/android/updater-script, and replace anything that said jfltetmo with jfltespr.
Code:
assert(getprop("ro.product.device") == "jfltespr" || getprop("ro.build.product") == "jfltespr" || abort("This package is for \"jfltespr\" devices; this is a \"" + getprop("ro.product.device") + "\"."););
7. Save the changes, and upload the TMO to phone and flash. Now you are running completely under TMO settings and calls can be received.
8. Setup everything you need and NANDROID backup.
9. So with this approach, I tested switching back to CDMA, and the EXACT problem happens (can't receive calls). So move on to next step.
10.To switch back and forth, you just need to boot into recovery and wipe system and replace it with the targeted system you want to be on. For instance, if I am on TMO and want to switch to SPR, I reboot into recovery, wipe current TMO /system and restore SPR /system and reboot. This whole process should take about 3 minutes.
If anyone has any better approach, please share.
Click to expand...
Click to collapse
vboyz103
you know what
this is probably one of the most important pieces of info i have come across on the boards
yes i look the root, recovery and rom sections but this is a coool tip
i have been doing this for a few years and have never tried doing this before
can i basically try any rom i want (for tbe GS4) as long as i use the kernel made for my specific phone?
are there any dos and donts we should be aware of?
so far i have only done it with CM11nightlies for jfltespr and jfltetmo and also same for gummy as you suggested
but those are basically identical roms....can we do this with any rom for the gs4?
1 more thing. it neworing defailts to LTE and if you go look at the APN's and there are the username "none" and password has a " * " and another setting has a " * * "
all the APN's are like this for that network
do we need to fix them or is that somehow correct?
i am super confused as to whats happening here.
you say do the *#0011# and hit numbers. heres the thing. i dont get any options. just a service menu with a bunch of stuff on it. nothing about debug screen or anything. ive unlocked many s3's and know what im looking for but its not there. on MJA or MK2. people are saying yea just flash the TMO CM and go, others are saying the sim unlock program works on MJA, others saying not to do it on that version because it doesnt work, others saying it only works on MF9...WTF CAN WE PLEASE GET A VIDEO TUT OR SOMETHING. ive been pulling my hair out for days with this thing. ive followed loads of instructions but none of it works. please give precise step by step what version you should be on, root or not, bootloader version, everything thanks
dragonhart6505 said:
i am super confused as to whats happening here.
you say do the *#0011# and hit numbers. heres the thing. i dont get any options. just a service menu with a bunch of stuff on it. nothing about debug screen or anything. ive unlocked many s3's and know what im looking for but its not there. on MJA or MK2. people are saying yea just flash the TMO CM and go, others are saying the sim unlock program works on MJA, others saying not to do it on that version because it doesnt work, others saying it only works on MF9...WTF CAN WE PLEASE GET A VIDEO TUT OR SOMETHING. ive been pulling my hair out for days with this thing. ive followed loads of instructions but none of it works. please give precise step by step what version you should be on, root or not, bootloader version, everything thanks
Click to expand...
Click to collapse
how about you just read the freaking first post
you can clearly tell you havent read crap
POST #1
tells you about the exact problem you are having trying to see the correct info in *#0011#
everyone who reads what you wrote about *#0011# is gonna laugh at you for demanding info and tuts when you havent even read the 1st freaking post!!!!
not in this thread but DOMESTIC UNLOCK
its always at the top in the threads in the forums....it might even be a sticky
en11gma said:
how about you just read the freaking first post
you can clearly tell you havent read crap
POST #1
tells you about the exact problem you are having trying to see the correct info in *#0011#
everyone who reads what you wrote about *#0011# is gonna laugh at you for demanding info and tuts when you havent even read the 1st freaking post!!!!
not in this thread but DOMESTIC UNLOCK
its always at the top in the threads in the forums....it might even be a sticky
Click to expand...
Click to collapse
Edit: NVM, got it working, cept i kept it on stock. thanks for the tut, its better when its clearer.
dragonhart6505 said:
Edit: NVM, got it working, cept i kept it on stock. thanks for the tut, its better when its clearer.
Click to expand...
Click to collapse
i started out thinking the thread i was in was that domestic sim unlock
there are 3 threads you really want
1st
sim unlock international (that has the unlock.exe)
2nd
domestic sim unlock (that one tells you what to do with *#0011#
3rd
this one
i have those 3 tabs open quite a bit
on a side note
when we install those tmobile romz they are doing something (correct) to the *#0011# area and maybe something else
we should just be able to flip flop with some simple script
shouldnt have to restore romz
but hey at least we got something
Yknow, i think thats the very first useful thought towards dual booting ive seen yet.
dragonhart6505 said:
Yknow, i think thats the very first useful thought towards dual booting ive seen yet.
Click to expand...
Click to collapse
lol
yep it is dual booting
do it on my linux / windows pc all the time
but the thing is...these settings are in *#9090# and a little simple script should be able to do this on the fly
en11gma said:
lol
yep it is dual booting
do it on my linux / windows pc all the time
but the thing is...these settings are in *#9090# and a little simple script should be able to do this on the fly
Click to expand...
Click to collapse
Oh trust me I do as well. Can't go without my Linux lovin' ^_^ as this was a pain in the arse but now super easy, I can't wait to do it again.
<3 bein a nerd lmao
Also, OP, since I havent found one yet (and making tuts is kinda my thing) mind if I make one? With all credits where due of course
dragonhart6505 said:
Oh trust me I do as well. Can't go without my Linux lovin' ^_^ as this was a pain in the arse but now super easy, I can't wait to do it again.
<3 bein a nerd lmao
Also, OP, since I havent found one yet (and making tuts is kinda my thing) mind if I make one? With all credits where due of course
Click to expand...
Click to collapse
Have at it man..I'm not so good it making tuts.
Nice. Ty. Will link when its done of course
would it be the same steps if i wanted to a use a touchwiz rom?
nemofbaby2010 said:
would it be the same steps if i wanted to a use a touchwiz rom?
Click to expand...
Click to collapse
From my previous testing, TW rom dialer is better in handling GSM technologies. Therefore, you don't need to do these steps. The link to the original Unlock thread will give you more information in terms of what to do with TW.
vboyz103 said:
From my previous testing, TW rom dialer is better in handling GSM technologies. Therefore, you don't need to do these steps. The link to the original Unlock thread will give you more information in terms of what to do with TW.
Click to expand...
Click to collapse
Also while using slim ROM I got a persistent notification about call fowarding
Sent from my SGH-M919 using Tapatalk
ROMs
Hi everyone,
I live in Asia, and this post was a lifesaver for me because I was pulling my hair out over why I wasn't receiving calls.
In terms of ROMs, however, I've had some issues that I wanted to ask about (I've followed the instructions above to the dot).
Here are ROMs that work (for the most part):
Cyanfox (some freezing, halo issues)
Here are ROMs that have issues:
Gummi (Won't mount my external SD card)
Omni (Won't mount my external SD card)
Cyanogenmod (Crashes, can't install apps, bunch of other problems)
AOKP (No wifi, crashes, etc.)
I currently have MJA baseband. Any thoughts? Thanks!