Hello,
My carrier (SFR France) doesn't recognize the One SV, because it's not in their database.
How can i make the carrier believe the phone is another phone, like a Desire 601?
Thanks,
Did you try to edit build.prop?
Thanks for the answer. i didn't think it was that easy. However i'm not ready to root my phone. (Warranty, risks etc...)
I've manage to open, read, copy to SD card and modify with text editor, but how can i push it back (and not loose modifications after reboot)
(adb, something else? )
anyway. I've check the build.prop and found i need to change the ro.product.model= xxx
Now i just need to push it back. Could ADB or Fastboot do it ?
Any idea on how device identification works when it's not an android phone ?
Regards,
Well I never try to use adb without root, but I think without root you can't edit system files. Fastboot will not work. You need root or costume recovery.
Ivory_75 said:
Thanks for the answer. i didn't think it was that easy. However i'm not ready to root my phone. (Warranty, risks etc...)
I've manage to open, read, copy to SD card and modify with text editor, but how can i push it back (and not loose modifications after reboot)
(adb, something else? )
anyway. I've check the build.prop and found i need to change the ro.product.model= xxx
Now i just need to push it back. Could ADB or Fastboot do it ?
Any idea on how device identification works when it's not an android phone ?
Regards,
Click to expand...
Click to collapse
Unless you unlock your bootloader and root then there is really nothing you can do to the build.prop file. Restrictions won't allow you to make changes.
Sent from my K2_CL using Tapatalk
Related
http://forum.xda-developers.com/archive/index.php/t-644769.html << I got my idea from there.
If you update the
Code:
/data/data/com.android.providers.settings/databases/settings.db
file so that "install_non_market_apps" = 1 instead of 0, you will be able to install non-market apps off of your sdcard or wherever.
This works for me at least, but you'll have to root first.
I ended up editing the file with the SQLite Manager firefox add-on.
But, since that took me a really long time, I'll just upload the edited settings.db for you. (don't forget to make the extention .db instead of .db.txt)
Now, as far as I know, this won't mess anything up... BUT, I'd feel a lot better if someone who knows more about Android would provide some feedback before anyone else tries this. [It works for me, but I'm not sure if any other user-specific settings are kept in that file that I don't know about!]
But, at least for me, I no longer need to use adb to install apks that aren't from the Android Market.
I hope this is useful to someone...
EDIT::
You will lose your settings if you use the attached settings.db.txt file. Your best bet is to pull the file off your phone, edit it with something that understands sqlite3's database format, and then push it back. It's just better that way.
Further EDIT:: As someone pointed out later in this thread, this file unbeknownst to me when I shared it, actually has a unique ID by which phones can be identified on the android market, etc. While this isn't a huge deal, it can lead to some rather strange behavior... my phone for example has started attempting to download apps from the android market all by itself.
So--- if you want to side-load apps, change the variable in the database like I explained above.
Sorry, completely new to android but where would you put this file so it would allow side-loading?
You'd have to replace
Code:
/data/data/com.android.providers.settings/databases/settings.db
with it. You'll have to have your phone rooted first though. Then you'll have to transfer the file to your phone with adb, and you'll then copy it over the existing settings.db file.
Honestly, it might not even be worth the trouble now that attn1 is just doing the whole ROMs.
But make sure you take off the .txt.
This works. Thanks.
For some reason, i'm getting a permissons error regardless that i successfuly rooted my phone...o_o
justince said:
For some reason, i'm getting a permissons error regardless that i successfuly rooted my phone...o_o
Click to expand...
Click to collapse
did you boot the phone and do adb remount with debugging enabled?
USB debugging? Yeah.
What i did was i used the other method to sideload root explorer, took the settings.db.txt, deleted the .txt part and replaced it via root explorer, and now i can sideload whenever...however, when i try to delete any of the att bloatware, its read only o_o fawking att
Can anyone confirm any other way to remove bloatware without flashing the rom?
justince said:
USB debugging? Yeah.
What i did was i used the other method to sideload root explorer, took the settings.db.txt, deleted the .txt part and replaced it via root explorer, and now i can sideload whenever...however, when i try to delete any of the att bloatware, its read only o_o fawking att
Can anyone confirm any other way to remove bloatware without flashing the rom?
Click to expand...
Click to collapse
That's why made the ROM without all that -er- stuff.
attn1 said:
That's why made the ROM without all that -er- stuff.
Click to expand...
Click to collapse
Attn's Rom is ****ing great. many thanks btw
a little help please
a bit confused..
how do i type in this code "/data/data/com.android.providers.settings/databases/settings.db"?
adb /data/data/com.android.providers.settings/databases/settings.db
or something else because that doesnt work.
fluffyarmada said:
I'm not sure if any other user-specific settings are kept in that file that I don't know about!
Click to expand...
Click to collapse
The only issue I see (as an Android newcomer, but with a development background) is that the settings.db contains an android_id that is supposed to be unique (it gets generated when you boot the phone the first time after a reset). So anyone installing your settings.db is going to have the same ID.
I'm sure it won't be an issue for most people but I wonder if there'd be a collision in any apps that are designed to communicate between Android devices? For this reason I'll be tweaking my own settings.db once the phone arrives later today.
Big thanks for posting this though!
Thanks for that, I honestly had no idea. I'm very new to Android. And this was a kludge.
fluffyarmada said:
http://forum.xda-developers.com/archive/index.php/t-644769.html << I got my idea from there.
If you update the
Code:
/data/data/com.android.providers.settings/databases/settings.db
file so that "install_non_market_apps" = 1 instead of 0, you will be able to install non-market apps off of your sdcard or wherever.
This works for me at least, but you'll have to root first.
I ended up editing the file with the SQLite Manager firefox add-on.
But, since that took me a really long time, I'll just upload the edited settings.db for you. (don't forget to make the extention .db instead of .db.txt)
Now, as far as I know, this won't mess anything up... BUT, I'd feel a lot better if someone who knows more about Android would provide some feedback before anyone else tries this. [It works for me, but I'm not sure if any other user-specific settings are kept in that file that I don't know about!]
But, at least for me, I no longer need to use adb to install apks that aren't from the Android Market.
I hope this is useful to someone...
EDIT::
You will lose your settings if you use the attached settings.db.txt file. Your best bet is to pull the file off your phone, edit it with something that understands sqlite3's database format, and then push it back. It's just better that way.
Further EDIT:: As someone pointed out later in this thread, this file unbeknownst to me when I shared it, actually has a unique ID by which phones can be identified on the android market, etc. While this isn't a huge deal, it can lead to some rather strange behavior... my phone for example has started attempting to download apps from the android market all by itself.
So--- if you want to side-load apps, change the variable in the database like I explained above.
Click to expand...
Click to collapse
NOTE: You MUST have root access in order for this to work
sqlite3 is included in the Android SDK tools, so this would be the best way:
COMMON
Enable USB debugging (settings > applications > development > USB Debugging)
adb remount
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
Linux/OS X
echo "update secure set value = 1 where name = 'install_non_market_apps';"|./sqlite3 settings.db
WINDOWS
echo update secure set value = 1 where name = 'install_non_market_apps';|sqlite3 settings.db
COMMON
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
Reboot phone and sideloading works. (thanks fluffyarmada)
I wonder if this might be why google voice fails to install properly for some...
Sent from my HTC Liberty using XDA App
Cobus said:
I wonder if this might be why google voice fails to install properly for some...
Sent from my HTC Liberty using XDA App
Click to expand...
Click to collapse
It is possible. The Google apps all use the android_id, afaik.
Although, I do remember I was never able to get the settings menu to setup the voicemail forwarding... I always had to use the weird GSM code. (The weird number with a bunch of * and # that you have to type in if you follow google's directions.)
judicious said:
a bit confused..
how do i type in this code "/data/data/com.android.providers.settings/databases/settings.db"?
adb /data/data/com.android.providers.settings/databases/settings.db
or something else because that doesnt work.
Click to expand...
Click to collapse
After you've rooted your phone, download the new settings.db into the same folder as where your adb program is. Then type:
adb push /data/data/com.android.providers.settings/databases/settings.db
in that folder while your phone is connect via usb.
I'm not sure if you have to restart your phone into recovery or not. Can someone check on this?
tiga2001 said:
After you've rooted your phone, download the new settings.db into the same folder as where your adb program is. Then type:
adb push /data/data/com.android.providers.settings/databases/settings.db
in that folder while your phone is connect via usb.
I'm not sure if you have to restart your phone into recovery or not. Can someone check on this?
Click to expand...
Click to collapse
Well, it's
Code:
$ adb push /path/to/file/on/computer/settings.db /path/to/file/on/phone/settings.db
So, if your settings.db is in your tools folder, then you can do
Code:
$ adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
what happen to the file download? i cant find it..
judicious said:
what happen to the file download? i cant find it..
Click to expand...
Click to collapse
Please follow the instructions posted by attn1 on reply number 13 to this thread.
I removed the settings.db, because it actually has a bunch of extra settings I didn't know about like a handset specific android_id variable... that caused me a bit of trouble...
But, follow the instructions on reply #13 on this thread, and you'll be able to fix it yourself.
Sorry for the inconvenience.
so if we already used the file, is there anyway to revert it back to default and then change the settings via the method outlined above? or.. if we failed to make a copy of our original settings.db file.. basically am i SOL?
EDIT: nevermind, just rebooted into Clockwork and wiped the phone.
UPDATE: I have reach the file through "adb pull", however, the adb shell still prevent me from reading that file. Strange, but my problem is solved. Thank you herbthehammer!
UPDATE: I have adb into NS, but it isn't a root shell. so still can't access that file.
Hi all, I have a problem here.
I have a stock 2.3.4 Nexus S. Now I need to copy a file from /data/data to my PC.
I can't even see this file unless I root my phone. But rooting means wipe all the data and then I'll lose that file forever.
So....How can I get this file?
Any suggestion?
Thank you for reviewing my question.
What file?
Sent from my Nexus S using XDA App
I don't know for sure, I'm just guessing. If you booted into the bootloader, couldn't you adb into the phone with root access? Then copy that way? I can't imagine what file would be sitting there that would be important enough to copy it. I think the sd card might get wiped in an unlock. Wasn't there a guide to root and recovery without unlock?
Rooting the phone doesn't wipe your data, unlocking the bootloader does.
Try adb commands as suggested above.
herbthehammer said:
I don't know for sure, I'm just guessing. If you booted into the bootloader, couldn't you adb into the phone with root access? Then copy that way? I can't imagine what file would be sitting there that would be important enough to copy it. I think the sd card might get wiped in an unlock. Wasn't there a guide to root and recovery without unlock?
Click to expand...
Click to collapse
Thank you for your reply!
It's a profile generated by an app. It seems only that app and the Android system can gain access to that file.
The guide to root and recovery without unlock? You mean this post? http://forum.xda-developers.com/showthread.php?t=931865
I think it only works for Android 2.3.3 and 2.3.2.
I'm interested in "adb into the phone with root access", just need some instructions.
As My desire is amoled and unbranded i don't know for sure if this tut gonna help Slcd/Branded desire user if some one with slcd or branded desire fix there brick by follow this tut please leave a comment Here.
*To work this Hole Thing Out You need to setup Adb and fastboot in your pc,if you don't know how to do it follow this nice Guide.
http://androidforums.com/desire-all-things-root/337356-faq-adb-fastboot-windows-updated-1st-june-2011-a.html
Last few days i saw lots of people having usb brick problem even after they flashed the Ruu.exe or PB99IMG.zip update via hboot that because misc.img is corrupted and they stuck on stock rom without any usb function.Few Days ago i was in the same situation and solved my problem thought i should share this Information with people who need help.
Note-If you usb bricked on s-off device then try this fastboot command to solve this
fastboot oem enableqxdm 0(unblock your sd-card)
fastboot oem eraseconfig(fix misc partition)
if above command don't work then you have to flash a ruu.exe or PB99IMG.zip file via hboot to return to stock
rom usally that fix the usb brick but some time that trick also fails,if that happen then you have to go through the process below.
If your device is branded then create a goldcard and flash a unbranded PB99IMG.ZIP cause maybe this not gonna work on branded device.
I solve my usb brick this way
after return to stock rom via PB99IMG.zip file flash via hboot(didn't fix my usb brick so i had to do the steps below)
1.i unlocked my sd card via fastboot command"fastboot oem enableqxdm 0" sd card recognized by phone and i can browse it via file explorer.
note-you can access your sdcard only via file explorer nothing else so after execute the command download a file explorer from android market.
2.then i copied the visionary+(it gave me temporary root access which is needed to work this whole thing out).
root explorer,terminal emulator apk and those usb bricked update file(image_flash,mtd0.img) to sdcard from pc via card reader and installed them.
before copy those update file on sd card i edited the mtd0.img to put correct cid n rom info via hex editor.
To find cid info
If you don't know your Cid then type this command in fastboot-fastboot oem boot this will show you info about your phone cid.when the info shows up look for‘INFOCID HTC___xxx'
To find The Rom version-Go to Settings>About phone>Software Information and note your Software Number.
3.after that i copied those update file in phone memory to copy file in phone memory you have to set permission for r/w.When open root explorer look at the top left corner you will see mount as r/o mount r/w tap on mount r/w that's it you set permission to read/write on your phone memory and copy the file in
/data/data/ folder and set permission for r/w and execute for those file via root explorer.
4.after that i simply typed this command in terminal emulator
"su
/data/data/flash_image misc /data/data/mtd0.img"
Rebooted my phone and voila usb brick is gone htc sync,usb tethering,sd card mount,charge everything is working and now i am rooted and s-off again
Note-you don't need the rageagainstthecage file which only need if you try to get root access via terminal emulator which is lengthy n complicated but with visionary+ you can get root access with 1 click and it's much easier than typing command in T.E.
If above information helps you to fix Your usb brick Please Leave a comment Here and you can also hit the Thanks button
Exiled_SouL said:
before copy those update file on sd card i edited the mtd0.img to put correct cid n rom info via hex editor.
Click to expand...
Click to collapse
how do you edited it? thx
edited it with hex editor software it included in the zip file
I know. but how exactly?
tma24 said:
I know. but how exactly?
Click to expand...
Click to collapse
when you open the mtd0 file with hex editor look for
"HTC_1xx"-your cid
"ClearAutoImage .x.xx.405.x"-your rom value
and edit those according to your cid and rom value information.
i updated the thread with some more useful info so recheck the 1st post.
Thank you very much. While my phone is fine but I'm trying to fix a friend
you welcome,if it work out please leave a reply here
of course
my translated your post in slovak forum
http://smartmobil.sk/forum/viewtopic.php?f=142&t=12610
thank you very much
Regards.
Exiled_SouL said:
you welcome,if it work out please leave a reply here
Click to expand...
Click to collapse
Yes, I fixed it!!! Thx man.
Congrats.thanks for confirming
You've made my day. You need a donate button. Thanks.
Hi, thank you very much for responding my thread, and thank's to you my desire is back to normal..., I have one question, Is it safe to use permanent root using Visionary+ ?
thank's
kebhoganteng said:
Hi, thank you very much for responding my thread, and thank's to you my desire is back to normal..., I have one question, Is it safe to use permanent root using Visionary+ ?
thank's
Click to expand...
Click to collapse
Glad that it worked out for you about V+ root,TBH i don't know but my opinion is it's safer to use unrevocked for root.
Marc. said:
I read it, but a few questions...
( My phone is S-ON )
1. I'm not on a stock rom, but on Insertcoin
2. I can already acces my SD card, so can I skip the first step? Done that yesterday already.
3. Can I use the mtd0.img generator? If yes I have already the file.
4. With step 3, which files must be in /data/data?
5. With step 2, I have super user, so can I use that instead of the root acces thing?
Click to expand...
Click to collapse
Quote from the other topic, maybe you read it here faster.
Edit, just tried it. I generated my mtd0.img out of another topic. Read a lot, and it works perfect again!! Thanks!! You saved my phone!
Exiled_SouL said:
Glad that it worked out for you about V+ root,TBH i don't know but my opinion is it's safer to use unrevocked for root.
Click to expand...
Click to collapse
Hi, again
I have a new problem after fixing the USB Brick. I can't root my desire using Unrevoked 3, it was always failed on process uninstalling unrevoked3 system and showed :
Validation error : Backup CID is Missing
do you have any idea for this problem?
thx for your respond
That same error showed up when i tried to root after usb brick but in my app drawer the super user icon showed that means it worked somehow even after the error,so check your app drawer and recovery if you see the su icon and cwm recovery then it worked don't worry about the error
Sent from my HTC Desire using XDA App
Hello,
Can I try this method on my Desire S (unrooted, s-on v2.3.5-sense3.0) ?
a great big thank you. I am very happy!
rakhan01 said:
Hello,
Can I try this method on my Desire S (unrooted, s-on v2.3.5-sense3.0) ?
Click to expand...
Click to collapse
Yes, if you want to brick your device by flashing a misc meant for another one..
Hello,
I'm Using a Rooted Starmobile Up has an MediaTek MT6582M
well, it started when i was changing the bootanimation of my phone with an marvelboot.zip using ES File Explorer, i forgot to set the permissions so after i restart it, my phone stucked at boot animation.
i copied the marvelboot.zip at the /Device > system > media folder as far as i can remember.
i think it will be solved if i am able to delete the bootanimation.zip from that media folder using computer or something else.
i am wondering how can i delete that file from the system folder, or perhaps change permission? and is there a way to browse the system folder from android to computer?? i just wonder if theres such, but i will go with your answers.
i have no CWM installed and i dont know how, i dont know ADB, or SDK and all
when i tried installing CWM from recovery menu, it says installation aborted and thats my only way.
can someone help me?
another thing is i forgot to backup the firmware, and ofcourse warranty is voided as it is rooted, i cannot get it's firmware anywhere.
thanks again
I need your help, thank you.
OK so you can post your question here: http://forum.xda-developers.com/showthread.php?t=2257421&page=1
However, I urge you to keep searching for the stock firmware. This is a rare device that has practically no support.
If you had adb support which is highly unlikely you could use the command "adb push bootanimation.zip/system/media"
But I very much doubt you will be able to get adb to communicate.
I wish you all the best in searching, but I think you may have just learned a very costly lesson on always having a backup before tinkering.
Good luck
hello, hmm what if i buy a new unit of this model? lets say another starmobile up, and i backup its firmware, is it possible to do that?
and is it possible to copy the back up on this device?
whateverwhenever said:
hello, hmm what if i buy a new unit of this model? lets say another starmobile up, and i backup its firmware, is it possible to do that?
and is it possible to copy the back up on this device?
Click to expand...
Click to collapse
I honestly don't think it would work. You really need a custom recovery or a way to access your bootlooping phone's system.
You can check this thread out on adb http://forum.xda-developers.com/showthread.php?t=2588979
If you're successful in getting adb to work you may have a shot at fixing it. But the odds are against you.
This is why we are all encouraged to read and be careful.
There two level of boot animation of an android device, right? And to change the system one is to go to /system/media or /system/customize/resource to change the boouanimation.zip. But is there any method for me to change the animation show earlier than the system one ( perhaps it is from /boot ? I dont know, I want to search for clues but I even dont know what the keyword is ).
I am using an htc 2014 phone btw.
iSaidyiu said:
There two level of boot animation of an android device, right? And to change the system one is to go to /system/media or /system/customize/resource to change the boouanimation.zip. But is there any method for me to change the animation show earlier than the system one ( perhaps it is from /boot ? I dont know, I want to search for clues but I even dont know what the keyword is ).
I am using an htc 2014 phone btw.
Click to expand...
Click to collapse
Usually not, as that part is in the bootloader, and only the manufacturer can change that.
jisoo said:
Usually not, as that part is in the bootloader, and only the manufacturer can change that.
Click to expand...
Click to collapse
Thanks for your reply!!!!
However, will there be any ways ( perhaps the OEM method ? idk.... ) for us to export the bootloader so that we can modify it?
iSaidyiu said:
Thanks for your reply!!!!
However, will there be any ways ( perhaps the OEM method ? idk.... ) for us to export the bootloader so that we can modify it?
Click to expand...
Click to collapse
To install a modified bootloader, usually it needs to be cryptographically signed, and only the OEM has the signing keys. So in practical terms, it is not possible for us users to modify the bootloader in any way.
There are some cases where some of the files used by the bootloader are stored on user-accessible storage, and in this case modifying those is feasible. But this is more exception than norm, and you'll need to read through your device forums to see if anyone has investigated this.
I will take a look in it. Thanks for your reply after all!!!