[Q] ICS 4.0.4 BCM RC3.1U0 black screen after flash - Desire Q&A, Help & Troubleshooting

hi
Coming from MildWild CM 3.9, I just tried to flash BCM ICS RC3.1U0 full rom.
Aroma installer asked to switch hboot to data++. So I did (before I had cm7r2).
Then flashing worked succesfully!
After rebooting from 4EXT to try out the newly installed rom I only got Black Screen and no bootup animation. Waited for more than 10minutes but nothing happened.
Has anyone else experienced these issues? Any Ideas why and how to solve?
thanks
also did full wipe and cleared dalvik

Sometimes we need to wait longer after reflashing...
Sent from my HTC Desire using xda premium

i got the same problem, so i tried to flash RC3.0update0 and it worked. after flashing RC3.0U0, i updated to RC3.1 & everything works fine

ok I'll try
thanks in advance

Download the rom again and try to re-flash; maybe you have a corrupted rom file!

Ryther said:
Download the rom again and try to re-flash; maybe you have a corrupted rom file!
Click to expand...
Click to collapse
I dont think so, because aroma says everything successfull and there were no errors.
maybe the issue is due to changing hboot. I flashed the pb99img.zip via bootloader. this was also succesful because after that bootloader says hboot data++ (instead of cm7r2 previously). is this enough or do i have to do something else

Have you tried to do a full wipe again using "wipe | format -> format all partitions" and do a fresh install?
Wich option did you set for m2sd?

boerxt said:
maybe the issue is due to changing hboot. I flashed the pb99img.zip via bootloader. this was also succesful because after that bootloader says hboot data++ (instead of cm7r2 previously). is this enough or do i have to do something else
Click to expand...
Click to collapse
i switched from cm7r2 hboot to data++, just like you and faced the same problem. but flashing a previous rom-version fixed it.

Ryther said:
Have you tried to do a full wipe again using "wipe | format -> format all partitions" and do a fresh install?
Wich option did you set for m2sd?
Click to expand...
Click to collapse
I wiped before hboot flash. cant remember if I also did after, but I choose the additional erase and format settings in aroma.
I used all the default settings regarding m2sd, launcher etc (didnt choose costumize in aroma)

Can you try to flash the rom using the custom method?
I've installed latest BCM few hours ago with:
Apex
Stock Browser
Play Store
Mount2SD
In M2SD config: Apps, Cache, Ext4, 768
Try this settings and report.
Edit: Use the Readahead for your SD, obiously

Related

[Q] Help.... phone stuck in saying "CyanogenMod 7"...

HI... i updated my phone with cyanogen 7 rc2, but after it booted up it's stuck in the animation that says cyanogen mod 7 , and the blue android sign... in comes than goes, again it comes... about 20 min stuck... what to do???
It sounds like you need to go into recovery mode and delete all your caches. If you are using ClockworkMod recovery do the following (make sure you are backed up first):
Delete all user data and info (under wipe data/ factory reset),
Wipe cache (under wipe cache partition),
Wipe Dalvik Cache (under advanced).
Then once you've done that try installing and running the ROM again.
i done that one time... for info im using AmonRA.. i cleaned all the cache and everything also... and installed again... nothing happens... fortunately i restored my nand backup and booted my phone with the OTA again... waiting for some answer.... do u think that installing stable version can fix this?
Sounds like a bad flash. I had rc2 running for a month or so with no issues. I've had times when the rom just doesn't install properly ans reflashing fixes it.
Download the zip again, if possible check md5 to make sure it's all good, make sure you have the desire/bravo GSM version, clear everything and flash just the rom and nothing else. If it boots, then go back and flash your gapps and whatever else you want.
Sent from my HTC Desire using XDA App
thx for replying.. as i was waiting for your reply, i download the cm 6 that is a stable version and checked, it has the same problem too.. i also downloaded GingerVillain 1.6 and it had the same problem too. do u think the problem might be that my phone is "s-on"? and how should i know if my phone is s-on or s-off... when i was rooting my phone with unrevoked, i checked the option that says disable security, but i'm not sure if it's disabled.... because i can't install un-signed zip packages....
any reply?
That definitely sounds odd. Its definitely not an issue with S-ON/OFF, nothing you've done here requires S-OFF to work properly.
Lets just make sure you're following all the steps.
In amonra, you've done your nandroid backup, so no need to do it again. There's no point having a non working backup
Go to wipe and wipe data/factory reset
Wipe davlik cache
Wipe sd-ext (shouldn't need to do this one as you don't have apps2sd yet, but better to be safe)
Now you flash your update.zip, then reboot and you should be fine. The only other thing I can perhaps suggest if every rom you flash sticks at boot is to perhaps try clockwork recovery instead of amonra. Apart from that we might have to wait for folks more knowledgeable than myself cause I'm all out of ideas.
thx for reply.... in meanwhile , i s-off ed my phone and it has the same problem too... i have problem with all cm and gingervillain roms.. but i don't have any problem with leedriod... one more question that maybe the problem is that i have android 2.2 installed, but gingervillain and cm use android 2.3 ... this maybe the problem.... and that's why leedroid works right, because it uses android 2.2.... i'm going to check OxyGen roms... i will post the result here...
i also faced same problem CM7 .. i tried CM6 and it went on fine..
heyyy... right after i posted the reply , i went to recovery and wiped anything, then installed gingervillain 1.6, and everything's fine now... it booted up and now im setting it up.... im going to check the cm 7 too.
i tried cm7 rc2 ... and it was fine and now im using it... here's a how to for solving the problem...:
1.S-OFF your device with AlphaRev : http://forum.xda-developers.com/showthread.php?t=805811
2.Install the AlphaRev Recovery(S-OFF Image will do it automatically).
3.Go to recovery and install the rom...
4.Boot up and it should not go to system and it should stay in loop as the problem was..
5.Now you should reboot your device into recovery... there are two ways to do this... either take the battery off and put it on, then boot to bootloader by pressing the volume down and the power key and select recovery , or the second way connect it to your computer and start adb and run this command:
adb reboot recovery
6.In AlphaRev recovery first wipe the cache partition , wipe user data, and factory reset...
7.then install the rom (either cm7 or gingervillain)...
8. boot up , and now you have the system running...
This solved my problem... reply if it didn't yours...
hooo.. it worked for me now. just kept update.zip in a new SD card and not flashed google apps..
im very happy that i solved one's problem.. ... thread marked as solved...
*UPDATE* : now i realized that we can mark it as solved.. !!! hehe.. Admin do it for us...

FIXED [Q] Stucked on boot after HBOOT change

Hi,
I am not new at flashing and modding but got stucked and need some expert help
Here is what I have done:
1. had hboot cm7r2 and Runnymede AIO ROM - Working great but decided to sell Desire
2. Changed HBOOT to Alfarev Sense, partitioned to ext3
3. Installed Leedroid 3.0.8. Sense ROM
4. Rebooted - after that can not go further than boot screen
I repeated procedure few time but still on boot screen
Any ideas ?!
Why don't you try the STOCK partition table because it has a bigger system partition size
Probably the best choice for you would be to restore stock HTC rom.
Just sayin...
Sent from my HTC Desire using Tapatalk
did you format all partitions? aligned ext3?
Sounds like you did not wipe cache after changing Hboot and did not wipe anything when changing Rom. If you did that, the Leedroid Rom does not fit into Sense Hboot, so you have to change to Stock Hboot:
Wipe everything, flash hboot (do not forget to reboot bootloader and wipe cache afterwards) and then flash ROM again.
MatDrOiD said:
Sounds like you did not wipe cache after changing Hboot and did not wipe anything when changing Rom. If you did that, the Leedroid Rom does not fit into Sense Hboot, so you have to change to Stock Hboot:
Wipe everything, flash hboot (do not forget to reboot bootloader and wipe cache afterwards) and then flash ROM again.
Click to expand...
Click to collapse
Thanks, I did not follow that procedure.
Flashed stock hboot and wiped all, now all works
Sent from my Transformer Prime TF201 using xda premium

First boot taking forever on ICS BCM ROM

Hi folks,
I flashed the ICS 4.0.4 BCM RC3.2U1 ROM on my phone and I have now been waiting for first boot to complete for well over 90 minutes (animation looping continuously).
I wiped Dalvik-cache, formatted the SD-Ext partition as recommended and then flashed the ROM.
How long is the first boot supposed to take? Should I remove the battery and try flashing again?
HTC Desire
S-OFF
Radio 5.17.05.23
Stock hboot
Clockwordmod Recovery
Thanks.
thegreendroid said:
Hi folks,
I flashed the ICS 4.0.4 BCM RC3.2U1 ROM on my phone and I have now been waiting for first boot to complete for well over 90 minutes (animation looping continuously).
I wiped Dalvik-cache, formatted the SD-Ext partition as recommended and then flashed the ROM.
How long is the first boot supposed to take? Should I remove the battery and try flashing again?
HTC Desire
S-OFF
Radio 5.17.05.23
Stock hboot
Clockwordmod Recovery
Thanks.
Click to expand...
Click to collapse
It says about five mins
just be patient
I froze my self few days ago until I've red it in their thread
thegreendroid said:
animation looping continuously
Click to expand...
Click to collapse
this is known as a bootloop. whenever your phone does this for a long time, don't bother waiting for 90mins, it's not going to go anywhere. pull the battery.
thegreendroid said:
I wiped Dalvik-cache, formatted the SD-Ext partition as recommended and then flashed the ROM.
Click to expand...
Click to collapse
as a bare minimum you need to perform a full wipe before flashing a rom: 'wipe data/factory reset' option within recovery.
i don't think you have done this, therefore you have bits of old and new rom mixing up so it bootloops
eddiehk6 said:
this is known as a bootloop. whenever your phone does this for a long time, don't bother waiting for 90mins, it's not going to go anywhere. pull the battery.
as a bare minimum you need to perform a full wipe before flashing a rom: 'wipe data/factory reset' option within recovery.
i don't think you have done this, therefore you have bits of old and new rom mixing up so it bootloops
Click to expand...
Click to collapse
Aye, correct. Before you flash a new rom format boot, system, data, cache, dalvic and sd-ext (which you need if you want mounts2sd!!)
It also says on the BCM thread that at first it may take a while to boot, and 2nd time it will not boot at all, for which you press volume down, power and trackpad to restart the phone, and it will boot fine.
Thanks for the replies all, as it turns out I hadn't wiped the /data partition prior to installing the ROM.
Although I now have a "insufficient storage space" available issue even though I have enabled m2sd. Is anyone else having the same problem?
here's same as u!
thegreendroid said:
Thanks for the replies all, as it turns out I hadn't wiped the /data partition prior to installing the ROM.
Although I now have a "insufficient storage space" available issue even though I have enabled m2sd. Is anyone else having the same problem?
Click to expand...
Click to collapse
its not comin up..its an ics on htc desire, but its not working, i'd performed a factory full wipe, heading for another full wipe..hope it works,
but a question?! should i update the firmware when im coming from gingerbread rom (stock) to ics?
Hi,
can you load your old working rom ?
which one was it ?
thegreendroid said:
Thanks for the replies all, as it turns out I hadn't wiped the /data partition prior to installing the ROM.
Although I now have a "insufficient storage space" available issue even though I have enabled m2sd. Is anyone else having the same problem?
Click to expand...
Click to collapse
did u change the hboot to alpharevs data ++? The rom needs 180mb on the system partition.

[Q] HTC Desire HD 4.2.x ROM Process Stopped Help

Current ROM JellyTime - http://forum.xda-developers.com/showthread.php?t=1827590
Rom Manager v5.5.1.5.
Current Recovery ClockworkMod 5.0.2.0.
So I use Rom Manager to reboot into Recovery, where I wipe dalvik-cache, cache partition and data/factory reset. I then flash the zip, followed by gapps
Tried the following ROMS
http://forum.xda-developers.com/showthread.php?t=2003273
http://forum.xda-developers.com/showthread.php?t=2073992
GAPPS
http://goo.im/gapps - I used the top one CyanogenMod - 10.1.x - 4.2.1.
When booted, I get two messages, press OK and they both continue to appear
"unfortunately system ui has stopped"
"unfortunately, the process com.android.phone has stopped"
It appears as I have only just signed up, I cannot ask the Devs direct. I have searched through threads, and can see some others with same problem - no solution though. About to try a dirty flash from Jellytime.
Thanks
Dave
It must fullwipe before install...cause jelly time is 4.1.2 as and the 2 link above is 4.2
wiping
hdorius said:
It must fullwipe before install...cause jelly time is 4.1.2 as and the 2 link above is 4.2
Click to expand...
Click to collapse
I wipe dalvik-cache, cache partition and data/factory reset - is this not enough?
I forgot the menu of cwm recovery,I use 4ext... Is there any option like format all partitions except sdcard
hdorius said:
I forgot the menu of cwm recovery,I use 4ext... Is there any option like format all partitions except sdcard
Click to expand...
Click to collapse
Ok so, CWM "Wipe Menu" :
wipe dalvik-cache
wipe cache partition
wipe dalvik cache and cache partition
wipe battery stats
wipte data/factory reset
Try to
wipe data, cache and dalvik again
then manually (in the advanced menu if I recall correctly):
format boot
format system
<...> (everything except sdcard)
I've taken a look, and nothing relating to formatting is under Advanced.
Under Mounts and Storage Menu however, there is the following:
unmount /cache
mount /data
unmount /sdcard
mount /system
format /cache
format /data
format /sdcard
format /system
mount USB storage
Yep there.
format /cache
format /data
format /system
-SmOgER said:
Yep there.
format /cache
format /data
format /system
Click to expand...
Click to collapse
Rightyho, well I cleared dalvik & cache (from the Wipe menu)
Then into Mounts & Storage Menu and formatted the 3 above.
Then flashed the ROM followed by Gapps, but still system UI and com.android.phone stopping
davestar7 said:
Rightyho, well I cleared dalvik & cache (from the Wipe menu)
Then into Mounts & Storage Menu and formatted the 3 above.
Then flashed the ROM followed by Gapps, but still system UI and com.android.phone stopping
Click to expand...
Click to collapse
Seems like the gapps flashed is the wrong one.. I got the same problem as yours when i was flashing 4.2.1 rom with gapps for 4.1.2.. after that i realized and use the correct one and it boot up perfectly..
That's right. Download the correct gapps for your Android version. http://goo.im/gapps has a properly categorised list.
Jelly Time = CyanogenMod 10 (Android 4.1.2)
Sent from my Desire HD using xda premium
yumm91 said:
Seems like the gapps flashed is the wrong one.. I got the same problem as yours when i was flashing 4.2.1 rom with gapps for 4.1.2.. after that i realized and use the correct one and it boot up perfectly..
Click to expand...
Click to collapse
I flashed just the ROM by itself, and booted up with the same two errors
davestar7 said:
I flashed just the ROM by itself, and booted up with the same two errors
Click to expand...
Click to collapse
Thats weird.. if you have already format everything except sdcard, and flash the rom only, and still got the same problem, then the cause is either from the cwm,which is quite outdated, or the rom itself.. but i doubt the rom is the culprit... try use ext4 recovery or update the latest cwm.. or maybe wait for someone who have a better solution..
Sent from my Desire HD using xda app-developers app
sashank said:
That's right. Download the correct gapps for your Android version. http://goo.im/gapps has a properly categorised list.
Jelly Time = CyanogenMod 10 (Android 4.1.2)
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
Sorry but I am currently running Jellytime, but trying to flash TO 4.2.x AOSP codefirex - http://forum.xda-developers.com/showthread.php?t=2003273
Where do I update CWM from? I have the rom manager installed, should I use that?
Try to remove SD card. Just in case, as it all seems a bit mysterious.
davestar7 said:
Sorry but I am currently running Jellytime, but trying to flash TO 4.2.x AOSP codefirex - http://forum.xda-developers.com/showthread.php?t=2003273
Where do I update CWM from? I have the rom manager installed, should I use that?
Click to expand...
Click to collapse
Im not sure about updating cwm, because i changed it to ext4 recovery after cwm 5.0.70 that came with aahk cannot do backup correctly for me.. but if you would like to try ext4 recovery, you can find it in google play.. and it is very easy to install it..
Sent from my Desire HD using xda app-developers app
yumm91 said:
Im not sure about updating cwm, because i changed it to ext4 recovery after cwm 5.0.70 that came with aahk cannot do backup correctly for me.. but if you would like to try ext4 recovery, you can find it in google play.. and it is very easy to install it..
Sent from my Desire HD using xda app-developers app
Click to expand...
Click to collapse
Thanks for the replies, sorry I was busy over the weekend.
I tried booting 4.2.x with no SD, and same error occurs.
I am not interested in trying 4EXT, CWM is a widely used custom recovery I can't see why this could be at fault? I am running the latest version, though not the "touch" version!
Can't find anyone else with this issue!
BTW - I am S-ON?
Any further help or advice on this one?
Thank you.
I would try 4ext. CWM has had some problems on thus phone in the past. Also, if you are S-ON, are you fastboot flashing the boot.img? Check the Ace Think Tank thread in the General forum for a guide on how to do that. Though usually, not doing that results in a phone that hangs at the splash screen, not one with systemui stopping...

Wildfire major problem!!!

Hey guyss
I am currently using RemPuzzle's latest ROM but the reason why i am posting it here is becoz it has been happening with all the ROMs that I have tried!
The phone works completely fine until the display is turned off for quite some time (put to sleep)! Then when ever I try to open it, it wont! The only way to make it work is by battery pull! I have tried flashing other ROMs but the same problem occurs with them. For now, I have selected in 'Screen Timeout' to 'never turn off'! But still it is very annoying me!
What I do when flashing the ROM: (CWM 5.0.2.0)
Wipe data/cache partition
Wipe cache partition
Wipe Dalvik Cache
Wipe boot
Wipe cahe
Wipe data
Wipe system
Flash ROM
Flash gapps (if necessary)
Flash CronMod
Flash CronMod dalvik cache wipe tool
Reboot system
Do tell me if im doing anything wrong!
Thnx in advance!
CallOfHonor100 said:
Hey guyss
I am currently using RemPuzzle's latest ROM but the reason why i am posting it here is becoz it has been happening with all the ROMs that I have tried!
The phone works completely fine until the display is turned off for quite some time (put to sleep)! Then when ever I try to open it, it wont! The only way to make it work is by battery pull! I have tried flashing other ROMs but the same problem occurs with them. For now, I have selected in 'Screen Timeout' to 'never turn off'! But still it is very annoying me!
What I do when flashing the ROM: (CWM 5.0.2.0)
Wipe data/cache partition
Wipe cache partition
Wipe Dalvik Cache
Wipe boot
Wipe cahe
Wipe data
Wipe system
Flash ROM
Flash gapps (if necessary)
Flash CronMod
Flash CronMod dalvik cache wipe tool
Reboot system
Do tell me if im doing anything wrong!
Thnx in advance!
Click to expand...
Click to collapse
I think the phone isn't functioning properly, you've done everything right :good:
But my best guess that it's the phone
I've got a few tips, revert back to stock
Flash cwm revolutionary 4.0.1.4 and re install a custom ROM, it's what I've done every time to solve all my issues :good:
If my way doesn't work or solve any issues, then I'll try to give more advice in return, if others would like to aswell
Also if phone still reacts all weird, it's best if you take the phone to someone who can fix it up :good:
In any case i'll try and do my best
CallOfHonor100 said:
Hey guyss
I am currently using RemPuzzle's latest ROM but the reason why i am posting it here is becoz it has been happening with all the ROMs that I have tried!
The phone works completely fine until the display is turned off for quite some time (put to sleep)! Then when ever I try to open it, it wont! The only way to make it work is by battery pull! I have tried flashing other ROMs but the same problem occurs with them. For now, I have selected in 'Screen Timeout' to 'never turn off'! But still it is very annoying me!
What I do when flashing the ROM: (CWM 5.0.2.0)
Wipe data/cache partition
Wipe cache partition
Wipe Dalvik Cache
Wipe boot
Wipe cahe
Wipe data
Wipe system
Flash ROM
Flash gapps (if necessary)
Flash CronMod
Flash CronMod dalvik cache wipe tool
Reboot system
Do tell me if im doing anything wrong!
Thnx in advance!
Click to expand...
Click to collapse
Do you have a HTC buzz or a HTC bee? This is a deep sleep issue from the kernel. My and kylon had this issue with the htc bee.
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
heavy_metal_man said:
Do you have a HTC buzz or a HTC bee? This is a deep sleep issue from the kernel. My and kylon had this issue with the htc bee.
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
Click to expand...
Click to collapse
Yep! I am sure it is HTC buzz!
Stone. Cold said:
I think the phone isn't functioning properly, you've done everything right :good:
But my best guess that it's the phone
I've got a few tips, revert back to stock
Flash cwm revolutionary 4.0.1.4 and re install a custom ROM, it's what I've done every time to solve all my issues :good:
If my way doesn't work or solve any issues, then I'll try to give more advice in return, if others would like to aswell
Also if phone still reacts all weird, it's best if you take the phone to someone who can fix it up :good:
In any case i'll try and do my best
Click to expand...
Click to collapse
Unrooted and rooted again! At first, i thought it had worked but...BAM...it hanged again!
I think I am not rooting correctly...=(
1. I wasnt able to S-ON my device after unrooting so I carried on...=/
2. After doing the revolutionary part, I wasnt able to install Android Bootloader Interface! It kept giving me the error that the hash of the file is missing or something! So I did something else. Now, when I go to cmd and write 'adb devices', it doesnt show my device! Although, when I write 'fastboot devices', it shows my device attached! (weird)
3. I flashed recovery with revolutionary so I reckon that I didnt had to do the unrevoked method...was i wrong??
Help appreciated...=)
CallOfHonor100 said:
Yep! I am sure it is HTC buzz!
Unrooted and rooted again! At first, i thought it had worked but...BAM...it hanged again!
I think I am not rooting correctly...=(
1. I wasnt able to S-ON my device after unrooting so I carried on...=/
2. After doing the revolutionary part, I wasnt able to install Android Bootloader Interface! It kept giving me the error that the hash of the file is missing or something! So I did something else. Now, when I go to cmd and write 'adb devices', it doesnt show my device! Although, when I write 'fastboot devices', it shows my device attached! (weird)
3. I flashed recovery with revolutionary so I reckon that I didnt had to do the unrevoked method...was i wrong??
Help appreciated...=)
Click to expand...
Click to collapse
What is this cronmod you've been flashing?
Sent from my Nexus 7 using Tapatalk 4
heavy_metal_man said:
What is this cronmod you've been flashing?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Its this:
http://forum.xda-developers.com/showthread.php?t=1716124
But now there is something else!
I again unrooted my phone and rooted it again! This time, I did everything perfectly! The drivers, the unrevoked, everything right! But, I didnt flash ANYTHING!! I didnt flash cronmod or even a ROM! And it still hangs up!! =(
Is it possible that im rooting it wrong! Or it doesnt support sense? =/
CallOfHonor100 said:
Its this:
http://forum.xda-developers.com/showthread.php?t=1716124
But now there is something else!
I again unrooted my phone and rooted it again! This time, I did everything perfectly! The drivers, the unrevoked, everything right! But, I didnt flash ANYTHING!! I didnt flash cronmod or even a ROM! And it still hangs up!! =(
Is it possible that im rooting it wrong! Or it doesnt support sense? =/
Click to expand...
Click to collapse
Well this will only work if you have the correct ext partition on your sdcard, and I don't think root has anything to do with this. Have you ran an ruu yet? If not run one, if yes which one?
Sent from my Nexus 7 using Tapatalk 4
heavy_metal_man said:
Well this will only work if you have the correct ext partition on your sdcard, and I don't think root has anything to do with this. Have you ran an ruu yet? If not run one, if yes which one?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Oh DAMN! I completely forgot about the ext partition! =D
I made the partition long ago via recovery! I dont know what type of ext it is... =/
will removing the ext would solve the problem?
Which ext is the correct ext partition??

Categories

Resources