Im using this method...
DLed the drivers and files needed already..
After a connect phone and turn on USB debuging and run CMD
cd C:\FascinateRoot_v02
adb devices
It will state
"List of devices attached
I500******* device"
If you dont see this you are not connected
adb push rage.bin /data/local/tmp/rage.bin
adb shell
cd /data/local/tmp
chmod 0755 rage.bin
This step is important. After you type the next command there will be a pause and you will have to wait until you are kicked out of adb shell. It is important you do not touch your phone or type anything in the command window. If you do don't worry, nothing bad will happen you will most likely have to pull your battery and try to run the command again. If your phone doesn't lock up you can probably unplug it and plug it back in and start back at "adb shell"
./rage.bin
After several seconds the $ prompt will come back
After another 20 seconds or so you will be kicked back to the C:\FascinateRoot_v02 prompt.
adb devices
If your device is still connected proceed,if not give it a min or to and type adb devices again. if the phone is locked up after a couple mins battery pull and start over.
adb shell
You should now be at a # prompt
This mean you have achieved temporary root on the device.
exit
You should now be at the C:\rootfiles prompt again
Type the following commands:
adb push su /sdcard/su
adb push busybox /sdcard/busybox
adb shell
mount -t rfs -o remount,rw /dev/block/stl9 /system
cd /system/xbin
cat /sdcard/su > ./su
cat /sdcard/busybox > ./busybox
chmod 4755 su
chmod 4755 busybox
exit
You should be back at the C:\FascinateRoot_v02 prompt
adb install Superuser.apk
It will now install the Superuser.apk this may take some time while it installs when it is over it will say:
Success-after you see Success hit Ctrl-C Then reset your device
The problem i have is that ADB doesnt recognize my device
tryd different "one click" attempts for it also and same thing
"Device not connected or found or seen"
What can i do?
Help pls
Thnx in Advance
Found in this page to be specific
http://forum.androidcentral.com/ver...-roms-hacks/33899-how-root-74.html#post526222
JeezyMT3G said:
Im using this method...
DLed the drivers and files needed already..
After a connect phone and turn on USB debuging and run CMD
cd C:\FascinateRoot_v02
adb devices
It will state
"List of devices attached
I500******* device"
If you dont see this you are not connected
adb push rage.bin /data/local/tmp/rage.bin
adb shell
cd /data/local/tmp
chmod 0755 rage.bin
This step is important. After you type the next command there will be a pause and you will have to wait until you are kicked out of adb shell. It is important you do not touch your phone or type anything in the command window. If you do don't worry, nothing bad will happen you will most likely have to pull your battery and try to run the command again. If your phone doesn't lock up you can probably unplug it and plug it back in and start back at "adb shell"
./rage.bin
After several seconds the $ prompt will come back
After another 20 seconds or so you will be kicked back to the C:\FascinateRoot_v02 prompt.
adb devices
If your device is still connected proceed,if not give it a min or to and type adb devices again. if the phone is locked up after a couple mins battery pull and start over.
adb shell
You should now be at a # prompt
This mean you have achieved temporary root on the device.
exit
You should now be at the C:\rootfiles prompt again
Type the following commands:
adb push su /sdcard/su
adb push busybox /sdcard/busybox
adb shell
mount -t rfs -o remount,rw /dev/block/stl9 /system
cd /system/xbin
cat /sdcard/su > ./su
cat /sdcard/busybox > ./busybox
chmod 4755 su
chmod 4755 busybox
exit
You should be back at the C:\FascinateRoot_v02 prompt
adb install Superuser.apk
It will now install the Superuser.apk this may take some time while it installs when it is over it will say:
Success-after you see Success hit Ctrl-C Then reset your device
The problem i have is that ADB doesnt recognize my device
tryd different "one click" attempts for it also and same thing
"Device not connected or found or seen"
What can i do?
Help pls
Thnx in Advance
Found in this page to be specific
http://forum.androidcentral.com/ver...-roms-hacks/33899-how-root-74.html#post526222
Click to expand...
Click to collapse
Hm...May sound stupid, but is USB debugging ENABLED? I mean, I see where you posted the directions, which include that, but are you positive it IS enabled? Aside from that, this is a new one to me.
yeah its enabled lol
ive tried it while enabled and disabled
even tryd to disable while plugged in
but to find out i cant lol
......
this is really a bummer cuz im not a noob or anything with
ADB or root
(Rooted G1 MT3g MT3gS D1 D2 DInc and G2)
and this little device has stumped me
here is my firmware info
just to see if thts affecting it
Hardware:i500.04
Model SCH-I500
Firmware 2.1 update1
Baseband
S:i500.04 V.DL09
Kernel 2.6.29
Build Number
SCH-I500.DL09
JeezyMT3G said:
yeah its enabled lol
ive tried it while enabled and disabled
even tryd to disable while plugged in
but to find out i cant lol
......
this is really a bummer cuz im not a noob or anything with
ADB or root
(Rooted G1 MT3g MT3gS D1 D2 DInc and G2)
and this little device has stumped me
here is my firmware info
just to see if thts affecting it
Hardware:i500.04
Model SCH-I500
Firmware 2.1 update1
Baseband
S:i500.04 V.DL09
Kernel 2.6.29
Build Number
SCH-I500.DL09
Click to expand...
Click to collapse
Hm. Damn. Well, you're on stock Eclair, but it should still be working. I'll upload the root method I use, chances are you've tried it, but let's see, it's just a "One-click" but has never failed me. Wait, after re-reading your OP, I think I see your problem. Your One-Click, I think, is outdated. Mine does not have all of this extra crap and directions yours seems to. Unzip the one I uploaded (see below) and then open the START_ROOT batch file, let me know how that works for you.
JeezyMT3G said:
yeah its enabled lol
ive tried it while enabled and disabled
even tryd to disable while plugged in
but to find out i cant lol
......
this is really a bummer cuz im not a noob or anything with
ADB or root
(Rooted G1 MT3g MT3gS D1 D2 DInc and G2)
and this little device has stumped me
here is my firmware info
just to see if thts affecting it
Hardware:i500.04
Model SCH-I500
Firmware 2.1 update1
Baseband
S:i500.04 V.DL09
Kernel 2.6.29
Build Number
SCH-I500.DL09
Click to expand...
Click to collapse
You know, also, if you wanted...You could Odin the stock EB01 with the .pit file, it'd upgrade you to EB01, as well as give you root. Just a thought, if the above did not help.
Ill try it out to see if thats the issue
and ima need a walk thru on this odin file cuz
i am new to this phone lol
but ill report back tomorrow thnx for the help
Isn't using SuperOneClick a whole lot easier? You just plug it in, press root, and wait a couple minutes...just my $0.02
Nemesis2All has a superuser root package zip.file that you can flash from cwm recovery. Just Odin cwm red recovery all 3/30 Fix.tar file and then flash root package zip.file via cwm recovery and you're rooted. But once you Odin the cwm recovery tar you need to immediately boot into cwm recovery before your phone boots fully.
Sent from my SCH-I500 using XDA Premium App
juanv145 said:
Isn't using SuperOneClick a whole lot easier? You just plug it in, press root, and wait a couple minutes...just my $0.02
Click to expand...
Click to collapse
I tryd doin that but it just sits on 'waiting on device' since my computer isn't seeing my phone I don't think any root method will work at this point. ...
I can't even get the SD to mount
I plug in my phone and swipe down notification and hit 'mount' but nothing shows up on my computer
Sent from my SCH-I500 using XDA Premium App
JeezyMT3G said:
I tryd doin that but it just sits on 'waiting on device' since my computer isn't seeing my phone I don't think any root method will work at this point. ...
I can't even get the SD to mount
I plug in my phone and swipe down notification and hit 'mount' but nothing shows up on my computer
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
@JEEZYMT3G read my comment about the the flashable root.zip package from Nemesis2All. It's the most reliable way to root. You don't even have to mount your phone. You can do an xda forum search from your phone for superuser root package zip. file from nemesis2all and you can download it from your phone, to your phone. Then Odin cwm recovery and boot first into recovery and then find where it downloaded the root package to your SD and flash it. You're rooted.
Sent from my SCH-I500 using XDA Premium App
kidserious said:
@JEEZYMT3G read my comment about the the flashable root.zip package from Nemesis2All. It's the most reliable way to root.
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
So its a zip flashable thru stock recovery or what do I need?
I am new this phone so I need to get specific info instead of 'use this file to flash this file to get root' ..don't wanna sound like an a**hole it a d*ck but all the help I can get is greatly appreciated
Sent from my SCH-I500 using XDA Premium App
JeezyMT3G said:
So its a zip flashable thru stock recovery or what do I need?
I am new this phone so I need to get specific info instead of 'use this file to flash this file to get root' ..don't wanna sound like an a**hole it a d*ck but all the help I can get is greatly appreciated
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
Do you know about Odin?
Sent from my SCH-I500 using XDA Premium App
JeezyMT3G said:
So its a zip flashable thru stock recovery or what do I need?
I am new this phone so I need to get specific info instead of 'use this file to flash this file to get root' ..don't wanna sound like an a**hole it a d*ck but all the help I can get is greatly appreciated
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
I sent you a PM.
Sent from my SCH-I500 using XDA Premium App
also another thing
everytime i plug in my phone it installs the drives
everysingle time time
is that bad?
JeezyMT3G said:
also another thing
everytime i plug in my phone it installs the drives
everysingle time time
is that bad?
Click to expand...
Click to collapse
It could be. Are you plugging it in to mount it in order to copy stuff onto your SD?
Sent from an admitted XDA junkie and flashaholic
ive tryd everything
mount to trasfer files and unmout to root
dissabled usb debugging enabled it
reseated the sd card even formated it
still a no go
i read in a couple of forums the "update1 to 09"
messed alot of usb connections on different fascinates
now is this is true how can i root with out a usb connection?
and its not the original cable it came with its another
mini usb i had...
could that be an issue?
JeezyMT3G said:
ive tryd everything
mount to trasfer files and unmout to root
dissabled usb debugging enabled it
reseated the sd card even formated it
still a no go
i read in a couple of forums the "update1 to 09"
messed alot of usb connections on different fascinates
now is this is true how can i root with out a usb connection?
Click to expand...
Click to collapse
You don't actually need a USB connection to root. Download "dropbox" (free from market). Also download dropbox on your computer. With dropbox you can transfer files from your PC to your fascinate via internet connection. Download "New superuser root package your fascinate" from Nemesis2All. (Do an XDA forum search for this) When you have done this call me.
Sent from an admitted XDA junkie and flashaholic
can i use this method?
http://www.droidforums.net/forum/sa...roms-w-root-new-clockwork-updated-2-11-a.html
i have DL dropbox and transfered a files and works flawlessly
now the above method seems PRETTY easy to do
can i go on about using this method?
if so can i flash other roms once in this rom
it says it has clockwork recovery so im guessing yes but just want to be 100% possitive
cuz i been wanting to use MiUi even if its not fully complete ^.^
ok last double check before i try anything
pre:
1. Pull battery from device
2. Open odin on desktop
3. Hold volume down button and plug device into computer
-This will place the device into download mode
4. Verify device shows up in odin
5. Click "PDA" button in odin
6. Select the recovery file below
1st:
Odin this recovery
All 3-30-Fix tar file:
http://forum.androidcentral.com/ver...od-superclean-roms-erasing-cwm-confusion.html
2nd:
Boot into recovery by pushing both vol up vol down buttons
3rd wipe data cache dalvik so on
4th select rom droped in SD
in my case this rom:
http://www.droidforums.net/forum/sa...wifi-sms-gps-themes-bt-a2dp-only-updated.html
5th navigate thru recovery then reboot phone
6th boot up and enjoy my rooted miui right???
or is there anything im missing? thnx
JeezyMT3G said:
pre:
1. Pull battery from device
2. Open odin on desktop
3. Hold volume down button and plug device into computer
-This will place the device into download mode
4. Verify device shows up in odin
5. Click "PDA" button in odin
6. Select the recovery file below
1st:
Odin this recovery
All 3-30-Fix tar file:
http://forum.androidcentral.com/ver...od-superclean-roms-erasing-cwm-confusion.html
2nd:
Boot into recovery by pushing both vol up vol down buttons
3rd wipe data cache dalvik so on
4th select rom droped in SD
in my case this rom:
http://www.droidforums.net/forum/sa...wifi-sms-gps-themes-bt-a2dp-only-updated.html
5th navigate thru recovery then reboot phone
6th boot up and enjoy my rooted miui right???
or is there anything im missing? thnx
Click to expand...
Click to collapse
That's it Jeezy. Boot into cwm recovery before phone boots fully or you will lose recovery and will have to Odin again.
Sent from an admitted XDA junkie and flashaholic
Related
First of all i spent 3 days Trying and failing to root the phone and this is my first tutorial if theirs anything i missed please don't hesitate to point it out.
I am Not responsible for any damage, Explosions, Nuclear Holocaust etc. this root method may cause.
Files you will need below:
1. Engineering Recovery package: Download
2. SuperOneClick v1.7: from Here Thanks to CLShortFuse
3. A GoldCard: To easily create a Goldcard in a couple of minutes without ADB skills or commands, check this thread
4. Stock firmware: Download
5.the ClockworkMod Recovery 2.5.0.7 : Download
5. a know how of how to use ADB.
- There's a good ADB learning guide here: ADB for noobs
(Thanks steviewevie)
Lets Begin
Step 1: Assuming you already created a gold card place it in your phone and mount it place the Stock Firmware zip and update.zip on root. and unzip Engineering Recovery package and place them in your AndroidSDK in the "Platform-tools" folder.
Step 2: unzip and run SuperOneClick v1.7 and make sure your phone is connected via USB with USB Debugging ON. Now press Shell Root and let it run you should get a success pop up.
Step 3: Run ADB and type the following:
adb devices
you should get your devices serial
adb push flash_image /data/local
adb push mtd0.img /data/local
adb shell
cd /data/local
chmod 04755 *
/data/local/flash_image misc /data/local/mtd0.img
Step 4: Once complete, power off the TMobile myTouch Slide
Step 5: Hold the Volume Down button while powering on until the device is in bootloader mode.
Step 6: After a minute or so, the device will prompt to see if you want to run the update. Press the Volume Up button to accept & apply the update.
NOTE: (IF YOU GET A ERROR MSG THAT THE ZIP VERSION IS OLDER THEN THE THE PHONE VERSION YOUR GOLDCARD WAS MADE WRONG!!)
Step 7: Once the device is finished applying the update, it will ask you to reboot. DON'T reboot the device & press the Volume Down button to tell the device not to.
Step 8: Back at the bootloader menu, use Volume Down to highlight Recovery and press the Power button to boot into the recovery.
Step 9: Once in the recovery, you will see a device with a triangle. Press Volume Up & the Power button.
Step 10: Use the Volume Down button to highlight Apply update.zip & press the Power button to select this.
Final Step: After a moment, the TMobile myTouch Slide will boot into the ClockworkMod Recovery.
After that you can now pull battery and insert your main memory card with your desired ROM and Radio Update if you wish and boot into recovery and Happy
Flashing
Enjoy!!
This is how I achieved root! I guess great minds think alike. I was just about to post too, but you beat me to the punch. See the minute I realized with SuperOneClick I could achieve Shell root I could push mtd0.img and flash and then flash the engineering build but you beat me to it! I was thinking about it all day during class and it worked but kudos to you!
Sent from my T-Mobile myTouch 3G Slide using XDA App
iDaZzLeFatHoeZz said:
This is how I achieved root! I guess great minds think alike. I was just about to post too, but you beat me to the punch. See the minute I realized with SuperOneClick I could achieve Shell root I could push mtd0.img and flash and then flash the engineering build but you beat me to it! I was thinking about it all day during class and it worked but kudos to you!
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
I kinda stmbled onto the root method when I was testing a couple
Sent from my T-Mobile myTouch 3G Slide using XDA App
Yeah me too, I was looking through root methods for other phones and I saw SuperOneClick and then realized with that I can get get shell root and then use ADB to push the files needed, and then flash the engineering build.
Sent from my T-Mobile myTouch 3G Slide using XDA App
But, something of note, this will NOT allow you to gain S-OFF. Once you update to stock OTA you will permanently lose the ability to S-OFF unless you have your device replaced by T-Mobile.
Following your instructions and finally I find myself with RC4 again. Thanks a bunch for helping me out.
Yeah nbetcher is right, stuck on HBOOT 1.0 Thanks for the heads up NB
Sent from my T-Mobile myTouch 3G Slide using XDA App
Does rooting this way effectively get rid of the actual official 2.2.1?
or is the esprimg that of 2.2.1 or the old 2.1?
nobreak1970 said:
Does rooting this way effectively get rid of the actual official 2.2.1?
or is the esprimg that of 2.2.1 or the old 2.1?
Click to expand...
Click to collapse
Gets rid of 2.2.1
Sent from my T-Mobile myTouch 3G Slide using XDA App
Thanks much for this. Back to ArayrayMod Revamped...woot!!!
I love messing with stuff so this was fun.
worked great. thanks!
When I get to step 2 and type in
"#cd /data/local
#chmod 04755 *
#/data/local/flash_image misc /data/local/mtd0.img"
should it be repeating what I type? Cause when I reboot, it checks ESPRIMG then says main version is older, but I know I made my goldcard correctly.
maybe my fault
This method worked great, my only problem is that when using rom manager, reboot into recovery doesnt work. It goes to stock recovery but with a question mark. I placed the update.zip on my sdcard and it wont read it pressing volume up and power. I was able to flash cm7, and google apps, but now cant get back into recovery. Not sure what I did in error. I should mention that, trying to stop my wifes complaining about the stock rom, I updated to froyo. I'm familiar with all the tinkering with these phones, I have a G2 rooted, s-off, with CM7 on it. I just don't know about the slide. Any help would be appreciated. Thx in advance.
It should repeat what you type as a confirmation
Sent from my T-Mobile myTouch 3G Slide using XDA App
This method worked great, my only problem is that when using rom manager, reboot into recovery doesnt work. It goes to stock recovery but with a question mark. I placed the update.zip on my sdcard and it wont read it pressing volume up and power. I was able to flash cm7, and google apps, but now cant get back into recovery. Not sure what I did in error. I should mention that, trying to stop my wifes complaining about the stock rom, I updated to froyo. I'm familiar with all the tinkering with these phones, I have a G2 rooted, s-off, with CM7 on it. I just don't know about the slide. Any help would be appreciated. Thx in advance.
Click to expand...
Click to collapse
U have to keep the update.zip witch is the recovery on sd root and select flash update.zip in stock recovery sense we dont have s-off
Sent from my T-Mobile myTouch 3G Slide using XDA App
Chisle31 said:
U have to keep the update.zip witch is the recovery on sd root and select flash update.zip in stock recovery sense we dont have s-off
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
OK, thats what I figured. Thanks alot!
I don't know what I'm doing wrong, if anything. There's a few things that I might not have right:
1: I'm supposed to cd\ to whatever folder I have the Engineering Recovery package saved to, right?
2: I know when I type adb shell, I should get "#" as a response to my input. So should my prompt look like this:
adb shell
# #cd /data/local
# #chmod 04755 *
# #/data/local/flash_image misc /data/local/mtd0.img
or like this:
adb shell
# cd /data/local
# chmod 04755 *
# /data/local/flash_image misc /data/local/mtd0.img
Ok, just want to make sure I got everything here: basically, once you're rooted with this method, you can go back to factory condition by placing the same esprimg.zip from S-Off troubleshoot section and then re-update with HTC Sync, right?
austinbrown92 said:
I don't know what I'm doing wrong, if anything. There's a few things that I might not have right:
1: I'm supposed to cd\ to whatever folder I have the Engineering Recovery package saved to, right?
2: I know when I type adb shell, I should get "#" as a response to my input. So should my prompt look like this:
adb shell
# #cd /data/local
# #chmod 04755 *
# #/data/local/flash_image misc /data/local/mtd0.img
or like this:
adb shell
# cd /data/local
# chmod 04755 *
# /data/local/flash_image misc /data/local/mtd0.img
Click to expand...
Click to collapse
Did you try both? From my experience with command line stuff, the second looks correct. But, someone can correct me if I'm wrong.
txdeathray said:
Ok, just want to make sure I got everything here: basically, once you're rooted with this method, you can go back to factory condition by placing the same esprimg.zip from S-Off troubleshoot section and then re-update with HTC Sync, right?
Click to expand...
Click to collapse
It seems to me like it would - wouldn't hurt to give it a try.
I did try both. It just repeats it when I hit enter. So I turn my phone off, hold vol down + power, let esprimg load, then it says "Main version is older! Do you want to restart?" I choose no, try to apply update.zip, then it says sig verification failed, so i reboot. Not sure what to do
Hey guys, I'm in need of some help with my prime. Just got it a few days ago and rooted it just fine using vipermod. The used OTA root keeper to save root for ICS. After installing ICS, I restored root and everything was fine. Then I noticed that my prime would loose wifi signal ever 2 minutes. I did a factory reset thinking that would fix it (and it did) but now a few things are beyond messed up and i can't figure it out! For one, I cannot access the notifications area (when i tap it, nothing comes up) the home button also does not work at all. so i tried to install cwm so i can re flash the ROM from scratch but now ADB does not see my device AT ALL. i tried everything. i have all the drivers installed and all. I'm at a loss and extremely frustrated. does anyone know whats going on here? how can i get adb to see my prime so i can flash cwm? or is there an alternative way to completely flash the rom? (i also tried the method on asus' website by downloading ICS and placing it on the root of the SD, and still nothing)
You won't be able to install CWM without unlocking the bootloader (and voiding your warranty first). After that, you can no longer flash a ROM from Asus without bricking your device. There is the latest updated ROM in the dev section though.
Good luck!
I did that as well and still nothing :-/
For ADB to work you need to have usb debugging enabled on the tablet....probably a silly thing to ask but always have to check...
scook9 said:
For ADB to work you need to have usb debugging enabled on the tablet....probably a silly thing to ask but always have to check...
Click to expand...
Click to collapse
yup thats enabled as well. when i first got it with 3.2 on it, i plugged it in and drivers installed automatically and adb recognized it right away. now that ics is on it, adb cant see it. i have never ran into this with any android device ever.
Mine did that once and I also had to disable ASUS Sync in settings. After that ADB worked fine.
Update the drivers on your PC
http://forum.xda-developers.com/showthread.php?t=1426502
If you do it right, it will work.
BUT YOU DONT EVEN NEED ADB, LOOK BELOW (I am not advocating not knowing how to adb but lets just fix your prime)
Since you have unlocked your bootloader you can install CWM and just install the latest Virtuous Rom:
If you dont have CWM download Rom Manager from the market, run it, select "Flash recovery" at the top. (btw rom manager just released this today)
*Note that the 'reboot into recovery' option within RM will not reboot into recovery, you must do it manually.. See below
-Backup your apps with Titanium Backup if you want
-Download Virtuous S
-Boot into recovery (directions beneath)
---Power off
---Hold Vol Down (-) and Power until you see spash screen with white text at the top THEN HIT VOL UP (+) within 5 seconds. this will boot into recovery
-if you are coming from stock then: select "wipe data/factory reset"
-Install zip from sdcard, browse for the rom
-Profit?
Guys, thanks a million for all the replies! After uninstalling the drivers and re-installing them then moving my ADB directory to the root of my C drive, it now recognizes my Prime and I was able to flash CWM. I'm now running Virtuous Prime and loving it! Thanks again!
Nissan350 said:
Guys, thanks a million for all the replies! After uninstalling the drivers and re-installing them then moving my ADB directory to the root of my C drive, it now recognizes my Prime and I was able to flash CWM. I'm now running Virtuous Prime and loving it! Thanks again!
Click to expand...
Click to collapse
I would still recommend that you go download Rom Manager and flash the new recovery.
The one in the thread in the dev section is an unofficial port. The one is the Rom Manager is official and works a little better.
Additionally, if you plan to use ADB in the future, there is a simple thing you can do to make it so that within command prompt you can type 'adb' commands ANYWHERE, and not just in the folder that your adb files are..
Right click on Computer--> Properties-->Advanced-->Environmental Variables
Click edit on PATH in the top box if it exists already, add ';' to the end of the previous path and enter the path to your ADB, mine is like
Code:
C:\Users\Mike\Downloads\android-sdk_r16-windows\android-sdk-windows\platform-tools\;
and if it PATH doesnt already exist just create it.
Hope I helped
mtotho said:
I would still recommend that you go download Rom Manager and flash the new recovery.
The one in the thread in the dev section is an unofficial port. The one is the Rom Manager is official and works a little better.
Additionally, if you plan to use ADB in the future, there is a simple thing you can do to make it so that within command prompt you can type 'adb' commands ANYWHERE, and not just in the folder that your adb files are..
Right click on Computer--> Properties-->Advanced-->Environmental Variables
Click edit on PATH in the top box if it exists already, add ';' to the end of the previous path and enter the path to your ADB, mine is like
Code:
C:\Users\Mike\Downloads\android-sdk_r16-windows\android-sdk-windows\platform-tools\;
and if it PATH doesnt already exist just create it.
Hope I helped
Click to expand...
Click to collapse
Will do! Thanks for the PATH tip! Wish I knew about it earlier lmao.
Nissan350 said:
Will do! Thanks for the PATH tip! Wish I knew about it earlier lmao.
Click to expand...
Click to collapse
yup lol, makes it so you can do it from any directory.. absolutely necessary if you use adb frequently
mtotho said:
yup lol, makes it so you can do it from any directory.. absolutely necessary if you use adb frequently
Click to expand...
Click to collapse
Awsome, thanks again man
So, i was in recovery to restore to a previous backup. I was wiping my system to prevent errors but unfortunately i wiped EVERYTHING, including the backup and the OS. So, i kept it in recovery till i got home hoping to just mount my storage and transfer a ROM over and ten install..sounds easy enough. However, i plug my phone in and click mount storage and it doesn't mount with twrp, or even clock work mod.
Soo....i have no OS, can't mount my storage..and i'm stuck.
Can i flash a ROM through command line? If so, how? And why isin't my Droid DNA mounting?
Wttttfff help asap please!
Aaannd...now i'm stuck in the boot screen and it won't turn off.
Just use either adb push or adb sideload
Sent from my HTC6435LVW using xda app-developers app
Nice! forgot about those commands, however it's telling me that adb is not a recognized command. I've forgotten how to fix that? Can you help with that?
Adb sideload starts up and says daemon not running, then start's it succesfully. then says device not found. I'm pretty sure i don't have the right drivers for my DNA, can you point me in the right direction for that?
I really need help, i don't think i can even turn on usb debugging because i have no OS to boot into.
FIXED. I got this
soundofcarnage said:
FIXED. I got this
Click to expand...
Click to collapse
What steps did you take?
I looked a little more into ad sideload. I sideloaded a zip of the Rom I wanted and then chose to flash through sideload.
You pretty much:
Download your rom and put it into your fasboot directory oin your.
Boot into recovery and choose "install" then "install zip from sideload"
It should say to now type into command promt "adb sideload romfilrname"
It then loads it, and you just hit flash after it loads.
soundofcarnage said:
I looked a little more into ad sideload. I sideloaded a zip of the Rom I wanted and then chose to flash through sideload.
You pretty much:
Download your rom and put it into your fasboot directory oin your.
Boot into recovery and choose "install" then "install zip from sideload"
It should say to now type into command promt "adb sideload romfilrname"
It then loads it, and you just hit flash after it loads.
Click to expand...
Click to collapse
with no o/s and im pretty much on the same boat, how did you get adb to read your device? when i type in adb devices it gives me a blank list of devices
It worked for without ever actually listing my device.
soundofcarnage said:
It worked for without ever actually listing my device.
Click to expand...
Click to collapse
Oh okay, this is basically my last step. Im stuck on cannot read sideload. is it because of the romfilename? or am i missing something.
IceAzures said:
Oh okay, this is basically my last step. Im stuck on cannot read sideload. is it because of the romfilename? or am i missing something.
Click to expand...
Click to collapse
Are you adding .zip after filename?
Sent from my HTC6435LVW using Tapatalk 2
rsims26 said:
Are you adding .zip after filename?
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
no ill try that
IceAzures said:
no ill try that
Click to expand...
Click to collapse
That's kinda necessary.
Sent from my HTC6435LVW using xda app-developers app
Sorry if i am making things complicated. I havent done adb since January to unlock bootloader and install custom recovery
IceAzures said:
Sorry if i am making things complicated. I havent done adb since January to unlock bootloader and install custom recovery
Click to expand...
Click to collapse
you have old adb
just adb push it and then flash in recovery
adb push some_damn_rom.zip /sdcard/
beaups said:
you have old adb
just adb push it and then flash in recovery
adb push some_damn_rom.zip /sdcard/
Click to expand...
Click to collapse
The longer this happens the more i feel like an idiot. I can't push anything either. Where in sdk is a new adb and how much more will it help?
IceAzures said:
The longer this happens the more i feel like an idiot. I can't push anything either. Where in sdk is a new adb and how much more will it help?
Click to expand...
Click to collapse
hmm thought I replied.
cwr has issues with adb
download twrp recovery and flash it - http://techerrata.com/browse/twrp2/dlx
beaups said:
hmm thought I replied.
cwr has issues with adb
download twrp recovery and flash it - http://techerrata.com/browse/twrp2/dlx
Click to expand...
Click to collapse
You did, there's 2 different threads he's posting in.
Sent from my HTC6435LVW using xda app-developers app
Hi,
I'm not a newbie to Android by any measure, but this is my wife's phone, not mine (I have a Nexus 4) so I'm not familiar with a lot of the LG stuff.
Anyways, I rooted her phone to get rid of some of the bloatware and the stupid Qslide thing, and also to edit the build.prop so Netflix will have the Chromecast button. I had deleted quite a few bloatware system apps, and rebooted, everything was fine. I deleted a few more, then edited the build.prop. Rebooted.
Now it shows the LG logo, but then the screen goes blank, but is still on (you can see the backlight) and never boots. I only removed a few more of the LG and Tmobile apps and edited the model and manufacturer in the build.prop
Do I have any easy options to fix this? Or do I need to flash the KDZ?
Flash kdz then install cwm then backup the stock ROM THEN do your mods. Every time every phone. Good luck
Sent from my LG-P769(20F) using the xda-developers app. If I helped you please hit the "thanks" button.
swm5126 said:
Hi,
I'm not a newbie to Android by any measure, but this is my wife's phone, not mine (I have a Nexus 4) so I'm not familiar with a lot of the LG stuff.
Anyways, I rooted her phone to get rid of some of the bloatware and the stupid Qslide thing, and also to edit the build.prop so Netflix will have the Chromecast button. I had deleted quite a few bloatware system apps, and rebooted, everything was fine. I deleted a few more, then edited the build.prop. Rebooted.
Now it shows the LG logo, but then the screen goes blank, but is still on (you can see the backlight) and never boots. I only removed a few more of the LG and Tmobile apps and edited the model and manufacturer in the build.prop
Do I have any easy options to fix this? Or do I need to flash the KDZ?
Click to expand...
Click to collapse
Yes, offline flash the kdz. Always backup your rom whenever you so something like that.
Sent from my LG-P769 using Tapatalk 4
If it's just the build.prop causing it not to boot, you can flash (with fastboot) the boot.img for the kdz you are on. Look at my signature on how to extract it.
If that doesn't work, flash the ice cream x & u partitions for p769 in fastboot, and then run offline flash
Fastboot info and help
http://forum.xda-developers.com/showthread.php?p=43703982
Install the locked bootloader cwm
http://forum.xda-developers.com/showthread.php?t=2095825
And use this busybox
https://play.google.com/store/apps/details?id=com.bitcubate.root.busybox.complete
Next time make a backup (make sure the backup is good, try to restore it)
CM 10.1 P769
kuma82 said:
If it's just the build.prop causing it not to boot, you can flash (with fastboot) the boot.img for the kdz you are on. Look at my signature on how to extract it.
If that doesn't work, flash the ice cream x & u partitions for p769 in fastboot, and then run offline flash
Fastboot info and help
http://forum.xda-developers.com/showthread.php?p=43703982
Install the locked bootloader cwm
http://forum.xda-developers.com/showthread.php?t=2095825
And use this busybox
https://play.google.com/store/apps/details?id=com.bitcubate.root.busybox.complete
Next time make a backup (make sure the backup is good, try to restore it)
CM 10.1 P769
Click to expand...
Click to collapse
Get outta here kuma, no one wants you here. -___- lol im jk.
Sent from my LG-P769 using Tapatalk 4
Lol, okay
NOT!
CM 10.1 P769
kuma82 said:
Lol, okay
NOT!
CM 10.1 P769
Click to expand...
Click to collapse
Thanks for the suggestions guys. I've tried the offline KDZ flashing it, but I can't get my computer (tried two actually, mine and my wife's laptop) to do anything once its in the S/W Upgrade mode. I used the method previously to update her phone the JB when Tmobile pulled the update. Since then it downloaded the most recent OTA. But anyways, I don't know why it wont work. It just continally tells me that my phone isn't connected, even though I'm using the latest drivers and the phone shows up correctly in the device manager. It's driving me nuts since it worked previously!
Any ideas?
swm5126 said:
Thanks for the suggestions guys. I've tried the offline KDZ flashing it, but I can't get my computer (tried two actually, mine and my wife's laptop) to do anything once its in the S/W Upgrade mode. I used the method previously to update her phone the JB when Tmobile pulled the update. Since then it downloaded the most recent OTA. But anyways, I don't know why it wont work. It just continally tells me that my phone isn't connected, even though I'm using the latest drivers and the phone shows up correctly in the device manager. It's driving me nuts since it worked previously!
Any ideas?
Click to expand...
Click to collapse
What variant do you have 769? Flash recovery.img in fastboot.
Sent from my LG-P769 using Tapatalk 4
swm5126 said:
Hi,
I'm not a newbie to Android by any measure, but this is my wife's phone, not mine (I have a Nexus 4) so I'm not familiar with a lot of the LG stuff.
Anyways, I rooted her phone to get rid of some of the bloatware and the stupid Qslide thing, and also to edit the build.prop so Netflix will have the Chromecast button. I had deleted quite a few bloatware system apps, and rebooted, everything was fine. I deleted a few more, then edited the build.prop. Rebooted.
Now it shows the LG logo, but then the screen goes blank, but is still on (you can see the backlight) and never boots. I only removed a few more of the LG and Tmobile apps and edited the model and manufacturer in the build.prop
Do I have any easy options to fix this? Or do I need to flash the KDZ?
Click to expand...
Click to collapse
boot into stock recovery "vol+"&"home"+"power"
adb should work and you can :
adb push busybox /tmp
adb push build.prop /tmp
adb shell
try "su" or "/system/bin/su" or "/system/xbin/su"
chmod 755 /tmp/busybox
/tmp/busybox mount -o remount,rw -t auto /system
/tmp/busybox cp /tmp/build.prop /system
/tmp/busybox chmod 644 /system/build.prop
swm5126 said:
Thanks for the suggestions guys. I've tried the offline KDZ flashing it, but I can't get my computer (tried two actually, mine and my wife's laptop) to do anything once its in the S/W Upgrade mode. I used the method previously to update her phone the JB when Tmobile pulled the update. Since then it downloaded the most recent OTA. But anyways, I don't know why it wont work. It just continally tells me that my phone isn't connected, even though I'm using the latest drivers and the phone shows up correctly in the device manager. It's driving me nuts since it worked previously!
Any ideas?
Click to expand...
Click to collapse
Sorry I didn't break it down enough for you. You have to get fastboot up and running. Jellybean does not operate when starting in S/W mode, that's why you get the connection problem. Now ice cream, does operate when starting in the S/W upgrade mode. With fastboot you can flash everything you need to get the offline flash working. These three links are all the info you need.
Lelus fastboot
Select the option to flash x & u for p769
1. http://forum.xda-developers.com/showthread.php?p=41768774
Help if you can't get fastboot installed
2. http://forum.xda-developers.com/showpost.php?p=43210006&postcount=15
Info on how to use fastboot manually. Not really needed because lelus has everything needed in the first link.
3. http://forum.xda-developers.com/showthread.php?p=43642515
Please read each thread before starting and read the instructions txt found in Lelus fastboot zip
Sorry I told you flashing the boot.IMG will help(was thinking of default.prop), I just remembered the build.prop is in the system partition.
CM 10.1 P769
---------- Post added at 11:00 PM ---------- Previous post was at 10:52 PM ----------
Lelus said:
boot into stock recovery "vol+"&"home"+"power"
adb should work and you can :
adb push busybox /tmp
adb push build.prop /tmp
adb shell
try "su" or "/system/bin/su" or "/system/xbin/su"
chmod 755 /tmp/busybox
/tmp/busybox mount -o remount,rw -t auto /system
/tmp/busybox cp /tmp/build.prop /system
/tmp/busybox chmod 644 /system/build.prop
Click to expand...
Click to collapse
Thanks for sharing, I didn't know stock recovery allowed ADB commands :thumbup:
CM 10.1 P769
swm5126 said:
Hi,
Do I have any easy options to fix this? Or do I need to flash the KDZ?
Click to expand...
Click to collapse
Factory LG mobile support tool has an option to "update recovery" in top right menu. This will download latest factory rom via internet and reflash phone in software update mode to reset everything.
http://www.softpedia.com/get/Mobile-Phone-Tools/Others/LGMobile-Support-Tool.shtml
Works well.
might have to set phone into software update mode by pressing vol up and then inserting usb cable..
kuma82 said:
Please read each thread before starting and read the instructions txt found in Lelus fastboot zip
Click to expand...
Click to collapse
Ok, I got the timing down and fastboot seems to come up, but after I can see the logo on my phone with the v 0.5, the script just says < waiting for device >. Thats where it should flash the ICS xloader? Or am I missing something and I should flash the JB images with fastboot? Where can I get the images?
swm5126 said:
Ok, I got the timing down and fastboot seems to come up, but after I can see the logo on my phone with the v 0.5, the script just says < waiting for device >. Thats where it should flash the ICS xloader? Or am I missing something and I should flash the JB images with fastboot? Where can I get the images?
Click to expand...
Click to collapse
Just kidding, got it figured out. Flashed the ICS xloader. Looks like its letting me restore finally! Thanks!
Hello everyone,
I have been searching in vain for a while now to find a solution to my problem and I fear that I may have done something daft to my phone.
I am using a HTC One X+ that was unlocked, s-off and rooted for about a year, i had TWRP and stock android 4.1.1. For ages I have been getting an update alert saying a software update is ready and i think it was some Vodafone update (1.17.161.7). Whenever i accepted and tried to install this it would obviously reboot into TWRP and then the update would fail. This was fine until last night when I decided to install it through TWRP, it said it failed again and i rebooted to find that WiFi wouldnt turn on, my phone was no longer rooted or s-off and that I get no signal. I tried to re-root it but command prompt on the computer or HTC Sync wouldnt recognise my device however it was appearing as HTC One X+ in My Computer and i could access the internal storage.
I restarted into recovery and managed to flash a new root using twrp and the root file using the unlockr.com - how to root the htc one x
Then thinking it was a ROM issue i downloaded and installed InsertCoin Evolution ONE X+ 5.0-6 Sense 5 Android 4.2.2.
This all went through ok however when i reboot from this install it just sticks at the HTC Quietly Brilliant screen. I wiped everything using twrp beforehand.
When i restart into bootloader, it says unlocked, S-On and HBOOT -1.30.0000
Not sure what else to do as now i have no ROM, i read that you have to partition the SD card for InsertCoin to work but the option to partition SD card isnt there in my TWRP (ver. 2.3.3.0)
Any help to even reset my phone back to basic stock everything would be amazing, i have a Titanium Backup of most of my stuff saved btw.
Thanks to anyone who can help.
Did you flash the insert coin boot.img?
Sent from my HTC One X+ using Tapatalk
AndroHero said:
Did you flash the insert coin boot.img?
Sent from my HTC One X+ using Tapatalk
Click to expand...
Click to collapse
No I just copied the whole zip file to the SD card section and installed it from there - ive encountered a new problem now in the fact that my computer no longer can recognise the phone via USB - it still appears in device manager but cant access the sd card and the sd card got wiped by twrp so now i dont have any way of getting things onto the phone that i know of. It just says - failed to open usb master mode in the bootloader. How could i get the computer to recognise the phone again so i can transfer it back onto it and try installing insertcoin again? Really hoping i havent managed to make my phone useless as ive had to dig out the old Nokia 6230 from the drawer haha!
Thanks.
EDIT - Now seen the instruction to flash the boot.img - what a fool i am. Now i need to get it recognised by USB again so i can transfer the zip file to it and go again.
maxwell689 said:
No I just copied the whole zip file to the SD card section and installed it from there - ive encountered a new problem now in the fact that my computer no longer can recognise the phone via USB - it still appears in device manager but cant access the sd card and the sd card got wiped by twrp so now i dont have any way of getting things onto the phone that i know of. It just says - failed to open usb master mode in the bootloader. How could i get the computer to recognise the phone again so i can transfer it back onto it and try installing insertcoin again? Really hoping i havent managed to make my phone useless as ive had to dig out the old Nokia 6230 from the drawer haha!
Thanks.
Click to expand...
Click to collapse
Now seen the instruction to flash the boot.img - what a fool i am. All I need now is to get it recognised by USB again so i can transfer the zip file back and go again.
maxwell689 said:
Now seen the instruction to flash the boot.img - what a fool i am. All I need now is to get it recognised by USB again so i can transfer the zip file back and go again.
Click to expand...
Click to collapse
Without a rom installed you're not able to acces the internal memory of your phone directly. You have to use "adb sideload" command to transfer a rom onto your phone. Look in the General and/or Q&A forum of this device, there are enough guides or topics on how to solve this "problem".
maxwell689 said:
Now seen the instruction to flash the boot.img - what a fool i am. All I need now is to get it recognised by USB again so i can transfer the zip file back and go again.
Click to expand...
Click to collapse
Hi use this link..may be useful (http://forum.xda-developers.com/showthread.php?t=2066390) by the way reaper90 is right you need to sideload the rom..
In TWRP:
1-wipe everything
2-goto advance in twrp
3-select sideload
4-navigate to the folder where you have adb.exe, adbwinapi.dll, adbwinusbapi.dll and fastboot.exe. and make sure to keep the rom and its image; bootimg there.
5-then in command prompt write (adb sideload *name of the rom*.zip) make sure the name is a letter.
6- also make sure to keep the screen alive and not let it goto sleep while adb sideload is working.
7- rom will start setup once sideload is 100%.
Hope this helps. Goodluck.
Optimus said:
Hi use this link..may be useful (http://forum.xda-developers.com/showthread.php?t=2066390) by the way reaper90 is right you need to sideload the rom..
In TWRP:
1-wipe everything
2-goto advance in twrp
3-select sideload
4-navigate to the folder where you have adb.exe, adbwinapi.dll, adbwinusbapi.dll and fastboot.exe. and make sure to keep the rom and its image; bootimg there.
5-then in command prompt write (adb sideload *name of the rom*.zip) make sure the name is a letter.
6- also make sure to keep the screen alive and not let it goto sleep while adb sideload is working.
7- rom will start setup once sideload is 100%.
Hope this helps. Goodluck.
Click to expand...
Click to collapse
Hi, thanks very much for the responses - its much appreciated.
Nothing happens when i type that command, a load of text appears in cmd prompt showing all the adb commands and thats it, i have searched for this problem and found this on twrp website as a possible solution "You will need version 1.0.29 or higher. You can find your current version by typing "adb version" at the command line" My version says 1.0.26 I have tried to update this but cant seem to find a way to do it, would that be an issue?
I think once ive managed to sideload the zip i should be good to go its just getting to that point that seems to be stumping me at the moment.
maxwell689 said:
Hi, thanks very much for the responses - its much appreciated.
Nothing happens when i type that command, a load of text appears in cmd prompt showing all the adb commands and thats it, i have searched for this problem and found this on twrp website as a possible solution "You will need version 1.0.29 or higher. You can find your current version by typing "adb version" at the command line" My version says 1.0.26 I have tried to update this but cant seem to find a way to do it, would that be an issue?
I think once ive managed to sideload the zip i should be good to go its just getting to that point that seems to be stumping me at the moment.
Click to expand...
Click to collapse
Dont sweat it. They understood you wrong.
Guys what he wants to do is copy the file FROM the SDCARD TO the PC.
First you will need to know where the location of your rom then type in the following commands:
Code:
adb devices
If you device is not detected then try to run the CMD as an administrator and try again
then:
Code:
adb pull {location without the curly brackets}
For example if its on the SDCard then:
Code:
adb pull /sdcard/rom.zip
It will paste the file to the folder where the adb is found
Then just open the zip file and get out the boot.img and flash it using fastboot
Hope this helps you out.
Ghand0ur said:
Dont sweat it. They understood you wrong.
Guys what he wants to do is copy the file FROM the SDCARD TO the PC.
First you will need to know where the location of your rom then type in the following commands:
Code:
adb devices
If you device is not detected then try to run the CMD as an administrator and try again
then:
Code:
adb pull {location without the curly brackets}
For example if its on the SDCard then:
Code:
adb pull /sdcard/rom.zip
It will paste the file to the folder where the adb is found
Then just open the zip file and get out the boot.img and flash it using fastboot
Hope this helps you out.
Click to expand...
Click to collapse
Hey, thanks.
No they got me correctly, there is absolutely nothing on my phone at all and I need to get my new ROM zip file from the PC to the phone so that I can install it. I am currently downloading SDK manager to try and update my adb to 1.0.29 or higher and will see if that works.
maxwell689 said:
Hey, thanks.
No they got me correctly, there is absolutely nothing on my phone at all and I need to get my new ROM zip file from the PC to the phone so that I can install it. I am currently downloading SDK manager to try and update my adb to 1.0.29 or higher and will see if that works.
Click to expand...
Click to collapse
Ok, i downloaded the hasoon toolkit and select ADB Sideload a ROM and it says "error device not found" in the command prompt. I am in ADB Sideload mode in TWRP with it plugged in via USB so dont know what to try next.
maxwell689 said:
Ok, i downloaded the hasoon toolkit and select ADB Sideload a ROM and it says "error device not found" in the command prompt. I am in ADB Sideload mode in TWRP with it plugged in via USB so dont know what to try next.
Click to expand...
Click to collapse
Lol.. Well, as i said try to run the Toolkit/cmd as administrator and try different usb ports.. It took me 5 minutes on windows 8 for the adb to properly read the device , had to try different usb ports, unplug , replug, and so on..
maxwell689 said:
Ok, i downloaded the hasoon toolkit and select ADB Sideload a ROM and it says "error device not found" in the command prompt. I am in ADB Sideload mode in TWRP with it plugged in via USB so dont know what to try next.
Click to expand...
Click to collapse
Hi goto htcdev n download the latest sdk
Sent from my HTC One X+ using xda app-developers app
---------- Post added at 09:08 PM ---------- Previous post was at 09:07 PM ----------
I will try to send I over the files for command prompt tomorrow.
Sent from my HTC One X+ using xda app-developers app
Optimus said:
Hi goto htcdev n download the latest sdk
Sent from my HTC One X+ using xda app-developers app
---------- Post added at 09:08 PM ---------- Previous post was at 09:07 PM ----------
I will try to send I over the files for command prompt tomorrow.
Sent from my HTC One X+ using xda app-developers app
Click to expand...
Click to collapse
Right ive manged to download the latest sdk and then after much unplugging and plugging and right clicking things in device manager its recognised my phone enough to sideload and install the ROM. I have also managed to fastboot the boot.img file as well after 3 attempts but it finally worked so i have a phone back again!! Thanks everyone here!!! Now to upload my titanium backup of apps, sadly i think ive lost all my photos thou
But thanks again to all. Sorry if ive been a bit noob but its been a good learning curve for me as i never had these issues with my HTC desire
maxwell689 said:
Right ive manged to download the latest sdk and then after much unplugging and plugging and right clicking things in device manager its recognised my phone enough to sideload and install the ROM. I have also managed to fastboot the boot.img file as well after 3 attempts but it finally worked so i have a phone back again!! Thanks everyone here!!! Now to upload my titanium backup of apps, sadly i think ive lost all my photos thou
But thanks again to all. Sorry if ive been a bit noob but its been a good learning curve for me as i never had these issues with my HTC desire
Click to expand...
Click to collapse
Thats great news that all is well now..feel free to post.. and dont forget to press the Thanks button