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
Related
Hello everyone. I haven't flashed Android to NAND yet but I'd like to try it.
I am sure this question has been asked before but I did try the search and I couldn't find it. Sorry if this has already been asked.
So, for the Kaiser, if I flash Android to NAND (ie: Polymod's most recent) how do you flash back to Windows Mobile?
I'm concerned because USB does not connect properly when Android is running with HaRET ("unrecognized USB device" using XP SP3 couldn't make heads or tails of the drivers in the SDK but then I didn't try installing the whole environment)
So I guess my question is -- even with the device unrecognized, can you still flash it back? If so, how? Is it really simple and easy?
Please let me know and point me in the right direction! Thanks!
aikeru said:
Hello everyone. I haven't flashed Android to NAND yet but I'd like to try it.
I am sure this question has been asked before but I did try the search and I couldn't find it. Sorry if this has already been asked.
So, for the Kaiser, if I flash Android to NAND (ie: Polymod's most recent) how do you flash back to Windows Mobile?
I'm concerned because USB does not connect properly when Android is running with HaRET ("unrecognized USB device" using XP SP3 couldn't make heads or tails of the drivers in the SDK but then I didn't try installing the whole environment)
So I guess my question is -- even with the device unrecognized, can you still flash it back? If so, how? Is it really simple and easy?
Please let me know and point me in the right direction! Thanks!
Click to expand...
Click to collapse
I beleive you can always follow the process here.
Your boot loader should not change when flashing so not being able to use the USB while in Android is not going to prevent your returning back to a stock ROM. I have not tested this but I'm pretty sure that you can always get back to your boot loader screen and re-flash from that point. Can someone confirm that this is the appropriate solution?
deekjx said:
I beleive you can always follow the process here.
Your boot loader should not change when flashing so not being able to use the USB while in Android is not going to prevent your returning back to a stock ROM. I have not tested this but I'm pretty sure that you can always get back to your boot loader screen and re-flash from that point. Can someone confirm that this is the appropriate solution?
Click to expand...
Click to collapse
Did anyone try this solution?
Since the bootloader is still there all you do if not able to flash via async when in android is flash via bootloader
Moved to general as not ROM Dev.
Thanks for the information, guys!! I will have to try it out over this weekend and see how it goes...
I can confirm that flashing via bootloader works fine, also flashing from SD works as well, in fact I keep a 128MB sd with a WM kaisimg.nbh on it handy just in case I need to flash a good WM rom for some reason.
Is there an Android OS with everything working on the Kaiser?
Dukenukemx said:
Is there an Android OS with everything working on the Kaiser?
Click to expand...
Click to collapse
You can see in different post of android rom what works and what doesn't works.
actually, Bluetooth and camera never works for in android 2.x build and some other apps doesn't works
I've been running Android for a few weeks now from this thread:
http://forum.xda-developers.com/showthread.php?t=614382
I've found everything to work with the exception of Bluetooth, video camera (normal camera works fine), and the barcode scanner. Also, my battery life is cut in half, but I have an extended life battery so I get a day or two out of it.
I prefer this method as you can just boot Android at will and can soft reset to go back to WinMo.
Just to let everyone know I did flash WM back just fine since I have HardSPL 3.56 and used the stylus to press the reset + camera button at the same time to get to the tri-color screen.
From there I flashed from USB without any problems.
Thanks again for all the help!
I am having problems reverting back to WM after attempting to install android to NAND. Something happened where the only way I was able to get to the android installer would be if I had the KAISDIAG.nbh file on the SD card so it would get past the tri color hard spl screen . Well as a result, I can't get into boot loader. It shows that screen for a split second, then if I do camera + power and then reset. Then I have to pull the battery. Can someone help me? It seems like it will only go into the Android bootloader, which obviously won't allow it to install a WM rom. SD flashes are my only choice because the usb port is pretty messed up. Any help would be greatly appreciated. Thanks.
The procedure for flashing WM back using SD card is much the same as flashing the Nand bootloader for Android.
First get a WM rom, copy the RUU_Signed.nbh to SD card, rename it to KAISimg.nbh, pull the battery, replace, press power and hold camera button, this should start the flash process.
Note that the SD card must be formatted FAT32, or it will not find the KAISimg.nbh.
If you prefer to flash a stock rom you will usually have to extract the RUU_Signed.nbh from the installer, just open it in winrar.
the reset in android is not working correctly. The correct way to get into bootloader is to pull the battery, wait a few minutes, rpelace the battery, press power and then press and hold camera button, do not use reset.
zenity said:
The procedure for flashing WM back using SD card is much the same as flashing the Nand bootloader for Android.
First get a WM rom, copy the RUU_Signed.nbh to SD card, rename it to KAISimg.nbh, pull the battery, replace, press power and hold camera button, this should start the flash process.
Note that the SD card must be formatted FAT32, or it will not find the KAISimg.nbh.
If you prefer to flash a stock rom you will usually have to extract the RUU_Signed.nbh from the installer, just open it in winrar.
the reset in android is not working correctly. The correct way to get into bootloader is to pull the battery, wait a few minutes, rpelace the battery, press power and then press and hold camera button, do not use reset.
Click to expand...
Click to collapse
Thanks, but unfortunately this still did not work. Have any other suggestions? I think the only way will it even do anything is if I have the KAISDIAG.nbh file on the card. It recognizes that, but then goes straight to linux. IDK what else to do. Could you be a little more clear on the procedure for getting into the bootloader? Thanks.
Ok please follow these steps carefully.
1. Format the SD card, make sure you are formatting it as FAT32, not FAT.
2. Download a Winmo Rom from somewhere handy.
3. Extract the Rom to a handy folder, find the RUU_Signed.nbh file, rename that to KAISimg.nbh
4. Copy the KAISimg.nbh file to the SD card. You should only have one file on the SD card, no folders just the NBH file.
5. pull the battery from the phone, wait at least 5 minutes.
6. Replace the battery. Press Power button, and hold down camera button, until the tri color screen appears.
7. The screen should now change to a white one, and when it's checked the nbh it will ask you to press power key again. do that.
8. Now it should flash the rom, this should take a while, 5-10 minutes, once it's finished you should get a message of success.
9. Now pull the battery again, wait 5 minutes, replace the battery, and power on, you should now boot into Winmo.
Hopefully this should solve your problems, if not then let me know which setp failed and we can work on that stage.
Finally, don't panic, take it slow, it'll all work out
Thanks, but the problem starts at number 6. I am supposed to press the power button, release it, and hold the camera button till it gets to the white screen, right? It's still stuck at the splash screen. I tried holding both and that didn't work either. Anything else I can try? I hope i'm not screwed?
If I put the battery in, boot it up, then push the camera and insert the stylus into the reset hole, it gets to the tricolor screen, then for about 0.5sec it flashes the white screen with a message saying "No image File." I know for sure the .nbh file is there.
I have experienced this before, when I tried to use an SD card that was formatted FAT, when formatting you must make sure it is formatted FAT32, the bootloader cannot read FAT formatted SD cards, even if Winmo and Android can.
I format using a card reader, and in windows it is sometimes easy to overlook the file system type, most SD cards are usually formatted FAT when they are new, and you must change the formatting, or it will just format FAT again.
zenity said:
I have experienced this before, when I tried to use an SD card that was formatted FAT, when formatting you must make sure it is formatted FAT32, the bootloader cannot read FAT formatted SD cards, even if Winmo and Android can.
I format using a card reader, and in windows it is sometimes easy to overlook the file system type, most SD cards are usually formatted FAT when they are new, and you must change the formatting, or it will just format FAT again.
Click to expand...
Click to collapse
Unfortunately, as much as I wish it was, it is not the problem. I'm on a Mac, but booted windows 7 to be make sure it was formatted to FAT 32, which it was. Is there some way I can fix permissions? Every time it runs, I keep getting the error saying that it is in read only mode. I obviously need to get it into writing mode. I don't think the fix permissions option on the installer did anything either.
The eclair build still will not install on my phone. I changed to an earlier .nbh file and now don't need the KAISDIAG.nbh file to get out of the splash screen and into the installer. When I run the install command for NAND, it says it can't mount, "no such file exists", "failed to extract." Keep in mind I haven't even gotten Android installed to NAND, just the installer itself. I can't even go back to WinMo either. It also seems like a permissions error since I believe it said the SD card is read only, but when plugged into my computer I fixed that and now it is read-write, but not on the phone. Please help because I really want to either get this working, or get back to WinMo instead of have this useless phone I currently have. Thanks.
Is there a way to enter the command line from the installer screen?
Tilt Fanatic said:
The eclair build still will not install on my phone. I changed to an earlier .nbh file and now don't need the KAISDIAG.nbh file to get out of the splash screen and into the installer. When I run the install command for NAND, it says it can't mount, "no such file exists", "failed to extract." Keep in mind I haven't even gotten Android installed to NAND, just the installer itself. I can't even go back to WinMo either. It also seems like a permissions error since I believe it said the SD card is read only, but when plugged into my computer I fixed that and now it is read-write, but not on the phone. Please help because I really want to either get this working, or get back to WinMo instead of have this useless phone I currently have. Thanks.
Is there a way to enter the command line from the installer screen?
Click to expand...
Click to collapse
Alright, I'll try and sum up your experiences. Tell us if we're missing anything;
You have the following symptoms
Linux Android-installer works
Tri-color bootloader semi-works
You cannot use the USB
You cannot install polymod's Eclair build
Now, you have mentioned a couple of things you have tried, such as
Replacing the Linux NBH with another version
Fixing permissions on the SD-card
Fixing permissions through the Android-installer
Flashing a WinMO ROM through SD card
You did mention getting other behaviours when you switched to another NBH, such as "KAISDIAG.nbh" not being required.
Now, this is a long shot coming from me, as I have had no troubles with flashing, and the fact that I can use my USB, but since your phone is pretty messed up I guess it can't hurt as a suggestion;
You can flash to other NBH's I take it, as you mentioned you did a downgrade. What I'm a bit curious about is whether you did try to flash to a WinMO rom when you had downgraded to your current NBH.
Also, you said the previous NBH required you to have "KAISDIAG.nbh" on the card to even get working. Did you try and rename a WinMO-ROM's NBH to "KAISDIAG.nbh" and flash that? Might be that the flasher is really constrictive with the file names.
EDIT: Oh, and what about trying to run other Eclair builds? Just to see if you can nail it down to this being a problem of the builds or something more bound to the actual hardware/SPL/NBH's.
hi, i'm using tp2 from t-mobile
using EnergyROM
fat32 clean format (not quick one)
installing in the sd card
--
i tried the 3 cabs
and i get to the black screen then is showing this:
failed to mount the sd card
"/bin/sh: can't access tty; job control turned off"
also keep getting
"kernel time out blah blah"
what to do?
thanks in advance
atomiq said:
hi, i'm using tp2 from t-mobile
using EnergyROM
fat32 clean format (not quick one)
installing in the sd card
--
i tried the 3 cabs
and i get to the black screen then is showing this:
failed to mount the sd card
"/bin/sh: can't access tty; job control turned off"
also keep getting
"kernel time out blah blah"
what to do?
thanks in advance
Click to expand...
Click to collapse
not exactly sure....when u tried each cab, did u completely uninstall and delete all traces of each build including the fsck files? alot of times if not, and u try to install a new one, itll stick pick up the old data and mix with the new and cause issues. The one to try thats the easiest is the AOSP. data and service works off tops without doing anything.
try this...whatever cab u got in there..uninstall it...then ...go into file explorer or whatever and delete any and all traces of the previous build. after that, if u have clear temp or clean ram, use that. then soft reset.
get the build cab of ur choice, but id recommend the AOSP for the quickest start. download it to root of storage card which is /storage , not in a folder in storage(example /storage/programs). it has to b in the root. then install. then soft reset. once it boots back up, go to the android icon. press it..then update all the new files for the build b4 ur first boot up. u should see the tab to let u update. after update complete, then press run android...and hopefully any little issues or residual files are gone and u can complete the startup or bootup of android. let us know if that didnt wrk for ya.
ok now boots, and works fine
i'm using AOSP 2.1 updated
EDIT MY INTERNET WORKS NOW, LOL,
I'm having the same exact error on my AT&T Tilt 2 with stock ROM. I downloaded the AOSP into the storage/programs folder of the SD card, installed it to the SD card, then ran the update. After the update, I got the "Failed to mount the SD Card. Cannot Continue" error. I uninstalled the program and got rid of everything ans started from scratch with the same error.
Any idea?
Okay.... I've tried this a few times with no luck. Here is what I have:
AT&T Tilt 2 with stock ROM. I started with a fresh Hard Reset this morning (due to problems with Good Mobile Messaging) and loaded the AOSP file to my micro SD card (\Storage Card\ProjectAndroid 2.1AOSP 042610.cab). I ran a level 3 CleanRAM, then double clicked on the AOSP file on the SD card using TotalCommander. The file asked where to load it to and I chose the SD card. It successfully installed and I did a Soft Reset using the red reset button behind the battery cover.
Once turned back on I go to Start and press Project Android. Once loaded up, I went to Menu and Update. It updated successfully in about 5-10 minutes and I then clicked Run Android. The screen goes black and runs a bunch of script until it gets to this:
Welcome to Vogue Linux
Running an fsck on SD card
dosfsck 3.0.1, 23 Nov 2008, FAT32, LFN
Logical sector size is zero
mount:mounting/dev/block/mmcglkopl on/sdcard failed: Invalid argument
Failed
Failed to mount the SD card. Cannot continue
/bin/shi can't access tty; job control turned off
It then freezes at this point and stays there. I've uninstalled and removed all sources of the files (that I could find) and started from scratch several times and it does the same thing each time.
Is something wrong? Am I missing something simple?
ROM Version: 1.59.502.3 (67150) WWE
Rom date: 09/25/09
Radio Version: 4.48.25.20
Protocol version: 61.39tc.25.30U
is there any other info you need?
i did use this formatter
http://www.megaupload.com/?d=287HD74A
extract, install, open, select your unit, click on option, select full erase ON
let ir run..
this promise to fix this error acording to a forum that i read
outside of XDA, it can also throw that same error if you are using
a SLOW storage card.
pls report what happened so we help other people with the same issue..
The error message is normal. Just ignore it unless the thing wont boot overnight
thebulletfromhell said:
The error message is normal. Just ignore it unless the thing wont boot overnight
Click to expand...
Click to collapse
So just leave it there and let it keep running? I'll give it a try.....
sethjamto said:
So just leave it there and let it keep running? I'll give it a try.....
Click to expand...
Click to collapse
No joy..... it hung up on the same screen that I quoted above for over 5 hours. I soft reset and then uninstalled the software. I guess if I'm destined to have Android, then I'll just go out and buy an Android based phone.....
i guess you didnt tried the FORMATTER that i've posted
anyways
maybe you should wait for the release of HTC VISION
or wait much looooooonger a couple of years for an official android rom
for our poor htc rhodium..
good luck.
**Disclaimer so that this doesn't get deleted. I looked at all the posts and tried to search, couldn't find any answers and I made this thread HERE because I doubt anyone in "General" would know what I'm talking about. This is more of a development question.**
----------
Ok, I am actually having two problems.
1) Normally when I plug my phone in the computer and choose "disk drive" mode, a screen pops up on my PC titled "Removable Disk (J)" That's actually not the right one because right behind that screen I get another pop-up titled "Removable Disk (K)" and that's actually the one with the folders and everything that I'm supposed to use (the root of the sd card folder.) So I hit cancel on (J) and am on my way using (K).
Well over the weekend, on Friday, I rooted my phone using toast's way and then I went camping without doing ANYTHING else.
Then I come back last night, everything is working fine and I installed ROM Manager on there because I wanted to flash Pete's "BuglessBeast". Since my internet connection in my basement is super slow I decided to just leave it at that and work on it at work today. Well here I am.
Problem: Phone was not connecting to computer. It kept giving me errors and then asked me to Format my card. After about half hour of trying to get it to connect I said "fine.. I'll just format it and factory reset my phone and root all over again and do all this. Well now.. phone is only connecting to (J) drive. (K) never appears.
2) Also, after rooting and finding out that ROM Manager won't work for me I have to manually download the file, I tried to go into recovery mode and every time I selected "sd card: apply update.zip", I keep getting the same error saying "FILE NOT FOUND ON SD CARD".
Any help please?
Am I doing something wrong?
Is there a way to start over, all over again?
With the problem running (where you can see both disks), right click on "My Computer" and select "manage", then go to "Disk Management" and see if your SD card is partitioned or something. That's very unusual and should only present itself if your SD card is partitioned and it's seeing both partitions.
arozer said:
**Disclaimer so that this doesn't get deleted. I looked at all the posts and tried to search, couldn't find any answers and I made this thread HERE because I doubt anyone in "General" would know what I'm talking about. This is more of a development question.**
----------
Ok, I am actually having two problems.
1) Normally when I plug my phone in the computer and choose "disk drive" mode, a screen pops up on my PC titled "Removable Disk (J)" That's actually not the right one because right behind that screen I get another pop-up titled "Removable Disk (K)" and that's actually the one with the folders and everything that I'm supposed to use (the root of the sd card folder.) So I hit cancel on (J) and am on my way using (K).
Well over the weekend, on Friday, I rooted my phone using toast's way and then I went camping without doing ANYTHING else.
Then I come back last night, everything is working fine and I installed ROM Manager on there because I wanted to flash Pete's "BuglessBeast". Since my internet connection in my basement is super slow I decided to just leave it at that and work on it at work today. Well here I am.
Problem: Phone was not connecting to computer. It kept giving me errors and then asked me to Format my card. After about half hour of trying to get it to connect I said "fine.. I'll just format it and factory reset my phone and root all over again and do all this. Well now.. phone is only connecting to (J) drive. (K) never appears.
2) Also, after rooting and finding out that ROM Manager won't work for me I have to manually download the file, I tried to go into recovery mode and every time I selected "sd card: apply update.zip", I keep getting the same error saying "FILE NOT FOUND ON SD CARD".
Any help please?
Am I doing something wrong?
Is there a way to start over, all over again?
Click to expand...
Click to collapse
development is not for posting questions, q and a is for posting questions (hence the name)
you probably built an ext container before (partitioned the card, using one of the recoveries). if you partition the card, they will come up as two disks when you plug the usb in. when you 'repaired' it, it formatted the whole thing into one block. by formatting, you've erased anything you had on it. you'll have to put the files you want back on the card.
arozer said:
Any help please?
Am I doing something wrong?
Is there a way to start over, all over again?
Click to expand...
Click to collapse
ive seen quite a few windows users on here name their file update.zip but have hidden file extensions turned on so in reality the name is update.zip.zip which will not work.
if thats not the issue, something sounds very wrong with your microsd card.
not sure why you had two partitions, J and K, but seems to hint at app2sd or had two partitions setup on the microsd card ...
my friend had one go bad on him yesterday, i had never seen it before but perhaps there is something defective.
otherwise, a reformat of the card, should bring it back to new.
Thread Moved to Q&A.
[Fixed]
joeykrim said:
ive seen quite a few windows users on here name their file update.zip but have hidden file extensions turned on so in reality the name is update.zip.zip which will not work.
if thats not the issue, something sounds very wrong with your microsd card.
not sure why you had two partitions, J and K, but seems to hint at app2sd or had two partitions setup on the microsd card ...
my friend had one go bad on him yesterday, i had never seen it before but perhaps there is something defective.
otherwise, a reformat of the card, should bring it back to new.
Click to expand...
Click to collapse
THANK YOU SOOOO MUCH!
Ok. That worked.
That was actually the problem. =D
I thought my phone was going all sorts of crazy.
Thank you thank you thank you.
---
Now installing bugless beast. Hopefully the phone will connect to my computer now.
Edit: everything seems to be running fine now.
Thanks joey.
I've searched and read guide after guide and I'm getting absolutely nowhere. I have tried to partition using ADB, I have tried to partition using a new Recovery image but I can't even change it.
Am I the only person who is having this trouble?
Can anyone see where I am going wrong....
Phone was modified using unrevoked3 and has Clockworkmod 2.5.0.1 on it.
I have downloaded the SDK for windows package and extracted it to C:\Android I then run CMD in administrator mode, go to the directory and type 'adb shell'... works fine so I then disconnect and then type 'adb shell reboot recovery' and I get 'reboot: no such tool'. I have also tried rebooting the phone into recovery mode myself but when I try to connect to it via 'adb shell' it tells me there is no device (It shows in the device manager just the same as it did before). Screeched to a halt there.
Next I thought I would change the recovery image to "RA-desire-v1.7.0.1-R5". According to the comments in the thread I can use unrevoked to install this image. I run the program select the image, plug the phone in and away it goes. After 10 mins of it saying "waiting on root, you can safely reboot" or something like that I gave up and took the battery out as nothing was happening.
Where am I going wrong here? I am only trying to get an EXT3 partition onto the phone so that I can put the apps on there and having it run faster.
This is a VERY brief runthrough of what I have done. I have been searching for about 10 hours in total, reading guide after guide and trying to follow them. I don't even get past the first couple of steps and there is an awful lot of wrong and old information out there.
Oh, as a side note. Is there any way to have the OS boot up in 10 seconds like Sense on the desire z?
Thanks for any help, I'm at my wits end.
if you r rooted download Rom manager from market and select partition SD card
secondly u can get fast boot if you flash the hd Rom in Android development section
'adb shell reboot recovery' written in only one line leads you to nowhere, you should open the shell with 'adb shell' and then issue the command 'reboot recovery' (never used that last one so I don't know if it works).
Appart from that you should do what is said in the above post, just download ROM Manager and partition your SD from there (you will need to go back to clockworkmod, but I think you don't need to do unrevoked again since you are already root)
Thanks a lot guys. Will give this a go tomorrow.
Sounds so simple too, can't believe the way I was going about it.
if you have a cd rw on your pc, just download the gparted live cd ....... its awsome
i'm also struggling with this...also followed the methods OP has posted and getting no where..dont want to use ROM manager because i want to have around 1/2GB space for partition...ROM manager only allows a maximum of 512mb
Worked flawlessly, I can't believe how much searching I done and the answer was so simple.
Off to see what I can do with it now
killa_byte said:
i'm also struggling with this...also followed the methods OP has posted and getting no where..dont want to use ROM manager because i want to have around 1/2GB space for partition...ROM manager only allows a maximum of 512mb
Click to expand...
Click to collapse
If using windows download
Acronis*Disk*Director*Home (it is paid)
or
Linux (free) -- through USB
http://www.ubuntu.com/desktop/get-ubuntu/download
dexteral said:
secondly u can get fast boot if you flash the hd Rom in Android development section
Click to expand...
Click to collapse
Just gave this a go and it takes even longer to load lol. Once it hits the Matrix screen it's quick enough. The white screen with HTC is where it takes forever. It takes literally AGES.
The setup looked good too but I think I'll be back to froyo.
Scott M said:
Just gave this a go and it takes even longer to load lol. Once it hits the Matrix screen it's quick enough. The white screen with HTC is where it takes forever. It takes literally AGES.
The setup looked good too but I think I'll be back to froyo.
Click to expand...
Click to collapse
have you ticked fasboot in the option menu i think it was in applications menu
http://www.youtube.com/watch?v=GUdal1o9e38
dexteral said:
have you ticked fasboot in the option menu i think it was in applications menu
http://www.youtube.com/watch?v=GUdal1o9e38
Click to expand...
Click to collapse
Ah haaa
No I didn't. Will give that a go. Is there a link to information on the fastboot? Does it use the battery or just store the current memory to the SD card (Like hibernation)?
Thanks
Scott M said:
Ah haaa
No I didn't. Will give that a go. Is there a link to information on the fastboot? Does it use the battery or just store the current memory to the SD card (Like hibernation)?
Thanks
Click to expand...
Click to collapse
jus search there, u'll know everything u need to know.
http://forum.xda-developers.com/showthread.php?t=789830
dexteral said:
If using windows download
Acronis*Disk*Director*Home (it is paid)
or
Linux (free) -- through USB
http://www.ubuntu.com/desktop/get-ubuntu/download
Click to expand...
Click to collapse
installed ubuntu on my USB how do i partition the sd card?
Woowww 157 pages lol. My head SERIOUSLY hurts.
I managed to get the fast boot thing to work by selecting "Hibernate" rather than "Power Off". Going by the desire Z demo, it can shutdown and restart in approx 10 seconds without going into hibernation (Can't remove battery/power).
Still, I'm going to have a play around with the HD firmware you liked to. It seems to be getting very good reports
Fingers crossed on the camera getting sorted out soon.
Thanks again for your help.
Scott M said:
Woowww 157 pages lol. My head SERIOUSLY hurts.
I managed to get the fast boot thing to work by selecting "Hibernate" rather than "Power Off". Going by the desire Z demo, it can shutdown and restart in approx 10 seconds without going into hibernation (Can't remove battery/power).
Still, I'm going to have a play around with the HD firmware you liked to. It seems to be getting very good reports
Fingers crossed on the camera getting sorted out soon.
Thanks again for your help.
Click to expand...
Click to collapse
scott can u provide any guidance to a first time rooter?
i'm really stuck...all i want to do is partition my sd card with 1/2gb for apps and the rest for my files etc.
killa_byte said:
scott can u provide any guidance to a first time rooter?
i'm really stuck...all i want to do is partition my sd card with 1/2gb for apps and the rest for my files etc.
Click to expand...
Click to collapse
Rom manager did it all for me bud. Is your phone already rooted? With a custom firmware? If so just download "Rom Manager" from the market and run it
killa_byte said:
scott can u provide any guidance to a first time rooter?
i'm really stuck...all i want to do is partition my sd card with 1/2gb for apps and the rest for my files etc.
Click to expand...
Click to collapse
ubuntu 9.10 netbook remix
what i did
intalled on d drive
ran ubuntu
on device boot to recovery > mount usb, should be detected,
on ubuntu unmount by rick clicking on the file sytem on left side. now go to the disks and right click on the sd card and create a partition.
or search youtube to format sd card
what other s did
http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=772325
hope m clear
dexteral said:
ubuntu 9.10 netbook remix
what i did
intalled on d drive
ran ubuntu
on device boot to recovery > mount usb, should be detected,
on ubuntu unmount by rick clicking on the file sytem on left side. now go to the disks and right click on the sd card and create a partition.
or search youtube to format sd card
what other s did
http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=772325
hope m clear
Click to expand...
Click to collapse
it sounds clear enough but ubuntu takes 5 hours to install on a usb drive...is this normal?
killa_byte said:
it sounds clear enough but ubuntu takes 5 hours to install on a usb drive...is this normal?
Click to expand...
Click to collapse
takes half hour tops if run from hard disk. 600 mb file ... not sure abt usb though
I just received my replacement G2 (after two decades of owning a cell phone, I finally joined the ranks of those spilling drinks on them) and am in the process of rooting it. I'm using this guide from the Wiki and everything has been working however I'm stuck at the downgrade process. After I run 'adb reboot bootloader', I press the power button as instructed but absolutely nothing happens.
I've checked and double checked the MD5 as well as that the file is named PC10IMG.zip and not PC10IMG.zip.zip but every time I follow the steps, still nothing happens.
when you boot into bootloader it should automatically search for a couple different files on sd card, do you see the text scrolling?
if so it is either not on the root of sdcard (not in any folders)
or it is not named correctly (windows hides extensions sometimes, but it looks like you know this)
or sd isnt mounting (bad tray or whatever)
or sd isnt partitioned to fat32
only reasons why it wouldnt find it
but either way fastboot is safer so why not just use this method? it should be in the guide you linked