Database Develop

Problem with G1 software - PLEASE HELP!!!

Dear Users,
I am experiencing an issue which has been raised once before and no clear,
simple solution was found.
My current problem is that, after updating my G1 from 'cupcake' to 1.6, all
the calls I make and all the calls I receive are labelled as 'unknown',
despite the fact that these numbers are in my contacts. Here is the link to
the similar issue which was officially declined by Google:
http://code.google.com/p/android/issues/detail?id=2949
In the discussion thread amoung the users, there seem to be two possible
solutions (although this was not confirmed by Google, since the issue was
declined):
1. Complete factory reset.
2. STEPS:
1) Get to a shell prompt. If you're using ADB, it's "adb shell". If
you're using a
terminal/console app, just launch it.
2) Type "rm /data/misc/rild_ril.clip"
3) Reboot the phone.
My phone is currently not rooted and I have no intentions to root it in the
near future. Also, I do not favour the idea of a factory reset, since I
shall have to re-install all my applications, which will take time. The
second method to solve the problem seems the most probable in my case,
however the only problem is that, since I am not very good on the technical
stuff (i.e. 'shell prompt', 'console app', 'ADB'), I cannot figure out how
to perform what that method requests.
I would be very grateful to a person who would explain how to sort the
problem out in clear, step-by-step, user-friendly language.

The first method would be easiest for you but the second method makes the most sense. ADB is easy to set up & there are guides on here for it, also it doesn't require you to be rooted.
PS: This is in the wrong section so expect the mods to move it quickly.

You should start by trying option two.
1. Goto the market and search for Terminal. Downlaod and install the app.
2. Open your app drawer and open Terminal (The app you just installed)
3. Enter the line rm /data/misc/rild_ril.clip and hit enter.
If the command is accepted you'll get a blank prompt, type reboot and hit enter again to reboot the phone. If you get a mesage that says the command can't be completed, read only file system you'll probably need to setup ADB on your computer and enter the commands there. Search XDA for ADB for Dummies to find a thread on how to set up ADB, its really very straightforward.
Good Luck!

You could also go into Application manager and see if you can clear your Dialer or Dialer storage's cache or data (whatever they have there). I assumed that you've tried powering your phone off and on to see if that fixes it, right?

If you dont have root, you wont be able to remove stuff from the system.
It sounds like you have your contacts numbers saved without a 1 or 0 such as,
555-555-5555
1-555-555-5555
Try to edit the numbers and make them appear the same way they do when a contact calls you. I am sure this will solve the problem.

[GUIDE] Tweak the built in task killer

UPDATE: Use Appkiller to do the same thing if you're not into the whole modding scene
Hi all.
So, I'm a new user to this part of XDA (Those HTC Hero forums have taken quite the dip lately) - received my milestone on Friday, and wow, what can I say - truly blown away from the performance I can get out of it, especially since it is getting along in it's days now too. However, I'm always hungry for as much power as possible .
Something that really shocked me though is that it doesn't seem to me that anyone has played around with the automatic internal memory killer of Android. Basically, it eliminates the need of having a task killer program running at all - allows you to have Android kill your unnecessary tasks for you. But, before I repeat an already-written informational post on this, here's the link to read up about it for yourself: How to configure Android's *internal* taskkiller.
Anyway, here's a quick guide on how to add this to your wonderful Milestone (PLEASE NOTE - THIS METHOD REQUIRES ROOT):
WARNING - Playing around with system files is always dangerous. MAKE SURE YOU DO A NANDROID BACKUP JUST IN CASE. I take no responsibility for any damage what so ever (even though there cannot really be any with this ).
This guide also requires you to know about ADB Commands - google is your best friend in this case. Right now, I'm too lazy to post a guide for that .
Well, now that the formalities are out of the way...
1) Firstly, you need to have the G.O.T Open Recovery. I'm pretty certain I don't have to go into anymore details with this step - it's posted all over the place
2) (OPTIONAL FOR SAFETY. If you don't care much for safety, you may skip this step) Start your phone up as normal (if it's off) and then run the following commands from Terminal/Command Prompt on your computer, using ADB:
Code:
adb shell
su [B][U](Look out on your phone for the Root dialog)[/U][/B]
cat /sys/module/lowmemorykiller/parameters/minfree
This should return a few values that look like this:
Code:
1536,2048,4096,5120,5632,6144
TAKE NOTE OF THESE VALUES. Although it's pretty simple to remove this if it causes problems, keep these values handy somewhere. Never hurt anyone to have another back up plan
3) Mount your SD Card so that you may access it on your computer
4) Browse to OpenRecovery/GOT/bin/boot_script on your SD Card
5) Open the file "71_overclock.sh" with a text editor or something you can use to edit the shell script.
PLEASE NOTE: THIS IS USING THE OVERCLOCKING SCRIPT FROM THE G.O.T OpenRecovery. I AM USING THIS AS IT IS USUALLY RUN AT BOOT, PROVIDING YOU HAVE OVERCLOCKED YOUR PHONE TO ANY OF THE VALUES IN THE G.O.T OVERCLOCK MENU. So, long story short, you need to have selected at least one of the overclocking settings in OpenRecovery for this to work.
6) At the bottom of the file, add the following lines of code:
Code:
echo "1536,2048,4096,5120,15360,23040" > /sys/module/lowmemorykiller/parameters/minfree
THIS IS FOR THE AGGRESSIVE MODE. You can read up yourself for your own desired values in the thread link I posted above, and replace them in the above line of code as desired.
7) Save the file and close. Turn off your phone. Boot into OpenRecovery (You should know how to do this by now).
8) Go back to the overclocking menu and reset your desired clock speed. If you haven't set one before, now's the time to select
9) Restart your phone. To test if your new values have worked, boot your phone as normal, and once it's booted, connect it to your computer again, and load up Terminal/Command Prompt once again. Then, as we did in the beginning, run the following commands:
Code:
adb shell
su [B][U](Look out on your phone for the Root dialog)[/U][/B]
cat /sys/module/lowmemorykiller/parameters/minfree
This should return your newly set values. And voila! Your phone is ready to fly. Although I haven't tested speed differences on the Milestone as such, it really helped on my hero. So, post some feedback and let me know.
-----------------------------------------------------------------------------------------
IF YOU RUN INTO ANY PROBLEMS LIKE BOOTLOOPS/STUCK BOOTS:
Bootloops/stuck boots usually happen when the phone doesn't like the modification you've added to it I have no idea how this will react on other phones. It worked 100% for mine, but if you cannot run this mod, then you can remove it by doing the following:
1) Boot back into OpenRecovery.
2) Go to the G.O.T Modding menu, and then to the Restore Menu.
3) Select to restore the mot_boot_mode file.
4) Restart your phone - this time it should start, but you might notice a drop in speed. This is normal, as we have reset the overclocking to normal.
5) Mount your SD Card again, open the file "71_overclock.sh" again with a text editor or something you can use to edit the shell script.
6) Remove the line you added previously. Save and close. Unmount the SD Card.
7) Turn your phone off and boot back into OpenRecovery. Apply your overclocking again, and reboot your phone. It should boot up fine.
8) Breathe.
----------------------------------------------------------------------------------------
I'll be updating this guide in the near future to possibly include a way of doing this without having to use any overclocking, as well as a more noob friendly version, including ADB How-to's etc. For now, the extra boost in power isn't going to hurt anyone
Credits: androcheck for his original guide on this feature.
Happy speeding,
MrP.

Great job! I will be trying this on my Milestone shortly.
Hopefully this helps with the low amount of RAM our Milestones have.

free market app called autokiller
used for a while on agressive settings , stopped using it 2 weeks ago , I dont see any diffrences at all , great guide tho !

I know - I realised that there's a market app Silly me, seeing as I've used that app on my hero before. *stupid slap*
But, I prefer things like this to be incorperated into the system files as opposed to being set by an app - just one less thing to worry about I suppose. With that said however, either way will work
MrP.

MrPadie said:
I know - I realised that there's a market app Silly me, seeing as I've used that app on my hero before. *stupid slap*
But, I prefer things like this to be incorperated into the system files as opposed to being set by an app - just one less thing to worry about I suppose. With that said however, either way will work
MrP.
Click to expand...
Click to collapse
Great thread!! I was acually thinking about this a couple of days ago, I thought it wasn't possible because we need to modify the init.rc in the boot.img to initialize it... But of course we have our mot_boot_mode that can do that

Fix for nonworking WiFi on Simunlocked ATT Atrix 4G

Hey, guys after hours of thinkering it seems i devised a fix (at least a temporary, i guess it can be better implemented), but still wifi works with turned on radio.
I will not be doing any scripts or whatever.
DISCLAIMER
THIS IS ALL ON A BASIS OF INFORMING PEOPLE
I AM NOT RESPONSIBLE FOR ANY DAMAGE, LOSS OF DATA, OR BRICKED DEVICES IN CONJUNCTION OF TRYING OUT THESE STEPS
DO IT ON YOUR OWN RISK.
K now the requirements:
1. nonworking sim card (or att sim card)
2. RSD lite 5.0
3. stock 4.1.2.6 SBF flash file
4. Installed drivers on the computer for rsd
5. GladRoot http://forum.xda-developers.com/showthread.php?t=1016060 than you very much Ririal
6. OTA update
7. Working adb shell (there are other ways too but i prefer this one so ill write how i did it)
8. SQL editor, i used SQLite database browser (get it online its freeware)
9. titanium backup (if you wish to backup things, YOU MUST NOT RESTORE the [SETTINGS/BLUETOOTH] Settings Storage 2.2.1 however.
10. turned debug mode on when using adb
The process:
1. backup your data
2. Flash the stock image with RSD lite as its written here http://forum.xda-developers.com/showthread.php?t=991072 thank you kennethpen
3. put in the nonworking/att sim turn on the phone use wifi to configure motoblur
4. do not download the update yet
5. obtain root as described here, use the 1.5.7 method tho since we will be updating the ota http://forum.xda-developers.com/showthread.php?t=1016060
thanks again ririal
6. download and install ota update
7. do the afterupdate with the GladRoot
8. still on wifi, set up google account, update market gmail etc.
9. use adb/root explorer to copy the /data/data/com.android.providers.settings/databases/settings.db file to your sdcard into a directory you made before (name doesnt matter) example:
Code:
adb shell
su
cp /data/data/com.android.providers.settings/databases/settings.db /sdcard-ext/test
10. put phone into airplane mode, turn off phone
11. put in your sim card, turn on
12. let it boot and wait a min or two
13. before sliding press and hold the off button and choose airplane mode (it is IMPERATIVE that airplane mode is turned on)
14. sign into motoblur again (wifi should still work - turn it on tho since your in airplane mode)
15. repeat step 9 but copy to a second directory (lets say test1)
16. turn airplane mode off - you will loose wifi and sign into motoblur again
17. repeat step 9/15 but copy to a third directory (lets say test2)
18. copy the files from test2 and test1 to your computer - obviously to two different folders (use mass storage setting or adb pull)
19. open up the settings.db with sqlite from the not working config (in our case the one in test2) go to browse data and table secure
20. find the entry wifi_country_code and the value will be the one of your country (at least so it was with me), change that value by double clicking on it to US
21. Save the file
22. copy to your sdcard via usb to a directory lets name it "works"
23.turn off your phone, and put in the nonworking/att sim card, power it up
24. register motoblur again blah blah (ye its annoying there are ways around but that comes later and we needed it for the ota update)
25. turn the airplane mode off (its imperative to do so)
26. now we use adb again:
Code:
adb shell
su
cd /data/data/com.android.providers.settings/databases
rm settings.db
cp /sdcard-ext/works/settings.db .
chown system settings.db
chgrp settings.db
chmod 440 settings.db
cd ..
chmod 555 databases
exit adb shell with ctrl+d (in linux dont know about windows)
27. turn off phone, put in your sim card, turn on phone, register motoblur
28. most probably wifi will work for a moment than it will stop working and youll get a notifiaction lost data connection and something on (at least so it was for me)
29. use the wifi toggle on/of button to turn off and on the wifi a few times, than at the third or fourth time turn it off than on than immediately go into the browser and click on refresh as soon as you see the wifi icon in the notification tab. WiFi should work now, you can even turn it off and on with the wifi toggle button and it still works.
30. ANOTHER WARNING THO, THERE ARE QUITE SOME DRAWBACKS TO THIS METHOD (WHICH I HAVENT DISCOVERED ALL YET, TO BE HONEST BUT IM SURE THERE ARE QUITE SOME - SINCE WE DO NOT ALLOW THE SYSTEM TO EDIT THE SETTINGS.DB ANYMORE - BY CHMODDING THE PERMISSIONS), AN ISSUE I SAW IS THAT YOU CANNOT GO INTO AIRPLANE MODE ANYMORE - that is because the airplane mode state is saved in the same settings.db as the setting that blocks wifi, and if you just change that one and dont write protect the file and the databases folder the system just overwrites it again, so for now this is it.
AGAIN this is all on your own RISK, i cannot bi liable for anything out of the ordinary that happens, damages or whatsoever your phone or even you.
So now im awaiting responses if it works for you guys.
Oh and a few of the steps are just for backup purposes
Many thanks goes to Azuzu aswell, he was of great help all the time.

What about for the Canadian Bell Atrix can you please help us.

When I insert non working sim card into the phone, wi-fi working only once, after booting. Then when phone is going to lock, wi-fi is sleep and never work again. Is it instruction help to work with wi-fi during the day without rebooting? Thanks for instruction!
---
All is fine with Wi-Fi when it in Motoblur...
What about GPS?
May be needed to add GPS ON in this instruction?

Thanks guys. Its work for me. But too much DRAWBACKS. GPS does not work, settings are not saved

my friends you figured it all out like i did after a day of testing.
As i already said before there are some rather big probles that arise with this method, however for now this is the only way i found to having a working sim +wifi working.
Basically all the issues arise from the settings menu, since the settings from there are stored in the setting.db file that we disallow changing, due to this fact, i have devised a rather simpler way to do all the above + apply your specific settings - however you still wont be able to change them once you change the permissions.
1. gps state cant be changed as reported
2. ringtone/notification tone cant be changed
3. USB mode is stuck in NONE mode or the one you changed it to before doing read only
4. Possibly you cant pair new BT devices (havent tried that but i assume it might happen)
5. cant change lockscreen type (so if you pick fingerprint afterwards it wont change the lockscreen)
6. more possible problems, still if you want wifi you will endure some of those, they are however rather easy to fix, for people who dont change things all the time.
7. i found out that you have to turn off and on wifi (with the widget or in the networks menu) 2 times to make it work and it stops working if your phone changes the network from 3g to 3g or vice versa, however you just turn wifi off and on again and its fine (eventually you can just set your phone to 2g only or 3g only - either the dialer method or edit a config file - ill post that another time)
8. airplane mode not changing as stated above
So i did it like this this time:
lets assume you already have the phone 1.5.7 rooted (you can even have 1.2.6 rooted but the ota update brings nice features like longer battery, better fingerprint reader etc) and activated. NOW THIS SHORTENS THE PROCESS BY FAR and improves on the things that werent working before, it might lower battery life minorly but, well mine is still at 70% after ~16 hours so )
YOU WILL HAVE TO DO THIS ONLY ONCE (well at least until you want to change your ringtone hahaha )
1. Put in your working sim (just into the rooted atrix and the databases dir has to be read write like before, if you followed my guide above you have to go with adb shell to /data/data/com.android.providers.settings and write chmod 755 databases)
2. turn on phone in normal mode
3. set all your settings as you like and i really mean all - ringtones notifications - everything you can think of
4. turn all the networks on - wireless (it wont work but the state has to be on), bluetooth, gps - the thing is you can always turn them off, but if you write protect the file with them off you cant turn them on properly
5. pair your bluetooth devices (all of them) - havent tried yet if necessary but i think it is
6. reboot phone into normal mode, assure yourself that all the things are as you like
7. connect phone in debug mode, and set usb to none (it will stay in the none state, but you can always copy stuff with adb over, to your sdcard/internal phone mem as opposed to choosing mass storage mode where you have no adb access to them, but that is your choice ( you can manually change the state in the settings.db before making it read only, but i wont go into those details now)
Code:
adb shell
su
cd /sdcard-ext/test
cp /data/data/com.android.providers.settings/databases/settings.db .
ctrl+c/d to exit shell
8. connect phone in mass storage mode, open the settings.db file in the /sdcard-ext/test with the sqlite editor go to the brose tab, and secure, change the wifi_country_code value to ALL (last time i wrote US but ALL works fine so its more relaxed), save it
9. change the usb connection mode back to none
10. failure to chown and chgrp the settings.db to system and chmod it correctly can results in a soft brick
Code:
adb shell
su
cd /data/data/com.android.providers.settings/databases
rm settings.db
cp /sdcard-ext/test/settings.db .
chown system settings.db
chgrp system settings.db
chmod 440 settings.db
cd..
chmod 555 databases
reboot
11. the phone shoudl reboot now with all the networks turned on, you can use the widgets (or int he wireless menu) to turn off wifi and bluetooth (tested it myself and it works), havent tested gps turning off yet, but its no problem since gps turns on itself only when apps use it (maps etc, weatherbug can use it aswell, so might check into it if its permanently turned on than)
12. turn wifi off and on 2-3 times, than turn it on, it should be working now
Thanks for testing this out to confirm that it works at least
Anyhow if someone might get a clue what issues the command to change the wifi_country_code hes encouraged to share, so we can only fix that problem and there wont be these side effects than
you can however change all the settings by just editing the settings.db with the sqlite editor manually, youd have to figure out all the parameters and values yourself (some are fairly easy - for instance for usb mode, some can be rather hard - for instance ringtones, cuz you must have the path and everything)
EDIT, YOU CAN LEAVE OUT THE PAIRING BLUETOOTH DEVICES STEP, pairing works, i just tried it with an apple bluetooth kb, and its fine.

RacecarBMW i cannot say anything with certainty, since i dont have one to test it on, but probably the same method would work for the bell atrix (use the method in the post above, with the ALL value for wifi_country_code), however you have no sbf to flash and its way more dangerous that you will create a softbrick, so please be very careful and its all YOUR RESPONSIBILITY. I AM AND WILL NOT BE LIABLE FOR ANY ADVERSE EFFECTS.

We need to lock only some rows in db file or creating daemon which would keep these lines in memory. Is it posible with SQLite?
crnkoj Please change on step 10 in listing:
cd /data/data/android.providers.settings/databases
to
cd /data/data/com.android.providers.settings/databases
I do all steps and my GPS works fine... Thanks

how can i undo this:
chown system settings.db
chgrp system settings.db
chmod 440 settings.db
chmod 555 databases
what's default settings?

loggin111 said:
how can i undo this:
chown system settings.db
chgrp system settings.db
chmod 440 settings.db
chmod 555 databases
what's default settings?
Click to expand...
Click to collapse
you can just enter to another folder to /data/data/ directory with cd and run ls -l to view directory permissions.
chmod 755 databases
and something like 755 for settings.db

thank you Jartyn, replaced that in step 10. And yes Jartyn exactly as you say we jsut have to keep this line permanent and everything else changeable (maybe there is an option in sqlite to block only 1 line? - i dont know so much).
I do however know now, which process is changing this:
it is the WifiStateTracker ( http://www.androidjavadoc.com/1.1_r1_src/android/net/wifi/WifiStateTracker.html ) from android.net.wifi , i however dont know where to find this on the phone.... we would most probably only have to change one line in the WifiStateTracker and it would work fine (however this still wouldnt be fixing the source, we would just fix the change in country code, yet the reference to which its compared is still unknown to me, but i think it would suffice for us) the funny thing here is the WifiStateTracker is not in the official android tutorial tho:
http://developer.android.com/reference/android/net/wifi/package-summary.html
so if anyone knows where to find this we could fix it easyly

1.5.2
crnkoj said:
thank you Jartyn, replaced that in step 10. And yes Jartyn exactly as you say we jsut have to keep this line permanent and everything else changeable (maybe there is an option in sqlite to block only 1 line? - i dont know so much).
I do however know now, which process is changing this:
it is the WifiStateTracker ( http://www.androidjavadoc.com/1.1_r1_src/android/net/wifi/WifiStateTracker.html ) from android.net.wifi , i however dont know where to find this on the phone.... we would most probably only have to change one line in the WifiStateTracker and it would work fine (however this still wouldnt be fixing the source, we would just fix the change in country code, yet the reference to which its compared is still unknown to me, but i think it would suffice for us) the funny thing here is the WifiStateTracker is not in the official android tutorial tho:
http://developer.android.com/reference/android/net/wifi/package-summary.html
so if anyone knows where to find this we could fix it easyly
Click to expand...
Click to collapse
hi
does it work with 1.5.2 rooted?
i flashed sbf back from unroot 1.5.7 to 1.2.6 , i didn't gladroot because i had not wifi for update & after update.bat
so i stopped @ 1.5.2 & i cannot update anymore, please help me to activate my wifi.....

zeidof you can do it on the 1.2.6 rooted aswell, use the same steps as described above, it should work fine.

hey guys what wifi issues? i have a ATT on vodafone UK and i dont seem to see any issues.

crnkoj said:
zeidof you can do it on the 1.2.6 rooted aswell, use the same steps as described above, it should work fine.
Click to expand...
Click to collapse
Hi can this fix be on a custom rom? i mean it will be included on a custom rom..

ronaldo, use search ... http://forum.xda-developers.com/showthread.php?t=1010942&page=3 lucky you arent one of us who have this issue.
emorej, if you read my first post, it says i wont be doing any scripts/cwm flashable updates/custom roms. If anyone wants to implement this in his rom hes free to do so, he has to be careful tho, since basiically the script that updates it, has to change only the wifi_country_code ALL and than make the databases folder read only, it must not copy over a generic settings.db since there are user specific things in it.
Jartyn and i are trying to figure a more source problem related fix for the issue, but that will take quite some time i fear.

Here is an even better solution from akizakian
http://forum.xda-developers.com/showthread.php?t=1058260

Simplest Solution
I had this same issue and the simplest solution is here:
1. Extract the attached zip file and you will get two files.
2. Turn off Wi-Fi, replace the two files in
/system/etc/firmware/wifi
This can be done using adb or Root Explorer.
turn Wi-Fi back on, and that's it!

Mate you are mistaken, its two totally different issues you and i are talking about, yours is that 5ghz isnt working, mine is that wifi isnt working in certain countries at all. by copying the files you supplied my wifi again stops working, because there is a country lock within the moto atrix wifi drivers (the version doesnt matter, may it be 1.2.6, 1.5.2, 1.5.7 or 1.8.3, the issue you fixed with your method is only the nonworking 5ghz on the 1.5.2. leaked sbf)
ceo.mtcl said:
I had this same issue and the simplest solution is here:
1. Extract the attached zip file and you will get two files.
2. Turn off Wi-Fi, replace the two files in
/system/etc/firmware/wifi
This can be done using adb or Root Explorer.
turn Wi-Fi back on, and that's it!
Click to expand...
Click to collapse

The LG Optimus wifi drivers fixed my simunlocked wifi problem in qatar.
The other solutions that were being thrown around did not.

seems moto is gonna fix it with an update:
https://supportforums.motorola.com/thread/50598?start=15&tstart=0

[Perma-Temp Root] Better Temp Root [From The Rezound]

This release has been out in the wild for several days now for the Rezound. Everyone who has gotten it to work reports root lasting much longer than previous methods. I am glad that it is working out for others. This should also work on other devices, such as the Vivid and that is why I am posting it here. There is nothing about it that makes it work specifically for the Rezound.
It still uses zergrush and absolutely does not provide any other capability than other temp roots. (Although some people have reported root apps see root better so it might actually be better). The only difference is I have the things relating to root (ie su,busybox, etc) stored in a ramdisk that lasts alot longer (I have not seen of a report of it being lost before a reboot yet) than things "written" or linked to /system. This is because we still have /system write locked so when we write things to it (like the original zergrush implementation) it gets forgotten after while.
Your mileage may vary. I am obviously not responsible for bricks, data loss, etc if you use this. I and others have used it for about a week and it has been fine.
To use:
0) Make sure superuser isn't installed
1) Reboot phone (full reboot), make sure usb debugging is on.
2) Plug in phone in charge only mode to PC.
3) Kill everything in the built in task manager, then go back to the rosie home screen.
4) Extract zip and doubleclick temproot.bat
5) There is a 20 second time out at the beginning just in case you forgot to plug in your phone, etc so you have time to cancel the process before it starts. To skip it just hit enter on the keyboard or wait the 20 seconds.
6) Hit the thanks button (bottom left of this post) if you like it!
Let me know if you like it better or if something bad happens so I can take it down. Lets hope we get S-Off soon and don't have to deal with this temp root **** anymore.
Troubleshooting:
1) Bootlooping? Pull the battery. If you still are boot looping, an RUU restore may be necessary. I believe this has only happened to one user and it was likely a result of something that was done AFTER root and not directly caused by this program.
2) Just not working? Reboot both your PC and Phone. If ADB cannot see your phone, it is not a fault of the program. If you haven't gotten other temp root methods to work, it is likely this one won't either.

con247 said:
This release has been out in the wild for several days now for the Rezound. Everyone who has gotten it to work reports root lasting much longer than previous methods. I am glad that it is working out for others. This should also work on other devices, such as the Vivid and that is why I am posting it here. There is nothing about it that makes it work specifically for the Rezound.
It still uses zergrush and absolutely does not provide any other capability than other temp roots. (Although some people have reported root apps see root better so it might actually be better). The only difference is I have the things relating to root (ie su,busybox, etc) stored in a ramdisk that lasts alot longer (I have not seen of a report of it being lost before a reboot yet) than things "written" or linked to /system. This is because we still have /system write locked so when we write things to it (like the original zergrush implementation) it gets forgotten after while.
Your mileage may vary. I am obviously not responsible for bricks, data loss, etc if you use this. I and others have used it for about a week and it has been fine.
To use:
0) Make sure superuser isn't installed
1) Reboot phone (full reboot), make sure usb debugging is on.
2) Plug in phone in charge only mode to PC.
3) Kill everything in the built in task manager, then go back to the rosie home screen.
4) Extract zip and doubleclick temproot.bat
5) There is a 20 second time out at the beginning just in case you forgot to plug in your phone, etc so you have time to cancel the process before it starts. To skip it just hit enter on the keyboard or wait the 20 seconds.
6) Hit the thanks button (bottom left of this post) if you like it!
Let me know if you like it better or if something bad happens so I can take it down. Lets hope we get S-Off soon and don't have to deal with this temp root **** anymore.
Troubleshooting:
1) Bootlooping? Pull the battery. If you still are boot looping, an RUU restore may be necessary. I believe this has only happened to one user and it was likely a result of something that was done AFTER root and not directly caused by this program.
2) Just not working? Reboot both your PC and Phone. If ADB cannot see your phone, it is not a fault of the program. If you haven't gotten other temp root methods to work, it is likely this one won't either.
Click to expand...
Click to collapse
Just don't execute the program again after you have done it once, or it will boot loop the vivid to high hell. And you'll have to do a factory reset.
Sent from my HTC PH39100 using xda premium

Did that just happen to you? There is a 20 second timeout for a reason...

Is there a possibility in making a Mac or Linux friendly version?
Thank
Drew
Sent from my HTC PH39100 using xda premium

drewdatrip said:
Is there a possibility in making a Mac or Linux friendly version?
Thank
Drew
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
If you know how to use adb on Mac or Linux you can just run the equivalent command one by one
Sent from my ADR6425LVW using XDA App

Code:
timeout /T 20
adb shell rm /data/local/tmp/boomsh
adb shell rm /data/local/tmp/sh
adb push zergRush /data/local/
adb shell chmod 755 /data/local/zergRush
adb shell /data/local/zergRush
adb wait-for-device
adb shell sleep 1
adb remount
adb shell mkdir /system/xbin
adb shell mount -t tmpfs none /system/xbin
adb push busybox /system/xbin
adb shell chmod 4755 /system/xbin/busybox
adb push su /system/xbin/su
adb shell chmod 4755 /system/xbin/su
adb shell cd /system/xbin
adb shell /system/xbin/busybox --install -s /system/xbin
adb install Superuser.apk
Does nothing different from the original scripts that were posted here a month ago.

Read my OP bud. I have downloaded all of the ones posted in your Vivid section and made sure. This one stores the root to a ramdisk that lasts until a reboot instead of /system rw mount going away after a short time.

I had a problem pushing this to the phone at first. Then I made sure the screen didnt time out and everything worked fine for me....just a little FYI incase someone runs into this problem as well.
Thanks

Didn't work for me.
I followed the instructions to the letter, and when I ran the batch file, there was no 20-second wait; it started immediately. It found the phone, went through the "sending speedbots" or whatever, and then rebooted the phone. It then re-ran ADB with "wait-for-phone" and the phone got stuck in a bootloop. I kept it connected to the PC and did a battery pull, and as the Beats Audio logo came up during boot, the command window on my PC flashed some more text and then closed. I let the phone completely boot and tried to run Titanium Backup and I get an error indicating it doesn't have root access. Any thoughts?
BTW - running Windows XP on a Dell Optiplex 755 with 4GB of RAM.
UPDATE - I tried performing the whole process again, and it ran for about 10 seocnds then just closed. So, I tried again, and it went through the process, up to rebooting my phone and indicating "wait-for-device," but the phone never completely shut down; it hung at that shutdown point where the entire screen is black but you can see a bit of lighting. So I did another battery pull and turned the phone on again, and after about 15 seconds, the command window scrolled a bunch more stuff and then closed and the phone continued to boot. It did manage to boot this time without a battery pull and no loops, and SU is there, but when I run Titanium Backup, I still get a "phone not rooted" error.
Looks like I'm waiting for perm root. Thanks for your work though. I'm glad it worked for others. Viva la Android!!!!

FYI: I did disable bloatware using a script, within the same command prompt window right after achieving temporary root.
The bloatware APPS and widgets remain disabled even after full reboots, including a battery pull.
I'm very grateful to temporary root, since it allows to disable most of the pre-installed bloatware.

Went from bad to worse.
I ran this on my phone last night, and even though it didn't temp root my phone, it still ran fine for the rest of the night and all day today. I decided to reboot the phone before I went to bed and now I am stuck in some kind of loop. The phone actually boots to the lock screen, and I can unlock it, but some of the icons on my homescreen don't load and the phone becomes unresponsive after about 10 seconds and then reboots. It's done this about 10 times and a battery pull does not resolve the issue. Help?

Have you tried a factory reset ? After that it may allow you to run the temp root. At least that is what happened once when I tried it.

Well through trial and error, I have found out several things...
1. The temp root that comes with the Rezound Clean Tool is the only temp root tool I can get to work.
2. Even if you have BT turned on before using the Rezound Clean Tool, turning it off permanently disables it until a reboot is done.
3. It is common for the Rezound to suddenly start boot looping, even if you haven't done any rooting or anything. This is caused by the connection type in Phone Properties randomly changing to a type that is incompatible with the Verizon SIM. (Google search "rezound boot loop" and you'll find the fix quite easily.) Also, removing the battery cover may disable the antenna but only a SIM-less boot will stop the boot looping so that the communication type can be set back to what it should be.
4. I still love this phone. It is the best phone on the market today; it has the fastest processor available from any carrier and has the most internal memory of phones that allows for removeable storage.
Thanks to all the devs for their hard work - I can't wait for perm root and custom ROMs!!!!

[Guide] How to fix black screen of death after dirty flashing lollipop

On threads of lollipop flashing, There are quite lots of people asking about the black screen issue, but not really clear solution's out there.
These are the symptoms:
1. After booting, you get black screen with just upper notification bar and back button below
2. If you turn on the screen after a few second, you see the normal screen but only for a fraction of second.
3. You can hear some notification sound, but notification bar still says "no notification" (or something, well I'm not using english ui )
4. no response on cancel button
The reason is that, you've set a lock screen before, but your phone thinks you've never performed initial setup, so your phone gets confused and doesn't know what to do.
You can solve this by deleting /data/system/gesture.key (for gesture lock) or /data/system/password.key (for password lock) on recovery mode. Now your lock screen's gone, and you can normally boot your phone. If you're doing this on recovery, you should mount /data partition to locate the file.
There could be some other problems because your phone still thinks that you haven't initiallized it, so you should manually run initial setup by "adb shell am start -n com.google.android.setupwizard/.SetupWizardTestActivity" on normal boot.
I hope this helps!
credit : @nighthammer http://forum.xda-developers.com/showpost.php?p=56715651&postcount=7664

FreakyTux said:
On threads of lollipop flashing, There are quite lots of people asking about the black screen issue, but not really clear solution's out there.
These are the symptoms:
1. After booting, you get black screen with just upper notification bar and back button below
2. If you turn on the screen after a few second, you see the normal screen but only for a fraction of second.
3. You can hear some notification sound, but notification bar still says "no notification" (or something, well I'm not using english ui )
4. no response on cancel button
The reason is that, you've set a lock screen before, but your phone thinks you've never performed initial setup, so your phone gets confused and doesn't know what to do.
You can solve this by deleting /data/system/gesture.key (for gesture lock) or /data/system/password.key (for password lock) on recovery mode.
after that, you should manually run initial setup by "adb shell am start -n com.google.android.setupwizard/.SetupWizardTestActivity" on normal boot, to avoid several problems.
I hope this helps!
credit : @nighthammer http://forum.xda-developers.com/showpost.php?p=56715651&postcount=7664
Click to expand...
Click to collapse
This would be sweet except for some reason I hadn't accepted the adb authorization request on my device before I went all darkscreen duck.
wipe it is.

perdid0 said:
This would be sweet except for some reason I hadn't accepted the adb authorization request on my device before I went all darkscreen duck.
wipe it is.
Click to expand...
Click to collapse
You can delete the file via recovery, with file explorer or adb.
Since you have to unlock the bootloader to flash a factory image, you can flash a recovery image any time if you need one.

FreakyTux said:
You can delete the file via recovery, with file explorer or adb.
Since you have to unlock the bootloader to flash a factory image, you can flash a recovery image any time if you need one.
Click to expand...
Click to collapse
i cannot find that file in the location you specified. any other suggestions for locating it?!
---------- Post added at 09:23 AM ---------- Previous post was at 09:16 AM ----------
actually.......i found it!!!! same place you said!!! deleted both .key files and rebooted.......the screen was gone allowing me to accept the adb autorization and run the setupwizard!!! woot woot.....thanks a billion!!

perdid0 said:
i cannot find that file in the location you specified. any other suggestions for locating it?!
---------- Post added at 09:23 AM ---------- Previous post was at 09:16 AM ----------
actually.......i found it!!!! same place you said!!! deleted both .key files and rebooted.......the screen was gone allowing me to accept the adb autorization and run the setupwizard!!! woot woot.....thanks a billion!!
Click to expand...
Click to collapse
I'm glad that it helped!:highfive:

Hey man, thank you for your post !
I delated the file you said, but i didn't understand what should I do then ? Does it work if I don't do that adb setup (that I don't know what it is..)
Thank you for your help !

jordanl68 said:
Hey man, thank you for your post !
I delated the file you said, but i didn't understand what should I do then ? Does it work if I don't do that adb setup (that I don't know what it is..)
Thank you for your help !
Click to expand...
Click to collapse
Check the help threads for Nexus devices, there are "how-to" ADB & fastboot guides just everywhere. It works for all Nexus devices just the same way.
tetakpatalked from Nexus 7 flo

Please add this to your post. I had the black screen, but I never had a password set up. The black screen was happening because before I flashed an update, I had a system profile set to bypass the lockscreen. Once I put it back on the default profile (which you can do from the notification bar) everything was fine.

HELP! BLACK SCREEN ISSUE (Lollipop)
I flashed cm12 on my Galaxy Grand 2,but everytime i push the power button to unlock the screen,All i get is a black screen.I can hear touch sounds and responses and the harware buttons light up,but that's it.The black only goes on rebooting and I have to reboot my phone everytime I unlock it.Please Help?

Better Explanation
To make this guide appear better , and make it more easy doing etc etc..
Add this instead of a line method (well explained)
Download Aroma File Manager
Place it in your scdard directory
Boot in recovery
Mount Data
Go to Install and flash this zip..
Navigate to /data/system
Now delete password.key if a normal password or
gesture.key if a gesture

akastixx said:
Please add this to your post. I had the black screen, but I never had a password set up. The black screen was happening because before I flashed an update, I had a system profile set to bypass the lockscreen. Once I put it back on the default profile (which you can do from the notification bar) everything was fine.
Click to expand...
Click to collapse
I don't understand what you're saying. I've never seen "system profile set to bypass the lockscreen". could you tell me more specifically?
Aman_Arora said:
To make this guide appear better , and make it more easy doing etc etc..
Add this instead of a line method (well explained)
Download Aroma File Manager
Place it in your scdard directory
Boot in recovery
Mount Data
Go to Install and flash this zip..
Navigate to /data/system
Now delete password.key if a normal password or
gesture.key if a gesture
Click to expand...
Click to collapse
Thanks for your help. that's also a great workaround, but you know, it was nexus 5 that I was working on. If you were to place the file on the device, you would have to use adb anyway.

how can you do anything while screen is black? You just do not have any options displayed. I mean I am a layman

As everyone involved seems to be new to rooting, judging from the number of posts , tell them to READ READ READ . There is something called running before you can walk.

A clean install avoids the BS to begin with ...

Doesn't work with Nougat 7.1.1 (Dark ROM)
Does anyone know what if this solution works with Nougat 7.1.1 (Dark ROM)? I couldn't find the given files under /data/system, but I've found one as gatekeeper.password.key. However, if I delete it and reboot, I still get black screen.
Also, trying to run the setup wizard using ADB gives me a "SecurityException: Permission Denial: starting intent { ... } from null ( ... ) not exported from uid 10020".
Any ideas?