i hope it doesnt force itself on the phone..
cookzitall said:
i hope it doesnt force itself on the phone..
Click to expand...
Click to collapse
Just don't let it force itself on the phone
If you want to disable OTA updates, you can remount your system folder, and delete /system/app/Updater.apk and /system/app/Updater.odex
I've done that on my own phone with no negative effects (so far). I'm fairly sure that should disable any OTA updates from being installed.
Once it does come out, I plan on downloading it (onto my computer), and giving it a good going over. I'll yank out anything that looks like it will disable my root access, and then resign it with the test keys and load it onto the phone using a modified recovery tool.
JesusFreke said:
Just don't let it force itself on the phone
If you want to disable OTA updates, you can remount your system folder, and delete /system/app/Updater.apk and /system/app/Updater.odex
I've done that on my own phone with no negative effects (so far). I'm fairly sure that should disable any OTA updates from being installed.
Once it does come out, I plan on downloading it (onto my computer), and giving it a good going over. I'll yank out anything that looks like it will disable my root access, and then resign it with the test keys and load it onto the phone using a modified recovery tool.
Click to expand...
Click to collapse
Ditto my good man.
We don't have to reject it per se any OTA "official" update. We just have to modify it and load it. It will have benefits to update, just not completly to Google's standards
can some one please help..
in the "how to get root" thread i asked a question..can some one help me out...thank u
JesusFreke said:
Once it does come out, I plan on downloading it (onto my computer), and giving it a good going over. I'll yank out anything that looks like it will disable my root access, and then resign it with the test keys and load it onto the phone using a modified recovery tool.
Click to expand...
Click to collapse
Details? I was under the impression the retail bootloader wouldn't accept any keys except tmob/google's.
With root though its no biggie to just install the update manually.
well who ever does accept this update please make not of the url it's calling so those of us that aren't can manually grab it. assuming this will still be an option
cookzitall said:
i hope it doesnt force itself on the phone..
Click to expand...
Click to collapse
It sounds like the current state of affairs is not safe. Everything typed on the phone is also submitted to a root shell. It is just a matter of time before I inadvertently type something that damages the filesystem.
wolfgangrupprecht said:
It sounds like the current state of affairs is not safe. Everything typed on the phone is also submitted to a root shell. It is just a matter of time before I inadvertently type something that damages the filesystem.
Click to expand...
Click to collapse
So start each reboot by typing "kill 26"
Disconn3ct said:
So start each reboot by typing "kill 26"
Click to expand...
Click to collapse
That won't help, as it's respawned by init when it dies. Maybe kill -STOP 26 would work, but I haven't verified that.
jimparis said:
That won't help, as it's respawned by init when it dies. Maybe kill -STOP 26 would work, but I haven't verified that.
Click to expand...
Click to collapse
Nope
Tried kill -STOP from adb shell, then "<cr>sleep 90<cr>" and ps showed 'sleep' running. (Sure, I could use 'reboot' but thats just a pita.)
has anyone thought to type "exit" and see if that terminal closes?
Darkrift said:
has anyone thought to type "exit" and see if that terminal closes?
Click to expand...
Click to collapse
it does but a new one is automatically spawned, so..
there are a new terminal emulator in the market that close with exit and you can do the same .
Disconn3ct said:
it does but a new one is automatically spawned, so..
Click to expand...
Click to collapse
satru said:
there are a new terminal emulator in the market that close with exit and you can do the same .
Click to expand...
Click to collapse
we are talking about the "invisible" ghost terminal that is open on the G1 by default, not one you install and run.
Can somebody explain to me why you woudnt want to update to rc30?
donutman said:
Can somebody explain to me why you woudnt want to update to rc30?
Click to expand...
Click to collapse
rc30 prevents root access. if you don't know why you want root, you prolly don't
JesusFreke said:
Just don't let it force itself on the phone
If you want to disable OTA updates, you can remount your system folder, and delete /system/app/Updater.apk and /system/app/Updater.odex
I've done that on my own phone with no negative effects (so far). I'm fairly sure that should disable any OTA updates from being installed.
Once it does come out, I plan on downloading it (onto my computer), and giving it a good going over. I'll yank out anything that looks like it will disable my root access, and then resign it with the test keys and load it onto the phone using a modified recovery tool.
Click to expand...
Click to collapse
You are awesome. Thanks and God bless you!
bennekl said:
You are awesome. Thanks and God bless you!
Click to expand...
Click to collapse
Wondering if Google guys are cursed him already
i keep getting a pop up saying that there i an update ready for the hone or something like that. is that the new update trying to come in. i just keep canceling it
The Great NY said:
i keep getting a pop up saying that there i an update ready for the hone or something like that. is that the new update trying to come in. i just keep canceling it
Click to expand...
Click to collapse
Hack it now or never, it will eventually apply the patch anyway.
Related
I just got a message saying there is an update available. I told it not to do it. I do not want RC30 because it gets rid of root.
However, the other side of me is tempted to see if telnetd and all the other goodies are still there.
I'm also very tempted to install it to see if it removes root access. I hope someone who doesn't care about root access tests this out and reports back soon, because my curiosity is about to get the better of me.
It won't stop prompting me and I don't think I have the heart to keep saying no.
Look on your phone, and see if there is a file named "update.install" in the /cache folder. Or maybe in the /cache/recovery folder. If so, would you mind grabbing it off your phone and posting it somewhere?
Woobins said:
I'm also very tempted to install it to see if it removes root access. I hope someone who doesn't care about root access tests this out and reports back soon, because my curiosity is about to get the better of me.
It won't stop prompting me and I don't think I have the heart to keep saying no.
Click to expand...
Click to collapse
If you ever do say yes can you tell us what your software version is?
JesusFreke said:
Look on your phone, and see if there is a file named "update.install" in the /cache folder. Or maybe in the /cache/recovery folder. If so, would you mind grabbing it off your phone and posting it somewhere?
Click to expand...
Click to collapse
neoobs said:
If you ever do say yes can you tell us what your software version is?
Click to expand...
Click to collapse
The only file of interest in the /cache directory is named, signed-RC30-from-RC29-fat.1582cace.zip. From this I'm assuming it's going to update my phone to RC30. I've made the file available here in case anyone is curious.
Ah, ok. It looks like that's the same file I just posted a link to then. Thanks
boo
neoobs said:
If you ever do say yes can you tell us what your software version is?
Click to expand...
Click to collapse
It did it.
just as I get home to catch up on the "jailbreak" and start doing it I get an
error while connecting to server, "connection refused"
error while receiving from server null
So I figured I'd check (I neglect my phone when I'm at work, and no, I don't recall accepting the update)
lo and behold:
Build description: kila-user 1.0 TC4-RC30 116143
ota-rel-keys, release-keysBuild ID: TC4-RC30
Build Date: Fri Oct 31 19:00:53 PDT 2008
Build type: user
Phone type: dream
Product brand: tmobile
Build user: android-build
Build host: undroid11.corp.google.com
Linux kernel version: 2.6.25-01843-gfea26b0
[email protected] #6Mon Oct 6 14:13:36 PDT 2008Baseband version: 62.33.20.08H_1.22.12.29
RIL Impl version: HTC-RIL 1.0 (Aug 19 2008,21:32:33)
Default keyboard device: trout-keypad-v3
That just proves that RC30 is specificaly out to close the telnet jailbreak method.
No need to apply it to patch/update other parts of the OS since it doesn't have anything else.
MMTest97 said:
error while connecting to server, "connection refused" error while receiving from server null
Click to expand...
Click to collapse
After starting telentd via pTerminal?
quedijo said:
That just proves that RC30 is specificaly out to close the telnet jailbreak method.
No need to apply it to patch/update other parts of the OS since it doesn't have anything else.
After starting telentd via pTerminal?
Click to expand...
Click to collapse
It has more than just that fix. It patches quite a few other packages on the phone... for what purpose? I don't know.
quedijo said:
That just proves that RC30 is specificaly out to close the telnet jailbreak method.
No need to apply it to patch/update other parts of the OS since it doesn't have anything else.
After starting telentd via pTerminal?
Click to expand...
Click to collapse
yes
tried pterminal and terminal emulator
netstat shows the ip
but telnet from pc fails to connect failed on port 23 and the port shown on netstat
I also tried the steps koush put up but still fail
granted I'm no linux/unix pro and I just installed cygwin a couple days after the connect bot app came out; so I may be doing something wrong
Does google check in the new change into the source tree before they push a update?
In addition to jailbreak fix there is a battery fix as well and a few others according to androidcommunity.com.
Well I finally got tired of clicking no and decided to go ahead and perform the update. After it finished, the phone rebooted and instead of booting up, the phone simply displays a '!' icon with a triangle around it and hangs. I'm not taking this as a good sign. I tried removing the battery but that didn't help.
I really hope the update didn't just brick my phone.
Woobins said:
Well I finally got tired of clicking no and decided to go ahead and perform the update. After it finished, the phone rebooted and instead of booting up, the phone simply displays a '!' icon with a triangle around it and hangs. I'm not taking this as a good sign. I tried removing the battery but that didn't help.
I really hope the update didn't just brick my phone.
Click to expand...
Click to collapse
When you're at the screen with the ! and triangle, Try pressing home+back (maybe several times). It should reboot, and hopefully boot back up normally.
JesusFreke said:
When you're at the screen with the ! and triangle, Try pressing home+back (maybe several times). It should reboot, and hopefully boot back up normally.
Click to expand...
Click to collapse
No dice. The phone reboots but still hangs at the error screen. The only thing I can think that might have caused it is that, while playing around, I set a root password and forgot to clear it before the update rebooted the phone. Who knows. I guess I'll call tmobile and see what can be done.
edit: I should mention that pressing alt-w to wipe the phone does not work either. It still returns to the error screen. I'm talking to tmobile tech support now and the original tech said that 'they were informed that a small number of users might experience this problem with the update'. I'm on hold waiting to talk to an android tech now. My advice to everyone who's played around with adding any extra files to /etc to hold off on upgrading for now. I'll report back with the results of my call with the android tech.
Now they're saying they would like to exchange the phone. Problem is the g1 isn't in their replacement program yet.
Aaaand they're out of stock so it's going to be at least 2 weeks.
I wish I'd have just kept hitting no.
Disturbing news, especially as I'm wanting to install a modified rc30. What exactly did you change?
I was playing around with trying to get dropbear to work and in the process I created some files in /etc (passwd, shadow, groups, etc). As well as creating a new regular user, I also added a password to the root account and carelessly forgot to remove it before applying the update. I'm only guessing here but I wouldn't be surprised if the new root password is what did it. The system does not have one by default and I wonder if that caused it to hang, waiting for a password to be entered while booting.
On a brighter note, I persisted and was able to get them to send me out a new phone immediatly. This has the added benefit of possibly fixing the loose-screen/creaking problem that I, like many others, am experiencing with the phone.
I'm wondering if I should try manually applying the update from the SD card while I wait for the new phone to see if that solves the problem. I probably should have tried that before calling. I'm hesitant to do that now, however, since if it does fix it, I'm not sure how tmobile would react to me returning a perfectly working phone.
Woobins said:
No dice. The phone reboots but still hangs at the error screen. The only thing I can think that might have caused it is that, while playing around, I set a root password and forgot to clear it before the update rebooted the phone. Who knows.
Click to expand...
Click to collapse
I don't get it. The update should restore whole /system folder, isn't it? /etc is actually a symlink to /system/etc, so, it should be restored too and passwd file successively removed.
Otherwise, I don't see any problem to keep the root access! Since /system is mounted without nosiud (any changes in RC30?), just keep a copy of shell with chmod 4777 somewhere there... where it wouldn't be removed by update, as it keeps passwd, and that's it.
Please, tell me where am I wrong, cause I definitely should be wrong somewhere.
PS: BTW, what was the progress with dropbear? I actually tried to make it work too, creating passwd etc, but no success...
Dimath said:
I don't get it. The update should restore whole /system folder, isn't it? /etc is actually a symlink to /system/etc, so, it should be restored too and passwd file successively removed.
Otherwise, I don't see any problem to keep the root access! Since /system is mounted without nosiud (any changes in RC30?), just keep a copy of shell with chmod 4777 somewhere there... where it wouldn't be removed by update, as it keeps passwd, and that's it.
Please, tell me where am I wrong, cause I definitely should be wrong somewhere.
PS: BTW, what was the progress with dropbear? I actually tried to make it work too, creating passwd etc, but no success...
Click to expand...
Click to collapse
Unlike the RC29 update, the RC30 update doesn't actually do a complete wipe and restore of the /system folder. It patches a number of files (which will fail if any of them have been modified), and does a recursive chmod on the entire /system directory to clear any suid bits.
Hot off the presses. Get it here.
That file is the crappy "patch" version that tries to patch you from RC29 to RC30.
Here is the full update, which should be much more reliable
Obviously, don't install it unless you want to lose root access
Update for those who are interested: I went ahead and bought myself a new G1. One of the stores in the area had a couple. It still had RC28 (not RC29) on it, so I'm back in business. I'll just unlock my RC30 one and sell it on ebay.
OMG how stupid can they be... look what I see in the update script
# delete unneeded files
delete SYSTEM:system/bin/telnetd
Click to expand...
Click to collapse
Can we patch this like today cause I kinda think there is more to this than just doing that.
neoobs said:
OMG how stupid can they be... look what I see in the update script
Can we patch this like today cause I kinda think there is more to this than just doing that.
Click to expand...
Click to collapse
There is. They added a kernel option "console=null", which I suspect basically makes it so that the physical keyboard no longer sends input to the console device. Note that there is still a root shell running on the console though.. it's just that now there isn't any way to send keypresses to that root shell.
Plus there are a ton of patches to the android apps and framework jars and such. Not sure what all changed there.
I'm in the process of modifying the patch, to apply to my phone without losing root access. More to come
What does the "applypatch" piece do?
That part looks different.
Interesting that it's only a 4 meg update, and that it only contains a new recovery.img and a new boot.img - I wonder what is different in those images. I hope they are keeping the recovery stuff in the open source branch updated - because, well, that's the nice thing for them to to do
Jesus Freke - when you get your patched-up version ready, please post it somewhere for us lazy bastards who want to ride your coat-tails
I just noticed something. This update doesn't wipe the system partition. If you had created a setuid copy of the shell ("su", or whatever), I don't think it will get deleted if you applied the update as-is.
but didn't you say it removes the use of keyboard in shell? If so we would still be up the creek. you know what a notice this update came really fast i never got and OTA until this(fishy) i had to force OTA. Well hope you work your magic JesusFreke.
Arg! dangit. I accidentally applied RC30 and lost my root access. I copied the wrong update file to my sdcard... grrrr!
So I'm out of the game. Sorry.
Oh, btw - I was wrong about the update keeping the setuid shell around. It completely wipes the permissions of the system folder, so if you did have a setuid copy of the shell, it will be set back to normal non-setuid status by the update. duh.
Sh**!! You were the shining hope , one question can you still get root through the adb shell? cuz if so you can save your a**
Nope. Like I said, I'm out of the game. Unless someone wants to trade me for a RC19/RC29 phone. Or until another root exploit is found. *sigh*
DOH! That sucks! Sorry to hear that, and thanks for taking one for the team.
So if an update does try to install do we just need to turn off the phone until a solution is found? I may need to go back to my Dash for a while until this all gets figured out!
The update that you meant to put on the card- was it a test? If the worst that will happen is the update will take maybe someone that doesnt mind the update could test it for you?
JesusFreke said:
Arg! dangit. I accidentally applied RC30 and lost my root access. I copied the wrong update file to my sdcard... grrrr!
So I'm out of the game. Sorry.
Click to expand...
Click to collapse
I'm sorry about that!
Also, I'm confused. Hadn't you updated the keys in your bootloader to prevent an update? Or does that simply prevent the phone from downloading an update?
Can not we flash back that old RC29 File again ????
The update zip contains the boot.img and the recovery.img. so when the update starts it rewrites JesusFreke's mod recovery.img
spoofing
could we spoof the version # on our device? thus ending the nag and the ability to force the upgrade, for the time being?
bhang
RegGuheert said:
I'm sorry about that!
Also, I'm confused. Hadn't you updated the keys in your bootloader to prevent an update? Or does that simply prevent the phone from downloading an update?
Click to expand...
Click to collapse
Yes. But I had accidentally re-signed the full update with the new key and updated my phone with it. I was in the process of modifying the update, and had grabbed the wrong file to sign and update.
JesusFreke said:
Yes. But I had accidentally re-signed the full update with the new key and updated my phone with it. I was in the process of modifying the update, and had grabbed the wrong file to sign and update.
Click to expand...
Click to collapse
Ahh! That's a pain in the arse... the usb mass storage process is running as root, any chance of a buffer exploit there?
JesusFreke said:
Yes. But I had accidentally re-signed the full update with the new key and updated my phone with it. I was in the process of modifying the update, and had grabbed the wrong file to sign and update.
Click to expand...
Click to collapse
koush said:
mount -oremount,rw /dev/block/mtdblock3 /system
You can't remount that directory that unless you have root.
Use the dd command to copy stuff around (the cp command is not available). I should mention I'm a Windows guy, and am pretty clueless with Linux: my coworker figured the rest of this out once I got to a root prompt.
Incidentally, in the /system/bin directory there is a flash_image executable that changes the recovery.img used when you hard reset the device. I've noticed that I can run this without root access from a standard adb shell. Maybe we never needed to root the device after all... I think we can flash it without root access... I'm too scared to mess with that at all though.
Click to expand...
Click to collapse
I found this, you may want to look into it.
syrusfrost said:
I found this, you may want to look into it.
Click to expand...
Click to collapse
Thanks. But you have to have root access for the flash_image command to work. Or more precisely, you have to have write access to the /dev/mtd/mtd# device that you are trying to flash.
I am also the same unlucky guy who had Press Update Button and now we are in RC30
Now what are the chances of our device to get root access or ability to flash Test_Signed code in RC30
well i removed( # delete unneeded files delete SYSTEM:system/bin/telnetd )and replaced the boot.img and recovery.img with jesusfreke's anything else i should edit before i try to resign and update?
It seems that quite often after an upgrade (especially when using Apps2SD), Android rebuilds the /data/system/packages.xml file because it thinks you have reinstalled all of your apps. This results in missing apps, force closes, etc, because UIDs have changed and they don't match whats in your /data/data directory. It's almost always fixed by a wipe, but screw that
Download this file: http://n0rp.chemlab.org/android/fix_permissions.sh
Push it to your sdcard, su, and run "sh /sdcard/fix_permissions.sh" and reboot. You should be good to go with NO WIPE!
Credit goes to this guy, I simply ported it to shell code: http://blog.elsdoerfer.name/2009/05/25/android-fix-package-uid-mismatches/
UPDATED: Now works with protected apps.
anddep said:
so when installed.. i dont have to wipe for a new build?
Click to expand...
Click to collapse
Well, there are some other factors, like app data that is stored in the same place but in a different format. You'd likely run into this going back and forth from an HTC based build like Hero or Sapphire and an Android based build like mine, Dude's, or JF's. I can't fix that situation, YMMV.
Except for that special case, this should do the trick.
I hope I don't sound like a complete idiot. Do you do this before or after the update and will this work with any update (like moving from ION to Rogers?
al74 said:
I hope I don't sound like a complete idiot. Do you do this before or after the update and will this work with any update (like moving from ION to Rogers?
Click to expand...
Click to collapse
second that about will it work on any update?
Powermaniac said:
You don't sound like an idiot. That's actually a good question. I'd say before, but I'm curious as well.
Click to expand...
Click to collapse
You would have to do it after the update, and reboot.
Bravo!!!
@Cyanogen: YOU **ARE** THE MAN! Woot!
Now I'm not so hesitant to test out new roms! Thanks cyan
so when installed.. i dont have to wipe for a new build?
damn your good..
Thank you very much
Out of curiousity, is it even possible to implement this into ROM Builds? it would seem simple enough. however I haven't built my own ROM so I'm going off of what I know from programming. ask the guy who created it if you can use his work. lol you're the man, as always.
ok i may of did something wrong but i couldnt get it to work. i used the terminal emulator on the phone and typed the command and it says
mount: permission denied (are you root?)
it continued to do the script but said not permitted for each app.
i definately have root as i just installed your latest rom so what am i doing wrong?
Did you SU first?
Woodard2589 said:
ok i may of did something wrong but i couldnt get it to work. i used the terminal emulator on the phone and typed the command and it says
mount: permission denied (are you root?)
it continued to do the script but said not permitted for each app.
i definately have root as i just installed your latest rom so what am i doing wrong?
Click to expand...
Click to collapse
Denkai said:
Out of curiousity, is it even possible to implement this into ROM Builds? it would seem simple enough. however I haven't built my own ROM so I'm going off of what I know from programming. ask the guy who created it if you can use his work. lol you're the man, as always.
Click to expand...
Click to collapse
Yeah, it should be possible. The script is a little slow, though, so it would need a way of detecting an upgrade in the first place, and it would have to run after all the apks are processed.
g2crx said:
Did you SU first?
Click to expand...
Click to collapse
sure didnt. thanks.
so may I ask... if I wanna go from Haykuro's Hero to JAC's 1.4... all I would have to do is... flash the new ROM and then run your script and I'm done?
That is the idea, yes.
Ran script and flashed from dude's to your build without wipe. I'm getting force closes on
android.process.acore
klaxon
weather widget free
I'm using marcus apps2sd.
Edit nevermind I'm a retard. Figured it out.
amazing, doing this after upgrading from 3.3.6 to 3.3.8 fixed all my issues so far! thank you sir!!
Ryanmo5 said:
Ran script and flashed from dude's to your build without wipe. I'm getting force closes on
android.process.acore
klaxon
weather widget free
I'm using marcus apps2sd.
Click to expand...
Click to collapse
You ran the script first, before the flash? I believe the script is to be run after the flash. Try that and see what happens.
Hey i was wondering if anyone knew how to change the Verizon Wireless text in the notification screen and lock screen on the Droid x!? Easy way??
MonoDraken said:
Hey i was wondering if anyone knew how to change the Verizon Wireless text in the notification screen and lock screen on the Droid x!? Easy way??
Click to expand...
Click to collapse
look here and on droidforums for modifying the eri.xml
HMmm let me look!
http://alldroid.org/default.aspx?g=posts&t=876
Thanks for that but i am wondering if there is a easier way?..
MonoDraken said:
Thanks for that but i am wondering if there is a easier way?..
Click to expand...
Click to collapse
Pay me to do it for you
Haha i would but dont have credit card or anything like that lol...
and parents wont let me use there... -.-'
MonoDraken said:
Thanks for that but i am wondering if there is a easier way?..
Click to expand...
Click to collapse
Its actually quite easy. Takes like 5 minutes.
I'm like a noon at these things :/
Sent from my DROIDX using Tapatalk
It's really not that hard and the feeling of accomplishment you will get by doing it yourself will be worth it.
Just do it.
Just used this method and it was super easy! Got rid of that stupid VZW name and replaced it with something cool. Thanks a bunch!!
Dont really wanna mess up my phone so lol.
MonoDraken said:
Hey i was wondering if anyone knew how to change the Verizon Wireless text in the notification screen and lock screen on the Droid x!? Easy way??
Click to expand...
Click to collapse
Casen said:
http://alldroid.org/default.aspx?g=posts&t=876
Click to expand...
Click to collapse
Wanted to thank MD for starting the thread and Casen for the lnk. Very cool. I now have "android droidX".
MD- how far have you got? Try downloading the android sdk and you can start experimenting with ADB (android debug bridge). If you just google "android sdk" you can go right to google's site and they have instructions there. Or maybe you have all ready messed around with ADB?
anyways, cheers for the good question.
Thanks and idk im trying to look for a easier way first. Theres a app out there it just doesnt support DX yet.
Whenever I push my changed apk back to my system I lose all of my contacts. What's up?
zehkaiser said:
Whenever I push my changed apk back to my system I lose all of my contacts. What's up?
Click to expand...
Click to collapse
I had that same problem originally. Did you follow the directions on the link exactly? If you push the framework-res.apk back to the phone while it is running "normally"- that is what happens (or it happened to me at least).
But when I booted into recovery, mounted system (it will actually read unmount when it is mounted) and then pushed the apk- I didn't have that problem.
I am not sure if that was the only step that made the difference- but is the only one I can think of.
thepolishguy said:
I had that same problem originally. Did you follow the directions on the link exactly? If you push the framework-res.apk back to the phone while it is running "normally"- that is what happens (or it happened to me at least).
But when I booted into recovery, mounted system (it will actually read unmount when it is mounted) and then pushed the apk- I didn't have that problem.
I am not sure if that was the only step that made the difference- but is the only one I can think of.
Click to expand...
Click to collapse
Thanks. I couldn't get my system to recognize the phone while in recovery. I ended up mounting the system while the phone was in Media Sync Mode, issuing the "stop" command, replacing the files and rebooting. Worked like a charm. :-D
zehkaiser said:
Thanks. I couldn't get my system to recognize the phone while in recovery. I ended up mounting the system while the phone was in Media Sync Mode, issuing the "stop" command, replacing the files and rebooting. Worked like a charm. :-D
Click to expand...
Click to collapse
That sounds easier. I am no ADB wizard. Could you type it out for me?
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
etc.
Or whatever commands you issued?
Thanks.
It's much easier to use Android Terminal Emulator on the phone instead of the cable/ADB method.
dave8311 said:
It's much easier to use Android Terminal Emulator on the phone instead of the cable/ADB method.
Click to expand...
Click to collapse
A couple of things...
1. This is in no way meant as a "come back". Just my view.
2. Whether it is easier to use terminal or not - I still need the commands.
3. And for me it is easier to use a full size key board. The USB cable is less of a hassle to me then the mini touch screen keyboard.
Again- that's just me.
I download the OTA and the phone resets. When I get the Android updating screen, it dies on 20%... then reboots and tells me the update failed. anyone know why it's failing to update? I did freeze some apps from titanium backup.
ImYoungxD said:
I download the OTA and the phone resets. When I get the Android updating screen, it dies on 20%... then reboots and tells me the update failed. anyone know why it's failing to update? I did freeze some apps from titanium backup.
Click to expand...
Click to collapse
That is probably why. I'd recommend doing a factory reset in recovery.
ImYoungxD said:
I download the OTA and the phone resets. When I get the Android updating screen, it dies on 20%... then reboots and tells me the update failed. anyone know why it's failing to update? I did freeze some apps from titanium backup.
Click to expand...
Click to collapse
If you're running titanium then that means you're rooted, right? If you're rooted you should NOT (ie. Never) take a factory ota update. It has the potential to brick your phone.
What ota was it?
Sent from a SYNERGIZED GalaxySIII
Thats your device telling you to stay way the hell away from OTA's and revert to the dev section for your flashing needs!
I usually update my rooted transformer infinity OTAs with no problems.
Never knew rooted S3 can't update OTAs. meh.
I don't feel like flashing the phone because backing up the IMEI looks like such a pain ... Looks like I will have to look over it again.
ImYoungxD said:
I usually update my rooted transformer infinity OTAs with no problems.
Never knew rooted S3 can't update OTAs. meh.
I don't feel like unlocking the phone because backing up the IMEI looks like such a pain ... Looks like I will have to look over it again.
Click to expand...
Click to collapse
all you do is open terminal emulator, grant super user access, and type "NV Backup". I almost busted out in sweat the task was so strenuous.
droidstyle said:
all you do is open terminal emulator, grant super user access, and type "NV Backup". I almost busted out in sweat the task was so strenuous.
Click to expand...
Click to collapse
I have to start from scratch. I don't have ABD or whatever that thing was called. I'm going to try it out again some other day.
ImYoungxD said:
I have to start from scratch. I don't have ABD or whatever that thing was called. I'm going to try it out again some other day.
Click to expand...
Click to collapse
terminal is a app you download from the playstore... all you need is root access to use it.
droidstyle said:
terminal is a app you download from the playstore... all you need is root access to use it.
Click to expand...
Click to collapse
It's that simple...? never knew i can download it from the play store...
What is this whole site for? http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
read this thread
http://forum.xda-developers.com/showthread.php?t=1852255
I got that link in step 1.
"1. If your phone does not have Terminal Emulator installed, you will need to use ADB. Download and install the Android SDK platform-tools for your platform. This is a bit non-trivial as it requires the installation of the Android SDK, however, you can find a guide for installing adb here. After installing, open a command prompt and navigate to the "platform-tools" folder within the SDK, where adb is stored. If you need additional help on this, simply ask in this thread."
That site with the guide to install adb has terrible instructions so I gave up.
ImYoungxD said:
I got that link in step 1.
"1. If your phone does not have Terminal Emulator installed, you will need to use ADB. Download and install the Android SDK platform-tools for your platform. This is a bit non-trivial as it requires the installation of the Android SDK, however, you can find a guide for installing adb here. After installing, open a command prompt and navigate to the "platform-tools" folder within the SDK, where adb is stored. If you need additional help on this, simply ask in this thread."
That site with the guide to install adb has terrible instructions so I gave up.
Click to expand...
Click to collapse
Dude you are making this way too difficult lol...install terminal emulator from the playstore and run the nv backup command...then never worry about losing imei again.
For Terminal Emulator: The actual "beef" of the command is the "reboot nvbackup" line. Therefore, if you have Terminal Emulator installed, you can just run the command straight off your phone. Enter these two commands from the app:
Code:
su
reboot nvbackup
I had the same problem. Ended up using odin to push the latest stock software which included the update. Now to see if I still get the no sim error. Realizing after all this time I really didn't need to root.
ImYoungxD said:
I did freeze some apps from titanium backup.
Click to expand...
Click to collapse
This is without a doubt the reason the update failed (unless there are multiple reasons). If you unfreeze the apps, it should install as expected.
apacseven said:
This is without a doubt the reason the update failed (unless there are multiple reasons). If you unfreeze the apps, it should install as expected.
Click to expand...
Click to collapse
I had zero apps frozen and was unable to install the update. Pushing it via Odin was the only thing that worked for me.
mdt73 said:
I had zero apps frozen and was unable to install the update. Pushing it via Odin was the only thing that worked for me.
Click to expand...
Click to collapse
Yes it isnt the only thing that can cause an update to fail. But since he already stated that he had frozen some apps, then it is known that the check will fail and the update wont proceed.
If you don't know why it failed. download to OTA. And when it prompts you to install, say you'll do it later. Now extract the update file from your /cache/ directory. (That's where it was on Motorola's, I think its /cache/fota/ on our S3 ). Copy/move that file to the root of your SD card. Reboot into stock recovery and flash it. Watch the update when it fails it will call out specifically what went wrong. When you let the system automatically do it you don't get that luxury. If you initiate the update on your own through stock recovery though, you are granted that key piece of Intel as to what it didn't like.
Freezing anything in titanium will fail an OTA automatically. It checks system files to make sure certain ones are there, especially bloatware. Also having custom recovery will fail you.
As was said if your rooted you should never both with OTA anymore. If you're coming from a motorola like I did it is hard to grasp that at first. We needed official OTA to update the kernel. So you almost had to do it. Now though. We have an unlocked bootloader here. You can flash any kernel you feel. So OTA are meaningless for us on the S3. The devs steal all the good code and bits and put it in their ROMs and leave out the garbage. No reason to need official OTA anymore then unless you truly want to
Sent from a GlaDos Baked Potato
droidstyle said:
Dude you are making this way too difficult lol...install terminal emulator from the playstore and run the nv backup command...then never worry about losing imei again.
For Terminal Emulator: The actual "beef" of the command is the "reboot nvbackup" line. Therefore, if you have Terminal Emulator installed, you can just run the command straight off your phone. Enter these two commands from the app:
Code:
su
reboot nvbackup
Click to expand...
Click to collapse
Seriously..... That was easy lol. What's the point of step 1
Since I never read the next lines that says " If your phone is rooted and has Terminal Emulator installed, you don't need to do any of this. Simply open up the Terminal Emulator and go to step 2.", I never completed backing up the IMEI probably because I didn't know the Terminal Emulator was an playstore app.... Now I got a backup, I'm unlocked, running a custom rom. Thanks a lot man. You helped a lot.
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thanks
FNM
ImYoungxD said:
Seriously..... That was easy lol. What's the point of step 1
Since I never read the next lines that says " If your phone is rooted and has Terminal Emulator installed, you don't need to do any of this. Simply open up the Terminal Emulator and go to step 2.", I never completed backing up the IMEI probably because I didn't know the Terminal Emulator was an playstore app.... Now I got a backup, I'm unlocked, running a custom rom. Thanks a lot man. You helped a lot.
Click to expand...
Click to collapse
No prblem sir, glad to help!