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!!!
Related
Hi, I've had lot's of problems with my HTC recently, no adb access etc, device not being recognised and recovery playing up, ie not being able to wipe install roms etc... however I fixed the recovery issue and managed to do a nandroid backup, I put on I think it was 1.5 HTC sense hero rom... and recently realised that i can only flash 1.5 roms, not 2.1 anymore? would any developer know what would of caused this problem? Any 2.1 rom just locks on the Hero logo, and I've left it for over an hour in some cases and nothing happens. Again, I used to be able to put on any custom rom.... I'm all out of ideas.
wipe
did you wipe? what recovery image you using etc etc?
1. post in the correct section.
2. remove the ext4 partition from your sdcard, or change it to ext2 or ext3.
3. get adb logcat, otherwise this is like the question "my car won't run, can anybody tell me why?"
I have wiped numerous times... sorry for the "my car won't run type question etc...." just that I've done my research, gooogled, posted detailed info previously on here and another forum, I even fixed my own problem of the recovery image, without fixing that I would have nothing. But anyway the card is partitioned with swap, ext2, fat32 using the latest Amon_Ra image 1.6? something... i've spent weeks trying to resolve this and learnt a lot along the way.
Obviously not where to find the adb logcat... don't worry I'll google it.
Apologies for posting in the wrong forum, if it can be moved could a mod do so?
i had this problem with my magic,Using the goldcard method to downgrade and starting from scratch will fix this
bonesy said:
i had this problem with my magic,Using the goldcard method to downgrade and starting from scratch will fix this
Click to expand...
Click to collapse
Thanks for your reply, I will approach this method again at some point and give it a try, but I think I read somewhere that I couldn't do it for whatever reason, but I'll look into it again seeing as you've had the same issues. Thanks.
bonesy said:
i had this problem with my magic,Using the goldcard method to downgrade and starting from scratch will fix this
Click to expand...
Click to collapse
Actually I believe I didnt attempt this because I was no longer able to get my HTC hero working with ADB, as soon as I plug the device in, it comes up as device unrecognised, so I think goldcard method it out.. :-(
on the risk of offending you again (even though i am trying to help here...): you did not provide really much valid info. for most things you just said "doesn't work". what happens if you start by pushing home+power? saying the recovery doesn't boot up tells what does NOT happen, for a diagnosis we need the info what DOES happen.
anyway, if i get you right your recovery is now working. now repartition your sdcard (ext2 and fat, NO swap), do a full wipe, then install the rom you desire to use, then move the log to sdcard ("other" in recovery). reboot your phone and execute "adb logcat > c:\logcat.txt" on your pc. if it doesn't boot up after five minutes stop logcat with ctrl-c and post the two logfiles (recovery.log and logcat.txt). you need to set up adb, if you have problems with that sort them out, there is no way to get any information about your problem without the log.
oh, and about the goldcard: i don't know too much about goldcard'ing, but i can't see how this should help here. my strongest guess is that the swap partition interferes with the boot process...
No worries no offence taken. Pushing Home+Power works and takes me to recovery. Back+Power takes me to bootloader and USB Bootloader device is recognised, so I am able to get Fastboot.
Just recently installed stock rom, to see if that solved the USB and ROM issues but no such luck, re-rooted, put anom latest recovery back on, and went on to do what you have advised to help.. i've attached only the recovery.log in zip format only, as when doing adb logcat command use mentioned(after installing new rom), all I get is "waiting for devices" whilst the phone is stuck on the Hero logo, I waited about 10 minutes, exited from the adb, and the log file was empty as I guessed. I've tried every possible way that I found on the web to try and get the ADB function working again and I realise this is important to get some info.. but I've ran out of ideas for that.
Maybe the recovery(attached) may show something, all I noticed is that the cache and something else was not wiped for some reason? If you or someone has time, have a look through maybe someone knows what is going on.
Thanks for your help and patience
Tuesday night I loaded CM7, and then the Market wouldn't update my apps so I decided I would restore BAMF 1.5. After doing so, the Market just gave me "Fails" trying to update, and I could not access recovery, as I was going to do a complete wipe and reflash. Most of Wednesday, an extremely helpful & knowledgable member, Mattgyver83, tried diligently to help me rectify the situation, but to no avail. We tried to Fastboot, tried flash_image, tried fix permissions...shoot, I practically wore out adb..anyway, I ended up reverting back to stock and unrooted. I used jcase's method to revert back to stock, and that was painless, and successful. I decided last night to try rooting again, thinking a fresh root would solve my issue of not being able to access recovery. Root was successful, but I still cannot access recovery, through rom manager, or through bootloader. When I attempt it my Tbolt goes to white HTC screen, and stays there. All functions of my phone now work, and all aspects of root work, except I cannot flash anything. Rom manager shows I have clockwork recovery, but I just can't get to it.
Sorry for the long ramble. If anyone has had this issue, or if anyone knows a fix, I would appreciate it. Otherwise, I wait for Gingerbread.
Thanks
Happened to me with CM7 builds. For some reason they were erasing the recovery. Just have to reflash the recovery in Rom Manager and you'll be all set in the future.
do what i do pull batt leave out for a min, then put the batt back in and connect usb right away.
travishamockery said:
Happened to me with CM7 builds. For some reason they were erasing the recovery. Just have to reflash the recovery in Rom Manager and you'll be all set in the future.
Click to expand...
Click to collapse
Tried that, but thanks. Still just goes to white HTC screen, and stays there until I do battery pull.
jr4000watts said:
do what i do pull batt leave out for a min, then put the batt back in and connect usb right away.
Click to expand...
Click to collapse
I can get to bootloader, just not able to get into recovery.
I'm stabbing in the dark at this, but this did work for me with my Droid...
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Ie. Flash recovery and wait until the confirmation pop-up/message only takes a few seconds to pop up. If the message takes longer than 5 seconds or so, re-flash recovery and repeat until the confirmation comes up quickly.
This sounded retarded to me, but I was at the end of my rope so I tried it. It worked like a charm.
M.
monolithic said:
I'm stabbing in the dark at this, but this did work for me with my Droid...
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Ie. Flash recovery and wait until the confirmation pop-up/message only takes a few seconds to pop up. If the message takes longer than 5 seconds or so, re-flash recovery and repeat until the confirmation comes up quickly.
This sounded retarded to me, but I was at the end of my rope so I tried it. It worked like a charm.
M.
Click to expand...
Click to collapse
Thanks, but that didn't work. I think something in my os got lost when I restored BAMF from CM7.
Yea I spent a good few hours yesterday trying to help Orio out and we attempted a ton of things to try and fix the recovery issue, this post should offer a bit more insight to the methods used, this is running off memory;
adb reboot recovery failed
Reinstall latest Rom Manager apk and Flash CWM
flash latest rom manager via fastboot (CWM only)
(fastboot flash recovery /sdcard/recovery-clockwork-3.0.2.5.img)
**did not do fastboot erase recovery first**
"return to stock safely and properly" XDAthread by jcase
return to stock image [RUU], reroot, try again
try to boot into recovery via hboot
manually installed fix_permissions.sh script and busybox on rooted stock, ran.. didnt fix
tried to see if flash_image method would work, didn't
All of the above have failed and we basically tried almost all combinations. Not once would this phone get back into recovery, even after flashing the appropriate RUUs which include either stock android or CWM recovery. The only thing we have not currently attempted which might be the last thing left is to do is manually install the nandroid.sh script and do an advanced restore of the recovery image only from a nandroid backup on SD. I would rather not go down this method as it could have an undesired result, I have done it to restore a G1 back in the day but not 100% if its gonna work on a tbolt. Thankfully his phone boots, and we can get into hboot, but yea.. pretend recovery just doesnt exist at all...
Curious if anyone has any knowledge above what we have already tried.
monolithic said:
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Click to expand...
Click to collapse
I recall the same thing and its a good thought however that was mostly a generic error due to a CWM update and CM6 (I think) but either way flashing an RUU should override this shortcoming and im pretty sure that issue was worked out in CWM as well.
Not to be rude, but I don't think this question belongs in the development section.
Orio56 said:
I can get to bootloader, just not able to get into recovery.
Click to expand...
Click to collapse
do you still have the P zip file for the radio (baseband) on your SD card? if you do....try to delete it...then hold power and volume down button down....then see if you can get into recovery....
probably not going to work...but it is worth a try......
hogowner said:
do you still have the P zip file for the radio (baseband) on your SD card? if you do....try to delete it...then hold power and volume down button down....then see if you can get into recovery....
probably not going to work...but it is worth a try......
Click to expand...
Click to collapse
Thanks, but no, I deleted that after loading it. I actually reverted back to stock/unrooted last night and rerooted and the problem still remains. It's quite strange.
maybe i missed it if someone suggested this but what about flashing an older version of CWM?
shelooga said:
maybe i missed it if someone suggested this but what about flashing an older version of CWM?
Click to expand...
Click to collapse
That is what I was going to suggest. In ROM Manager at the very bottom try and flash an older version.
Sent from my ADR6400L using XDA Premium App
SUCCESS !!!
I fixed it !
Apparently, when I loaded up cm7, files showed up about the same time on my sdcard in clockworkmod download file. I deleted those files, and reflashed clockworkmod in rom manager, (which this time took like 3 - 4 minutes), and rebooted into recovery and it worked...did it again, just in case it was a fluke and it worked.
All is well now...the planets are realigned !!!
Thanks everyone for your ideas and especially thanks to mattgyver83 who helped me for something like 4 hours yesterday. Exceptional kindness !!
mods...you can close this thread.
GREAT NEWS!!!! CONGRATULATIONS!!
THANKS FOR REPORTING BACK!
This may help out other members with the same problem!!
now go ahead and start playing with your T-BOLT again!
That's a very odd solution. My first two things to try would have been:
1) fastboot:
fastboot erase recovery
fastboot flash recovery C:\some\local\path\recovery.img
You can't, well, probably shouldn't, flash a recovery from the /sdcard. When in fastboot mode I don't think the sdcard is even mounted. Either way, I think fastboot needs the img file on the local file system.
2) Create a PG05IMG.zip file with the recovery.img file in it, and flash that through HBOOT. Although this should have been done in some form or fashion when you downgraded or re-rooted, so YMMV.
Ok, this is my first post so be gentle. I tried to root my sons phone and now it's useless. I went thru HTC's website to unlock bootloader due to having HBOOT 1.5. I'm unlocked and thinking life is good but, I loaded several different ROM's and get the same result. It starts to load the ROM and reboots, sometimes it goes into a safemode with the Viper Rom. I've been jacking with this for 2 days and need some help. I can't find a good link for the RUU or PG86...bla bla bla, I would take it back to stock and surrender but, can't even do that. I've installed TWRP and CWM, just to try different stuff, but get all the same reults.
I think you need to flash the boot.img separately. I'm not sure though. There's a thread for flashing with 1.50 somewhere in the development section
We're comin from a pure power source.
I am having the same issue here, I installed several ROMS, it works for a day, but then the reboot attack starts. Constant lockups and random restarts, sometimes 3 reboots in a row.
ROMs I tried to flash:
1. Xperia XE
2. Titan Trinity 3 HD
3. Nocturnal Adrenaline 1.0.2
Maybe it's the kernel, is there a list of kernels that I can flash?
This worked for me
My phone kept rebooting after root before, but I managed to fix it. This will only work if you can get into fastboot. Download the ruu file located here and run it while in fastboot. This will unroot your phone if you have S-On. After that is done, if it still loops, take out the battery and count to five, then put the battery in and hold the power button on the phone until the phone starts to turn on normally. That fixed my problem, hope it fixes yours. You may have to update after you get your phone started and you will lose all your data. Sorry about the link, I updated to one that has a working download.
armydude13090 said:
My phone kept rebooting after root before, but I managed to fix it. This will only work if you can get into fastboot. Download the ruu file located here and run it while in fastboot. This will unroot your phone if you have S-On. After that is done, if it still loops, take out the battery and count to five, then put the battery in and hold the power button on the phone until the phone starts to turn on normally. That fixed my problem, hope it fixes yours. You may have to update after you get your phone started and you will lose all your data. Sorry about the link, I updated to one that has a working download.
Click to expand...
Click to collapse
Unroot my phone?
Is it possible to re-root it?
Thanks all for the posts. I will give some of this a shot and see what happens. I can get to fastboot, and have loaded a couple of things thru the cmd prompt to try and help, but nothing so far. I'm not really sure if the kernel thing is what's stopping the roms for loading. I can't get the S-OFF, I'm unlocked. I can send anything I want thru the cmd prompt, and also flash zips thru twrp or cwm. Would like to start over but ca't even find a way to do that. Thanks again for the posts.
Cardmastr, we're on the same boat, pg86 takes forever to download, so as I'm waiting patiently, keep me in on the loop with what you're doing.
RUU didn't cut it, kept failing. have not found an image file to flash thru the cmd prompt. Still no luck. What can I throw into fast boot that might help me?????!!!!!!
When I started flashing after using HTC Unlock, I ran "fastboot boot recovery.img" - which booted TWRP with the necessary permissions. Then I wiped everything and flashed the ROM. Haven't had any issues with the ROMs I've tried.
Which recovery did you install? Twrp 1.1.1 is your best bet.
The 2.x version twrp or cwm do not okay nice with some phones.
S3nt from my 3D wond3rland
I used the TWRP 1.1.1. Might of messed up with some of the cmd prompt stuff I'm going back thru.
thefsfempire said:
When I started flashing after using HTC Unlock, I ran "fastboot boot recovery.img" - which booted TWRP with the necessary permissions. Then I wiped everything and flashed the ROM. Haven't had any issues with the ROMs I've tried.
Click to expand...
Click to collapse
Everyday is Halloween for u dude!! UR a Monster! This little tidbit hooked me up. Thanks to you we are back in game.
When installing a ROM, doesn't it wipe /data, /system, etc for us?
Not the first post a noob really wants to make...but I've been searching the forums for an answer to my problem, but can't seem to find the info on the issue I'm having. I've seen some that were close & tried what was posted there without any success. I've checked out the Don't Panic -- Please Read First, includes troubleshooting guide Thread By: om4
A few days ago, I tried to install CM10 on my 4G LTE w/S-ON / HBOOT- 1.19. I was able to unlock the bootloader & install TWRP. Everything seemed to go okay until I rebooted my phone after installing CM10. It just hung on the Cyanogenmod splash screen. I tried re-installing it & kept getting the same problem. Today, I tried to install MeanROM ICS v6.5, but it keeps saying install failed. If I let the phone boot up, it'll hang on the MeanRom splash screen. I can still get into fastboot so I know it has to be a software issue. I've been beating my head against the wall for the past few days & just don't know how to fix it. Right now I have a very expensive paperweight. I'm hoping someone can help me fix this & get my phone back up & running.
TIA
for the millionth time
flash the boot.img seperately in hboot
Get (Flash Image GUI) off the Play Store.
If yr S-ON then u have to flash the kernel separate. That's why the ROM's keep hanging.
sent from my EVO LTE
http://forum.xda-developers.com/showthread.php?t=1772769&highlight=fastboot+gui
flex360 said:
for the millionth time
flash the boot.img seperately in hboot
Click to expand...
Click to collapse
I've been trying this all day, but must be doing something wrong. I found this: http://forum.xda-developers.com/showpost.php?p=29417266&postcount=1397, but was wondering if you might have more info on option 3.
TIA
if you know how to Fastboot, go for it, but use the Boot.img from the ROM you are flashing.
popper668 said:
if you know how to Fastboot, go for it, but use the Boot.img from the ROM you are flashing.
Click to expand...
Click to collapse
It's the only option I have now, so I hope I can figure it out. Wish me luck. I know it's probably something stupid that I'm missing & it's driving me crazy. lol
For meanrom make sure you have twrp 2.2.2.0 or later to be able install. The kernel installer will force the phone to reboot upon first run, this is when the kernel installs. For cm10 or other aosp based roms be sure to properly wipe phone. Cache, dalvik, factory reset, and system. Fastboot the kernel using SDK, mini SDK, uniflash, or boot image flasher. Do not use clockwork mod recovery to install roms as it is known to damage internel storage and or misc partitions.
ADB Tools Mini SDK
Thanks for all the info!!! I'm glad I found this place!!! I was able to get my phone working again. I found this post: http://forum.xda-developers.com/showthread.php?t=1937949 from back in October and found out that I was putting the boot.img in the wrong location. Once I fixed that, I have my phone back. Now I have to get it re-activated because I had to switch back to my Hero because I wasn't sure how long this would take. I hope Sprint will activate it even though is not stock anymore.
buddahj said:
Thanks for all the info!!! I'm glad I found this place!!! I was able to get my phone working again. I found this post: http://forum.xda-developers.com/showthread.php?t=1937949 from back in October and found out that I was putting the boot.img in the wrong location. Once I fixed that, I have my phone back. Now I have to get it re-activated because I had to switch back to my Hero because I wasn't sure how long this would take. I hope Sprint will activate it even though is not stock anymore.
Click to expand...
Click to collapse
have your first thanks
lol
the thanks is for using the search function lol
Well now I have another small problem. When I try to use the camera or go into gallery, it says no external storage available. Looks like I'm off to search the forums again for a fix. I'm sure it's something minor.
It looks like it's the internal SD card. Under storage in settings it shows the external card's total space & the 3 GBs used for app data, ect...
When I try and mount the SD card, it says preparing card but doesn't do anything. I think I say something about changing something in TWRP.
Forgot to mention, I can't connect the phone via USB either.
Ha, fixed my SD card/USB issues by following the directions in this thread - http://forum.xda-developers.com/showthread.php?t=1812774
Ok so here's the deal...
I was running ViperRez ROM and decided it was time for a change and found a few ROMs I wanted to check out. Tried EclipticRez, kept force closing and rebooting before or just after I could finish the phone set up. Tried Nils Business, no luck. So finally tried to load MIUI for ICS and ran into trouble.
Each time before loading these ROMs I used Clean Wipe to wipe before loading the ROM. I am S-on. Unlocked. HBOOT- 2.11
So here's where my trouble is... Normally when a ROM fails to work, I'd simply reboot into recovery, wipe, and load a different rom via zip from SD card. The problem I'm having, besides the ROM not loading and getting stuck on the HTC flash screen is, I cant get into recovery. I can reboot into the bootloader screen, get to fastboot. When I try to select recovery the phone goes black, flashes something quickly on the lower part of the screen with CWM recovery looking logo, then reboots and sticks on the HTC white screen. Another issue, my battery will no longer charge via phone charger, so I had to go out and buy a battery charger today to even get my phone running again since all this drained the battery.
I've flashed the PH98IMG, removed it since it was causing me to constantly reflash it and reboot. Removed the boot img from the MIUI ROM and placed it in the root of my SD card, seemed to do nothing. I've also tried to use abd, although I'm not really sure how to use it, basically tried to follow a few different threads, but when I typed adb devices, the list was always blank.
Can anyone help me to either get this MIUI ROM working or at least get me back into recovery so I can re-load ViperRez that I know was working? I am no expert, so please give detailed instructions if you can. Thanks in advance.
ronin_rone said:
Ok so here's the deal...
I was running ViperRez ROM and decided it was time for a change and found a few ROMs I wanted to check out. Tried EclipticRez, kept force closing and rebooting before or just after I could finish the phone set up. Tried Nils Business, no luck. So finally tried to load MIUI for ICS and ran into trouble.
Each time before loading these ROMs I used Clean Wipe to wipe before loading the ROM. I am S-on. Unlocked. HBOOT- 2.11
So here's where my trouble is... Normally when a ROM fails to work, I'd simply reboot into recovery, wipe, and load a different rom via zip from SD card. The problem I'm having, besides the ROM not loading and getting stuck on the HTC flash screen is, I cant get into recovery. I can reboot into the bootloader screen, get to fastboot. When I try to select recovery the phone goes black, flashes something quickly on the lower part of the screen with CWM recovery looking logo, then reboots and sticks on the HTC white screen. Another issue, my battery will no longer charge via phone charger, so I had to go out and buy a battery charger today to even get my phone running again since all this drained the battery.
I've flashed the PH98IMG, removed it since it was causing me to constantly reflash it and reboot. Removed the boot img from the MIUI ROM and placed it in the root of my SD card, seemed to do nothing. I've also tried to use abd, although I'm not really sure how to use it, basically tried to follow a few different threads, but when I typed adb devices, the list was always blank.
Can anyone help me to either get this MIUI ROM working or at least get me back into recovery so I can re-load ViperRez that I know was working? I am no expert, so please give detailed instructions if you can. Thanks in advance.
Click to expand...
Click to collapse
Have you tried fastboot flashing the boot.img?
gleggie said:
Have you tried fastboot flashing the boot.img?
Click to expand...
Click to collapse
I have tried. Although Im not sure it worked right, or if I even did it right. Just an update. I tried flashing another PH98IMG and it said it was older. Still stuck
ronin_rone said:
I have tried. Although Im not sure it worked right, or if I even did it right. Just an update. I tried flashing another PH98IMG and it said it was older. Still stuck
Click to expand...
Click to collapse
your are s-on you need to extract the boot.img from the zip. go to fastboot and make sure it says fastboot usb
fastboot flash boot boot.img
that will flash the kernel that you need. the ph98img you only need if you are trying to make firmware changes. everything else can be run from the computer.
Also, make sure you are flashing 3.04 roms. Viperrez i think never updated to the global . If you are flashing global roms, you HAVE to do the firmware update.
dragonstalker said:
your are s-on you need to extract the boot.img from the zip. go to fastboot and make sure it says fastboot usb
fastboot flash boot boot.img
that will flash the kernel that you need. the ph98img you only need if you are trying to make firmware changes. everything else can be run from the computer.
Also, make sure you are flashing 3.04 roms. Viperrez i think never updated to the global . If you are flashing global roms, you HAVE to do the firmware update.
Click to expand...
Click to collapse
I kinda understand what you are saying, but the other problem I have is.... When running adb my phone is not listed in the adb devices, although it is listed in the usb devices. Not sure what to do about that.
Are you in charge only mode on the phone?
Is usb debugging enabled?
USB debugging was selected prior to this incident and it was on charge only as well. It was not connected as a usb drive. I cannot get into the settings of the phone to find out what it is now or if its changed.
I would suggest going S-Off, it will make flashing a whole lot easier. As for getting back to a usable state, you should be able to flash a PH98IMG in bootloader. If anything, flash an RUU and go from there.