Database Develop

:( Random Problem......Help, Please! :(

Right then,
Already searched on this one and not yet seen a solution to my problem. I own a T-mobile G1 and my phone crashes after it has booted up, or will not boot up properly: either the T-mobile G1 screen stays on for 5-6 seconds then I get a black screen, or it boots up then freezes with a black screen, or it won't switch on at all.
I currently have:
T-Mobile G1 with Root
2.22.19.26I radio installed
1.33.2005 "Death" SPL installed
Amon_RA's RA-v1.2.3 recovery installed
MghtyMax "What a feeling" 1.9.1 Hero ROM installed
fat32, ext3 and linux-swap on class 6 8Gb sdcard
I can get to recovery (sometimes.....it doesn't always get that far) and fastboot, so hopefully it's not bricked. I have already tried wiping (ALT+W) and formatting the ext2 (from the option in RA's recovery menu and also via console); removing all the partitions and starting afresh recreating them (after removing them of course), and as I can get to recovery (sometimes) I have tried flashing a different ROM (SENSEhero 1.3.3 unthemed) but still get the same issue.
I have flashed quite a few ROMs recently and not had any issues, so any help on this one would be most appreciated!

matthenry87 said:
Check your SD Card. My buddy had the same "black screen" problem and I discovered his SD card was slightly popped out. I clicked it back in and boom. problem solved. For him at least!
Click to expand...
Click to collapse
I'll give it a go..........

Seems like it is a problem with the sd card. Removed it and plugged it into my pc via a card reader and it couldn't recognise the card. Amazon here we come! Thanks for the help!

Give us a logcat from ddms.bat.

Binary100100 said:
Give us a logcat from ddms.bat.
Click to expand...
Click to collapse
he already solved it....

Not again......
B-man007 said:
he already solved it....
Click to expand...
Click to collapse
Okay,
It is still doing it and I'm not sure if it is the sdcard. Tried a different card I have at home and I still have the same problem.
I'm also getting extra coloured pixels appear on the T-Mobile G1 screen.
I can still get to bootloader and recovery (sometimes.....).
How do I pull a logcat?
MrZ

adb logcat
you can also run ddms.bat and get the log from there

misterzak said:
Okay,
It is still doing it and I'm not sure if it is the sdcard. Tried a different card I have at home and I still have the same problem.
I'm also getting extra coloured pixels appear on the T-Mobile G1 screen.
I can still get to bootloader and recovery (sometimes.....).
How do I pull a logcat?
MrZ
Click to expand...
Click to collapse
well trying to solve the problem by trying another sdcard is not a fix... since some roms do rely on the ext contents for things to work properly. what i suggest is having the 3nd card completely wiped and partitioned correctly..then move a rom onto the card and flash like u normally would.

Thanks for the info.
That was one of the first things I tried. I managed on Tuesday to install AOSP_ADP_1.6_r1.2_DRC92_rooted_base_v2.zip, and it worked for a short period of time, but it now crashes or doesn't boot up.
Getting worried now.......

misterzak said:
Thanks for the info.
That was one of the first things I tried. I managed on Tuesday to install AOSP_ADP_1.6_r1.2_DRC92_rooted_base_v2.zip, and it worked for a short period of time, but it now crashes or doesn't boot up.
Getting worried now.......
Click to expand...
Click to collapse
Something may be wrong with the phone itself
Try flashing the RC29 and seeing if the problem persists. if it does, then its probably a hardware problem. You can talk to tmobile or HTC about it and see what they say

B-man007 said:
Something may be wrong with the phone itself
Try flashing the RC29 and seeing if the problem persists. if it does, then its probably a hardware problem. You can talk to tmobile or HTC about it and see what they say
Click to expand...
Click to collapse
Thanks for that. I assume if they ask me to return it to them to reflash the original bootloader and recovery screens so that they cannot tell I've been "playing" with my phone...

Haha well once you flash the RC29 you wont have to because it will all be stock. If Tmo replaces phones for missing text messages, which is for sure a software problem (yes ive seen them do this), then they definitely will for this issue.

B-man007 said:
Haha well once you flash the RC29 you wont have to because it will all be stock. If Tmo replaces phones for missing text messages, which is for sure a software problem (yes ive seen them do this), then they definitely will for this issue.
Click to expand...
Click to collapse
If I flash RC29 (or RC7 for me) will this brick the phone as I currently have Death SPL. I'm sure I've read that somewhere on here?

Unrooted.......
I've now reverted back to RC7 (as I'm in the UK) and all seems okay....for now.
I will run it like this for a day to see if it still crashes or does anything funny. If it doesn't, I will re-root and start again!
Thanks for the help with this. I will update if it continues to crash.

Alright lets hope this fixed it lol
also it may be a little late but you should be fine flashing the RC7 as it replaces the SPL and radio

EVT Board.........
B-man007 said:
Alright lets hope this fixed it lol
also it may be a little late but you should be fine flashing the RC7 as it replaces the SPL and radio
Click to expand...
Click to collapse
Now this is interesting, RC7 was fine. Re-rooted the phone, fine. Flashed AOSP_ADP_1.6_r1.2_DRC92_rooted_base_v2.zip ROM, fine. Flashed Amon_RA's v1.2.3.img recovery, fine. This is where it gets fun, partitioned my card within the recovery to FAT32, ext2 and linux-swap, then rebooted into recovery. The phone crashed. So, I thought there must be an issue with the sdcard. Put in the stock 2Gb card with the RC7 DREAIMG.nbh file on and pressed camera+power to go back to RC7. It came up with an red code 00058002, then went back to the bootloader screen. It stated at the top that it was an EVT board. Searched all of the Dream Q&A section for EVT and absolutely nothing. Tried going into bootloader again and that screen started to warp and the graphics and pixels started to jumble up.
Any ideas?

wow.....it changed board types on you?
did you manage to flash cyan at all before that happened?
you should flash cyan and boot on it before flashing amonra's recovery.
you can then flash the recovery then partition the card and wipe just to be safe

B-man007 said:
wow.....it changed board types on you?
did you manage to flash cyan at all before that happened?
you should flash cyan and boot on it before flashing amonra's recovery.
you can then flash the recovery then partition the card and wipe just to be safe
Click to expand...
Click to collapse
I flashed the AOSP_ADP_1.6_r1.2_DRC92_rooted_base_v2 ROM and booted it up fully. Then using the Terminal Emulator within Dev Tools I flashed Amon_RA's recovery. All went well until I partitioned the sdcard. It won't boot up at all into the home screen or recovery, just bootloader, although it did this before when it first started crashing. I'm gonna leave it tonight and try again tomorrow.
Do you know anyone else on here who has any idea on this one? Seems like I'm the first!

This is probably an issue with the recovery itself...though ive never read about anything like your having.
ill bump this thread and see if anyone can help...maybe david can (ill tell him to get on here)

why dont you give a differant recovery image and dont try to partition just try with a fat32 sdcard on a cyan rom or something see what happens with that

How to do Linux-swap partition?

I have a 4gb card with 450mb(or something like that) assigned to A2SD. I did the A2Sd with the one click system in the recovery menu but now i would like to put in a linux swap partition so my G1 can have access to more ram. How would i go about this. i have seen other tutorials do it but they all did A2SD and the linux all in one swoop. I just want to do linux-swap. Thanks!
all i really need is someone to direct me to a tutorial, btw im running the latest cyanogen build.

Just a few days ago, I did the same thing. After seriously bricking my phone, I realized how to do it. I found it easiest to just back up everything on your sd card, then follow the instructions at
http://wiki.cyanogenmod.com/index.php/Apps2SD
from the beginning. Then just pull everything back. The first boot up took a while, but it works great.
I tried just adding the partition, but it locked my phone at the boot screen. I had to do it this way to get my phone functional.

dsipma said:
Just a few days ago, I did the same thing. After seriously bricking my phone, I realized how to do it. I found it easiest to just back up everything on your sd card, then follow the instructions at
http://wiki.cyanogenmod.com/index.php/Apps2SD
from the beginning. Then just pull everything back. The first boot up took a while, but it works great.
I tried just adding the partition, but it locked my phone at the boot screen. I had to do it this way to get my phone functional.
Click to expand...
Click to collapse
Stop using old methods!!(no offense) Dont tell others that either since there are simple ways to do it
Amon_Ra made a Recovery image that makes to partition for you..So dont follow these old guides anymore.

Or you could just download the Ubuntu .iso and burn yourself a Live disc and use GParted.

Cyanogen 4.2.11.1 Issues

Hi there Android people.
I am having some issues with running the current Cyanogen *4.2.11.1*.
Phone: G1 Drea100 PVT 32B with stock 1GB SD
using anmon RA 1.5.2 recovery image
-wipe all available in menu.
-created a new partition- FAT32, Ext1 (upgraded to 4), Swap 32MB
-wiped all again.
-repair SD: ext
-flash signed-dream-devphone-userbug-ota-14721
-Once the flash above completed I did not restart, I simply flashed to update-cm-4.2.11.1
-reboot
Once it boots, my home process stops responding if I touch anything. This last for about 15 seconds, after that it seems to responds fine, but the browser and market place seems to auto-close on me from time to time, and I get random phone reboots, after a few reboots my phone simply stops turning on. I have to wait about 10 minutes to get into recovery and try to flash all over again.
I tried fix_permissions in the terminal, no luck.
I did some reading and noticed a lot of people are running different Radio/SPL versions other than stock, I am no super user, so I don't know if any of this effects ROMs, or if I should be flashing either for any sort of benefits I am missing out on? could this be the issue? Current SPL/Radio below:
HSPL10.95.3000
CDLP-4
Radio-2.22.19.261
Any input would be much appreciated.
Thanks,

D3AD PIX3L said:
Hi there Android people.
I am having some issues with running the current Cyanogen *4.2.11.1*.
Phone: G1 Drea100 PVT 32B with stock 1GB SD
using anmon RA 1.5.2 recovery image
-wipe all available in menu.
-created a new partition- FAT32, Ext1 (upgraded to 4), Swap 32MB
-wiped all again.
-repair SD: ext
-flash signed-dream-devphone-userbug-ota-14721
-Once the flash above completed I did not restart, I simply flashed to update-cm-4.2.11.1
-reboot
Once it boots, my home process stops responding if I touch anything. This last for about 15 seconds, after that it seems to responds fine, but the browser and market place seems to auto-close on me from time to time, and I get random phone reboots, after a few reboots my phone simply stops turning on. I have to wait about 10 minutes to get into recovery and try to flash all over again.
I tried fix_permissions in the terminal, no luck.
I did some reading and noticed a lot of people are running different Radio/SPL versions other than stock, I am no super user, so I don't know if any of this effects ROMs, or if I should be flashing either for any sort of benefits I am missing out on? could this be the issue? Current SPL/Radio below:
HSPL10.95.3000
CDLP-4
Radio-2.22.19.261
Any input would be much appreciated.
Thanks,
Click to expand...
Click to collapse
Why did you use "signed-dream-devphone-userbug-ota-14721"
I'm no pro but I used the base image that cyanogen recommends on his wiki page. The DRC83 defanged located here:
http://wiki.cyanogenmod.com/index.php/Latest_version#Defanged_DRC83

staunty said:
Why did you use "signed-dream-devphone-userbug-ota-14721"
I'm no pro but I used the base image that cyanogen recommends on his wiki page. The DRC83 defanged located here:
http://wiki.cyanogenmod.com/index.php/Latest_version#Defanged_DRC83
Click to expand...
Click to collapse
He used that because it is the proper image to use. A defanged file simply means that it has been rendered safe to download with no fear of infection. The link on his site is to the file used by the OP, so no worries there. Also, your radio is good, so do not worry about that either.
I have to ask, because you did not mention part of the process that should be happening. You flash the HTC image, then you do not reboot and flash the CyanogenROM. At this point you reboot. What happens? It should flash the radio, go to an HTC screen, stay for awhile, then reboot itself back to recovery where it gives a message regarding the cache being cleared. At this point you reboot for the actual boot process. Is this not happening for you?

cloverdale said:
He used that because it is the proper image to use. A defanged file simply means that it has been rendered safe to download with no fear of infection. The link on his site is to the file used by the OP, so no worries there. Also, your radio is good, so do not worry about that either.
I have to ask, because you did not mention part of the process that should be happening. You flash the HTC image, then you do not reboot and flash the CyanogenROM. At this point you reboot. What happens? It should flash the radio, go to an HTC screen, stay for awhile, then reboot itself back to recovery where it gives a message regarding the cache being cleared. At this point you reboot for the actual boot process. Is this not happening for you?
Click to expand...
Click to collapse
You are correct- after flashing CM the phone will flash the radio and reboot to the recovery screen where I will reboot again. Sorry for not including that detail.

Home process hanging in the beginning is not a problem, most people have that happenning. Eventhough home screen is shown, Android is still booting up, you just have to wait a little bit for everything to finish up.
Problems with stock apps usually indicate that something went wrong with instalation of the rom (i.e HTC 1.6 rom was not installed properly) so you may want to re-flash that again followed by CM rom of your choice.
Next time you phone reboots itself, try to get a log (there's more on how to do it in Cyan's thread), it's the only way to find out what happens.
Last, but not least, stock 1GB card is not advised for swap/apps2sd because if it's slow speed (it's class 2). Get one that's faster (class 6 preffered) and try that out, it may be the source of your problems after all.
Good luck.

how do i install this Cyanogen on my G1 with 1.6 firmware ?

simple007 said:
how do i install this Cyanogen on my G1 with 1.6 firmware ?
Click to expand...
Click to collapse
http://tinyurl.com/yjuy6u3

But in all seriousness
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod
This would work. Please use search, this is such a n00b question.

Did another fresh install, so far no issues.
I will get a log the next time I install to see if I can track down the issue.
Also had time to install Enoch 4.2.11.2 theme. <3 this theme.
I will be heading to Frys today to pick up some cooling fans for the old PC, I will take a look for new mini SD
thank you to everyone that responded.

Just got home from Frys Electronics.
Purchases an A-DATA 8GB Class 6 microSD.
wiping/flashing again.
I am having a hard time learning about the swap file part of all this... I can find guides on how to create a Swap Partition, but not sure how to make it work and/or optimize it.
So I created a 32MB Swap- Previously I read the commands to enable Swap through the terminal- "linux_swap_en=1" I have used this and it does indeed turn on swap, but is there some sort of command to optimize? I believe tweaking the swap files is adjusting the "swappiness"?
The other way I enabled the Swap file was from the spare parts menu- Enabling Compache enabled my Swap file. Does this need adjustment? for size? or any other parameters? Or is this kind of an auto on for Swap?
Sorry I am a total noob, and want to know if I am missing out, I just keep loving this phone more and more.
I will be buying Cyanogen some beer soon ^_^

I've played with swap a long time ago and never quite understood it neither. As of lately, I've been running 10mb hack (in the developement section) and it works great. If you're inclined to get the swap thing going I suggest you read this thread. This will give you an idea of how to enable and tweak swap-related tasks.
Glad to hear that you have original problems taken care of (so far at least).
Good luck.

I think I just may have bricked my phone...
I did all the steps stated in my first post while flashing to 4.2.12.2 and got things going great. Flashed Enoch's Theme 4.2.12.2. Everything was rocking.
Then today, it shut it self off, I rebooted. Got to Enoch load screen then shut off, tried it again, and it won't even get past the G1 splash screen. I have had this happen a few times before, where it would power off randomly and I had to pull the battery, wait like 5 minutes and then get into recovery and clear/flash again. Now I am getting into recovery but after a minute or so it just shuts itself off again.
Can't wipe, Can't flash, cant even get into Cam+power to flash back to previous RC...
Not really sure what to do at this point...
If I do manage to get it running again, I do wonder why its doing this.
I use Cachemate to clear my catche and task killer to kill apps. Could Cachemate be the culprit in this mess, its the only app that I own that uses root? Not sure what else to blame it on other than the G1 one being one big POS and is only good if you can even get a ROM to run on it. I am 5 minutes away from ordering a Nexus.
once again thanks in advance for any input you can provide.

D3AD PIX3L said:
I think I just may have bricked my phone...
I did all the steps stated in my first post while flashing to 4.2.12.2 and got things going great. Flashed Enoch's Theme 4.2.12.2. Everything was rocking.
Then today, it shut it self off, I rebooted. Got to Enoch load screen then shut off, tried it again, and it won't even get past the G1 splash screen. I have had this happen a few times before, where it would power off randomly and I had to pull the battery, wait like 5 minutes and then get into recovery and clear/flash again. Now I am getting into recovery but after a minute or so it just shuts itself off again.
Can't wipe, Can't flash, cant even get into Cam+power to flash back to previous RC...
Not really sure what to do at this point...
If I do manage to get it running again, I do wonder why its doing this.
I use Cachemate to clear my catche and task killer to kill apps. Could Cachemate be the culprit in this mess, its the only app that I own that uses root? Not sure what else to blame it on other than the G1 one being one big POS and is only good if you can even get a ROM to run on it. I am 5 minutes away from ordering a Nexus.
once again thanks in advance for any input you can provide.
Click to expand...
Click to collapse
This sounds like a hardware issue, and not a bricking. Try a new battery, this may fix it, otherwise I am not sure.

cloverdale said:
This sounds like a hardware issue, and not a bricking. Try a new battery, this may fix it, otherwise I am not sure.
Click to expand...
Click to collapse
I will try the other battery I have at home in my other G1 and report back

D3AD PIX3L said:
I will try the other battery I have at home in my other G1 and report back
Click to expand...
Click to collapse
I tried it.
Same issue.
I did noticed that the batter pins were abnormal... One was sticking out more which was normal according to my other G1, the other 2 were shoved down. I tried to mess with the 2 to get them to pop back up to their normal position with no luck.
I am thinking about ordering a replacement.

okay, so tonight I am going to take the G1 apart and see if I can get those pins straightened out. Not sure if it will help, but its better than declaring it a paper weight.
will post the outcome.

Just out of curiousity (and I don't exactly know where I'm going with this) will your phone turn on and stay on if you plug it in (usb or charger)?

borodin1 said:
Just out of curiousity (and I don't exactly know where I'm going with this) will your phone turn on and stay on if you plug it in (usb or charger)?
Click to expand...
Click to collapse
It does not.
I think i will take both phones apart and swap out the screen since that is why I don't use the one. I watched a visual walkthrough seems easy enough
Has anyone disassembled their G1 and reassembled successfully? any tips?

Started to take apart the non-cracked bricked G1.
Once I removed the motherboard and started on the next step, I realized how bad it would be to end up getting the parts swapped and then have it not work... Put it back together and loaded up the latest Cyanogen on my working cracked G1.
*shrugs* it will do for now.
Waiting till the end of next month to order my Nexus 1, then I will have fun ripping apart both G1's and hopefully end up with one great looking, fully functional G1 to possibly sell or keep as an extra phone...
thanks to all who replied!

Stupid newbie question v. fresh 1.5 to Damagecontrol

I just got my Hero last week and using fresh kitchen, flashed to fresh 1.5.
I wanted to move up to the new damagecontrol rom, but since I used fresh kitchen to upgrade the first time. I wanted to know what I had to do. Is it just a matter of draging the dc zip to my sd card, booting to recovery and then updating (or what ever the menu says) and that be it? thanks for helping a newb

pyropup55 said:
I just got my Hero last week and using fresh kitchen, flashed to fresh 1.5.
I wanted to move up to the new damagecontrol rom, but since I used fresh kitchen to upgrade the first time. I wanted to know what I had to do. Is it just a matter of draging the dc zip to my sd card, booting to recovery and then updating (or what ever the menu says) and that be it? thanks for helping a newb
Click to expand...
Click to collapse
That will update the ROM yes. But you HAVE to wipe the factory default/dalvik-cache first. Which means you'll need to back up stuff you want first.
Going from 1.5 to 2.x isn't easy. If you have the right tools (I used Titanium backup) you can get your text messages back. Contacts will fail (unless you have them synched online) and you'll likely want to reinstall your apps.
If you're going to move from 1.5 I recommend a fresh start, don't try and restore anything and reinstall. It's a whole lot easier (I did this on my wife's phone last weekend, so I'm speaking from fresh experience). I'm sure there will be a lot of people who disagree, but it's definitely going to be better to wipe and go then try and restore it.

so do i just boot up to ra, do a wipe and then re-boot and copy over the dc zip? I have all my contacts and pics stashed away via wavesecure and I can just re sync them that way. not too worried about losing the text msgs.
also, i just added swype last night, again using fresh kitchen. how do i add those using dc?
Sorry for the stupid questions.

pyropup55 said:
so do i just boot up to ra, do a wipe and then re-boot and copy over the dc zip? I have all my contacts and pics stashed away via wavesecure and I can just re sync them that way. not too worried about losing the text msgs.
also, i just added swype last night, again using fresh kitchen. how do i add those using dc?
Sorry for the stupid questions.
Click to expand...
Click to collapse
Also I had to partition the sd card cause DC went into a boot loop till I did. Just remember to partition before moving DC 2.08.1 to your sd card or you will erase the rom.

You can probably re-add swype with Fresh Kitchen on the 2.1 ROM. If not do a search for 'adb'.
Basically you would do an adb remount, followed by 'adb push nameofapplication.apk /system/app' (this is not exact commands, look it up for where swype goes, I believe /system/app is correct, though).
For the rest:
Reboot into recovery
Do a wipe factory
Do a wipe dalvik-cache
Do a wipe SD:ext (it will fail if you've never used a2sd, don't worry about the failure message).
Then select 'flash zip from sd card' and flash the ROM you put on it.
If you're flashing the latest DC roms be aware: I've seen that take anywhere from 10 minutes to 30 minutes to boot after installation. So don't freak out. Also make sure your battery's fully charged before you install it. (The minimum is 30%, but if you have it at 100% you definitely won't need to worry about the battery when flashing a ROM).

animal7296 said:
Also I had to provision the sd card cause DC went into a boot loop till I did. Just remember to provision before moving DC 2.08.1 to your sd card or you will erase the rom.
Click to expand...
Click to collapse
Partition you mean? Shouldn't have to, to install that ROM. I installed 2.0.8 on my wife's prior to re-partitioning it for a2sd and it worked fine.

smw6180 said:
Partition you mean? Shouldn't have to, to install that ROM. I installed 2.0.8 on my wife's prior to re-partitioning it for a2sd and it worked fine.
Click to expand...
Click to collapse
Thank you. I was having a brain fart and that is what I was having problems with. I flashed the rom and it went into boot loop (about 1/2 hr) removed battery wiped and boot looped again. Finally partitioned sd and booted fine.

animal7296 said:
Thank you. I was having a brain fart and that is what I was having problems with. I flashed the rom and it went into boot loop (about 1/2 hr) removed battery wiped and boot looped again. Finally partitioned sd and booted fine.
Click to expand...
Click to collapse
Odd...but yeah I just remembered reading you had that issue. I think that dconfig might not be 100% ready for prime time, which can cause that kind of issue. But that's a guess. Seems to be a random deal, though, because it doesn't happen to everyone.

[Q] Nook Internal memory locked up

I haven't been able to find anything on this so I figured I would post. I had my nook set to CM 7.03 and for the first time decided to do a nightly build. Tried 203 and it worked okay (had fixed the density issue, etc.). It had a few too many hard lock ups so I decided to use ROM Manager to go back to my saved restore. Well, it kind of went back but it was a weird reboot. All my apps showed up but it was laggy, all my apps on the deskstop were gone, the default CM logo was there and the tool bar wouldn't load. Also, the N key stopped working. I tried a lot but eventually tried to completely gut it and start from scratch but no matter what I tried, no go.
From a 2 Gig CWR SD I tried to wipe cache, system and data but wouldn't let me do data. I tried Factory Reset and no go. It said it did but when I tried a vanilla install it went to the above load in with all my apps, same hang ups, etc.
I tried going back to 1.2 original Nook set up and it almost did but got locked in the boot up screen.
Yadda yadda yadda I finally just did a bootable SD card and that seems to work but it essentially cuts out all that original internal memory. A temporary fix at best.
Any ideas how to really gut this sucker and get back to square one??? I can't even get in through the USB because the tool bar won't load so I can't connect it. Gah!!
Any ideas would be greatly appreciated by this old noob.

fil42skidoo said:
I haven't been able to find anything on this so I figured I would post. I had my nook set to CM 7.03 and for the first time decided to do a nightly build. Tried 203 and it worked okay (had fixed the density issue, etc.). It had a few too many hard lock ups so I decided to use ROM Manager to go back to my saved restore. Well, it kind of went back but it was a weird reboot. All my apps showed up but it was laggy, all my apps on the deskstop were gone, the default CM logo was there and the tool bar wouldn't load. Also, the N key stopped working. I tried a lot but eventually tried to completely gut it and start from scratch but no matter what I tried, no go.
From a 2 Gig CWR SD I tried to wipe cache, system and data but wouldn't let me do data. I tried Factory Reset and no go. It said it did but when I tried a vanilla install it went to the above load in with all my apps, same hang ups, etc.
I tried going back to 1.2 original Nook set up and it almost did but got locked in the boot up screen.
Yadda yadda yadda I finally just did a bootable SD card and that seems to work but it essentially cuts out all that original internal memory. A temporary fix at best.
Any ideas how to really gut this sucker and get back to square one??? I can't even get in through the USB because the tool bar won't load so I can't connect it. Gah!!
Any ideas would be greatly appreciated by this old noob.
Click to expand...
Click to collapse
Are you trying to wipe everything and install with a version of CWR that is older than 3.2.0.1?

Yah I think it is 3.0.2.8. Is that bad? It is weird. Now even the "bootable" SD runs but some legacy stuff that should be there bleeds in. I think it is haunted (pics from what should be the part of the Nook not being accessed).
I am going to try the "restore Nook easily" bit and see what happens, too.

fil42skidoo said:
Yah I think it is 3.0.2.8. Is that bad? It is weird. Now even the "bootable" SD runs but some legacy stuff that should be there bleeds in. I think it is haunted (pics from what should be the part of the Nook not being accessed).
I am going to try the "restore Nook easily" bit and see what happens, too.
Click to expand...
Click to collapse
Yes, use version 3.2.0.1 and you will be able to properly wipe.