Database Info

Flashed CM6 RC2, can't boot into recovery PLZ HELP!!!

Okay I just recently Flashed CM6 Rc2, Everything was working fine. Then I noticed the Market started FC every time I tried to load it. I can't get it to open at all anymore. So I figured I would wipe and reflash, but I when I reboot and hold down HOME AND POWER it just stays stuck on the TMobile G1 Splash screen. But if I pull the battery out and put it back in, I can start up the phone again. Everything else works pretty good besides random things at times. Every now and then it will randomly restart. Also, I tried to factory wipe through the settings, and it just rebooted and then stuck on the G1 screen again.
Can anyone PLEASE help??

Try ADB? Or through the terminal? CMD, lol. I had the same problem with market, so i got tired of it. And flashed Cannon Complete Eclair, It works better than Froyo, and they aren't that much different.

Try using fastboot in the bootloader. That happened to me a couple of times with the Clockwork rom manager and going between roms.
1) Download another copy of the recovery img
2) Rename it something simple like recovery.img
3) boot into the bootloader (Camera + Power)
4) open a command prompt navigate to the directory that you have the image in
5) run this command without the quotes "fastboot flash recovery recovery.img" (if you didn't name it recovery.img then substitute the name you chose)
Hopefully that works for you.
**If you don't have the sdk tools files (adb.exe..., fastboot.exe) copied into your /system32 folder like I do then you will need to put the new copy of your recovery.img into the sdk tools folder and navigate there in the command prompt, coping them into the /system32 folder lets use them regardless of the directory that you are workin.

I had a similar problem like this a few days ago where I couldn't load up my recovery so I used the method similar to the post above me. After searching for just trying stuff I was able to learn how to use adb on my own (where was ya post when i needed it roadmasta01 lol)
But I think I did almost he same steps he took except I loaded into fastboot by holding the back button and the power button and I erased the old recovery before flashing the recovery again.(fastboot recovery erase)

I too used a similar process Roadmasta01 and biglo used. I had a buddy that had the exact same problem today. His G1 was progressively getting worse ... pretty soon everything would FC and he couldnt get it to the boot loader and then it just wouldnt boot past teh G1 logo.
Booted the G1 into fastboot
downloaded the latest clockwork recovery image from koush's site and saved it to the folder location adb and fastboot are located in the sdk.
fastboot erase recovery
fastboot flash recovery <recovery you downloaded.img>
rebooted and al was well again.

biglo said:
I had a similar problem like this a few days ago where I couldn't load up my recovery so I used the method similar to the post above me. After searching for just trying stuff I was able to learn how to use adb on my own (where was ya post when i needed it roadmasta01 lol)
But I think I did almost he same steps he took except I loaded into fastboot by holding the back button and the power button and I erased the old recovery before flashing the recovery again.(fastboot recovery erase)
Click to expand...
Click to collapse
Sorry homie, just happened to see this thread. Besides I still consider myself a novice at this stuff, I am usually able to pull my butt out of the fire; Except for when I took my phone completely apart to replace the housing and android.process.acore started to FCing whenever I tried to call somebody or received a call. That was frustrating as all get out, everything but the actual phone worked on my phone. On top of that I tore the ribbon for the digitizer when I replaced my housing so when I tried wiping and flashing a different ROM to try to fix it, I could do the whole "touch the android to start" thing. I eventually fixed the FC issue by flashing the dreaimg.nbh file and just starting over from scratch. ezterry helped me with that issue and he was very patient. I realize you didn't ask and you were joking, but I starting into a background ramble and I had to finish it.

Roadmasta01 said:
Sorry homie, just happened to see this thread. Besides I still consider myself a novice at this stuff, I am usually able to pull my butt out of the fire; Except for when I took my phone completely apart to replace the housing and android.process.acore started to FCing whenever I tried to call somebody or received a call. That was frustrating as all get out, everything but the actual phone worked on my phone. On top of that I tore the ribbon for the digitizer when I replaced my housing so when I tried wiping and flashing a different ROM to try to fix it, I could do the whole "touch the android to start" thing. I eventually fixed the FC issue by flashing the dreaimg.nbh file and just starting over from scratch. ezterry helped me with that issue and he was very patient. I realize you didn't ask and you were joking, but I starting into a background ramble and I had to finish it.
Click to expand...
Click to collapse
Its kool man its always good to hear about users with different experiences on things they try in case we run into that same problem. I'm juust like you I try to figure things out myself before I resort to posting on how to because I know most answers are already out there.

Guys, thanks to this thread, I was able to bring my G1 back from the brink. This morning it reset itself and froze at the G1 screen no matter what I did. Pulling the battery and rebooting... nothing. Plugging it to a charger when starting...nothing. I thought it was done for since I couldn't access the recovery section.
Something mine was doing that I didn't see mentioned above is that if I went into the HBOOT/Fastboot screen (camera/power held to startup), it would freeze at that screen after just a couple of seconds. Once I got adb up and running, it wouldn't even find the phone at first. After playing with it for a few minutes, I noticed that I had, literally, about 3 seconds of time that it would register seeing the G1 at the fastboot terminal screen. I took a chance and set up the command line to reflash the recovery, rebooted to flashboot, and plugged in the USB. As soon as the screen showed that it saw my phone, I hit enter. Luckily, it transferred the new recovery .img in time and I was able to bring it back to life. DAMN...
Anyway, thanks again to you fellas!

reese.leblanc said:
Guys, thanks to this thread, I was able to bring my G1 back from the brink. This morning it reset itself and froze at the G1 screen no matter what I did. Pulling the battery and rebooting... nothing. Plugging it to a charger when starting...nothing. I thought it was done for since I couldn't access the recovery section.
Something mine was doing that I didn't see mentioned above is that if I went into the HBOOT/Fastboot screen (camera/power held to startup), it would freeze at that screen after just a couple of seconds. Once I got adb up and running, it wouldn't even find the phone at first. After playing with it for a few minutes, I noticed that I had, literally, about 3 seconds of time that it would register seeing the G1 at the fastboot terminal screen. I took a chance and set up the command line to reflash the recovery, rebooted to flashboot, and plugged in the USB. As soon as the screen showed that it saw my phone, I hit enter. Luckily, it transferred the new recovery .img in time and I was able to bring it back to life. DAMN...
Anyway, thanks again to you fellas!
Click to expand...
Click to collapse
Good job thinking on your feet!!

i`m having kind of the same problem with my G1 it won't boot all of a sudden and when i try to enter recovery mode it freezez at " Build : " once after about 5-10 minutes it loaded the recovery menu but nothing was working it was extremely slow ... i tried the options above to erase and reflash the recovery.img but it just won't work it does the same thing ... anyone have a solution ? ...

reese.leblanc said:
Guys, thanks to this thread, I was able to bring my G1 back from the brink. This morning it reset itself and froze at the G1 screen no matter what I did. Pulling the battery and rebooting... nothing. Plugging it to a charger when starting...nothing. I thought it was done for since I couldn't access the recovery section.
Something mine was doing that I didn't see mentioned above is that if I went into the HBOOT/Fastboot screen (camera/power held to startup), it would freeze at that screen after just a couple of seconds. Once I got adb up and running, it wouldn't even find the phone at first. After playing with it for a few minutes, I noticed that I had, literally, about 3 seconds of time that it would register seeing the G1 at the fastboot terminal screen. I took a chance and set up the command line to reflash the recovery, rebooted to flashboot, and plugged in the USB. As soon as the screen showed that it saw my phone, I hit enter. Luckily, it transferred the new recovery .img in time and I was able to bring it back to life. DAMN...
Anyway, thanks again to you fellas!
Click to expand...
Click to collapse
Lol I'm glad my problem helped ya out. I actually ended up fixing it myself luckily enough. But thanks to all who posted responses
Sent from my HTC Vision using XDA

Bricked! Please Help!!

Man I hope somebody can help me! I was trying to flash the latest CM7 nightly when in the process my phone just froze (while the ROM was flashing in recovery). I left it and the phone finally rebooted. I have the latest CWM with ext4 recovery and the Trinity kernel installed on my phone. When I boot up and try to get back into recovery the phone just hangs on the Trinity splash screen and won't let me into recovery.
I tried to reboot recovery through adb, and the phone reboots but it just takes me back to the battery charging screen (since the phone was plugged in). When I use adb the phone does show up when I do adb devices but gives an error when I do adb shell.
Is there anything I can do to do a nandroid restore or flash a new ROM or basically anything to get my phone back?

dude the same thing happened to me take the battery out then press vol up n power this will reboot ur phone now when its rebooting n u get the blank screen for a split second QUICKLY hold vol down n power (recov) n u should get back in recovery good luck bro

after u take batt out make sure to put it back in n do steps forgot to clarify

I had something like this happen a few weeks ago. I re-preformed the NVFlash of CWM and everything worked after that. I don't pretend to know why, but maybe it'll help you. I was still using the test CWM and no extra kernels at the time. Good luck.

Whew! Man that was a close one! Ok It is doing a NANDROID restore now. Here's what I did:
I installed an older CWM thru NVFlash and then I pulled the batter, placed it back in and then did the power+vol up and then quickly power +vol down and it got me to recovery.
Thanks guys for your help!

mightykc said:
Man I hope somebody can help me! I was trying to flash the latest CM7 nightly when in the process my phone just froze (while the ROM was flashing in recovery). I left it and the phone finally rebooted. I have the latest CWM with ext4 recovery and the Trinity kernel installed on my phone. When I boot up and try to get back into recovery the phone just hangs on the Trinity splash screen and won't let me into recovery.
I tried to reboot recovery through adb, and the phone reboots but it just takes me back to the battery charging screen (since the phone was plugged in). When I use adb the phone does show up when I do adb devices but gives an error when I do adb shell.
Is there anything I can do to do a nandroid restore or flash a new ROM or basically anything to get my phone back?
Click to expand...
Click to collapse
Dont stress too hard, ya its a pain and you may have to funble around for a while but you'll get it. I started periodically copying a 'latest backup' along with a 'cwm recovery' file and saving it on my PC Hard Drive. I actually have it setup now where both ROM Manager and TI Backup save the file to my SD card and it then sync's nightly at like 3am to my DropBox fileshare... that way if I'm ever away from my pc I can just find a pc to use and quickly grab it with all the materials I need in one spot (TIB backs-up all your apps by the way which is nice).
If worst comes to worst I grabbed the stock ROM off a thread here and I can link you to it if you need it. I'm sure you'll be able to reflash your backup but if not your phone isnt necessarily toast... its just a headache.

Relock US Xoom Tiamat 1.4.4 resulted in hanging at Motorola logo

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

Bricked Inspire After New Rom Install

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!

[Solved] Can't boot, only enters download mode

So I've been trying to install some different roms and try some things out, and I've gotten myself into a jam. I didn't let a format operation complete because I thought it was just frozen and my internal memory started showing a size of 0b. TWRP couldn't format or mount the cache, system, or data so I went hunting for info. Someplace I read that switching to cwm and back to twrp helped some folks. I successfully got CWM onto the tablet, only to find that after reboot, it also doesn't fully boot, only going into what I'd assume is download mode.
At this point, I'm able to access it via ADB, but I'm definitely out of my element by now so any suggestions would be appreciated. I'd like to basically get back to working with twrp if at all possible, but I'm afraid I might be hooped.

eternalbl said:
So I've been trying to install some different roms and try some things out, and I've gotten myself into a jam. I didn't let a format operation complete because I thought it was just frozen and my internal memory started showing a size of 0b. TWRP couldn't format or mount the cache, system, or data so I went hunting for info. Someplace I read that switching to cwm and back to twrp helped some folks. I successfully got CWM onto the tablet, only to find that after reboot, it also doesn't fully boot, only going into what I'd assume is download mode.
At this point, I'm able to access it via ADB, but I'm definitely out of my element by now so any suggestions would be appreciated. I'd like to basically get back to working with twrp if at all possible, but I'm afraid I might be hooped.
Click to expand...
Click to collapse
Define 'download mode'
Thx Josh

The screen shows the green android guy with his stomach open with a blue 3d geometrical shape spinning around.

eternalbl said:
The screen shows the green android guy with his stomach open with a blue 3d geometrical shape spinning around.
Click to expand...
Click to collapse
I am sure that is a factory reset ......
Boot into this plug it into power and let it do its thing ....
Thx Josh

lj50036 said:
I am sure that is a factory reset ......
Boot into this plug it into power and let it do its thing ....
Thx Josh
Click to expand...
Click to collapse
Well, it seems you were right. After about 45 minutes I checked on it and it said something about re-applying root, I accepted it and now it says android is upgrading like after an initial rom install.
edit: yup, booting normally now. Can't thank you enough, I thought it was done for.

eternalbl said:
Well, it seems you were right. After about 45 minutes I checked on it and it said something about re-applying root, I accepted it and now it says android is upgrading like after an initial rom install.
edit: yup, booting normally now. Can't thank you enough, I thought it was done for.
Click to expand...
Click to collapse
Great to see you up and running ..... :good:
Can you add 'SOLVED' to the thread tittle.
Thx Josh