Related
hi there
i really need your help. i'm trying to install android on my HTC TyTnII. But i'm having problems to install.
can you please help me to get Android run on my Kaiser?
Right now i'm running the windows mobile 6.1. I want to install Android as a secondary OS.
i followed this installation guide.
androidonhtc.com/wiki/Installing_Android
1. I went to this link to download files.
androidonhtc.com/wiki/Latest_Builds_%28Kaiser%29
2. I downloaded the basefiles-20091116.zip
vogue-android.googlecode.com/files/basefiles-20091116.zip
3. Unzipped this zip file. Renamed the default-kaiser.txt to default.txt and moved the whole folder "android" to my storagecard.
4. then i downloaded the haretinstall.zip and unzipped that file as well. I moved the folder "andboot" to my storagecard.
sourceforge.net/projects/androidhtc/files/2010-02-20/haretinstall.zip/download
5. then i downloaded the polymod_2.1g.zip and unzipped that file. I moved the file "androidinstall.tar" to my storagecard as well.
ponack.net/poly/2.1g/polymod_2.1g.zip
6. i clicked than on "haret.exe" and clicked on Run. the android started to load but then it stops. It gives me this error.
--------
....
Checking for partition...
s2fsck 1.41.4 (27-Jan-209)
ext2fs_check_if_mount: No such file or directory while determing whether /dev/block/loop0 is mounted.
/dev/block/loop0 was not cleanly unmounted. check for ced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/loop0: 11/65536 files (0.0% non-contigous), 10335/262144 blocks
losetup: /dev/block/loop1: No such file or directory
Failed
Failed to find system.im on SD Card
/bib/sh: can't access tty1 job control turned off
/ #
--------
Can anyone help me out to solve the problem?
Do i need to do some partition? if yes...how can i do it? i'm using a windows xp OS.
This is how my SD-storagecard looks like:
/[android]
/[android]/[andboot]
/[android]/androidinstall.tar
Thank you for your support.
The androidinstall.tar should be in andboot folder, with all the haret files. andboot must be in root of SD card.
/
/andboot
If you were installing to nand it'd be :
/KAISimg.nbh
/andboot
You do not need to partition the SD card, just make sure it is formatted FAT32, not FAT
hi zenity
thanks for the response. I did what you said. Still having the same problem with the same error message.
how do i check format of my sd card? i've never formated it before. it's the original sd card.
Depends if you have an sd card reader and adaptor for micro-sd, if you do you can just format it in windows.
It's likely that it's formatted FAT, most new pre-formatted micro-sd are formatted FAT as standard, how are you transferring files to the sd at the moment?
i connected my htc with microsoft activesync then transfered the files via windows explorer.
i'm still struggeling to get android run on my device.
are those steps correct? or am i doing something totally wrong?
those installation guide are too complicated for me. the instructions are mostly for total replacement of the OS. But i would like to keep my windows mobile because of tomtom navigator. I want to make both OS run with Dual booting function.
if you are so kind...can you please guide me to make this run? I'll be thankful for that.
Best way to format an SD card is to use a card reader and micro-sd adaptor, I've never tried to format an SD with winmo or through activesync, so I'm not sure how easy that is.
I have transferred the files via activesync before, and that works fine, but your SD card must be FAT32, winmo probably does not know the difference, I'm sure there must be a way to format the card FAT32 in winmo, but I cannot think of one, I'll look into it though. I think total commander is able to show what type of format the sd card is, but don't know if it's able to format it.
All the Haret files plus the androidinstall.tar must be in the andboot folder on the SD card, you do not need any other files or folders on the card, but it should not matter if there are any.
You will need an SD card of at least 1GB, 2Gb is better.
I know the guide is meant for Nand install, but does show the installer screen part clearly, and the install procedure is the same for nand and haret, and shows the installer screen you should see when installing on FAT32, (haret).
Download Card Export or WM5Storage to mount the card. Then format it like you would do with a usb stick.
me too
I get the same error.
I have haretinstall and androidinstall.tgz in the /andboot folder.
I renamed default.txt to default.txt.no
I renamed default-kaiser.txt to default.txt
I edited default.txt to point to zImage-eclair
I tried with the regular zImage
I wait till it ask for dpad or vol up button then I press and hold dpad. It never recognizes? Or thats my guess from what has been said here.
right clicking on the drive from within windows using a card reader it says fat32.
When I press dpad it prints a ^@ to the screen, ironically it does the same key for ok. I don't see how I can hold down the vol up/down key cause its a jog wheel? Should I try dpad down?
Volume Up Is the RIght SOftKey. FOr some build only that work.
@zenity: i manage to format my miniSD to fat32. it was fat before. but the problem is still there..does anyone else know how to deal with this?
as tyler51773 already mentioned..i fi start the "haret" which is stored in "andboot" folder it request to hold down the vol button. although i pressed the vol. button,,,it still doesn't work. getting the same error message like tyler51773
seems like i'm totally lost. someone please help!!!
can anyone write down a clean instruction how to install the kaiser on SD incl. the right link (instead of telling users to find out the right one) without wiping out the windows mobile. this would be more helpful to us.
i'm sure there are other users who might be interested in this too.
thankx
When you run Haret and see scrolling text, immediately hold down the d-pad or vol button. Don't wait for it to ask.
hi all,
i have the same problem. the instructions seems to be bad. i cant run it and tried many things. in install-instructions says "androidinstall.tar" but download is androidinstall.tgz.
i don't know if its a big mistake, but someone should make a new "correct" instruction with correct files. maybe it then will be worked.
i also stuck on "can't found system.img"
greetz an sorry for my english
@dukennukemx: i did what you said. no improvement.
@lenzen24: i'm 100% with you!
i tried again,
but also failed on find system.img on sd-card
hope someone has a solution, becaused i woudn't flash a image over my wm6.5.
greetz lenzen
progress
The right soft key button worked, (i.e. the one right above the mail, to the left of the red phone to the right of the dpad just to be perfectly clear for anyone else).
I got the menu, and then it said unbalanced irq 102, unbalanced irq 86?, unbalanced irq 87? it froze then rebooted.
Second try, I hold down the right softkey after i see the penguin. I get the menu with the ok warning. I try all the buttons the warning stays up. I open up the keyboard. I press enter I now am in the menu.
The install option is missing? I have 1. fix permisions. (vs it saying install?) The dpad doesn't seem to work. I have 7 options. The last option is quit. The 6th one is recovery. 5 is wipe. As I'm staring at errors and not the menu I forget which the rest are. I remember seeing a backup/restore. Then their is wipe. Their was also the wipe cache options.
When I try to navigate the menu its a no go. The only real options I have is fix permissions. That leads to errors due to a missing system.img that hasn't been made yet? And then their is quit. I get to quit using the left opt key, and I can get to fix perms using the right opt key. If i open up the keyboard and try every key the only key the menu responds to is enter. I also tried w/ fn lock, but not shift, no responce to the arrow keys was a bummer. When I accessed a shell I can atleast confirm that qwerty mapping was right, but didn't hang out long enough to see the rest of the keymap.
Should I try zimage-eclair? I will of course do that at some compulsive moment, but hey, maybe I wont, or maybe I will and say I haven't yet - maybe I already have {knowingly or not}.. do I need some options in my default.txt? Should I try a different androidinstall? this is polymod-2.1g
This is actually a Tilt vs a Kaiser.
Thanks for the speedy replies and help!
Tyler
Problems with the install option not appearing are usually caused by not formatting the sd as FAT32, or a wrongly set up sd card, for haret installs, everything goes in andboot folder, for nand, androidinstal.tar, (or tgz), in andboot folder, kaisimg.nbh in root, the install instructions are clear enough, they are just not as easy to follow for inexperienced users, and tilt and kaiser are the same thing, if you look under the battery it will say 'kaisxxx'.
zenity
Your last post you can tell someone got under your skin...
I'm a fairly experienced user. I have had troubles installing android since the nand came along.
I feel that if I were willing to nuke my winmo it would be installed. my primary objective with this phone is voip. I'm hoping sipdroid gets fixed or the reports of sipagent working better than sipdroid are true. I'd like to investigate that. I'm poor and with winmo I pretty much make free calls. Albeit I have reliability issues, and I have lots of things i should script to make things work which is all the more motivation to move over. Especially with winmo7 stripping voip out completely [rumor mill]. Anyhow, I am not willing to nuke my winmo. It's quite cryptic to call the volume key, the volume key, when on the kaiser its the right opt key. Perhaps the problem is that I am running a tilt vs a kaiser, another cryptic difference? good thing we don't have a lot of sidekicks running around either. Anyhow. My card is formatted right. I even tried another almost virgin 2gb card, never been formatted but did have a raw filesystem that was only used on sundays while driving to church, it was freshly formatted with fat32 and still it was a no go.
I also just tried myns build. I get an install option, when I press enter it warns me that it is about to delete my all my stuff. So I would say no, but after feeling wrath I tried to say yes, but of course I can't navigate nothing I push will let me choose yes. So I safely run with no.
If I did have a dpad where it says backup data could I backup my winmo? That makes me feel good I've always wanted that. That feature alone would make my day as it would let me finally upgrade my sacred voip setup w/o fear of having to find all those little f!&@&# registry entries again.
Enter does a carriage return in shell? New line in any event..
Dpad/Ok on the front both print a ^@, so does the side ok button, and so does the keyb ok button. {so does; Winkey, MailKey, GreenPhone{send}}
Dpad/Keyb/Jog Up does a ^[[A
Dpad/Keyb/Jog Down does a ^[[B
Dpad/Keyb Left does a ^[[D
Dpad/Keyb Right does a ^[[C
Left Opt: ^[[26~
Right Opt: [BLANK]
e does ^[[1~
red phone{end} ^[[4~
PwrOff ^[[4~
Admittingly this is using myn's androidinstall.tar as i just got done trying that, not sure if the keymap would vary at all (I highly doubt that). Anyhow I also did see the sdcard mounted. I cd'ed into it and did an ls. Everything showed up. It was mounted rw.
Let me know if I can do anything else to speed along the development.
Hate to ask a dumb question? But why not continue to distribute the sqsh builds if they're so much easier to test out for winmo users? Isn't that what the installer is trying to do is process the androidinstall.tar file into either one of three options one of which is cacheable - the sqsh files?
But still, I'd love to hear I now have a back up option..
Zenity thank you for your hard work and even diligent support! I totally get the stress that comes with messing with software for long periods of time. If it helps we can sacrifice a user to the /dev/null ? Hope you're feeling better.
tyler51773 said:
Your last post you can tell someone got under your skin...
Zenity thank you for your hard work and even diligent support! I totally get the stress that comes with messing with software for long periods of time. If it helps we can sacrifice a user to the /dev/null ? Hope you're feeling better.
Click to expand...
Click to collapse
Lol, sorry if it came over like that, I was typing it at a cafe on my kaiser, so I didn't spend as much time as I usually try to on a post, I usually try to structure them as carefully as possible to avoid misunderstandings
To be more accurate, I feel that the present sets of install instructions do assume a lot more knowledge than a lot of those new to Android actually have, this is not a disrespectful statement, simply that most builds have grown and changed so much, and the users who have been using them have also grown in specific knowledge of the install process, this, naturally, has led to some instructions assuming that those users all know the basics, which of course would be true if there were no new users.
It is difficult to produce a generic set of install instructions, since there are still a number of ways to get android onto our devices, and some builds are designed for other hardware originally, myn's for Vogue for example, so the install instructions tend to be more focused on those devices.
As far as the actual installer is concerned, the only time you will wipe winmo is if you have already flashed to nand, running via haret will not wipe winmo, the warning about wiping the system, or data, applies only to the Android build you are installing.
The present installer will process the androidinstall.tar or .tgz and install either to nand, if that is available, EXT2 partition, again, if available, or FAT32 partition, most commonly known as SD card or Haret install, the actual installation will then unpack the tar file to the proper destination, and on haret will produce a system and data img file, I'm unsure if it produces a sqsh file, since it's been a long while since I ran from anything but nand, but I do understand the confusion the install produces for those wishing to stay with winmo, and would prefer that it was clearer, but as with most of android development, once it works, development ceases until it breaks
Rest assured, unless you flash to nand, your winmo should be completely safe, I have not yet seen anyone wipe winmo using the SD/Haret method, not in all the time that we have been running Android on our kaisers.
I'm confused now however, I was always under the impression that the Tilt was merely another kaiser model, and unless you have forgotten to edit the default.txt file to reflect your hardware, the keypad/dpad should function properly, which as far as the escape sequences you have posted, would seem to be the case, ( dpad centre should give ^@ in console etc), so navigating the installer should be as easy as pressing the left, right up or down keys, followed by centre to choose options.
What I am now tempted to do is reflash my secondary Kaiser to winmo stock, and try a few haret installs just to check out things, since most of the above is mainly from memory, although a lot of the Nand install procedure is similar, may not be identical.
Sacrifices will not be necessary, however offerings may be made of caffeine, and/or chocolate, this may help me continue to function in my role as helpful user, and reduce my occasional visits to the mild irony I call my sense of humour
cool
I feel you about short emails making one sound bad! I made that mistake a few times. I actually hate email. I wrote this very funny email to my advisor, he liked it, and forwarded to his boss - just communicating, not to share a laugh or to complain, but to answer a question he did not know; atleast I was told that as I was then later forced to ask him 'did I make you mad?'. Anyhow I got chewed out for professionalism by the department chair which is not the way to a elect a major. Funny enough, I had decided writing funny was the way to go after i had peeved someone off for writing short almost angry sounding emails. In short I hate email/communicating via text.
I was thinking about the whole solution thing. If i need to do a key remap maybe we could just write up a shell script and I could execute it from /sdcard and then re-execute the installer ? unknown.sh??
Also, if you produce some img files what's to stop you from sharing those? I'd totally be willing to try it, maybe it'll work, maybe it'll break wifi calibration? who knows?
Bug found:
http://code.google.com/p/vogue-android/issues/detail?id=124#makechanges
set cmdline "ppp.nostart=0 pm.sleep_mode=1 mddi.width=240 mddi.height=320 no_console_suspend board-kaiser-keypad.atttilt=1"
just tried to change board-kaiser-keypad.atttilt=1 with no results
Just my .02c
So for the past week or so ive been trying to root my incredible to no avail... ive used every method posted and none work..
The two cards i tried are the 2gb card that came with my droid incredible.. formatted Fat32 1024 byte size with nothing on the card, and it didnt work on ANY method.. so then i tried my transcend 8gb class 6 card that was previously formatted to Fat32 awile ago and had a bunch of stuff on it, and nothing worked with that one either..
So then i said screw this, i went out and bought the holy card that supposidly has a 100% success rate... the Kingston 4gb class 4 card.. put that bad boy in and it dosent work either! what the hell can i do... the Kingston is brand new.. nothing on it, formatted Fat32 1024 byte size
did you format it in the phone?
Sent from my ADR6300 using XDA App
I formatted it via my PC.. Windows7 i used the format tool in My Computer... i didnt do quick format either i did the full format Fat32 1024 byte size
format it in your phone once and give it a few tries
Sent from my ADR6300 using XDA App
is this done in recovery or Hboot or what?
while phone is fully booted. menu > settings > sdcard and phone storage
scroll down to the bottom
Sent from my ADR6300 using XDA App
Just formatted the card via phone then went back into recovery and tried and no go.. ive tried it about 35 times now with this *100% successrate card* and gotten zero, also keep in mind that the design of this particular card makes it impossible to click in and out in rapid succession, it keeps getting stuck like the stock verison 2gb card does while my transcend 8gb has no problems clicking rapidly
my guess is you are doing something wrong or something is not set up right
Sent from my ADR6300 using XDA App
invisiblek said:
my guess is you are doing something wrong or something is not set up right
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I wish that was the case but i have no problem using ADB in any setting, the drivers are definately set up right as i can use ADB fine while in android and i can even get an adb reboot recovery out of it before the phones fully booted up normally as in binnys method
http://www.youtube.com/watch?v=Z8mheIkQ-1o
dunno if u saw that yet, thats the video i made the night they got root
i have a kingston 4gb class 4 and thats the method i did there
this method works 100% of the time for me too
yeah. been trying that method for an hour just as in the video and its been 0% for me lol
There is no sdcard that is going to make the method foolproof. You need to reduce your variables. Windows driver scheme can become a mess very, very quickly. I recommend booting your PC with a Linux LiveCD like Linux Mint 9 Isadora or Ubuntu 10.04 Lucid Lynx. They're both free and both distros recognize the DI out of the box. I've attached the ./loop.sh that I've used successful to bring up the adb error you're looking for--just rename the file before you run it from linux terminal. Navigate your browser in linux and download the Linux Android SDK ho ~/Downloads, and once you do, extract it to ~/Downloads. Then, to be ultra-safe, use these commands:
Code:
*open terminal*
cd ~/Downloads/ # assuming you d/l'd my file/SDK file to your home Downloads folder in Linux
cd android-linux-sdk_86/tools
sudo ./android
# this will trigger the SDK installer, just tell it to fetch all packages, then close it
rename loop.sh.txt loop.sh
chmod a+x loop.sh
sudo ./loop.sh
# you'll get an infinite loop with "adb: device not found"
At that point, pop the back cover off your DI, power it down, connect the USB cable, boot into bootloader, eject the SDcard, making sure your terminal window is visible: select Recovery menu, then start counting from the boot vibrate. Count to seven seconds (as in: one-one-thousand, two-on-thousand ...), then insert the card exactly on 7 or when the white screen scanline flickers, whichever comes first.
Hint: I like to do this with the terminal window kinda small with a maximized "Computer" Nautilus file explorer window up in the background, showing all devices. You'll notice with this view that your android devices appear, in bootloader, disappear on recovery reboot, then reappear when recovery/black triangle screen is done loading. If you've missed the timing window and the card wasn't inserted right, you'll see those two volumes pop-up, but your adb shell error message won't have changed--and you know to pull the battery and start over. If the message does change when when the drives appear: success! You can "up vol-power" and continue with whatever rooting method you like, provided you know the slight (good) differences using linux introduces versus Windows.
Good luck, you only have to do this right once, then Unrevoked2 locks it in place!
Dude, it took me forever. In the end it was finding the right time to insert the SD card for me. I would start out with it in then right before I selected recovery I would pop it out and then I would push it back in as close to the same time as the 2nd "mount tone" as I could. I have only had success with class 6 cards but both an 8 gig and the infamous 2 gig PNDY card have worked for me. I also had a prob with getting the adb shell to work after a did the push payload witch turned out to be a bad download of the "tools folder". re-downloaded it with the phone still in recovery and it was smooth sailing from there.
Don't get discouraged and have a lot og free time when you start trying the next time.
Did you try downgrading? I had no much for a week then I downgraded ands got it on the very first try. Good luck
Sent from my ADR6300 using XDA App
I tried for DAYS to get this to work... I searched every android forum on the net for tricks... I gave up... I got pissed and started again... gave up again... and finally like magic I found the right combination of bull**** trickery to make it work.
How I did it:
1. Turn off the phone normally
2. Remove sd card (I used the 2g card that Verizon sent)
3 Boot up into recovery with the Vol- /Power button method (sd card out)
4. Let the phone do it's thing
5. Run loop.bat
6. The trick here- When you press the power button to select recovery have the sd ready to go in (sitting in the slot but not clicked into mounted position)... then when you hear the second usb "ding" push it in as fast as you can- almost simultaneously with the "ding".
This got me into the error message in about two tries (after possibly hundreds of failed attempts using other methods)- after that it's pretty much downhill.
No guarantees, but it worked for me and quite a few other frustrated souls.
Keep the faith- root is definitely worth the headache
Edit: Disregard. I didn't see that rynosaur had already posted detailed steps above.
Windows needs to see the device as too many different things during the different stages (i.e. HBOOT, Recovery, Fully booted). I did it under Linux and didn't have to worry about that. If you have a Linux partition or a Linux Live Distro, try it there. The commands are basically the same except you need to preceed the adb commands with ./ as in ./adb reboot recovery
DobbsianYeti said:
I tried for DAYS to get this to work... I searched every android forum on the net for tricks... I gave up... I got pissed and started again... gave up again... and finally like magic I found the right combination of bull**** trickery to make it work.
How I did it:
1. Turn off the phone normally
2. Remove sd card (I used the 2g card that Verizon sent)
3 Boot up into recovery with the Vol- /Power button method (sd card out)
4. Let the phone do it's thing
5. Run loop.bat
6. The trick here- When you press the power button to select recovery have the sd ready to go in (sitting in the slot but not clicked into mounted position)... then when you hear the second usb "ding" push it in as fast as you can- almost simultaneously with the "ding".
This got me into the error message in about two tries (after possibly hundreds of failed attempts using other methods)- after that it's pretty much downhill.
No guarantees, but it worked for me and quite a few other frustrated souls.
Keep the faith- root is definitely worth the headache
Click to expand...
Click to collapse
the sdcard usb ding timing is key
So heres what happened, my first Kingston 4gig card didnt work after like 40 tries, so i said screw this and returned it, and then i went somewere else and picked up a second 4gb kingston
Went home, put it in my phone, rebooted recovery and got it to work instantly... got the recovery flashed... removed cityid.. pushed the update.zip and su and superuser all on my phone
however my phone would NOT chmod no matter what i did.. i tried everything, i copied and pasted the directions exactly as on the screen and it would never work, when i got to the last line that starts of 1n - or something like that it would say permission denied even though i was in su...
So anyway i said maybe it had worked, so i rebooted the phone.. i saw that superuser.apk was in my app drawer as an installed app.. then i went into terminal emulator and typed in "su" and it said permission denied.. the root didnt stick because the stupid Chmod did not work for me...
Oh and to top it off guess what else happens? Obviously when i try to go back into recovery it DOES NOT work... tried it about 35 times again now and it wont go back in whatsoever after doing it the first time.. also for me in recovery my second usb ding happens MANY seconds into the black screen.. if you start counting right when you press the power button for recovery and the white screen turns to black at like 5 seconds.. my second usb ding dosent happen until like 10 seconds... deep in the black screen
Joe92T said:
Oh and to top it off guess what else happens? Obviously when i try to go back into recovery it DOES NOT work... tried it about 35 times again now and it wont go back in whatsoever after doing it the first time.. also for me in recovery my second usb ding happens MANY seconds into the black screen.. if you start counting right when you press the power button for recovery and the white screen turns to black at like 5 seconds.. my second usb ding dosent happen until like 10 seconds... deep in the black screen
Click to expand...
Click to collapse
What's the difference now? Look at the root directory of the card. There's files there now. You need to re-format the card. The most effective formatting I (and others) have found is a split 2gig ext4 partition (linux fs), followed by a fat32 @ 1024k block allocation, long format. As soon as Android boots, it starts writing your card.
rynosaur said:
What's the difference now? Look at the root directory of the card. There's files there now. You need to re-format the card. The most effective formatting I (and others) have found is a split 2gig ext4 partition (linux fs), followed by a fat32 @ 1024k block allocation, long format. As soon as Android boots, it starts writing your card.
Click to expand...
Click to collapse
How can i format it like that using windows? The easy format tool you find when right clicking on the drive under my computer dosent have those functions
OK, here's my problem. My EVO was smashed last night by a raving drunk psycho (Yes, cops showed up and took him, but I need my nandroid to put on my replacement phone when I get it). The screen is in about 1 million pieces, the entire case is warped as well. But oddly enough, this tough a$$ phone still boots up. I can issue adb commands and such, but can't see jack on the screen. So I know I can boot into recovery mode and whatnot via adb. My problem is this. I know there are 2-3 nandroid backups. How the hell can I get them? I tried putting the sdcard into a reader on my laptop, but to my stupidity I now realize it's in some linux or other file system format, so I can't simply read the card directly. Any help would be greatly appreciated!!!
Also, I have nand root acces on the phone if that helps at all.
SteelH said:
OK, here's my problem. My EVO was smashed last night by a raving drunk psycho (Yes, cops showed up and took him, but I need my nandroid to put on my replacement phone when I get it). The screen is in about 1 million pieces, the entire case is warped as well. But oddly enough, this tough a$$ phone still boots up. I can issue adb commands and such, but can't see jack on the screen. So I know I can boot into recovery mode and whatnot via adb. My problem is this. I know there are 2-3 nandroid backups. How the hell can I get them? I tried putting the sdcard into a reader on my laptop, but to my stupidity I now realize it's in some linux or other file system format, so I can't simply read the card directly. Any help would be greatly appreciated!!!
Also, I have nand root acces on the phone if that helps at all.
Click to expand...
Click to collapse
The sdcard is formatted by the phone as fat32. Put it in an sd card adapter, then into your computer. The files are in the nandroid folder, just copy that full folder. While you are at it, you might as well just copy the full card...and keep the card to put in your next phone, right?
If the card doesn't read in your computer, then it is damaged. There are numerous file recovery programs you can try, but it is questionable to me that your nandroid backup is really worth using a recovery program to save. Your contacts should be in Google and the rest takes 30min top to set up (right?).
If you REALLY want to save it try:
Code:
adb pull /sdcard/
It will copy everything into the directory you are in I think.
The backups should be stored in /sdcard/nandroid/
Man, you can ADB into your phone after it got smashed up like that?
Jykinturah said:
Man, you can ADB into your phone after it got smashed up like that?
Click to expand...
Click to collapse
Yeah, it's getting txts and emails too apparently. Wifi is connecting to my router too. No sounds at all, no vibration, no screen. But seems the phone is working aside from that. It's crazy.
Got a problem it seems:
Code:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\android-sdk\tools>adb devices
List of devices attached
HT05VHL13839 device
C:\Program Files (x86)\android-sdk\tools>adb pull /sdcard/
pull: building file list...
0 files pulled. 0 files skipped.
C:\Program Files (x86)\android-sdk\tools>
Seems the sdcard went down with the raving alcoholic man.... crap.
Is there any way to run nandroid backup without seeing the screen?
I say, get a micro SD card reader, and put use your PC to do a backup.
Sent from my PC36100 using Tapatalk
lafrad said:
I say, get a micro SD card reader, and put use your PC to do a backup.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
As you can see from my prior post, the sdcard appears to be shot. I need some way to run a nandroid backup without being able to see the screen.
SteelH said:
As you can see from my prior post, the sdcard appears to be shot. I need some way to run a nandroid backup without being able to see the screen.
Click to expand...
Click to collapse
boot up the phone and do
Code:
adb shell
then
Code:
reboot recovery
when it reboots redo
Code:
adb shell
then put
Code:
nandroid-mobile.sh --help
and that will give you what you need to do. However if your sd card is shot then your screwed lol. nandroid needs an sd card to work
Yeah, do what mrono suggested, but with a new Micro SD card. Just buy a cheap-o 1GB card or something to run the backup. I've got 3-4 cards around here myself. Maybe you can borrow a card from another phone or a digital camera? Chances are a 256mb card will work as well, or 512mb? A 32 won't work since it's too small. You've of course lost everything else, but you should be able to make a backup.
This is all assuming that the SD Card slot in the phone didn't break in the process, and since the SD card is fried, chances are it did break the slot since those bastards are a pain to fry in the first place.
Thanks guys. I figured that out a little while ago. I just used the sdcard out of my old blackberry. Worked great!
I was recently given a new SCH-I435 from a family member. This is my first time having an android in a very long time(Switching from an iPhone 4s). I have a few questions about it. (this may be a lengthy post)
First I know that you cannot flash custom ROMs to it, as the bootloader is still locked. I have heard that there are some de-bloated stock ROMs out there, but have entirely failed to find any. I can probably get by without it, as I already have it rooted, but there are several things I am attempting to do, and every time I look up how to do it, step one is having a custom ROM.
If anyone can point me to a de-bloated stock ROM I would greatly appreciate it (or at least one that is compiled to not be a "production build" as I keep running into "adbd cannot run as root in production builds" and it is severely limiting what I am trying to do, and what I am going to want to do in the future)
What I am trying to accomplish next is taking over the "connected as installer" feature that Verizon has on it when you plug it into USB (I am using linux exclusively so have absolutely no use for their software). I figured I may as well put this feature to good use. I am attempting to swap the ISO file in /system/etc for a CrunchBang LiveCD.
This has only been a partial success, apparently /system is it's own partition, and there is not enough room to fit the whole ISO (It is 739mb and it stops at 423mb) Even though it does not get the whole ISO copied, if I reboot my computer the ISO does indeed boot into the options, but fails to load the live session (no brainer there) so I know I am on the right track. I don't want to use DriveDroid for this, as it is very very finicky, and only seems to work 1 out of 6 times (and that is a kind guesstimate) My guess it that the "connected as an installer" is messing with it, so I would hope to turn the problem into the solution.
So I either need to find a de-bloated ROM that can free up ~ 400mb on /system, find a way to link the ISO from elsewhere on the device (I tried a soft symlink from my SD card and that did not work, it opens the ISO as an archive and not a file system), find a way myself to free up ~400mb on /system, or find a way to re partition /system to be larger (I have the 16gb S4, so I have plenty of room to spare).
I would prefer the debloated ROM(I don't know if that will free enough room), but finding a way to re-partition would be a close second (Every guide I have found for re-partitioning starts of with "First you need cyanogen(or another custom ROM)") I may need to re-partition it anyway. (Honestly I would like to learn how to do all of these, as they would be valuable tools in the future)
I had more questions, but got kinda lost writing this up, I will append them to this post later when I remember them... Thank you in advance for any help you may send my way.
**edit**
Oh yea, my other issue is accessing the files on the phone under Debian Wheezy. I have tried mtpfs, jmptfs, ptp mode, mtp mode, go-mtpfs (that one somewhat works, I can see *some* of the files, and probably take them off the device, but I attempted to add a file to the SD card and it corrupted the entire card, had to reformat it, just glad I did not do that to the phone)
ADB partially works, but only for taking files off the device, or putting them onto the device in non root areas, I get stuck with "adbd cannot run as root in production builds". I have tried almost everything I can find under the sun in regards to USB access.
Hello,
I have an Oppo Find 7 for a while and I always thought that the Color OS is not very good, and specially, it comes with a very limiting partition division.
So, when I could no longer decide on which Apps to keep and which to uninstall, since I had no longer space left on my phone due to the stupid small partition for applications, I decided to format my phone, reconfigure the partitions and install a new ROM (CM 13).
I had done it often on my lapton, how difficult could it be to do it on the phone?
It all seemed to work fine, but when I started my "new" phone with CM I noticed that something was wrong. I tried to use the camera and it showed an error saying I did't have a storage device.
Well, I was sure I had left enough space for photos in the other (not OS) partition, and I had also the SD card.
I went to Settings->Storage and I saw that my phone was recognising the OS partition only (about half of all internal storage) and had a portable storage device called "sdcard0" (not the actual SD card) reading "Damaged" below.
I've tried to erase and format that partition, but it shows an error reading "command '41 volume partition disk: 179_0 public' failed with '400 41 Command failed'".
I've tried to rearrange the partitions again, to reinstall CM13, but nothing worked, so I just accepted that my phone could not take pictures. Everything that did't require to have a file system worked fine (well, I cannot see the naked ladies pictures my friends share on whatsapp). This was a few months ago, so I don't remember precisely what I did.
Recently I decided that I actually need a phone that takes pictures, so I went back to trying to fix it.
Unfortunately, I can't. At least without some custom help. I've read plenty of tutorials, forum pages, but there's always something that doesn't work in my case.
Here's what I can do with my phone:
- It boots
- It works
- Computer recognises it
- adb recognises
Here's what I can't do:
- Have any files (the file system is broken)
- Take photos
- Restart with bootloader - when I tried, the screen just shows a sitting penguin for a few seconds and then turns off. I do remember to be able to do so, but I can't now.
I've tried to load bootloader though the phone's interface, through the power+volume down button combination and through adb. They all had the same result. The stupid penguin and then darkness.
Can someone help me?
Hello, you're phone is not bricked. What is the exact name of you're ROM ? Do you have make LVM, or chinese storage partion?