Related
hey guys i had andromeda installed but messed the flash up by disabling lots of system stuff so i one clicked back to stock, rooted, installed rom manager like normal but every time i try to flash clockwork recovery mod it keeps telling me "An error occurred while downloading your recovery." and i cant install it so i can re-flash the rom plz help me i dont know what to do thx ahead of time
praramis said:
hey guys i had andromeda installed but messed the flash up by disabling lots of system stuff so i one clicked back to stock, rooted, installed rom manager like normal but every time i try to flash clockwork recovery mod it keeps telling me "An error occurred while downloading your recovery." and i cant install it so i can re-flash the rom plz help me i dont know what to do thx ahead of time
Click to expand...
Click to collapse
Put this on your internal SD card along with your ROM of choice. Reboot in to recovery and install packages 2 times. The second time it will be in clockwork recovery and you can flash your ROM.
I just had the same problem after doing countless ROM flashes in the past. Perhaps its something in their server preventing the download of CWM? Anyways, thanks for the .zip. Worked like a charm!
yes thank you very much for that zip u saved my life well appreciated
Keep that .zip on your HDD and you can bypass Rom Manager (and all the associated problems) altogether.
I have my phone rooted and unlocked. It's the AT&T Captivate but I'm using it on T-Mobile. I've had no problems so far with it.
I downloaded Clockwork's Rom Manager (v3.0.0.7) and tried to Flash ClockworkMod Recovery to begin experimenting with ROMs.
When I click on that it tells me "An error occurred while downloading your recovery."
I have over 4 gigs of memory left and I have 3 bars on 3g and WiFi going. No internet connection problems (i checked the net using market and using the browser, it works fine.)
What else could be causing the problems.
I'm just wanting to get a good stable rom going which ditches all the junk AT&T put on the phone.
Jonathan
lanternslight456 said:
I have my phone rooted and unlocked. It's the AT&T Captivate but I'm using it on T-Mobile. I've had no problems so far with it.
I downloaded Clockwork's Rom Manager (v3.0.0.7) and tried to Flash ClockworkMod Recovery to begin experimenting with ROMs.
When I click on that it tells me "An error occurred while downloading your recovery."
I have over 4 gigs of memory left and I have 3 bars on 3g and WiFi going. No internet connection problems (i checked the net using market and using the browser, it works fine.)
What else could be causing the problems.
I'm just wanting to get a good stable rom going which ditches all the junk AT&T put on the phone.
Jonathan
Click to expand...
Click to collapse
Read the above solution...
I Can't get the update.zip file to work. After I reinstall packages is says E:Can't open /sdcard/update.zip (No such file or derectory) Installation aborted. I've tried it probably 20 times today with no luck.
Thank You
Nothing like flashing to find out it wasn't working. Thanks for making my day go better.
Noobie Mistakes
Just like everyone in this forum I'm having the same problem, I followed your instructions posted, but every time I reinstall packages in recovery mode a whole list of new problems comes up..... see below.
---Install from sdcard---
Finding update package...
Opening update package....
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
PLZ Help.......
Thanks
i have been fight this same thing for 2 days. im going to try the update.zip he posted i hope it works
npe didnt work. still says error downloading
tat2messiah said:
npe didnt work. still says error downloading
Click to expand...
Click to collapse
if the update.zip is already on your /sdcard/ then there is no reason to try and download/flash clockwork recovery.....thats what the update.zip IS
thats what i thuoght but not true. even goin in normal recovery and selecting to install packages gets a error some about no such directory or something even though updat.zip is there even fix permissions gives a error
I'm having the exact same problem. After reading the development section I have decided to flash a custom rom from my stock rom. Installed "Rom manger" from market, then tried to run the "recovery" got the same error msg. Also uploaded the update.zip to my /sdcard the I got the below errors:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
tat2messiah said:
thats what i thuoght but not true. even goin in normal recovery and selecting to install packages gets a error some about no such directory or something even though updat.zip is there even fix permissions gives a error
Click to expand...
Click to collapse
Did you flash back to stock JF6 first not JI6?
try this cuz this is what i did and the update.zip worked just fine for me
1. one click back to stock jf6
2. master clear
3. root with galaxy s one click root
(after the root there should be an update.zip in your sdcard)
4. replace the update.zip in the root of your sd card with the one here posted which is the clockwork recovery one and if you want while u do that you can throw in the rom that you want to flash in there as well to kill 2 birds with one stone
(i will re post the update.zip for cwm just in case)
5. power off the phone and boot into stock recovery and hit reinstall packages two times
6. you should now be in clockwork mod recovery and can now flash the rom of your choice
this is what i did and everything went smoothly but this is just me if this helps someone else plz let me know if this works for you
p.s. i will make a video if needed just ask
Try This
After flashing back to stock do a master clear from Odin3
Put update.zip onto internal sd
Boot into recovery
Reinstall packages
After boot enable USB debugging and mock locations
Get Rom Manager from market
Start Rom Manager
Flash ClockworkMod Recovery
Flash away
jhernand1102 said:
Put this on your internal SD card along with your ROM of choice. Reboot in to recovery and install packages 2 times. The second time it will be in clockwork recovery and you can flash your ROM.
Click to expand...
Click to collapse
You guys are making it harder then necessary, the update zip I posted is the clockwork recovery MOD, just flash stock, reboot into recovery and reinstall packages 2 times and you will be in the green clockwork recovery then you can install zip from sd and choose your ROM you placed on your internal sd card. No need to root every again as long as you keep this update zip handy.
I too am having problems with Rom Manager. I just wanted to change modems. No go. So I used the power button to go into Recovery mode, picked the modem file, flashed it then told the menu to reboot system.
Sent from my Samsung Captivate with Perception 10.3, Firebird2 v0.8 #77 Kernel, Firmware 2.2.1, Modem T9000UGJL2 using XDA App
I can flash clockworks recovery through adb and can get in but I'm getting some errors:
E: Can't find misc
E: failed to find "cache" partition to mount at "/cache"
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
And a bunch few more which seem to repeat
I also tried to run the restore to stock from here but get an error right when I have to click to write the image.
When I just boot all I see is the unlocked lock and google. It used to boot into storage so I can mount it but not anymore. The only thing I have on the SD is the super user app, Netarchy kernel for 4G, CM7 latest stable for NS and thats it.
Need help
I can push something to the phone through the sdk but I don't know how to mount the sd card to do it.
ufff.... nevermind. I tried the factory restore one more time on another machine 32 bit and it works. It's restoring the image again. Will be locked again so I'll have to try again tomorrow. But the steps on rooting the NS4G don't really work well.
There is a bunch of stuff missing. Like the recovery gets overwritten each time. There are some links missing and dead.
Someone should fix that before we brick some phones.
OK, it restored but only gave me the sd card mount thing. I tried going back to fastboot and unlocked was still there. So I flashed recovery again and wanted to see if I can put the stock rom for 4G from here on it.
No go. I get:
assert failed: write_raw_image("/tmp/netharchy.img", "boot")
Installation aborted.
Help
ok, I'm not sure what ROM I have but I unplugged the cable and bam... sign in screen came in so I'm sighing in. Once I can get to the main menu I'll check versions and kernel but it looks like I have root. It's just that recover is not working well. I have 3.0.0.5. should I get a different one?
OK, I restored again because wifi didn't work. I think it was because I was trying to flash after the first restore and it wouldn't take. So now I checked and the lock when I boot showes up as unlocked but none of the root apps work so I don't think I have root. Not sure.
I also have to figure out what's up with that recovery. I know I need to rename the original so it doesn't flash it every time on boot but I think I need a new version. Anyone know which one is the latest and which one works on NS4G?
3005 is the problem. Use 3024. I don't know for sure but are you absolutely sure cm7 is compatible with the ns4g? Isn't a lot of stuff still not working? Isn't 4g still not working? If flashing the wrong rom is what happened here then this problem isn't going away. Many people are doing this and almost bricking their phones. I read one post recently that pointed to a doc that said the gsm and cdma are two separate versions of the same os. I thought I read something that said kernels might be cross compatible but roms aren't yet.
Here are the correct recovery files for the ns4g
I think I remember seeing recovery ***** about cache when I was nandroid for the first time. I think after that I chose factory reset and clear dalvik and some other cache and might have rebooted then came back and flashed cwm again and tried nandroid and it worked that time. This was the very last step for me after I had managed to get the su file to the root of the card, flashed it in cwm, rebooted and changed the filename of the script to check and reinstall stock recovery in system/etc. I forget the name but it was a .sh file. It's name was in the guides somewhere...
I think that's backwards. Roms might be compatible but kernels which these roms come with are not. So I believe that it I just flash netarchys kernel which now supports NS4G all should work ok.
Like I said, I'm back to stock and all looks like exactly like it was before ie. no root but the weird part is that fast boot menu says "unlocked". And I also get the lock which looks unlocked with the google sign during boot.
So how is that possible? Anyone?
When trying any app with root it tels me it has no access or it failed. Ie, su cmd says access denied.
BTW, why you attached two files? What is the difference between the two?
herbthehammer said:
3005 is the problem. Use 3024. I don't know for sure but are you absolutely sure cm7 is compatible with the ns4g? Isn't a lot of stuff still not working? Isn't 4g still not working? If flashing the wrong rom is what happened here then this problem isn't going away. Many people are doing this and almost bricking their phones. I read one post recently that pointed to a doc that said the gsm and cdma are two separate versions of the same os. I thought I read something that said kernels might be cross compatible but roms aren't yet.
Here are the correct recovery files for the ns4g
I think I remember seeing recovery ***** about cache when I was nandroid for the first time. I think after that I chose factory reset and clear dalvik and some other cache and might have rebooted then came back and flashed cwm again and tried nandroid and it worked that time. This was the very last step for me after I had managed to get the su file to the root of the card, flashed it in cwm, rebooted and changed the filename of the script to check and reinstall stock recovery in system/etc. I forget the name but it was a .sh file. It's name was in the guides somewhere...
Click to expand...
Click to collapse
Thanks for your help. I'm rooted and recovery is sticking ok. It was the old recovery. As soon as I flashed it all was good.
One is stock and the other is cwm that works with the ns4g. It wouldn't hurt to have the stock laying around. There might be a time when you need it.
Thanks for the stock recovery.
Sent from my Nexus S 4G using XDA App
Good Morning,
I have run into a problem with my HOX. After rooting and unlocking, I attempted to flash a custom ROM. Well, in my haste I flashed the new boot.img before transferring the new ROM to the phone. I have now formatted all info in all areas of the phone (wrong move I know). I can boot into fastboot, I can boot into CWM.
The problem lies in the mounting of the SDcard. I read through countless threads and everything I have tried up to this point has netted zero results. I have been flashing since the old Win Mobile days. I have a fairly strong understanding of ADB. I am not a developer, nor do claim to have the knowledge of one. I am reaching out and asking for help. I have CWM, version 5.8.3.1 touch. I also tried flashing back to the original boot.img and still no dice. Perhaps I have missed a step, I hope that is all. I did make a quick post in another thread, but it was made before I read allot of the other threads, so I am double posting. I am open to trying any advice that is offered.
Thank You all so much
Jason
zad2k2 said:
Good Morning,
I have run into a problem with my HOX. After rooting and unlocking, I attempted to flash a custom ROM. Well, in my haste I flashed the new boot.img before transferring the new ROM to the phone. I have now formatted all info in all areas of the phone (wrong move I know). I can boot into fastboot, I can boot into CWM.
The problem lies in the mounting of the SDcard. I read through countless threads and everything I have tried up to this point has netted zero results. I have been flashing since the old Win Mobile days. I have a fairly strong understanding of ADB. I am not a developer, nor do claim to have the knowledge of one. I am reaching out and asking for help. I have CWM, version 5.8.3.1 touch. I also tried flashing back to the original boot.img and still no dice. Perhaps I have missed a step, I hope that is all. I did make a quick post in another thread, but it was made before I read allot of the other threads, so I am double posting. I am open to trying any advice that is offered.
Thank You all so much
Jason
Click to expand...
Click to collapse
1. Wrong section, things like this should be in Q&A
2. Did you flash the CWM recovery with working ADB? If so you should be able to push the rom to your sdcard from recovery (someone correct me if I'm wrong about that).
RUU back to stock?
Sent from my HTC One X using XDA
Enter Fastboot re flash a recovery that has ADB working either teamwins or the CWM that has working ADB. Then push the rom to the sd card through ADB in recovery.
My apologies for posting in the wrong area...Thank you for the quick responses. I reflashed the current CWM, no luck. I flashed the recovery from Teamwin and things are looking up. I was able to look at the sdcard in recovery and I was able to push the ROM to the sdcard via ADB. However, when I try to install the zip, it gives the error again "can't mount sdcard" failed....hmmm Any other ideas or thoughts??
Thank You
Jason
I just wanted to say thank you to those who helped. All the time wasted, I never relocked before trying to flash RUU!!
made same mistake
...everything was too cool to be true,
rooted my HOX with
One Click HTC One X Root by kennethpenn (Win/Mac/Linux) (Recommended)
then
Auto Deodex/Debloat AT&T One X by kennethpenn
then let my HOX relax for a week, but past weekend after install CWM with
How To: Install CWM Recovery on HTC One X (AT&T)
Filed under Development, Guides by Kenneth Pennington
i was not sure about wether to install ROM
CleanROM DE 2.1 -★| Sense / AOSP Blend | Smooth! | Refreshing! |★-
or
CleanROM 2.4.5 SE -★| Landscape! | EQS! | APM! | Clean! |
i download both and then restart in recovery then i did
install zip from sdcard, but instead of do it over CleanROM 2.4.5, I did it with CleanROM DE 2.1
after reboot i realize that i screw it big time since CleanROM DE 2.1 comes without boot.img
so now when i start my HOX just reboot by itself after 5sec, the only thing i am able to do is start on recovery and when i tried to install all over again thru install zip from sdcard i just get
"E: Cant mount /sdcard/"
I ran AT&T RUU_Evita_UL_Cingular_US-1.83.502.exe and RUU 1.73 but it cant detect my HOX
help!!!
I found this for you. Give it a try. It was not my work just googled.
This is for people who have the following problem:
Cannot boot into ROM (e.g Stuck at the HTC Logo)
Boot Loop
Re-locked bootloader while having a non-working ROM
Cannot flash RUU because battery is below 30%
[edit] Try this first
The most common problem is being stuck at the HTC Logo after flashing a ROM, try clearing the fastboot cache with these steps:
Power off your phone and hold the power button + volume down
Choose fastboot from bootloader
Connect the phone to your computer
In command prompt window opened in your platform-tools folder type:
fastboot erase cache
Choose "Reboot" in fastboot menu
If this doesn't work, try the rest of the guide
http://forum.xda-developers.com/wik...very_-_what_to_do_in_the_event_of_a_bad_flash
Thanks for your help and time in advance. I am trying to flash a ROM to my At&T HTC One X. It is HBOOT 1.14 running ics 2.20. I am specifically trying to flash ViperXL and have failed about 3 times so far. I keep getting my phone stuck in a boot loop. It is no longer in a boot loop because I have flashed the factory ROM. My phone is rooted and I have TWRP as my recovery. I have some specific questions to ask:
1) What version of ViperXL should I use? I think I might be trying to flash the wrong version.
2) Do I leave the entire file zipped when I put it on my sd card or do I specifically extract the boot.img file and keep that file separate from the zip file?
3) If I have Flash Image GUI from the playstore should I use that to flash it? If so do I still follow step 2 above?
This is what I have been doing so far:
1) Downloading this file: ViperXL 3.2.1 - Android File Host (685MB) from http://forum.xda-developers.com/showthread.php?t=1868236
2) Using WInRar to extract its contents and move it to my sd card.
3) Using Flash Image GUI to select boot.img and then pressing flash.
4) Rebooting my phone and then wa-la, boot loop. I have actually been following a youtube video on how to do it but I'm not getting no luck.
If there is an easier way please inform me. I am a noob but love this stuff. Please be specific with instructions so I can enjoy an awesome custom ROM.
Again, thank you for your time and have a great day.
dirty2k9 said:
Thanks for your help and time in advance. I am trying to flash a ROM to my At&T HTC One X. It is HBOOT 1.14 running ics 2.20. I am specifically trying to flash ViperXL and have failed about 3 times so far. I keep getting my phone stuck in a boot loop. It is no longer in a boot loop because I have flashed the factory ROM. My phone is rooted and I have TWRP as my recovery. I have some specific questions to ask:
1) What version of ViperXL should I use? I think I might be trying to flash the wrong version.
2) Do I leave the entire file zipped when I put it on my sd card or do I specifically extract the boot.img file and keep that file separate from the zip file?
3) If I have Flash Image GUI from the playstore should I use that to flash it? If so do I still follow step 2 above?
This is what I have been doing so far:
1) Downloading this file: ViperXL 3.2.1 - Android File Host (685MB) from http://forum.xda-developers.com/showthread.php?t=1868236
2) Using WInRar to extract its contents and move it to my sd card.
3) Using Flash Image GUI to select boot.img and then pressing flash.
4) Rebooting my phone and then wa-la, boot loop. I have actually been following a youtube video on how to do it but I'm not getting no luck.
If there is an easier way please inform me. I am a noob but love this stuff. Please be specific with instructions so I can enjoy an awesome custom ROM.
Again, thank you for your time and have a great day.
Click to expand...
Click to collapse
wipe cache dalvik system and factory reset in recovery
fastboot flash boot boot.img or use the gui to flash the boot.img extracted from the viper rom
install the viper rom within recovery.
read more before you end up with a brick.
it says all this right in the second post of the viper thread
"Download the ViperXL 3.0.0 from the download section
Confirm the md5 checksum is correct on both files (it will be noted on the dl page)
Place the file somewhere on your phone storage
Reboot to TWRP recovery
Backup current ROM
Install ROM using twrp and select wipe during aroma install if coming from another base
If you have 1.14 hboot you will need to flash the boot.img in fastboot. You will need to extract this from the ROM zip. I have found the following tool useful: [TOOL] HTC Auto Boot.img Installer (One Click Tool)
Reboot and Enjoy"
All Flash Image GUI does is flash the boot.img, which is a small part of the overall ROM. You also need to have the entire ROM zip on your SD card. Boot into bootloader, then go into TWRP recovery. Once in TWRP, go to Wipe, do a factory reset (do not factory reset in bootloader, as it will corrupt your SD memory), wipe Dalvik, wipe cache. Then select Install, and navigate to the ROM zip. The ROM will begin to install. AROMA will then launch, giving you a variety of install options specific to ViperXL. Go through the AROMA options. Then when the ROM install is complete, TWRP will give you the option to reboot. Reboot and enjoy.
Do not extract rom lol. Flash it as is!
Sent from my One X using Tapatalk 2
flash successful
Thank you everyone for your replies. I got the ROM flashed and it's working great.
redpoint73 said:
(do not factory reset in bootloader, as it will corrupt your SD memory
Click to expand...
Click to collapse
Wow how did you figure this out? I now know why my sd corrupted on me once. I did click that once in my life. In fact it put me i have the "soft brick and gonna cry" category, complete with post in q&a.
There needs to be a sticky for things like this.. Little nuggets of knowledge.
The sticky should also contain the factory recovery.
And then the sticky should be mandatory before you are allowed to download roms, recoveries, etc. It would save headache for many.
wdkingery said:
Wow how did you figure this out? I now know why my sd corrupted on me once. I did click that once in my life. In fact it put me i have the "soft brick and gonna cry" category, complete with post in q&a.
There needs to be a sticky for things like this.. Little nuggets of knowledge.
The sticky should also contain the factory recovery.
And then the sticky should be mandatory before you are allowed to download roms, recoveries, etc. It would save headache for many.
Click to expand...
Click to collapse
Agreed. I too fall into the category of accidently bootloader factory resetting and almost dieing lol
it has been stated not to factory reset in bootloader, i have posted it probably almost 100 times. i'm glad this thread is finally over it was making me itch and twitch.
wdkingery said:
Wow how did you figure this out? I now know why my sd corrupted on me once.
Click to expand...
Click to collapse
Its a fairly common mistake, and as DvineLord stated, it been discussed quite a bit in various places.
Hey guys,
Having some problems with this ROM. I downloaded the ZIP, used Titanium backup to back it all up, and flashed the Rom with no problems at all...got through all the screens and whatnot, and upon launching for the first time it's stuck on the "Beats Audio" screen. Not really sure why or what happened. I'm coming from MIUI ROM and haven't had issues with flashing any other ROM before.
One thing I noticed is on the HD 7.3 first page there is a firmware update that you apparently need before you flash the ROM but all links are 404/not found.
Wondering if any of you pros can offer a hand?
-Cain
Cainsmoker said:
Hey guys,
Having some problems with this ROM. I downloaded the ZIP, used Titanium backup to back it all up, and flashed the Rom with no problems at all...got through all the screens and whatnot, and upon launching for the first time it's stuck on the "Beats Audio" screen. Not really sure why or what happened. I'm coming from MIUI ROM and haven't had issues with flashing any other ROM before.
One thing I noticed is on the HD 7.3 first page there is a firmware update that you apparently need before you flash the ROM but all links are 404/not found.
Wondering if any of you pros can offer a hand?
-Cain
Click to expand...
Click to collapse
post the output of this command
fastboot getvar all
don't show your imei and serial number
and what recovery do you have?
rzr86 said:
post the output of this command
fastboot getvar all
don't show your imei and serial number
and what recovery do you have?
Click to expand...
Click to collapse
In looking at my Hboot, it's old as sin....I'm using Revolutionary Hboot 1.17.1111 and Radio 10.14.9035.01_M
I run clockwork recovery mod v5.0.2.0 as well. This could be an issue causing the problem. I've been using the MIUI ROM for probably 2 years or so because I enjoyed it but I'm ready for a change. Apparently my phone doesn't agree. lol.
You want me to connect via USB and run the cmd prompt for the getvar command and let you know what it says?
Cainsmoker said:
In looking at my Hboot, it's old as sin....I'm using Revolutionary Hboot 1.17.1111 and Radio 10.14.9035.01_M
I run clockwork recovery mod v5.0.2.0 as well. This could be an issue causing the problem. I've been using the MIUI ROM for probably 2 years or so because I enjoyed it but I'm ready for a change. Apparently my phone doesn't agree. lol.
You want me to connect via USB and run the cmd prompt for the getvar command and let you know what it says?
Click to expand...
Click to collapse
there is no need to do it now
you gave me exactly what i need
you still have gb firmware that's why you can't boot ARHD 7.3(ics rom)
see this thread
http://forum.xda-developers.com/showthread.php?t=1459767
flash 3.33 universal
follow the instructions to the letter
and before flashing check md5 sums(important)
The speedy reply is much appreciated.
I'll go ahead and update the firmware and see where that lands me. I figured it could have been a problem from the get go but in the original thread for the HD 7.3 Rom the firmware link has been removed (likely since it was from 2011)
Thanks for the point in the right direction Rzr, and I'll let you know how it goes!
rzr86 said:
there is no need to do it now
you gave me exactly what i need
you still have gb firmware that's why you can't boot ARHD 7.3(ics rom)
see this thread
http://forum.xda-developers.com/showthread.php?t=1459767
flash 3.33 universal
follow the instructions to the letter
and before flashing check md5 sums(important)
Click to expand...
Click to collapse
Hmmm....the firmware update didn't work.
I can verify that I'm on the firmware 3.3, Hboot is 1.27.1100, Radio is 11.24A.3504.31_M.
Each time Hboot is run it asks if I want to start the update. If I select yes, I've got 9 on screen options that it runs through and tells me "Update complete. Press power to reboot" The only way to do anything at all is to take out the SD card so it does not try to load up the firmware zip
Pushing power reboots the phone on an endless boot loop. Regardless of what ROM is being used (I also downloaded cyanogenmod) I can not make it past the spash screen.
Could it be that I'm just flashing the ROM incorrectly? To my knowledge I've followed instructions for both and have backed up my phone and it's contents and done everything from a factory reset/wipe to wiping the dalvik cache, etc. I didn't have this many problems rooting my phone and putting on MIUI to begin with and have flashed ROMS before with no trouble....not really sure where I'm going wrong on this one.
Anyway, I'll await your reply.
Thank you!
-Cain
Update: awww frick. So now it looks like this will be more difficult....I hope you like a challenge. I can now no longer get into my phone. It appears that it's soft bricked. I have tried going to a clockwork mod recovery from my first MIUI in 2012, it goes through the entire process of factory resetting restoring the boot image, system and data information. It asks for a reboot which I do. It goes to the white HTC splash screen and the MIUI initializes and goes black immediately. There doesn't seem to be a way to get my phone connected to my computer to get into the SD card to troubleshoot from inside the phone. Hopefully one of you guys has the answer for me. Is there any way to get into it via bootloader usb?
Cainsmoker said:
Hmmm....the firmware update didn't work.
I can verify that I'm on the firmware 3.3, Hboot is 1.27.1100, Radio is 11.24A.3504.31_M.
Each time Hboot is run it asks if I want to start the update. If I select yes, I've got 9 on screen options that it runs through and tells me "Update complete. Press power to reboot" The only way to do anything at all is to take out the SD card so it does not try to load up the firmware zip
Pushing power reboots the phone on an endless boot loop. Regardless of what ROM is being used (I also downloaded cyanogenmod) I can not make it past the spash screen.
Could it be that I'm just flashing the ROM incorrectly? To my knowledge I've followed instructions for both and have backed up my phone and it's contents and done everything from a factory reset/wipe to wiping the dalvik cache, etc. I didn't have this many problems rooting my phone and putting on MIUI to begin with and have flashed ROMS before with no trouble....not really sure where I'm going wrong on this one.
Anyway, I'll await your reply.
Thank you!
-Cain
Update: awww frick. So now it looks like this will be more difficult....I hope you like a challenge. I can now no longer get into my phone. It appears that it's soft bricked. I have tried going to a clockwork mod recovery from my first MIUI in 2012, it goes through the entire process of factory resetting restoring the boot image, system and data information. It asks for a reboot which I do. It goes to the white HTC splash screen and the MIUI initializes and goes black immediately. There doesn't seem to be a way to get my phone connected to my computer to get into the SD card to troubleshoot from inside the phone. Hopefully one of you guys has the answer for me. Is there any way to get into it via bootloader usb?
Click to expand...
Click to collapse
remove the pg58img.zip from your sdcard so it won't scan and identify any pg58img.zip file
and don't restore your miui rom because probably is a gb one and now you have an ics firmware installed
just download an ics or jb rom
put it on your sdcard
full wipe from recovery
flash the rom
done
rzr86 said:
remove the pg58img.zip from your sdcard so it won't scan and identify any pg58img.zip file
and don't restore your miui rom because probably is a gb one and now you have an ics firmware installed
just download an ics or jb rom
put it on your sdcard
full wipe from recovery
flash the rom
done
Click to expand...
Click to collapse
With the phone being in a boot loop I can't get it detected by my computer to remove/add anything from the SD card. I do have the HD 7.3 ROM on and the Gapps that's required but it never makes it past the "beats audio" splash screen. I have no idea what's going on with it but will try any suggestions you've got up your sleeve.
Ahhhhh....I've gotten a fix for this!
I was unable to do anything because of the update zip which wanted me to update every time bootloader was initiated. By keeping my case off I removed my SD card to be able to boot in recovery and then put the SD card back in to load the HD 7.3 zip from the card. This seemed to take care of the problem.
Thanks for the help Rzr