Related
Hi! first of all i dont know if this is the right forum to right this question. Dont know if it should be in the Dream forum but i have a magic, so i write it in the Magic forum.
My problem is that i for some reason can't flash Cyanogen's ROMs.
I have had Cyanogen's 4.0.3 ROM on my magic, but a couple of days ago i decided to upgrade it and try the Experimentel version 4.1.8.
I First tried to use the CM Updater, but for some reason it did not work, it would not flash the ROM.
So i downloaded the ROM manually and did as i always do: boot in recovery, wipe, apply and then reboot. Everything went fine until the reboot. After reboot the phone gets stuck at the HTC Magic screen, and nothing happens, only thing i can do is to remove the battery and the try and boot the phone again, and then it just get stuck at the HTC Magic screen again.
I have no problem flashing a MyHero 1.1.1. It works perfect.
I have also tried with a number of the other Cyanogen ROM versions, even tried 3.9.1 (cant remember the exact version number) have also tried the 4.0.3 version that did work before all this happened, but still no luck.
I have tried installing the Cyanogen Recovery image and the flash the Cyanogen ROM, but it still gets stuck at the HTC Magic screen.
I have tried reformating my sdcard and then flash, but no luck.
Can it be that i need a new SPL, Radio or something?
My current Fastboot screen looks like this:
SAPPHIRE PVT 32A ENG S-OFF H
HBOOT-1.33.2010 (SAPP10000)
CPLD-12
RADIO-3.22.20.17
If anyone know what i need to do to get the Cyanogen ROM on my magic, i would really like to know.
Any suggestions would be much appreciated. Hope to here from you.
Per
Cyanogen is built for 32B (You seem to have a 32A) so you need to flash a 32A-kernel on top of the cyanogen ROM.
Check this thread:
http://forum.xda-developers.com/showthread.php?t=544854
do what psyduck says, AND wipe before you do it. going from a stable to an experimental build requires a wipe or you will have a lot of issues.
Okay, thx for the answer both of you.
So i just "flash" the kernel first, like if it was an normal update? e.g. rename it update.zip, push it to sdcard, wipe, flash and then reboot. And then flash the ROM like i would normal do?
But what if I would like to flash a stable build, e.g. 4.0.4 what do i do then? i can't find a kernel for that in the link. Or can i just use 1 of the kernels in that link?
Per
Cyanogens ROM first! Otherwise the kernel will be overwritten with the one included in the cyanogen ROM.
Don't know why the old kernels were removed? Better to ask in the linked thread.
Decided to try Donut on my MT3G and had the same issue, I did a wipe after I noticed it didn't get past the first splash screen and that fixed it.
Thx for the help all of you, im now on the Cyanogen ROM, finally. its good to be back
But have 1 last question: When i deside to upgrade the current Cyanogen ROM im on now, i would also need to flash a new kernel right?
the thread listed by PsyDuck has it.
first page, look at the file called "Base Kernel v4.1.9.2"
link for it is right below.
Use amonRA's Recovery so you dont have to rename the updates.
download CM's latest 4.1.9.2 ROM and the basekernal. put both in root directory of SD.
boot into recovery, nandroid backup, wipe, Flash ROM then Flash update.
reboot. should work fine.
I did so, and everything works now. really nice, finally
32a looping after flashing CyanogenMod 4.1.99
I have a 32a and I used to run CM 4.0.4 perfectly fine.
I've been trying to flash to later CM roms but until now still not able to do so.
Every steps in http://forum.xda-developers.com/showthread.php?t=568032 were followed carefully. Here is what I do:
1. Copy the HTC ADP 1.6 DRC83 into the SD card
2. Copy CyanogenMod 4.1.99 into the SD card
3. Copy the Kernel Port file into the SD card
4. Wipe
5. Flash HTC ADP 1.6 DRC83
6. Flash CyanogenMod 4.1.99
7. Flash the Kernel Port file
8. Reboot
The phone reboots into the first screen (HTC Magic) and after a while, reboot again and still stuck at the same screen.
Eventually I have to take out the battery.
I don't partition my SD card and it has been working fine with the other roms such as RA 1.6.1H, MyHero 1.1.2 etc, so I doubt that could be the problem.
I tried to plug the USB and "adb lolcat" but my WinXP says USB device not recognized.
The strange thing is it seems everyone's 32A doesn't have this problem, except me. I've reported this problem before but wasn't able to get a solution.
Is there anyway to troubleshoot to find out what goes wrong?
Thanks in advance.
thats actually weird..try restoring nandroid backup..
i followed the same instructions with the exception of not wiping..try that see if it helps.
Thanks for replying. I didn't manage to flash successfully before that's why not able to do a nandroid backup ... unless of course if someone is willing to share the backup with me.
str4vag said:
thats actually weird..try restoring nandroid backup..
i followed the same instructions with the exception of not wiping..try that see if it helps.
Click to expand...
Click to collapse
Same Boat
I have the same problem when flashing CM 4.1.99[9] ROMS. It goes into the endless boot/reboot mode.
I used to have the problem with the HoFo ROM as well (between versions 2.0.5 - 2.0.9). HoFo started working after that. I don't know what changed.
Code:
SAPPHIRE PVT 32A ENG S-OFF H
HBOOT-1.33.2005 (SAPP10000)
RADIO-3.22.20.17
Apr 20 2009, 15:30:43
ranger79 said:
I have a 32a and I used to run CM 4.0.4 perfectly fine.
I've been trying to flash to later CM roms but until now still not able to do so.
Every steps in http://forum.xda-developers.com/showthread.php?t=568032 were followed carefully. Here is what I do:
1. Copy the HTC ADP 1.6 DRC83 into the SD card
2. Copy CyanogenMod 4.1.99 into the SD card
3. Copy the Kernel Port file into the SD card
4. Wipe
5. Flash HTC ADP 1.6 DRC83
6. Flash CyanogenMod 4.1.99
7. Flash the Kernel Port file
8. Reboot
The phone reboots into the first screen (HTC Magic) and after a while, reboot again and still stuck at the same screen.
Eventually I have to take out the battery.
I don't partition my SD card and it has been working fine with the other roms such as RA 1.6.1H, MyHero 1.1.2 etc, so I doubt that could be the problem.
I tried to plug the USB and "adb lolcat" but my WinXP says USB device not recognized.
The strange thing is it seems everyone's 32A doesn't have this problem, except me. I've reported this problem before but wasn't able to get a solution.
Is there anyway to troubleshoot to find out what goes wrong?
Thanks in advance.
Click to expand...
Click to collapse
Hi Guys,
Got a bit of a problem, got a sensation xe and tonight i did the s-off and rooted then tried to put a new rom on but it just bootlooped so went to recovery and did a restore and all was ok,
rooted it again and put the PG58IMG back on did the update then it just went as far as the beats logo and looped.
i tried to get into recovery but it wouldnt go and just kept saying no image or wrong image every time i tried, i read some similar threads to this and so eventually i took out the sd card and then got back into recovery but doing a restore didnt work,
took the sd card out and using the pc deleted the PG58IMG which i thought might be causing the problem, tried recovery and it started again but on rebooting it just bootloops again, can anybody help me?
Need to know exactly what you did at the time of flashing? What steps have you done and what ROM?
Sent from my HTC Sensation 4G XE with Beats Audio using xda premium
start
Ok i followed the guide on here....http://forum.xda-developers.com/showthread.php?t=1192300 got s-off and root.
tried to super cid and couldnt get it done anyway got s-off and rooted put the PG58IMG in root updated and then took it out of root then tried to put the darkforest sensation xe ics 3.2.1 rom on, got bootloop then went to recovery and did a restore, everything was then ok.
Checked the phone and it was unrooted so did another complete backup looked to see what might be wrong and i thought i had put the wrong PG58IMG on so i went and put what i thought was the right PG58IMG on updated it and then rebooted and it went into a bootloop.
Tried to do a recovery but would not allow it it just kept running through "no image" then "wrong image" then "no image" and so on.
Tried to get into recovery but wouldnt move down so after reading a similar thread i pulled the sim and got into recovery selected the first of the two restore options and it was restoring from cwd rebooted and it started on a bootloop again going to the beats logo this time.
Thank for your help btw.
Forgot to add it was the revolution system. Thanks for any help!
highlander1v said:
Ok i followed the guide on here....http://forum.xda-developers.com/showthread.php?t=1192300 got s-off and root.
tried to super cid and couldnt get it done anyway got s-off and rooted put the PG58IMG in root updated and then took it out of root then tried to put the darkforest sensation xe ics 3.2.1 rom on, got bootloop then went to recovery and did a restore, everything was then ok.
Click to expand...
Click to collapse
To install ICS roms you need an additional step. Before installing the rom you should supercid and install the new ICS firmware. You can find the link on the second line of darkforest sensation xe ics 3.2.1.
If don't want to supercid follow the instruction here and download the firmware package for your CID (3.24, revolutionary or normal).
Install the new firmware.
Remove the PG58IMG from your sd card
Install the ICS rom.
highlander1v said:
Checked the phone and it was unrooted so did another complete backup looked to see what might be wrong and i thought i had put the wrong PG58IMG
Click to expand...
Click to collapse
You don't root with PG58IMG, that's for the custom recovery. Have you installed the su-2.3.6.3-ef-signed.zip file from the guide?
Hi, yes i have the su-2.3.6.3-ef-signed.zip installed and have removed the PG58IMG from the sd card, but as i say the thing is just boot looping after the beats logo and i would like to find out the next steps to get things back to normal?
Thanks grandelama can you tell me my next move to get back to normal and out of bootloop?
What ROM do you currently have on your phone that doesn't boot? Stock or Darkforest or something else? I'm not sure what rom you restored from the backup... If you restored the Darkforest rom and didn't install the correct firmware as Grandelama said, it will get stuck in a bootloop. If you did install the firmware, try reinstalling the Darkforest rom.
Otherwise, to get your phone working, just do a full wipe in recovery and try to install any gingerbread based rom, for example Android Revolution HD 3.6.13 from here. It should install fine and get your phone to a working condition. Then you can try to get superCID and install the firmware if you want to use ICS roms.
If you have Clockworkmod working and are going to install custom roms anyway, you don't need to worry about installing the su-2.3.6.3-ef-signed.zip file, since all those custom roms are already rooted.
If you have completed without errors the points 1, 2 and 3 of the guide, and you can use Clockworkmod recovery you are now ready to install any NON ICS rom like Android Revolution HD 3.6.13.
Run the superwipe script in Android revolution HD thread, install the 3.6.13 rom and you should boot up allright
If you want to use an ICS rom your missing a step (new firmware) and you need to follow the instructions I gave you in the last post.
Ok thanks guys, i'll try that and let you know how i get on.
Dr Madman i tried the dark forest rom but it wouldnt load so went into recovery and went back to the original stock gingerbread then thinking i had put the wrong 58img changed it and updated but it just bootloaded so did a cwm restore and it still bootloads.
I'm still not sure just what to do next because i'm afraid i might make things worse.
I went into recovery then to backup and restore and then restore and this time restored the second image that was there in CWM it went thru all the recovery, asked to reboot and when i did it still keeps bootlooping.
Why is CWM not getting me back to stock?
Grandelama i'm certain i did what you suggested in your first post but got bootloop after that and CWM got me back but it hasnt worked this time!
Dr Madman,, i could do a wipedata/factory rest wipe cache partition and install Android Revolution HD 3.6.13 because its on the sd card but to be honest i'm just to frightened to at the moment, basically i wanted to go to restore and have it back as stock but it wont! and now i'm not sure which way to go?
highlander1v said:
Grandelama i'm certain i did what you suggested in your first post but got bootloop after that and CWM got me back but it hasnt worked this time!
Click to expand...
Click to collapse
If you did what I suggested you have installed the 3.24 firmware for ICS roms, am I right?
Can you tell which exact version did you install? Where did you download it from? The one from the Kohr-Ah thread...mike1986's version or what?
If you installed mike1986's version without Supercid first you will bootloop with both ICS and Gingerbread roms.
yes
Yes i am certain i did but not sure which one, heads all over the place with this, anyway i will check and get back to you.
Thanks.
Grandelama i think? this is the one i used......DOWNLOAD 3.24 Revolutionary: http://goo.gl/82UpA
MD5: 74e67609f67c3ad6ab94cdb89f19f2fa
Is there a way to find out for sure for you?
Thanks
Do you still have on your pc the zip package you used? If that's the case you can find the md5 of your file and with that you can know which firmware package you installed.
Maybe it's a stupid question, but can you tell me which is exactly your CID? What is the output you get with "fastboot getvar cid"? Are 100% you sure you installed exactly the firmware package for your CID?
Grandelama, firstly thanks for your help, i have a hero that i have rooted and had at least a dozen different roms on from 1.6 thru to 2.3 never had a problem but its been a while and this xe is it seems more complicated, either that or my brains going (more likely) anyway the CID is HTC--001 and the MID is pg5813001.
I will look and see what i have and let you know.
The phone i take it is not yet bricked??? so i really dont want to do anything to screw that up(unless its too late?)
I ran restore and got back to normal, should have left it at that but didnt and cant understand why it wont work this time, i thought thats what it was for.
Anyway i will get back to you with what info i have and thanks again
no, not now 100 sure!
Htc driver 3.0.0.007
v4.3.233.pub.odex.zip
revolutionary -0.4pre4
su-2.3.63-efgh-
darkforest sensation xe ics 3.2.1
PG58IMG
Android revolution hd sensation 3.6.13
This is what else i have plus i have a xe backup folder on the pc if this is of any use ?
is this what you are asking for?
http://forum.xda-developers.com/attachment.php?attachmentid=874000&stc=1&d=1327610186
highlander1v said:
Grandelama, firstly thanks for your help, i have a hero that i have rooted and had at least a dozen different roms on from 1.6 thru to 2.3 never had a problem but its been a while and this xe is it seems more complicated, either that or my brains going (more likely) anyway the CID is HTC--001 and the MID is pg5813001.
I will look and see what i have and let you know.
The phone i take it is not yet bricked??? so i really dont want to do anything to screw that up(unless its too late?)
I ran restore and got back to normal, should have left it at that but didnt and cant understand why it wont work this time, i thought thats what it was for.
Anyway i will get back to you with what info i have and thanks again
Click to expand...
Click to collapse
Hi,
i had the exact same problem and yesterday i solved it. I tried to flash the latest InsertCoin ICS ROM and failed to first install the new Firmware. When i realized this, i did it but forgot to check the CID, wich was not in the FW-zip.. so.. my phone just bootlooped, came to the splashscreen the rebooted. Your phone is not bricked.
This is what i did to solve it:
First i got Super-CID wich you can read about in this thread: [Guide] to Installing S-off, Unlocking, ClockWork, Root, SuperCID & S-on .. it took me about 30 sec to get Super-CID, its very easy if you just read the text.
Then i flashed the new Firmware (3.24.401.1 RUU) that you can find here [DEV] HTC Sensation & HTC Sensation XE firmware | Partitions Info | [22.01.2012]
After that i just flashed the ROM like before and voila, it worked.
Hope it helped some.
Alright I'm sorry if this has already happened to someone and they've posted about it. I couldn't find any threads about this, which is not surprising to me as this was a stupid mistake that most likely users here wouldn't make.
I have an HTC Sensation.
I wanted to run the ARHD XE rom 6.5.1.
Completed S-off, installed CWM, and successfully rooted device.
I then downloaded the following zip files and put them onto the sd card to be flashed.
PG58IMG.zip(firmware package)
SuperWipe
The rom itself
I also installed 4EXT.
I also completed the process where you write in the command line with the phone hooked up. the phone reboots a bunch of times during the process, I don't remember the name of the step. but I completed it successfully. I remember the step "allows you to flash any rom"
after I had the rom downloaded(took the longest to download and was the last thing I transferred to the sd card.)
I unplugged the phone then booted into bootloader, where I had planned to continue into CWM recovery to flash the zips.
but once I entered the white screened boot loader, the phone instantly read through the sd card and found the firmware update, began checking it, I briefly saw( and see) a message or two saying that no image or file was found, then it loads up a list like this:
Parsing....[sd zip]
1.SBL1
2.SBL2
3.SBL3
4.TRUST_ZONE
5.ADSP
6.BOOTLOADER
7.RPM
8.RADIO_V2
And it says " Do you want to start update?"
The first time this happened I said no, and the phone just rebooted.
So I turned it off and went back into the bootloader and it asked me the same question and it didn't(doesn't) let me do anything else so I figured(being dumb and not checking online first) that I was supposed to let it update and said "yes". It then went(and goes) through the process of updating the firmware(I'm guessing) and after it gets done, the only option I have is to reboot the phone, and after this all happened, the phone is now locked in a boot loop, "htc" then "htc quietly brilliant" then it starts over.
after reading I now know that your supposed to enter the command line again when your going to update the firmware. I'm so screwed if I bricked my phone.
Please help me out anyone if there's anyway I fix or save my phone.
Thank you in advance.
UPDATE: I took out the sd card, then booted into bootloader, then after I got into 4ext, I put the sd card back in, I am now doing a restore.
UPDATE 2: system restore didn't work, and I think it's because I installed 4ext after I made my backup, i made the backup with CWM. :/
two post down from yous is my post {fix} for 3.24-3.32 firm bootloopsgive it a read youll be good to go
Your system restore should work regardless when you installed 4EXT. It just acts as a unique touch interface if you didn't have it before? If you installed new firmware, then it might be because you need to flash the old firmware from your backup
Mate, you said yourself what the problem was..
Place PG58IMG.zip on sd, boot into recovery, let it update, after update put SD card in computer and delete the PG58IMG.zip. FIXXED!!!
Remove your sdcard, boot into hboot, keep the phone on, insert the sdcard, choose recovery and continue
next rename or delete the PG58IMG.zip
I have a rooted sensation, it had android revolution hd's last version (with gingerbread)... now yesterday I tried installing the latest version of it Android revolution HD 7.2 by mike 1986 ... every time i finish installation and reboot, it just freezes onto the start-up screen where it says beats audio , I then remove the battery
someone suggested flashing 3.33 firmware and ARHD rom .
. Now will I have to install ARHD7.2 again after flashing firmware ?!
.What version of the firmware is suitable for my phone sensation T-mobile (shows sensation XE in the settings because of ARHD)
jay.illicit said:
I have a rooted sensation, it had android revolution hd's last version (with gingerbread)... now yesterday I tried installing the latest version of it Android revolution HD 7.2 by mike 1986 ... every time i finish installation and reboot, it just freezes onto the start-up screen where it says beats audio , I then remove the battery
someone suggested flashing 3.33 firmware and ARHD rom .
. Now will I have to install ARHD7.2 again after flashing firmware ?!
.What version of the firmware is suitable for my phone sensation T-mobile (shows sensation XE in the settings because of ARHD)
Click to expand...
Click to collapse
yeap you have to upgrade your fw version first
flash 3.33fw as suggested
after that flash again the rom
don't worry about the info(sensation xe)
the info are taken from build.prop file which is located in system folder of the internal storage
this file can be edited which means you can change the name of the device with any file manager with root permissions
but there is no need to do anything
just upgrade the fw version and then flash the rom
rzr86 said:
yeap you have to upgrade your fw version first
flash 3.33fw as suggested
after that flash again the rom
don't worry about the info(sensation xe)
the info are taken from build.prop file which is located in system folder of the internal storage
this file can be edited which means you can change the name of the device with any file manager with root permissions
but there is no need to do anything
just upgrade the fw version and then flash the rom
Click to expand...
Click to collapse
I've flashed the firmware and the rom both but the phone just got stuck at the start-up screen where it says beats audio! :crying:
jay.illicit said:
I've flashed the firmware and the rom both but the phone just got stuck at the start-up screen where it says beats audio! :crying:
Click to expand...
Click to collapse
i saw your posts in the other thread
you are still in gb firmware
the installation was unsuccessfull
do as malybru 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
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
I have a Rogers Infuse 4G (i997r) and I have been trying to upgrade it to kitkat by using a unofficial Cyanogenmod rom. More recently have been trying to use Carbon rom to update it. I have been running into problem after problem, error after error and I have finally decided to post something on XDA in hopes that someone with more experience can help me out. More information about the errors and what I have done to the phone below.
About a year ago I got this Rogers infuse 4G from a friend. I messed around with it for a bit but what I really wanted to do with it was install a custom rom and update it to a more recent version of Android (It started out on gingerbread (2.3)).
I had a real hard time getting modified recovery 3e because there was not original recovery file in system>bin to replace.
I forget most of what happened but it ended with me using a application to convert the cwm recovery zip to a md5 because I couldn't get modified 3e to work.
I tried using odin to flash the files I made but odin got stuck (or was just taking forever) and I unplugged my Infuse.
The infuse was bricked and would only show "firmware upgrade encountered an issue please select recovery mode in kies and try again". The phone would'nt enter recovery or download mode. It was recognized by odin but seemed as if it was not responding.
About 3 days ago I finally decided to try to unbrick the phone again (I don't know why just felt like it) and I found GTG ultimate unbrick with a pit file. I tried uploading this using odin and the phone responded and downloaded the files.
The phone showed a AT&T splash screen and then the Samsung logo. It hanged at the Samsung logo for about 3 minutes then would turn off reboot, show the AT&T splash screen then the hang at the Samsung logo for 3 minutes again.
I decided that I didn't actually need to install working android because I just needed CWM Recovery and found a CWM Recovery that was flashable with odin.
Now that the phone would actually show a splash screen I could access download mode and the stock 3E recovery.
I went to download mode and flashed CWM Recovery 6 - Voodoo Lagfix with odin
In the CWM Recovery I clicked install update.zip
The phone said installing and when it finished it rebooted.
It showed the AT&T logo and then the Samsung screen then it started talking (which btw scared the **** out of me) and it said installing voodoo lagfix, estimated time remaining 2 minutes
After it was done installing it rebooted and I had the same problem as before. It would show the AT&T logo then hang at the Samsung screen for 3 minutes.
I reflashed the GTG unbrick with odin then I reflashed the CWM Recovery and I was back into the recovery. (It wouldn't just let me boot into it I had to reflash it which was weird)
This time instead of clicking install update.zip I installed the Cyanogenmod-11-infuse-4g-unofficial-2014(some build number).zip
I got (status 7) installation aborted.
when the phone rebooted it showed a cyanogen mod loading screen and I got really excited
after the loading screen it went straight to proper CWM Recovery then it instantly crashed with a little fallen over Android and a red triangle over it.
It kept boot looping like this so I asked for the unbrick files for a Rogers Infuse 4G and installed those.
Once I installed the Rogers Infuse 4G Rom I set it up but I ran into the same problem I had last time.
I can't install the modified 3E recovery because the recovery file is not system>bin. CWM Recovery also fails to install even though it says it has installed.
It turns out the recovery file is on the root of my phone not /system/bin
Im not really sure what to do and guidance would be appreciated.
It's because the CWM is not only device specific, but carrier specific (at least for the Infuse).
Flash the following file (extracted) with Odin. It will talk to you as well after reboot, but it will give you CWM red which you can use to move on to custom ROMs:
https://www.dropbox.com/s/t0kc92124jat6yt/CWM Infused Kernel.zip?dl=0
Be sure to disable Voodoo Lagfix before installing any ROM's, especially if shortcut'ing directly to CarbonROM (versus installing CM9, then CM10.1 and finally a KitKat ROM).
Good luck, let me know if you have any questions.
Thanks so much for both the Rogers stock rom and the help today. I left out one crucial piece of information earlier by mistake. I tried installing both cyanogenmod and carbon rom earlier using the voodoo fix version of CWM Recovery and I got another status 7 installation aborted. I deleted the assert part of the update-script. My problem now is I get status 6 installation aborted and I haven't been able to find a quick fix for it. I just tried again using the red version of CWM Recovery you gave me and I still get the same error
Thanks so much for both the Rogers stock rom and the help today. I left out one crucial piece of information earlier by mistake. I tried installing both cyanogenmod and carbon rom earlier using the voodoo fix version of CWM Recovery and I got another status 7 installation aborted. I deleted the assert part of the update-script. My problem now is I get status 6 installation aborted and I haven't been able to find a quick fix for it. I just tried again using the red version of CWM Recovery you gave me and I still get the same error. Accidentally Double Posted... Im a noob. If someone could delete this repost it would be appereciated
OnfireNFS said:
Thanks so much for both the Rogers stock rom and the help today. I left out one crucial piece of information earlier by mistake. I tried installing both cyanogenmod and carbon rom earlier using the voodoo fix version of CWM Recovery and I got another status 7 installation aborted. I deleted the assert part of the update-script. My problem now is I get status 6 installation aborted and I haven't been able to find a quick fix for it. I just tried again using the red version of CWM Recovery you gave me and I still get the same error
Click to expand...
Click to collapse
Just to be clear. With the original ROM file, did you try installing the ROM with this CWM and Voodoo Lagfix disabled? That is go into CWM's options menu, and disable there?
Just trying to pick the low hanging fruit, unfortunately I don't know where to go from there (as this is my only idea now, besides re-downloading the ROM).
I have no problem reflashing the roms are anything. I have a iPhone 5S (hoping to get a S5 or S6 in 2015 once my contract expires ) so I have no important files or anything on this phone. (In fact I just reflashed that rogers rom yesterday from a blank slate) I noticed you have (had?) a Infuse 4G running Carbon 4.4.4 and honestly that's all I want to get to. If you want me to reflash roms or files I have no problem doing so. I just would like my infuse to run Carbon 4.4.4.
OnfireNFS said:
I have no problem reflashing the roms are anything. I have a iPhone 5S (hoping to get a S5 or S6 in 2015 once my contract expires ) so I have no important files or anything on this phone. (In fact I just reflashed that rogers rom yesterday from a blank slate) I noticed you have (had?) a Infuse 4G running Carbon 4.4.4 and honestly that's all I want to get to. If you want me to reflash roms or files I have no problem doing so. I just would like my infuse to run Carbon 4.4.4.
Click to expand...
Click to collapse
It used to be that in order to get from Gingerbread to say, Jellybean, you needed to install the Ice Cream Sandwich ROM (CM9) first. This gives you a relatively new CWM in order to do your bidding. But you man need to install a Jellybean ROM (I suggest CM10.1) in order to get a CWM that will like the installation of KitKat.
So Stock (Infused CWM) -> CM9 -> CM10.1 -> CarbonROM 4.4.4
Of course, I did say used to. Apparently if you disable Voodoo lagfix in CWM you can go straight to CarbonROM. I never tried it, but it is worth a shot (avoids having to go on a scavenger hunt).
But if you already tried it with no success, now you know the classical way.
Thanks a lot. By upgrading to cm9 then cm10 then finally Carbon Rom I was able to get the phone to kitkat!
Cheers