i have the evo 3d and flashed some roms and alwats did back ups but tried the miui rom and now usb does not work at all...tried restoring or flashing other roms that were already on my usb cant do commands cuz usb doesnt work can someone please help
babybear293 said:
i have the evo 3d and flashed some roms and alwats did back ups but tried the miui rom and now usb does not work at all...tried restoring or flashing other roms that were already on my usb cant do commands cuz usb doesnt work can someone please help
Click to expand...
Click to collapse
can't do commands via usb, i'm reading this to mean, you don't have adb access.
after wiping the /data partition, where system settings are stored, including the toggle for adb access via, you will probably have to re-enable.
to enable adb access via usb on sense -> settings -> applications -> development -> usb debugging. this should be toggle on.
if that doesn't work, post back and we can start digging deeper but i'm hoping that'll resolve your isse!
I apologize in advance for being lengthy, but I want to be thorough to give you a good idea of what I did. Hopefully someone will point out what I did right or wrong.
I had this same exact problem with MIUI the other day. I am not an expert on rooting/flashing, but I was able to resolve the issue with a little trial and error.
I flashed MIUI on my 3d. I wasnt too impressed with it really and flashed back to Eternity. A few days passed and I decided to give MIUI another shot and flashed back a second time. Mind you, I always do a factory reset twice, wipe cache twice, and wipe dalvik cache twice before any flash (even if it is an updated version of the ROM I am using), so I made sure to wipe everything before flashing. When I flashed I noticed the little bug on the notification bar area of MIUI and thought it was a clever way of showing debug mode was on.
After messing with it some more I realized that I just plain didnt like it and giving it any more time was not neccessary. I decided to flash back to Eternity. I booted up my phone into bootloader and tried to get into fastboot USB, but it wouldnt activate when I put my USB in. I rebooted into MIUI to make sure I didn't mistakenly turn debugging off. It was still on. I tried to get into fastboot USB a second time. Still an error. I searched XDA came across this thread. Noted that USB debug was on. Followed steps, no progress.
At this point I figured I would just try to flash eternity to see what happened without using fastboot. Froze on bootup. So I flashed MIUI back on. I then remembered hearing about Flash Image GUI on market (made by JoeyKrim who posted above me in this thread). I figured I would give it a shot.
Failed. I had Ziggy kernel from Eternity already on my SD, so I flashed that. It said it was successful. So I powered down. Then I booted into bootloader and went into recovery. I tried to flash Eternity and it froze during boot. I tried to boot up several times and always froze. I went back to MIUI figuring that perhaps the kernel really didnt flash. MIUI made it past boot, to the lockscreen, but I couldnt unlock it. Bascially I was stuck. None of the buttons worked except for power. I tried again to reboot MIUI again. Same problem.
Starting to get a bit desperate, and not being able to get into fastboot USB at all, I figured I could try to nand restore to stock rooted. Of course...still wont work since I couldnt access fastboot USB. My screen froze during boot on this as well.
So here I am stuck with no fastboot USB, a restore that wont flash, Eternity wont flash, and MIUI isnt responding. Honestly I was getting upset and had half a mind to hit the phone with a stun gun and take it to Sprint. (not my idea, but a Sprint person told me once to fry it and take it in and they would say it was a battery short which fried it). Anyhow. I then figured I would try RUU. Problem was that I heard RUU wont work unless you are locked. So I tried to re-lock, and of course couldnt do it since fastboto USB wont work.
I decided to hit the RUU anyhow and it failed saying it was Security fail. I wazs thinking of options, hit it with stun gun hopefully sprint replaced, sink it and insurance replace it, or just head to sprint to see if they could help. But much to my surprise, I tried to boot into bootloader one more time and sure enough fastboot USB was back. My recovery was gone, so I flashed CWM again and was able to put eternity back on. The only problem is that my CWM was deleted and I lost my Nand. Not too big a deal as I can always put a stock rooted rom on and use that as my Nand. Or I can always just RUU to stock, then re-root just to be certain I have a clean nand.
Alright guys. Anyone care to comment on what could have been done differently?
thos25 said:
I apologize in advance for being lengthy, but I want to be thorough to give you a good idea of what I did. Hopefully someone will point out what I did right or wrong.
I had this same exact problem with MIUI the other day. I am not an expert on rooting/flashing, but I was able to resolve the issue with a little trial and error.
I flashed MIUI on my 3d. I wasnt too impressed with it really and flashed back to Eternity. A few days passed and I decided to give MIUI another shot and flashed back a second time. Mind you, I always do a factory reset twice, wipe cache twice, and wipe dalvik cache twice before any flash (even if it is an updated version of the ROM I am using), so I made sure to wipe everything before flashing. When I flashed I noticed the little bug on the notification bar area of MIUI and thought it was a clever way of showing debug mode was on.
After messing with it some more I realized that I just plain didnt like it and giving it any more time was not neccessary. I decided to flash back to Eternity. I booted up my phone into bootloader and tried to get into fastboot USB, but it wouldnt activate when I put my USB in. I rebooted into MIUI to make sure I didn't mistakenly turn debugging off. It was still on. I tried to get into fastboot USB a second time. Still an error. I searched XDA came across this thread. Noted that USB debug was on. Followed steps, no progress.
At this point I figured I would just try to flash eternity to see what happened without using fastboot. Froze on bootup. So I flashed MIUI back on. I then remembered hearing about Flash Image GUI on market (made by JoeyKrim who posted above me in this thread). I figured I would give it a shot.
Failed. I had Ziggy kernel from Eternity already on my SD, so I flashed that. It said it was successful. So I powered down. Then I booted into bootloader and went into recovery. I tried to flash Eternity and it froze during boot. I tried to boot up several times and always froze. I went back to MIUI figuring that perhaps the kernel really didnt flash. MIUI made it past boot, to the lockscreen, but I couldnt unlock it. Bascially I was stuck. None of the buttons worked except for power. I tried again to reboot MIUI again. Same problem.
Starting to get a bit desperate, and not being able to get into fastboot USB at all, I figured I could try to nand restore to stock rooted. Of course...still wont work since I couldnt access fastboot USB. My screen froze during boot on this as well.
So here I am stuck with no fastboot USB, a restore that wont flash, Eternity wont flash, and MIUI isnt responding. Honestly I was getting upset and had half a mind to hit the phone with a stun gun and take it to Sprint. (not my idea, but a Sprint person told me once to fry it and take it in and they would say it was a battery short which fried it). Anyhow. I then figured I would try RUU. Problem was that I heard RUU wont work unless you are locked. So I tried to re-lock, and of course couldnt do it since fastboto USB wont work.
I decided to hit the RUU anyhow and it failed saying it was Security fail. I wazs thinking of options, hit it with stun gun hopefully sprint replaced, sink it and insurance replace it, or just head to sprint to see if they could help. But much to my surprise, I tried to boot into bootloader one more time and sure enough fastboot USB was back. My recovery was gone, so I flashed CWM again and was able to put eternity back on. The only problem is that my CWM was deleted and I lost my Nand. Not too big a deal as I can always put a stock rooted rom on and use that as my Nand. Or I can always just RUU to stock, then re-root just to be certain I have a clean nand.
Alright guys. Anyone care to comment on what could have been done differently?
Click to expand...
Click to collapse
Well there is a lot going on in that post ... Not sure how my application Flash Image GUI failed. I would be more than happy to fix/resolve any bug or issue you've encountered!
Fastboot usb mode should always work. There is no setting in Android which will have any impact on fastboot usb mode (other than not allowing the device to boot into the bootloader). I generally find the best process to be, boot the device into the bootloader, plug in usb and then select fastboot.
Perhaps, once you're in the bootloader, you can also select fastboot and then plug in USB (this works best on my NS4G).
Either way, fastboot usb should always work. If you're using Windows, there could definitely be a drivers issue or Windows being finicky with the drivers and that might result in fastboot USB not working. A simple reboot of the Windows machine should clear any fastboot driver issues.
The best working method to correctly load a ROM is by properly loading the recovery to work with the HTC unlock method. HTC unlock method will only grant the recovery write access to the boot partition when the recovery image is temporarily fastboot boot'd. The command is: fastboot boot c:\android\cwm-recovery.img.
If you boot into the bootloader and select recovery from the menu, it will boot into the recovery, but the HTC unlock method will not grant the recovery write access to the boot partition. You can flash a ROM from here and restore a nand. Both will completely successfully and claim they flashed the kernel w/o any issues but the memory write lock will have prevented the kernel writes from being retained.
Also, regarding my application, Flash Image GUI, it should properly flash any EVO 3D kernel .zip file from normal Android mode as the HTC unlock method allows kernel write access while in normal Android mode.
Why did HTC block kernel write access from recovery mode? They haven't provided an answer .. we can only speculate ...
Hope that helps explain a few more steps to the process and provide greater clarity!
thanks Joey.
Who knows. I have no idea why your app didnt work. I would also like to point out that I am not blaming your app at all. I may have simply done it incorrectly. To be honest by the time I even used your app I was pretty frazzled, so I may have done an error.
Ok. So, yes. Everytime I flash I always use fastboot USB. The command you use is different from mine though. My command is courtesy of Zedomax (HTC Evo Hacks method). CD desktop \rootevo3dnew
fastboot boot cwm-4.0.1.4-shooter.img
So, I always use that when I flash.
I have no idea why fastboot USB dissapeared. At first I figured it was a USB port error. I have heard that many people with OG Evo and 3vo's have USB port issues. So, like a good troubleshooter, I went for the obvious and switched my USB cord. No luck. Then I figured I would plug it into the wall to charge to see if it charged. It did. So I knew it wasnt the cord and it wasnt the port.
Perhaps like you said, the driver was just wonky. I ran a check and it said driver was up to date, so I doubt it.
In the end plugging it into HTC Sync to run an RUU fixed the problem. Even though the RUU didnt go through because I was HTC unlocked, it did fix the USB error and I had USB access again. From there I was able to flash back into recovery and flash back to Eternity.
And on a side note, I also learned the importance of copying my ClockworkMod file off of my SD card and onto my desktop. Since I lost the recovery I no longer had CWM on my SD card and my nand backup was gone. So now I will always keep a copy of the folder on my desktop so that I make sure to have a working NAND.
And to be thorough I decided to re-lock, then re-unlock, re-root today as well. I figured this way I would be working with a 100% clean working ROM again to have a good NAND as a basis as opposed to downloading a stock rooted ROM. Im sure it is probably basically the same thing, but I wanted to do it this way to be sure.
thanks again. Ill let you know if I have any additional issues with your app.
thos25 said:
thanks Joey.
Who knows. I have no idea why your app didnt work. I would also like to point out that I am not blaming your app at all. I may have simply done it incorrectly. To be honest by the time I even used your app I was pretty frazzled, so I may have done an error.
Ok. So, yes. Everytime I flash I always use fastboot USB. The command you use is different from mine though. My command is courtesy of Zedomax (HTC Evo Hacks method). CD desktop \rootevo3dnew
fastboot boot cwm-4.0.1.4-shooter.img
So, I always use that when I flash.
I have no idea why fastboot USB dissapeared. At first I figured it was a USB port error. I have heard that many people with OG Evo and 3vo's have USB port issues. So, like a good troubleshooter, I went for the obvious and switched my USB cord. No luck. Then I figured I would plug it into the wall to charge to see if it charged. It did. So I knew it wasnt the cord and it wasnt the port.
Perhaps like you said, the driver was just wonky. I ran a check and it said driver was up to date, so I doubt it.
In the end plugging it into HTC Sync to run an RUU fixed the problem. Even though the RUU didnt go through because I was HTC unlocked, it did fix the USB error and I had USB access again. From there I was able to flash back into recovery and flash back to Eternity.
And on a side note, I also learned the importance of copying my ClockworkMod file off of my SD card and onto my desktop. Since I lost the recovery I no longer had CWM on my SD card and my nand backup was gone. So now I will always keep a copy of the folder on my desktop so that I make sure to have a working NAND.
And to be thorough I decided to re-lock, then re-unlock, re-root today as well. I figured this way I would be working with a 100% clean working ROM again to have a good NAND as a basis as opposed to downloading a stock rooted ROM. Im sure it is probably basically the same thing, but I wanted to do it this way to be sure.
thanks again. Ill let you know if I have any additional issues with your app.
Click to expand...
Click to collapse
I'll give you a little feedback on the process to sum up your knowledge around the edges. Everything seems correct, there are a few points.
1) CD desktop \rootevo3dnew and fastboot boot cwm-4.0.1.4-shooter.img is the same as fastboot boot desktop\cwm-4.0.1.4-shooter.img . The only difference here is where the recovery image is stored. The key part is being able to supply the fastboot binary with the correct command being "boot" instead of "flash recovery".
2)If you lose your CWM recovery, it does not always mean you have lost your nandroid images. They are stored on the sdcard card under clockworkmod directory, /sdcard/clockworkmod . Even if you switch recoveries, these files will still remain. They should never be erased unless you intentionally erase them.
3) If you really want to start with 100% clean stock ROM, running an RUU is the best way. re-lock and un-lock, all it does is toggle a setting in the bootloader and wipe your /data directory. it won't make any changes to radio, system partition, etc. an RUU will copy over most of all the partitions with stock files, completely resetting the device.
appreciate your support with my app and hope the extra details help round out the edges! good luck!
I had a similar issue when i was switching to AOSP kernels/roms. I rebooted my phones once or twice and it connected fine. Maybe it have something to do with AOSP since MIUI is aosp also.
joeykrim said:
I'll give you a little feedback on the process to sum up your knowledge around the edges. Everything seems correct, there are a few points.
1) CD desktop \rootevo3dnew and fastboot boot cwm-4.0.1.4-shooter.img is the same as fastboot boot desktop\cwm-4.0.1.4-shooter.img . The only difference here is where the recovery image is stored. The key part is being able to supply the fastboot binary with the correct command being "boot" instead of "flash recovery".
2)If you lose your CWM recovery, it does not always mean you have lost your nandroid images. They are stored on the sdcard card under clockworkmod directory, /sdcard/clockworkmod . Even if you switch recoveries, these files will still remain. They should never be erased unless you intentionally erase them.
3) If you really want to start with 100% clean stock ROM, running an RUU is the best way. re-lock and un-lock, all it does is toggle a setting in the bootloader and wipe your /data directory. it won't make any changes to radio, system partition, etc. an RUU will copy over most of all the partitions with stock files, completely resetting the device.
appreciate your support with my app and hope the extra details help round out the edges! good luck!
Click to expand...
Click to collapse
Thanks for the comments and lesson. I apologize for not responding sooner, but a recent death in family prevented me from really being on here too much lately.
1) I pretty much figured that. Yeah. I only try to flash using this method, that is why when my fastboot USB disapeared I thought I was really in a bad spot. Luckily I got it working again, so all was not lost.
2). Yes. I know it should remain on SD card, which was strange why I couldn't find it. However, thinking back on it, I do remember deleting some files off of my SD card on the same night. I probably just mistakenly deleted my CWM Recovery with my NAND backups. Sometimes when I double click a file to look at it, when I leave the file I see that there is a checkmark on that file. I may have just not noticed the checkmark on the CWM, went to delete another file, and mistakenly deleted CWM with it.
3) An RUU will not change a RADIO? I was under the impression that they did. Sort of like applying an OTA, but manually doing it through SYNC.
well, thanks again though. I learned some new things and appreciate it.
Flash image GUI works like a charm
Sent from my PG86100 using XDA App
i m a newbie
plz tell me how to get out of the fastboot usb mode. i m stuck with the G1 screen having fastboot usb title on the top.
PLZ HELP!!!
I had the stock rom installed but I had recovery on it and I decided to just load the new rom on it and I didn't realize I was suppose to root the phone before flashing. So basically everything was a little weird. When it started and was at the unlock screen it said sim card is locked and I don't have a sim card. Then later when looking at the sd card it was saying -- for the available space and space used. I tried to format it and it said please wait while calculating and was showing some odd algebra equation. Then it just did a soft reset and basically showed the IHO boot screen then the loading screen. No LG icon thus being a soft reset. But that is all it would do. And upon trying to shut it off it was showing no option to shut off just a bunch of odd icons and one saying airplane mode or something with a power icon next to it. So I chose it and it was saying something like reset and it had menu for a title. So I chose it and it shut off. So I was just wanting to make sure that if I rooted it before re installing the IHO that this would clear up those issues.
You need a custom recovery to install custom ROMs. Here is a tutorial how to flash one without rooting.
You need custom recovery to install custom roms and to flash custom recovery without rooting Follow http://forum.xda-developers.com/showthread.php?t=1318750
you just need to format your system with any method
and then flash new one
that's what recovery do
may be sometime adb also help
I have this installed on my phone: Xionia_CWMA_12518.6_VM_Recovery-signed and I use it to get the phone formated with a new rom. I know that I can get a custom rom on the phone perfectly fine when it is rooted. I guess since I did it without it being rooted it somehow made things look corrupt after installing the rom without the phone being rooted. I hope that it will work properly when I get the phone re rooted and install the latest version of the rom I use: BACKside-IHO-VM670-11022011 this is the first rom I ever used to get on my phone so I was thinking of sticking with it unless there is a more stable one that performs better and can run most anything thrown at it. As I have run into a few issues with this rom. I can end up having things run off the sd card and they end up crashing the phone and doing a hard reset as well as games or apps not wanting to work at all and give a force close error. I am really wanting to play annoying orange kitchen carnage I have even tried a stock rom at 2.2.1 and it still didn't work. Is there a specific kernel I should be installing or something?
http://forum.xda-developers.com/showthread.php?t=1197991
This should answer all your questions.
Ok thanks. Just wanted to know as I know how to root and get a rom installed on the phone. So thanks for the help.
Well I was running the leaked sense ics build and it was causing my phone to overheat so I decided I would switch back to cm7 for a while, when I when I tried to reboot to recovery it just booted showed a black screen then rebooted back to the rom. So I tried to reinstall the recovery from both rom manger and the bootloader nothing worked. I then noticed that it was hard to get my sd card out and that it was slow to load upon boot, odd but it was still readable by the system and I could get to my files on it. I treid a few other sd cards with the same results. It was then I decided it would be a smart idea to try and flash a ruu to try to just return to stock (but leave the bootloader unlocked). I ended up flashing PG05IMG_no_hboot_2.11.605.19.zip from [HOW TO]return to stock (gingerbread) from revolutionary or normal hboot(11/2/11) - xda-developers Which then lead to my phone not booting to rom or recovery all I can get to is the (still unlocked at least) bootloader.
Any ideas on where to proceed? I attempted to run a ruu exe so I can restore it from a computer in case the problem with sd is why it is failing to flash properly but the one I tried 2.11.605.0_Radio_0.01.78.0802w_3_NV_8K_1.41_9K_1.6 4_release_210841.exe required the phone to be booted to the rom to confirm the current build before flashing a new one. Anyone know of a way around that maybe? Or anything?
flamesbladeflcl said:
Well I was running the leaked sense ics build and it was causing my phone to overheat so I decided I would switch back to cm7 for a while, when I when I tried to reboot to recovery it just booted showed a black screen then rebooted back to the rom. So I tried to reinstall the recovery from both rom manger and the bootloader nothing worked. I then noticed that it was hard to get my sd card out and that it was slow to load upon boot, odd but it was still readable by the system and I could get to my files on it. I treid a few other sd cards with the same results. It was then I decided it would be a smart idea to try and flash a ruu to try to just return to stock (but leave the bootloader unlocked). I ended up flashing PG05IMG_no_hboot_2.11.605.19.zip from [HOW TO]return to stock (gingerbread) from revolutionary or normal hboot(11/2/11) - xda-developers Which then lead to my phone not booting to rom or recovery all I can get to is the (still unlocked at least) bootloader.
Any ideas on where to proceed? I attempted to run a ruu exe so I can restore it from a computer in case the problem with sd is why it is failing to flash properly but the one I tried 2.11.605.0_Radio_0.01.78.0802w_3_NV_8K_1.41_9K_1.6 4_release_210841.exe required the phone to be booted to the rom to confirm the current build before flashing a new one. Anyone know of a way around that maybe? Or anything?
Click to expand...
Click to collapse
It may not work but I've had some luck with http://forum.xda-developers.com/showthread.php?t=1703455 in rooting and unrooting, it may be able to see it and do its thing. I know you said you tried different cards but it might be worth looking into reformatting your card in Windows (FAT32) and trying it with a good radio by itself to get it to boot. Then pull or rename the radio zip off the card and then reinstall the ROM or RUU.
I am a relative noob at flashing roms and rooting phones, but last night I ran into an issue. My phone was having all sorts of problems so I was going to put it back to factory, then start from scratch. I then decided to just flash a different rom. here is what happened.
I deleted SuperSU - this was done as part of the process to unroot and put back to factory, after this step I decided to flash a different rom
Put new ROM on phones internal memory as well as SD card
Wipe data
wipe cache and delvic cache
install new rom
Black screen
In an attempt to unbrick I relocked my bootloader.
Now, my phone can power on (Give white screen and HTC logo), then go black, and I can access Recovery mode. That is all.
I have plugged the phone to my computer and tried running the RUU, but the RUU will not recognize the phone.
I am not sure what to do to unbrick my phone and get it working again. Any and all help would be most appreciated!
Sorry I can't be more eloquent with my words, but I'm at work. I will be responding throughout the day, though.
thanks again so much to anyone that can help!
Try running it straight from bootloader
I loaded into Bootloader, selected Fastboot(USB), ran the .exe and it still won't recognize the phone. However, I did get recovery unlocked again. So I can get into recovery mode, flash all the ROMs I want, mount and unmount, yet still everytime I flash a new ROM it still boots to a black screen. Am I doing this right?
Try a Rom with kernel installer
Thanks! Since I am still a little new could you tell me how I would spot a ROM with kernel installer or could you point me to any one that could work? From then, it's the same process as flashing any other ROM? Do I need to do something with the kernel?
Meanbean and stock with goodies are the 2 that I'm certain of. Meanbean needs to be flashed twice the first time
Thanks so much for your help, I will post my results soon!
Failed
Here's what it says. Sorry for the blurry picture. I followed directions closely.
What version of recovery are you using? You may need to update it. Assuming you have a pc, try mounting the internal memory to pc through twrp. Windows will automatically tell you to format if its damaged
2.1 Updating now
omg it finally worked! Updated TWRP using fastboot and flashed MeanBean. Thank you so much!!!
Trying to install MeanBean...I updated the Firmware to the latest, have the phone unlocked and rooted (it says TAMPERED and UNLOCKED in the recovery screen) and did a factory reset. I have TWRP installed and can still get to the TEAMWIN RECOVERY project interface...
I was installing MeanBean and it just stuck on about 75% and stayed there. I waited for about ten minutes and figured something must have gone wrong so I didn't really have a choice but to shut it down. After starting back up when I tried to install again it said "FAILED" in red letters. I decided to re-download the ROM but now when I mount the SD CARD from within the recovery menu (to transfer the new file) my computer says that I must format the drive before I can use it and won't let me see the contents of the sd-card. I didn't want to do that for fear of bricking...so I don't really know what to do from here. I should add that I don't have a backup made in TWRP (I got the phone yesterday and hadn't installed or done anything to the OS)
Anyone know what should be done at this point?
thx
I'm updating this for anyone else who runs into issues like this: I went ahead and formatted the SD card from within windows, then relocked the phone, reinstalled the RUU and I'm back in a workable mode
itsmattgw said:
Trying to install MeanBean...I updated the Firmware to the latest, have the phone unlocked and rooted (it says TAMPERED and UNLOCKED in the recovery screen) and did a factory reset. I have TWRP installed and can still get to the TEAMWIN RECOVERY project interface...
I was installing MeanBean and it just stuck on about 75% and stayed there. I waited for about ten minutes and figured something must have gone wrong so I didn't really have a choice but to shut it down. After starting back up when I tried to install again it said "FAILED" in red letters. I decided to re-download the ROM but now when I mount the SD CARD from within the recovery menu (to transfer the new file) my computer says that I must format the drive before I can use it and won't let me see the contents of the sd-card. I didn't want to do that for fear of bricking...so I don't really know what to do from here. I should add that I don't have a backup made in TWRP (I got the phone yesterday and hadn't installed or done anything to the OS)
Anyone know what should be done at this point?
thx
Click to expand...
Click to collapse
I had the exact same problem. I just reformatted the internal storage and that fixed a lot of my issues. I can't however get the RUU to work. Can't seem to find my phone, neither can HTC Sync. Is this just a problem caused by MeanBean? I use to run MeanBean but then switched to CM10 for a few months and was going to switch back. Never had an issue like this before.