Develop Bugs

[q] help phone stuck in boot loop!!

I flashed a new kernel, I was running kkernel v14cw
and I flashed buzz_cm_1.1.4_OCUV
and now it is stuck in a boot loop.
please help me D:

I got the same problem? You found a fix yet pal???
Cheers

Try this tool for flashing your kernels instead of doing it by recovery guys. The problem its not uncommon.
http://forum.xda-developers.com/showthread.php?t=852357
Sent from my performance enhanced Desire HD.

P1xelVandal said:
I flashed a new kernel, I was running kkernel v14cw
and I flashed buzz_cm_1.1.4_OCUV
and now it is stuck in a boot loop.
please help me D:
Click to expand...
Click to collapse
Boot into recovery and flash your ROM again , this will restore the original kernel and keep your data intact

ghostofcain said:
Boot into recovery and flash your ROM again , this will restore the original kernel and keep your data intact
Click to expand...
Click to collapse
You only need to restore the kernel (boot partition, i think).

Maybe someone should make the stock kernels availible to flash? i had to reflash my roms yesterday, because i tried a kernel i didnt like, and could find the stock one to return back

[Q] HTC Desire HD Stuck on White screen - S-On with Root access

I have a problem with my HTC Desire HD after attempting to flash a custom rom.
Bootloader unlocked using HTCDev
Clockwork Mod Recovery (Touch version) installed
Root access
Phone will not boot into Android, stuck on white 'HTC' screen.
I have adb access when phone is in Clockwork Mod Recovery
adb shell is showing # so assume I have root
When attempting to flash RUU or PD98IMG get Main Version Older error.
So please can someone guide me in the right direction to recover this phone?
Many thanks
K

When you unluck using HTC dev flashing roms is different. You have to flash the boot.img separately. So what you do is flash rom,then boot into hboot and make sure fast boot is selected. Then flash the boot.img using the command
Fastboot flash boot boot.img
Then reboot. You'll have to do this every time you change roms. I recommend getting 4ext as it has a new feature that will do both steps for you and make it more like the regular soff method of flashing
Sent from my Inspire 4G using XDA

Hi
Many thanks for tyour help, but I am still having problems.
I copied the boot.img from the Rom I had flashed (in Kernal/saga directory)
flashed boot.img using fastboot
but... still stuck on HTC white screen.
What have I misssed?

Not sure what you mean by kernal/saga directory. What from are you trying to flash? Saga is a different phone
Sent from my Inspire 4G using XDA

Hi
I have tried again flashing boot.img that is in a PD98IMG.zip file.
Same result - stuck on HTC White screen.
Thanks for your help with this - is there anything else I need to check / do?

Your trying to flash the boot image of the pd98 onto a custom rom? Let's start from the beginning. Download a custom from from the dhd dev section. Let's say arhd. Place it on SD card and a copy of it boot image(from inside the from zip) in sdk where fast boot is located.
Boot into car do a full wipe(data/cache/system) and flash rom. Reboot into boot then flash the boot img
Sent from my Inspire 4G using XDA

Many thanks - I realised my error from your previous comment on the sage Kernal.
repeated with the boot.img from the Ace directory in the ROM and I now have success.
I borked this on Sunday and have spend hours googling and reading trying to get it back - so many thanks for your help (and patience).
Muchly appreciated!!

it worked for me i flashed a pac-man 4.2.2 and a jelly time rom both successful after i flashed the boot img thanks a million bro :good:
inspire 4g
unlocked bootloader
s-off
root access
clockwork recovery

I think I corrupted something

I picked up a Wildfire S Virgin Mobile that cannot be activated. I wanted a small mp3 player with an Android flavor. I unlocked the bootloader via HTCdev.com. I loaded Team BlueRidge Recovery 1.1.0. I made a nandroid backup.
I tried to flash a couple CM roms and on bootup they would get past the HTC splash screen and go blank and that would be it. I tried a GB rom and it flashed fine and booted up. However it turned out it was a marvel rom and not a marvelc rom so wifi and BT didn't work. I decided to try loading a TeamWin recovery. I put the newest one and when I tried to flash a rom it gave me an error. I downgraded it to v2.2.2.0 and had the same error. I put TeamRidge back on and now every rom I try to install errors on me.
I am guessing that I corrupted something when I tried to flash with TeamWin and now I can't flash anything. I reformatted the sdcard but it made no difference.
CAn anyone bail me out. I really want to run a CM9 or CM10 rom.

Anyone?? I am kinda stuck, so any ideas might help. Thanks

Try to install clockwork mod recovery using either fast boot or adb via your PC. I have never had issues flashing ROMs that way
Sent from my Crescent using xda app-developers app

[Q] Recoveries (CWM, TWRP, stock) not working after JB4.2 update

Hi,
I've never posted here before because I've always been able to find info via searches up until this point, but it seems I am the only one who's had this problem?
THE PROBLEM:
I upgraded to JB 4.2 this morning on my GSM Galaxy Nexus. I had CWM recovery. I've never had a problem with it before. I needed to re-root my device so I tried using the tool found here (http://forum.xda-developers.com/showthread.php?t=1392310) and various other methods. None worked.
Furthermore, I noticed that every time I went into recovery it just showed the android lying on his back with a red error symbol above him. I tried re-flashing CWM recovery, then tried TWRP recovery, then even tried re-flashing stock recovery, and all of them give the same result.
Can anyone shed some light on this situation for me? I'm an app developer and I need to have my phone rooted (and I'd like to get the recovery sorted out too), but unfortunately I'm relatively noob when it comes to the inner workings of android.
Any help would be much appreciated!

How are you flashing the recoveries? Fastboot? I had to go back to 4.1, flashing latest recovery with fastboot, and then flash a custom/stock 4.2 using the recovery to achieve root on 4.2.

djluis48 said:
How are you flashing the recoveries? Fastboot? I had to go back to 4.1, flashing latest recovery with fastboot, and then flash a custom/stock 4.2 using the recovery to achieve root on 4.2.
Click to expand...
Click to collapse
Yeah I used fastboot, and I believe that toolkit uses it as well. Did you have the same problem as me?
How did your method work? Did 4.2 make changes to the fastboot, which is what you were getting around? I don't understand why that's a problem that other people don't seem to be having.

[Q] android 4.3 Rom installing

Hi
I'm on 4.3 and I tried to root my phone, after some serious reading I could manage to root it with the nexus root toolkit. after that I tried to install another Custom ROM but everytime it didn't boot. Can anyone tell me what I'm doing wrong? I've searched in this and other foruns but didn't see any solution.
best regards

Did you wipe prior to installing it?
Did you flash anything else with it?
Do you see the ROM's boot animation?
Does the custom recovery give an error when installing?

It didn't gave me any error, and I did all the wipe before. I've tried two diferent ROMs and the result was the same, they stuck in loop at the boot animation. I've tried also with different recovery and it was the same.
I had an HTC before and it gave me a similar problem, but with that I just had to upgrade hboot, with this one I don't know what to do...

F4B10F said:
It didn't gave me any error, and I did all the wipe before. I've tried two diferent ROMs and the result was the same, they stuck in loop at the boot animation. I've tried also with different recovery and it was the same.
I had an HTC before and it gave me a similar problem, but with that I just had to upgrade hboot, with this one I don't know what to do...
Click to expand...
Click to collapse
Can you fastboot back to stock?

Yes I can , my only problem is that I can't boot any custom ROM.