I've got a "brick" nook(not i killed it).which doesn't start ,just shows "don't turn off your device,installing...bla-bla.." for few seconds, than it says to "restart your device " and if i do, ot all starts again from point 1 ). the best, i could do after many hours was that screen, which appears when sd with stock system image is inserted. but it shows in right upper angle red cross,instead of a green check ( and i never got any further,on could do more... is it all hopeless?
What did you do prior to this, give some background to how you got to this point.
I am assuming you wiped something you shouldn't have.
Sent with my Dinc4G
poorstudent said:
when sd with stock system image is inserted.
Click to expand...
Click to collapse
Whats stock system image are you using? If it's the "repart.img" I don't have anything better to suggest. It indeed it is that one you're already using, try to burn it again. Probably won't help one bit, but hey, we're clutching at straws here !
There's also Adam Outler's method you could try if you haven't already.
But, like DacDoc says, more info needed!
Thanks a lot to both of you ! clutching at straws really we do! but mine seems to be a broken one! )
The previous ouner did it, but he told me, he tryed to install cm10 or 7.... smth like this. unfortunately, all info i could get,i already posted out.
Maybe, somehow will help,that nook and sd appear for few seconds as removable disks. both under win and ubuntu. but no reaction on my actions. the problem, as i see it, to make the damn device to "go out" somehow, to start installing new software. I'll try now to burn repart.img agane, ind see,if it helps. Thanks again, and feel free to hint me any idea that you will get ! )
Have you tried Adam Outler's unbrick? I haven't use it myself (thank heavens when I messed up mine the repart.img was all I needed! <phew>), but I have read several posts here of people that had success with his method after trying and failing other ways..
http://forum.xda-developers.com/showthread.php?t=1470910
Can you get into CWM using bootable sd card?
I want to say I have seen this screen before, trying to factory reset without having stock recovery.
Sent with my Dinc4G
Is this a tablet or a color? 8 or 16gb? Have you tried to run it strictly from an SD card with either CM 7 or CM 10?
Sent from my CM 10 nook. Thanks devs.
SlowCobra96 said:
Is this a tablet or a color? 8 or 16gb? Have you tried to run it strictly from an SD card with either CM 7 or CM 10?
Sent from my CM 10 nook. Thanks devs.
Click to expand...
Click to collapse
The picture shows a one piece glass which is the Nook Tablet. The Nook color has a two piece glass.
Look at Veronica's thread about fixing the NT http://forum.xda-developers.com/showthread.php?t=1415812
If the nook tablet is 16gb version see Adam's thread http://forum.xda-developers.com/showthread.php?t=1402190
The only reason I asked is because there have been more than a couple that have strolled into this forum not knowing what they had. I don't recall ever seeing that particular screen on an NT. The color of it looks off also. Probably just the photograph.
poorstudent said:
I've got a "brick" nook(not i killed it).which doesn't start ,just shows "don't turn off your device,installing...bla-bla.." for few seconds, than it says to "restart your device " and if i do, ot all starts again from point 1 ). the best, i could do after many hours was that screen, which appears when sd with stock system image is inserted. but it shows in right upper angle red cross,instead of a green check ( and i never got any further,on could do more... is it all hopeless?
Click to expand...
Click to collapse
OK it looks like you are trying to install a stock bn ROM by using an SD card. The correct procedure is here on the bn site
http://www.barnesandnoble.com/u/Software-Updates-NOOK-Tablet/379003187
Make sure the nook tablet is fully charged and hooked up to your computer. What happens when you turn on the nook with no SD card? Any messages come up? Do you know if previous owner installed CWM internally?
Here is Indirect's thread to flash stock recovery http://forum.xda-developers.com/showthread.php?t=1458630
poorstudent said:
I've got a "brick" nook(not i killed it).which doesn't start ,just shows "don't turn off your device,installing...bla-bla.." for few seconds, than it says to "restart your device " and if i do, ot all starts again from point 1 ). the best, i could do after many hours was that screen, which appears when sd with stock system image is inserted. but it shows in right upper angle red cross,instead of a green check ( and i never got any further,on could do more... is it all hopeless?
Click to expand...
Click to collapse
i have the same thing. i ended up installing newest jb rom with 10 touch firmware. i beleave it went into boot loop and tried to reset its self. i have tried everything i did adams linux and it just freezes. i tried all the partition ways and cant get sd mount in adb. cwm is all i can get to and when i load cwm from sd i get E:cant mount/cache/recovery/command exe, exe, i did the factory reset and get the red x aswell ant help would be great..
gowboy84 said:
i have the same thing. i ended up installing newest jb rom with 10 touch firmware. i beleave it went into boot loop and tried to reset its self. i have tried everything i did adams linux and it just freezes. i tried all the partition ways and cant get sd mount in adb. cwm is all i can get to and when i load cwm from sd i get E:cant mount/cache/recovery/command exe, exe, i did the factory reset and get the red x aswell ant help would be great..
Click to expand...
Click to collapse
For you new members with bricked Nook Tablets watch the video by Ray Waldo on how to unbrick your NT.
http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
He has step by step instructions and a video. Do every step in the order specified.
Thanks a lot 2 all,who tryed to help !
I've tryed Adam Outler's way -to rewrite all data with zeroes,but after i got ubuntu screen, there was a message "MLO partition will be written with all zeros" and progress bar was empty, no reaction at all.
2. i tryed many times 2 start from sd with "repart.img" but i har red cross instead of green check.
Looks like the same case has upper poster. So now i'm comletly stuck, don't see any ways out,but not gonna to give up! )
poorstudent said:
Thanks a lot 2 all,who tryed to help !
I've tryed Adam Outler's way -to rewrite all data with zeroes,but after i got ubuntu screen, there was a message "MLO partition will be written with all zeros" and progress bar was empty, no reaction at all.
2. i tryed many times 2 start from sd with "repart.img" but i har red cross instead of green check.
Looks like the same case has upper poster. So now i'm comletly stuck, don't see any ways out,but not gonna to give up! )
Click to expand...
Click to collapse
If your device is still under warranty contact BN for a replacement.
[QUOTEsteadilyudent;36119478]Thanks a lot 2 all,who tryed to help !
I've tryed Adam Outler's way -to rewrite all data with zeroes,but after i got ubuntu screen, there was a message "MLO partition will be written with all zeros" and progress bar was empty, no reaction at all.
2. i tryed many times 2 start from sd with "repart.img" but i har red cross instead of green check.
Looks like the same case has upper poster. So now i'm comletly stuck, don't see any ways out,but not gonna to give up! )[/QUOTE]
I didn't even boot to Ubuntu I just got blank screen. I you can try doing resets on sd and do dd method in adb. IM lost on what to do I don't understand why I can't even mount my SD card. Nexus 7 is what is next for me.
gowboy84 said:
[QUOTEsteadilyudent;36119478]Thanks a lot 2 all,who tryed to help !
I've tryed Adam Outler's way -to rewrite all data with zeroes,but after i got ubuntu screen, there was a message "MLO partition will be written with all zeros" and progress bar was empty, no reaction at all.
2. i tryed many times 2 start from sd with "repart.img" but i har red cross instead of green check.
Looks like the same case has upper poster. So now i'm comletly stuck, don't see any ways out,but not gonna to give up! )
Click to expand...
Click to collapse
Also Adam's and repart.IMG methods can take several hours (not minutes) to complete. I would suggest running Adam's method overnight. Don't touch it. Just go to bed and check it in the morning. Plug in charger just in case. Report back in the morning after you wake up.
hwong96 said:
Also Adam's and repart.IMG methods can take several hours (not minutes) to complete. I would suggest running Adam's method overnight. Don't touch it. Just go to bed and check it in the morning. Plug in charger just in case. Report back in the morning after you wake up.
Click to expand...
Click to collapse
I will try again I did it the first night it was bricked let it set all night with Adams method from 10on to 8am and was still on blank screen then tried repart to 1.4.2 and still got red x the **** down in 5sec. Thanks for your help I will try again tomorrow night. Real strange seams I am only on this happened to. Bat was dead went crazy like always then could not boot back up adb only shows boot file when look at partition parted /Dev/block/Mmcblk0 print
poorstudent said:
Thanks a lot 2 all,who tryed to help !
I've tryed Adam Outler's way -to rewrite all data with zeroes,but after i got ubuntu screen, there was a message "MLO partition will be written with all zeros" and progress bar was empty, no reaction at all.
2. i tryed many times 2 start from sd with "repart.img" but i har red cross instead of green check.
Looks like the same case has upper poster. So now i'm comletly stuck, don't see any ways out,but not gonna to give up! )
Click to expand...
Click to collapse
Can you get into CWM from SD card? Also, you still haven't answered whether you have a 16GB or 8GB NT. This will determine the fix you should use.
Adams method is reported as being pretty good. It does take a long time if you have a slow SD card.
i used 8 gb card . also, i let my nookm lay down for a few hours with adam's ubunu running and no single pixel moved on progress bar. I'll try to leav it overnight,and see,what'll come out. Damn,am i alone so lucky in the world!? ))
Related
OK well I have trying my best as a noob to research for 2 days not in and out on how to fix my issue
My friend tried rooting my phone and to install a different rom. I am on 2.1 and unfortunately I got the phone used with 2.1 already on it so I don't know if it was a leaked or legit 2.1 rom, and I am learning as I go here to fix this issue as I have never new how to do this stuff nor have I ever done it.
Where I am at now:
only thing that happens when I hit power is the phone "vibrates then stays on the 3 skateboard screen" or press "volume down + power" and it goes to the Hboot screen. I go into recovery and it goes to clockworkmod and from there after trying to install any roms from the sd card it says on the last 3 lines
"E:Failure at line 9:
copy_dir PACKAGE:system SYSTEM:
Installation aborted.
and every time I go back or power up to the Hboot screen it does not have any "update bar" (I guess if this was done right as I read on other threads there should be some type of update bar) on the right corner or any other options "for me to select" accept:
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
and then with some other info above the Hboot highlighted in blue
I have tried formatting the sd card a bunch of times, I did the clearing of the "wipe data, wipe cache partition, wipe dalvikcache" as I read to do over my reading, but I see that if I go under any restore options under clockwork, no files are found for me to back up too so I am seeing he did not back up any of my info, I also have tried using 2 different ds cards.
So more less it looks like my options are to get this fixed from the only place my phone will boot to with options and thats when I press volume + and power so I guess loading whatever I need to my sd card>>if thats an option or am I screwed, I have seen many tutorials but none of them start where my particular position is stuck at in Hboot. this is my only phone and I had to buy a prepaid which is just about out of minutes, I put an add on craigslist trying to get someone I will pay to fix my issue but no luck, please I need help and I will pay u somehow to guide me through this of my exact issue, I was trying to get to rom 2.3 but if it's easier to get back to 2.1 rom then so be it.
PLEASE!~~
Please HELP!
Cheeva316 said:
Please HELP!
Click to expand...
Click to collapse
Got a solution in the making for you, just give me about 30 minutes.
Edit: Maybe 45 minutes lol, sorry i'm testing this before I have you do it to see if it works.
Ok download the following files:
http://www.mediafire.com/?njwqa7axwzyaqgb
http://www.mediafire.com/?f69cl8dc747h0l9
http://www.mediafire.com/?xg8nnqs177xggx4
http://www.mediafire.com/?qxpi5wsx5lzbhbo
http://www.mediafire.com/?4tg67hck7vh1xxs
Edit: Flash the "rootme.zip" first then follow the rest.
Now what you need to do first is extract the "nandroid" file to somewhere you can easily find it.
Now take the folder called "nandroid" along with all the other zip files you downloaded and place them on your sd card. Put your sd card in your phone and power on with volume down+end. Press volume up. Use the trackball to select "Backup/Restore". Use the trackball again to select "Nand Restore". Use it again to select "HT9BGHG01402". Use it again to select "BDS-20110125-0901". Let the restore run, then power off your phone. Turn your phone back on with just the power button, let it run (might even take up to 10 minutes for the phone to start up). Let me know if the phone boots up or not after about 10-15 minutes. This should work and if it does then we can go from there, even to getting you 2.3 if you want.
You might be asking, what the hell is he having me do ? Here's what i'm doing. I made a nandroid backup a few months ago of when I had kaosfroyov39 which is a 2.2 rom. I am going to have you flash MY backup to YOUR phone which when done right, CAN work. Anyway, let me know what happens and remember to give the phone about 10-15 minutes to boot all the way.
Cheeva316 said:
"E:Failure at line 9:
copy_dir PACKAGE:system SYSTEM:
Installation aborted.
Click to expand...
Click to collapse
( Another phone on the precipice of being ruined by someone's cobbled-together "clockwork" recovery. )
If the /system flash memory partition got corrupted in a way that left a lot of pages marked as bad pages, then the /system partition will be "short", and only small ROMs will successfully load into it, if at all. That might be the cause of the above error messages.
But - because you are using Clockwork, there is really no way to know if that is the case, or if you simply have a whole bunch of corrupted ROM files on your SD card. That's because Clockwork does not verify ROM files before it starts flashing them - which allows total garbage to be flashed to the phone. (That's why Clockwork should never be used by newbs).
Here's what I would suggest you do.
- Make sure you are keeping the phone well charged. (Leaving the phone in HBOOT mode will discharge the battery quickly, even if it is plugged in to the charger, BTW).
- Report the exact bootloader version you have - probably 1.47.0000 or 1.49.0000, but it could be something other. Please be precise.
- With the power off, eject the SD card out of the slot and see if you can boot into the normal HBOOT menu with no SD card in the slot. Report your result.
- Boot into the recovery menu and tell us what version # of the recovery you have. If you can determine the details of how your friend attempted to root the phone, that might be pertinent. Again - precise details are valuable; vague hand-waving not so much.
- The Amon_RA recovery has a mode ("USB-MS toggle") which allows you to mount the SD card to the PC. Does your "Clockwork" recovery have this feature, or are you able to put files onto the micro-SD card using a media slot on a PC?
- Be aware that one or two people that were in situations that are very close to what you described ended up bricking their phones because they went from where you are now to attempting to use either a PB00IMG.ZIP ROM, or an RUU utility. Their phones went from bootable (in the way that yours is now) to bricks in that process.
What I would suggest you do at the moment is to find the SMALLEST Eris** ROM you can find, get it onto your SD card, verify that you didn't corrupt it, and then perform a "wipe data/factory reset" in your recovery and attempt to install it. If you get the same errors as above, then you should definitely NOT try to do a PB00IMG.ZIP or RUU installation. (The current gingerbread ROMs (e.g. GSB v1.4) are pretty small - they only use about 65% of the /system partition.)
I have a flashable "repair" file which might be applicable. It is not a "ROM" per se - it uses some low-level MTD (flash memory) repair techniques, and also flashes into place the original Amon_RA (v1.6.2) recovery, instead of whatever p.o.s. "Clockwork" recovery you currently have on the phone; but I regard it as something which should only be used as a last resort. But - without some more details and testing on your part, I don't feel comfortable about posting it up.
Let me know.
**PS I wanted to ask one more question - this is an Eris we are talking about, right? (I note you were posting in the Hero CDMA forum not so long ago).
Well I want to thank you for replying with such info but it seems that the recovery image file that I reinstalled on the phone was bad cause when it was updating the bar was going up but as it was going through each item it was updating.. I noticed "bootloader in red letters" with I believe saying "error" next to it and then same on another item it tried updating then the phone powered off and now it's dead, tried everything, no charging light comes on, computer (2 different computers) wont reconize it, it's doing nothing at all, I will try to get my hands on another battery but I am broke, but I doubt it's the battery cause I heard with a bootloader error (or damaged) then the phone won't boot up or do anything so I guess the phone is scrap for parts which sucks cause now my friend who started this deal killed my only phone me n my family had, another lesson learned...time to try n sell some stuff on craigslist..damn
Yes it's a Droid Eris...or was! damnnnn...
Again thank you for your help very much appreciated...
Wish I would of read this part before I let my friend re-load the "PB00IMG.ZIP" cause thats exactly what he loaded and then it started the process what I jus described above..f***k!
Be aware that one or two people that were in situations that are very close to what you described ended up bricking their phones because they went from where you are now to attempting to use either a PB00IMG.ZIP ROM, or an RUU utility. Their phones went from bootable (in the way that yours is now) to bricks in that process.
Cheeva316 said:
Wish I would of read this part before I let my friend re-load the "PB00IMG.ZIP" cause thats exactly what he loaded and then it started the process what I jus described above..f***k!
Be aware that one or two people that were in situations that are very close to what you described ended up bricking their phones because they went from where you are now to attempting to use either a PB00IMG.ZIP ROM, or an RUU utility. Their phones went from bootable (in the way that yours is now) to bricks in that process.
Click to expand...
Click to collapse
Well, I am very sorry that this happened to you and my advice to you didn't reach you in time. From the details that you added, I am pretty sure that you indeed have a hard brick.
BUT - the death of your Eris can still help others avoid the same fate. If you can reconstruct the rooting process you went through,
[SIZE=+2]PLEASE LET US KNOW EXACTLY WHAT ROOTING METHOD YOU USED[/SIZE] - and then we can wave people away from it.
When I say exactly, I mean extremely specific: do you still have the download file that you used? If so, push it up to an uploader site and give a link to it. (I think you mentioned unrevoked or something). Do you still have the exact link you used to download that rooting software? Was it Unrevoked? Z4root?
bftb0
I will tomorrow as I saved all the files on my laptop n I am on my pc now, but will do try my best as I am a newb to this phone stuff
Did you try what I suggested or is it too late ?
phone wont do anything so cant do nothing...
Did you find out any more details about the rooting method you used?
might be a couple more days till I can get to it, my laptop is messing up now...all the saved info was on it
I've checked the other threads for solutions and I've tried many different things today but my phone still doesn't work, so I guess I should make a thread and ask you guys directly.
Ok, so my phone stopped working last night. It was running stock everything. Only upgraded to Froyo through Kies Mini a long time ago. Anyway, when I powered up the phone, it gets to the Galaxy S logo and then the screen dies. It's technically still on, since the four keys light up when I tap the screen. I took the battery out for a bit and put it back in, same thing. Logn story short, I tried to odin it back to stock JFD this morning and it didn't change anything. The screen goes to black right after the logos. Then I tried Eugene's Vibrant_Full_Froydin_AND_2E_Recovery_+SD_Fixed. It sorta worked. By that I mean, the phone loads up the OS and I got the home screen, but now it doesn't recognize the internal SD card. In fact, the notification gives me "Blank Internal SD card." In the Settings area, the phone storage read as either unavailable or 0.0 space. I tried to odin back to stock but then it gets stuck on Galaxy S logo again. I've tried this back and forth multiple times and it's still the same. Either it gets stuck on the logo or it doesn't recognize the internal sd card. I've tried it with repartition on and repartition off, but no difference.
So, are there any trick to fixing this? Thanks in advance!
Could you post the links to the files you are flashing? Honestly ODIN should have fixed it.
kawika said:
Could you post the links to the files you are flashing? Honestly ODIN should have fixed it.
Click to expand...
Click to collapse
Hi. I got the stock JVD from the Noob Guide (http://forum.xda-developers.com/showthread.php?t=849028). I followed the steps there to flash to stock through ODIN and I got the black screen/lighted buttons. Then I downloaded and flashed it with the one that came with the toolbox (http://forum.xda-developers.com/showthread.php?t=954509). same thing, black screen with lighted buttons. I also tried Eugene's ROMs (Eugene_SD+2E_JK2_Froyo - http://www.multiupload.com/12QAKU043I and the Froyo ~That does not Brick! - http://www.4shared.com/file/dJiyRz3v/EUGENE373_SamsungS_Froyo_PDA.html). Both links are from Eugene's forum page.
The only "success" I have so far is using Eugene_SD+2E_JK2_Froyo, but whenever it's loaded, I always get the "Blank internal sd card" notification and the phone storage is shown as unavailable. :\
Bump. I'm still trying to get this phone to work. :\
Give the following a try..
http://forum.xda-developers.com/showthread.php?t=1230059
Alex9090 said:
Give the following a try..
http://forum.xda-developers.com/showthread.php?t=1230059
Click to expand...
Click to collapse
Didn't quite work for me unfortunately.
1. When it's in recovery mode, I can't get adb to connect. I can only do it when it's loaded up.
2. When I tried to do print in parted, I get this error
Error: /dev/block/mmcblk0: unrecognised disk label
Click to expand...
Click to collapse
.
Do you have external card in the phone? First try taking it out and then reboot without it and see what happens. If that doesn't do anything..try the cleaning and repartitioning method posted by Br1ck'd ..
I have posted about it in several threads, including my own, so I figured I would finally put it in a central location. This is my FTDNB method for starting with a fresh, clean phone, without any ghosts of roms past popping up to cause you issues.
Download this first, and flash through Odin with your standard 512 pit file
http://eb-productions.proboards.com/...splay&thread=8
Then when it reboots to the recovery screen, pull your battery, reinsert it and boot up to dl mode, and flash the following, with your same pit file, and selecting repartition in Odin this second flash only:
http://eb-productions.proboards.com/...splay&thread=3
The first link there is Eugene's Froyo That Does Not Brick, but it doesnt work that well as a driver. As an eraser its great though! The second link is the Froyo JK2 leak, with fixed recovery and already rooted. If the first one didnt, the second flash will definitely put you back on Froyo bootloaders.
Thats my whole secret to keeping a clean phone and wiping out any ghosts. You can proceed from there in your desired direction (back to ZD or GZ preferrably) in a safe manner. Its always worked for me to clear up any oddness, and literally takes 15 minutes tops once you have the files downloaded.
Click to expand...
Click to collapse
I've tried that before. Eugene's Vibrant_Full_Froydin_AND_2E_Recovery_+SD_Fixed (Froyo JK2 leak) is the one that lets me load the system all the way through (better than running stock JVF which only gets me to the logo and then gets stuck). The internal sd card problem remains however. I get the "Blank internal sd card" notification. The phone can't function properly.
EDIT: I finally got the external sd card to work. Is there any program for me to fix my internal sd through my external sd card?
I'm having similar problems. Flashed back to stock Froyo using Heimdall (Mac only here), everything seemed fine, but when it all came back to life, I have no service and my Internal SD card is blank and cannot be reformatted.
It won't mount in the recovery tools, and so unable to format.
Any thoughts on how to restore functionality??
Bump. I'm still trying to get my phone working again. Thanks in advance!
If it just "happend" one day, then you're looking at a hardware failure. Flashing firmware can only make it worse.
xoxo1001 said:
I've checked the other threads for solutions and I've tried many different things today but my phone still doesn't work, so I guess I should make a thread and ask you guys directly.
Ok, so my phone stopped working last night. It was running stock everything. Only upgraded to Froyo through Kies Mini a long time ago. Anyway, when I powered up the phone, it gets to the Galaxy S logo and then the screen dies. It's technically still on, since the four keys light up when I tap the screen. I took the battery out for a bit and put it back in, same thing. Logn story short, I tried to odin it back to stock JFD this morning and it didn't change anything. The screen goes to black right after the logos. Then I tried Eugene's Vibrant_Full_Froydin_AND_2E_Recovery_+SD_Fixed. It sorta worked. By that I mean, the phone loads up the OS and I got the home screen, but now it doesn't recognize the internal SD card. In fact, the notification gives me "Blank Internal SD card." In the Settings area, the phone storage read as either unavailable or 0.0 space. I tried to odin back to stock but then it gets stuck on Galaxy S logo again. I've tried this back and forth multiple times and it's still the same. Either it gets stuck on the logo or it doesn't recognize the internal sd card. I've tried it with repartition on and repartition off, but no difference.
So, are there any trick to fixing this? Thanks in advance!
Click to expand...
Click to collapse
'I had a similar problem but later learned tht the SD card was actually damaged some how during flashing'
so try using a new SD card and Odin back to stock
I already tried downloading it from the original post, but it says daily traffic limit reached. Already tried waiting two days, but the error remains. Could someone please upload it somewhere, or provide a working link? Help would be much appreciated, as Adam's method is my last hope.
Thanks in advance!
palbence said:
I already tried downloading it from the original post, but it says daily traffic limit reached. Already tried waiting two days, but the error remains. Could someone please upload it somewhere, or provide a working link? Help would be much appreciated, as Adam's method is my last hope.
Thanks in advance!
Click to expand...
Click to collapse
http://kat.ph/adam-outler-s-ubuntu-t...-t6208816.html
torrent
This is how I downloaded it a few weeks ago.
Good luck!
Thank you for your help, I managed to download and run the ubuntu recovery, but now I ended up being stuck at the "n" read forever screen. I already tried the 8 failed boots method, nothing changed. Any idea what to do now?
ouch.
It ran without a hitch for me (after I got it on card big enough to handle, sheesh). Head back to Adam's thread, I'm sure someone will be able to help you there.
After you put in the card you made, you did see ubuntu running, right?
When booting from Adams recovery sd it will take a long time before you even get to the 100 second countdown timer (about 5 MINUTES). It takes an additional 20 minutes or so to format, write zeros to all the partitions snd rewrite each with data for 1.4.0. THE SCREEN WILL TIME OUT at some point in the process and i found you can just press the N button to turn it back on to monitor progress. When it is finished, the script will tell you to take out the SD and then the tablet will reset and go into a recovery and reset the firmware. I had an issue reregistering when the B and N screen came up so i skipped registration by holding volume up and touching the left and right corners of the screen at the play video screen. A factory button appears and after pressing that, you hold volume up and touch right corner of screen and an option to skip Oobe registration appears. Skip oobe and then you are ready to root. Personally i made a CM7 root card and booted with it. I THEN INSTALLED CWM with Indirects recovery tool apk. Then you can flash Cm9 to the internal and use cyanoboot to chose between the internal cm9 or sd cm7. Good luck!
palbence said:
Thank you for your help, I managed to download and run the ubuntu recovery, but now I ended up being stuck at the "n" read forever screen. I already tried the 8 failed boots method, nothing changed. Any idea what to do now?
Click to expand...
Click to collapse
If you have a brick try my unbricking method http://forum.xda-developers.com/showthread.php?t=1562130
had to go to virtual box
my problem was not the downlaod. i got it from the OP link w/ no prob. but w/ windoze, the microhcsd did not work. aarrgghh. adam kind of responded to that conplaint by saying 'windoze has problems and linux does not'... so i am like a big zero w/ ubuntu but what the hay. i dnlded oracle's virtual box and got it going. then i dnlded ubuntu but did not like its layout and looks so i dnlded mint and that seemed better ( for me ). within mint, i made the sd using a cheapie 16GB from amazon. you do have to have patience and there is very little feedback. well, with the new sd, the un-brick process worked. just pluggin it into the pc and it ( slowly ) gets going. you think its still dead and will not work and then it comes to life and you see ubuntu graphics and its running its script. there is a progress bar of sorts. then you power on and it is at 1.40 and you have to skip over the OOBE ( out of box experience )
.
gotcha for me was that it was NOT powered off when you think it was powered off. the screen has a black / blank mode and then the 'real' black / blank mode. if you hold the tab at a really sharp obtuse angle . . . you can see that it is 'on' when you thought it was 'off'. with no cable attached, press and hold the power button for five seconds to make it off-off...
Hi, think I know a bit of what I'm doing, read all I could, etc.
W7 laptop, SD SD with HP format, RHOD100.
(Can get serial # from Nexus 7 with ADB install, can reflash WM from SD, etc)
USB cable to computer.
I can 'flash' (update image) new Android RHODIMG.NBH to phone, I get filled progress bar, and then Update Complete, UPDATE SUCCESS and phone will not cut off (stuck in bootloader?) I do manual reset button.
Then I can 3 finger reset (SEND, END, + ON) to get tri-color, and then VolUp option. (So far, this is just like WM reflash) I push VolUp.
Screen goes to "Restore... Waiting for completed" and unfilled progress bar - and that's it. At this point, other resets can get me tricolor with USB, white HTC with NO radio, version, etc, and this waiting screen.
(I can use same process and get right back to WM.)
Where is my error?
THANKS!!
You can't flash Android with USB. SD is the only way to flash the NBH for Android.
Do you see the blue boot loader screen?
(I've also got the image for android on SD, just not getting there...)
I never get a completely blue screen (get tri-color), I go exactly as far as I mentioned - 2nd progress bar with no progress.
Using these instructions and downloaded files... http://forum.xda-developers.com/showthread.php?t=1566955 stuck at step 10 or 11 or so.
THX
tshephard said:
(I've also got the image for android on SD, just not getting there...)
I never get a completely blue screen (get tri-color), I go exactly as far as I mentioned - 2nd progress bar with no progress.
Using these instructions and downloaded files... http://forum.xda-developers.com/showthread.php?t=1566955 stuck at step 10 or 11 or so.
THX
Click to expand...
Click to collapse
Did you unlock your phone?
Unlocked long ago, olinex or something similar. Been trying various roms for years with no problems, played with SD android for awhile, wanted to try NAND.
I have good SDK, etc, put image on SD, phone finds it, first loading bar looks great, reboot, second loading bar never starts.
Do you guys never see 2nd progress bar ("Restore... Waiting for completed") - is my fault before that? Is there a better set of instructions that what I'm using?
tshephard said:
Unlocked long ago, olinex or something similar. Been trying various roms for years with no problems, played with SD android for awhile, wanted to try NAND.
I have good SDK, etc, put image on SD, phone finds it, first loading bar looks great, reboot, second loading bar never starts.
Do you guys never see 2nd progress bar ("Restore... Waiting for completed") - is my fault before that? Is there a better set of instructions that what I'm using?
Click to expand...
Click to collapse
So you flash the NBH... and it's never flashed successfully? Not sure what you mean by "second progress bar"... there's only one when you flash the NBH via SD.
OK - now we're talking!
I definitely see a second progress bar that never starts under "restore, waiting for completed" on a whitish screen as above.
Is the RHODIMG.NBH from that instruction set the correct one?
I will try downloading again and moving to SD again in case of file fault.
THX for helping...
tshephard said:
OK - now we're talking!
I definitely see a second progress bar that never starts under "restore, waiting for completed" on a whitish screen as above.
Is the RHODIMG.NBH from that instruction set the correct one?
I will try downloading again and moving to SD again in case of file fault.
THX for helping...
Click to expand...
Click to collapse
I guess I'm still not following.
Have you ever flashed via SD? The process is really quite simple. Just place the RHODIMG.nbh file at the root of the SD, and put the phone in bootloader mode. It should pickup the file and offer to start the flash.
Yes, and since I tried this I have also successfully flashed back to WM by SD, numerous times now.
I am not successful at flashing and then loading the small .nbh for Android
Am trying new download now...
tshephard said:
Yes, and since I tried this I have also successfully flashed back to WM by SD, numerous times now.
I am not successful at flashing and then loading the small .nbh for Android
Am trying new download now...
Click to expand...
Click to collapse
So to get things straight, you downloaded this file and put it on the SD. Now when you load it, you won't be able to get it to load using the recovery. Recovery is for Windows original files only as far as I get that.
Instead you just press and hold the volume down button while powering on the device. After you see the tri-coloured screen you can let go. You will get prompted with a white screen. On this you'll see:
Now the rhodimg.nbh is detected and by pressing the power button you can flash it. (or press volume down to cancel and return to the tri-coloured screen) After it said OK/Succesfull you remove the battery or press the reset button, after this there's no further steps, you just let it power on and you get a BLUE screen with some white texts called the LK bootloader / minipooploader by [ACL]
Here's a short instruction video to explain what I typed.
Al - THX for joining in!
That's the file (only one I can find), I do exactly as described, but at "battery or press reset" I get a white HTC (like would have 4 files listed on WM) that cuts off after 4 seconds, a three button push gets me a reload with no progress.
I made films...
files on SD - http://www.youtube.com/watch?v=ZbK8aWh9378&feature=youtu.be
process - http://www.youtube.com/watch?v=01Uq1dqtydE&feature=youtu.be
that show reset and 3 button reset (USB in here, same USB out) (Also, fresh solo Task 29 from RUU advanced...)
Any clues anyone?
(Could RHODIMG.NHB be bad on server?)
Not sure why you are doing a hard reset after you load the android NBH. Skip that.
Just let it load.
The instructions and post 11 above indicate reset.
I'm trying just leaving it at the Update Complete UPDATE SUCCESS progress bar now....
Nope - that just sits there after RHODIMG.nbh - OK, OS - , and UC/US,...
tshephard said:
The instructions and post 11 above indicate reset.
I'm trying just leaving it at the Update Complete UPDATE SUCCESS progress bar now....
Nope - that just sits there after RHODIMG.nbh - OK, OS - , and UC/US,...
Click to expand...
Click to collapse
Just a regular reset, not a hard reset is what I think they are meaning. I have lost count of the number of times I have loaded android onto my device, and I have never ever done a hard reset after the initial nbh load.
When I load android on my rhod400 it always hangs at the update success screen from the initial nbh load. Try just popping out the battery (and putting it back in) and letting it boot normally after you see the update success screen from the android nbh. You should get to a blue boot loader screen.
That (simple on or reset button) after android.nbh success gets me:
a white screen with HTC (that would normally [WM] fill in with b,r,s,something - 4 ?file versions) for 4-6 seconds, and then off and blank. Battery yellow will cycle 80% on. Subsequent on times out (HTC white) and off as above.
Have you loaded recently with the current file?
tshephard said:
That (simple on or reset button) after android.nbh success gets me:
a white screen with HTC (that would normally [WM] fill in with b,r,s,something - 4 ?file versions) for 4-6 seconds, and then off and blank. Battery yellow will cycle 80% on. Subsequent on times out (HTC white) and off as above.
Have you loaded recently with the current file?
Click to expand...
Click to collapse
Unless you're using some old file, yes I have flashed recently. Just flashed a TP2 the other day...
https://code.google.com/p/rhodium-nand/downloads/list
That's where you're getting all your NAND downloads from yes? Please ensure you have the newest stuff. This part is really the "easy" part. Just need to be SPL unlocked, then flash .nbh via SD. Seriously, that's the easy part... the hard part is getting your computer to recognize the phone in fastboot mode, and flash the recovery image - that's the step I always seem to have issues with.
This is an video from a Rhod 210, but it gives you a good idea what to expect. Useful info starts around 7:00.
http://www.youtube.com/watch?v=_qNCHqGPofI
Redid it all - exactly per video... fresh downloads. etc...
Where video shows carrier splash, then 4 circular buttons, and then blue with text, I get white HTC for 5-6 seconds and then off.
Just to be sure, since original thread evolved...
Mine is a RHOD100, SEA Roms work fine, SPL 0.85 olinex (AT&T freqs, they think it's a Tilt 2)
Seems it was only some phones early...
tshephard said:
Redid it all - exactly per video... fresh downloads. etc...
Where video shows carrier splash, then 4 circular buttons, and then blue with text, I get white HTC for 5-6 seconds and then off.
Just to be sure, since original thread evolved...
Mine is a RHOD100, SEA Roms work fine, SPL 0.85 olinex (AT&T freqs, they think it's a Tilt 2)
Seems it was only some phones early...
Click to expand...
Click to collapse
I did not intend for you to follow the video to the letter. It was just to give you an idea what to expect.
Hello, first post here.
I am in some hot water. I got a nook tablet BNTV250A. Put CM7, etc on it. I don't know exactly what I did but now it ONLY boots into CWM.
It will not load an image off the sd card. I have tried Ray Waldo's fix, the Ubuntu fix, repart, and about half dozen others. All to no avail.
The only thing this POS does is boot into CWM (5.0.2.8). It can't mount any of the cache/recovery folders. When I tried mounting any other (/rom, /bootdata, /factory, etc) it just errors. I tried reflashing CWM, error. Tried relfashing CM7 (since that is the only version it will take), says complete then boots back into CWM. tried booting with and without it plugged into the computer, goes into CWM. In other words I cannot do ANYTHING.
I have been at this for 4 days. I am at the end of my rope. Any help would most greatly be apreciated.
Thanx in advance.
Veaceonee said:
Hello, first post here.
I am in some hot water. I got a nook tablet BNTV250A. Put CM7, etc on it. I don't know exactly what I did but now it ONLY boots into CWM.
It will not load an image off the sd card. I have tried Ray Waldo's fix, the Ubuntu fix, repart, and about half dozen others. All to no avail.
The only thing this POS does is boot into CWM (5.0.2.8). It can't mount any of the cache/recovery folders. When I tried mounting any other (/rom, /bootdata, /factory, etc) it just errors. I tried reflashing CWM, error. Tried relfashing CM7 (since that is the only version it will take), says complete then boots back into CWM. tried booting with and without it plugged into the computer, goes into CWM. In other words I cannot do ANYTHING.
I have been at this for 4 days. I am at the end of my rope. Any help would most greatly be apreciated.
Thanx in advance.
Click to expand...
Click to collapse
I hate to be the bearer of bad news, but I have seen instances (really only one in hundreds of NOOKS reworked)
where the flash memory gets corrupted to the point where its read only.
see: http://forum.xda-developers.com/showthread.php?t=2663470
if the RayWaldo fix and the Ubuntu dont seem to have any effect, you may be at that point.
The Ray Waldo thing has worked for me hundreds of times.
I finally just gave up on mine and used the good screen on one with a broken screen.
sorry...
dam..that sux..was hoping.:crying: