Related
Okay everybody, first off let me apologize, as I am sure that this is asked quite a bit. However, I am not very savvy with using terminal and such to enable sideloading on my Captivate, and I cannot get any of the methods to work properly.
I started off with the Unleash the Beast root on my phone, then for some reason I thought that froyo was out as an official update, because when I went to check for an update, it would download a package, reboot my phone, then tell me that the update could not be applied. So, thinking that it was due to the root, I had to use Odin to get Unleash the Beast off the phone; however, whatever "update" the phone was attempting to apply still would not work. So I reverted back to root the phone. I have used the One Click Root to program, I have installed BusyBox, and allowed SuperUser access. I am trying to enable sideloading so that I can download the Market Access app, but I am having troubles getting it to work. I have a Mac, and I have used many methods to try and enable it, but no matter what I do it will not work.
Again, I apologize for my ignorance. I have searched all over, and I still can't get this stuff to work. If anybody could provide any assistance, it would be greatly appreciated.
Thanks
goosefraba91 said:
Okay everybody, first off let me apologize, as I am sure that this is asked quite a bit. However, I am not very savvy with using terminal and such to enable sideloading on my Captivate, and I cannot get any of the methods to work properly.
I started off with the Unleash the Beast root on my phone, then for some reason I thought that froyo was out as an official update, because when I went to check for an update, it would download a package, reboot my phone, then tell me that the update could not be applied. So, thinking that it was due to the root, I had to use Odin to get Unleash the Beast off the phone; however, whatever "update" the phone was attempting to apply still would not work. So I reverted back to root the phone. I have used the One Click Root to program, I have installed BusyBox, and allowed SuperUser access. I am trying to enable sideloading so that I can download the Market Access app, but I am having troubles getting it to work. I have a Mac, and I have used many methods to try and enable it, but no matter what I do it will not work.
Again, I apologize for my ignorance. I have searched all over, and I still can't get this stuff to work. If anybody could provide any assistance, it would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
Could you provide a little more information about your phone? Is it stock JF6 with just root? If not provide firmware information and anything else that might be useful
P.S. Questions belong in the Q&A section
I'm not really sure what JF6 is haha...After I used Odin and set it back to stock conditions, the only thing I did was use the One Click Root.
As far as sideloading goes, the One Click De-Cripple method on page 2 of the general forum worked for me. If you want to know what version your phone is, go to the about phone section under your settings menu. If you need or want to upgrade to JH7, which was the last OTA update from ATT, do a search and there are a few options out there for that.
Well unfortunately I cannot use OCD on Mac..I tried to do the command prompts, but the su is asking for a password, which is odd because the way I understand it, it shouldn't be doing that
goosefraba91 said:
Well unfortunately I cannot use OCD on Mac..I tried to do the command prompts, but the su is asking for a password, which is odd because the way I understand it, it shouldn't be doing that
Click to expand...
Click to collapse
You did type adb shell first right? Then you should get a "$" where you then type su. It then echoes back su and you should see a "#".
From what you just said, it sounds like you're attempting to get root access on your mac through terminal, which in that case should be your password.
miztaken1312 said:
You did type adb shell first right? Then you should get a "$" where you then type su. It then echoes back su and you should see a "#".
From what you just said, it sounds like you're attempting to get root access on your mac through terminal, which in that case should be your password.
Click to expand...
Click to collapse
Ok, I got that to work. Now I'm just having trouble entering the code for mac. Like I said, I'm not very savvy with this stuff, so pardon my ignorance, haha.
I'm using the method in the "How to: Remove (Almost) Every Trace of AT&T" thread. (I would post a link, but since I'm a new user, it won't let me)
Is there anything different that I need to put into terminal other than the "./adb"?
I tried to paste the link to this thread but being a new member I am not allowed to post a link because of spam issues. Do a google search for "how to enable non market apps on captivate consolidated" and this will be the first xda thread that comes up.
This thread gives several methods for permanent enabling of sideloading. Being a noob, all of them were a little intimidating to me except for METHOD 3. You don't need a computer and you can do it all on your phone with Root Explorer, SQ Lite, and Terminal Emulator which are all available on the market. The step by step is pretty good and I have done it twice with no issues.
Roof King said:
I tried to paste the link to this thread but being a new member I am not allowed to post a link because of spam issues. Do a google search for "how to enable non market apps on captivate consolidated" and this will be the first xda thread that comes up.
This thread gives several methods for permanent enabling of sideloading. Being a noob, all of them were a little intimidating to me except for METHOD 3. You don't need a computer and you can do it all on your phone with Root Explorer, SQ Lite, and Terminal Emulator which are all available on the market. The step by step is pretty good and I have done it twice with no issues.
Click to expand...
Click to collapse
That method worked great. Thank you!
No prob!
Happy Modding!
Glad you got it working. For the record, the next time you guys wanna post links, just replace the http in the front with hxxp. Most people will fix it when they copy/paste it
Sent from my Captivate
I've been working on my framework-res.apk lately, but haven't tried pushing it yet. I know (most of) how to do the procedure, but i want to be sure before i try. If i screw up, i'll be without a phone for a few days due to my current internet connection. (No, i don't want to wait )
What i know, is that i should modify the apk with 7-Zip, replace the graphics i intended (mostly statusbar icons). I don't have to sign the apk since i'm pushing it trough adb shell, and my rom (V10e) is already rooted. The commands for pushing it from adb shell are simply as follows:
Code:
adb push framework-res.apk /system/framework
I have the three following questins that google can't seem to answer for me:
1. Should i wipe dalvik cache (or anything else) after i push the framework-res.apk?
2. If the answer to the previous question is yes, then can i wipe dalvik cache without a custom bootloader?
3. Does anybody have any experience with doing this to the V10e rom? According to google, a lot of users seem to have problems with apps force closing after doing this, even though it's only graphics that has been replaced. However, this is on random handsets, not P-970...
hulkhaugen said:
1. Should i wipe dalvik cache (or anything else) after i push the framework-res.apk?
2. If the answer to the previous question is yes, then can i wipe dalvik cache without a custom bootloader?
3. Does anybody have any experience with doing this to the V10e rom? According to google, a lot of users seem to have problems with apps force closing after doing this, even though it's only graphics that has been replaced. However, this is on random handsets, not P-970...
Click to expand...
Click to collapse
1.you don't have to wipe dalvik cache,just reboot
2.
3.to avoid fc,you should backup your original framework-res.apk,if you face fc,just push the original one back.
Well thanks for your reply
I just found out something stupid. I don't have access to WiFi atm, nor 3g, so i downloaded ClockworkMOD.apk and recovery-clockwork-5.0.2.6-p970.img, figured i could install it manually. So i started CWM, and tapped Reboot into recovery...nope, should note have done that, lol. When it started up, i got a huge error label, with LG security error as a subtitle to that. Now my phone won't start. After that message, my phone proceeds to boot, but stops at the LG logo. Tried removing the battery and start it up again, but same thing happens again, LG saying Error, lol in YOUR FACE to me, and gets locked in booting... Well, suppose i'll be without a phone for a few days...
hulkhaugen said:
Well thanks for your reply
I just found out something stupid. I don't have access to WiFi atm, nor 3g, so i downloaded ClockworkMOD.apk and recovery-clockwork-5.0.2.6-p970.img, figured i could install it manually. So i started CWM, and tapped Reboot into recovery...nope, should note have done that, lol. When it started up, i got a huge error label, with LG security error as a subtitle to that. Now my phone won't start. After that message, my phone proceeds to boot, but stops at the LG logo. Tried removing the battery and start it up again, but same thing happens again, LG saying Error, lol in YOUR FACE to me, and gets locked in booting... Well, suppose i'll be without a phone for a few days...
Click to expand...
Click to collapse
Ilko's package contained CWM I believe, installing via command with single click. Do you have a nandroid? Install v20a, chinese one via smartflash (no net connection needed). Install CWM (UPK) then restore nandroid.
Problem is if you don't have them. It's good to save these files for future troubleshooting.
Edit: my bad, sorry. You don't have CWM before. So no nandroid.
Nope, no nandroid. Recently unbricked my phone using LG software. My current internet connection is to slow to start up LGMobile update, lol. I'll be home in about 32 hrs (i hope, i'm far offshore atm). Guess i won't be able to do anything until then. I'll look into the framework-res.apk then, hehe. Merry x-mas
Thread moved
Questions belong here, not in development, until something is actually developed.
Do i need busybox?
I tried using RSD with 7.7.1Q-144_MB886_MR1-22_SIGNED_CFC and it failed (phone won't boot now either until I choose 'factory'). I tried using motofail2go and get the error: more than one device and emulator.
I wish I never updated (esp. since it broke Flash). Is there anyway I can root it, or revert the update?
I even tried running Motorola_Atrix_HD_Utility.bat and it gives the error "& was unexpected at this time."
I'm thinking maybe if I go to a different computer and just do motofail2go, it might work? Not sure, but the "more than one device and emulator" kind of sounds like there is too much stuff running? (I've been pissing with this for hours)
Can anyone fix any of my errors, or recommend a root / revert method that will work with 4.1.1?
Well
tibberous said:
I tried using RSD with 7.7.1Q-144_MB886_MR1-22_SIGNED_CFC and it failed (phone won't boot now either until I choose 'factory'). I tried using motofail2go and get the error: more than one device and emulator.
I wish I never updated (esp. since it broke Flash). Is there anyway I can root it, or revert the update?
I even tried running Motorola_Atrix_HD_Utility.bat and it gives the error "& was unexpected at this time."
I'm thinking maybe if I go to a different computer and just do motofail2go, it might work? Not sure, but the "more than one device and emulator" kind of sounds like there is too much stuff running? (I've been pissing with this for hours)
Can anyone fix any of my errors, or recommend a root / revert method that will work with 4.1.1?
Click to expand...
Click to collapse
Part of the problem is I had bluestacks running, which apparently breaks the motofail2go app. So, I got motofail2go to say exploit complete, and reset the phone.
Problem is, its still screwed up from RSD, and it only boots on 'factory'. I got the root checker app, and it's still saying I don't have root - problems might be related, I'm not sure.
!!!
tibberous said:
Part of the problem is I had bluestacks running, which apparently breaks the motofail2go app. So, I got motofail2go to say exploit complete, and reset the phone.
Problem is, its still screwed up from RSD, and it only boots on 'factory'. I got the root checker app, and it's still saying I don't have root - problems might be related, I'm not sure.
Click to expand...
Click to collapse
RSD fails every god damn time I run it. "preflash validation failed for GPT"
Any ideas? Please?
Update: I can get it to Flash ICS, but it won't overwrite 3 files, and the system version stays at 4.1.1. It also won't root with motofail2go.
I'll never update anything! I've NEVER seen a new version get rid of so many features - Google needs to remember it whole "Don't be evil" slogan. I could of literally dropped the phone in a pile of **** and done less damage than "upgrading" to jellybean.
I'm about ready to just buy a $100 phone off eBay that isn't ****ed up. If I could get a froyo phone with tethering, I wouldn't even need to root it.
tibberous said:
RSD fails every god damn time I run it. "preflash validation failed for GPT"
Any ideas? Please?
Update: I can get it to Flash ICS, but it won't overwrite 3 files, and the system version stays at 4.1.1. It also won't root with motofail2go.
I'll never update anything! I've NEVER seen a new version get rid of so many features - Google needs to remember it whole "Don't be evil" slogan. I could of literally dropped the phone in a pile of **** and done less damage than "upgrading" to jellybean.
I'm about ready to just buy a $100 phone off eBay that isn't ****ed up. If I could get a froyo phone with tethering, I wouldn't even need to root it.
Click to expand...
Click to collapse
So your on ICS but it says your still on job?
tibberous said:
RSD fails every god damn time I run it. "preflash validation failed for GPT"
Any ideas? Please?
Update: I can get it to Flash ICS, but it won't overwrite 3 files, and the system version stays at 4.1.1. It also won't root with motofail2go.
I'll never update anything! I've NEVER seen a new version get rid of so many features - Google needs to remember it whole "Don't be evil" slogan. I could of literally dropped the phone in a pile of **** and done less damage than "upgrading" to jellybean.
I'm about ready to just buy a $100 phone off eBay that isn't ****ed up. If I could get a froyo phone with tethering, I wouldn't even need to root it.
Click to expand...
Click to collapse
I keep getting this error also "preflash validation failed for GPT".... What did you do to get past that?
jkm43 said:
I keep getting this error also "preflash validation failed for GPT".... What did you do to get past that?
Click to expand...
Click to collapse
because cant roll back to ICS I AM too waiting for new exploit
I rooted once upon a time using Kingo Root. Worked fine, love being rooted, been doing it for years. But as everyone knows, the GPS signal is really crap on these phones. Mine keeps cutting out randomly.
Lo and behold! KitKat is now available! And among the changes AT&T is bragging about is improved GPS performance. As much as I enjoy being rooted, I need a working GPS a lot more. So I tried installing the OTA update... but it failed. I assume because the device status is listed as "Custom".
So I used Triangle Away, did a full unroot using SuperSU, rebooted... and it still says "Custom". There didn't used to be an open padlock during boot while I was rooted, but now there is, along with the word "Custom". Check the Odin mode, and sure enough it says the system status is "Custom". However Knox flag is still 0x0, and it states I'm running the Samsung Official binary. I've never flashed a ROM on this phone, all I did was root it.
Re-rooted, installed Triangle Away again. It states my system status is "Official" and the flash counter is at 0. However whenever I check the Device status in settings, it always says "Custom". There doesn't appear to be any way to get it back to "Official". Sometimes I can get it to say "Official" for a single boot, but then it always reverts back to "Custom" within a couple minutes whether the phone is rooted or not.
What am I doing wrong?
After unroot, you need to do a factory reset, then boot into your recovery, wipe cache, reboot your phone few times the pad lock and custom logo should go away. I am not sure about the "Device status in settings" showing custom, mine always shows official.
GoremanX said:
I rooted once upon a time using Kingo Root. Worked fine, love being rooted, been doing it for years. But as everyone knows, the GPS signal is really crap on these phones. Mine keeps cutting out randomly.
Lo and behold! KitKat is now available! And among the changes AT&T is bragging about is improved GPS performance. As much as I enjoy being rooted, I need a working GPS a lot more. So I tried installing the OTA update... but it failed. I assume because the device status is listed as "Custom".
So I used Triangle Away, did a full unroot using SuperSU, rebooted... and it still says "Custom". There didn't used to be an open padlock during boot while I was rooted, but now there is, along with the word "Custom". Check the Odin mode, and sure enough it says the system status is "Custom". However Knox flag is still 0x0, and it states I'm running the Samsung Official binary. I've never flashed a ROM on this phone, all I did was root it.
Re-rooted, installed Triangle Away again. It states my system status is "Official" and the flash counter is at 0. However whenever I check the Device status in settings, it always says "Custom". There doesn't appear to be any way to get it back to "Official". Sometimes I can get it to say "Official" for a single boot, but then it always reverts back to "Custom" within a couple minutes whether the phone is rooted or not.
What am I doing wrong?
Click to expand...
Click to collapse
Did you delete system (AT&T) apps?
coolmingli said:
After unroot, you need to do a factory reset, then boot into your recovery, wipe cache, reboot your phone few times the pad lock and custom logo should go away. I am not sure about the "Device status in settings" showing custom, mine always shows official.
Click to expand...
Click to collapse
Yep, I did all of that. Exact procedure:
- Reset flash counter using triangle away
- full unroot using SuperSU
- reboot immediately into Odin mode (system status says "Official")
- reboot immediately into recovery, do a factory reset
- reboot immediately into Odin mode (system status still says "Official")
- reboot immediately into recovery, do ANOTHER factory reset (because I'm anal that way)
- reboot immediately into Odin mode, (system status STILL says "Official")
- reboot normally, go through normal first-time setup, go into settings, check Device status... it says "Custom"
- reboot into Odin mode, system status now says "Custom"
- reboot normally, stupid open padlock is there again with the word "Custom"
- countless reboots later, it still says "Custom"
serpent2005 said:
Did you delete system (AT&T) apps?
Click to expand...
Click to collapse
Nope, none. They're all still there. Like I said, I'm still running the bone stock image, never flashed a ROM, and I never edited the image. I only use root for things like GMD S-pen control, Titanium Backup, and FS Trim.
What's really annoying is that damn open padlock is never there while the system really IS modified, it only shows up when I unroot and everything is back to stock. I call it irony.
Would region lock be affecting this? I disabled the region lock many moons ago using RegionLock Away. Does that survive after a factory reset, and would it cause my device status to show up as Custom?
Nope, restoring the region lock did not fix the problem. It continues to revert to "Custom" Device status no matter what I try. This is infuriating.
GoremanX said:
Nope, restoring the region lock did not fix the problem. It continues to revert to "Custom" Device status no matter what I try. This is infuriating.
Click to expand...
Click to collapse
This is what you need to do
http://forum.xda-developers.com/showthread.php?t=2559715
it fully returns your phone to stock. and you can get your OTAs again at that point.
the2rrell said:
This is what you need to do
http://forum.xda-developers.com/showthread.php?t=2559715
it fully returns your phone to stock. and you can get your OTAs again at that point.
Click to expand...
Click to collapse
I tried that too. Didn't work. Still says "Custom". However, part of those instructions failed for me, the Heimdall image upload did not work at all. Never could figure out why.
GoremanX said:
I tried that too. Didn't work. Still says "Custom". However, part of those instructions failed for me, the Heimdall image upload did not work at all. Never could figure out why.
Click to expand...
Click to collapse
they work, it maybe your PC, i know Heimdall can be a bugger at times. It DOES work though. have you tried another PC if that is an option.
the2rrell said:
they work, it maybe your PC, i know Heimdall can be a bugger at times. It DOES work though. have you tried another PC if that is an option.
Click to expand...
Click to collapse
I just tried it from my laptop, same result. The MI9_fix.img.ext4 file refuses to upload to my device. The instructions state it should fail at 95%, but it always fails immediately. I tried downloading the file multiple times from different mirrors to make sure I wasn't getting a bad one. The result is always:
Uploading SYSTEM
0%
ERROR: Failed to send file part packet!
ERROR: SYSTEM upload failed!
GoremanX said:
I just tried it from my laptop, same result. The MI9_fix.img.ext4 file refuses to upload to my device. The instructions state it should fail at 95%, but it always fails immediately. I tried downloading the file multiple times from different mirrors to make sure I wasn't getting a bad one. The result is always:
Uploading SYSTEM
0%
ERROR: Failed to send file part packet!
ERROR: SYSTEM upload failed!
Click to expand...
Click to collapse
you have all the drivers and everything loaded up?
thats odd.
Yep, everything called for in the instructions. I get the same result every time.
Did I mention how infuriating this is?
GoremanX said:
Yep, everything called for in the instructions. I get the same result every time.
Did I mention how infuriating this is?
Click to expand...
Click to collapse
Yes but it should work, another member just did the same thing you are trying to do. with success. it has to be drivers or maybe running odin as a admin.
Oh and you may want to move the Odin file to a folder on your desktop or just put them on your desktop and try that. im betting its something simple that we are just over looking.
Finally got it restored to factory. Just about everything that can go wrong did go wrong. My USB cable failed. Then my SD card failed and was spitting out garbage. And one of my downloaded files was corrupted. At one point, I got the status back to "Official", but the phone was so screwed up it was nearly unusable, spitting out error messages every 30 seconds. When this happened, I took it to a local AT&T store hoping they would just flash a new image on there (it did say "Official" in all the right places after all). But all they wanted to do was replace it with a refurb unit. Screw that! So I went home and tried AGAIN, re-downloading everything and using an all new USB wire and SD card, and this time it worked like a charm.
Now I'm attempting to install the OTA update, hopefully all goes according to plan.
Nope, complete failure. Update to NB4 worked fine, but then the update to KitKat failed at 27%. The MJ5 image being used in that thread is not a stock image. It's "fixed" to allow rooting.
Maybe I'll take that refurbished phone from AT&T after all... bastards
GoremanX said:
Nope, complete failure. Update to NB4 worked fine, but then the update to KitKat failed at 27%. The MJ5 image being used in that thread is not a stock image. It's "fixed" to allow rooting.
Maybe I'll take that refurbished phone from AT&T after all... bastards
Click to expand...
Click to collapse
That is stock. It's not prepared for root. You can choose to root or not. I have not updated so I don't know. But if you made it to nb4 why do think it would do that if the mj5 was fixed for root right
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Nah, everyone else in the same situation as me has the exact same problem:
http://forum.xda-developers.com/showthread.php?t=2686652&page=21
We're talking dozens and dozens of attempts by sozens and dozens of people here. Downgrading to the MJ5 image in that restore thread does not actually bring the phone back to stock. The NB4 upgrade apparently just doesn't have the same level of verifying in it as the KitKat update. The author of that thread specifically mentions that the MJ5 image he's listing has been modified to allow rooting using his method, but the rooting part of it is optional. Either way, the image itself has been modified. That's why it has the word "fix" in the filename.
Others have stated that going to an AT&T retail location and having them flash a real MJ5 image DID work, and allowed the KitKat update to happen without issues.
So.. if I missed any posts dealing with this, please forgive me. I am a total noobie at this hobby so I'm not really familiar with all the acronyms or terminology thrown around. I have an M8 HK, I rooted the phone using Opensourcegangster's youtube video. I was able to wi-fi tether no problem. All was good for a few days until the 1.54.654.13 update tried to come through. OK, so the rooted phone wouldn't update the phone, because of the root? I understand that and it kept asking to update. I didn't have time to do update the phone and it asked every 2 hours for days, Now, the phone has stopped asking to update but has also started dropping every call after 10 sec even though signal strenghth seems to be strong and now won't connect to 3G or LTE data. I don't know if any of this is related or if I can even go to a store for help because of the root.
Thanks in advance
chinrednek said:
So.. if I missed any posts dealing with this, please forgive me. I am a total noobie at this hobby so I'm not really familiar with all the acronyms or terminology thrown around. I have an M8 HK, I rooted the phone using Opensourcegangster's youtube video. I was able to wi-fi tether no problem. All was good for a few days until the 1.54.654.13 update tried to come through. OK, so the rooted phone wouldn't update the phone, because of the root? I understand that and it kept asking to update. I didn't have time to do update the phone and it asked every 2 hours for days, Now, the phone has stopped asking to update but has also started dropping every call after 10 sec even though signal strenghth seems to be strong and now won't connect to 3G or LTE data. I don't know if any of this is related or if I can even go to a store for help because of the root.
Thanks in advance
Click to expand...
Click to collapse
In order to accept an OTA update, such as the one trying to come through on your phone, you need to have stockish Sense Rom and the Stock Recovery. I haven't seen the video you mentioned but if your method of rooting involved installing a custom recovery this is likely why your update is failing. Your phone will reboot, enter your custom recovery, attempt to run the script, fail, rinse and repeat until you revert to stock recovery. Lucky for you rooting is really easy to undo, all you need to do is grab the stock recovery for your HK (I pulled the one out of the .9 RUU that's up at another link, i'll try to post it for you in a minute), and then reboot to fastboot (this requires the android SDK and administrator level command window - shift+right click the folder fastboot.exe is in and select open command window here). Then to flash it type "/fastboot flash recovery recovery.img" with no quotes and make sure you have the recovery in the same folder as fastboot. Give me a few minutes here and ill give you the recovery.img file you need.
Here is the link for the M8 HK stock recovery: http://rg.to/file/8e32e8cc37ac93d3f0206994f1c7a59b/recovery.img.html
That should be all you need to either a) accept the OTA (there are other methods of getting this update since you're rooted btw) or b) visit a sprint store and have them check over your phone.
As I suffered data loss on my first HK and no matter what could not fix it I suggest going with the lengthier method of getting the update as I've listed it above so that you can go in and get your phone checked out.
Oh, the bootloader.... so there is another step to take if you want to appear 100% unmodified and this step should be completed before you unroot...
I followed this method and had a Sprint technician run tests on my phone later that day and had 0 issues getting a replacement device...
It's a bit much to go into so I'm just going to link you to the forum page I followed: http://forum.xda-developers.com/showthread.php?t=2710503
You will need to grab the "Faux Locked Hboot" for Sprint near the bottom of the first post and then follow the instructions listed prior to it in the top section.
EDIT: It just occurred to me that you are S-ON, yes? The phone I did this with was S-OFF so I'm not 100% certain it will work for you. Can anyone else confirm that you can flash a modified Hboot in rebootRUU state being S-ON? Or perhaps have another method of making the bootloader say Locked and not Relocked as "/fastboot oem lock" results in?