Related
Tuesday night I loaded CM7, and then the Market wouldn't update my apps so I decided I would restore BAMF 1.5. After doing so, the Market just gave me "Fails" trying to update, and I could not access recovery, as I was going to do a complete wipe and reflash. Most of Wednesday, an extremely helpful & knowledgable member, Mattgyver83, tried diligently to help me rectify the situation, but to no avail. We tried to Fastboot, tried flash_image, tried fix permissions...shoot, I practically wore out adb..anyway, I ended up reverting back to stock and unrooted. I used jcase's method to revert back to stock, and that was painless, and successful. I decided last night to try rooting again, thinking a fresh root would solve my issue of not being able to access recovery. Root was successful, but I still cannot access recovery, through rom manager, or through bootloader. When I attempt it my Tbolt goes to white HTC screen, and stays there. All functions of my phone now work, and all aspects of root work, except I cannot flash anything. Rom manager shows I have clockwork recovery, but I just can't get to it.
Sorry for the long ramble. If anyone has had this issue, or if anyone knows a fix, I would appreciate it. Otherwise, I wait for Gingerbread.
Thanks
Happened to me with CM7 builds. For some reason they were erasing the recovery. Just have to reflash the recovery in Rom Manager and you'll be all set in the future.
do what i do pull batt leave out for a min, then put the batt back in and connect usb right away.
travishamockery said:
Happened to me with CM7 builds. For some reason they were erasing the recovery. Just have to reflash the recovery in Rom Manager and you'll be all set in the future.
Click to expand...
Click to collapse
Tried that, but thanks. Still just goes to white HTC screen, and stays there until I do battery pull.
jr4000watts said:
do what i do pull batt leave out for a min, then put the batt back in and connect usb right away.
Click to expand...
Click to collapse
I can get to bootloader, just not able to get into recovery.
I'm stabbing in the dark at this, but this did work for me with my Droid...
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Ie. Flash recovery and wait until the confirmation pop-up/message only takes a few seconds to pop up. If the message takes longer than 5 seconds or so, re-flash recovery and repeat until the confirmation comes up quickly.
This sounded retarded to me, but I was at the end of my rope so I tried it. It worked like a charm.
M.
monolithic said:
I'm stabbing in the dark at this, but this did work for me with my Droid...
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Ie. Flash recovery and wait until the confirmation pop-up/message only takes a few seconds to pop up. If the message takes longer than 5 seconds or so, re-flash recovery and repeat until the confirmation comes up quickly.
This sounded retarded to me, but I was at the end of my rope so I tried it. It worked like a charm.
M.
Click to expand...
Click to collapse
Thanks, but that didn't work. I think something in my os got lost when I restored BAMF from CM7.
Yea I spent a good few hours yesterday trying to help Orio out and we attempted a ton of things to try and fix the recovery issue, this post should offer a bit more insight to the methods used, this is running off memory;
adb reboot recovery failed
Reinstall latest Rom Manager apk and Flash CWM
flash latest rom manager via fastboot (CWM only)
(fastboot flash recovery /sdcard/recovery-clockwork-3.0.2.5.img)
**did not do fastboot erase recovery first**
"return to stock safely and properly" XDAthread by jcase
return to stock image [RUU], reroot, try again
try to boot into recovery via hboot
manually installed fix_permissions.sh script and busybox on rooted stock, ran.. didnt fix
tried to see if flash_image method would work, didn't
All of the above have failed and we basically tried almost all combinations. Not once would this phone get back into recovery, even after flashing the appropriate RUUs which include either stock android or CWM recovery. The only thing we have not currently attempted which might be the last thing left is to do is manually install the nandroid.sh script and do an advanced restore of the recovery image only from a nandroid backup on SD. I would rather not go down this method as it could have an undesired result, I have done it to restore a G1 back in the day but not 100% if its gonna work on a tbolt. Thankfully his phone boots, and we can get into hboot, but yea.. pretend recovery just doesnt exist at all...
Curious if anyone has any knowledge above what we have already tried.
monolithic said:
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Click to expand...
Click to collapse
I recall the same thing and its a good thought however that was mostly a generic error due to a CWM update and CM6 (I think) but either way flashing an RUU should override this shortcoming and im pretty sure that issue was worked out in CWM as well.
Not to be rude, but I don't think this question belongs in the development section.
Orio56 said:
I can get to bootloader, just not able to get into recovery.
Click to expand...
Click to collapse
do you still have the P zip file for the radio (baseband) on your SD card? if you do....try to delete it...then hold power and volume down button down....then see if you can get into recovery....
probably not going to work...but it is worth a try......
hogowner said:
do you still have the P zip file for the radio (baseband) on your SD card? if you do....try to delete it...then hold power and volume down button down....then see if you can get into recovery....
probably not going to work...but it is worth a try......
Click to expand...
Click to collapse
Thanks, but no, I deleted that after loading it. I actually reverted back to stock/unrooted last night and rerooted and the problem still remains. It's quite strange.
maybe i missed it if someone suggested this but what about flashing an older version of CWM?
shelooga said:
maybe i missed it if someone suggested this but what about flashing an older version of CWM?
Click to expand...
Click to collapse
That is what I was going to suggest. In ROM Manager at the very bottom try and flash an older version.
Sent from my ADR6400L using XDA Premium App
SUCCESS !!!
I fixed it !
Apparently, when I loaded up cm7, files showed up about the same time on my sdcard in clockworkmod download file. I deleted those files, and reflashed clockworkmod in rom manager, (which this time took like 3 - 4 minutes), and rebooted into recovery and it worked...did it again, just in case it was a fluke and it worked.
All is well now...the planets are realigned !!!
Thanks everyone for your ideas and especially thanks to mattgyver83 who helped me for something like 4 hours yesterday. Exceptional kindness !!
mods...you can close this thread.
GREAT NEWS!!!! CONGRATULATIONS!!
THANKS FOR REPORTING BACK!
This may help out other members with the same problem!!
now go ahead and start playing with your T-BOLT again!
That's a very odd solution. My first two things to try would have been:
1) fastboot:
fastboot erase recovery
fastboot flash recovery C:\some\local\path\recovery.img
You can't, well, probably shouldn't, flash a recovery from the /sdcard. When in fastboot mode I don't think the sdcard is even mounted. Either way, I think fastboot needs the img file on the local file system.
2) Create a PG05IMG.zip file with the recovery.img file in it, and flash that through HBOOT. Although this should have been done in some form or fashion when you downgraded or re-rooted, so YMMV.
Ok so I rooted and RoM'd my phone a long time ago with Cherryblur which apparently is no longer supported or updated. It has been so long that I forgot what I did and did not do to get cherry on it. Yesterday I spent most of the day researching how not to brick my phone. Today after doing everything I could find, I am stuck at the motorola screen. It is unlocked on the moto screen, has fastboot and adb installed, I can get into recovery and what seems to successfully recover the cherryblur install just results in a bootloop at the custom animation that is past the motorola screen.
I was trying to flash CM7 (tried neutrino as well) non nightly when this happened. After spending all day on here bouncing around while I was at work I found a fruitcake that seems to be the only thing that will allow my phone to boot which of course I cannot send the link to. Its titled [Fruit Cakes] XDA Re-Release [feb\18\2012] if you need to see it. What am I missing, I have clearly searched and searched these great forums (I do love to research, but find I'm at an impasse now) and am not sure what I need to do to proceed. That fruitcake updated my phone to 4.5.91 and I'm pretty sure I was 4.5.2 from the Cherryblur previously.
Thanks for any help!
Update: After getting fruitcake to work, I figured maybe this fixed my previous issues and tried to install CM7 again. Same story, not moving past the first Moto screen. So I tried recovery of the fruitcake and now the M screen comes up, waits a bit, then looks like it's going to load and starts to flash for about a second on, then off for 2-3, then on and so forth. I reflashed fruitcake after this and it is still working as a new install.
You are probably only softbricked. Do you know what "recovery" software you are using? If you are using romracers or one of the better respected recovery software packages, you should be able to use fastboot (if you have a windows machine) to wipe the relevant partitions on your phone and start again. Essentially, you will want to reinstall cherryblur (or install a new ROM - Neutrino, Nottachtrix, CM9s are all excellent) from your sd card. To do this, you will boot to fastboot and run "fastboot -w" from your pc. Then boot to recovery, and wipe cache, and dalvic for good measure, then install cherryblur or another package from the zip file. This will hopefully square you away and get rid of the boot loops.
My guess is that you did not wipe your partitions completely before attempting a new install, and may be having problems with ext3 vs. ext4 formatting between rom versions. Good luck to you.
Thank you for the reply!
Originally I'm pretty sure it was CWM, through the process of backing stuff up I installed Rom Toolbox from market and that seemed to have changed something? (Not sure here...) The text changed color from what I thought was white to blue and it looked a tiny bit different. The only thing I did not do was the fastboot -w, but I did download the link from [Batch] FFW - Fastboot Full Wipe and ran the fastboot from there, which was supposed to do a full wipe from what I read. Fastboot was previously installed on the phone.
I downloaded the 1.1 version which apparently may not be able to wipe the webtop, though when watching the text during the wipe it seemed to go through. Would you recommend me going to romracers, is it possible that my recovery software is borked somehow or just not compatible with the newer roms? If I got to RomRacer will the process of doing that just get rid of the current recovery software I have on the phone or will I run into issues? As far as the dalvik and cache I did run those, though the instructions for the CM7 said to do that after the install which felt backwards....
Oh yes, and I can't reinstall cherryblur, that rom is gone - you can't even download it anymore. I am doing this because I recently purchased a lapdock and the cherryblur was not doing so hot on it so looking to install a good clean rom (with a nice GUI) that works well on the lapdock as well. Yes, I will put an OC'd kernel on it as well, battery life has never been more than a day on my current rom and I am reading that the newer ones have over 1 day life on them so you could say I'd be used to the battery drain on the 1.3 kernels.
I see...that's frustrating. I think given your situation, I would probably not attempt to go from Blur to CM (at least while attempting to get the phone running again). If I were in your shoes, I would do the following...other more knowledgeable folks may steer you in varying directions, but I have been in your shoes before, and this should work. I am assuming you have use of a PC...if not, this won't be helpful.
1. Install ROMRacers recovery using these instructions: http://forum.xda-developers.com/showthread.php?t=1204500
2. Download Nottachtrix 1.3.1 to your SD card using your PC if necessary, and you will probably want to download the webtop 2.3.6 at the same time. These can be found here: http://www.nottachtrix.com/forum/
3. Boot into fastboot (hold volume down on power up, until fastboot appears, then hit volume up, and use a DOS prompt to do the fastboot commands through the USB on your PC), and do a fastboot -w, then fastboot -reboot.
4. This time boot into recovery by holding volume down on powerup, and hitting volume down seven times (I think) until you see the word recovery, then hit volume up.
5. Use recovery to wipe cache partition, then go to advanced and wipe dalvic cache, and then select factory reset/wipe data. Some of these steps may be duplicative, but I am a belt and suspenders kind of guy.
6. Now go to "install from sd card" and select the Nottachtrix build that you put on your external SD, and make selections using the cool Aroma installer. Once this installs, you can install the newer 2.3.6 webtop (if you need it).
7. Reboot when complete, and you should have the latest stock build in working order, and then you can repeat the process to install Neutrino, CM9 or whatever. Feel free to fire back any questions.
Good luck to you, and if this helps, please hit the "thanks" button!
Ill give this a shot when I get home, darn work blocking the download links for mediafire..... The fruitcake is driving me nuts, no notification bar (my biggest complaint) unless I use ADW launcher, which has for some reason no way for me to get into my texts..... Broken apps, and a real stock feel that is just making me grit my teeth lol.
Can't wait to have a nice ROM on my phone again. Glad the fruitcake got me back up and functional though!
So far so good! Had the notification bar problem like others with the 2.3.6 issue and found that fix (disable email notifications....). When / if I can 'thank' I will! And will keep you updated when I get the time to flash another rom.
Good news that you are back rolling again. Let the ROM flashing addiction continue
So, CM7 is pure sexy - and an OC'd kernel to 1.3 makes me so happy in both CM7 and Nottachrix. Wish I would have done it sooner, I wouldn't have been spending so much time searching for a new phone because my atrix was annoyingly laggy. Lag? What is that? Also, undervolting is AMAZING for battery life, for the first time since owning the phone I did not plug it in last night and even though my usage was in the light to medium area, im still at 66% after 22 hours off charger ! Can't wait to play with CM9.
Before doing my flash, I did my research, and it seemed that in order to update from CM7 to CM10, I had to flash a different version of CWM. So I booted into recovery, flashed the version 6.xxx CWM, and then rebooted (I assumed that in order to flash CM10, I had to be in a CM10-compliant recovery). After getting back to my regular desktop, I rebooted into recovery as normal... only it didn't go into recovery. Instead, it paused for a moment like it would go into recovery, then booted to my normal desktop.
I've tried about a billion ways to boot into recovery, to include SD based recoveries, but it either goes to a larger sized N screen, then hangs up on a black screen, or it boots me to my normal CM7. I "can" continue to operate on CM7, but until I can boot into recovery, I can neither update to CM10 nor address any problems I come across in my current build.
Suggestions?
nashdude said:
Before doing my flash, I did my research, and it seemed that in order to update from CM7 to CM10, I had to flash a different version of CWM. So I booted into recovery, flashed the version 6.xxx CWM, and then rebooted (I assumed that in order to flash CM10, I had to be in a CM10-compliant recovery). After getting back to my regular desktop, I rebooted into recovery as normal... only it didn't go into recovery. Instead, it paused for a moment like it would go into recovery, then booted to my normal desktop.
I've tried about a billion ways to boot into recovery, to include SD based recoveries, but it either goes to a larger sized N screen, then hangs up on a black screen, or it boots me to my normal CM7. I "can" continue to operate on CM7, but until I can boot into recovery, I can neither update to CM10 nor address any problems I come across in my current build.
Suggestions?
Click to expand...
Click to collapse
Have you tried holding on the power button and the "n" button as you boot? I recall running into a similar issue as yours and that was the only way I could get to recovery. If you're able to get into recovery that way I would consider maybe getting a different version fo CWM. I had trouble with the 6.0.1.5 version. You might try the 6.0.1.2 version here: http://forum.xda-developers.com/showthread.php?t=1640958&page=5
I ran into something similar when I tried installing CWM 6.x.x. I chickened out and decided to run CM10 from SD instead, and I'm so happy on the performance now that I do!
I did the "unbrick" thing with "repart.img" to get the Tablet back to "out of the box" state and sighed of relief when it worked!
Yeah, I was afraid of that. I really didn't wanna go through the process of unbricking, but I guess there's no help for it.
troy9829 said:
Have you tried holding on the power button and the "n" button as you boot? I recall running into a similar issue as yours and that was the only way I could get to recovery. If you're able to get into recovery that way I would consider maybe getting a different version fo CWM. I had trouble with the 6.0.1.5 version. You might try the 6.0.1.2 version here: http://forum.xda-developers.com/showthread.php?t=1640958&page=5
Click to expand...
Click to collapse
Power + 'n' doesn't work on my NT either, I have to turn the device off, insert the SD with CWM, then plug in the (still turned-off) NT to a wall charger and allow it to boot up that way - then (and only then) do I boot into recovery, and without touching any buttons. Hopefully that helps
Dang, whoever thought this would be such a booger of a deal?!?
Okay, first off, let me apologize for coming off like a noob, but it seems there's so much information out there that everything's kinda bleeding together, so let me tell you where I'm at.
I've unbricked and restored the NT to stock 1.4.2
I tried rooting, but the only root I can find that is flashable from SD is the 5.5 CWM which is older than the CWM 6.xxx that every CM10 version calls for. So I went ahead and did the root, so now I have a stock NT with root access. This is where I'm getting stuck...
I'm at this point...
http://forum.xda-developers.com/showthread.php?t=1640958&highlight=cwm+1+4+2
...and it apparently requires you to reboot into CWM in order to install CWM?!?
I've found the CWM 6+ files I think I need, but when I try to follow the instructions, my NT won't kick over into recovery---it keeps booting straight to the rooted 1.4.2 stock rom. I've found guides that take you from stock 1.4.3 to CM10, some that take you from 1.4.2 to root, and I even found Indirect's CM7 (without the instructions on how to get CWM on there in the first place!). I even downloaded Rom Manager and tried to boot into recovery that way, but it said there was my device wasn't supported.
I've been staring at this dang screen for three hours, trying to find a step by step, and I'm coming up empty. Maybe I'm just too frustrated at this point and need a breather.
What I need to know is how to install CWM 6+ on a NT that's either rooted or stock 1.4.2 (I still have the unbrick SD card) so that I can boot into CWM. From there, I can make my way through installing CM10. Help. Please. Am about to chew the lining out of my cheek.
I don't know if this might be helpful? http://forum.xda-developers.com/showthread.php?t=2037368
Sent from my NookColor using Tapatalk 2
Not yet. I was expecting OTA to kick in, updating my current 1.4.2 to 1.4.3, but it hasn't. Honestly starting to think my NT doesn't want to be rehacked LOL
Okay, so here's what I'm doing at the moment...
I'm at rooted stock. I moved CWM 6.0.1.2, CM10, and gapps over to internal SD.
I booted into recovery with an older version CWM SD card (SD card image with Win32 > turned off NT > insert SD > plug in USB to autoboot)
While in recovery (from SD), I flashed CWM 6.0.1.2 , CM10 (meghd00t), and gapps-jb-20121011.
I reboot...
WE HAVE JOY!
Now to check to see if the thing's gonna run right (got a whole lotta "XYZ has stopped" error messages upon boot up)
Dangit, keep getting those error messages about Gapps stopping and Google Play, and other stuff. Not allowing me to do hardly anything I need to. I can't even boot into recovery from the home page---it still loads straight to the Rom. In order to get into recovery, I need to use the SD that I made to get into recovery in the first place. Going to wipe dalvik and the other caches to see if that helps...
After wiping the caches, I boot into CM10 with no error messages. I DL'd a game from my Gmail account, and it appears to be working properly. Thanks for the suggestions and for letting me vent
I just went thru this similar ordeal too. It took me over 3 weeks to finally find a recovery & cm10 combo. What I found is that I couldn't get ANY version of twrp to act right. Indirect's flashing tool was invaluable. I finally used it to flash a cwm 6.x from Laverne's thread. It seems that not all versions of cwm 6.x are compatible with certain cm10 roms too & by chance I hit a combo that finally worked! I'm staying with what I got for a while!
Sent from my Nexus 7 using Tapatalk 2
So I got bored and decided to start messing with my old X2. It is rooted with Eclipse V2.3 ROM. All I did was change the theme a couple times. Worked perfect for the first two or three but then I found one that caught my eye.
This one here.
http://forum.xda-developers.com/showthread.php?t=1380719
It installed fine, liked the look, but had two problems right off the bat. First was that Eclipse Tools kept force closing so there was no way to get into bootstrap recovery. Second was when I pressed the power button, it would only reboot the phone, nothing else. So I decided to do a factory data reset on it to see if that would fix it...
It did the reset, but now it is stuck in the bootscreen. It gets past the red M, but that's it. Is it bricked or is there something I can do to get it back? I wouldn't mind doing a SBF and/or totally rerooting it again, but I need to find out how to do this while stuck in the boot screen with no way to get into recovery. Can anyone help me out?
if you are on eclipse 2.3, blue neon steel is for 1.3, not the version you are on. this is why youre having problems. 1.3 is based on 2.3.4, and 2.3 is based on 2.3.5 , so themes are not backwards compatable. or any compatable, it should be made specifically for your version of eclipse. ble neon is also my favorite theme, but an update for 2.3 seems unlikely, as i have tried to contact kevin about it before. everyone has moved on to other phones. a strong few still deal with this beast.
Well crap... Didn't even think about that. I have the other themes on my SD card, all I need to do is get into Bootstrap Recovery so that I can install the zip file. Is there a way to get into Bootstrap Recovery from a power off state?
ramthis9501 said:
Well crap... Didn't even think about that. I have the other themes on my SD card, all I need to do is get into Bootstrap Recovery so that I can install the zip file. Is there a way to get into Bootstrap Recovery from a power off state?
Click to expand...
Click to collapse
Try the Motorola system recovery by holding down volume down and power button. Wipe data and cache partition.
Did you ever install the bootstrap recovery? If so, try plugging in your charger with phone off to see if it will boot into bsr. Try this step first, then if that doesn't work try system recovery. If neither of these work you will more than likely need to sbf.
Sent from my Droid X2 using Tapatalk 2
Just plugged it in and it's stuck on the red M. I tried using stock recovery earlier and it didn't fix the problem either so hopefully SBF will be my rescue. Thanks for the help
give cm10 a try while youre on 2.3.4 :good:
Sorry I'm a noob at all of this. Successfully rooted my phone today thanks to Honsoon2000's excellent tutorial and toolkit. Then I went to install Android Revolution, which appeared to go successfully and then after I flashed the kernel the phone wouldn't load and just hangs at the quietly brilliant screen. I followed Honsoon's tutorial to the T (or so I thought) and everything went perfectly until right at the end when I flashed the kernel. I can make it back to the bootloader screen though it says "failed to load usb master mode". I can still make it into fastboot and recovery mode...tried recovery, and the process seemed to go sucessfully, but the phone still wouldn't load after...tried reinstalling ARHD-- it's still on the sd card and the install procedure still goes off without a hitch, but the phone still won't load. I've searched around and tried everything I can, to no avail. Any help would be muchly appreciated, and I apologize in advance for being a noob wasting people's time.
Edit: For example, when I follow the steps outlined in the FAQ it asks me to enter the command 'fastboot flash boot boot.img' , but when I do it says 'error: cannot load boot.img'.
Edit 2: So I put my boot.img file from Android Revolution into the data directory of the rooting toolkit and was able to complete the above flashboot command. I was also able to install the ROM off my SD card...however the phone still hangs on the Quietly Brilliant screen...I can't even power the phone down...whenever I try it just reboots...frustrating...really hoping someone can help me...cheers.
Before you begin, make sure that the drivers for the One X+ are installed.
Place the boot image being used on the computer's hard drive.
Boot in to recovery and flash the ROM.
When that is done, boot in to bootloader and connect the phone to the PC via a USB cable.
If the phone isn't in fastboot mode already, use the volume keys to highlight the word "fastboot", then press the power button.
Now, there should be text at the bootloader screen that says "Fastboot USB".
Finally, use the toolkit or command line and flash the kernel with the fastboot command.
This should successfully flash the ROM and the kernel. Make sure you full wipe before flashing a new ROM. If you can't seem to get the new ROM booting, the final choice is to relock the bootloader and run a RUU.
Which phone version you do own? International or AT&T / TELUS?
Did you flashed the correspondant boot.img? Did you cleared the cache? ( fastboot erase cache)
I'm trying to run an RUU but it keeps saying the battery isn't charged enough to flash anything...and this after it's been plugged in all day. Oh dear I think my phone might be done...really sucks :/
Also, it won't let me power the phone down-- every time i try it shuts the phone off briefly and then opens back up to the bootloader screen.
Fixed thanks to sarcasticphoenix. Cheers.
OK so I've tried 3 times to flash a new ROM onto my phone (Android Revolution twice and Eleganzia once) using Honsoon's toolkit...I've followed every instruction to the T as far as I can tell and all 3 times the process has gone perfectly right until the end when I flash the kernel...after that when I reboot the phone it just hangs at the Quietly Brilliant screen. I know how to relock the bootloader, flash the custom rom and get my phone back...but I really want to know what I'm doing wrong so I can install a custom ROM. I know I'm using the right ROM for my phone and am wondering what gives. Being driven crazy here...any ideas what's going wrong here would be helpful. BTW on the last attempt right after I finished and the phone hung I went into the boot loader and followed the instructions in the FAQ for fixing a bootloop...still nothing.
Edit: Solved my problem-- I managed to successfully load eleganzia...the only thing i did differently the last time was flash the kernel BEFORE installing the ROM off the SD card.
jrockwell said:
OK so I've tried 3 times to flash a new ROM onto my phone (Android Revolution twice and Eleganzia once) using Honsoon's toolkit...I've followed every instruction to the T as far as I can tell and all 3 times the process has gone perfectly right until the end when I flash the kernel...after that when I reboot the phone it just hangs at the Quietly Brilliant screen. I know how to relock the bootloader, flash the custom rom and get my phone back...but I really want to know what I'm doing wrong so I can install a custom ROM. I know I'm using the right ROM for my phone and am wondering what gives. Being driven crazy here...any ideas what's going wrong here would be helpful. BTW on the last attempt right after I finished and the phone hung I went into the boot loader and followed the instructions in the FAQ for fixing a bootloop...still nothing.
Edit: Solved my problem-- I managed to successfully load eleganzia...the only thing i did differently the last time was flash the kernel BEFORE installing the ROM off the SD card.
Click to expand...
Click to collapse
That's usually what I do first, flash the kernel and then install the zip via recovery
Sent from my HTC One X+ using xda premium
Which kernel are you referring too? Actually there is one or two kernels available but only for the International version, not the AT&T/TELUS which you seem to have.
I strongly suspect that your boot looping was because you didn't flash the boot.img file correctly or not at all. And you don't seem to install the good ROM version for your phone.
Elegancia has two ROM versions one for International and one for AT&T/TELUS users.
ARHD is for International users.
Please read Q12 of the FAQ.
Lucky Thirteen said:
ARHD is for International users.
Click to expand...
Click to collapse
Lol...yeah I don`t know how I missed that. I ended up getting elegancia successfully flashed and loaded so all is well. In retrospect this was a good experience because there`s nothing like having to get yourself unforked from a bad situation to gain an understanding of what`s going on. Cheers.
I have a couple questions and since I`m not allowed to post yet in the elegancia thread I'll try in this thread first:
1) An elegancia question: Is there a way (widget) to toggle data roaming on and off in this ROM?
2) Is there a way to tweak settings (transparent pull down, selection of launcher etc.) without wiping and reflashing the ROM?
3) What are people's favorite launcher for that ROM? I tried Atom but it was just a guess because I hadn't heard of any of them. I like it so far but am curious about the others.