Related
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.
I am a relative noob at flashing roms and rooting phones, but last night I ran into an issue. My phone was having all sorts of problems so I was going to put it back to factory, then start from scratch. I then decided to just flash a different rom. here is what happened.
I deleted SuperSU - this was done as part of the process to unroot and put back to factory, after this step I decided to flash a different rom
Put new ROM on phones internal memory as well as SD card
Wipe data
wipe cache and delvic cache
install new rom
Black screen
In an attempt to unbrick I relocked my bootloader.
Now, my phone can power on (Give white screen and HTC logo), then go black, and I can access Recovery mode. That is all.
I have plugged the phone to my computer and tried running the RUU, but the RUU will not recognize the phone.
I am not sure what to do to unbrick my phone and get it working again. Any and all help would be most appreciated!
Sorry I can't be more eloquent with my words, but I'm at work. I will be responding throughout the day, though.
thanks again so much to anyone that can help!
Try running it straight from bootloader
I loaded into Bootloader, selected Fastboot(USB), ran the .exe and it still won't recognize the phone. However, I did get recovery unlocked again. So I can get into recovery mode, flash all the ROMs I want, mount and unmount, yet still everytime I flash a new ROM it still boots to a black screen. Am I doing this right?
Try a Rom with kernel installer
Thanks! Since I am still a little new could you tell me how I would spot a ROM with kernel installer or could you point me to any one that could work? From then, it's the same process as flashing any other ROM? Do I need to do something with the kernel?
Meanbean and stock with goodies are the 2 that I'm certain of. Meanbean needs to be flashed twice the first time
Thanks so much for your help, I will post my results soon!
Failed
Here's what it says. Sorry for the blurry picture. I followed directions closely.
What version of recovery are you using? You may need to update it. Assuming you have a pc, try mounting the internal memory to pc through twrp. Windows will automatically tell you to format if its damaged
2.1 Updating now
omg it finally worked! Updated TWRP using fastboot and flashed MeanBean. Thank you so much!!!
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.
Hello,
I have an S-on 4g LTE unlocked with bootloader and running Viper 2.2. I've been getting those annoying update messages, so I thought I'd try a different ROM. I tried to switch to the Avatar ROM on the forums: http://forum.xda-developers.com/showthread.php?t=2207395, but I couldn't get it to take. I read somewhere that I needed to extract and load the boot.img file through ADB first, so I did that but it still didn't take. I could install the ROM, but I can't get it to boot past the "HTC: This build is for development purposes only" screen. It hangs there for a while, then the screen goes black, and eventually it loops back.
So then I decided to just go back to Viper 2.2, but that won't take. It's doing the same loop-back. I did a full backup before starting, so I tried restoring that but it made no difference. I thought maybe I needed to do the adb boot.img thing again using the boot.img file from the viper 2.2 file, but there's no boot.img in any of the viper files I have. So I tried looking on the forums, but all the boot.img file links I found were expired/dead/long gone.
So I need some help in figuring out how to get this phone back. I can get it out of the bootloop by pulling the battery and then do hboot via the downvolume + power button, and then I can get into teamwin recovery from there. But after that, I don't know what to do. Any advice/help to get back on my feet would be greatly appreciated!
Nevermind...got it! I tried installing the stock kernel from here http://forum.xda-developers.com/showthread.php?t=1770978 and it booted back up finally.
I kind of thought that's what I needed to do, but I was at the point where I didn't want to keep touching (or more like breaking!) more stuff until I knew what to do. Thanks anyway!