Hey guys,
ok, so I flashed an incorrect radio onto my phone (i think) I was running CM7 and flashed a new radio to try and fix the GPS and now it's stuck on the white HTC screen. I cannot boot into recovery because all I get is Hboot and no option to run a restore.
I put the SD card into another phone and downloaded the correct radio, rebooted to recovery and ran the update, but it still gets stuck on the white HTC screen.
Im in a bit of a panic here please can someone help me.
Sorry I know im not the first guy whos done this and im sure you gusy get sick of people asking for help but im really desperate here.
Many thanks,
Adam
We have all had that feeling ^^
Do this:
1. - Open the back cover
2. - Remove the SD Card
3. - Pull the battery out for 5 secs and put it back in
4. - Put the cover back on
5. - Press Vol Down and Power at the same time. Keep holding on Vol Down till you get in bootloader
6. - Select Recovery
7. - Wipe Cache
8. - Put your SD Card back in
9. - Reboot phone and its all working again. Yey.
It was in the thread
Thanks for the quick reply, I'll give that a shot and see how I get on, really appreciate the support.
Adam
flashing radio
I wouldn't have flashed a radio unless I absolutely had to if you can boot into recovery and you have a backup of your original radio and do a full wipe and do a clean install if you still have all your zip files in recovery see this why the dev's tell you don't mess with the radio your going to have this pushed from a pc good luck
There's nothing wrong with flashing a radio. It's a very simple procedure and shouldn't cause any problems if done properly.
Hey guys,
Just to let you know popping the SD card let me get into recovery and fix the problem.
As you can see from my sig it's been a loooong time since I played around with Android and I probably mis-read (didn't read) something.
You have my very humble thanks.
Thanks TheStigx! Really helped, I was freaking for a minute there
nichos said:
Thanks TheStigx! Really helped, I was freaking for a minute there
Click to expand...
Click to collapse
does anyone know exactly why sometimes flashing a radio does this? is it cause they didnt clear cache? im jus wondering so i can avoid this issue alll togetherrr
i tried the instructions in post#2 and it worked, thanks so much i was freaking out too lol. just goes to show how little i know. just an edit though, i had to pull my sd car out, boot into the bootloader, then install the sd card back in and reboot into recovery, then i got a bunch of errors about mounting so i ignored that and then just did the wipe cash and rebooted. then it came back to life! i thank you guys
Related
Hi all,
I have a Magic 32b and recently put the Modaco_custom_1_51 rom on, with the Amon Ra's recovery image (as recommended on unlockr)
It was working ok, not great, a bit slow and mms wouldnt work, so...
I decided to change the rom, unfortunately I was in a bit of a rush and I kind of forgot what I was doing...
I went straight to the Recovery mode and clicked 'part sd: fat32+ext2+swap'
Then I put the new rom on using usb storage mode, I clicked on applied update.zip and of course it wouldnt work (all without applying any recovery image when the phone was working and wiping first), I rebooted the phone and now after the vodafone image I just get a blank black screen...
I then woke up and realised what i'd done.
I have tried searching what to do when this happens but I couldnt find anything... I've never used abd or commands and dont really know how the commands work... I just flashed and applied the rom using the 'one click' method on unlockr.
I dont think its bricked... I can boot in Recovery and fastboot...
I would appreciate any help you can give, theres propably a simple way to do it (well simple for you guys) but I just cant work it out, if anyone can give me some instructions it would be really grateful.
Im new here so take it easy on me
I got no reply when I asked before so I'd really like someone to help
Regards
Gino
this happend to me
okay the process is to,
1. put something else on ur sdcard
2. Right click on ur computer Icon. once inside click on ur SdCard rout. which is or i can be j,k,l,m,p what ever yours is then
3. right click put saftly remove. once done that click on Storage off on ur Ra' Recovery
4. Then Click reboot, and press home button once ur screen goes black. u'll go back to ur recovery Images and u should have the things there, and if u dont then u know what that means ur SD card is fried.
Thanks for the reply...
This is what I done..
(Remember I cant get into the phone to do anything)
-Booted phone into recovery
-Wiped data
-Part sd card fat32+ext2+swap
-Took sd card out, put new rom on
-Put sd card back in
-Wiped again for safety
-Applied update.zip
-Rebooted phone and then...
Went past vodafone screen and stuck on Black screen again....
What am I doing wrong?
Someone must know
Thanks
What rom are you trying to flash? Have you tried any other roms? Are you sure it's actually flashing your new rom?
Thanks again for the reply... I think the problem was the rom. I tried the new Evil Hero rom -3s final... but it seems pretty slow for me.
Do I have to increase swappiness or anything... I dont know how to do that or even check it?
Thanks
Anyone have any idea why its so slow?
Gino_x said:
Anyone have any idea why its so slow?
Click to expand...
Click to collapse
How big is your swap partition? Most hero roms seem to require a lot of swap (96Mb+) and that will need to be configured either in swapper (app from market) of by editing user.conf if the rom has one.
Hey guys I really need your help, my phone has been down for the past 3 days now. I followed this guide:http://forum.xda-developers.com/showthread.php?t=547133&page=2. I will state that I am new to the forum so I cannot post on the actual how to, due to rules, or I would have. Basically i have made it all the way thru the guide, to the point where it tells me to:
- press MENU to power off! (do not reboot)
- hold HOME and POWER to boot into recovery mode
- apply update
once I reach there I have no way of resetting the phone so I just pulled battery after it said the cyanogenmod was installed from sdcard. I flashed the splash.nb, but now all that happens is my phone loads up the MyTouch 3g screen freezes for a few min then restarts and goes back into Android System Recovery screen. I really need your help and would be forever great-full if someone could lend me a hand. I will check back regularly.
Thank you very much ahead of time for whoever lends me a hand.
Troubled Guy With Non Working Phone
OP here
Come on guys someone has to have had this problem before. Even if you are sending me to another link who has dealt with this before it will still be a help.
First of all, I'm not familiar with your phone. But I will try to give you a few ideas and see if any of it works for you.
If you have a recovery installed and you have flashed Cyanogenmod, then you are rooted. I'm not sure how your recovery works, but you should have to use the volume buttons & power button to navigate recovery - or something similar. If you can get into recovery, you should be fine.
Go to the wipe menu and wipe cache/dalvik cache. If these weren't wiped properly before flashing, this could be the culprit. There should be an option to reboot, you may have to choose go back a couple times to find it. If that doesn't work, try flashing a different rom. You'll need to wipe everything in recovery (except the SD card) first, then choose "flash zip from SD card".
If your battery is almost dead, don't try flashing anything, just wipe. You'll need to get an external charger or a full battery before flashing anything.
Again, I don't know how your phone works, I have an Evo & pretty much just treated your post as such. It's a start, though. If you can give me more info, I can try to help further.
I also just noticed this is an old method for an old version of the phone. You do have the phone this was made for, correct? Have you tried sending a pm to the OP?
There is most likely an easier, newer way to root, but what's done is done. It also seems like it may be using Amon Ra recovery? If that's the case, that's the recovery I use so I can help you out there. You may also want to look at how to unroot and get your phone back to stock, then start over. I'm going in to work, but if you post back I'll try to help you out as soon as I get the chance.
Hey guys I was having some problems with my xoom's wifi on Tiamat's 1.4.4 so i decided to relock the device and use stock.
It's a US model and had build HMJ37 but i decided to follow this thread
http://www.xoomforums.com/forum/mot...4600-thinking-about-unrooting-read-first.html
I downloaded img build HRI66 and followed all the steps and it was ok. Then, i rebooted and now my device is at the motorola logo's dual core screen. Everytime i manually reboot with power and volume up it automatically reboots the device instead of shutting it down, it literally won't shut down and keeps hanging at the moto logo. It just keeps rebooting and getting stuck at the motorola logo. I then unlocked again, and performed the same process with the HRI39 img and still got the same problem
So im stuck. Please help me out guys, i'm in serious ****.
So you have gone as far as the "fastboot erase cache" and "fastboot oem lock" right? This is kind of funny because I tried to install Tiamat 1.1 ROM tonight and ended up going through this HUGE loop of problems.
Here's the problem I had: some time ago I installed ROMManager from the market. I thought it would be easier. It SHOULD be easier. I let it update my recovery to its own version 4.something. It allowed me to SORT OF install the ROM, but I wound up with some persistent system files that weren't getting wiped and a bcm4329.ko version mismatch.
This stumped me for a long time because all I could see was an "Error" message where I was supposed to be able to toggle the wifi on and off. I tried rolling back to my previous ROM. No go. And the culprit the whole time was ROMManager's CWM.
I tried rolling back my recovery.img file to the Tiamat version recommended in this forum. I kept getting all of these crazy "could not mount" errors for pretty much EVERYTHING. I thought my recovery partition was effed. So I rolled back to stock. Followed pretty much the same instructions you linked to.
From there I was able to boot into the stock OS. WiFi worked. I breathed deeply for a minute or two then dove right back in.
If I was in your position I would (and I did, though not from a boot loop) boot into fastboot and unlock the bootloader again. You can do it by holding the Vol down key as the device boots. When fastboot loads type "fastboot oem unlock". Press the Vol down key then the Vol up key. Do that again. Your device is unlocked now! Hooray!
Now you need to install a recovery.img. (I just did this too.) Get the .img file here: http://forum.xda-developers.com/showthread.php?t=1074979
Boot into fastboot again. Put the recovery img file you downloaded into the same directory as your adb and fastboot executables (if you haven't already linked to them in your PATH). Type "fastboot flash recovery recovery-lotsofstuffhere.img". Type "fastboot reboot". 2 seconds after the Motorola logo pops up press the Vol Down key. Then press the Vol Up key to enter recovery.
Ok, here's where I found out what a dumbass I was. I got all of the stupid "can't mount anything" errors again. I thought, HOLY ****. I just did all of that work, spent hours troubleshooting and reformatting and bringing it back to stock and flashing the custom recovery all over again just to run into the SAME error. I really thought I was screwed. Then I found some forum where a guy was complaining about the same error. He realized he was getting it because his sd card was half-way out. I thought - "SD CARD?!?" Some guys told me I needed one earlier too, but the ROMManager CWM didn't require it. It just screwed up my system files. So I popped one in and rebooted. Voila. Everything's kosher. If YOU have the same problem, make sure you've got an SD card in.
Ok, so now you're in recovery. You'll need to flash an OS of course. If you haven't already got it, get Tiamat 1.1 rom. Put it on the sd card. Wipe data/factory reset. Install zip from sd card. You're golden. At least I was. 5 hours later.
-Mike
Hey Mike I'm gonna give this a go. Just when i downloaded the img file to flash through fastboot i got an error saying battery was too lower to perform the recovery....damn it! The xoom isn't able to charge at the moment so i have to wait until it dies i guess (or i hope at least) and then charge it up and try again later.
Thanks again dude, hope i sort this out too. I'll download tiamat 1.1 in the meantime.
DUDE YOU'RE MY ****ING HERO!!!! I got it running can't say if everything is 100% just yet but the fac tthat im back in is enough to thank you so very much Mike!!! What a guy!
It worked? Great that's excellent news. Just out of curiosity - did you get there because you had ROMManager's ClockWorkMod? Or maybe you didn't do a full wipe before flashing a new rom? Or maybe you restored some WiFi settings with Titanium Backup after a new flash? How did you wind up with tthe problem in the first place - you know, for posterity.
well to be honest i am not 100% sure. I think the source of the problem msut have come from my previous installation of tiamat's 1.4.4 rom, it was always actin up on me and i don't believe i wiped the mod before i updated it and that may have done it. I wish i could give you more than just a pseudo answer.
DeeJayCruiser said:
Hey Mike I'm gonna give this a go. Just when i downloaded the img file to flash through fastboot i got an error saying battery was too lower to perform the recovery....damn it! The xoom isn't able to charge at the moment so i have to wait until it dies i guess (or i hope at least) and then charge it up and try again later.
Thanks again dude, hope i sort this out too. I'll download tiamat 1.1 in the meantime.
Click to expand...
Click to collapse
This is why they say to make sure you're plugged in when doing this important stuff, lol.
okantomi said:
This is why they say to make sure you're plugged in when doing this important stuff, lol.
Click to expand...
Click to collapse
Normally, I'd agree but in this rare case, he actually needed it to fully drain because he couldn't get it to power off using any normal method. Weird! so, it seems his only shot was to let it die to finally kill the screen and then start over. Very odd...
From original post
DeeJayCruiser said:
Everytime i manually reboot with power and volume up it automatically reboots the device instead of shutting it down, it literally won't shut down and keeps hanging at the moto logo.
Click to expand...
Click to collapse
farmsatguy said:
Normally, I'd agree but in this rare case, he actually needed it to fully drain because he couldn't get it to power off using any normal method. Weird! so, it seems his only shot was to let it die to finally kill the screen and then start over. Very odd...
From original post
Click to expand...
Click to collapse
You are right...I had forgotten that from the OP. Very strange indeed.
Yeah I dunno why, my xoom was just acting up. It's fantastic now, albeit the wifi still has a couple kinks but android market issues have been resolved, i get much better streams and with tiamat 1.1 everything is already built in and with a quickboot option =)
Xda...where would i be without you!
farmsatguy said:
Normally, I'd agree but in this rare case, he actually needed it to fully drain because he couldn't get it to power off using any normal method. Weird! so, it seems his only shot was to let it die to finally kill the screen and then start over. Very odd...
From original post
Click to expand...
Click to collapse
You should be able to reboot the device using vol up + power, then holding vol down and vol up until it says "Cold booting Linux.....".
This should do the same as letting the battery drain, plugging it in and turning it on.
DeeJay - dunno if you've done this already, but if you haven't you should go back to the Tiamat 1.1 thread and find the Modpack. It fixes the Market update issue and gives you built-in screenshot capabilities and an option to reboot into recovery from the power off menu. It's in there - you just have to scroll down a bit before you find it.
Also - what issues are you having with WiFi?
Thanks for that important tidbit, solarnz. I'm going to file it away for future use.
OMG!!!! Dude you just saved my life! I thought my baby was out the window. I had the exact same problem as you did. I was trying everything from every thread that had anything to do with this problem. I just finished installing and it booted. WHEWWW!!!
Thank u thank u thank u!!
Glad it helped. I'm seeing all kinds of posts in here about the ROMManager CWM. Not good.
Sent from my Xoom using Tapatalk
Ok be prepared, this post may be rather long winded however I will try my best to prevent that. I have a Tmobile G2x I purchased on launch date. Ive not attempted to Root, change roms, or anything of the sort. (as much as I always wanted to, I always felt that my skills were not good enough to attempt these ideas no matter how easy they may seem. I just did not want to be the cause of screwing up my phone that I paid dearly for)
So I have a friend who claims to be the master (of disaster so it turns out) of rooting androids and such. He stops by my house just to hang out and eventualy convinces me to let him root my phone and install CM7. Within a few minutes the phone was rooted (super1click) and was running CM7 release candidate. (I really dont know what all these things truly are but I drilled him for answers once he jacked up my phone and left me with a half-bricked phone) So he installed Rom manager and convinced me to upgrade to the premium version via marketplace so I did. He was then showing me how easy it was to flash new roms at the touch of a few buttons. He put on some other rom which looked like CM7 but claimed to have extra tweaks. It worked fine. A few minutes later he put on some Faux Rom which gave a boot up screen like my old Nexus One did. (Multicolored X) It seemed to work fine as well. Then he said lets check out the nightly CM7 Rom so he put it on. (however I dont think it ever actually put CM7 back on.-still on Faux?) Thats when things got crazy.
Now I get the com.google.process.gapps force close message all the time. He tried to fix it for 4 hours and finally gave up. Here is what I know he/we tried: After searching the internet for hours we tried everyone elses ideas. Clearing calenders cashes, un syncing, etc. We did about 40 factory resets. We have tried to install my backup (which was from BEFORE he even touched my phone) and upon holding both volume rockers and plugging in USB (no battery installed) and it still does nothing. Windows recognizes device but phone screen stays black. Tried Debug mode while doing this as well. If we hold the volume down button and power the little install bar comes on the screen and it does its thing (whatever that is) and goes right back to the way it was. I keep getting the gapps message all the time. After factory reset I cant even type in my gmail address to start the initial setup of the phone. The force close keeps cutting me off. If I type fast, I can sync the account but I cant use market whatsoever. Tried installing Rom manager to re-flash but just sticks at starting download and gapps pops up again.
My son is starting school tomorrow and he has a medical condition. I NEED this phone to communicate with the school nurse via emails and such. As of now I can only text, call, or surf web all while dodging force closes. If ANYONE out there can please help me get my phone back to normal Id greatly appreciate it. Im sure its something easy but as I said before, Im not good at this thing and thats why I never attempted it myself. Your welcome to submit answers here or PM me your phone # if you want to walk me through it on the phone. (I have a landline phone to talk to you on) Thanks in advance for everyones time and Im sorry this ended up being so long.
Download latest Gapps.zip from Cyanogen site to your phone's SD card, boot into recovery, wipe data and cache then flash the Gapps.zip file. Let me know if this helps.
I will try this now. Thank you
Im unable to get anywhere. It still has stock recovery and I cannot get to the screen where I can wipe. Im not great at this sort of thing but Im trying.
Omnichron said:
Download latest Gapps.zip from Cyanogen site to your phone's SD card, boot into recovery, wipe data and cache then flash the Gapps.zip file. Let me know if this helps.
Click to expand...
Click to collapse
i think you would be better off starting from scratch
1. remove your sd card from your phone and plug it in your computer
2. download the latest rom here
3. download gapps from the download links at the bottom of this page
4. transfer both files onto the sd card and put it back into your phone.
5. with your phone off, boot your phone into recovery by holding vol down+power
6. wipe data, cache, and dalvik cache
7. flash only the cm7 file
8. reboot normally
9. reboot into recovery
10. flash gapps
11. reboot normally
after you flash one file, it is highly recommended that you reboot before you flash another file (if your friend didnt do this, this may have been the problem)
HurtsBad said:
Im unable to get anywhere. It still has stock recovery and I cannot get to the screen where I can wipe. Im not great at this sort of thing but Im trying.
Click to expand...
Click to collapse
to flash custom recovery, use this (method two on the page)
EDIT: original post (http://forum.xda-developers.com/showthread.php?t=1056847)
Thank you guys for all your help. The instructions helped me out. Im very thankful. I can now rest better knowing that my sons school nurse can contact me if needed. Have a great night.
no more force closes? sounds good
feel free to post again if you have any more problems
sweetnsour said:
i think you would be better off starting from scratch
1. remove your sd card from your phone and plug it in your computer
2. download the latest rom here
3. download gapps from the download links at the bottom of this page
4. transfer both files onto the sd card and put it back into your phone.
5. with your phone off, boot your phone into recovery by holding vol down+power
6. wipe data, cache, and dalvik cache
7. flash only the cm7 file
8. reboot normally
9. reboot into recovery
10. flash gapps
11. reboot normally
after you flash one file, it is highly recommended that you reboot before you flash another file (if your friend didnt do this, this may have been the problem)
Click to expand...
Click to collapse
....touché
hello all,
I am new here and I have been searching the forums for a few days as well as the internet but I could not seem to find one that had my same problem, but if there is can you please direct me to it and apologies for that.
I was installing a new rom, the Blackout ICS Incredible v3.0.0 FULLY WORKING!!! [4.0.4][Sense 3.6], onto my inspire i did a full wipe using FULL_WIPE_1.5_EXT4_.zip and I cleared the caches. the install i thought went well because it went to 100% and i even chose what kind of background i could as well as choosing to over clock my processor. The phone the restarted after all of that and it went to the htc screen then faded to black, after about ten minutes of it being black screen i pulled out the battery.
Now when i try to recover it it wont go into hboot and it just goes to the htc white screen then it quickly fades to a black screen and stays like that.
so my question to you all is a Jtag the only way i can save my phone or is there something else i can do?
http://forum.xda-developers.com/showthread.php?p=30480411
Sent from a dream.
Teichopsia said:
http://forum.xda-developers.com/showthread.php?p=30480411
Sent from a dream.
Click to expand...
Click to collapse
Im sorry but I dont understand. I cannot enter hboot no mater what i do and don't you need to enter hboot to reflash it?
True, but I'm hoping you are doing something wrong.
Pull battery, wait a few minutes, place back in. Press and hold Volume down, then power button. Does it go into hboot? If not.
Read this.
http://forum.xda-developers.com/showthread.php?p=20382502
Edit: you are the first report with that issue after trying to flash that rom. My bet (that is, if you are new), you are not doing something wrong.
2nd edit: if you are new, then read the guide in post#7
http://forum.xda-developers.com/showthread.php?p=30007255
Sent from a dream.
Teichopsia said:
True, but I'm hoping you are doing something wrong.
Pull battery, wait a few minutes, place back in. Press and hold Volume down, then power button. Does it go into hboot? If not.
Read this.
http://forum.xda-developers.com/showthread.php?p=20382502
Edit: you are the first report with that issue after trying to flash that rom. My bet (that is, if you are new), you are not doing something wrong.
.
Click to expand...
Click to collapse
I really appreciate the help Teichopsia , but I've tried the power /volume - method many times and it still wont go to hboot. if it helps this is the 5 time i have have flashed a rom on my phone (and it is rooted) and yes sadly i had to be the first person to be unlucky enough to get my phone bricked from the blackout rom :crying:
i think i could get out of this mess if i could only get into hboot.
reading the method you linked to me will it work if i cant even get to the hboot screen? my phone only stays of the white htc logo screen for about 3 seconds then it goes to a lit black screen
on a side note should i report what happened to team blackout to see if they have any soloutions?
The only thing I can think of is trying to get into hboot without the sd card and sim card.
The rest is beyond my knowledge.
You'll need to wait for someone more knowledgable than myself to help you.
Remember, first press and hold the volume down button, while holding that down press the power button. Do not release either button till it shows the hboot. If that doesn't work, pull the battery for five minutes and try again. If you did this part exactly like that, then you can skip it.
Well, you already posyed your issue here, just wait for someone to help you. Glevitan is bound to show up sooner or later.
Sent from a dream.
I would see if you can send commands to it from adb while its in the blacked out state. adb is pretty easy to use and can be found easy online. if you get it installed type "adb devices", if it recognizes your device type "adb reboot bootloader" or "adb reboot recovery".
Novius vi said:
hello all,
I am new here and I have been searching the forums for a few days as well as the internet but I could not seem to find one that had my same problem, but if there is can you please direct me to it and apologies for that.
I was installing a new rom, the Blackout ICS Incredible v3.0.0 FULLY WORKING!!! [4.0.4][Sense 3.6], onto my inspire i did a full wipe using FULL_WIPE_1.5_EXT4_.zip and I cleared the caches. the install i thought went well because it went to 100% and i even chose what kind of background i could as well as choosing to over clock my processor. The phone the restarted after all of that and it went to the htc screen then faded to black, after about ten minutes of it being black screen i pulled out the battery.
Now when i try to recover it it wont go into hboot and it just goes to the htc white screen then it quickly fades to a black screen and stays like that.
so my question to you all is a Jtag the only way i can save my phone or is there something else i can do?
Click to expand...
Click to collapse
i also have the same problem. i'm using a DHD. and to add to that, my volume rocker is broken. i wonder why the warning not to select reboot immediately after installation wasnt part of the download as a readme or something. i may have just lost a perfectly good phone as a result
I can confirm as a third user and one knowledgable in flashing roms that the ICS blackout does the same thing to my phone. I can also confirm that pulling the battery and then trying hboot just results in the white htc screen instead of just popping up hboot. I was able to boot into recovery from the white htc screen by using adb and doing the "adb reboot recovery" command. I am able to restore my backup just fine so you guys will be able to fix it. it must just have a bad boot image for the version of hboot that we have installed.
Gizmoe said:
I can confirm as a third user and one knowledgable in flashing roms that the ICS blackout does the same thing to my phone. I can also confirm that pulling the battery and then trying hboot just results in the white htc screen instead of just popping up hboot. I was able to boot into recovery from the white htc screen by using adb and doing the "adb reboot recovery" command. I am able to restore my backup just fine so you guys will be able to fix it. it must just have a bad boot image for the version of hboot that we have installed.
Click to expand...
Click to collapse
Im sorry but this is the first time i have ever done something like that can you give me a step by step instruction how to do it or a link that says how, i dont want to sound lazy but I scared to mess up my phone even more
Use this guide its very easy. if you have already used your phone on your pc and the drivers are installed all you need to do is download the easyadb and follow the instrucions to where is says to type adb.exe. once it is started just type adb devices to make sure it sees your device and then adb reboot recovery
Ignore the fact the instructions are written for a xoom as it will work for any android device with the drivers already installed, which they should be from rooting, syncing and all the other stuff you have probably already done on pc.
UPDATE: I reinstalled ICS blackout but instead of wiping myself i just let aroma installer do it and everything went fine this time. I noticed the aroma installer reformats everything to ext4. its not mentioned in the op as a requirement but seems thats the case. Hboot version has nothing to do with it like i previously commented. It really is a cool rom with both ics and sense. I have only tried the sense version so far
Hope this helps?
Novius vi said:
Im sorry but this is the first time i have ever done something like that can you give me a step by step instruction how to do it or a link that says how, i dont want to sound lazy but I scared to mess up my phone even more
Click to expand...
Click to collapse
Just in case-- to get into recovery you must press and hold the volume down for a few seconds and then hold the power button. Do not do press them both at the same time. I realize you wrote that your volume rocker seems or is broken but I wrote above just in case-- when I first tried to root my phone, I was pushing them both at first and thought my rocker was broken....
Since you rooted the phone originally-- not sure how you did it. But if you go to this link you can download recovery flash. Read the "readme" file:
http://forum.xda-developers.com/showpost.php?p=29208930&postcount=10
Assuming you can get into recovery-- then reload the blackout ROM but you MUST let the aroma installer wipe and format do not use any other wipe/format tool. Then do NOT press the "FINISH" button-- instead press the back arrow-- you want to go back to flash recovery and reboot from there. If you press finish (like I did multiple times, the phone will just lockup).
Best of luck!
Three of us confirmed that hboot was inaccessible even after battery pull. I am no stranger to this device as well. The only fix was using adb reboot. Also if you actually reformat your partitions to ext4 before install, then aroma will install correctly. It's just not mounting anything if it's still in ext3 format. Definitely better to just do the full wipe within aroma though. I do agree with not hitting restart from aroma but someone already mentioned that a few posts up.
Thank you thank you thank you
After putting it into abd it recognized it and then i was able to put it into hboot. Im not out of the woods yet, but after not being to see hboot in so long, well its just amazing to see it again
ok now its in hboot it gives me 4 choices
bootloader
Reboot
Reboot Bootloader
power down
apologies again but just for reassurance which one should i select?
THANK YOU GUYS for getting me this far!!!
special thanks to Gizmoe for suggesting the adb route
Novius vi said:
After putting it into abd it recognized it and then i was able to put it into hboot. Im not out of the woods yet, but after not being to see hboot in so long, well its just amazing to see it again
ok now its in hboot it gives me 4 choices
bootloader
Reboot
Reboot Bootloader
power down
apologies again but just for reassurance which one should i select?
THANK YOU GUYS for getting me this far!!!
special thanks to Gizmoe for suggesting the adb route
Click to expand...
Click to collapse
Select bootloader to get to recovery option.
1shukla said:
Just in case-- to get into recovery you must press and hold the volume down for a few seconds and then hold the power
Assuming you can get into recovery-- then reload the blackout ROM but you MUST let the aroma installer wipe and format do not use any other wipe/format tool. Then do NOT press the "FINISH" button-- instead press the back arrow-- you want to go back to flash recovery and reboot from there. If you press finish (like I did multiple times, the phone will just lockup).
Best of luck!
Click to expand...
Click to collapse
I did exactly as you said I pressed finished and it asked if i wanted to reboot i said no. then it sent me back to recovery mode crossing my fingers hoping to see that it works:fingers-crossed:
Now, just manually reboot.
Sent from a dream.
You saved my phone!!
Thank you guys sooo much this Rom is great once I got past that minor issue
My phones working better than ever I even oced it a little bit
Again I am eternally grateful to you guys and team black out for this great Rom!