[MOD] Enable Native Tethering - Verizon Motorola Droid Turbo Android Development

Update: the patch for the latest OTA can be found here: http://forum.xda-developers.com/droid-turbo/general/enable-su4tl-49-stock-tethering-to-t3380911
Even though it's been reported that the old version works with the SU4TL-49 OTA, I recommend flashing the updated patch with the OTA, since the patch flashes a modified build.prop file, and the new patch will include any changes made to the build.prop by the OTA update.
This is exactly what the thread title says. The zip replaces the stock build.prop file with one modified to enable native tethering. This is not guaranteed to work with any other build than SU4TL-44. I have personally tested this on my own phone. If you use this on any other build, you do so at your own peril.
Flash in TWRP.
And a quick apology, I had thought I was in the General section when I started the new thread. If any moderators want to move this to the General section, by all means, please do.

pastorbennett said:
This is exactly what the thread title says. The zip replaces the stock build.prop file with one modified to enable native tethering. This is not guaranteed to work with any other build than SU4TL-44. I have personally tested this on my own phone. If you use this on any other build, you do so at your own peril.
Flash in TWRP.
And a quick apology, I had thought I was in the General section when I started the new thread. If any moderators want to move this to the General section, by all means, please do.
Click to expand...
Click to collapse
Flashed this to my Turbo yesterday; works like a charm. Thanks!

Guys, I'm sure this is dumbest question ever asked on XDA, but would somebody give me a hand on how to flash this via TWRP? I put the extracted files on my phone but couldn't find them to install from within TWRP, probably because they're not an .apk - do I need to somehow make these part of a ROM and flash the whole thing?
Just did sunshine/update/TWRP/root and everything is working great, if that makes any difference.
Thanks a lot!

thetastycat said:
Guys, I'm sure this is dumbest question ever asked on XDA, but would somebody give me a hand on how to flash this via TWRP? I put the extracted files on my phone but couldn't find them to install from within TWRP, probably because they're not an .apk - do I need to somehow make these part of a ROM and flash the whole thing?
Just did sunshine/update/TWRP/root and everything is working great, if that makes any difference.
Thanks a lot!
Click to expand...
Click to collapse
With TWRP you do not flash the extracted files. You flash the zip. It has to be a "flashable" zip, but this one is.
Over in the bootloader unlock warning image thread, some people were trying to flash a zipped file that was not meant to be flashed. The image was meant to be unzipped/extracted and then flashed with ADB.
But in this case this is a TWRP flashable zip.

Worked perfectly! Thank you both so much - this is a lifesaver!!

pastorbennett said:
This is exactly what the thread title says. The zip replaces the stock build.prop file with one modified to enable native tethering. This is not guaranteed to work with any other build than SU4TL-44. I have personally tested this on my own phone. If you use this on any other build, you do so at your own peril.
Flash in TWRP.
And a quick apology, I had thought I was in the General section when I started the new thread. If any moderators want to move this to the General section, by all means, please do.
Click to expand...
Click to collapse
Worked as advertised. I still have unlimited data and racked up an impressive 180GB of data. What a life saver!

Anyone tried this with the latest OTA yet?

Jazzy Josh said:
Anyone tried this with the latest OTA yet?
Click to expand...
Click to collapse
It works just fine.

Jazzy Josh said:
Anyone tried this with the latest OTA yet?
Click to expand...
Click to collapse
KOAO said:
It works just fine.
Click to expand...
Click to collapse
It works with the latest OTA? That's good to know. I hadn't tried, since the patch basically overwrites the stock build.prop, and there's always going to be a few changes in the file whenever a new update is installed.
I did put together a patch for the latest OTA, which I would recommend flashing if you used the SU4TL-44 version, as the build.prop file reports the software version to the OS.
The thread for that patch is here:
http://forum.xda-developers.com/droid-turbo/general/enable-su4tl-49-stock-tethering-to-t3380911
Sent from my XT1254 using XDA-Developers mobile app

Related

Super User 2.3 Availble !!!!!

I see talk the the Super User Root has been upgraded to 2.3. It's suppose to be much better than the current one. Will we have to uninstall the current one before applying the new root? Has anyone made an attempt to install SU 2.3 in a Captivate yet?
Qmotion said:
I see talk the the Super User Root has been upgraded to 2.3. It's suppose to be much better than the current one. Will we have to uninstall the current one before applying the new root? Has anyone made an attempt to install SU 2.3 in a Captivate yet?
Click to expand...
Click to collapse
my update.zip is getting it added soon.
edit---
uploading now
edit---
up now
http://forum.xda-developers.com/showthread.php?t=751934
I rooted my phone using the pimp my cap. PDF. If I wanted to unroot. Could I just delete the original update.zip file and replace it with out flashing back to stock? The reason I'm asking is I don't have a pc. (im on mac) and I can't use odin.
Sent from my SAMSUNG-SGH-I897 using XDA App
What will we have to do to replace the old version? Can one be installed on top of the other?
?
Qmotion said:
What will we have to do to replace the old version? Can one be installed on top of the other?
?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=682828
there is an update.zip that will do what you need.
So what your saying is you just install the new update.zip as we did during the first install?. As stated that means we don't have to uninstall or go back to the stock rom. It pays for us noobs to be certain.
Qmotion said:
So what your saying is you just install the new update.zip as we did during the first install?. As stated that means we don't have to uninstall or go back to the stock rom. It pays for us noobs to be certain.
Click to expand...
Click to collapse
yup, flash over
DONT UPDATE TO THIS. I did, and now I get force close after force close, I can't load a backup ROM at all. Going to unroot and root again hoping to get back to the previous version.
designgears said:
yup, flash over
Click to expand...
Click to collapse
Ok so just install over my current root? Or flash to stock then root?
Sent from my SAMSUNG-SGH-I897 using XDA App
Smallsmx3 said:
Ok so just install over my current root? Or flash to stock then root?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
install over your current root
flashman2002 said:
DONT UPDATE TO THIS. I did, and now I get force close after force close, I can't load a backup ROM at all. Going to unroot and root again hoping to get back to the previous version.
Click to expand...
Click to collapse
designgears said:
install over your current root
Click to expand...
Click to collapse
OK, now I'm confused. I almost did it. I'm scared now....
Designgears, you have done this to your phone and it works now. Flashman did you figure out what you did wrong?
The only thing I can figure is I updated through ROM manager. I imagine people that are using the update.zip should have no issues from what I read in the Superuser thread. I am not going to try again for a couple days to be sure, but people are able to make it work without issue. I figured with it showing up in ROM manager it would have been safe to load that way, as I upgraded to 2.2.2 when I first got ROM Manager.
Qmotion said:
OK, now I'm confused. I almost did it. I'm scared now....
Designgears, you have done this to your phone and it works now. Flashman did you figure out what you did wrong?
Click to expand...
Click to collapse
Just did mine, works fine.
Is this just the updated Su 2.3.1 ??
I see that you also have the http://www.multiupload.com/BCLH94FNVD file on the other thread that seems to include the new root file. Or does this update.zip file include everything?
Excuse me for being extra carefull. Better safe than sorry.
I actually want to install the file that includes the sideloading. I haven't made that mod to my phone yet.
Does the BCLH94FNVD file include everything all in one shot?
designgears said:
my update.zip is getting it added soon.
edit---
uploading now
edit---
up now
http://forum.xda-developers.com/showthread.php?t=751934
Click to expand...
Click to collapse
If I may.. Was there a changelog? I mean.. 2.2 grants needed privilege. Not trying to be sarcastic at all but I see so many people worried about this or that it left me wondering what was new.
I tried it and it said the update was aborted. Didn't give a reason. I took out the original update file and replaced it with the new one. Should I have left both files in?
Maybe I'm not asking the question right. The link to the update file you added to this thread. Is it for the EliteSuperRooter or is it just for the 2.3.1 root OR would we still have to add the file on the other thread that seems to include the new root file. Or does this update.zip file include everything?
mostyle said:
If I may.. Was there a changelog? I mean.. 2.2 grants needed privilege. Not trying to be sarcastic at all but I see so many people worried about this or that it left me wondering what was new.
Click to expand...
Click to collapse
In the General Android Dev forum there is a changelog and he changed a ton of stuff.
edit - It was in Apps and Games my bad.
http://forum.xda-developers.com/showthread.php?t=682828
for lazy ppl this is what different between 2.2 and 2.3.1
(New for 2.3)
- New layout of main app
- Full logging
- New request layout
- Fixed boot/widget bug
- Date/time format options
- Better notification system
- New icon
- Better allow system
- A whole mess of code cleanup
- Rearranged drawables so that only one apk needs to be built for any firmware
(New for 2.3.1)
- Big bugfixes
- Better support for landscape mode
- better support for ldpi devices
The question is, what does this offer that my current superuser doesn't?

[HOW TO] Flash Froyo without loosing downgradability and keeping cam flash

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)

[ROOT] PROPER Remake of Full Rooted Stock Image (aka Root66) + Easy CWM Install

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

[SYSTEM] De-Odex Framework / System [No-Wipe]

Currently designed for the Wifi version only. Alternates available upon request.
This package includes the de-odexed system and framework folder based on a wifi model.
This is NOT a full install, so do NOT wipe before using.
This package is designed to be used with the custom recovery image. This will NOT work with Odin.
This will delete the current system and framework folders and flash the new ones in their place. This is only a temporary solution until a full rooted install is established.
De-Odexed Install Pack
Custom Recovery Image
Custom Kernel Packages
twistedumbrella said:
Currently designed for the Wifi version only. Alternates available upon request.[/url]
Click to expand...
Click to collapse
Request!
My Verizon GC120 should be here in a couple of days. As far as I know it is untouched stock. Let me know the commands to pull the files you need for this and the other dev work you are doing.
Thank you for taking the time to do the work! We all appreciate it!
Finally received a GC120 camera I can do something with. Attached are the .img files pulled. About says my phone is on 4.1.2 (LK3) but I keep getting an install update request although the folder titled as the update in /cache is empty (so there's nothing I can pull from that).
I also pulled the modem.bin but it says invalid file when I try to upload.
*These are the files for LK3
Camera updated to LL2. Updated files attached.
MC4 files attached
So maybe I screwed myself updating all the way to MK4 update. Can't root using framaroot now like I did with all the others. Gonna try a few other options.
Can someone please tell me the adb command to find whether a bootloader is locked or not? I have tried several I've found online and don't receive anything conclusive. Thanks.
Be back in a week or so. Final project is in the beta test stage so I am swamped until it reaches the release candidate.
twistedumbrella said:
Be back in a week or so. Final project is in the beta test stage so I am swamped until it reaches the release candidate.
Click to expand...
Click to collapse
can you upload samsung galaxy camera apk
Can anyone post efs.img? I've screwed up my Cam and i need to flash efs.img to mmcblk03. Was playing around with swap and screwed up!
BUMP!!!!
rudie_techie said:
BUMP!!!!
Click to expand...
Click to collapse
? It wasn't part of the system image and you didn't specify which model but even so, I doubt people are randomly checking this thread for who needs backups of radio partitions.
Its a EK-GC100 bootloader mode says EK-GC100_EUR_XX
rudie_techie said:
Its a EK-GC100 bootloader mode says EK-GC100_EUR_XX
Click to expand...
Click to collapse
I dug through everything I have but no efs.img and if I remember right, you'd need one with your IMEI. Best bet is probably a factory reset.
Didn't help... tried factory reset with stock recovery and cwm recovery... nothing helps... i don't know a way to get it fixed... will keep looking...
Finally got it fixed. As GC100 is similar to S3, downloaded efs file for S3 flashed it via odin through bootloader and voila... attaching the file for reference if anyone else gets into trouble!
rudie_techie said:
Finally got it fixed. As GC100 is similar to S3, downloaded efs file for S3 flashed it via odin through bootloader and voila... attaching the file for reference if anyone else gets into trouble!
Click to expand...
Click to collapse
It's usually easier to post it all in one thread and link to it instead of making the same posts in two threads and ending up with the same answers.
can someone please re upload or send me links in private message? I have dropbox, please I need it... my ****z bricked gotta fix it
damn can someone upload these links or the stock odin tar???
GC120_GC120VRAMH2_1366980_REV00_user_low_ship.tar.md5
?? ANYONE please.... help

Need help rolling back/unrooting my phone

I rooted my phone last week because I wanted to use substratum to theme my notifications. Since then, I've run into a bunch of frustrating problems.
Current Model: OnePlus 7 Pro 12GB version, build xXx_NoLimits_7.7 on OOS 9.5.11-GM21AB
Problems:
Phone used to be 9.5.11-GM21AA but now it's 9.5.11-GM21AB - does this affect anything?
Substratum hasn't worked in stock+root, and 2 different ROMs I've tried
Favourite app of mine doesn't work properly and I think it's because I'm on build 9.5.11 and not 9.5.10
How I messed it up: Started by rooting and trying to install Renovate ICE Rom, installed the wrong file which converted me to 9.5.5-GM21AB. Then I updated to 9.5.11 but it remained AB. I tried several times to unroot, roll back and get to 9.5.10AA but it always kept itself at 9.5.11AB. Sometimes my wifi would break. I currently have xXx NoLimits Rom installed.
Desired outcome: I want to unroot and roll back to 9.5.10-GM21AA stock
Any help is greatly appreciated. Thank you!
MSM tool should fix it.
virtyx said:
MSM tool should fix it.
Click to expand...
Click to collapse
+1
virtyx said:
MSM tool should fix it.
Click to expand...
Click to collapse
zams85 said:
+1
Click to expand...
Click to collapse
Thanks, that was super easy. MSM automatically rolled back my phone to 9.5.3.GM21AA.
I have one more question - if I want to update it to 9.5.10GM21AA, how would I do that? If I update through the system, it will take me to 9.5.11, which I do not want. If the process is easier if I'm rooted, I already did that. To top it off, my substratum is working now after I reset my phone to how it is now. All I need is to update it to 9.5.10 and I would be sooooooo happy .
Thanks in advance!
bmcmr said:
Thanks, that was super easy. MSM automatically rolled back my phone to 9.5.3.GM21AA.
I have one more question - if I want to update it to 9.5.10GM21AA, how would I do that? If I update through the system, it will take me to 9.5.11, which I do not want. If the process is easier if I'm rooted, I already did that. To top it off, my substratum is working now after I reset my phone to how it is now. All I need is to update it to 9.5.10 and I would be sooooooo happy .
Thanks in advance!
Click to expand...
Click to collapse
Just download the full zip for 9510 and update via system update
virtyx said:
Just download the full zip for 9510 and update via system update
Click to expand...
Click to collapse
Thanks for your reply! I thought as much. Can you clarify if these steps are right?
Go to https://androidfilehost.com/?w=files&flid=294300
Download the one I want (9.5.10AA)
Move the file to my phone's internal storage
Update via Local Upgrade
Is this correct? Will I still have root after I do this?
bmcmr said:
Thanks for your reply! I thought as much. Can you clarify if these steps are right?
Go to https://androidfilehost.com/?w=files&flid=294300
Download the one I want (9.5.10AA)
Move the file to my phone's internal storage
Update via Local Upgrade
Is this correct? Will I still have root after I do this?
Click to expand...
Click to collapse
Correct
You will unrooted after the upgrade as itll flash completely stock.
Just re-roof after it and your good to go!
Hey @virtyx I copied the exact zip file I downloaded into my root directory for Local Upgrade but it wasn't recognized. I then tried to just flash the zip through TWRP but it said it was an "Invalid zip file format".
Do you know what I'm doing wrong?
bmcmr said:
Hey @virtyx I copied the exact zip file I downloaded into my root directory for Local Upgrade but it wasn't recognized. I then tried to just flash the zip through TWRP but it said it was an "Invalid zip file format".
Do you know what I'm doing wrong?
Click to expand...
Click to collapse
Strange
Try downloading the update again maybe it got corrupt during the download.
Make sure it's from OP website too
Whats wrong with .10 ? .11 borked or something?
virtyx said:
Strange
Try downloading the update again maybe it got corrupt during the download.
Make sure it's from OP website too
Click to expand...
Click to collapse
I got 9.5.9 from the OP forums and it worked! Everything is exactly how I want it now. Thanks for your help!
sarni84 said:
Whats wrong with .10 ? .11 borked or something?
Click to expand...
Click to collapse
For my purposes, 9.5.9 and 9.5.10 are good. 9.5.11 reverted something with the brightness and so I don't want to use it.
I found a zip from the OP site for 9.5.9 so I was able to update to that one and since I got root/substratum to work without issue, I'm happy to stay at this build. In my eyes, my phone is absolutely perfect now and I am extremely happy. The only thing I would change is the size but that has nothing to do with the software/OS. Thanks for everybody's help!
bmcmr said:
I got 9.5.9 from the OP forums and it worked! Everything is exactly how I want it now. Thanks for your help!
For my purposes, 9.5.9 and 9.5.10 are good. 9.5.11 reverted something with the brightness and so I don't want to use it.
I found a zip from the OP site for 9.5.9 so I was able to update to that one and since I got root/substratum to work without issue, I'm happy to stay at this build. In my eyes, my phone is absolutely perfect now and I am extremely happy. The only thing I would change is the size but that has nothing to do with the software/OS. Thanks for everybody's help!
Click to expand...
Click to collapse
I don't blame you, 9511 isn't as smooth as 9510.
also noticed 9510 had better battery life.
I might roll back myself

Categories

Resources