I'm in the US and just purchased one. Any idea how to identify?
pull the system and check the build.prop thats what i had to do? and ended up with the orange one!
Drizzy Drake Rogers said:
pull the system and check the build.prop thats what i had to do? and ended up with the orange one!
Click to expand...
Click to collapse
Kernel: 2.6.27
Build: 1.76.405.6
Can anyone help me? lol
Where is the build.prop file? Can we access it using a file manager (astro) or does it have to be done through ADB?
If ADB only, could someone please provide directions?
Breakthecycle2 said:
Can anyone help me? lol
Click to expand...
Click to collapse
What exactly are you trying to find out here? If it's an operator branded Hero, it will have... operator branding!
Regards,
Dave
foxmeister said:
What exactly are you trying to find out here? If it's an operator branded Hero, it will have... operator branding!
Regards,
Dave
Click to expand...
Click to collapse
Ahhh...mine isn't branded. Just says HTC
Actually, looking at the Orange website, it appears that Orange haven't applied any physical branding to the phone, whereas my T-Mobile unit has a T-Mobile logo on it.
What colour is your Hero? AFAIK, all Orange UK ones are graphite.
Regards,
Dave
rvashi said:
Where is the build.prop file? Can we access it using a file manager (astro) or does it have to be done through ADB?
If ADB only, could someone please provide directions?
Click to expand...
Click to collapse
ADB way:
> adb shell
# more /system/build.prop
Click to expand...
Click to collapse
cheers
Thanks for the instructions through ADB. Before I try that, I thought I'd give it a shot from Astro File Manager and it worked and I found the build.prop in the System folder.
Confusing though... Mine says its out of 'Rogers' and I know Rogers doesn't have the Hero. I wonder if Paul (Modaco) is using it on Rogers and since I have his ROM on my Hero, that's what it says...true?
rvashi said:
Thanks for the instructions through ADB. Before I try that, I thought I'd give it a shot from Astro File Manager and it worked and I found the build.prop in the System folder.
Confusing though... Mine says its out of 'Rogers' and I know Rogers doesn't have the Hero. I wonder if Paul (Modaco) is using it on Rogers and since I have his ROM on my Hero, that's what it says...true?
Click to expand...
Click to collapse
Yep I'd agree with your synopsis I too have used modaco's update and my build.prop also has rogers in it however it is in a commented out part of the text so will not cause us any problems so don't worry about it.
I am grateful to modaco for producing this rom as it a a hell of a lot better that the rom that the hero came with!!
suppose if you want the original build.prop you could take a nandroid backup, then restore your backup from before installing modaco's rom (that you should have taken) check then restore back to the first nandroid backup.
Then again are we trying to identify the hardware, if so I'm not sure the hero comes in different flavours (yet) apart from the sprint one which seems to quite different but still may have the same hardware.
Related
well~~~ i m about to flash the splash screen following with the instruction by charnsingh_online http://forum.xda-developers.com/showthread.php?t=555114
can i get it a backup for memorialize or maybe sometimes i wanna flash it back
ths~~~
some problem，waiting for answering
cadetnudt said:
some problem，waiting for answering
Click to expand...
Click to collapse
Well it's been almost 6 months and no one has answered.....and I'm not flashing squat until I have a backup of the original. If I want to sell the phone on it must look like the store-bought item it was when I acquired it.
linuxluver said:
Well it's been almost 6 months and no one has answered.....and I'm not flashing squat until I have a backup of the original. If I want to sell the phone on it must look like the store-bought item it was when I acquired it.
Click to expand...
Click to collapse
and you want which image? the Vodafone or HTC one?
The HTC one can be found here. Cannot help for the vodafone one.
to install : fastboot flash splash1 splash1_HTC_Magic.nb0
do a nandroid
charnsingh_online said:
do a nandroid
Click to expand...
Click to collapse
and this would help how?
Why bring back such an old thread. But yeah, nandroid would not help in this situation.
KAwAtA said:
Why bring back such an old thread.
Click to expand...
Click to collapse
Because I've looked hard and long, and still haven't found an answer.
Try this
there's various splash screens linked here including the original Vodafone one, along with info on how to install them
I suggest downloading it and keeping it as your 'backup'
if you are looking for splash screens, I just uploaded my first efforts today, have a look! http://forum.xda-developers.com/showthread.php?t=663712
Cheers
rfcvb72 said:
there's various splash screens linked here including the original Vodafone one, along with info on how to install them
I suggest downloading it and keeping it as your 'backup'
Cheers
Click to expand...
Click to collapse
I know that site and it is not a solution for me, the splash image my phone came with is not there.
Anyway, I don't care much anymore cause I overwrote my original splash1 anyway, but I'm still somewhat curious whether there's any way to do it.
you could just make one, can you find the components on the net?
my vodafone one was just a logo on a bright red background so not exactly testing ;-)
Sent from my T-Mobile myTouch 3G using the XDA mobile application powered by Tapatalk
My Motorola defy finally arrived by mail today, but unfortunately the market app isn't included and there is no way I can ship it back. If I install another rom will the market app work?
Thanks,
Yup for sure.
Or give this apk a shot...
http://m.cfa.aero/misc/Vending.zip
Where are you located? If you search around you'll find phones designed for the UAE often come w/o market as it's apparently not allowed. Also, most (if not all) who have this issue find they cannot add market. Perhaps rooting will make it work.
Also of note, some people who have ordered their phones over the internet have gotten "Saudi" phones even if they are not in that market. And, apparently, the manufacturers sometimes will not support the phone.
fritolays said:
Yup for sure.
Or give this apk a shot...
http://m.cfa.aero/misc/Vending.zip
Click to expand...
Click to collapse
It gave a 403 permission denied , is it included in the update.zip in mirror?
scrannel said:
Where are you located? If you search around you'll find phones designed for the UAE often come w/o market as it's apparently not allowed. Also, most (if not all) who have this issue find they cannot add market. Perhaps rooting will make it work.
Also of note, some people who have ordered their phones over the internet have gotten "Saudi" phones even if they are not in that market. And, apparently, the manufacturers sometimes will not support the phone.
Click to expand...
Click to collapse
I ordered it from the internet and I think its from the gulf region because of the arabic manual. I wanted to ask If I flashed another rom will it work and which rom should I flash ,that is stable and fast.
and now to flashing I just start the phone while pressing up volume and ON. Then connect to my pc, start RSD lite and flash the rom?
confusedfella said:
It gave a 403 permission denied , is it included in the update.zip in mirror?
Click to expand...
Click to collapse
Heh oops, fixed now. No its not in the update.zip.
fritolays said:
Heh oops, fixed now. No its not in the update.zip.
Click to expand...
Click to collapse
It gave a Parse error.
Thanks, I'll try flashing the 3.4.3-11-stock uk tmobile If I flash it theres no way going back right?
confusedfella said:
It gave a Parse error.
Thanks, I'll try flashing the 3.4.3-11-stock uk tmobile If I flash it theres no way going back right?
Click to expand...
Click to collapse
What version are you on now ?
If your on 2.34.1 CEE or less you can use a downgradable method.
fritolays said:
What version are you on now ?
If you're on 2.34.1 CEE or less you can use a downgradable method.
Click to expand...
Click to collapse
It's moto_version.2.54.0.mb525.retail.en.ME1.
confusedfella said:
It's moto_version.2.54.0.mb525.retail.en.ME1.
Click to expand...
Click to collapse
Then no, it would be a one way trip. I would make a backup of your current rom beforehand but thats all you can do.
Maybe try higgys way but I donno.
fritolays said:
Then no, it would be a one way trip. I would make a backup of your current rom beforehand but thats all you can do.
Maybe try higgys way but I donno.
Click to expand...
Click to collapse
Thanks for the help buddy, a few last questions, to booting into clockwork recovery is vol down and Power button right? and is flashing between other 2.2 roms possible? like the US one or indian one.
Anyone know how we can change this text? XML location?
This rom gives you the option to personalize the carrier text AOKP V9
Sent from my Galaxy Nexus using Tapatalk
Push spn-conf.xml to /system/etc
http://www.multiupload.com/Y2NEG07OI8
Edit it before you do. You need to change number 262 (=Germany) to the number for your country and the following 01 (= T-Mobile) to the number for your network.
At the end of the line you can enter the text you want to appear. Push it and reboot, enjoy
This works with EVERY Rom
Auf meinem Galaxy Nexus geschrieben
Tag, looking through the framework for this and other tweaks are on my lst for this weekend.
nachtschicht said:
Push spn-conf.xml to /system/etc
http://www.multiupload.com/Y2NEG07OI8
Edit it before you do. You need to change number 262 (=Germany) to the number for your country and the following 01 (= T-Mobile) to the number for your network.
At the end of the line you can enter the text you want to appear. Push it and reboot, enjoy
This works with EVERY Rom
Auf meinem Galaxy Nexus geschrieben
Click to expand...
Click to collapse
Anybody know the numbers for USA and Verizon?
BeADroid said:
Anybody know the numbers for USA and Verizon?
Click to expand...
Click to collapse
I'd like to know this too.
Just went into /system/etc with Root Explorer. Can't find the spn-conf.xml file anywhere (even did the search). Possibly different on the Verizon LTE SGN since the one from Germany is GSM...
http://forums.androidcentral.com/ve...d-removed-verizonwireless-lock-drop-down.html
here is a guide
SpinDisc said:
Just went into /system/etc with Root Explorer. Can't find the spn-conf.xml file anywhere (even did the search). Possibly different on the Verizon LTE SGN since the one from Germany is GSM...
Click to expand...
Click to collapse
That's OK, it won't be there. Just copy it there so it will be recognized
It doesn't have anything to do with GSM or LTE.
I just realized that you can start Market Enabler and it will tell you the correctly number
nachtschicht said:
That's OK, it won't be there. Just copy it there so it will be recognized
It doesn't have anything to do with GSM or LTE.
Click to expand...
Click to collapse
Thanks for the info! I'm still a newb. My family & friends think I'm a genius (rooted their D.Incredible, D2, Eris, etc). But none of it's possible without the knowledge on XDA. Still learning, and hoping to learn more. Thanks for the info on how to change the banner info, too!
If you want to customize/edit the banner I can confirm this method works 100% with the Gnex
http://d-h-o.us/home/?p=282
I have found the best way to flash it is to create an update.zip or to find file in the ROM you are using and flash it with the ROM. By doing this you lose no data, no need to restore any setting.
The method I posted on my site will nuke your account data (aka just sign into google again).
I have a VZW GNX.
The first method did not work, tried all the numbers I found for Verizon, unless I did something wrong, heh.
DHO's method, when I look for "64…Verizon Wireless" it's just "64...65..." on the Nexus.
So I'm assuming it's pulling the 'Verizon Wireless' information from something else. It would be nice to find that.
mrZoSo said:
I have a VZW GNX.
The first method did not work, tried all the numbers I found for Verizon, unless I did something wrong, heh.
DHO's method, when I look for "64…Verizon Wireless" it's just "64...65..." on the Nexus.
So I'm assuming it's pulling the 'Verizon Wireless' information from something else. It would be nice to find that.
Click to expand...
Click to collapse
I'll update my write up over the weekend as it is for the OG, but look for
HTML:
EriInfo......Verizon Wireless...64...65.
So in the Gnex it is immediately before 64
Can toss a link to market enabler
Sent from my Galaxy Nexus using xda premium
This is what's in the stock one now:
EriInfo...... Google ...64...65...
Nevermind that was a different one I had here, my bad.
I'm going to pull the one off the phone now.
mrZoSo said:
This is what's in the stock one now:
EriInfo...... Google ...64...65...
Click to expand...
Click to collapse
I am still running a stock 4.0.2 based ROM. When I look at some of the ASOP 4.0.3 that I am playing with, one has google, one has verizon. Changing whatever comes before ...64...65 will edit both the lock screen and the tag at the bottom of the notification bar.
CM9 based ROMs seemed to have moved this value to a different file. It would take some digging to determine where they move it to.
DHO said:
If you want to customize/edit the banner I can confirm this method works 100% with the Gnex
http://d-h-o.us/home/?p=282
I have found the best way to flash it is to create an update.zip or to find file in the ROM you are using and flash it with the ROM. By doing this you lose no data, no need to restore any setting.
The method I posted on my site will nuke your account data (aka just sign into google again).
Click to expand...
Click to collapse
Thanks for linking to your great write-up! I followed it (for the most part), and it works...until my screen shuts off (from no activity), and then it goes back to Verizon Wireless. I've tried it two different ways (I'm currently on Deoxed Stock ICL53F with APM & Softkeys):
1. I edited the eri.xml, repackaged it in the APM .zip (since I found that installing other framework-res.apk's broke the APM). Re-flashed the APM .zip, and the new banner "Galaxy Nexus" stuck until the screen shut off. Back on, and it's back to VW
2. I just repackaged the framework-res.apk, and took it out of the APM.zip. Placed it in the "sdcard" section, copied in Root Explorer, and pasted into /system/framework/. After a reboot, same this as #1.
So, how do I get it to stick? Does it have anything to do with the ROM I'm on? Or with APM? I feel like it should work, but something's just not sticking...ugh...
SpinDisc, I'm not sure. I think it may be a function of APM. I have been trying to replicate that bug and I cannot. What launcher are you using?
I cannot replicate it running a ROM compiled from Pete's 4.0.2 AOSP source and NOVA launcher. I will further explore this over the weekend.
This weekend I plan on testing/modding a few different 4.0.3 ROMs, if I find any nuances I will let you know.
If you're rooted, you can use Root Tools.
https://market.android.com/details?...51bGwsMSwxLDEsImNvbS5qcnVtbXkucm9vdHRvb2xzIl0.
Anyone have these yet by chance?
I am sure it is coming. I would like to get my hands on it also.
Would be nice to have as I've already screwed it up.
liquidblue1985 said:
Would be nice to have as I've already screwed it up.
Click to expand...
Click to collapse
did you flash the n7100 stock firmware?
JoJo2211 said:
did you flash the n7100 stock firmware?
Click to expand...
Click to collapse
Nope. Downloading that right now actually. The only issue I'm having is that it's not recognizing the baseband.
It would be nice to be able to flash the Tmobile modem.
gedster314 said:
It would be nice to be able to flash the Tmobile modem.
Click to expand...
Click to collapse
Yeah. I'm pretty much stuck at this point. I have a custom recovery installed, root and on an international rom but I cannot get cell service. Wifi works, but that's about it.
I believe it has to do with the isis security.
Was thinking about going to TMO and getting a non-isis sim card to try.
liquidblue1985 said:
Yeah. I'm pretty much stuck at this point. I have a custom recovery installed, root and on an international rom but I cannot get cell service. Wifi works, but that's about it.
Click to expand...
Click to collapse
+1 I need the modem or a stock tar to odin asap, hope it drops soon...
The non-ISIS sim card did not change anything.
Looks like I need the stock rom also.
:/
luser01 said:
I believe it has to do with the isis security.
Was thinking about going to TMO and getting a non-isis sim card to try.
Click to expand...
Click to collapse
If anyone can help out with getting a flashable radio for this it'd be greatly appreciated. I've looked around on how to extract the radio from the current version with no luck.
As far as the ROM, a user linked one here:
http://forum.xda-developers.com/showpost.php?p=33242968&postcount=67
I've restored that through custom recovery/nandroid and it works fine. But without the radio... I'm lost.
I get a MD5 mismatch when I try to restore it with nandroid.
Downloaded it twice. anyone else had luck?
liquidblue1985 said:
If anyone can help out with getting a flashable radio for this it'd be greatly appreciated. I've looked around on how to extract the radio from the current version with no luck.
As far as the ROM, a user linked one here:
http://forum.xda-developers.com/showpost.php?p=33242968&postcount=67
I've restored that through custom recovery/nandroid and it works fine. But without the radio... I'm lost.
Click to expand...
Click to collapse
luser01 said:
I get a MD5 mismatch when I try to restore it with nandroid.
Downloaded it twice. anyone else had luck?
Click to expand...
Click to collapse
Had the same thing. Best bet is to go into the md5 file with a text editor and just delete everything and save the file. Recopy the md5 file over and reflash. Not sure why it was causing this error because I even re-ran the md5's myself and they were the same.
Also, just got off the phone with Samsung, they pretty much said the phone is not in their system yet and they do not have access to the firmware at this point. Their suggestion was to go back to t-mobile and get an exchange unit.
I will try that..
I called Samsung last night and they gave me the same run around.
liquidblue1985 said:
Had the same thing. Best bet is to go into the md5 file with a text editor and just delete everything and save the file. Recopy the md5 file over and reflash. Not sure why it was causing this error because I even re-ran the md5's myself and they were the same.
Also, just got off the phone with Samsung, they pretty much said the phone is not in their system yet and they do not have access to the firmware at this point. Their suggestion was to go back to t-mobile and get an exchange unit.
Click to expand...
Click to collapse
Just hoping now that maybe someone with enough knowledge sees this and can extract a flashable baseband... I'd really hate to go and buy another unit.
liquidblue1985 said:
Just hoping now that maybe someone with enough knowledge sees this and can extract a flashable baseband... I'd really hate to go and buy another unit.
Click to expand...
Click to collapse
You should find a store with one on the shelf, and not much supervision... and root it/extract a nand image hehehe. Though that would mean you would have be able to do all that and I have no idea how to extract a baseband image that is the power of the xda dev gods!
How hard is it to extract a baseband image?
Could someone that has one do it easily?
MikeBrWade said:
You should find a store with one on the shelf, and not much supervision... and root it/extract a nand image hehehe. Though that would mean you would have be able to do all that and I have no idea how to extract a baseband image that is the power of the xda dev gods!
Click to expand...
Click to collapse
I'm not sure if this is what you're looking for in particular buuut...
http://forum.xda-developers.com/showthread.php?t=1954597
It was (and still is) posted on the N7100 dev forum. It's the T-Mobile boot.img in tar format. Read through the thread for more info.
That is for people that messed up the rooting.
I flashed a full ITL rom that had the modem in it.
All I need is the modem and I am good to go.
/Waits
anoneemooz said:
I'm not sure if this is what you're looking for in particular buuut...
http://forum.xda-developers.com/showthread.php?t=1954597
It was (and still is) posted on the N7100 dev forum. It's the T-Mobile boot.img in tar format. Read through the thread for more info.
Click to expand...
Click to collapse
luser01 said:
That is for people that messed up the rooting.
I flashed a full ITL rom that had the modem in it.
All I need is the modem and I am good to go.
/Waits
Click to expand...
Click to collapse
Oh so wait. You're using a T-Mobile Note 2 and managed to flash an international ROM with everything working and functional (except for signal/sms/data/call) ? No reboots?
I ask because I've been wanting to somehow "convert" my T-Mobile Note 2 to an international Note 2 (as in, be able to flash the updates the international version gets instead of waiting on T-Mobile). I'm not US based so I don't need it to work with T-Mobile SIM anyhow...
i've read there is a way to sideload the OTA updates. Can anyone provide provide the OTA files? someone who hasn't updated yet and the ota is available for download for them? anyone? help lol.
Can someone reply? or just inform if it is indeed impossible or difficult? can't someone do a clean system dump so it could be flashed? there are many of us using this at&t devices overseas. help would be greatly appreciated. thanks!!
flyhotstuff said:
Can someone reply? or just inform if it is indeed impossible or difficult? can't someone do a clean system dump so it could be flashed? there are many of us using this at&t devices overseas. help would be greatly appreciated. thanks!!
Click to expand...
Click to collapse
Not sure if impossible, but as far as I know you need root to capture and pull the OTA.
Well that quickly puts a damper on my plans with this phone. Should just sell it and get a t mobile or international version. Thanks!!
flyhotstuff said:
Well that quickly puts a damper on my plans with this phone. Should just sell it and get a t mobile or international version. Thanks!!
Click to expand...
Click to collapse
The update should be in /cache. Someone who has downloaded the update but has not applied it yet should be able to retrieve it using a root explorer app. One would not need root privileges to copy from that directory. You just have to catch it before it is applied.
Good luck
Can anybody here do that for us please? I'm at the point where I would even paypal someone to do it lol.
Surely if that is the case somebody with an AT&T Note 5 would just have to flash stock firmware then search for the update and then upload it?
Unfortunately no one with an AT&T note 5 has root access to pull the OTA.
Codenameredneck mentioned that root wasn't needed in order to copy from the folder, I assumed that would mean it is locked down when trying to write to cache.
Any help would be appreciated.
It has been a few years since I have had to do it that way so there is a chance I do not remember correctly. It is possible you do need root to see that file. I know you can open the cache folder without root and I know once you apply the update it gets deleted from the cache folder.
You can see the cache folder, but can't copy or pull the OTA file from it without root as you don't have read/write access.
flyhotstuff said:
Can someone reply? or just inform if it is indeed impossible or difficult? can't someone do a clean system dump so it could be flashed? there are many of us using this at&t devices overseas. help would be greatly appreciated. thanks!!
Click to expand...
Click to collapse
What build are you in search of? Are you looking for LMY47X.N920W8VLU1AOGB?
pwnurlife said:
What build are you in search of? Are you looking for LMY47X.N920W8VLU1AOGB?
Click to expand...
Click to collapse
I have the day one build so anything past that is a blessing.
flyhotstuff said:
I have the day one build so anything past that is a blessing.
Click to expand...
Click to collapse
Can you provide me your baseband/build number?
pwnurlife said:
Can you provide me your baseband/build number?
Click to expand...
Click to collapse
baseband # is n920AUCU1AOGG
build # is LM47.N920AUCU1AOGG
flyhotstuff said:
baseband # is n920AUCU1AOGG
build # is LM47.N920AUCU1AOGG
Click to expand...
Click to collapse
Well I got stopped right in my tracks. Sorry, but I tried my best to help. The AT&T variant has decided to be more difficult than expected. I would either sell the device and get a different variant, or pursue the warranty options. Warranty might be a great option anyway considering you haven't gained root and shouldn't be damaged.
Good luck to you!