Database Users

[Q] ADB doesn't see MT4G in recovery/bootloader modes, bad eMMC, file system issues

First of all, hello. I'm new to tinkering with Android, but I've flashed firmware on dumbphones 68 ways to Sunday, so I'm not new to phone modding nor am I worried about technical answers, so fire away.
To start, this phone has not been rooted (yet) and has the stock 2.3.4 ROM.
I've screwed around for the last six hours or so in fear of bricking the phone only to realize I should have followed a different set of instructions after Step 1 of Downgrading in this guide, because now that I've read other guides, I find this one unnecessarily complicated compared to directly pushing PD15IMG.zip to sdcard.
Since I'm already calling it quits on going any farther with this tonight, I just need a few questions answered before I give this another shot.
1. Is ADB supposed to see the phone when it is in recovery or bootloader mode? When the phone is in recovery or bootloader, entering adb devices in the Windows Command Prompt returns an empty list of devices attached.
2. I have the bad eMMC in my phone. In addition, once in recovery mode and I press Vol Up+Power, I see an error message that says E:Can't open /cache/recovery/command. I also get additional "can't open" error messages when I select Wipe data/factory reset from the recovery menu:
Wiping data...
Formatting /data...
E:Can't open /data/cwpkg.zip
E:Can't open /data/cw.prop
E:Can't open /cache/cwpkg.zip
E:Can't open /cache/cw.prop
Formatting /cache...
Data wipe complete...
Are those errors a concern? Are they a product of a failed eMMC or a corrupted file system? If they are because of the eMMC, would it be safe to say that I should leave this phone alone? If they are because of the file system, what I can do to fix these errors?
3. Now that I've read other, more MT4G-specific downgrading guides, will pushing PD15IMG.zip to sdcard and fastboot take care of the "can't open" errors in question 2 as well?

you need clockwork recovery if you want to flash.
You need to downgrade then root with s-off and have eng bootloader to attempt the wipes you've been trying. I just downgraded, last night, just follow the instructions. It's really easy. don't see how you can brick the phone while downgrading unless your phone dies during the flashing step.
Btw you shouldn't worry too much about the bad chip. Both good and bad have been known to brick. All bad chips aren't bad, it's only more susceptible to bricking. I have a bad chip and been flashing since forever
Sent from my HTC Glacier using XDA App

Snakecharmed said:
First of all, hello. I'm new to tinkering with Android, but I've flashed firmware on dumbphones 68 ways to Sunday, so I'm not new to phone modding nor am I worried about technical answers, so fire away.
To start, this phone has not been rooted (yet) and has the stock 2.3.4 ROM.
I've screwed around for the last six hours or so in fear of bricking the phone only to realize I should have followed a different set of instructions after Step 1 of Downgrading in this guide, because now that I've read other guides, I find this one unnecessarily complicated compared to directly pushing PD15IMG.zip to sdcard.
Since I'm already calling it quits on going any farther with this tonight, I just need a few questions answered before I give this another shot.
1. Is ADB supposed to see the phone when it is in recovery or bootloader mode? When the phone is in recovery or bootloader, entering adb devices in the Windows Command Prompt returns an empty list of devices attached.
2. I have the bad eMMC in my phone. In addition, once in recovery mode and I press Vol Up+Power, I see an error message that says E:Can't open /cache/recovery/command. I also get additional "can't open" error messages when I select Wipe data/factory reset from the recovery menu:
Wiping data...
Formatting /data...
E:Can't open /data/cwpkg.zip
E:Can't open /data/cw.prop
E:Can't open /cache/cwpkg.zip
E:Can't open /cache/cw.prop
Formatting /cache...
Data wipe complete...
Are those errors a concern? Are they a product of a failed eMMC or a corrupted file system? If they are because of the eMMC, would it be safe to say that I should leave this phone alone? If they are because of the file system, what I can do to fix these errors?
3. Now that I've read other, more MT4G-specific downgrading guides, will pushing PD15IMG.zip to sdcard and fastboot take care of the "can't open" errors in question 2 as well?
Click to expand...
Click to collapse
are you talking about the stock recovery? because the stock recovery is supposed to say "E: can't open /cache/recovery/command". not sure why but it does. happened on every stock recovery i've seen.

Yes, I'm on stock recovery, and that's good to know that it appears to be normal.
Currently, I have successfully downgraded to stock 2.2.1 with the .86 bootloader.
Now, in following this guide, I've gotten to the end of Step 10 and I get the following:
Code:
[B]# ./gfree -f[/B]
./gfree -f
--secu_flag off set
--cid set. CID will be changed to: 11111111
--sim_unlock. SIMLOCK will be removed
Section header entry size: 40
Number of section headers: 44
Total section header table size: 1760
Section header file offset: 0x000138b4 (80052)
Section index for section name string table: 41
String table offset: 0x000136fb (79611)
Searching for .modinfo section...
- Section[16]: .modinfo
-- offset: 0x00000a14 (2580)
-- size: 0x000000cc (204)
Kernel release: 2.6.32.21-g899d047
New .modinfo section size: 204
Attempting to power cycle eMMC... OK.
Write protect was successfully disabled.
Searching for mmc_blk_issue_rq symbol...
- Address: c02a63a4, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc02a6000
Kernel memory mapped to 0x40002000
Searching for brq filter...
- Address: 0xc02a63a4 + 0x34c
- 0x2a000012 -> 0xea000012
Backing up current partition 7 and patching it...
Backing up partition /dev/block/mmcblk0p7 to /sdcard/part7backup-1319315128.bin
...
Error opening backup file.
What should I do with the backup not being written?
Upon rebooting into bootloader, it still says S-ON.
Also, to back up a bit, in Step 5, I was supposed to unplug the phone from the computer and use the Android Terminal Emulator. I didn't and executed the commands through ADB because the soft keyboard input wasn't working at all in Android Terminal Emulator.
EDIT: Fixed the problem with backup not working and I now have S-OFF. The microSD card in my phone wasn't being detected properly, so instead of seeing the correct permissions d---rwxr-x with ls -l for directory /mnt/sdcard, it was being seen as read-only. When gfree attempted to write the backup to /sdcard, it failed because the SD was read-only.
I took out my 16GB card and put in my 8GB and this time, the gfree backup saved. I can't recall if I had the phone plugged in when I rebooted the phone or plugged it in afterward, but I'm slowly realized that the SD card gets remounted when you plug and unplug the phone from the computer due to the different file systems. That's why I had issues saving files to /sdcard through ADB. Now I understand why the commands were supposed to be entered in Android Terminal Emulator, but I couldn't get the soft keyboard to function in it. Hopefully, that won't be a problem after flashing the new ROM, but that will be the next concern for me.
EDIT 2: I have now installed CWM Recovery 5.0.2.0. Also, it looks like the Android Terminal Emulator developer borked the keyboard input with today's update. Read comments from October 22, 2011:
https://market.android.com/details?id=jackpal.androidterm&hl=en

remember to perm root your phone and flash the engineering bootloader i think it was like .85 something

Thanks. I had it perm-rooted and installed the engineering bootloader by the end of the weekend. I'm looking forward to flashing VU after I get some more free time and take note of settings and apps I might want to keep from the stock ROM.

your apps should be restored by google
but just in case, use titanium backup or my backup. I personally prefer my backup to backup my sms/mms, apps and settings because its quicker when you restore.
I use titanium backup to backup and restore system apps.
Oh yeah you shouldn't try to backup your settings from your stock and restore it when you flash VU, they're different OS so might cause problems. BUT it's useful when you flash new updates.
Other than VU, you might want to try TDJ's Darkside if you want to test out sense 3.5. However, i might go back to virtuous once they release a final build for sense 3.5
happy flashing

I actually didn't have any settings to back up because I haven't been using the phone as my primary phone since I bought it, but I backed up the stock Froyo ROM and flashed to VU 2.39 two nights ago. Everything appears to be running well. I reinstalled Swype 3.7 from the stock Gingerbread ROM and I still need to reinstall Genius with Button Shortcut.
I don't really like the trouble of going back and forth between ROMs, so thankfully, I'm quite pleased with VU and Sense 3.0. The rest is just customization at this point. I may eventually take a look at Virtuous Trentacinque after it goes gold, but I didn't want to wait around for it nor run a beta ROM on what will soon become my main phone. I have no problem with flashing files and making tweaks all day, but it gets old after a while and I'd rather just use the equipment instead.
So far, battery life on VU seems to be pretty good and is much better than stock. I'm enjoying the new ROM so far as well as finally getting to use the phone rather than just backing up files and testing features.

fyi, Swype 3.25 beta is out. I think Swype 3.26 beta is out too. I think there was a thread with themed Swypes somewhere. But I forget.
Sent from my HTC Glacier using XDA App

[Q] ra 3.16 recovery encryption problems

Tonight i was going to flash the newest flexreaper ics build on my iconia tab. While i was waiting for it to download, i decided to play around with the ra recovery options. I tried to upgrade the internal storage to ext4 but it said that it failed at data so i formated all of them back to ext3 but data still wouldn't mount and still won't. When i booted the rom up it said that there was a problem with the encryption and it needed to reboot. I tried an older honeycomb rom but now it asks for an password to decrypt the tablet but i never put one on. Is there anyway to get around it because it is unusable right now?

darktwolf380 said:
Tonight i was going to flash the newest flexreaper ics build on my iconia tab. While i was waiting for it to download, i decided to play around with the ra recovery options. I tried to upgrade the internal storage to ext4 but it said that it failed at data so i formated all of them back to ext3 but data still wouldn't mount and still won't. When i booted the rom up it said that there was a problem with the encryption and it needed to reboot. I tried an older honeycomb rom but now it asks for an password to decrypt the tablet but i never put one on. Is there anyway to get around it because it is unusable right now?
Click to expand...
Click to collapse
I thought Drellisdee put warnings about messing with those things. Check his RA Revamped thread, and I think he put some answers. More specifically in the very first paragraph, with a link to the fix
http://forum.xda-developers.com/showthread.php?t=1459821
Here I believe is the part you need, quoted from the post;
"Those are advanced options that most users shouldn't have a need for and shouldn't normally use. Your data should have already been ext4 and you tried to reupgrade it to ext4 and looks like you corrupted your /data partition. For reference the 1st page has a description of the menu items. Dont just go selecting every option if you dont know what it does.
To fix your blunder you will need to boot into my recovery and open adb shell.
This will cause loss of all data contained on /data which will lose your /data/media.
From adb shell
Code:
mount (this is to check data isn't mounted) if mounted use "umount data"
mke2fs -j -b 4096 /dev/block/mmcblk0p8
tune2fs -O extents,uninit_bg,dir_index -C 1 /dev/block/mmcblk0p8
e2fsck -fy /dev/block/mmcblk0p8
After this is done your file system on /data will be fixed."
Click to expand...
Click to collapse

Moscow Desire said:
I thought Drellisdee put warnings about messing with those things. Check his RA Revamped thread, and I think he put some answers. More specifically in the very first paragraph, with a link to the fix
http://forum.xda-developers.com/showthread.php?t=1459821
Here I believe is the part you need, quoted from the post;
Click to expand...
Click to collapse
i tried that method but it didn't find my device in adb but i found another way. If you hold the power and volume up button on boot and switch the rotate lock over it erases all file systems. I tried that and it booted up like brand new.

darktwolf380 said:
i tried that method but it didn't find my device in adb but i found another way. If you hold the power and volume up button on boot and switch the rotate lock over it erases all file systems. I tried that and it booted up like brand new.
Click to expand...
Click to collapse
Yep, that sometimes fixes it also. Sometime
ADB sometimes takes 2 or 3 plug ins to connect. Was messing with it earlier today, and had the same issue, but eventually it found the tab.
Glad you got it going.

Crashing Nook

Well, my Nook appears to be in trouble.
The long and the short of it is that it got wet. Not too wet, but wet.
It boots but whatever I boot to crashes. This includes sdcard installs. The ROM completes the boot, and I can sometimes even open the app drawer, but it crashes before I can interact with it in any meaningful way.
All ROMs complain of "System process" and Wireless issues, with FCs.
I cannot get adb to recognize the device anymore. lsusb does find the Google Inc. entry, though. When I try and run adb devices (ubuntu), it returns ?????? and says insufficient permissions. I have, in response, set up the 99-android.rules in etc/udev/rules.d but it still cannot connect. I have also tried to quickly access the android terminal in the brief period I am allowed before the device crashes with no luck. My goal with this was to try fdisk -l.
The sdcard never mounts while in the ROM, and the emmc storage appears completely wiped.
However, I was able to see I had the correct files in /rom once, so those are there.
Thinking that the wireless chip might be the problem (as when even when I return to stock the set-up fails there, well, until it crashes again...) I tried to just turn off Wifi in 7.2. But as I unchecked the box, right under the setting just displayed "error"
CWM appears to be working EXACTLY as it should, including mounting the sdcard and allowing me to choose update zips.
The uboot and the uboot menu work as well.
I have tried flashing CM7, 9 and stock, as well as booting from sdcard in CM9. All flash and boot normally, but crash.
I have done the 8x reboots, succesully, but when the B&N set-up begins, I cannot connect to wireless. Which would be okay, in the long run, but it then crashes, which is not okay.
I was hesitant to reveal that it got wet, because I can see this being written off as a hardware issue (which it may be, don't get me wrong). But the fact that CWM works and the ROMs boot sure look like software problems to me.
I have tried flashing just about everything that looked promising. I have not dd any images, because I cannot get adb to work, and don't have any idea which partitions are in what shape.
Any suggestions?

Position the unit upside down with the SD flap open. Blowdry it from the bottom up on medium several times over a couple of days. If it's still doing it after that you can probably eliminate moisture as a cause.

old cell phone trick
Fill a bowl with rice (uncooked).....the rice will draw the moisture out.

you can also submerge it in ispropol rubbing alcohol... is what we use to clean electronic components... it will combine with the water... also used for water in gas on a car

Whoa, isopropyl alcohol. I feel like that would take some stones...
I have already put it through a 30 or so hour rice regimen (if that is true, even. It makes some kind of weird intuitive sense, which is usually the kiss of death...)
I have it standing up now and will see about a little air dry method while I investigate where to find the alcohol.
It didn't get submerged, it was lying on a counter and a glass got knocked over. I grabbed it right up, and then left it off like I said.
It boots, CWM works, but since it has been set all the way back to stock and all iterations have the same issue I am fearing the worst...
Thanks for the ideas...any and all welcome!

You can take the back off. I have not done it, but somebody just said they did it to disconnect the battery to reset. Look at that recent thread in q/a. Maybe he can tell you how he did it.

Attempt at your own risk, no support will be provided.
I'm not the battery guy leapinlar was talking about but,
Open the battery flap, remove SD card, remove the tape dots from the T-5 torque screws then remove the screws. Slowly and carefully so as not to break any of the hooky thingies that are holding the back on pry the cover up from that point moving slowly around the unit.
I've only done this once, it was a while back and I ended up breaking two of the little hooky thingies. That's why I suggested providing points for evaporation to escape and attempting to accelerate evaporation. Heck we don't even know if moisture is the issue anymore.

Thanks for the extra suggestions.
I tend to think at this point that whatever water got in there is gone. It's been four days, and it wasn't soaking. I may just go ahead and try and take out the battery, I don't know exactly why that would help, but what have I got to lose?
If I had to guess, I would think that the wifi chip might be shorted, as that is the only thing that doesn't seem to work at least for some period of time.
The FC's sure do look software related though. I fail to see how CWM could read and mount the sdcard while the ROM cannot as being anything other than sotware. Unless they use wildly different methods to do the same thing.
This nagging feeling that I should be able to at least fix that with some software methods keeps me thinking the same or the other problems. I'd be okay with an non-networked tablet, if it came to that. But maybe the thing has to have wifi as an option to work right. I don't know...

Two weeks ago my daughter managed to completely soak her nook.The nook would just constantly reboot with the stock os and system process would repeatedly fc with the cm7 sdcard. I pulled the back cover off and let it stand for a week. Today I pulled the battery and power button cable and it booted up just fine so far. So there is hope.

Malave said:
Two weeks ago my daughter managed to completely soak her nook.The nook would just constantly reboot with the stock os and system process would repeatedly fc with the cm7 sdcard. I pulled the back cover off and let it stand for a week. Today I pulled the battery and power button cable and it booted up just fine so far. So there is hope.
Click to expand...
Click to collapse
Considering that this is basically what is happening to me (but with some additional Wifi setting crashes) this gives me hope.
I had burned a bootable CWM card, from Leapinlar, which was a higher version than I usually used. I think 5.5.0.4 (?)
Anyway, of interest (before I shut it down 2 days ago):
internal sd card is not wiped, it can be explored in CWM.
The /ROM partition is at least somewhat functional, as battery stats can be wiped
When I request a log, I get:
Code:
Battery Stats
Block Groups: 3
reserved block group size: 23
Created filesystem with 11/22608 inodes
and 2883/90357 blocks
warning: wipe_block_device: Discard Failed
W: failed to mount /dev/block/mmcblk1p2 (no such file or dir)
also at one point:
Code:
make_ext4fs failed on /dev/block/mmcblk1p2
(note: both of the above from hastily scrawled notes)
It looks like mmcblk1p2 is related to system mounting, although I am not sure. Maybe that is why I am having trouble with ADB. It just kept saying insufficient permissions and ???????????. I tried setting up android-rules for udev with no luck.
Unless I hear anything else promising, I will go get the proper screwdriver and try the battery thing. It has been sitting off for a couple days now...
Thanks for all the ideas, people.

I'm confused... but trying to help you out... why are you trying that stuff on /dev/block/mmcblk1p2 when /dev/block/mmcblk0p2 is the ROM partition?
Try your edits to /rom... and if you have to try: mount /dev/block/mmcblk0p2 /rom

DizzyDen said:
I'm confused... but trying to help you out... why are you trying that stuff on /dev/block/mmcblk1p2 when /dev/block/mmcblk0p2 is the ROM partition?
Click to expand...
Click to collapse
I actually didn't try to do anything. I just wiped system, cache, davlik, battery stats and asked for a log prior to flashing a new zip in the hopes that the rom would work if provided a blank slate.
I wiped battery stats since the .bin that holds them is in /rom. The log was something I had never done before.
The notes from above were just the CWM output from the log.
edit: I just saw your second paragraph. Don't know how I missed it.
But I don't know what you mean by edits. I haven't been able to get ADB working. I have been able to mount and unmount through CWM that's it. Unless you might know anther way to resolve insufficient permissions with beaucoup question marks instead of device number?

Ok... sorry about my confusion on that... It appears that you are using a CWM that is modifid to work on SD... since it is trying to access /dev/block/mmcblk1p2 since the rom partition is on /dev/mmcblk0.
I would try a different version of recovery.

DizzyDen said:
Ok... sorry about my confusion on that... It appears that you are using a CWM that is modifid to work on SD... since it is trying to access /dev/block/mmcblk1p2 since the rom partition is on /dev/mmcblk0.
I would try a different version of recovery.
Click to expand...
Click to collapse
Which I was. I got it from Leapinlar, and was under the impression, since I had seen him warn that roms flashed from that recovery would go to emmc, that it would work.
I did make a regular 3.2.0.1 bootable, and tried again, but with the same result, so I don't know if that made a difference. But it did seem hopeful, so thanks for the response.
I am going to finally go get the torque screwdriver and take this battery off and give it some days. It's been almost a week already, but you never know.
Thanks a bunch for the reponses, Diz.

mateorod said:
I had burned a bootable CWM card, from Leapinlar, which was a higher version than I usually used. I think 5.5.0.4 (?)
warning: wipe_block_device: Discard Failed
W: failed to mount /dev/block/mmcblk1p2 (no such file or dir)[/CODE]
also at one point:
Code:
make_ext4fs failed on /dev/block/mmcblk1p2
(note: both of the above from hastily scrawled notes)
It looks like mmcblk1p2 is related to system mounting, although I am not sure.
Click to expand...
Click to collapse
Mateorod, if you got that log using my CWM boot SD version 5.5.0.4, the recovery.fstab lists /dev/block/mmcblk1p2 as SD-EXT, which for some devices is the extended partition on SD for storing additional apps to supplement /data. Our implementation of CM does not use that. So when recovery tries to do some wiping, formating, backing up, etc, it always fails when it looks for that partition. It has nothing to do with /system or /rom.
If you told it to do a factory reset, it tries to wipe /SD-EXT as part of that and it fails to wipe that because it cannot find that partition.
Edit: That CWM SD does do its modifications to emmc. It only referenced mmcblk1p2 because of sd-ext.
Here is the filesystem table from my log using it on SD:
0 /tmp ramdisk (null) (null) 0
1 /boot vfat /dev/block/mmcblk0p1 (null) 0
2 /system ext4 /dev/block/mmcblk0p5 (null) 0
3 /data ext4 /dev/block/mmcblk0p6 (null) 0
4 /cache ext4 /dev/block/mmcblk0p7 (null) 0
5 /emmc vfat /dev/block/mmcblk0p8 (null) 0
6 /sdcard vfat /dev/block/mmcblk1p1 (null) 0
7 /sd-ext ext4 /dev/block/mmcblk1p2 (null) 0

The alcohol trick does work, I did it on my old HTC Kaiser. I disassemble it as much as I was comfortable, and then completely submerged it in alcohol until It stopped throwing up air bubbles; Thus showing there was no air left in the unit. I then removed the pieces from the alcohol and put them in a bowl of rice. I let it stand for about a week. Once the time was up a reassembled and turned it on like nothing had happened.
Little note: I was in the possession of a AT&T Go Phone for use as a back up in case this destroyed the unit. If you feel that there might be another way to repair it, I would suggest you explore that option first as I do not know what a significant time in alcohol will do to the inner workings of the Nook. However if you are at the point of already replacing or upgrading to a different tablet, than you have nothing to lose and can only gain a working Tablet or fancy Paper-weight from this.

Okay, a little update.
I had taken apart the Nook and let it sit for almost a week. But upon reconnecting the battery and clearing system/cache/davlik and reflashing anything, it still wouldn't allow in-ROM mounting of sdcard or adb or wireless and I would still get some version of "process System not responding" and "Setting Wireless not responding" toasts and then a crash, either in CM7, CM9 or Stock. Unusable.
What I think I have is a totally borked wifi chip. Which is okay, in the long run, but the Nook kept crashing and I would have liked to use it in some capacity.
What I decided (which was difficult to diagnose with no terminal or no ADB) was that the Nook was crashing upon trying to access the network and the saved network info. (which I know is mad persistent, as the wifi network I used to originally register the device still shows up in the stats, even after many many system wipes and 8x reboots and so forth.)
I had never reset to factory from stock settings and I couldn't now completely erase and deregister because you need wifi to do so.
However, I found this (which I had never heard of, sounds like a boon to thieves everywhere). After skipping out-of-box experience I could boot into stock recovery and finally erase the wireless settings.
Now I have a stable (albeit un-registered) stock nook, where I can at least read the books I have on sdcard.
I will eventually reflash a CM build now that the network settings have been forgotten and see if that is usable, even if there is no wifi.
But I am pretty happy to have some semblance of the Nook back, even if it is just a neutered (literally) stock.
I'll let you know how CM goes one day soon.
Thanks for the help!

Excellent, (and powerful), link.
And by virtue of that link I will find a way to proclaim my absolute geekitude within the company by dropping Kate's name. :good:

Well, I finally tried flashing Cyanogen 7 and 9 to the thing, but as it crashes when it tries to access wifi, I can't get it stable.
Unless anyone knows a code edit (smali maybe? I know there are a bunch of boolean settings in the SystemUI.apk, maybe there) where I can change the default wifi setting, I may just be stuck with stock.
Which is way better than nothing, at least it has use. Skipping OOBE was a life-saver for getting to a place where I could erase the WiFi info.

Okay, here's another shot in the dark, still trying to get this thing to successfully boot in CM...
I am working on a little project for the Nook, which will be infinitely easier to debug if I can actually boot into CM.
Does anyone familiar with the source code know how to modify it so that WiFi is set to off by default? I am thinking about changing the 'true' to 'false' in the /device/bn/encore/overlay/frameworks/base/core/res/res/values/config.xml entry for wifi found here...
Code:
<!-- This string array should be overridden by the device to present a list of network
attributes. This is used by the connectivity manager to decide which networks can coexist
based on the hardware -->
<!-- An Array of "[Connection name],[ConnectivityManager connection type],
[associated radio-type],[priority],[restoral-timer(ms)],[dependencyMet] -->
<!-- the 5th element "resore-time" indicates the number of milliseconds to delay
before automatically restore the default connection. Set -1 if the connection
does not require auto-restore. -->
<!-- the 6th element indicates boot-time dependency-met value. -->
<string-array translatable="false" name="networkAttributes">
<item>"wifi,1,1,1,-1,true"</item>
<item>"bluetooth,7,7,0,-1,true"</item>
<!-- item>"ethernet,9,9,2,-1,true"</item -->
</string-array>
This looks like I am on the right track (this will eventually end up being compiled into the res folder of framework-res.apk) but I may need to track down the ConnectivityManager. Although the cursory look I have given this seems like I may be close to on the right track...
(The wifi being on at boot always crashes my CM installs due to shorted wifi chip, for those of you who may be new to the thread.)
I am asking here just in case someone knows, I may just go ahead and try it if no one chimes in. But better to ask than to blindly shoot in the dark, I figure...
Update: Success. I am back on CM9 (well, a hybrid, actually...HINT), without wifi.
Update 2: Due to the fact that this nook is now in a Cyanogen-usable state, a new rom will be posted in development tomorrow from eyeballer and I. Thanks for the suggestions, everyone. I wish I had dipped it in isopropyl alcohol, just so I could say I did it...

LG G2 (Verizon) Bricking

OK, I have searched the forum and the web and everything I have found doesn't seem to work. It appears I may have bricked up my phone, soft or hard. I am not sure as this is the first time I have ever bricked up.
What I Have:
Verizon Lg G2
Rooted
Had [ROM OTA] LG G2 Verizon Stock Rooted VS98012B
ClockworkMod Recovery v6.0.4.4
What Happened:
My phone was working great until I was trying to figure out why my GF's G2 was not accepting the update from Verizon. So as the gentleman as I am, I decided to revert my G2 back to stock so I could DL and see if I got an error message as well.
So I was able to revert it back from my CW Recovery, after which it was acting sort in sloggish, strange in a way... I shrugged it off and tried the update from Verizon. I was able to DL no problem, but when I installed it, my cell rebooted... After sever attempts to re-installing an OS (ANY OS), I start searching the web for a cure to this mess.
I tried using this method HERE, only to find out that I cannot go into DOWNLOAD MODE as instructed in step #2. Every attempt I make, only brings me back to the ClockworkMod Recovery main screen.
I have no idea what else to do.
PLEASE!!! Anyone have any ideas??? Would really appreciate it as I am trapped from the outside world... :'(

manojsuper said:
mount the ohone in cwm and flash another custom rom and try again.
Click to expand...
Click to collapse
Mano,
Thanks for your quick response. I looked to see how I can do that and I cannot see where I can mount the CWM, nor do I have a ROM on my cell as I removed it to fit more music. lol

manojsuper said:
KEEP LOOKING IN THE CWM, IT WILL BE THERE.
Click to expand...
Click to collapse
I've searched everywhere and cannot find it. Where would it be and what will the cammonand be?

manojsuper said:
tell me the options that come up when you are in the recovery
Click to expand...
Click to collapse
Code:
- Reboot System Now
- Install Zip
- Wipe Data/Factory Reset
- Wipe Cache Partition
- Backup and Restore
- Mounts and Storage
- Mount /System
- Mount /Data
- Unmount /Cache
- Mount /Persist
- Mount /Firmware
- Mount /Sins
- Mount /Persist-lg
- Mount /mpt
- Format /System
- Format /Data
- Format /Cache
- Format /Persist
- Format /Firmware
- Format /SNS
- Format /Persist-lg
- Format /mpt
- Format /Data and /Data/Media (/SDCARD)
- Mount USB Storage (Tried this)
- Advanced
- Reboot Recovery
- Reboot to Bootloader
- Power Off
- Wipe Dalvik Cache
- Report Error
- Key Test
- Show Log
- Toggle Loki Support

Kilch said:
Code:
- Reboot System Now
- Install Zip
- Wipe Data/Factory Reset
- Wipe Cache Partition
- Backup and Restore
- Mounts and Storage
- Mount /System
- Mount /Data
- Unmount /Cache
- Mount /Persist
- Mount /Firmware
- Mount /Sins
- Mount /Persist-lg
- Mount /mpt
- Format /System
- Format /Data
- Format /Cache
- Format /Persist
- Format /Firmware
- Format /SNS
- Format /Persist-lg
- Format /mpt
- Format /Data and /Data/Media (/SDCARD)
- Mount USB Storage (Tried this)
- Advanced
- Reboot Recovery
- Reboot to Bootloader
- Power Off
- Wipe Dalvik Cache
- Report Error
- Key Test
- Show Log
- Toggle Loki Support
Click to expand...
Click to collapse
If you select install zip, do you see an option to SIDELOAD ZIP? If you do, you can push a ROM from your PC.

SplicedX said:
If you select install zip, do you see an option to SIDELOAD ZIP? If you do, you can push a ROM from your PC.
Click to expand...
Click to collapse
I do, let me check it out...

I'm at work now, so I will try when I get home in the AM.

In the event I cannot get this running, what is the best way to go about getting this phone switched out? Tell them it fell through a hole while ice fishing? Lost it? Or..... lol

Kilch said:
In the event I cannot get this running, what is the best way to go about getting this phone switched out? Tell them it fell through a hole while ice fishing? Lost it? Or..... lol
Click to expand...
Click to collapse
No need for that. You can fix this with a few simple commands.

SplicedX said:
No need for that. You can fix this with a few simple commands.
Click to expand...
Click to collapse
Thanks SplicedX. I am not that command knowledgeable. What would the commands be?

Kilch said:
Thanks SplicedX. I am not that command knowledgeable. What would the commands be?
Click to expand...
Click to collapse
Sorry I feel asleep on you. Here is a basic tutorial.
http://forum.xda-developers.com/showthread.php?t=2559200

SplicedX said:
Sorry I feel asleep on you. Here is a basic tutorial.
http://forum.xda-developers.com/showthread.php?t=2559200
Click to expand...
Click to collapse
No worries Spliced, I just got on about an hour ago.
OK, so I am following the instructions to the "T" and I keep getting an error: "cannot read {file name.zip}". Trying to transfer a ROM... Tried renaming the file, removing the .ZIP extension, everything... grrrr
UPDATE: I did a test to see it I can slide a file. I slid the adb.exe and it did slide it over. So sliding does work. Question is, why doesn't slide a ROM over? I am currently downloading another ROM and going to try to slide it over without changing the name of the file. Perhaps it's the signature of the file??? <shrug>

ANOTHER UPDATE:
Ok, it appears "[ROM OTA] LG G2 Verizon Stock Rooted VS98012B" is not like, cannot be sideloaded. I am now sideloading "[ROM] LG G2 VZW Digital Dream v2.1" but stuck on 85% sending... lol

KO, I was able to sideload an image and it instralls, but it still boots up in recovery mode. It appears my G2 is dead.
That said, what is a good excuse to use at Verizon for a replacement?

Kilch said:
KO, I was able to sideload an image and it instralls, but it still boots up in recovery mode. It appears my G2 is dead.
That said, what is a good excuse to use at Verizon for a replacement?
Click to expand...
Click to collapse
Don't replace it. This is the reason why carriers have gotten so picky with handing out replacement devices, example: VZW 14 day return policy. Guy buys new phone, guy f**ks up new phone, guy returns it claiming defect.
There is a guide to get you back to stock in this sub, and it's even specific to Verizon's G2. It works, I've used it myself. Just be patient during the process and follow the instructions precisely. Good luck!
VS980

Dork6243 said:
Don't replace it. This is the reason why carriers have gotten so picky with handing out replacement devices, example: VZW 14 day return policy. Guy buys new phone, guy f**ks up new phone, guy returns it claiming defect.
There is a guide to get you back to stock in this sub, and it's even specific to Verizon's G2. It works, I've used it myself. Just be patient during the process and follow the instructions precisely. Good luck!
VS980
Click to expand...
Click to collapse
I have tried that and there is a problem, when I press the volume up button, it just boots into CMW. In other words, I do not get the download screen.

Kilch said:
I have tried that and there is a problem, when I press the volume up button, it just boots into CMW. In other words, I do not get the download screen.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2448960
Verify power off. Hold vol up and connect USB.
VS980

Dork6243 said:
http://forum.xda-developers.com/showthread.php?t=2448960
Verify power off. Hold vol up and connect USB.
VS980
Click to expand...
Click to collapse
Did that, was a no-go. Thanks for the help. Went to Verizon and I am getting my replacement in a few days. I gave up...

[Q] Howto decrypt /data and /sdcard after phone was flashed with stock ROM?

It is my first post here so hello. Can you help me?
I broke my phone. Fortunately it was insured. However I haven't been doing backup for a while. Main board remains untouched and so I had been trying to recover my data before sending it to service. Phone was encrypted. I had little time that weak and get little confused with fastboot/odin. Thus, I decided to send it and reconciled with data lost. Phone back to me form service with flashed android 5.0.
I have no experience with android.
I am trying to recover my data. My idea is simple. If disc encryption master key (specifically crypto footer) is untouched I should be able to decrypt data partition (I am thinking about low level decryption, bit by bit) and then use some software to recover files (because directory table was overwritten) that where no overwrite when phone was flashed. Since I was not deleting my files often, the most recent files should be placed at the end of data partition. Whats is more I should be able to decrypt my sdcard which Is also encrypted.
What I determinated for this moment:
1. According to: source.android.com/security/encryption/#storing_the_encrypted_key every android 5.0 is encrypted with default password at first boot. However mine was no. Encryption flags are not set and data are available form TWPR level without decrypting.
2. Here is more how encryption works: (p. 263-266) books.google.pl/books?id=y11NBQAAQBAJ&pg=PA262&lpg=PA262&dq=android+disk+encryption+master+key&source=bl&ots=nUYyBSuT2G&sig=w77YZ9EJValOVoGhGXxbRMgwtmY&hl=pl&sa=X&ved=0ahUKEwi9qMzlgd3MAhUE_ywKHV0sAdwQ6AEISzAF#v=onepage&q=android%20disk%20encryption%20master%20key&f=false
I haven't read everything for now...
It says that crypto footer is written on either end of user data partition, file or dedicated partition. There is a chance that crypto footer remains untouched after flash. Can somebody check what is the the case on s5? I cant do this on my of because If I encrypt phone I erase previous crypto footer.
3. cmds: vdc cryptfs chengepw | checkpw returning -1 and no more and any valuable informations. I did not search in logs, there is noting in dmesg also.
Does anyone have ideas how to do this procedure? Check if master key is still there or any clues?
Thank you in advice