Related
I'm trying to push touchwizcalendar but it doesn't work. This is what I get:
C:\sdk\tools>adb push touchwizcalendar.apk /system/app/touchwizcalendar.apk
failed to copy 'touchwizcalendar.apk' to '/system/app/touchwizcalendar.apk': Per
mission denied
Click to expand...
Click to collapse
keep your phone unlocked, run the command and you'll see the Superuser app pop up. Hit allow.
The end.
Eugene has a init script that will have staten as rw always.. Its an update.zip you flash from cwmod recovery.. If you don't have a lag fix it will flash fine, if you do it will over write it so you have to modify...
His newest rom supports both, maybe you could just kang it..
I currently have his mount script on my phone bc im always editing my services.jar and need that ability..
Sent from my SGH-T959 using XDA App
cashless said:
keep your phone unlocked, run the command and you'll see the Superuser app pop up. Hit allow.
The end.
Click to expand...
Click to collapse
It didn't work and I got the same message.
junkdruggler said:
Eugene has a init script that will have staten as rw always.. Its an update.zip you flash from cwmod recovery.. If you don't have a lag fix it will flash fine, if you do it will over write it so you have to modify...
His newest rom supports both, maybe you could just kang it..
I currently have his mount script on my phone bc im always editing my services.jar and need that ability..
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Really appreciate that you are trying to help but I don't have a clue what you said. I'm totally new to this.
We had are First Sleepless Night with the New baby Boy.... Between Trying Figure out what was Wrong & taking turns with the Wife Holding Aries, I tried Pushing File's & forgot adb push didn't work...
Now this Script originally is what I made for the Behold 2, but the Basic still works For the SGV..
Just mod the script if your using the userinit.sh
Using this script you can place the userinit.sh any place you would Like...
I hope ever gets Good use out of this & Please Enjoy!
~Eugene
Download > adbpushGS1.zip
Installing*
Reboot to recovery, run the update.zip to run ClockworkMod Recovery, then installed the ZIP..
Quoted from eugene's post-- hope this helps...
Sent from my SGH-T959 using XDA App
How do I "Reboot to recovery" and I think I already run the "update.zip" when I rooted the phone. Do I have to download ClockworkMod Reovery or something? Like said I'm new to this so I'm sorry if I'm a nuisance.
Edit: Is it the same thing as this?
http://awdisk.com/2010/01/how-to-reboot-your-motorola-milestone-in-recovery-mode/
Now we can start. Plug your device to your computer and enable the debugging mode of your phone (Go to MENU->SETTINGS->APPLICATIONS->DEVELOPMENT->Enable the “USB debugging”).
Then you need the adb tool that is given with the SDK. (You can find it it the “Tools” directory of the SDK).
Open a command prompt, go to the directory of “adb.exe” and type:
adb.exe devices
You should see your device. If there is no device connected, maybe your phone is not in the “debugging mode” see above. If your device appears, you can now type:
adb.exe -d reboot recovery
Then your phone will reboot in recovery mode and you will see this logo:
Click to expand...
Click to collapse
You can go to the market and download rom manager and use it to flash a custom recovery...
Flash cwmod recovery from the app
Reboot into cwmod recovery from the app
First thing to do its go to the nandroid option and do a backup (always recommended before changing anything)
Then dl the link from above.. This is a new .zip make sure its on the internal sdcard (the 16gb one).. When you reboot into recovery (from the app like last time) go to flash any zip from sdcard.. Choose the new .zip file you just downloaded.. Your /system should now be rw upon reboot
Sent from my SGH-T959 using XDA App
do we rename the adbpushGS1.zip file??
i reboot into recovery and chose reinstall packages because that's all there was, besides deleting ?
edit: i ionstalled the push zip but when i reboot i get stuck at the galaxy s logo
junkdruggler said:
We had are First Sleepless Night with the New baby Boy.... Between Trying Figure out what was Wrong & taking turns with the Wife Holding Aries, I tried Pushing File's & forgot adb push didn't work...
Now this Script originally is what I made for the Behold 2, but the Basic still works For the SGV..
Just mod the script if your using the userinit.sh
Using this script you can place the userinit.sh any place you would Like...
I hope ever gets Good use out of this & Please Enjoy!
~Eugene
Download > adbpushGS1.zip
Installing*
Reboot to recovery, run the update.zip to run ClockworkMod Recovery, then installed the ZIP..
Quoted from eugene's post-- hope this helps...
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
So can I just go into userinit script and add this to the top...
Code:
show_progress 0.100000 0
show_progress 0.500000 0
delete SYSTEM:bin/playlogos1
copy_dir PACKAGE:system SYSTEM:
set_perm 0 1000 0755 SYSTEM:bin/playlogos1
set_perm 0 1000 0755 SYSTEM:bin/playlogosnow
show_progress 0.100000 10
Or was it a diff script we pull from and add to it? Also do I have to put anything after I copy this into the script before the normal script in userinit to signify a pause or finishing one task and starting another?
I saw ;fi placed throughthe script alot and im guessing its afinish point or something to start the next set of commands fresh m???
Pooped from my Samsung Vibrant using XDA app...
Dont mind the skidmarks...
p()()pypants said:
So can I just go into userinit script and add this to the top...
Code:
show_progress 0.100000 0
show_progress 0.500000 0
delete SYSTEM:bin/playlogos1
copy_dir PACKAGE:system SYSTEM:
set_perm 0 1000 0755 SYSTEM:bin/playlogos1
set_perm 0 1000 0755 SYSTEM:bin/playlogosnow
show_progress 0.100000 10
Or was it a diff script we pull from and add to it? Also do I have to put anything after I copy this into the script before the normal script in userinit to signify a pause or finishing one task and starting another?
I saw ;fi placed throughthe script alot and im guessing its afinish point or something to start the next set of commands fresh m???
Pooped from my Samsung Vibrant using XDA app...
Dont mind the skidmarks...
Click to expand...
Click to collapse
I would hate to tell you something wrong... If you use twitter I would ask eugene... or you can send him a pm or here is a link to the OP, you could ask in there
http://forum.xda-developers.com/showthread.php?t=741664
sorry I wasnt more help
Ok so I added that except to the userinit script, lag fix still works, adb doesnt seem to...
Just ran .zip file through clockwork to overwrite other file then just fix later after adb use was done, still no positive results...
Keeps saying
Cannot stat 'touchwizcalendar.apk' : no such file our directory
And if I open a shell and type the same command i get push: not found
Maybe I am just approaching this all wrong and not getting adb set up right first or something...
Can some one just step me through this crap, I can almost always figure this kind of thing out and this is pissing me off that I can't do a simple command to reinstall a damn calendar apk I want and that's the whole frickin point of having root...
Starting fresh again...
Running a fresh flash of vibrant6, have an up to date busy box, no lag fix activated at this time (but files are there from vibe6 and had it installed in the past before nand restoring.stock w/root and flashing fresh vibe 6), no adb push script installed yet but.zip is in root of sd if needed, running version 1.0.26 of adb on my computer and have apk files pulled from deodexed rom that are desired to be pushed sitting in root of sdcard (files named; "TouchWizCalendar.apk", "TouchWizCalendarProvider.apk", "TouchWizCalculator.apk", "ClockPackage.apk".)
Again guys any help would be appreciated as this is driving me nuts and should be slot easier with how some of you make it sound...
Sent from my SGH-T959 using XDA App
Do you use droid explorer? It makes adb much easier...
Sent from my SGH-T959 using XDA App
Finally got the Calendar to show up. Thanks a lot Junkdruggler and other members!
what I got lost... What you trying to do now? What do you want in you system file?
Sent from my SGH-T959 using XDA App
junkdruggler said:
what I got lost... What you trying to do now? What do you want in you system file?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I deleted stock samsung calendar (touchwizcalendar) via titaniumbackup and I pushed it back.
oh so your good now? everything working fine?
if so glad I could help...
junkdruggler said:
oh so your good now? everything working fine?
if so glad I could help...
Click to expand...
Click to collapse
Yes, everything is working fine now. Thank you
Can I delete the .apk, .odex, and update.zip from the internal sdcard?
yes you can...they're not needed anymore..
junkdruggler said:
Do you use droid explorer? It makes adb much easier...
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
can i push a boot animation zip using root explorer??
and may i ask how does droid explorer make adb easier?
What kind of boot animation.zip? You prob have to flash that thru recovery...
Droid explorer makes install a one click thing... It adds the sdk to your paths and pushing apps just takes a double click.. Prob more things I don't use also..
Sent from my SGH-T959 using XDA App
Hi everyone,
I tried using a script which automated the install for the the custom recovery, but I started to get messages that it ran out of disk space (I can't link to the file due to my noob status). I probably should have come here first before using that script, but such as life..
I have no important data on the phone, if I lose it all that's ok.
It rebooted and my p500 waits with the following
"Fastboot mode started"
"udc_start()"
It also gives some info when USB is connected ie.
"- suspend -"
"- reset -"
Do I have a paperweight?
thanks and sorry for the newb post ..
edit: so I found this : http://forum.xda-developers.com/showthread.php?t=1003790 and
http://forum.xda-developers.com/showthread.php?t=875881
and have gotten it to the yellow emergency mode, not sure how to flash it from here though.
edit2: dling the stock firmware from http://forum.xda-developers.com/showthread.php?t=1073827
edit3: there's this as well.. http://forum.xda-developers.com/showthread.php?t=1088046 If I try this method, will it screw up again from too little free disk space?
I'm to drunk to guide our give you the link to fix it but I will tell you, you can fix it just hold on we will help you ; ) and we don't by the time I wake up I will help you its ok ))
Sent from my LG-P500 using XDA Premium App
dislplin01 said:
I'm to drunk to guide our give you the link to fix it but I will tell you, you can fix it just hold on we will help you ; ) and we don't by the time I wake up I will help you its ok ))
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
thank you very much, I appreciate it haha
Your phone has booted in fastboot mode. Go to development section and read a tutorial how to recover from fastboot.
Sent from my LG-P500 using XDA Premium App
setTopbox said:
thank you very much, I appreciate it haha
Click to expand...
Click to collapse
Then did u unbricked now
Mahesh
go here....
http://forum.xda-developers.com/showthread.php?t=1088046
or here
http://forum.xda-developers.com/showthread.php?p=13813493
How to install Android SDK /ADB
http://lgoptimusonep500.blogspot.com/2011/01/how-to-install-android-sdk-adb.html
dislplin01 said:
I'm to drunk to guide our give you the link to fix it but I will tell you, you can fix it just hold on we will help you ; ) and we don't by the time I wake up I will help you its ok ))
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
Most honest post I've seen on the entire forum.
Sent from my Kyocera Echo.
mvgadagi said:
Then did u unbricked now
Mahesh
Click to expand...
Click to collapse
I got the phone working again - thanks! I guess it's not a great idea to install the custom recovery
with low disk space?
setTopbox said:
I got the phone working again - thanks! I guess it's not a great idea to install the custom recovery
with low disk space?
Click to expand...
Click to collapse
Hmmm. Well, should not matter? /recovery uses a separate partition. Perhaps you flashed a corrupt (incomplete) image?
well if u ever wish to install recovery just download rom manger from market (latest) and install recovery from rom manger option make sure u hav eusb debugging enabled. it works easy
shhbz said:
well if u ever wish to install recovery just download rom manger from market (latest) and install recovery from rom manger option make sure u hav eusb debugging enabled. it works easy
Click to expand...
Click to collapse
Erm... reading all the posts about fastboot after using ROM Manager for this, I guess I would rather stick with the custom script using flash_image.
doktornotor said:
Hmmm. Well, should not matter? /recovery uses a separate partition. Perhaps you flashed a corrupt (incomplete) image?
Click to expand...
Click to collapse
hmm, I'm not sure (when I dl'd the file I did compare the hash as per instructions). I used the following instructions:
manast.com/2011/05/07/how-to-install-custom-recovery-on-lg-optimus-one-p500
I then went into a terminal emulator, and ran "sh /sdcard/rf.sh". At that point the output of the script started to say "disk full" (and then it reboot into the fastboot prompt).
setTopbox said:
I then went into a terminal emulator, and ran "sh /sdcard/rf.sh". At that point the output of the script started to say "disk full" (and then it reboot into the fastboot prompt).
Click to expand...
Click to collapse
No idea about that script. Using flash_image and never had any issue with "disk full", frankly the message does not make sense. All you need is to copy the recovery image to SD and run as root:
Code:
# flash_image recovery /sdcard/recovery.img
Done.
doktornotor said:
No idea about that script. Using flash_image and never had any issue with "disk full", frankly the message does not make sense. All you need is to copy the recovery image to SD and run as root:
Code:
# flash_image recovery /sdcard/recovery.img
Done.
Click to expand...
Click to collapse
I'm getting permission denied when trying to use flash_image. Gingerbreak says the device is rooted, and the terminal does ask for superuser permission when i open it (su works in the terminal). I also tried chmod 755 flash_image but that didn't work either.
the permissions for flash_image are r-xr-x any thoughts ?
edit: apparently the sdcard is mounted with -noexecute ? So I tried copying flash_image to / but it's read only. Is there somewhere where I can execute this?
This rf.sh script seems most notorious, I too went into fastboot after that. Doktornotor's method worked (in fact I think he/she was the one who bailed me out back then as well).
If you got into fastboot, most probably you have a rooted phone.
To use flash_image you need to get the flash_image.sh on the root of your sd card. Search the forum for Amon-Ra custom recovery, and you shall find this file in that thread (it is required for Amon ra setup). Log in to your adb console, and use fastboot to push the new image in the recovery partition.
Unless your recovery.img or flash_image.sh is corrupted, it will work for sure.
Keep in mind, fastboot is a very powerfull tool, if you can access it, you're safe.
Cheers,
Alex
did you get out??
just flash stock firmware with kdz worked for me bro
Buddy,
You do not need to flash anything with KDZ. The ROM is fine nothing happened to it. All your issue is with the recovery being flashed wrongly for some reason.
I had the same issue just yesterday and I managed to flash the recovery through fastboot.
What you need to do is:
1. Install android SDK from Google.
2. Connect the phone while it is on fastboot.
3. If your windows does not find the fastboot drivers online, use the drivers in this link:
http://www.megaupload.com/?d=39ZR16W1
4. extract the .zip file that you copied to your SD. The one that contains the recovery.
5. Copy the recover.img (or whatever the name of the .img file in the .zip file) to the folder inside the android sdk where fastboot.exe is located (I think its the tools folder)
6. Copy the adbwinapi.dll file from the android SDK\platform-tools\ to the folder containing fastboot.
7. issue the command (and replace recovery.img with the .img file name you have):
fastboot flash recovery recovery.img
fastboot reboot
Dr.Alani said:
Buddy,
You do not need to flash anything with KDZ. The ROM is fine nothing happened to it. All your issue is with the recovery being flashed wrongly for some reason.
I had the same issue just yesterday and I managed to flash the recovery through fastboot.
What you need to do is:
1. Install android SDK from Google.
2. Connect the phone while it is on fastboot.
3. If your windows does not find the fastboot drivers online, use the drivers in this link:
http://www.megaupload.com/?d=39ZR16W1
4. extract the .zip file that you copied to your SD. The one that contains the recovery.
5. Copy the recover.img (or whatever the name of the .img file in the .zip file) to the folder inside the android sdk where fastboot.exe is located (I think its the tools folder)
6. Copy the adbwinapi.dll file from the android SDK\platform-tools\ to the folder containing fastboot.
7. issue the command (and replace recovery.img with the .img file name you have):
fastboot flash recovery recovery.img
fastboot reboot
Click to expand...
Click to collapse
I appreciate the information. When I'm in adb, su won't allow me to gain root access on the phone. The phone itself is rooted using gingerbreak though.
setTopbox said:
I appreciate the information. When I'm in adb, su won't allow me to gain root access on the phone. The phone itself is rooted using gingerbreak though.
Click to expand...
Click to collapse
I do not see how you need to use adb.
Sent from my LG-P500 using XDA App
Greetings everyone!
New *registered* user here! I've been frantically sifting through post after post on the forums all night hoping to get some help with an issue I am having on my Vibrant.
Goal:
Remove some bloatware ONLY, not looking to install any ROMs or modify the phone too much...just clean some annoying apps and icons off.
Phone Information:
Model SGH-T959
Firmware 2.2
Baseband T959UVKB5
Kernel 2.6.32.9
Build FROYO.UVKB5
I currently have the latest version of Java, Android SDK, and SuperOneClick installed.
Install directory of AndroidSDK:
C:\AndroidSDK
My method of failure:
Open SuperOneClick, Click "Root"
Start, Run, "CMD"
cd c:\AndroidSDK\tools
adb shell
mount -o rw,remount /dev/block/st19/system
This is where it fails and I run into an endless loop of it telling me the proper usage of the "mount" command. I thought I had it at one point but when I typed: rm /system/AmazonMp3.apk all it did was tell me that it was a read-only file and that it couldn't be deleted.
Can someone help lead me in the right direction of what I am doing wrong? I rooted and removed all bloatware about a year ago but I just did an upgrade through MiniKies to the latest version of firmware and I can't seem to remember the process I went through that long ago to get it done right.
I apologize for possibly asking a question that has been asked numerous times but I just couldn't seem to get the wording right to get any helpful results in the search of the forums. Thank you so much for the time in reading this and the future help if any can be provided. Have a great night!!!
It looks like you are in the wrong directory. Open a command prompt in
C:\AndroidSDK\platform-tools
Open the platform tools folder. Click on a blank space > hold down the shift key > hit right click > select open command window here. Then enter the commands:
adb devices "to check if your device is connected. also make sure usb debugging is enabled on your phone.
adb remount
adb shell
su
mount -o remount,rw -t rfs /dev/stl5 /system
rm -r /system/app/[AppName].apk
If you want a list of all your /system/apps enter this command
cd /system/app
ls *.apk
This is much easier if you download rom toolbox from the market. All you do is go to /system/app and delete whatever bloatware you dont want.
BUT BE EXTREMELY CAREFUL WHEN DELETING SYSTEM APPS. ONLY DELETE WHAT YOU KNOW IS BLOATWARE OTHERWISE YOU WILL GET FC'S
good luck
Would I still need to follow the steps prior to that and use SuperOneClick to root the device or do I just skip that process and go straight to the cmd prompt?
Also, I followed a tutorial I found for installing the Android SDK that informed me to copy all the files from android-tools to the tools directory and use that instead but I don't know what the use in that is except for maybe a smaller directory name?
EDIT: I tried what you said with and with using SuperOneClick prior to the procedure and the cmd prompt displayed the following text:
*opened cmd promt in C:\AndroidSDK\tools (no files in platform-tools anymore)*
adb devices (it found my device connected)
adb remount (adb remount: no such file or directory exists)
The adb shell and su commands works fine BUT I still hit the endless loop of it trying to explain to me the "usage" of the mount command.
I will look into Rom toolbox as I'm trying to figure this out as well. Thank you.
I strongly recommend you download root explorer or some similar root browser app. Of course though your phone must be rooted. Just try rom toolbox. It has its own root browser within the app along with other useful features. This is probably the easiest way to uninstall the bloatware in your case since you are having issues with adb.
Sent from my Galaxy Nexus using XDA
Thank you!
Okay, I have the suggested "rom toolbox" downloaded from the market and I will try to use that but SuperOneClick does not root the phone deep enough for rom toolbox to see the phone as rooted so...will the "updated.zip" method work for this instead?
I haven't tried it before but I am willing to give it a go if you think it's the best method. If this is the method you recommend, would you happen to have a link to the most recent or atleast most trusted updated.zip rooting method?
CScrivener said:
Thank you!
Okay, I have the suggested "rom toolbox" downloaded from the market and I will try to use that but SuperOneClick does not root the phone deep enough for rom toolbox to see the phone as rooted so...will the "updated.zip" method work for this instead?
I haven't tried it before but I am willing to give it a go if you think it's the best method. If this is the method you recommend, would you happen to have a link to the most recent or atleast most trusted updated.zip rooting method?
Click to expand...
Click to collapse
You can try rooting your phone using this toolbox.
http://forum.xda-developers.com/showthread.php?t=954509
If that does not work for you i will try and find the link to the "one click root program" i use all the time.
Here is an excellent guide to root.
http://forum.xda-developers.com/showthread.php?t=849028
Sent from my Galaxy Nexus using XDA
Here is the program i use. Just remember to have usb debugging enabled on your phone. It really cant get any easier than this.
http://forum.xda-developers.com/showthread.php?t=739300
Sent from my Galaxy Nexus using XDA
So I downloaded the one click program you suggested and the program itself seems to bee pretty straight forward.
I connected phone to computer with debugging on. Opened program and hit one click root. It started doing it's thing...phone rebooted and went into recovery. I started to follow instructions up until I got to where it said install packages. When I clicked it, the phone said installation failed no such file our directory exists.
The phone is looking for the updated.zip file but none exists in the one click folder. There is a root.zip and an unroot.zip...do I need to rename one of them to proceed???
Thank you so much for all the help so far, I feel like I'm so close but just not there yet. You have been an incredible help!
Sent from my SGH-T959 using XDA
CScrivener said:
The phone is looking for the updated.zip file but none exists in the one click folder. There is a root.zip and an unroot.zip...do I need to rename one of them to proceed???
Click to expand...
Click to collapse
The way (Stock) Recovery works is if you are not "Install from SD" then it will look for the file labeled Update.zip. So you can rename only the Root.zip to Update.zip and make sure that is the only thing on your internal SD labeled that or with .zip Put the unroot.zip in a folder for now. Then try again.
Alright, will give that a try when I get home. I thought I read that the program copied the update.zip file to the phone during it's process so I didn't want to do anything to work against that. I will rename one of the files, copy it to the phone and give the one click root another shot. Thank you!
Sent from my SGH-T959 using XDA
CScrivener said:
Alright, will give that a try when I get home. I thought I read that the program copied the update.zip file to the phone during it's process so I didn't want to do anything to work against that. I will rename one of the files, copy it to the phone and give the one click root another shot. Thank you!
Sent from my SGH-T959 using XDA
Click to expand...
Click to collapse
There is no need to rename anything. The program does it all for you. Play close attention to the first screen (green one) if it says update.zip copied successfully it will then reboot your phone to stock recovery. Once you are in stock recovery all you do is click reinstall packages. Keep clicking reinstall packages even if it reboots the first time. To prove my point mount your phone to your pc and check to see if the update.zip is copied onto the root of your into storage. If not well copy the update.zip from the last guide i suggested from above.
Also check to see if the superuser app is installed on your phone. The program also installs that along with the update.zip. If you have superuser then go to the market download rom manager so you could download CWM.
Sent from my Galaxy Nexus using XDA
Alright, so I tried it again once I got home. Didn't work BUT I did see that update.zip was installed into my phone. The sig verification failed, which means I need to change recovery versions to the one that skips sig verification correct?
I'll go search the forums for that since I remember seeing that a little while ago but that is the correct path I need to take at this point in time am I right?
Thank you so much! Big big help!
You can pull the CWR from my signature. Same as before. Put it on your internal labeled update.zip, boot into recovery and and scroll down to Reinstall Packages. Hit it. It will cycle and probably come back to stock recovery. Hit Reinstall Packages again and the stock recovery will go from blue to green (CWR).
Side note, probably from there you will be able to install the Superuser update.zip. Just go to Install from SD card and find it and hit it. The reboot. Might not but the CWR instructions above shoudl work for you.
Well I changed the recovery version using the file from http://forum.xda-developers.com/showthread.php?t=833423 and then used the OneClickRoot and was able to get the update installed (I think). The phone booted up normally, I noticed that SU Permissions was installed so I figure I am rooted correct? WRONG. Rom toolbox says I am not. Is there another way to verify? Should I reinstall Rom toolbox incase it's just bugging out on me?
So I tried using Rom Manager too. Looks as tho SU is not installed correctly, will have to try again I guess.
Cannot install CWR, tried and the recovery text stays blue even after 14 times of reinstalling packages...
This phone will be sent flying across the room sometime tonight I'm guessing. About to erase the entire thing and try starting from scratch again. (Start from Eclair and work my way up maybe)
If you are willing to start from Eclair it would be soooo much easier that all this stuff.
Odin to stock, flash CWR from my signature, go from blue to green and then flash Fishman's Bionix and you are good to go. Simple and way easier than all this mess. Just download Fish's and put it on you SD card somewhere you'll remember. Once in green recovery just scroll to that ROM and flash it per OP.
We've just been trying to Root you since on your OP you said you didn't want to flash a custom ROM.
Well...I'm still trying to avoid flashing Roms (I've upgraded through MiniKies and that's it).
I've only been trying to root just to clean bloatware off but it seems that I must be lacking the technical skills to follow instrcutions properly....nothing is cooperating and even after following all steps nothing wants to work like it should.
Grrrr! One last try to get CWR working before I lose my mind and need to take a break/walk away for a bit.
Ok, so I'm currently back to stock Eclair (ew!!) and about to boot to recovery to install CWR. Wish me luck on that one....
Wooo, CWR up and running! Now I just have to work on a flash maybe or whatever steps were suggested next...I might try the ROM you suggested.
The ROM gets placed on external sdcard and installed from within CWR correct?
Do most ROMs remove bloatware and useless apps?
Yes and are pre-Rooted. Put the ROM.zip on either card. I have a folder that I use. Boot into recovery and get green recovery back. Go to install from SD, find the ROM and flash it per the OP instructions.
Bloat free, pre-Rooted and usually has Voodoo so you can get Voodoo Sound from the market and have a sonic ear-gasm.
Just wanted to say thanks for all the help! I installed the suggested ROM last night and I am very happy with the results thus far. It was alot easier than I thought it would be. Flashing a ROM was MUCH more simpler than the root only decision. Thank you again!
For all you Shotputterz heres the factory image we've been waiting for
assuming you have debug mode enabled, ADB and fastboot working properly
EDIT 1: REUP'D CWM mod
EDIT 2: reordered process to make more sense
Method:
1. Download the Beta CWM mod from rootzwikis credit to birdman EDIT:REUP'ED http://d-h.st/Fdp
2. Using fastboot, DO NOT FLASH Clockwork mod just use the syntax
"fastboot boot 'File path of clockwork mod image'
Note* this will boot directly into the recovery without permanently writing to the recovery and boot partition on the eMMC on the Nexus Qs board
3. Download the posted CWM factory backup posted
4. make the directory on the device and adb push the backup folder (unzipped) to /sdcard/clockworkmod/backup while in CWM recovery
*The device should show up in "adb devices" while in the CWM recovery*
5. *TEXT WILL BE REALLY SMALL! Now navigate with the Scroll wheel to backups and restore and tap the mute button to select.
*IF SOMETHING IS SELECTED IN ERROR THERE IS NO BACK BUTTON JUST REBOOT AND REDO FASTBOOT BOOT*
6. Now select restore and select the image folder
7.blah blah CWM Freaking MAGIC
8. Your Q is back to factory state
If someone wants to PM me or show me how to package this in a nicer CWM zip to install with a script let me know
http://d-h.st/yeo
*Note* I am NOT responsible if you brick your already bricked Nexus Q*
You sir get a beer, since my 2nd (dev) Q won't arrive until later this week, and mine was a shot put until this post.
If you happen to be in NYC before I move to SF, you get three beers.
Hoppy ones.
I am moving to SF
Did the reflash go smoothly?
fiveipads said:
I am moving to SF
Did the reflash go smoothly?
Click to expand...
Click to collapse
No unfortunately it didn't--I blew away all partitions other than bootloader so I can't, to my knowledge at least, push the zip since I can't adb.
I've got factory recovery, boot, system imgs but the system img won't push out because of fastboot's apparent inability to handle files that large (1GB exactly I believe).
...I guess I have to patiently await my second Q but the point of having two was to *use* one and have one for dev... rather than have one as a heavy reminder of my overzealous endeavors...
Hopefully I can give it more time while on this SF trip...
Boot into the cwm bootloader with fastboot without flashing. Adb will be enabled and you can push files the files while your in adb recovery. Try that and flash it.
Sent from my SPH-D710 using xda app-developers app
Does our Q's have internal memory.. if not wouldn't it be possible to run back up of off otg memory stick if recovery would support it
Sent from my Galaxy Nexus using xda premium
fiveipads said:
Boot into the cwm bootloader with fastboot without flashing. Adb will be enabled and you can push files the files while your in adb recovery. Try that and flash it.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
The problem I'm having is that ADB is not responding from CWM... at least not on a Windows machine. The drivers are fine as ADB was working in normal mode before my issue sprung up.
EDIT: As suspected Virtual Ubuntu on a Win host didn't see the device, Physical Ubuntu had no issue. NQ reloaded.
fiveipads said:
Boot into the cwm bootloader with fastboot without flashing. Adb will be enabled and you can push files the files while your in adb recovery. Try that and flash it.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Can we do this by say pushing the file to the download folder and then installing from zip?
And i know slightly off topic but once we've installed some apks for example, what's currently the best interface to use to navigate through the apps and use them?
How do I make a directory on Nexus Q
fiveipads said:
For all you Shotputterz heres the factory image we've been waiting for
assuming you have debug mode enabled, ADB and fastboot working properly
Method:
1. Download the posted CWM factory backup posted
2. make the directory on the device and adb push the backup folder (unzipped) to /sdcard/clockworkmod/backup
http://d-h.st/yeo
Click to expand...
Click to collapse
In step 2 you say make a directory for the file that is posted below. How do I create a directory on the Nexus Q? Currently my Q is stuck in a bootloop after trying to launch CWM from a Galaxy Nexus. If you could post command codes that would be awesome!
I figured it out. You can just follow step #4 and in CWM you can push the CWM Factory img to the /sdcard/Download/ folder and use CWM to unzip and launch.
Could someone please provide me the beta cwm image for Nexus Q? The links are all circular and point to
http://goo.im/devs/birdman/CWM-steelhead-beta.img
Which is dead...
discoltk said:
Could someone please provide me the beta cwm image for Nexus Q? The links are all circular and point to
http://goo.im/devs/birdman/CWM-steelhead-beta.img
Which is dead...
Click to expand...
Click to collapse
I've been trying to get ahold of this image too! Anyone?? anyone?? Bueller???
WildSatchmo said:
I've been trying to get ahold of this image too! Anyone?? anyone?? Bueller???
Click to expand...
Click to collapse
Me as well...not sure why I got this damn thing...lol
The edit didn't prompt an email to me even though I'm following the thread, so those of you looking for the clockworkmod beta image please take note that OP was kind enough to provide a working link to the image.
Thanks fiveipads!
Can someone post full backup please?
caioketo said:
Can someone post full backup please?
Click to expand...
Click to collapse
The link at the bottom still works for me...
http://d-h.st/yeo
..
ok this is really bothering me, i've restored with this factory image several times, and I have to do it again right now and I cannot seem to push this file folder to /sdcard/clockworkmod/backup
what am i doing wrong..
it should be:
adb push NexusQFactoryImage /sdcard/clockworkmod/backup/ (assuming the file is in same folder as adb which it is)
that's it right.... the extracted folder contents in a folder.. not the zip.. so i dont understand why this is not working. Everytime I go to CWM and try to restore it tells me nothing to restore...
what really bothers me is that i've done this a hundred times, and never had this problem..
UKROB86 said:
ok this is really bothering me, i've restored with this factory image several times, and I have to do it again right now and I cannot seem to push this file folder to /sdcard/clockworkmod/backup
what am i doing wrong..
it should be:
adb push NexusQFactoryImage /sdcard/clockworkmod/backup/ (assuming the file is in same folder as adb which it is)
that's it right.... the extracted folder contents in a folder.. not the zip.. so i dont understand why this is not working. Everytime I go to CWM and try to restore it tells me nothing to restore...
what really bothers me is that i've done this a hundred times, and never had this problem..
Click to expand...
Click to collapse
BUMP.. stuck in CWM unable to get a restorable file.. no idea why...
Download OneClickRestore (it's the factory image straight from Google with the needed fastboot files included)
Extract zip to OneClickRestore
Unplug Nexus Q
Plug in Nexus Q and place hand on it til the leds turn red then remove hand
Launch "flash-all.bat" from the OneClickRestore folder
You may need to do a full reset, it's hit or miss
Another option is push & flash (Nexus Q)uantum Singularity Project RTS ROM from CWM and again may need to hard reset.
RTS is
Based on stock 4.0.4 build IAN67K
Deodexed
Zip aligned
init.d Support
bash support
Busybox updated
Prerooted
Superuser
Updated Keymap (Home=Home, End=Back, Delete=Menu, Insert=Visualizer)
Lokifish Marz said:
Download OneClickRestore (it's the factory image straight from Google with the needed fastboot files included)
Extract zip to OneClickRestore
Unplug Nexus Q
Plug in Nexus Q and place hand on it til the leds turn red then remove hand
Launch "flash-all.bat" from the OneClickRestore folder
You may need to do a full reset, it's hit or miss
Another option is push & flash (Nexus Q)uantum Singularity Project RTS ROM from CWM and again may need to hard reset.
RTS is
Based on stock 4.0.4 build IAN67K
Deodexed
Zip aligned
init.d Support
bash support
Busybox updated
Prerooted
Superuser
Updated Keymap (Home=Home, End=Back, Delete=Menu, Insert=Visualizer)
Click to expand...
Click to collapse
The problem with putting Quantum singularity project on is that I can't turn on ADB debug, because i use a bluetooth mouse and keyboard, don't have an OTG mouse/keyboard, so somehow I need to be able to connect with adb to setup a bluetooth connected mouse/keyboard
I was thinking to install stock image, and then without wiping install Quantum SIngularity Project over top to preserve the settings for usb debug, on.
what's confusing to me is that i've restored the stock image many times before, and never had a problem.. that's why im wondering what the problem is.. if im typing something wrong.
I used the OneClickRestore as you said, and im just booting it up now
EDIT: didn't get past boot logo, i'll try again
So just to confirm this OneClickRestore is loading the stock nexus Q img right? I've never used it before I usually manually do it
EDIT: still stuck at the nexus q logo before home screen
do you see any error in my commands of trying to push the stock img folder (original post) to "/sdcard/clockworkmod/backup" ? I've done it many times before never had a problem
The Short Directions
download DroidX2_Root_2012.exe
(self extracting batch file)
watch the video By: Tomsgt
turn phone on
phone- enable usb debugging (menu/system settings/apps/developer options)
connect phone to pc
phone- change usb mode to charge only or pc mode (pull down from top notification bar
pc- start program, (click on DroidX2_Root_2012.exe)
just follow on screen instructions
these are the details, but most is click enter on keyboard
a file is pushed to your phone with adb
phone will reboot to fastboot, all you will see on phone is moto boot logo dualcore screen
click enter on pc
two files will be flashed to phone
phone will reboot
when it has completed reboot
click enter on pc
phone will reboot again
when phone has completed reboot
click enter on pc
files will be pushed to phone with adb
phone will reboot
phone will reboot to android recovery
press both volume buttons when you see ! in a triangle with android andy
wipe cache using volume buttons to scroll, select with power button
when complete, select reboot with power button
Done.
if you want to know more, see the other options, read info below
bhigham/beh and I have modified root method
based on New root method for stock 2.3.4 (621/622) found (Droid2, R2D2)
5 Options
a self extracting batch file Mirror: DevDB backup - 2021
regular batch file
linux/slitaz boot image file, (like ezSBF) Mirror: DevDB backup -2021
manual using adb/moto-fastboot
Voodoo method uses 2.3.4 sbf and other rooting method
I have tested and they work
Watch Video
By: Tomsgt
How this works
phifc said:
There's an exploit in loadpreinstall.sh. It compares md5 sum files of preinstalled apps and if they're different, copies the md5 to the local cache. The preinstall just has an empty file in app/ so it will parse the md5 for it. Instead of an md5 sum, it contains a local.prop that allows adb root shell. So the system thinks it's copying the md5sum to the cache when it bounces off the symlink and overwrites the /data/local.prop, giving adb root on next reboot
Click to expand...
Click to collapse
Basic Instructions/steps for Batch files and Slitaz
first you need to be on 2.3.5/1.3.418
VRZ_MB870_4.5.1A-DTN-200-18_1FF_01.sbf (not .zip) MD5 Sum: 2F746145401FA9E921C1DEC2339A473E
SBF and update.zip here http://forum.xda-developers.com/showthread.php?t=1703640
moto drivers need to be installed (for batch root only)
turn phone on
enable usb debugging (system/apps/developer options)
connect to pc
change usb mode to charge only or pc mode
start program, see instructions specified with the option you chose
there are on screen instruction, but this is what will happen
a file is pushed to your phone with adb
phone will reboot to fastboot, all you will see on phone is moto boot logo dualcore screen
click enter
two files will be flashed to phone
phone will reboot
when it has completed reboot
click enter
phone will reboot
when phone has completed reboot
click enter
files will be pushed to phone with adb
phone will reboot
when phone has completed reboot
click enter
files will be pushed to phone with adb
phone will reboot to recovery
press both volume buttons when you see ! in a triangle with android andy
wipe cache using volume buttons to scroll, select with power button
when complete, select reboot with power button
Done.
when running the batch file or slitaz you may see these errors
rm failed for /data/preinstall_md5/magic.md5 no such file or directory
no root.img.gz no such file or directory
rm failed for /data/preinstall_md5/magic.md5 read only file system
that is fine, it will still work
and bsr/system recovery will be installed
Root DX2 2.3.5 batch file in self extracting exe
DroidX2_Root_2012.exe
download
double click on DroidX2_Root_2012.exe to start
follow onscreen instructions
note: first reboot, goes to a nonlabeled fastboot mode, all you will see is moto boot logo dualcore screen just click enter to flash files
Root DX2 2.3.5 batch file
DX2_Batchroot.7z
download file
extract with 7zip
double click on rootdx2.bat to start
follow onscreen instructions
note: first reboot, goes to a nonlabeled fastboot mode, all you will see is moto boot logo dualcore screen
slitaz boot img, like ezSBF
Droid2_D2G_DX_DX2-RootCD-2012.iso
has options for D2, D2G, DX, and DX2
1KDS said:
Don't let the word Linux scare you, this is just a cd you burn, nothing installs to your pc. Once you burn this CD you are ready to SBF flash anywhere you have a computer, no net connection needed to download any files.
This is an .iso file. It is a complete Linux operating system that you will download, burn to CD (or USB) then boot your pc from CD or USB, this allows your pc to reboot into a different operating system.
Click to expand...
Click to collapse
1KDS said:
Instructions (Mac):
Download .iso
Use Disk Utility (built in) to burn iso file to a CD (instructions)
Shut computer down
Hold c key, push power and hold c until you see the Linux OS start
Hit enter at the yellow "boot baby... boot" screen
You will see yellow dots for 3-5 minutes then the script will start
Instructions (Windows):
Download .iso
Burn iso image to a disk (Instructions, Windows 7 - Vista and XP) or (Load to a USB flash drive)
Reboot PC
Hit F12 (sometimes F8 or esc) during boot to go to boot menu (possibly google search how to boot your specific pc from CDROM)
Select boot from CDROM (or USB if you used a flash drive)
Hit enter at the yellow "boot baby... boot" screen
You will see yellow dots for 3-5 minutes then the script will start
Live USB Instructions (Windows):
(Instructions from pendrivelinux.com)(thanks)
Download UNetBootin for Windows
Download your favorite Linux ISO
Double click the Unetbootin Executable to start the program
(1) Click the Diskimage radio box
(2) browse to select your ISO
(3) Set your target USB drive
(4) click OK to start the creation
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(5) After the USB drive is done select reboot.
(6) During boot enter the boot menu and change USB to boot first, save and reboot.
(7) When booting from UNetbootin select SliTaz
________________________________________________
You will now be in the script and ready to flash.
Click to expand...
Click to collapse
manual method may update this later
you need
moto-fastboot.exe not fastboot.exe found in batch files
adb files found in batch files
Petes root tools http://www.psouza4.com/Droid3/
root.img found in batch files
instructions
extract any .zip or .gz
move all files to same folder like C:root to make it easy
Enable USB debugging on phone
open command prompt
enter
Code:
cd/
cd c:root
adb shell rm /data/preinstall_md5/magic.md5 ( don't worry if you see an error)
adb shell ln -s /data/local.prop /data/preinstall_md5/magic.md5
boot phone to fastboot
run commands
Code:
moto-fastboot.exe flash preinstall root.img
moto-fastboot.exe reboot
let phone boot complete, then reboot again (reboot just replaces the local.prop, but the old local.prop is still in memory, till second reboot)
command
Code:
adb shell
should give you a root prompt # (instead of $)
run petes root tools, zerg rush, or superoneclick
then you rooted
VooDoo Method
1 start with full stock 2.3.4/1.3.380,if you have rooted with anything other than Pete's Root Tools*, have altered/deleted stock file, or if you are already on 2.3.5/1.3.418 you have to SBF
SBF to full stock 2.3.4/1.3.380 (VRZ_MB870_4.5.1A-DTN-150-30_1FF_01.sbf)
read How to SBF an X2, ezSBF DX2, and Common X2 Questions and Answers
if you don't want to lose data, don't wipe data (although it is recommended), unless you bootloop
if you bootloop you have no choice, but to wipe data via stock recovery see Common X2 Questions and Answers
2 Root with Pete's Root Tools
3 install Voodoo OTA Root Keeper, backup su, then temp unroot (keeps backup)
4 install update 2.3.5/1.3.418 , (Blur_Version.1.3.380.MB870.Verizon.en.US.zip)**
a via over the air or
b download, place in sd card root (not in a folder)
md5 B127D3AF93FD6A75C3A3D897C6D0FCD1
and install via stock recovery see Common X2 Questions and Answers
5 restore root with Voodoo
*zergrush may remove stock files, to root, causing update to fail
**updates are named by the version they are updating
md5 checksum windows / android
Magic MD5 Root 2.3.4 for D2, R2D2, D2G, DX and 2.3.5 for DX2 - Google Docs
sd_shadow's [Collection] of Links: FAQs, Guides, Rooting, SBFs, ROMs... - Google Docs
updates
09 aug 12 added video
11 aug 12 edited name to magic md5, added voodoo links
16 Oct 12 new link to Pete's
09 Feb 2013 added clickable link to options files - Google Docs/ reworded some
12 March 2013 moved things around...
27 March 2015 converted thread to DevDB
16 Oct 2021 DevDB Archived new link
16 Oct 2021 Google links no longer working
XDA:DevDB Information
[Root] Droid X2 (MB870) - 2.3.5/1.3.418 magic md5 method, Tool/Utility for the Motorola Droid X2
Contributors
sd_shadow, bhigham, phifc, among others
Version Information
Status: Stable
Created 2015-03-27
Last Updated 2015-03-27
Thank christ, now hopefully some of those older 2.3.4 based roms can be updated. I've been wondering why this has taken so long, glad it's finally out.
They won't be upgraded to this kernel. All the cm based roms are going to stay at 2.3.4 as dzk has said he isn't going to update. And there is only one other currently new ROM and it's already at 2.3.5. Liberty and molten are no longer being developed so they aren't going anywhere.
Sent from my DROID X2 using xda app-developers app
Maximinus I said:
They won't be upgraded to this kernel. All the cm based roms are going to stay at 2.3.4 as dzk has said he isn't going to update. And there is only one other currently new ROM and it's already at 2.3.5. Liberty and molten are no longer being developed so they aren't going anywhere.
Sent from my DROID X2 using xda app-developers app
Click to expand...
Click to collapse
Well then, at least it will make installing Eclipse easier. No more SBF to 2.3.4, root, temp unroot, update, reroot. Now it should just be SBF 2.3.5, root. yay!
thanks for the guide!
Made a video of me doing this if you want to add it to op.
https://www.youtube.com/watch?v=sHVCOkFMYAE&feature=youtube_gdata_player
Sent from my DROID BIONIC using Tapatalk 2
great, will do that
Sent from my DROID2 using xda app-developers app
I've been working on this for 2 days.
I SBF to 2.3.5, then use various methods listed to root it and flash Eclipse. However I lose root, and can't root again. When I try to root Eclipse, root can't be acquired, and no files can be pushed to /system/bin. One more try tonight, then I give up. I'm out of ideas. Can't update and carry root from 2.3.4 with RootKeeper since I don't have service.
Scur827 said:
I've been working on this for 2 days.
I SBF to 2.3.5, then use various methods listed to root it and flash Eclipse. However I lose root, and can't root again. When I try to root Eclipse, root can't be acquired, and no files can be pushed to /system/bin. One more try tonight, then I give up. I'm out of ideas. Can't update and carry root from 2.3.4 with RootKeeper since I don't have service.
Click to expand...
Click to collapse
Use the stock recovery and flash the update from there. Don't need to get the ota. And use root keeper. The update can be found in the link on the op.
Sent from my Nexus 7 using Tapatalk 2
haven't seen this problem, but
you could try removing root files, that are no longer needed
with terminal emulator or adb shell
su
rm /data/preinstall_md5/magic.md5
rm /system/preinstall/md5/magic.md5
rm /system/preinstall/app/magic
Sent from my DROID2 using xda app-developers app
Tomsgt said:
Use the stock recovery and flash the update from there. Don't need to get the ota. And use root keeper. The update can be found in the link on the op.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Nope. I can't update from recovery either. My phone is a bit off, I have a wholethread about it.
sd_shadow said:
haven't seen this problem, but
you could try removing root files, that are no longer needed
with terminal emulator or adb shell
su
rm /data/preinstall_md5/magic.md5
rm /system/preinstall/md5/magic.md5
rm /system/preinstall/app/magic
Sent from my DROID2 using xda app-developers app
Click to expand...
Click to collapse
Nope, doesn't help. I'm going through the process manually using adb right now, at it seems to me that after flashing Eclipse the root.img I'm using isn't valid with Eclipse on 2.3.5. Specifically, here's what I'm doing and here's what's happening...
adb shell ln -s /data/local.prop /data/preinstall_md5/magic.md5 (no error)
adb reboot-bootloader (no error)
moto-fastboot flash preinstall root.img (sending 'reinstall'... okay, whiting 'preinstall'... okay)
moto-fastboot reboot (no error)
adb reboot (no error)
adb shell mount -o remount,rw /dev/block/system /system (mount: Operation not permitted)
So, I think the root image doesn't work with something, though I'm still noobish with it all. Maybe I'll try some different ones...
sd_shadow said:
haven't seen this problem, but
you could try removing root files, that are no longer needed
with terminal emulator or adb shell
su
rm /data/preinstall_md5/magic.md5
rm /system/preinstall/md5/magic.md5
rm /system/preinstall/app/magic
Sent from my DROID2 using xda app-developers app
Click to expand...
Click to collapse
The batch file already attempts to remove those files, right before rebooting into recovery to have the cache wiped. So unless something failed in the batch file, those files should already be deleted.
---------- Post added at 08:41 AM ---------- Previous post was at 08:21 AM ----------
Scur827 said:
Nope. I can't update from recovery either. My phone is a bit off, I have a wholethread about it.
Nope, doesn't help. I'm going through the process manually using adb right now, at it seems to me that after flashing Eclipse the root.img I'm using isn't valid with Eclipse on 2.3.5. Specifically, here's what I'm doing and here's what's happening...
adb shell ln -s /data/local.prop /data/preinstall_md5/magic.md5 (no error)
adb reboot-bootloader (no error)
moto-fastboot flash preinstall root.img (sending 'reinstall'... okay, whiting 'preinstall'... okay)
moto-fastboot reboot (no error)
adb reboot (no error)
adb shell mount -o remount,rw /dev/block/system /system (mount: Operation not permitted)
So, I think the root image doesn't work with something, though I'm still noobish with it all. Maybe I'll try some different ones...
Click to expand...
Click to collapse
I have a thought on something that might work, but it will require a bit of work on your part. One of the steps in rooting batch file, is putting the local.prop file back to normal, which no longer gives adb root access.
If you are indeed able to root stock 2.3.5, then here is what I would suggest trying, (but I don't know if the local.prop file will get overwritten by flashing eclipse)
SBF to stock 2.3.5
Root stock 2.3.5 using any method that will work for you.
Install ES File manager
enable root permissions (up to root, root explorer, and possibly mount file system)
go to /data and open up local.prop (ES Note editor works well)
In the allow all adb line, change the 0 to 1, and save the file.
Reboot, and make sure that file still has 1 for allow all adb.
if so, try flashing eclipse, and see if adb shell has root access. If so, then you can push the necessary files to get root.
Don't know if this will work or not, as I am not sure of where the local.prop file actually comes from, so it might get regenerated. But, if you want to try it, you are welcome to.
I checked to see if local.prop would survive an sbf, and it does not, but I am not sure about with a custom rom.
Very good idea, I'll try it tonight.
Droid X2 > Rooted 2.3.45> Tapatalk
Problems getting it to work
Friends, Thanks for taking the time to post these instructions, I love these forums!
I have a question, I have tries to do this twice using the "Root DX2 2.3.5 batch file in self extracting exe"
But have had no luck, as I am still stock (2.3.5. & 1.3.418 MB870)
It fails to push SU to the phone, and give the errors mentioned in the instructions, but root checker tells me I'm still not rooted.
I feel like I have taken my time, and read through the instructions as I went along, but I guess I'm missing something somewhere.
I (we all) have waited a long time for a root method for the DX2, now it looks like we may have one, but I can't get it to work.
I would be thankful for any advice or help given.
Thanks in advance!
wipe cache, before trying again
be sure to let phone finish booting, before pressing continue
after flashing files in fastoot, phone needs to reboot twice
before pushing su
may want to try slitaz boot img
---> Thank you SD_Shadow!
Thanks my friend, SU granted!
Finally!
Thanks again!
.....Happy camper!
great, did you use the slitaz boot image,
or was it not rebooting the 2 times after flashing
It was hanging on the 2nd reboot.
I just let it sit there this time, and it eventually cycled through to completion.
Now I guess I'm going to either nandroid, or buy Titainium Backup (full),
I want to start learning how to flash roms, while keeping my phone safe and secure.
Thanks again for your advice!
PS~Can you offer a short list of essential root tools/apps? Thanks!
titanium, is a must
if you are going to flashing different roms
sms backup +
is good for backing up call log and texts
and a home launcher
like go launcher, launcher pro, or adw launcher there are more
great for restoring apps and widgets icons after flashing a new rom
remember to backup launcher before
try nova launcher, on ics roms
edit: also will want a file manager or root browser with rw (read/write)
lots of them out there, needed to move system file and change permissions
Sent from my DROID X2 using xda premium
Tomsgt said:
Made a video of me doing this if you want to add it to op.
https://www.youtube.com/watch?v=sHVCOkFMYAE&feature=youtube_gdata_player
Sent from my DROID BIONIC using Tapatalk 2
Click to expand...
Click to collapse
WTF why wont this work, hahahaha i yelled that at my laptop
i had this youtube playing in the background and i hear you say
"well we're going to turn on USB debug..."
facepalm....
thank you for the help.