Hello! I tried installing a new kernel on my G2X from this thread. I used the CM DL over the DS.
http://forum.xda-developers.com/showthread.php?t=1073626
I believe I made the mistake of clearing all cache instead of just the Davlik Cache and am unable to get ROM Manager as I fear I may have wiped it from my phone. Subsequently I am stuck in a boot loop after the LG screen loads and just get a black screen.
I tried flashing my ROM back to Stock ROM from NVFlash and was able to do that successfully. I could not continue with the steps in the thread below past Step 5 as I just get a black screen after the LG logo loads.
http://forum.xda-developers.com/showthread.php?t=1180331
Did I permanently brick my phone or is there a way to recover from this? Thanks for any help!
You need to flash cwm 5020 with the nv flasher. Then you can install any rom you want and boot successfully. It sounds like you are not installing a real recovery. Any other questions just PM me or email at [email protected]. You are not bricked.
Sent from the fastest g2x in the world
I was running Cyanogenmod9 on my SGH-I727R when I got into a bootloop. I reflashed stock Rogers Rom and still stuck in a boot loop. Any help please?
Scarecrow Legion said:
I was running Cyanogenmod9 on my SGH-I727R when I got into a bootloop. I reflashed stock Rogers Rom and still stuck in a boot loop. Any help please?
Click to expand...
Click to collapse
Can you please be more specific?
What screen are you exactly getting, the boot logo then a reboot? are you getting a recovery screen or do you bootloop not into the system but into ClockworkMod recovery?
The boot boot logo then restart. same thing with the stock rom it would boot into the Rogers logo then restart
Have you tried formatting through recovery? formatting can be found in mounts and storage.
yup, when I get back home I'll see if I can darkside wipe. see if that will help
That should help a lot. It should definitely work, make sure you install a Custom ROM and not a Stock ROM.
Make sure in future situations you don't install a stock ROM if your current ROM is a custom ROM, this can cause problems and will not fix problems. If you want to revert back to Stock ROMs after installing a Custom ROM I highly recommend you use Fastboot to flash the image. However there are tutorials and instructions on how to use Fastboot efficiently and properly so you don't mess anything up.
Cheers
Thanks again, darkside wipe worked. I have no clue what bricked it in the first place though
Scarecrow Legion
No problem Wiping everything would've worked too lol!
I can access recovery, Hboot and flashboot, but no luck getting the phone to boot up past the splash screen, it think it, its the white screen with HTC logo on it
Have you tried a factory reset from recovery, then flashing a custom ROM?
post-mortem said:
Have you tried a factory reset from recovery, then flashing a custom ROM?
Click to expand...
Click to collapse
I have tried factory reset from hboot, my cwm recovery, and i cant find a custom rom. I have extracted the rom.zip from my original ruu found on htcdev. I put it on sd card and tried flashing thru recovery and thru hboot. I try doing fastboot, with the system.img and it actually crashes my pc, and when loading thru hboot, i get stuck at parsing .zip
I think you need to ask people who are more familiar with HTC devices. Type "htc rhyme" in the search bar at the top right of this page.
CWCOXXX said:
I have tried factory reset from hboot, my cwm recovery, and i cant find a custom rom. I have extracted the rom.zip from my original ruu found on htcdev. I put it on sd card and tried flashing thru recovery and thru hboot. I try doing fastboot, with the system.img and it actually crashes my pc, and when loading thru hboot, i get stuck at parsing .zip
Click to expand...
Click to collapse
Boot into fastboot and run the RUU.
Theonew said:
Boot into fastboot and run the RUU.
Click to expand...
Click to collapse
I did, believe me, I have spent hours and days googling, and every similar situation ppl have, the soution doesnt work for everybody, lol, and I just happen to be one of them. My rhyme is an upgraded OTA, from the original stock rom which is an ruu: RUU_Bliss_C_VERIZON_WWE_1.26.605.6_Radio_1.15.00.0816_NV_VZW2.67_release_214911_signed, and when i try running the ruu installer it says; From:image version 2.0.0.134076
To: 1.26.605.6, After 16% PROGRESS, ERROR [155]: UNKNOWN ERROR, The ROM upadate uti;ty couldn't update, please find correct RUU and update again. I dont know what else to do, ive been researching for a while and so now im in the XDA forums asking for help, before i was just searching for anything related to this problem with HTC rhyme, and not much about the rhyme it self is out there for support in these situations, so ive been researching the issue with all htc devices, and even android in general. I'll admit i am a noob at androids, but im actually pretty familiar with OS's and computers period. All help is much appreciated too, so thank you and if you know something i dont, please feel free to let me know where I am screwing up. I can get My CWM on it, and actually before all this, i had CWM touch recovery, somehow i lost it too and had to put the one i have now on it. i also parsed thru hboot my boot.img, and recovery before, , and it said it was successful. when doing system.img thru the PI46img.zip with boot and recovery, it freezes on parsing, and if i fastboot the system.img, it causes my computer to freeze, and i got the system.img from the rom.zip out of this RUU, that i mentioned above. ive done all the wiping from recovery of partitions that ppl had mentioned, and still no luck, and also when trying to flash it thru CWm it always says installation aborted. tahnk s for responding too man, ive noticed most questions with The HTC RHyme, get the shaft....and thats why i feel like im at a deadend, and i dont know if there is some number out there for support in theses situations, because HTC wont help after the bootloader has been unlocked, and it would seem a lil easier having someone walk you through it on either a live chat or over the phone
http://forum.xda-developers.com/images/smilies/confused.gif
.
BLISS XC SHIP S-ON RL
HBOOT-1.32.0011
RADIO-1.23.00.0224
eMMC-boot
HTC rhyme recovery prob.
Hi I really need help. I unlocked the boot loader from HTC Dev. Then rebooted the the bootloaderbfrom adb. The fastboot flash recovery. Everything was good until I pushed the mount through adb it gave me an error. Now every time I try a factory reset or try to go to recovery it takes me to the white HTC logo and nothing happens. Please help. The phone is switching on everything is working. I just can't factory reset or go to the recovery.
Okay, let me tell you how I soft bricked (Atl east I think its a soft bricked)
It all starts out with me unlocking my bootloader with htcdev, flashing a recovery on it, then putting superuser.
I wanted to install CM 10.1. I don't have s-off, so I read up on how to do it with the procedure of fastboot flash boot boot.img. I put the zip file on ym sdcard and I went into 4ext, wiped cache and dalvik factory reset , and formated system. I rebooted into bootloader and flashed the boot.img. Rebooting it, it got stuck on black screen. With a little research, i found out my hboot probably did not support the jellybean (cm) I was flashing onto it. So I download a gingerbread rom and used the boot.img of that to try and fixed it, it went into a bootloop. Later on after trying this again, it softbricked (Stuck on htc screen). I tried to install another rom onto it , GizRoot. Its a gingerbread rom. It did not help whatsoever.... Anyone can help me with this?
So recently I ended up with a soft brick trying to flash a custom rom. I was able to fix it with by flashing the RUU.zip. When trying to reroot my device and flash a custom rom, I ended up stuck in a boot loop. It gets to the HTC Screen and after that it goes black for about a minute before repeating. When I go into recovery and try to install a custom rom, it tells me it cannot mount data... Any help would be greatly appreciated!!
P.S. I am on a mac so my options are much more limited