Related
Ive used programs like TestDisk to get pictures from a "formatted" flash card. I forgot to backup my SMS messages before doing a wipe (backed up everything...). Is there a way I can access the phones built-in memory using software like TeskDisk?
http://www.cgsecurity.org/wiki/TestDisk
androidmonkey said:
Ive used programs like TestDisk to get pictures from a "formatted" flash card. I forgot to backup my SMS messages before doing a wipe (backed up everything...). Is there a way I can access the phones built-in memory using software like TeskDisk?
http://www.cgsecurity.org/wiki/TestDisk
Click to expand...
Click to collapse
Did you do a nandroid? if not then I am pretty sure the answer is no.
That's like formatting my HDD then asking if can i recover all those programs.
Ace42 said:
That's like formatting my HDD then asking if can i recover all those programs.
Click to expand...
Click to collapse
Umm... you do know that when you format your hard drive you can still get some of the data back, right? Unless you use a secure erase program, the data is still on the hard drive. The same goes for flash memory. Format or delete images from your flash card and use TestDisk to see what you can get back. If you havent written anything to the drive, chances are you can get it all back. For your sake, I hope you securely wipe your hdds before throwing/giving them away. That goes for everyone.
Back to the topic. I just want to know how to access the built-in memory where this stuff is stored. Some type of developer tool maybe?
I'd personally like to know what this really has to do with development. You may be looking for some "developer tool" to recover lost data, but this adds nothing to any development going on or anything.
grandomegabosses said:
I'd personally like to know what this really has to do with development. You may be looking for some "developer tool" to recover lost data, but this adds nothing to any development going on or anything.
Click to expand...
Click to collapse
The chances of such a tool existing would be known by the smart developers/coders in this forum
androidmonkey said:
The chances of such a tool existing would be known by the smart developers/coders in this forum
Click to expand...
Click to collapse
Check the rules of the forum. This section isn't meant to ask developers something. It's meant for development.
I would try booting into recovery and then use adb to manually mount your partitions. I would assume you just need to mount the /data partition.. I know this works on my Magic so just check and make sure that you have the right block device if your running on a Dream!
1. open adb shell
2. make a new directory with mkdir "name of new dir"
3. mount /data with mount -t yaffs /dev/block/mtdblock5 "name of new dir"
4. open new terminal/command prompt and use adb pull command as follows
to bring the data partition over to your computer:
adb pull "name of new dir" "name of file to be placed on computer"
5. now see if you have any files and attempt recovery of your sms database
Good Luck
[EDIT] Oh yeah the other guy's are right you should post this type of question in General next time. Fortunately I'm not a **** so I posted how I would try to rescue my stuff and remember Nandroid would have saved your ass
nrmerritt said:
I would try booting into recovery and then use adb to manually mount your partitions. I would assume you just need to mount the /data partition.. I know this works on my Magic so just check and make sure that you have the right block device if your running on a Dream!
1. open adb shell
2. make a new directory with mkdir "name of new dir"
3. mount /data with mount -t yaffs /dev/block/mtdblock5 "name of new dir"
4. open new terminal/command prompt and use adb pull command as follows
to bring the data partition over to your computer:
adb pull "name of new dir" "name of file to be placed on computer"
5. now see if you have any files and attempt recovery of your sms database
Good Luck
[EDIT] Oh yeah the other guy's are right you should post this type of question in General next time. Fortunately I'm not a **** so I posted how I would try to rescue my stuff and remember Nandroid would have saved your ass
Click to expand...
Click to collapse
Thanks nrmerritt, ill give it a try. How do I get root in adb shell via windows? When I try to mkdir, it says "Read-only file system"
Also, I do have a Dream (G1), any ideas which block to use?
Thanks
Are you using Amon_Ra's latest recovery? On my phone when I boot into recovery mode and connect with adb it's already in a root environment.
About the block device I would try the one I posted. You can always just do an "ls" command on the new directory you mounted it on before you copy it to the computer so can you see if/what files are possibly still left.
As a last resort effort you could also try the "dd" command to make an image of the partition while it's still on the phone then copy that to your computer with adb.
One more thing..If you did a wipe and rebooted your phone, your chances are not very good for recovery since the phone would have written a whole bunch of files to the data partition on first boot into Android. Side note, maybe one day Google will incorporate messages into sync and improve our lives a little.
consider this thread deprecated, will keep the original post here for historic sake, and maybe it will help someone down the road
there are way easier ways to do this now
please do not try any of this
if you do decide to do anything on this thread, it is at your own risk
you have been warned
Code:
get:
[url]http://www.droidaftermarket.com/koush//test/inc.zip[/url]
[url]http://www.droidaftermarket.com/koush//test/keys[/url]
1. Boot to recovery with adb (if u dont know how...learn)
2. Run the unrEVOked method to get an adb shell, then do su to get # (if u dont know how...learn)
3. push the inc.zip to /sdcard/update.zip
4. push the keys file to /sdcard/keys
5. Do:
/system/bin/mount -o remount,rw -t yaffs2 /dev/mtdblock3 /system
/system/bin/rm /res/keys
/system/bin/cat /sdcard/keys > /res/keys
/system/bin/ps recovery // note the pid of it
/system/bin/kill <pid>
6. Vol+ and Power to get menu again
7. Vol - then power to run the update.zip
8. Profit!
Big thanks to the unrEVOked team and koush for making this happen!
This method does not stick, it is only good until reboot, but adb works now so have fun
Some problems with accessing /data and some other stuf, but well get it sorted out
i have rooted my phone and was able to get the adb shell working originally; however it seems that now when i get back into adb shell in recovery i am not able to run adb shell to get su....any thoughts? I just continue to get -exec '/system/bin/sh' failed: No such file or directory (2) -
my apologies for being such a n00b...i got it!
WOW
Worked like a charm
Video Tut
http://www.youtube.com/watch?v=BuPFee7IIfM
test key
the test key download is just a bunch of #s do i copy it and put that in a file then push? it doesnt download for me it just opens a window with keys
B-dub25 said:
the test key download is just a bunch of #s do i copy it and put that in a file then push? it doesnt download for me it just opens a window with keys
Click to expand...
Click to collapse
right click on the link and hit save as, remove the .txt extension once it downloads. Look at my video which i have a link for one post above if you need help.
thanks
thanks i`ve been doing three things at once lol got conf. i had to make a program for my finiles c++ programming fun and linux adm. finile too thanks thou
ejlax said:
i have rooted my phone and was able to get the adb shell working originally; however it seems that now when i get back into adb shell in recovery i am not able to run adb shell to get su....any thoughts? I just continue to get -exec '/system/bin/sh' failed: No such file or directory (2) -
my apologies for being such a n00b...i got it!
Click to expand...
Click to collapse
You need to go through the rooting process again, since we can't flash recovery yet, for anyone that was wondering. At least up until the point where you inject the payload.
Has anyone managed to use the nanadroid backup option with this recovery? It seems to backup ok and I can see the backup on my sd card, but if you try and restore, it says:
Code:
Checking MD5 sums...
MD5 mismatch!
This even happens when doing an advanced restore and choosing the file. Here is what is in the Recovery.log file.
Code:
Checking MD5 sums...
md5sum: nandroid.md5: No such file or directory
MD5 mismatch!
Then it just quits. Can you fix it please?
I can get adb to work just about everytime
I can even get recovery to update but still it wont stick no matter what I try. So needless to say anytime I want to try anything I must do the entire procedure over again
There has to be a better way or is this all caused but the nand protection many talk about. Sorry im kindof of newbie to this sort of problem.
All other phones I have rooted for friends usually take once you get it to work. Mytouch 3g fender, a bunch of Moto droids and one N1 so far, and of course my DI
I hope someone figures this out soon then we may start seeing some ROMS, I cant wait for a vanilla rom that I can dress up the way I want and not have all the bloat from SenceUI. Ony thing i'd like to keep would have been htc's weather widget and maybe freindstrean. If I can use it with Sweeter home preview 2. Im so happy with this last release of SH2 its rock solid on my incredible like its been on the moto droid the last 2 or 3 releases for me.
ihtfp69 said:
Has anyone managed to use the nanadroid backup option with this recovery? It seems to backup ok and I can see the backup on my sd card, but if you try and restore, it says:
Code:
Checking MD5 sums...
MD5 mismatch!
This even happens when doing an advanced restore and choosing the file. Here is what is in the Recovery.log file.
Code:
Checking MD5 sums...
md5sum: nandroid.md5: No such file or directory
MD5 mismatch!
Then it just quits. Can you fix it please?
Click to expand...
Click to collapse
Thats basically the hurdle everyone is trying to jump right now. getting a valid nand backup that works, once that is done, custom recovery and roms will be flowing. Im also working on some messing around to try to help out, but on the same hand being careful not to brick since theres no way to restore at this time.
Has anyone heard how progress of making sp recovery stick going? Thanks.
tats_06 said:
Has anyone heard how progress of making sp recovery stick going? Thanks.
Click to expand...
Click to collapse
From what I hear its going well..stay tuned as we might see something from the unrevoked team soon.
760hacker said:
From what I hear its going well..stay tuned as we might see something from the unrevoked team soon.
Click to expand...
Click to collapse
Thanks!!! Thats reassuring.
Can anyone please post a copy of the keys file? The link is down and I can't find it anywhere else either!
I'm just sayin' I hope that we get to see some love and get the CM9 rom for the OB. I would really like to get ICS before the middle of next year. Is there somewhere we can put in some kind of request? or is there a way to use an existing CM9 build to port it to the OB using something from a CM7 build? I've had the phone for about 5 months and getting tired of running 2.2 Froyo just still debating whether to take the plunge and root and put on CM7 or wait it out a little longer. I really have never messed with an android phone before but I read alot on the forum and it seems relatively easy to get the CM7 on there just afraid to root and lose my warranty and something break lol.
Just hack away, don't worry about your warranty. You might get your phone stuck in a bootloop, i've done that several times already, lol. It sucks when it happens, but you can always connect it to your windows pc and restore it to factory settings, unrooted and everything. No one will ever know your phone was rooted
And just to add something, if you can install Android SDK on your computer, you can use ADB Reboot Recovery (if you put recovery on your phone of course). It save me great time.
Sent from my LG-P970 using xda premium
how do u restore the phone? if I know I can unroot it and it won't affect my warrenty ill do it lol I have v10a and have never been able to update higher then that. do I use gingerbreak and the app says it can unroot? like I said if I can unroot it and keep warrenty ill do it
Sent from my LG-P970g using xda premium
I would like Sobralobo to elaborate what he is talking about, sounds like it could save some time after a screwup. However, no matter the condition of your software, you can remove battery, hold vol+ and connect the microusb to your pc. On your pc, you run a LG app, input your imei, and the app will identify your device. It will also tell you if a new software is available. Even if it says it isn't, you can click Options > Recovery (or something like that, i write from my own memory now), and force a update. I'm also pretty sure you'll get V10d or V10e if you do. This process equals to format you phone and install everything from scratch, the way LG intended it to be. All of your personal stuff will be gone, all apps etc. (Obviously, not the stuff you got stored on your sd card, and apps you already bought are linked to your google account and will always follow you
Gingerbreak works for V10a/b afaik, if you get V10c/d/e, you can use this method:
xantaro said:
I got the EU Version of 10c rootet with this method:
1. Download and start SuperoneClick 1.9.5, click Shell Root
2. When it hangs up on a black CMD windows, close this Window. (You should have Shell Root now)
3. Unpack the attached File in your ADB Folder.
4. open a Command Prompt and enter "adb push su /tmp/" & adb push superuser.apk /tmp/"
5. Type "adb shell" ( When Shellroot worked, you should se a "#" on the shell
6. Enter the following commands in shell:
Code:
mount -o rw,remount -t ext3 /dev/block/mmcblk0p8 /system
cat /tmp/su > /system/bin/su
cat /tmp/superuser.apk > /system/app/Superuser.apk
chown root.root /system/bin/su
chmod 06755 /system/bin/su
chown root.root /system/app/Superuser.apk
chmod 0644 /system/app/Superuser.apk
reboot
7. The Phone will now reboot, after reboot it´s rooted again
Click to expand...
Click to collapse
hulkhaugen said:
I would like Sobralobo to elaborate what he is talking about, sounds like it could save some time after a screwup. However, no matter the condition of your software, you can remove battery, hold vol+ and connect the microusb to your pc. On your pc, you run a LG app, input your imei, and the app will identify your device. It will also tell you if a new software is available. Even if it says it isn't, you can click Options > Recovery (or something like that, i write from my own memory now), and force a update. I'm also pretty sure you'll get V10d or V10e if you do. This process equals to format you phone and install everything from scratch, the way LG intended it to be. All of your personal stuff will be gone, all apps etc. (Obviously, not the stuff you got stored on your sd card, and apps you already bought are linked to your google account and will always follow you
Gingerbreak works for V10a/b afaik, if you get V10c/d/e, you can use this method:
Click to expand...
Click to collapse
What Sobralobo said is that just installing Android SDK (Search Google and you get more thousands of tutorials to install SDK and everything you need. Even in O Black section I think there is one with Black drivers and all. Maybe is this one.) you can use "adb reboot recovery" when your Black is in a bootloop or whatever, then you just flash/restore and you are done way faster than reflashing stock firmware. And in certain occasions (for example when you have a certain ROM and you try to flash a modded file in flashable zip that breaks it, you can just flash your ROM without wipe just to fix it and you lose nothing).
PS: You don't even need SDK. There are standalone adb packages, and with LG Black drivers, you can do the same.
This is needed when you mess up with the phone testing all the freaking day like I used to and many others do now.
OK, cool. I'm using adb for rooting and pull/push framework-res.apk and other small mods, didn't know it was compatible with nandroid backups. That can save me a lot of time and trouble next time i mess it up
hulkhaugen said:
OK, cool. I'm using adb for rooting and pull/push framework-res.apk and other small mods, didn't know it was compatible with nandroid backups. That can save me a lot of time and trouble next time i mess it up
Click to expand...
Click to collapse
Well, not directly related to nandroid backups. Just do "adb reboot recovery" (without the "") when you are in trouble. Depending on the situation you will have to input that many times (up arrow and enter fast and many times) if it's bootlooping to find the proper moment when the phone actually receives the command, but it's easy. Once in recovery, you do what you need to do.
aha. so i suppose it won't work with stock bootloader, since LG says "ERROR, LG Security team!!". Still neat that i can restore my backup from bootloader
hulkhaugen said:
aha. so i suppose it won't work with stock bootloader, since LG says "ERROR, LG Security team!!". Still neat that i can restore my backup from bootloader
Click to expand...
Click to collapse
Hmm I think you are partially right. I think in Black bootloader is never changed. When "ERROR, LG Security team!!" is because you really messed up and I believe you have nothing else than flashing. But if you have Clockworkmod recovery (you have if you do nandroid backups), it's worth a try.
I was talking more about bootloops, but maybe when "ERROR, LG Security team!!", if you take the battery off and when put it in again you play with adb reboot recovery, it may work. I can't remember.
antonio1475 said:
Hmm I think you are partially right. I think in Black bootloader is never changed. When "ERROR, LG Security team!!" is because you really messed up and I believe you have nothing else than flashing. But if you have Clockworkmod recovery (you have if you do nandroid backups), it's worth a try.
I was talking more about bootloops, but maybe when "ERROR, LG Security team!!", if you take the battery off and when put it in again you play with adb reboot recovery, it may work. I can't remember.
Click to expand...
Click to collapse
It won't work with adb reboot recovery,I've tried it and failed,won't detect the phone
At least,in my case, it happened when i tried to do a nandroid restore from cm7 to stock (v10a, wiped)
Sent from my heart into yours
Hey everyone,
So about 1 hour ago I attempted to install a kernel onto my rooted HTC One through Team Win Recovery Project. I got onto the kernel and loaded it
Once I was finished i went to reboot my phone and it shows the HTC splash screen and does nothing. I waited but with no response.
I got back onto the recovery screen to find out i no longer had an OS.
My computer (Windows 7 64-bit) cannot detect my HTC One. I have a couple of save backups i had done through TWRP available on my computer, but not on my One.
I have attempted to boot into the HTC screen (Power + Volume down) and tried a factory reset,but it just sent my back to the TWRP.
How can i reload my OS? Im not very experienced with android so step by step instructions would be just great.
Thank you very much
Also, i forgot to mention. I was running the stock ROM.
Youssef26500 said:
Hey everyone,
So about 1 hour ago I attempted to install a kernel onto my rooted HTC One through Team Win Recovery Project. I got onto the kernel and loaded it
Once I was finished i went to reboot my phone and it shows the HTC splash screen and does nothing. I waited but with no response.
I got back onto the recovery screen to find out i no longer had an OS.
My computer (Windows 7 64-bit) cannot detect my HTC One. I have a couple of save backups i had done through TWRP available on my computer, but not on my One.
I have attempted to boot into the HTC screen (Power + Volume down) and tried a factory reset,but it just sent my back to the TWRP.
How can i reload my OS? Im not very experienced with android so step by step instructions would be just great.
Thank you very much
Click to expand...
Click to collapse
Since you can still access recovery..
1. Find a guide on how to 'adb push' or 'adb sideload' a ROM to your phone.
2. I'd recommend a ROM that doesn't require AROMA installer, it makes it a little easier. For now, CM 10.1 will be fine.
3. Once you can access your phone again, put your backups onto your phone from your computer.
4. Restore your backup in recovery.
Or you could just buy a USB-OTG cable and put the backup on a USB and restore in it TWRP.
Sent from my HTC One using XDA Premium 4 mobile app
Or, instead of redbull's approach, you can boot the phone into recovery, then (after reading about how to install and run ADB), use "adb push" to push the recovery files to the phone:
Code:
adb push /path/to/TWRP /data/media/0/TWRP
If that directory doesn't exist, you can probably push to /data/media/TWRP instead. After this, you should see your backups in TWRP and can recover them.
fenstre said:
Or, instead of redbull's approach, you can boot the phone into recovery, then (after reading about how to install and run ADB), use "adb push" to push the recovery files to the phone:
Code:
adb push /path/to/TWRP /data/media/0/TWRP
If that directory doesn't exist, you can probably push to /data/media/TWRP instead. After this, you should see your backups in TWRP and can recover them.
Click to expand...
Click to collapse
I have tried both methods now.
For redbull's approach, as i try to put my phone into ADB Sideload mode through TWRP, TWRP simply says Starting ADB Sideload Feature... but does nothing. I have left it for a little while to no avail.
I have noticed when i put in the command "adb devices" it shows my device as a "host" and i checked on another thread and i believe it should show up as "device". Any ideas?
Worst case scenario i will have to wait a few more days for my OTG Cable to arrive from eBay and then hope that it works from there.
Youssef26500 said:
I have tried both methods now.
For redbull's approach, as i try to put my phone into ADB Sideload mode through TWRP, TWRP simply says Starting ADB Sideload Feature... but does nothing. I have left it for a little while to no avail.
I have noticed when i put in the command "adb devices" it shows my device as a "host" and i checked on another thread and i believe it should show up as "device". Any ideas?
Worst case scenario i will have to wait a few more days for my OTG Cable to arrive from eBay and then hope that it works from there.
Click to expand...
Click to collapse
Once you start the sideload, that's when you command 'adb sideload name_of_rom.zip'. Make sure the rom zip is in the same folder as your adb and fastboot files. Or 'adb sideload ' then drag your zip into the cmd window.
Also, if you're using a usb 3.0 port - they have been known to cause problems.
Sent from my HTC One using XDA Premium 4 mobile app
redbull123 said:
Once you start the sideload, that's when you command 'adb sideload name_of_rom.zip'. Make sure the rom zip is in the same folder as your adb and fastboot files. Or 'adb sideload ' then drag your zip into the cmd window.
Also, if you're using a usb 3.0 port - they have been known to cause problems.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
YAY
Thanks. Finally got my phone running on CyanogenMod, and I was able to get in a factory reset to remove all the data etc from the old rom.
Just a final question though XD
On TWRP I go to the restore option but I don't find anything there. I have put the backup folder in /data/media/0/TWRP but it doesn't appear in the restore option. Any idea of where i should put the files?
Thanks
/data/media/0/TWRP/BACKUPS/
There will be another folder inside the above with a random string of alpha numeric characters. The backups are inside there.
If you perform a backup, you will see its location. Then you can place any others in there also.
Youssef26500 said:
YAY
Thanks. Finally got my phone running on CyanogenMod, and I was able to get in a factory reset to remove all the data etc from the old rom.
Just a final question though XD
On TWRP I go to the restore option but I don't find anything there. I have put the backup folder in /data/media/0/TWRP but it doesn't appear in the restore option. Any idea of where i should put the files?
Thanks
Click to expand...
Click to collapse
Good to hear.. As nobnut says - do a backup then see where it saves it to, then just put your backup in there, then restore :good:
Sent from my HTC One using XDA Premium 4 mobile app
I was trying to install bad seeds sense 6 and sadly did not back up and did not had any old rom as aback up. the rom installed ok but i got this at the end set_metadata_recursive: some changes failed . the phone just keeps rebooting to twrp. i tried to transfer another rom via adb but im not getting my commands right, any other way to add another rom. or way to update my twrp ? please help?
kmacho714 said:
I was trying to install bad seeds sense 6 and sadly did not back up and did not had any old rom as aback up. the rom installed ok but i got this at the end set_metadata_recursive: some changes failed . the phone just keeps rebooting to twrp. i tried to transfer another rom via adb but im not getting my commands right, any other way to add another rom. or way to update my twrp ? please help?
Click to expand...
Click to collapse
Here's what to do (before having to RUU):
boot into TWRP;
connect USB cable;
adb shell into the device;
Code:
adb shell
see if /sdcard is ok (meaning you didn't mistakenly flash entirely the wrong ROM or something):
Code:
ls /sdcard
if the above shows files is a list of tings you recognize (like Downloads, Ringtones, whatever), two things are ok: i) your data area; and ii) your adb is working, then issue these commands (for good measure):
Code:
umount /system
exit
Using TWRP normally (use the touch screen), Wipe the following: system, cache, dalvik-cache, data;
Now, push a ROM file you want, for now I'd suggest one of the Sense 5.5 ROMs -- at least until the Sense 6 ROMs stabilize a bit more and we've had time to settle out all the new idiosynchrasies). Once downloaded, you'll have some zip file, let's call it "myrom.zip" for the purpose of commands (it'll be something different, just use the actual file name instead of myrom.zip below):
Code:
adb push myrom.zip /sdcard
Using the TWRP touch interface, just install the rom from /sdcard/myrom.zip
Just fyi -- the Sense 6 Roms have been exhibiting some oddities for folks in recoveries -- the issue actually is not the ROM, rather in the ext4 file system and some file system metadata bugs when dropping so many files in one shot as the ROM installer zips are doing. I've been debugging this in my TWRP builds and will be putting an option in to cover for the problem (it's deep in the android of ext4, believe it or not -- the kernel is detecting a problem and remounting the file systems read-only and that's what makes the install fail).
Hope this helps.
twrp sideload
tdhite said:
Here's what to do (before having to RUU):
boot into TWRP;
connect USB cable;
adb shell into the device;
Code:
adb shell
see if /sdcard is ok (meaning you didn't mistakenly flash entirely the wrong ROM or something):
Code:
ls /sdcard
if the above shows files is a list of tings you recognize (like Downloads, Ringtones, whatever), two things are ok: i) your data area; and ii) your adb is working, then issue these commands (for good measure):
Code:
umount /system
exit
Using TWRP normally (use the touch screen), Wipe the following: system, cache, dalvik-cache, data;
Now, push a ROM file you want, for now I'd suggest one of the Sense 5.5 ROMs -- at least until the Sense 6 ROMs stabilize a bit more and we've had time to settle out all the new idiosynchrasies). Once downloaded, you'll have some zip file, let's call it "myrom.zip" for the purpose of commands (it'll be something different, just use the actual file name instead of myrom.zip below):
Code:
adb push myrom.zip /sdcard
Using the TWRP touch interface, just install the rom from /sdcard/myrom.zip
Just fyi -- the Sense 6 Roms have been exhibiting some oddities for folks in recoveries -- the issue actually is not the ROM, rather in the ext4 file system and some file system metadata bugs when dropping so many files in one shot as the ROM installer zips are doing. I've been debugging this in my TWRP builds and will be putting an option in to cover for the problem (it's deep in the android of ext4, believe it or not -- the kernel is detecting a problem and remounting the file systems read-only and that's what makes the install fail).
Hope this helps.
Click to expand...
Click to collapse
sorry but i feel so ignorant. i installed the drivers and have the rom ready, but how to i the phone to adb shell. do i go to mount on twrp or on the advance settings adb sideload? when i put adb shell in the command prompt but it says adb not recognized. i would really appreciate your help if you could help me with more detail if possible.
kmacho714 said:
sorry but i feel so ignorant. i installed the drivers and have the rom ready, but how to i the phone to adb shell. do i go to mount on twrp or on the advance settings adb sideload? when i put adb shell in the command prompt but it says adb not recognized. i would really appreciate your help if you could help me with more detail if possible.
Click to expand...
Click to collapse
Goodness -- I thought you were all setup for adb and understood this stuff.
Here's what you need to do *first*, then follow the instructions above after you get adb working. To "adb shell" in to the phone -- you will boot into TWRP, which starts the adb server on the phone. But you use your computer and a "command terminal" window. We have to have this one way or another, so you have to learn. You will plug in your USB cable to the phone and computer, then the commands will work -- yes, they will work with TWRP.
To setup the adb stuff, learn here: http://forum.xda-developers.com/showthread.php?t=2277892 and look for Question 8
adb
tdhite said:
Here's what to do (before having to RUU):
boot into TWRP;
connect USB cable;
adb shell into the device;
Code:
adb shell
see if /sdcard is ok (meaning you didn't mistakenly flash entirely the wrong ROM or something):
Code:
ls /sdcard
if the above shows files is a list of tings you recognize (like Downloads, Ringtones, whatever), two things are ok: i) your data area; and ii) your adb is working, then issue these commands (for good measure):
Code:
umount /system
exit
Using TWRP normally (use the touch screen), Wipe the following: system, cache, dalvik-cache, data;
Now, push a ROM file you want, for now I'd suggest one of the Sense 5.5 ROMs -- at least until the Sense 6 ROMs stabilize a bit more and we've had time to settle out all the new idiosynchrasies). Once downloaded, you'll have some zip file, let's call it "myrom.zip" for the purpose of commands (it'll be something different, just use the actual file name instead of myrom.zip below):
Code:
adb push myrom.zip /sdcard
Using the TWRP touch interface, just install the rom from /sdcard/myrom.zip
Just fyi -- the Sense 6 Roms have been exhibiting some oddities for folks in recoveries -- the issue actually is not the ROM, rather in the ext4 file system and some file system metadata bugs when dropping so many files in one shot as the ROM installer zips are doing. I've been debugging this in my TWRP builds and will be putting an option in to cover for the problem (it's deep in the android of ext4, believe it or not -- the kernel is detecting a problem and remounting the file systems read-only and that's what makes the install fail).
Hope this helps.
Click to expand...
Click to collapse
do i need android sdk? and htc sync? i have the drivers i think? on my device managers it doesnt say adb . just device and on the info it says htc device
thank you
tdhite said:
Goodness -- I thought you were all setup for adb and understood this stuff.
Here's what you need to do *first*, then follow the instructions above after you get adb working. To "adb shell" in to the phone -- you will boot into TWRP, which starts the adb server on the phone. But you use your computer and a "command terminal" window. We have to have this one way or another, so you have to learn. You will plug in your USB cable to the phone and computer, then the commands will work -- yes, they will work with TWRP.
To setup the adb stuff, learn here: http://forum.xda-developers.com/showthread.php?t=2277892 and look for Question 8
Click to expand...
Click to collapse
thanks a lot! those commands work ! just needed to install the drivers . thanks! again