Related
Can anyone tell me what I am doing wrong...
I am trying to push an apn list to my magic 32b (vodafone) and am using the following commands
adb devices
adb remount
adb push apns-conf.xml /system/etc
This is how i`ve seen to do it on these forums... and it pushes ok... but i never get any apns show up on my phone..
even after doing the reset to default thing.
What am i doing wrong?? does the file need to need to be somewhere else on the phone?? or called something different???
any help is appreciated
bump######
maybe try packaging it into an update.zip and updating it through recovery. that might work. some files wont let you just simply push stuff through.
you can try first to push it again through recovery. so reboot into recovery and try pushing it.
if dont work, try the update.zip method.
will try what you mentioned... but I have a feeling it wont work...
as cyanogenmod roms already have the file in them. Why does it not already show up some APNs if not mine.
Now trying again.
ok so tried pushing while in recovery mode, and no luck...
I have never put together an update.zip... so am wondering how i would go about it...
Does the zip need signing??? and how would i structure it to make certain the file goes to the right place??
Thanks for your help
Yep.. it needs to be signed.. I've re-searched this files to sign and they are a bit out there.. you may find some dead links, but there's always a good one.. But, tell me you, use a linux OS? Because what's out there is for linux, I don't even researched if there's something for windows!
i`m on windows :-(
wud luv to make the change to linux, but dont know enuf... and like my gaming to much!!
Cud anyone on a linux machine possibly put together an update.zip for me??
search in the dream's theme forum for stericson's easy auto sign app. works for windows.
I always push my apns-conf that way.
Just one thing: do you do it right after wiping, updating and rebooting? On the PIN screen at first boot, before the Android tutorial.
That's how I do it and it works fine for me.
RolSMcS said:
I always push my apns-conf that way.
Just one thing: do you do it right after wiping, updating and rebooting? On the PIN screen at first boot, before the Android tutorial.
That's how I do it and it works fine for me.
Click to expand...
Click to collapse
it wont work because the system doesnt read that file after first boot...apn list is loaded elsewhere in /data/data/
If ur going to do it that way u have wipe data after in recovery or delete the data/data/com.android.telephony watever folder and then reboot .....wiping data being easier
Sent from my EVO 4G using XDA App
I noticed earlier that m:zombie and m:vampire are not in the market. Any other programs that any of you have noticed are missing?
jlem26 said:
I noticed earlier that m:zombie and m:vampire are not in the market. Any other programs that any of you have noticed are missing?
Click to expand...
Click to collapse
it's because the ruu is signed with test keys, not the release keys, so not everything is showing up.
regaw_leinad said:
it's because the ruu is signed with test keys, not the release keys, so not everything is showing up.
Click to expand...
Click to collapse
That's what I figured but these are the only two apps I have seen missing so far. I was just wondering if anyone else came across more.
jlem26 said:
That's what I figured but these are the only two apps I have seen missing so far. I was just wondering if anyone else came across more.
Click to expand...
Click to collapse
Most of my purchased apps are gone, and they include Basketball, Toss It, Flight Control, and a few others..quite disappointed as I did the RUU install via the .exe file and so far, haven't found a way to undo it and go back to DamageControl 2.1...
spatel9114 said:
Most of my purchased apps are gone, and they include Basketball, Toss It, Flight Control, and a few others..quite disappointed as I did the RUU install via the .exe file and so far, haven't found a way to undo it and go back to DamageControl 2.1...
Click to expand...
Click to collapse
Not to laugh about this, but maybe if that RUU had been kept hidden in the bowles of someones computer that wouldn't have happened. This is what drama does....
Kcarpenter said:
Not to laugh about this, but maybe if that RUU had been kept hidden in the bowles of someones computer that wouldn't have happened. This is what drama does....
Click to expand...
Click to collapse
lol very,very true!
RUU has test-key. thats means no protected apps. You should have flashed one of the many roms based on this RUU(damage,fresh or darchlegend even though its based on the Legend RUU). There already set to go.
Anyway I can do that now?
Lol, not to sound like a jerk but we knew this. I started the thread because I was wondering if anyone else knew which programs were affected. The whole idea behind loading the RUU was to test it out. It would be great if everyone didn't come in here and tell us how we should have loaded a custom ROM. Most of us probably came from a custom ROM to this, like myself.
jlem26 said:
Lol, not to sound like a jerk but we knew this. I started the thread because I was wondering if anyone else knew which programs were affected. The whole idea behind loading the RUU was to test it out. It would be great if everyone didn't come in here and tell us how we should have loaded a custom ROM. Most of us probably came from a custom ROM to this, like myself.
Click to expand...
Click to collapse
Sorry, that was just your first post to the forum, and it had no implications that you knew how to do anything whatsoever. I was just going on what I read from your post. I was guessing you just joined and saw the RUU and flashed it. I am sorry.
regaw_leinad said:
Sorry, that was just your first post to the forum, and it had no implications that you knew how to do anything whatsoever. I was just going on what I read from your post. I was guessing you just joined and saw the RUU and flashed it. I am sorry.
Click to expand...
Click to collapse
Don't be sorry, I wasn't really aiming that at anyone in particular, I was just hoping to head off the thread turning into a point and laugh at the RUU users.
spatel9114 said:
Anyway I can do that now?
Click to expand...
Click to collapse
Manually push flash_image to /system/bin >> You have to give flash_image permissions with adb
Code:
adb shell chmod 0755 /system/bin/flash_image
>> Root and reflash recovery (use this guide, except substitute 1.6.2 instead of 1.5.2 recovery (or use whatever recovery you want)>> Then reboot into recovery and nandroid back to your original build. You can even nandroid back to Fresh 2.0d and you will retain your new PRI.
If you have never made a backup, then download whatever ROM you want to try and use flash from .zip in recovery to flash the new ROM.
I included flash_image if you need it to push. This is not a .zip file, but I had to add .zip to attach it here. Rename it without the .zip or push it by typing
Code:
adb push flash_image.zip /system/bin/flash_image
Well I modified the build.prop last night and now all the apps are showing up in the market.
jlem26 said:
Well I modified the build.prop last night and now all the apps are showing up in the market.
Click to expand...
Click to collapse
Wow, is this easily done? I'm missing root manager, but otherwise am liking the leak (minus sprint crap).
Also.notice quick boot isn't working, but I'm sure its fixable, I just haven't looked or may not have the experience to get it going.
MILH0U5E said:
Wow, is this easily done? I'm missing root manager, but otherwise am liking the leak (minus sprint crap).
Also.notice quick boot isn't working, but I'm sure its fixable, I just haven't looked or may not have the experience to get it going.
Click to expand...
Click to collapse
Yeah it is pretty easy, just need to get your build.prop, then in wordpad, if using windows use wordpad not notepad, just have to make a few changes. After that you clear the market cache. When I did this last night, none of the protected apps showed up, however this morning they all did. So for reason it may take a bit to work right but it did work. Just checked and root manager is showing in my market too.
I'll just post one I found online. If you adb push this to /system/ it should work.
Kcarpenter said:
Not to laugh about this, but maybe if that RUU had been kept hidden in the bowles of someones computer that wouldn't have happened. This is what drama does....
Click to expand...
Click to collapse
@Kcarpenter, maybe dont post inflammatory stuff like this and instead be helpful and we wont have drama?
@Jlem
Good to see you got it going. You should share your build.prop (or link to instructions) so others that may have made the early (and quite risky) install of the RUU could get it going. That would be a nice thing to do
Personally I think you're crazy for trying that RUU!!! hahaha ! I'm glad someone did, and I hope it all works out for you.
edit:And you did! good work
Kcarpenter said:
Not to laugh about this, but maybe if that RUU had been kept hidden in the bowles of someones computer that wouldn't have happened. This is what drama does....
Click to expand...
Click to collapse
+1 Truth.
I have a feeling many people will do this.
danknee said:
Manually push flash_image to /system/bin >> You have to give flash_image permissions with adb
Code:
adb shell chmod 0755 /system/bin/flash_image
>> Root and reflash recovery (use this guide, except substitute 1.6.2 instead of 1.5.2 recovery (or use whatever recovery you want)>> Then reboot into recovery and nandroid back to your original build. You can even nandroid back to Fresh 2.0d and you will retain your new PRI.
If you have never made a backup, then download whatever ROM you want to try and use flash from .zip in recovery to flash the new ROM.
I included flash_image if you need it to push. This is not a .zip file, but I had to add .zip to attach it here. Rename it without the .zip or push it by typing
Code:
adb push flash_image.zip /system/bin/flash_image
Click to expand...
Click to collapse
Alright, so when I go to do that, I get an error "Read-Only File System"..How can I make it read/write?
spatel9114 said:
Alright, so when I go to do that, I get an error "Read-Only File System"..How can I make it read/write?
Click to expand...
Click to collapse
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
jlem26 said:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
or adb remount first.
im trying to debrand the vodafone desire hd, its unlocked but the vodafone boot up and the pointless links are really annoying me,
is there anyway i can do this without having to lose any of my existing settings, i.e. contacts, calendar, gallery, etc. i just want this pointless sh#t off my phone
i believe i may need to root, but im not really sure how to do this, ive read up on a few methods but im not even sure how to access a terminal on the dhd, on the n900 it was all preloaded so if anyone could give me some quick info on this,
Sure
Make sure to read the guides in here first
http://forum.xda-developers.com/showthread.php?t=821220
Do this first
-Root and S-OFF your Desire HD the "easy" version!
Then this
-ClockworkMod recovery for HTC Desire HD
And after you've done all this you should be fine to install custom roms
ok im trying to make some sense of the link you posted
i tried deleting the com.vf and sz voda files from the system/app folder, but it says it cannot delete
mox123 said:
ok im trying to make some sense of the link you posted
i tried deleting the com.vf and sz voda files from the system/app folder, but it says it cannot delete
Click to expand...
Click to collapse
You can't delete anything from /system without perm root and s-off. With perm root only it will reappear when you reboot.
So you need to perm root with visionary, s-off, then you need to either flash an insecure boot.img or remount /system as read-write using either adb, terminal emulator or (the easy way) root explorer.
After all that you will be able to remove system files using either command line or root explorer app.
The easiest way to fix to de brand would be to use a stock ruu but you will have an empty phone after that.
Sent from my Desire HD by magic.
how do you enter recovery mode without update.zip? not too sure where to get this from
i suggest go to the app dev threads and read the stickies.
it should tell u basically the background.
u cant just jump in without knowing the background as to ..why you need s-off and why u need recovery..and why u need to have perm root..
yes i know..we want quick solutions..but for your benefit it will be better if u just read and start first by..doing small steps at a time
Hey i came from Galaxy S and rooting and flashing are so much different in that world is not funny!..
Hey guys, complete n00b here
I'm trying to root my htc desire z, and in the process I realised I have to downgrade.
adb, sdk... etc. etc. I'm very in the dark about a lot of this... I've trawled through page after page after page (mostly on this site) and I get lost for a lot of it. I'm only learning very basic stuff about cmd prompt now.
Can anyone help me through this? Maybe fire some questions at me to get the ball rolling? Any help at all is much appreciated.
Oh, and if this is posted in the wrong forum, please direct me otherwise
Cheers guys.
Further info
I'm running Android 2.3.3
I've been following this:
http://forum.xda-developers.com/showthread.php?t=905261
Although I've been using a different downgrade folder (replace "psneuter" with "fre3vo")
All the files are in a folder called "Downgrade", directly on my C drive...
I go into cmd prompt and type the following...
---------------------------------------------------------------------------------------------------
cd\Downgrade
adb push fre3vo /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/fre3vo
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/fre3vo
and then it gets stuck at
fre3vo by #teamwin
Please wait....
---------------------------------------------------------------------------------------------------
It used to continue on from that, and I'd type adb shell and get a # instead of a $, but I had the wrong .zip file on my SD card so the reboot thing didn't work properly.
Now that I'm certain I have the right .zip file on it, I'm stuck at this command prompt problem.... I'm very, very confused...
Ok, I've gotten past all those problems. But it just won't downgrade to older firmware for some reason. I get to the bootload, and it waits for a second, then comes up with a quick list (that I can't make out in time) but I'm fairly sure it's coming up with the .zip files and saying they're not images? Then it just reverts back to the bootloader screen.
Am I completely wasting my time based on the fact that it's 2.3.3?
Can you see the file extensions on your PC? A common mistake is to name the file zip.zip instead of just .zip at the end.
Here is a good downgrade guide for gingerbread.
Like ArmedandDangerous said, make sure your computer is not set to 'hide file extensions' (quick google search will tell you how to check/change).
If hboot still refuses to flash the PC10IMG.zip, come to #G2ROOT on freenode irc for help.
-Nipqer
Hey guys thanks for the replies! (likin the profile pic Nipqer )
Yeah I can see the file extensions and I'm fairly sure that I have the .zip file named perfectly. I'm not on my PC right now, but I'll have a "root" ( ) around when I am. I'm fairly certain I already gave that downgrade guide a bash though, but I'll try it once more. I'll post updates when I have them, thanks guys!
little more extensive on the rooting procedure if maybe your interested
http://techticians.com/index.php/mobile-tech/14-mobile-phones/27-rooting-the-t-mobile-g2
Is it possible to downgrade from 2.3.3 though? I've read in a lot of places that it can't be done?
Thanks for all your responses guys! I understand how irritating n00bs can be
No worries--we've all been newbs once
It IS in fact possible to downgrade then upgrade from stock 2.3.3 (I've actually done it; I've messed about with custom firmware back when I had a Samsung Omnia, but this was pretty much my "rooting deflowering" as far as Android phones went).
Here's how I did mine (this assumes you are running Windows and not MacOS X or Linux). I'm assuming you've backed up your apps first
a) Install Android SDK Tools (http://developer.android.com/sdk/index.html). I pretty much did the full install.
b) Install HTC Sync (I got it from http://www.htc.com/de/SupportViewNews.aspx?dl_id=1073&news_id=918 which is all in German but will still get you set up).
c) You will need to set paths correctly--in my case I had to click "Start", "Control Panel", "System", "Advanced", then click the button labeled "Environment Variables", then add in the "PATH" where the apps for ADB and (more important for our purposes) the platform-tools directory for ADB lives.
(There's actually a pretty good, in-depth guide at http://forum.xda-developers.com/showthread.php?t=879701 on how to do this, but I'm just posting the Cliff's Notes version here )
d) Set USB Debugging on with the phone. Connect phone to computer using stock cable, click "Start", "Run", then "cmd" to open a command window. Type "adb shell cat /dev/msm_rotator" in that command window, hit return--if it gives some error about invalid length, your phone is visible to ADB and you SHOULD in theory be ready to downgrade.
e) Download and unzip the files attached in the article on downgrading (http://forum.xda-developers.com/showthread.php?t=1178912) to the directory where "platform-tools" lives (usually something like C:\Program Files\Android\android-sdk-windows\platform-tools unless you installed it in a nonstandard location) and then in the command window type "cd C:\Program Files\Android\android-sdk-windows\platform-tools" (without quotes, and change that last bit to the actual directory if you installed it in a nonstandard location).
f) From there, follow the downgrade guide--if it hiccups, go on IRC to #G2Root and ask for help. (I didn't have any hiccups with this guide.) All the commands will be typed in that command window I mentioned. (Oh yes, you'll be getting intimately familiar with a command line and command window with this.)
g) Confirm (once the phone boots up after you re-flashed the ROM) that it is running 2.2.
h) Follow the guide on how to root a stock Froyo phone (http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision)--you won't have to worry about psneuter or any of that, because you've already done that (with fre3vo rather than psneuter).
i) Once you've confirmed it's rooted (according to that guide), then (assuming you're upgrading to 2.3.4 rooted or CM7 or whatnot) install the latest radio for the T-Mobile G2 (yes, you want to do this before ever messing with putting on a new ROM, otherwise you are going to find that stuff will go sideways). Get the latest T-Mobile G2 radio (http://www.mediafire.com/?vumdi3gges6ia4o), rename it to PC10IMG.zip, and follow this guide (http://forum.xda-developers.com/showthread.php?t=970809&highlight=install+radio).
j) Install the particular rooted ROM you want to use. (I ended up just using a rooted version of stock in this thread: http://forum.xda-developers.com/showthread.php?t=1202498).
And--barring a hiccup with the phone--voila, root.
This is pretty much what worked for me--can't guarantee it'll work for others. (Probably the scariest part to me was the radio update, but even this actually was relatively painless.)
I could KISS you guys!!!!
I ended up just going with the guide that Tbbo514 linked, and after a few hiccups, it works like a charm. I'm now rooted, gonna go search for a ROM so exciting.
Once again, you guys are legends! Thanks so much!
philbagg said:
I could KISS you guys!!!!
I ended up just going with the guide that Tbbo514 linked, and after a few hiccups, it works like a charm. I'm now rooted, gonna go search for a ROM so exciting.
Once again, you guys are legends! Thanks so much!
Click to expand...
Click to collapse
no problem at all dude i wrote the article because i wanted people to have exact details it makes it easier when you dont have to research anything
Tbbo514 said:
little more extensive on the rooting procedure if maybe your interested
Click to expand...
Click to collapse
Thank you so much! Took me a while since I just rooted my phone for the very first time, time to install a ROM! <3
corrupted23 said:
Thank you so much! Took me a while since I just rooted my phone for the very first time, time to install a ROM! <3
Click to expand...
Click to collapse
no problem just trying to make things a little easier
I have downgraded no probs, just having problems getting S-OFF with stock froyo 2.2 with temp root.
slufoot69 said:
I have downgraded no probs, just having problems getting S-OFF with stock froyo 2.2 with temp root.
Click to expand...
Click to collapse
which methods have you attempted to turn S-off
Well I finally figured out the S-OFF issue now im stuck on the last step to perm root my 2.3.4 GingerBread. Here is where Im stuck now.
http://forum.xda-developers.com/showthread.php?t=1228515
thanks...
Sean...
slufoot69 said:
Well I finally figured out the S-OFF issue now im stuck on the last step to perm root my 2.3.4 GingerBread. Here is where Im stuck now.
http://forum.xda-developers.com/showthread.php?t=1228515
thanks...
Sean...
Click to expand...
Click to collapse
should have just posted it here lol..this may sound stupid to say lol but are you hitting the power button or the optical pad button..if you hit power i noticed sometimes it would show the gear with the hat on..try selecting with the optical button instead
Just to clear from start: My phone is NOT rooted
I'm on a stock rom
I don't want to void my warranty
i have E610
Ok now lets begin....I want to change my boot animation with a custom one but i don't have a rooted phone but i found that tutorial(and other similars this is the best)
HERE---> http://forum.xda-developers.com/showthread.php?t=1580642 but i'm afraid in case something goes wrong like the phone not being compatible with the dir (/data/local) that he suggests and in result not booting at all...Or other things that may not go well...But lets be optimists :fingers-crossed:
Oh i forgot i have install SDK (so i have adb ready)
i tested adb and it's work (as far as being recognized by cmd)
So guys can someone advice me to try or not to try ? be sure before answering because i don't want to harm my phone
sorry for my english...
biluris said:
Just to clear from start: My phone is NOT rooted
I'm on a stock rom
I don't want to void my warranty
i have E610
Ok now lets begin....I want to change my boot animation with a custom one but i don't have a rooted phone but i found that tutorial(and other similars this is the best)
HERE---> http://forum.xda-developers.com/showthread.php?t=1580642 but i'm afraid in case something goes wrong like the phone not being compatible with the dir (/data/local) that he suggests and in result not booting at all...Or other things that may not go well...But lets be optimists :fingers-crossed:
Oh i forgot i have install SDK (so i have adb ready)
i tested adb and it's work (as far as being recognized by cmd)
So guys can someone advice me to try or not to try ? be sure before answering because i don't want to harm my phone
sorry for my english...
Click to expand...
Click to collapse
see if you can push the zip with adb to /system/media/
if you can do that you're good
Sent from my LG-E400
checked
Angelcho said:
see if you can push the zip with adb to /system/media/
if you can do that you're good
Sent from my LG-E400
Click to expand...
Click to collapse
i checked this folder through my phone(i used Astro file manager) and there were 4 bootanimation but with different names so i think thats if i move my custom one there will be a confusion....
plz go to that folder so you can understand what i'm talking about..
There shoul be one simple zip - bootanimation.zip
BTW when you start your phone do the bootanimations shuffle or you get just one
UPDATE
I tried pushing though adb a bootanimation to /system/media but it told me "failed to copy" and thats "Read only file system"
So in conclusion i think i must be rooted to do these kind of stuff...
biluris said:
I tried pushing though adb a bootanimation to /system/media but it told me "failed to copy" and thats "Read only file system"
So in conclusion i think i must be rooted to do these kind of stuff...
Click to expand...
Click to collapse
I guess so...
Sent from my LG-E400 using Tapatalk 2
have you try to put onto /data/local/*...???
yayakuya said:
have you try to put onto /data/local/*...???
Click to expand...
Click to collapse
again Permision is not allowed
It doesn't let me even see whats inside that folder
biluris said:
again Permision is not allowed
It doesn't let me even see whats inside that folder
Click to expand...
Click to collapse
Geezz... mad for advice
calm down dude.... if you're using root explorer or simillar apps, ofcourse it won't show up... lol :laugh:
use adb to push that files into /data/local/*. it should be mounted as read-write by default ( thought )
i'm sorry if i wrong, i never use Un-Rooted Android devices for more than 3 hours, except my tablet for work ( it's never touched by adb thingy )...
i'm outta here................ good luck for ya