Database Develop

[Q]

Ok, so I promise I've tried to search for a solution, but I really don't even know where to start. Please let me apologize if this has been discussed at exhaustion, but the guys I've asked so far have not seen this issue. Perhaps some of you have.
I'm going to list EVERYTHING I can think of that I've done. Please tell me what I've done wrong.
1. After picking up my NC last night, I tried running the Non-Root SDcard method of running Froyo to try it out. I tried running Rom Manager but wasn't able to do much. I tried Flashing CWM and feel that might have been a mistake. Hopefully, someone can reassure me that was not a problem.
2. I was unable to get GApps (Market most importantly) to show.
2a. After Flashing CWM and removing the SD card, I found that if I tried to force the 1.1.0 update, it would error out and put me into Recovery. That was something I assumed would not be possible, since I was of the understanding that the Non-root SDcard method was restricted solely to the SD card and didn't actually touch the Onboard memory.
3. Assuming the SDcard method might be limited to not having Market access and was more of a pre-root preview. I moved on to actually Root my NC. I did the whole, SD-image method and let my NC auto-reboot. The method I followed didn't mention anything about skipping the Google Account step. So, I tried that with some difficulty and had to back out. I never tried the whole Youtube account sync. I accessed the Market, but none of my downloads will actually go through. Tried multiple reboots, but no luck.
4. I tried to root again to see if something went awry. This time, I didn't have to go through the Android Setup steps??? But, I went ahead and logged into YouTube. Then, I went to Gmail Accounts>Account Setting, but each time it just causes my NC to reboot. Market still doesn't actually download anything.
I know it probably seems like I'm trying to many things, but I'm trying to discover the source of the problem, but behind each corner is another problem. I can't think of anything I'm doing wrong. I'm becoming very agitated. This was supposed to be a simple process, but it is not at all right now.
5. Now, as a last ditch effort, I tried to UnRoot my phone with the 8-Boot-Interruptions method. Problem is, instead of restoring the device to stock, it puts me back into CWM recovery.
Is it possible that Flashing CWM has irreversibly imprinted itself on my NC and I can not get past it to actually move forward with the Market and such? Is there any way to reverse the Flashing of CWM?
Thanks a ton in advance.

My guess is CWM writes to the system folder no matter if it has booted from SDCard or not...
Try this:
http://forum.xda-developers.com/showthread.php?t=931720
I believe that is the correct set of instructions, if not, my apologies.
migrax

For reference, I'm running B&N 1.0.1 and used auto-nooter-2.12.25.

It sounds like you might want to navigate overt to the development forum and do a bit of reading. I'm unsure why you flashed CWM onto your nook, but everything is easily fixable. It really depends on what state you want your nook to be in when it's all said and done. There's a thread in the development forum about restoring back to stock, doing so will remove cwm and let you start over. This is probably the best way to go as the current state of yur nook is questionable. Once you have stock working your best bet for the most functionality is rooting, and the easiest way to do that is autonooter. Definitely read the threads more than once before attempting any of this so you will know what to expect before it happens.

migrax said:
My guess is CWM writes to the system folder no matter if it has booted from SDCard or not...
Try this:
http://forum.xda-developers.com/showthread.php?t=931720
I believe that is the correct set of instructions, if not, my apologies.
migrax
Click to expand...
Click to collapse
Just read through that link. Looks very promising. Dont think I'll have a chance to do it tonight, but I will report back ASAP. I'm hoping to get back to stock and then go straight through the root process as intended. I really feel that my unintentional CWM Flashing experience is the root of my frustration.
I'm hopeful that this will be the end of it.
Thanks again.

Thanks a BUNCH!!! It all worked out. Getting the .img out of the .tar.gz was the most difficult, but once I figured out how to use 7-zip, all was well.
I'm now rooted and have full Market/Gmail access. I'm a very happy boy

Need help "read only?"

Hey Everyone,
I think someone, somewhere has talked about this before but here goes;
cdzo72 and I are having similar issues. We can get to fastboot and adb with all the corrected drivers and what not, but anytime we try to flash cwr or any of the other images, it tells us that it sent successfully then when we reboot it reverts back to the original (corrupted) image. It seems to be like the internal SD card is defaulting to read only and we can not get it to "remember" the changes we made to the images. Does anyone know if there is a way to check or change read write access through NVFlash? Here are some quotes with what we have been dealing with:
cdzo72:
"For some wacky reason, aside from going back to stock at each reboot, the Streak is also erasing any files I place on the internal SD card. So, I placed the gingerbreak apk on an external sd and installed it from there using quickoffice as my file browser... to my excitement it seemed to go off without a hitch until I rebooted.... now once rebooted everything force closes, including the wizard and the home launcher... I'm worse off than I was before....
Is there anywhere I can find the OTA update.pkg so I can flash that from recovery?
UPDATE:::
Well last night as a grasping attempt I deciced to go the NVFlash route. I was sitting on pins and needles waiting for all the files to download. I was elated when I was able to correctly install the drivers and you can imagine my joy when it went off without a hitch (so I thought). I booted up and entered in all my info and started using my Streak, then I shut it down just to evacuate my fears... When I booted up I was greeted with the setup wizard once again as if the Streak had never been used.... I literally shed a tear....
I'll be bald in a couple of days if this keeps up....."
"Originally Posted by bigmac124
You know, I have been thinking about this alot today. I am pretty sure people have talked about it before but I think our internal SD cards are stuck on read only, because no matter what we flash on; .img, adb push, or even Nvflash, it reverts back to the same(buggy) original image. I wonder if there is a away through nvflash to make sure we have read write access. Anyone have any ideas or know about NVflash for the d7? I'm at a lose here
Sent from my HTC HD2 using XDA App
I tend to want to agree with you bigmac and maybe someone can point us in the right direction to change this.
Through all the flashing I've been doing something has changed, I can now flash with fastboot and the Streak takes the command, but when I reboot it comes right back to how it was.
I've flashed CWM and it didn't stick, I tried to flash Steve's ROM through fastboot and it just hung up, I did the NVflash and it didn't change anything either"

mine did that several times on stock, but if you skip it all, the info is still there though somehow corrupted (everything on the internal sd force closes). Just a couple of days ago I put on dj steve's custom 1.3 a couple of days ago. If I get that error again, back to stock and back to dell it goes and I will try to get out of my t-mobile data contract since it will be the second broken device in 2 months time since I'm mostly using it for watching movies anyways.

[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.

Revolution Problems

Ok, so i've spent a few hours at this already but let me give as much info as I can. I have read through many threads searching for info. I am no expert but I have had OG Droid, Incredible, and currently Thunderbolt all rooted so I am a novice.
This is my GFs phone and was previously bone stock, never rooted, no Roms nothing. So she gets the update recently and clicks yes and that is where the trouble began, phone constantly reboots and will not go past the language/activation screen. It never once went past that first screen, and she tried the hard reset and the battery pull.
So this is where I took over. I retried the hard reset (power + vol down) and also the battery pull. I also tried to activate in numerous other languages, all cause a reboot.
As per
http://forum.xda-developers.com/archive/index.php/t-1208713.html
I was finally able to get past the activation screen and make some progress. However after about a minute the phone always reboots, no matter what it is doing. I hard reset in the settings menu and that did nothing.
I next followed
http://forum.xda-developers.com/showthread.php?t=1326347
and got the phone rooted.
Installed
http://forum.xda-developers.com/showthread.php?t=1144951
and than installed CWR 4.0.0.4 ? (not sure the version whatever it comes with) Tested recovery and it it seems to stick even after rebooting several times, which the phone automatically does (maybe its a feature and not a flaw?) So I was unsure of what version of Android was even running because the phone will not allow me to go into about phone it always force closes *com.android.settings* but I figure what the heck and try my luck with a new Rom. I decided on
http://forum.xda-developers.com/showthread.php?t=1326542&page=11
So I did the usual. Rebooted into recovery, made a nandroid backup, wiped data, cache, davlik and even did /system for good measure. Than did the install and upon first boot all the same problems are there. It will not activate from the screen, it just reboots the phone eventually. I used the same method above to avoid the screen and now it will boot up and the phone is in fact running an AOSP Rom but it still reboots after about a minute. Oddly enough it also continues to refuse to let me open About Phone, in the settings menu. I also for good measure went into recovery and wiped everything again and also tried fixing permissions in recovery, all to no avail.
At this point I am thinking it is perhaps just a hardware issue, although the phone does not reboot itself in recovery. I would be willing to try a different Rom, however I don't think it would work. I am wondering if anyone has any other suggestions? Should I try this?
http://forum.xda-developers.com/showthread.php?t=1120062
Other info:
What does work is wifi, so i can get on the internet briefly. I can connect to google and get apps from the market.
I am leaving this for a few hours or I may have to re-title the thread "How do you put the LG Revolution back together after throwing it against a wall?"

Currently I'm sad face that you rooted and installed cwm but I think the update bricked it personally. Hopefully S.Meezy will see this as he has stock recovery. I would say just get back to bone stock and get it replaced. If anyone else knows how to get it fixed, my best guesses would be mt or S.Meezy, though adb that might work. I hope it all gets figured out. Someone needs to post stock GB without data or anything for people to flash to if need be. That might fix your issue.

My suggestion is to get the recover the whole phone...
http://forum.xda-developers.com/showthread.php?t=1211295
follow that but use the v6 TOT file. That will revert the phone to out of factory new, with updated radios. If you still have the issue then I would contact Verizon.
If everything works then you can re-run the update to Gingerbread.

Could be a long shot but I remember seeing something a little way back in another forum where a user w the same problem accidentially resolved his issue by restarting w the sd card out. For him it turned out to be a bad or incompatible sd card at the root of the problem.
If you have one in, pull it and restart. Hope thats it for you...
Sent from my VS910 4G using XDA App

Well i'm a glutton for punishment so i'm back.
I didn't want to bother with rooting it honestly but I did it out of desperation, figured a total wipe + brand new Rom would surely fix things.
Going to attempt the full recovery.
Tried pulling the SD card, than just the Sim card and finally without anything and none of the combinations worked.

Have you tried downloading a stock ROM to your PC/Mac and dropping that on your SD card and then flashing that ROM, after checking the md5? To me it sounds like your gf just had a bad download.
I think the issue is that you keep trying to flash the bad bits. Just my two cents...
Sent from my Dell Streak 7 using Tapatalk

Honestly you really need to try reflashing the entire phone with one of the TOT files. At this point to me it is clearly not the ROM that is installed. Restoring the phone with one of the TOT files will cleanly overwrite everything on the phone. Takes about 20 minutes or so after you have the program installed and recognizing the phone. Do it and post back.
H.

Haxcid said:
Honestly you really need to try reflashing the entire phone with one of the TOT files. At this point to me it is clearly not the ROM that is installed. Restoring the phone with one of the TOT files will cleanly overwrite everything on the phone. Takes about 20 minutes or so after you have the program installed and recognizing the phone. Do it and post back.
H.
Click to expand...
Click to collapse
What he said.
Remember: Absolutely do not, under any circumstance, unplug/turn off your phone once you start that process. It can take awhile, and might look like it froze, but just let it do it's thang.

[Q] HELPPP Accidental internal storage wipe

ok, so i was trying to root my sprint htc one, and everything was going, ok. i unlocked the bootloader simple enough. then i wanted to back up the data, before i tried putting roms on it. well twrp kept saying i only had about 34 mb of space which made no sense since i had formatted it, and only brought back things like contacts and texts. when i checked my phone it said that i had 24gbs. so i couldnt find an answer to this anywhere so while looking through twrp i saw the wipe function. not having seen anything about it, i said, maybe if i reformat it again, itl clear up. so i hit wipe all. well after it was done it only said i had 1.2 gbs, so still confused i went to load my normal os, well i cant. because wiping everything meant the system data the os is on. i spend hours trying to find a fix, as im only able to go between the bootloader and twrp, and i see a sideload option, and after following the steps, i attempt to sideload. everything is going well. Viper looks like its about to install, until at the last second it says install fail. but now i cant even access the recovery menu. literally stuck in the boot loader option. all my contacts and pictures and stuff are backed up, so i have no problem formatting my phone to scratch if it means fixing this, but can anyone point me in the right direction???? i cant find anything on this, ive been searching through this site, and some people with similar issues solve it by sheer luck, but i have no rom back up(since i was trying to do that when i got into this problem) please please help!!!
**edit** i was able to get into twrp by using the recovery steps, though im just back to square 1. is there a guarenteed reliable sideloader that can work?

Look HERE
Try the latest RUU first if it does not work follow the guide from the beginning it will get you fixed up.

raynefr said:
ok, so i was trying to root my sprint htc one, and everything was going, ok. i unlocked the bootloader simple enough. then i wanted to back up the data, before i tried putting roms on it. well twrp kept saying i only had about 34 mb of space which made no sense since i had formatted it, and only brought back things like contacts and texts. when i checked my phone it said that i had 24gbs. so i couldnt find an answer to this anywhere so while looking through twrp i saw the wipe function. not having seen anything about it, i said, maybe if i reformat it again, itl clear up. so i hit wipe all. well after it was done it only said i had 1.2 gbs, so still confused i went to load my normal os, well i cant. because wiping everything meant the system data the os is on. i spend hours trying to find a fix, as im only able to go between the bootloader and twrp, and i see a sideload option, and after following the steps, i attempt to sideload. everything is going well. Viper looks like its about to install, until at the last second it says install fail. but now i cant even access the recovery menu. literally stuck in the boot loader option. all my contacts and pictures and stuff are backed up, so i have no problem formatting my phone to scratch if it means fixing this, but can anyone point me in the right direction???? i cant find anything on this, ive been searching through this site, and some people with similar issues solve it by sheer luck, but i have no rom back up(since i was trying to do that when i got into this problem) please please help!!!
**edit** i was able to get into twrp by using the recovery steps, though im just back to square 1. is there a guarenteed reliable sideloader that can work?
Click to expand...
Click to collapse
Do you still have the memory issue? If so, try running a RUU, and see if that fixes your problem.
If not, just use adb sideload to sideload a ROM. Then wipe everything except internal storage and install the ROM normally.
EDIT: Looks like @BD619 ninja'd me XD

BTW sideload very rarely works when you wipe your sdcard.

BD619 said:
Look HERE
Try the latest RUU first if it does not work follow the guide from the beginning it will get you fixed up.
Click to expand...
Click to collapse
hey thanks for the reply. i followed the guide and after some effort, everything seemed good, but when i was trying to load 5.03 sense 6 rom, i got to the htc start up, then it defaulted back to the bootloader..i went with the deodex version of the download, should i try the odex? or a different version all together?

and now it doesnt want to boot into recovery mode either! going to try redoing the steps, but i just cant figure out what the problem is
**edit* i cant fix twrp. the title loads, but thats it. endless loop

ok i got it to seemingly work. restoring content now. sat in fron of my pc for 15 hours...not even sure where imat or if i got any closer to rooting..smh..thank you everyone who helped. if anyone comes across this
to get out of the endless cycle of recover/loading screen.. delete your twrp, or whatevs your using. even if you have the latest, just redownload it. worked for me. i guess there is a huge difference between the odex and the deodex.i had figured deodex was a more refined version, but maybe it had more complicated software. in any case, if you are at a point where you dont have a base os, and you make it this far, go with odex, it worked for me. htc is big on back up, so i was more worried about having to scrap my phone then i was regaining data, especially with most of my stuff backed up to google drive. hopefully you guys are careful.
now...about this backup issue i had in the first place. how can i fix the storage issue? i have a 32 gb phone minus partition leaves me with over 24gb..why is it going based off the separate phonememory slot? why cant i change it?