Related
Hiya all, I am quite desperate for help, I consider myself intermediate when it comes to dealing with android devices but I am well and truly stumped on this one.
I received a second hand streak from eBay yesterday, turned on first time and booted fine, running Steakdroid 1.9.0 by DJ Steve. I had a few issues with it reboot randomly or crashing, as it had Streakmod Recovery installed I did a full wipe all areas, reinstalled the Rom 1.9.0 and bit a factory reset on reboot from the Dell recovery menu.
All the device does now is reboot in bootloop on the dell logo it stall when it goes as far as booting or trying to load the Rom.
I ran the test in fastboot to test the internal drive as this is known to fail and both that and my SD memory passed the test.
I used fastboot and CMD to flash 4399 recovery image the OEM recovery image for the Rom Streak_104_4399_21.pkg I renamed this to update.pkg and rebooted the device into recovery where I then went to restore the original firmware (1.6) but as soon as I pressed the camera button to proceed I was greeted with a lovely black screen.
I left the device for about 2 minutes where it reset itself and just keep rebooting on the dell logo the restore did not seem to work, just to check fastboot and CMD was working as it should I went to reinstall the Streakmod Recovery image and sure enough it worked I managed to boot the device back into streakmod.
Unfortunately every time I try to install a custom rom they just do not seem to load the device simply stalls on the Dell logo because I cant seem to restore the original recovery image for the stock rom I cannot factory restore and nor will any custom rom boot.
All I have is access to fastboot and Streakmod recovery aaaah!!
If anyone can help me in the slightest I would well very, very, very much appreciate it!
As you have fastboot working, go to the wiki and download the recovery.img for the latest 360 rom, put the corresponding rom on your sd card named update.pkg and try to do a recovery by powering on device holding down volume up and down.
Flash then do a factory reset and you should be fine.
Streakmod is a great tool for flashing custom roms, not too many problems using custom roms, but you must use Streakmod with care, never use the factory reset option from within streakmod itself, this can render your phone a brick.
(InsertNameHere) said:
As you have fastboot working, go to the wiki and download the recovery.img for the latest 360 rom, put the corresponding rom on your sd card named update.pkg and try to do a recovery by powering on device holding down volume up and down.
Flash then do a factory reset and you should be fine.
Streakmod is a great tool for flashing custom roms, not too many problems using custom roms, but you must use Streakmod with care, never use the factory reset option from within streakmod itself, this can render your phone a brick.
Click to expand...
Click to collapse
Thanks for the reply here's my progress so far:
Flashed recovery image and loaded rom to SD card..... Booted into dell recovery and this is what happened
Finding update package
Opening update package
Verifying update package
Yellow bar 25%ish at this point
flashing lights
Installing Update
33%ish lights flash again
Yellow bar jumps 3/4 then fills screen, streaks screen goes blank/ off
Doesn't reboot/ cant turn on so I remove battery and switch back on and I am back to Dell logo then I get a picture of an android and another small progress bar that slowly fills and the device and it again reboots
Streak reboots again about 3 times like it is stuck in bootloop, I leave it and keep my fingers crossed I then get an animation of the Dell logo and glowing lights behind it.
Keep fingers crossed and sure enough it boots into the lock screen, I go to unlock it but it freezes and I get the flashing lights syndrome and the screen goes blank
Remove battery and switch on again, dell logo bootloop after about 8 or 9 bootloops it boots back up into the ROM above but then crashes once again...
Is it fair to say this streak has given up the ghost?
Flashing lights could mean baseband mismatch.
Try again, but be certain to use the correct recovery.img for the rom you are flashing, get the 351, 354 or 360 recovery.img that matches your choice of rom.
Make sure there is only 1 update.pkg on your microsd card, the one you want to flash, move all others, rename them or delete them. The Dell recovery always looks for update.pkg, nothing else.
Flashing lights could be something more major, but i still think its a baseband mismatch.
(InsertNameHere) said:
Flashing lights could mean baseband mismatch.
Click to expand...
Click to collapse
Honestly thats what I wanted to hear but what worries me is I downloaded the recovery and image from Wiki both relating to 360 will try flashing again I really do hope it can be fixed! Seems today is not a good day for me today many things going up the creek!
I am 75% certain if you flash it with the right update.pkg, that is a renamed 360 pkg you downloaded, you will have success.
When you flashed Streak_104_4399_21.pkg you were trying to revert to Android 1.6.
You may have to use the QDLTool to fix the Streak. I am not sure what problems trying an 1.6 build over an Android 2.2 build can cause. You may want to wait for some more feedback.
Start here for more info and try the links in my signature.
I dont believe you can downgrade directly from 2.2.x -> 1.6.
2.2.x -> 2.1 -> 1.6 might work but why are you doing this in the first place?
Just directly install 360 or the like
teaganravetta,
Does this sum up your situation?
1) you bought a used phone and it had StreakDroid 1.9.0 on it
2) because of issues with SD 1.9.0, you tried to flash Streak_104_4399_21.pkg, not realizing that SD is based on a newer stock rom
3) you then tried flashing bb 360
3) Now you are having issues with boot loops and phone won't boot?
marvin02 said:
teaganravetta,
Does this sum up your situation?
1) you bought a used phone and it had StreakDroid 1.9.0 on it
2) because of issues with SD 1.9.0, you tried to flash Streak_104_4399_21.pkg, not realizing that SD is based on a newer stock rom
3) you then tried flashing bb 360
3) Now you are having issues with boot loops and phone won't boot?
Click to expand...
Click to collapse
Yes thats exactly what happened and in that exact order I am guessing this means the worse, am going to try for the 3rd time now reflashing 360 so fingers crossed
teaganravetta said:
Yes thats exactly what happened and in that exact order I am guessing this means the worse, am going to try for the 3rd time now reflashing 360 so fingers crossed
Click to expand...
Click to collapse
I'm not going to tell you anything different than anyone else, however I am going to give you links to the exact files you need so there is no confusion.
Download this:
http://mirror2.streakdroid.com/manii/360/recovery.img
This is the recovery image for 360. Save it in the folder on your computer that has fastboot.
Now download this:
http://mirror2.streakdroid.com/manii/Streak_360_17397_00.pkg
Rename this to Update.pkg and place in the root of your SD Card. (ensure there is no other Update.pkg on your card)
Power off the phone, if not done already.
Hold the power and camera button down until you get a white screen. Click on fastboot on your phone. Wait 10 seconds.
Plug it into your computer with the usb cable.
Wait for it to say fastboot ready (or something similar).
Now flash the recovery.img using the following command (This command assumes a Windows PC):
fastboot.exe -i 0x413 flash recovery recovery.img
When both your computer and the phone says it was successful, complete, or whatever, pull the battery.
Replace the battery, hold both volume buttons along with the power button.
In the menu that opens, choose the second option. Let us know your results.
I only added this post in case their was confusion over which files were actually needed. No need for a separate baseband, dsp1, or anything else. These are all included in the pkg file.
many thanks for all the help, so far I have downloaded "QDLTool3rd_20101022_GAUSB1A130500" turned off driver signing as I am x64 all ADB drivers fine and COM ports okay have restored via this tool according to the log successfully.
Phone rebooted a few times it has paused on the Dell logo for a moment but the guide did say anything up to 10minutes for first boot so I am holding for the moment to see if this has cured it otherwise I will report back and re download the above files and try that!
It takes me a while because I am out in the sticks I only have a 60kbps download speed (yikes) I know!!
Because your first attempt at flashing a stock ROM was the Android 1.6 version I am not sure you can just flash 360 at this point. I think you have to use the QDLTool (repairtool), but I am not sure. Try searching for the procedures that were used to upgrade from 1.6.
Edit to use the QDLTool:
In this post DL under commonly downloaded tools get Fastboot/ADB utils + drivers for Streak 5/7 and Venue and QDL Tool.
Then download qdltool-tutorial.zip from this page. unzip the tutorial and open it with a browser that supports flash or other flash viewer.
After using the QDLTool let the Streak boot and then flash the 360 recovery file and the 360 ROM. You must not let the phone boot completely after flashing a different recovery or the phone will restore the one that came with the ROM currently on the phone. Read this.
You can find more info about QDLTool by searching. As I said I think that is what you need to do.
lordmorphous said:
I'm not going to tell you anything different than anyone else, however I am going to give you links to the exact files you need so there is no confusion.
Download this:
http://mirror2.streakdroid.com/manii/360/recovery.img
This is the recovery image for 360. Save it in the folder on your computer that has fastboot.
Now download this:
http://mirror2.streakdroid.com/manii/Streak_360_17397_00.pkg
Rename this to Update.pkg and place in the root of your SD Card. (ensure there is no other Update.pkg on your card)
Power off the phone, if not done already.
Hold the power and camera button down until you get a white screen. Click on fastboot on your phone. Wait 10 seconds.
Plug it into your computer with the usb cable.
Wait for it to say fastboot ready (or something similar).
Now flash the recovery.img using the following command (This command assumes a Windows PC):
fastboot.exe -i 0x413 flash recovery recovery.img
When both your computer and the phone says it was successful, complete, or whatever, pull the battery.
Replace the battery, hold both volume buttons along with the power button.
In the menu that opens, choose the second option. Let us know your results.
I only added this post in case their was confusion over which files were actually needed. No need for a separate baseband, dsp1, or anything else. These are all included in the pkg file.
Click to expand...
Click to collapse
Thanks, this got my problem solved (endless boot logo issue with Simple Droid rom), however I am left with a no cell tower reception ?
I flashed the official stock unlocked retail rom ? still no tower reception ?
Try Simple Streak 1.2 , as i had this problem yestrday , but for simple streak 1.2 everything Worked Fine , just goto its thread and follow its instructions and u wll hve 2.2.2 in 15minutes , hit thnx if this helps
I wanted to run a custom ROM on my A500 (first attempt at installing custom ROM), but i'm now stuck at the boot animation.
I downgraded my A500 to 3.0.1, rooted, installed clockwork mod, upgraded cwm to 1.5. So far so good.
Then i downloaded thor rom v12, copied it to the external sd card (by putting it on USB thumb drive, transfer to tablet, copy to external SD using file explorer - something tells me I'm going to need to pick up an sd card reader for my computer)
Rebooted into recovery, wiped everything (had nothing of value installed yet), and then chose to install zip file, chose thor_rom_v12.zip on external SD card, it started installing - looked like it succeeded.
Reboot tablet, and i've been staring at the boot animation (electric blue pulsating android with spinning gears on it) for about 45 minutes.
How should I proceed from here? Any idea what I did wrong?
Thanks
Hold the power button down and see if you can force it to shut down. I dont think itll turn off but its worth a try. You could also try the hard reset button (pin hole on the side of the tab) if the reset works than you should be able to boot back into recovery. If not than youll just have to wait till the battery dies.
Once you eventually get it turned off than try booting into recovery and do a full wipe and reflash the rom. I have a feeling the file you downloaded is corrupted though. if this is so than your tab probally wont boot up again.
At this point id redownload the thor or another rom and than try flashing that. You'd have to get an sd reader since you won't be able to transfer the files through your iconia again. If you can manage to get a clean download on your micro sd somehow than i'd skip straight to this step and start redownloading the rom right now.
BTW these are just the things i would try from knowing what I do about android. I haven't had any issues with my tab yet so I havent looked for solutions for this it, but ive dealt with other boot looped and soft bricked devices.
I'm sure if you do a search you'll find something.
I flashed an ICS nightly from over in the development forum and I'm left with a Nook that won't boot. Basically I flashed the nightly, booted ICS and then rebooted as I forgot to flash gapps. Upon rebooting I got the new cyanoboot bootloader however I can not boot into anything. I just get loading... If I try to boot into recovery I get loading recovery... and nothing. I tried flashing recovery onto my SD card and selecting each one of the 3 SD card boot options from the bootloader menu however none of them work. Everything hangs at loading. Any ideas one what my next step should be?
Sigh!!!
eMMC or uSD?
votinh said:
Sigh!!!
eMMC or uSD?
Click to expand...
Click to collapse
Here's the original thread. My best guess is that it's eMMC.
http://forum.xda-developers.com/showthread.php?t=1526115
Obviously the recovery image I tried was flashed to the external SD card.
Got it! Turned out to be a shotty card reader. Swapped it out with another I had lying around and it worked just fine. Thanks anyway!
EDIT: I got recovery working on the external SD card so I tried flashing a stock image. (nookcolor_1_4_1_signed-cwm-OC) I made sure to format everything first. After flashing I held in the power button, removed the sd card, placed it in my reader and formatted it. I reinserted it into the nook and booted. Everything seemed to boot fine until it got to the "nook color by barnes & noble" screen. The gradient bar goes back and forth across the lettering a bit and then I get a flash of a black screen and then back to the lettering. It keeps doing this over and over again like its in a boot loop. Any ideas?
tlenker09 said:
Got it! Turned out to be a shotty card reader. Swapped it out with another I had lying around and it worked just fine. Thanks anyway!
EDIT: I got recovery working on the external SD card so I tried flashing a stock image. (nookcolor_1_4_1_signed-cwm-OC) I made sure to format everything first. After flashing I held in the power button, removed the sd card, placed it in my reader and formatted it. I reinserted it into the nook and booted. Everything seemed to boot fine until it got to the "nook color by barnes & noble" screen. The gradient bar goes back and forth across the lettering a bit and then I get a flash of a black screen and then back to the lettering. It keeps doing this over and over again like its in a boot loop. Any ideas?
Click to expand...
Click to collapse
Since you just flashed the stock firmware with OC and CWM (as alternate) you should also have the ability to boot eMMC Recovery Mode... do that... it will clear data... and restore the data from the original rombackup.zip file... should solve your problem.
DizzyDen said:
Since you just flashed the stock firmware with OC and CWM (as alternate) you should also have the ability to boot eMMC Recovery Mode... do that... it will clear data... and restore the data from the original rombackup.zip file... should solve your problem.
Click to expand...
Click to collapse
I actually did something along these lines last night but since I flashed the stock firmware that was pre-rooted and with CWM... I booted into CWM, wiped everything, mounted usb, copied over the stock pre-rooted zip file, flashed it and then fixed permissions. Everything booted fine.
i have the same problem but im on emmc. im just stuck with loading... any solution for me?
Hello. I have an Acer Iconia Tab A200, and recently I tried a factory reset. However, due to my meddling with system files, it won't reset.
I've tried to do a hard reset (Power on, Volume+, Orientation lock switch) but it says the following:
Erasing Userdata...
Erasing Cache...
It then reboots, and does nothing. It hangs on the Acer logo.
When trying to go into recovery (Power On, Volume-), it says the following:
Erasing Cache before SD update...
SD update cmd: recovery
--update_package=SDCARD:update.zip
Booting recovery kernel image
Recovery verified fail ...
Now, I mentioned that I meddled with the System Files. Here is what I did:
1. Removed unwanted Vendor Apps
2. Removed the DEFAULT LAUNCHER <-- I think this plays a big part in this
3. Placed a CUSTOM LAUNCHER in the VENDOR APPS FILE
4. Did a FACTORY RESET
My brother is more techy than me, so he tried to fix it. However, he somehow re-locked the bootloader and even replaced the bootloader with a newer version.
I talked to Acer Support claiming it's system files corrupted itself, but they won't fix it unless I also pay to fix my cracked screen. I'm willing to do so, but hey, I'd like to see if I could save $120. I don't mind the cracked screen.
NOTES:
The Acer Iconia Tab A200, along with their other tablets, has a USB port. I can probably load stuff from there somehow, but not sure.
It is a 16GB model with a 32GB Class 10 MicroSD card in it.
Any ideas? All help is appreciated.
Vuciz said:
Hello. I have an Acer Iconia Tab A200, and recently I tried a factory reset. However, due to my meddling with system files, it won't reset.
I've tried to do a hard reset (Power on, Volume+, Orientation lock switch) but it says the following:
Erasing Userdata...
Erasing Cache...
It then reboots, and does nothing. It hangs on the Acer logo.
When trying to go into recovery (Power On, Volume-), it says the following:
Erasing Cache before SD update...
SD update cmd: recovery
--update_package=SDCARD:update.zip
Booting recovery kernel image
Recovery verified fail ...
Now, I mentioned that I meddled with the System Files. Here is what I did:
1. Removed unwanted Vendor Apps
2. Removed the DEFAULT LAUNCHER <-- I think this plays a big part in this
3. Placed a CUSTOM LAUNCHER in the VENDOR APPS FILE
4. Did a FACTORY RESET
My brother is more techy than me, so he tried to fix it. However, he somehow re-locked the bootloader and even replaced the bootloader with a newer version.
I talked to Acer Support claiming it's system files corrupted itself, but they won't fix it unless I also pay to fix my cracked screen. I'm willing to do so, but hey, I'd like to see if I could save $120. I don't mind the cracked screen.
NOTES:
The Acer Iconia Tab A200, along with their other tablets, has a USB port. I can probably load stuff from there somehow, but not sure.
It is a 16GB model with a 32GB Class 10 MicroSD card in it.
Any ideas? All help is appreciated.
Click to expand...
Click to collapse
Do you have access to any a200 Update roms? Sometimes, you can pull the update.zip from the rom, place it on your ext sd card, reboot holding Vol+ and PWR, and it might install.
MD
Moscow Desire said:
Do you have access to any a200 Update roms? Sometimes, you can pull the update.zip from the rom, place it on your ext sd card, reboot holding Vol+ and PWR, and it might install.
MD
Click to expand...
Click to collapse
I have searched for some A200 ROMs, but can't find any that work using that method. I'm open for ANY Acer A200 official ROM, then simply updating using OTA. I tried an Acer A200 Recovery Pack I found. It is the exact stock Honeycomb image, but it didn't go. It always says recovery verified fail. I cannot unlock the BootLoader either.
Stockimage flashable while having bricked /DATA Partition
Hi Vuciz,
do you still have the issue with your bricked A200 ?
I got the same problem with mine, the only solution was to send it to repair, it seems the storage controller chip has some bug which destroyed the /DATA partition unrecoverable.
if you need to revert your Tablet to an locked bootloader you have to download an StockRom and modify it by removing the partition check (called "assert") in the update script.
please send me an message if you need further assistance.
regards and good luck with your tab.
Nickbert said:
Hi Vuciz,
do you still have the issue with your bricked A200 ?
I got the same problem with mine, the only solution was to send it to repair, it seems the storage controller chip has some bug which destroyed the /DATA partition unrecoverable.
if you need to revert your Tablet to an locked bootloader you have to download an StockRom and modify it by removing the partition check (called "assert") in the update script.
please send me an message if you need further assistance.
regards and good luck with your tab.
Click to expand...
Click to collapse
Yes I do. However the screen is also cracked so they want me to pay for that. Which I'm unable to do at this time.
anything I do, fails
Vuciz said:
Yes I do. However the screen is also cracked so they want me to pay for that. Which I'm unable to do at this time.
Click to expand...
Click to collapse
I also have this tablet. I bought it for 20 bucks because the screen was cracked. replaced the screen and then found out that the bootloader was trashed. I've done almost everything I can think of to fix it. Used APX mode to get UID from ubuntu, tried to use that UID to get sbk, got the SBK and then tried using blackthunder's tool got connection failure, tried using babsector same thing, even went in ubuntu, with tablet in manual apx mode for all three and when I attempt to reflash the bootloader, all I get is that command failure message with a nvflash connection failed nv error 0x30011 message and when that happens in windows, the tablet disappears from device manager, and in ubuntu when I run nvflash with the sbk function --sbk XXXX and so on, I get the command sent failure message, and then when i rerun lsusb, the nvidia device that represents my tablet in apx mode that showed before is no longer listed unless i reboot the tablet in apx mode again. If i boot it normally, the acer logo appears and then goes to the little animation and then the iconia tab screen and thats it. I've tried attempting to flash the bootloader from that screen which i know probably wasn't going to work anyways. If anyone has any advice on something I've missed, or anything that could help, i'll all eyes. thanks in advance.
twanhines said:
I also have this tablet. I bought it for 20 bucks because the screen was cracked. replaced the screen and then found out that the bootloader was trashed. I've done almost everything I can think of to fix it. Used APX mode to get UID from ubuntu, tried to use that UID to get sbk, got the SBK and then tried using blackthunder's tool got connection failure, tried using babsector same thing, even went in ubuntu, with tablet in manual apx mode for all three and when I attempt to reflash the bootloader, all I get is that command failure message with a nvflash connection failed nv error 0x30011 message and when that happens in windows, the tablet disappears from device manager, and in ubuntu when I run nvflash with the sbk function --sbk XXXX and so on, I get the command sent failure message, and then when i rerun lsusb, the nvidia device that represents my tablet in apx mode that showed before is no longer listed unless i reboot the tablet in apx mode again. If i boot it normally, the acer logo appears and then goes to the little animation and then the iconia tab screen and thats it. I've tried attempting to flash the bootloader from that screen which i know probably wasn't going to work anyways. If anyone has any advice on something I've missed, or anything that could help, i'll all eyes. thanks in advance.
Click to expand...
Click to collapse
Just so you know, I was never able to resolve this issue.
Hello,
I search help for my Acer Iconia Tab A200.
During a flash with TWRP, it block and I have to set my A200 off using Power.
And then, my A200 don't work, don't vibrate.
I try :
Reset + Power : nothing, no vibration
Power + Vol- : nothing, no vibration
Power + Vol+ + switch : same result
Connected to PC : adb devices : nothing
All commands adb or fastboot : waiting for device
I don't know what to do...
where can I send my Acer tablet to fixed stuck on bootloader
hello I have an acer iconia 200 stuck bootloader cant find anyone to fix it. Acer wont touch it unless its under warrenty! my 90 day store warrenty has been way past! taken to 2 local computer tech both told me I needed to send it back to acer but I cant! so what can ido i or where can I send it?? anyones time and effort would greatly appreicated!!! thanx for your time
Summary:
I bricked my sister's Nook Color. She bought it refurbished at a pawn shop for cheap and everything was working until I told my sister that I could root the nook and put an android rom on it. My biggest mistake ever.
I looked at a lot of forums relating to the problem and it seems like there isn't a fix. So basically I got to the point of having CWM working.
All was going so well and I decided to flash eyeballer's cm-9-encore-20120904-0700-unofficial.zip on it. The one on Goo.im. After looking at screenshots of CM9 I was impressed.
I did the factory reset on it and wipe the cache, I flashed the CM9 and it was installing and it seem that it was taking a long time and then the nook turned off.
The biggest mistake that I made was that I formatted the boot , I'm a noob, I figured I wasn't the only one so I came across a thread here http://forum.xda-developers.com/showthread.php?t=949699
I thought that CM9 got installed and when I went to turn it on, nothing whatsoever... It doesn't boot no more.
I tried putting the 1gb bootable CWM on a 1gb sd card with Win32 Disk Imager and the Nook didn't boot from the SD card either and I also did the same with an 8gb.
When I go connect the Nook on the computer it searches for a driver called Omap3630 but it doesn't install and it seems to disconnect itself.
I am was looking for more threads and found out that I'm in a similar situation as a user called Jiv_au here,
http://forum.xda-developers.com/showthread.php?t=1146065
3rd post. I also tried what he did with the 8 boot attempts, pressing power button for 60 seconds and pressing the power on, the N and the volumes.
Seakuza said:
Summary:
I bricked my sister's Nook Color. She bought it refurbished at a pawn shop for cheap and everything was working until I told my sister that I could root the nook and put an android rom on it. My biggest mistake ever.
I looked at a lot of forums relating to the problem and it seems like there isn't a fix. So basically I got to the point of having CWM working.
All was going so well and I decided to flash eyeballer's cm-9-encore-20120904-0700-unofficial.zip on it. The one on Goo.im. After looking at screenshots of CM9 I was impressed.
I did the factory reset on it and wipe the cache, I flashed the CM9 and it was installing and it seem that it was taking a long time and then the nook turned off.
The biggest mistake that I made was that I formatted the boot , I'm a noob, I figured I wasn't the only one so I came across a thread here http://forum.xda-developers.com/showthread.php?t=949699
I thought that CM9 got installed and when I went to turn it on, nothing whatsoever... It doesn't boot no more.
I tried putting the 1gb bootable CWM on a 1gb sd card with Win32 Disk Imager and the Nook didn't boot from the SD card either and I also did the same with an 8gb.
When I go connect the Nook on the computer it searches for a driver called Omap3630 but it doesn't install and it seems to disconnect itself.
I am was looking for more threads and found out that I'm in a similar situation as a user called Jiv_au here,
http://forum.xda-developers.com/showthread.php?t=1146065
3rd post. I also tried what he did with the 8 boot attempts, pressing power button for 60 seconds and pressing the power on, the N and the volumes.
Click to expand...
Click to collapse
The problem is that you formatted boot, and CM does not include all of the needed boot files if you formatted boot. You will need to flash the stock firmware back onto the device, and then you can proceed to flash whatever ROM you want on the device, LINK.
I am not sure what version bootable CWM you are using, but download and flash this one,LINK. Since you saw the Omap3630 driver prompt, it does mean that it still is alive and attempting to go through the booting process. As for getting it to boot from this card, you will not get any visual indication that the device is on or not, the screen will stay dark if it’s on or off. Since the device might have been on this whole time I recommend that you fully charge the device before proceeding forward. With no USB cable connected to the device, press and hold the power button for 30 seconds, then insert the SD card, then press and hold the power button for 5 seconds to turn it on. It should boot into the CWM recovery, if it does not press the power button for 30 seconds and try again. It might take a couple attempts, but you should be able to get it. Once you get the device to boot, wipe data/cache, and flash the stock image, and reboot the device. Once you have a working device, you can then boot into the CWM card, and flash the ROM that you want.
GMPOWER said:
The problem is that you formatted boot, and CM does not include all of the needed boot files if you formatted boot. You will need to flash the stock firmware back onto the device, and then you can proceed to flash whatever ROM you want on the device, LINK.
I am not sure what version bootable CWM you are using, but download and flash this one,LINK. Since you saw the Omap3630 driver prompt, it does mean that it still is alive and attempting to go through the booting process. As for getting it to boot from this card, you will not get any visual indication that the device is on or not, the screen will stay dark if it’s on or off. Since the device might have been on this whole time I recommend that you fully charge the device before proceeding forward. With no USB cable connected to the device, press and hold the power button for 30 seconds, then insert the SD card, then press and hold the power button for 5 seconds to turn it on. It should boot into the CWM recovery, if it does not press the power button for 30 seconds and try again. It might take a couple attempts, but you should be able to get it. Once you get the device to boot, wipe data/cache, and flash the stock image, and reboot the device. Once you have a working device, you can then boot into the CWM card, and flash the ROM that you want.
Click to expand...
Click to collapse
You gave me a bit of hope but its not booting. The nook is dead... thanks for the help.
edit: I heard that pressing Power + N is like forcing a shut down so I hold those for 30 seconds and then put the SD card in it No boot.
I tried it again and put the Sd card in it and then press the power button still nothing. I believe this is definitely dead. I wish she had bought it at the B&N store. I think I'm getting her a Nook tablet. I owe it to her.