Edit: I think i fixed it by "cleaning" with diskpart and using an sd card to copy a rom and flash it, then booting up android and letting it format the internal storage. Will report back if any problems occur! Check post # 6 on this page for the solution. Also, sorry for the erratic writing, it's 4:55AM here and i need to be up at 9AM!
AtrICS rom did a random reboot and was saying something about encryption failed. Strange, i've never used that setting (i don't even have a screen lock). I rebooted the phone and it wouldn't get to the ROM, so i went into recovery and tried restoring a backup. After a few seconds it aborted. Strange. I mounted usb so i could copy a fresh rom.zip to flash, but after a few MB, it was throwing a "cannot read from source disk" error. Internal storage was corrupted.
I can read data from the partition, but after a while it'll lock up. I cannot write to it at all. I also get an error in CWM "unable to write to ums lunfile (no such file or directory)".
How can i fix this? I was thinking full sbf flash, but is that too risky? I'm in the UK (t-mobile), came with stock froyo, unlocked bootloader and flashed gingerbread onwards. Is it safe for me to flash back to froyo or something, or will my unlocked bootloader get me bricked? How can i fully clean this pesky corrupted partition any other way?
Thanks.
coolnow said:
AtrICS rom did a random reboot and was saying something about encryption failed. Strange, i've never used that setting (i don't even have a screen lock). I rebooted the phone and it wouldn't get to the ROM, so i went into recovery and tried restoring a backup. After a few seconds it aborted. Strange. I mounted usb so i could copy a fresh rom.zip to flash, but after a few MB, it was throwing a "cannot read from source disk" error. Internal storage was corrupted.
I can read data from the partition, but after a while it'll lock up. I cannot write to it at all. I also get an error in CWM "unable to write to ums lunfile (no such file or directory)".
How can i fix this? I was thinking full sbf flash, but is that too risky? I'm in the UK (t-mobile), came with stock froyo, unlocked bootloader and flashed gingerbread onwards. Is it safe for me to flash back to froyo or something, or will my unlocked bootloader get me bricked? How can i fully clean this pesky corrupted partition any other way?
Thanks.
Click to expand...
Click to collapse
Sound like the same issue myself and some others are having. I was using the atrics rom and icsrom as well before my phone went to heck. We cannot delete stuff from sd card or flash any other rom..
boonemeat said:
Sound like the same issue myself and some others are having. I was using the atrics rom and icsrom as well before my phone went to heck. We cannot delete stuff from sd card or flash any other rom..
Click to expand...
Click to collapse
Did you mess with the encryption settings? I know i didn't. Whatsapp was throwing errors so i rebooting the phone and now all this has happened. Can't even moto-fastboot flash system because it always gives an error :crying:
coolnow said:
Did you mess with the encryption settings? I know i didn't. Whatsapp was throwing errors so i rebooting the phone and now all this has happened. Can't even moto-fastboot flash system because it always gives an error :crying:
Click to expand...
Click to collapse
Sure did not mess with encryption. Rsd flashing did nothing, fastboot does nothing for me. Now the rom I'm stuck on is getting errors and fc's like crazy and the touch screen is beginning to fail.
boonemeat said:
Sure did not mess with encryption. Rsd flashing did nothing, fastboot does nothing for me. Now the rom I'm stuck on is getting errors and fc's like crazy and the touch screen is beginning to fail.
Click to expand...
Click to collapse
Damn. I would have thought RSD would be the last resort...
I think i've made some progress. I have to be up in 5 hours so i'll be making this short. You will need an SD card.
I was sick of the lockups created by the corrupted /emmc/ partition, so i rebooted my phone, went back into recovery (it would never mount any filesystem after mounting emmc once, so a reboot was needed every time) and mounted emmc. Showed up on my computer, and gave me a chance to copy my photos and all that. Thank you!
I started CMD as an admin and typed in
diskpart
Click to expand...
Click to collapse
When it loaded up, i typed
list disk
Click to expand...
Click to collapse
I saw a 10GB partition as disk 2 so i then
select disk 2
Click to expand...
Click to collapse
then i did
list partition
Click to expand...
Click to collapse
and saw only 1 partition, as partition 1, so
select partition 1
Click to expand...
Click to collapse
then
clean
Click to expand...
Click to collapse
Went into Disk Management and right clicked the black bar "unallocated space" and made a new simple volume, formatted as fat32 and that's that.
I then copied a rom onto my sd card and flashed via cwm. Everything seemed to go well, i could boot up (remember, because of the failed encryption, i was wiping my /system/, /data/ etc to try to get a fresh start so i had no rom to get on.
Will report back any problems. Just had one, i booted up fine but realised my usb cable was still plugged in so sd and internal storage were unmounted. Unplugged USB and phone froze (due to corrupted partition?). I recognise that freeze, i had it earlier on today (is that when the partition got corrupted?). It's rebooting right now, no usb cable plugged in. Wish me luck.
Android gave me a "your internal storage is corrupted" notification and offered to format. I allowed it and everything seems to be well! I will be filling it up right now before going to bed to see if it will lock up, but i think i fixed it!
Well congrats I'm glad you had such luck! It seems our problems are a bit different unfortunately because it goes a little deeper on my end. Thank you so much for the help.
Here is my struggle with the same problem. I have no solution, but maybe something here will help you?
http://forum.xda-developers.com/showthread.php?t=1967620
Related
for this fix, you will need to have a CWM sdcard ready and waiting followed by and drivers properly installed for your tablet.
YOU MUST have CWM running from sdcard to fix this issue. Otherwise nothing will happen.
instructions to install to sdcard are here (I suggest using windows)
Needed files for download:
just download this zip and run the script while booted into cwm from sdcard.
download it here.
Instructions: Boot from sd (don't worry, it will work), ensure sdcard is mounted, and then you just run the fix.bat from the computer after extracting.
Credits: Succulent for the xloader image
Fattire for the idea that it might have formatted mmcblk0p1 (which it dead instead of mmc1)
You're welcome.
Might want to add that the cause of the "brick" appears to be that CM7 is confusing mmc1 and mmc0 and instead of wiping the first partition of the SD card, it's presumably wiping the first partition of the emmc, which contains the x-loader.
I already have said it.
Ah okay... well glad everything is fixed now.
fattire said:
You're welcome.
Might want to add that the cause of the "brick" appears to be that CM7 is confusing mmc1 and mmc0 and instead of wiping the first partition of the SD card, it's presumably wiping the first partition of the emmc, which contains the x-loader.
Click to expand...
Click to collapse
Bowing head in shame here...... Rookie mistake!
Looks like we have to make a bit of a tweak to the system then do some testing.
New download link due to a small scripting error.
Need help
Hi Indirect. I see that you have fixed your NT. I did not use sd i did install cm7 internally but i did format all the mounts . And now it just restarts in CWM. What should i do. Any idea please
Well guys, I'm still having problems. I ran the brick fix before you updated it - didn't work. I then re-ran after you updated it - still didn't work. It'll boot to CWM from SD, but won't boot to any ROM. Tried re-installing CM7 (didn't work), then I tried the Nook141root.zip which supposedly installs the BN 1.4.1 from CWM (also didn't work). Tried re-running the brick fix a handful of times after and before installing each ROM with no luck. Then I tried running it without installing a ROM. Tried the brick fix then I tried the BN 1.4.0 restore file. I tried on multiple freshly formatted SD cards and I even tried on a computer I was working on with a fresh install of Win7 with a fresh install of the drivers just to rule that out.
Before all this I had CWM and CM7 installed internally - if that makes a difference. Ideas?
Edit: More info. When trying to wipe data/factory reset in CWM I get the errror "E:format_volume: make_ext4fs failed on /dev/block/mmcblk1p2"...this occurs right after rebooting from the brick fix.
Edit 2: More info yet...in the brick fix I'm getting the text "error: device not found" twice right after entering "y" then again a handful of times later. Is there anything special I have to do in CWM to get it to detect it? I have sdcard mounted...
Im geting this and then my nt restarts by itself and then im back in cwm again so nothing is fixed.
Fatos said:
Im geting this and then my nt restarts by itself and then im back in cwm again so nothing is fixed.
Click to expand...
Click to collapse
What do you have mounted to get it the fix to detect the tablet? Does it matter?
scsione889 said:
What do you have mounted to get it the fix to detect the tablet? Does it matter?
Click to expand...
Click to collapse
Actually with mine it does not matter . I get till the step y or n without mounting nothing. Than i mount the sd card and press y and enter.
Than as u can see does try to write something and than my nook does reboot .
And the ending is the same. So no progress so far.
Fatos said:
Actually with mine it does not matter . I get till the step y or n without mounting nothing. Than i mount the sd card and press y and enter.
Than as u can see does try to write something and than my nook does reboot .
And the ending is the same. So no progress so far.
Click to expand...
Click to collapse
Were you running from internal or SD when it bricked?
Does it boot to CWM on it's own without an sd in the slot? If it does have you tried restoring/flashing a backup?
Reason I say about the backup is I just bricked my own systems on purpose when running from sdcard, it kept gpoing back to CWM after the xloader was returned to it. Restored an original backup and all is well again
CelticWebSolutions said:
Were you running from internal or SD when it bricked?
Does it boot to CWM on it's own without an sd in the slot? If it does have you tried restoring/flashing a backup?
Reason I say about the backup is I just bricked my own systems on purpose when running from sdcard, it kept gpoing back to CWM after the xloader was returned to it. Restored an original backup and all is well again
Click to expand...
Click to collapse
Yes i have had it internally.Not in an sd.
Yes mine doew boot to CWM on its own without and sd in slot. And yes i have tried restoring to re flash back up. Cause i have installed CM7 once and it did run well. But than after installing some programs became slow so i wanted to redo it again. And than i did format all: bootdata, cache, emmc, rom, system,sd-ext.
And then i installet cm7 again and all the installing went well againg . But it just want start cause is missing something in one of the mounts. So what i think is only needed if ill be able to restore the data that is in all those small partitions like emmc. I know that bootdata,and cached gets backed up but i dont know if the orthers are backed up or not.
Thanks for trying to help.
Edit: I have to go to university now. But if it would make it easier for you to help, I can shot a video afterwards with all the steps what i have done and how is my nook behaving now.Just let me know .
Edit1: I did try to restore to stock or update to 1.4.1 but it tells me MD5 mismatch.
Is it possible that i can push in with adb the files that are in the boot data, eMMc and other mounts i mean one by one.
I was running internal when it bricked. Only boots to cwm from SD now.
Sent from my Incredible 2 using XDA App
Fatos said:
Yes i have had it internally.Not in an sd.
Yes mine doew boot to CWM on its own without and sd in slot. And yes i have tried restoring to re flash back up. Cause i have installed CM7 once and it did run well. But than after installing some programs became slow so i wanted to redo it again. And than i did format all: bootdata, cache, emmc, rom, system,sd-ext.
And then i installet cm7 again and all the installing went well againg . But it just want start cause is missing something in one of the mounts. So what i think is only needed if ill be able to restore the data that is in all those small partitions like emmc. I know that bootdata,and cached gets backed up but i dont know if the orthers are backed up or not.
Thanks for trying to help.
Edit: I have to go to university now. But if it would make it easier for you to help, I can shot a video afterwards with all the steps what i have done and how is my nook behaving now.Just let me know .
Edit1: I did try to restore to stock or update to 1.4.1 but it tells me MD5 mismatch.
Is it possible that i can push in with adb the files that are in the boot data, eMMc and other mounts i mean one by one.
Click to expand...
Click to collapse
I'm in the same boat...I think when we did a format of the rom partition, we lost some data that was not backed up...That being said I have done a lot of reading and I think all hope is not lost.
We did not format the "factory" partition which from what I have been reading may contain a backup of the "rom" and other partitions.
I wonder if it is possible to pull the data from the factory partition, extract the data that we need and then push the appropriate files back to where they belong? It's way beyond my expertise, although I do have ADB working and I think if someone could point us in the right direction, it wouldn't be that difficult...I could be completely off base though...Good Luck and If I make any progress I'll make sure I pass the info along.
Need help!
I got the bloody ADB issue.... I was able to boot to CWM from SD card, and it's mounted. BUT! Adb devices gives me nothing, no device. I did all the troubleshooting of the driver, i got the "Android composite ADB interface" device but still no adb device appearing. Please help! My only idea if this fix can be incorporated into a flashable zip. May be there is some other way?
Thanks.
ElectroMike said:
I got the bloody ADB issue.... I was able to boot to CWM from SD card, and it's mounted. BUT! Adb devices gives me nothing, no device. I did all the troubleshooting of the driver, i got the "Android composite ADB interface" device but still no adb device appearing. Please help! My only idea if this fix can be incorporated into a flashable zip. May be there is some other way?
Thanks.
Click to expand...
Click to collapse
That's exactly what I've got. I'm going to spend a little time on fixing that up today. ADB just won't work through CWM for me.
ElectroMike said:
I got the bloody ADB issue.... I was able to boot to CWM from SD card, and it's mounted. BUT! Adb devices gives me nothing, no device. I did all the troubleshooting of the driver, i got the "Android composite ADB interface" device but still no adb device appearing. Please help! My only idea if this fix can be incorporated into a flashable zip. May be there is some other way?
Thanks.
Click to expand...
Click to collapse
I had thought about a flashable zip. I will look shortly and build one
I tried repartitioning my nook and it really bricked it now. It won't boot from SD. Tried a different card and fresh download of CWM. I think it's totally borked.
Edit for clarification: repartitioned from within CWM on SD
Edit2: Tried a 3rd card (first 2 were 32gb, 3rd was 16gb) and it let me back into CWM. ADB still isn't working though.
Edit2 clarification: I only say ADB isn't working because the brick fix says device not found. If I'm wrong please feel free to correct me.
scsione889 said:
I tried repartitioning my nook and it really bricked it now. It won't boot from SD. Tried a different card and fresh download of CWM. I think it's totally borked.
Edit for clarification: repartitioned from within CWM on SD
Edit2: Tried a 3rd card (first 2 were 32gb, 3rd was 16gb) and it let me back into CWM. ADB still isn't working though.
Edit2 clarification: I only say ADB isn't working because the brick fix says device not found. If I'm wrong please feel free to correct me.
Click to expand...
Click to collapse
Mne does not say that but it restarts my nook. But it does not fix it. I think its just some small starting files missing. But im not so good so i cant help it. So im just sitting and watching around internet if there is any fix. It looks that they have had the same problem with NC to start with to.
Hey, I have a problem with my Vibrant:
First I had the "Low internal storage w/ CM10, Slimbean, Hellybean due to Partition Error" and did the fix shown on XDA. However when I boot my phone it automatically goes into Android system recovery and the following in yellow letters shows:
-- Movi_check Start..!!
checksum confirmation need_checksum[1301305579]
MBR_ChkSum in header : 4.1
MBR checksum: 00A35E062CE062CE4230BC72D52C175496072
MBR Checksum Error
Movinand Checksum Confirmation Fail
-- movi_checking done!...
# MANUAL MODE #
-- Applying Multi-CSC...
Installing Multi-CSC
Then when i try to do 'reinstall packages' to install CWM, this pops up in red font:
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(Invalid argument)
E:Can't mount SDCARD:update.zip
Installation aborted.
What does kinda unbrick my phone is flashing Eugene_2E_JK2_Froyo (PDA), Vibrant_Froyo.tar (BOOTLOADER) and s1_odin_20100512 (PIT) and ticking re-partition on ODIN. This let's me go back to the stock rom, but a pop up shows that my 'Internal Memory is Damaged' and I cannot access or view the stats for my internal memory at all. And when I try to install Rom Manager I get 'Not enough space'.
I'm really stuck and would appreciate any help! Thanks!
Which "fix" did you use for low storage issue? Was it this thread http://forum.xda-developers.com/showthread.php?p=32346116
IIRC, the update.zip doesn't work in froyo. There is a work around but you need figure out the int SD card issue first.
Do you have any way of analyzing the internal SD card? Like storage analyser app or something like that?
I am Jack's inflamed sense of rejection.
i dont know this can works but you can try
here is the link
forum.xda-developers.com/showpost.php?p=26285877&postcount=12
Hi OP, I probably have very unfortunate news for you. What you are experiencing is exactly the same thing that happened to our old pal Dan_Brutal's first vibe.
He ended up sending it to me, and I could never fix it. The only thing that would boot it, was Eugene's JK2, and it had the exact same messages when attempting to flash in the stock recovery. I could never get the EU fix to work either, it seems to he a deeper problem than that.
I went as far as using the reparted method, since I could successfully connect to the phone via adb and adb shell, and rebuilt the partition table via shell, and still, nothing would work, internal sd was lost and all it would ever boot from was an Odin flash of JK2, and that sd error never went away.
After about six months of trying different fixes, we decided it was a lost cause, and a severely corrupted internal sd. That was in fact the phone that was parted out in an attempt to get Woody a USB port replacement.
I say try the EU fix/workaround, it's gonna be your best bet at getting a running phone again. I could never get it to take when I was in your shoes, but I wish you better luck than I had.
Sent from the ICZen Experience
Br1cK'd said:
Hi OP, I probably have very unfortunate news for you. What you are experiencing is exactly the same thing that happened to our old pal Dan_Brutal's first vibe.
He ended up sending it to me, and I could never fix it. The only thing that would boot it, was Eugene's JK2, and it had the exact same messages when attempting to flash in the stock recovery. I could never get the EU fix to work either, it seems to he a deeper problem than that.
I went as far as using the reparted method, since I could successfully connect to the phone via adb and adb shell, and rebuilt the partition table via shell, and still, nothing would work, internal sd was lost and all it would ever boot from was an Odin flash of JK2, and that sd error never went away.
After about six months of trying different fixes, we decided it was a lost cause, and a severely corrupted internal sd. That was in fact the phone that was parted out in an attempt to get Woody a USB port replacement.
I say try the EU fix/workaround, it's gonna be your best bet at getting a running phone again. I could never get it to take when I was in your shoes, but I wish you better luck than I had.
Sent from the ICZen Experience
Click to expand...
Click to collapse
Thanks! I decided to just give up and get a new one lol
I made a post 4-5 weeks ago about this(no one replied sadly) and since then I've been using a bootable SD card to use my tablet. I got errors before (something about cant mount E: )
I was stupid and (if i remember correctly) formatted all the partitions (don't judge, I was stupid). Since then I've tried to replace all the partitions (except for mmcblk0p11, mmcblk0p10, and mmcblk0p5).
I start the nook tablet after the process and it boots into CWM and wont leave it. I have also done the Total Wipe which works then when its in the restore process and reaches 25% before it gives me an
error saying to restart and and try again. Any help and i would be very appreciative.
DaltonHeintz said:
I made a post 4-5 weeks ago about this(no one replied sadly) and since then I've been using a bootable SD card to use my tablet. I got errors before (something about cant mount E: )
I was stupid and (if i remember correctly) formatted all the partitions (don't judge, I was stupid). Since then I've tried to replace all the partitions (except for mmcblk0p11, mmcblk0p10, and mmcblk0p5).
I start the nook tablet after the process and it boots into CWM and wont leave it. I have also done the Total Wipe which works then when its in the restore process and reaches 25% before it gives me an
error saying to restart and and try again. Any help and i would be very appreciative.
Click to expand...
Click to collapse
If you deleted all partitions (that includes DATA, ROM, etc...) then you might have a problem. I recommend using the repart.img found here if you want to restore your nook back to stock:
http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
If you just want CM installed internally then make an SD card with CWM Recovery on it along with the ROM and GAPPS files. Just install the .zip from the SD card and you'll be good.
If you have problems or need anything explained PM me.
datallboy said:
If you deleted all partitions (that includes DATA, ROM, etc...) then you might have a problem. I recommend using the repart.img found here if you want to restore your nook back to stock:
http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
If you just want CM installed internally then make an SD card with CWM Recovery on it along with the ROM and GAPPS files. Just install the .zip from the SD card and you'll be good.
If you have problems or need anything explained PM me.
Click to expand...
Click to collapse
I've already tried the repart.img before. I never got the check mark just the X and i've tried it multiple times. (but thanks for trying!)
DaltonHeintz said:
I've already tried the repart.img before. I never got the check mark just the X and i've tried it multiple times. (but thanks for trying!)
Click to expand...
Click to collapse
Try this method. http://forum.xda-developers.com/showthread.php?t=1470910
datallboy said:
Try this method. http://forum.xda-developers.com/showthread.php?t=1470910
Click to expand...
Click to collapse
I mentioned above that I have tried the Total Wipe and it only gets 25% done till it gives me an error saying to try again or contact customer service.
This should be your next step after the repart.IMG
http://forum.xda-developers.com/showthread.php?t=1513583
datallboy said:
This should be your next step after the repart.IMG
http://forum.xda-developers.com/showthread.php?t=1513583
Click to expand...
Click to collapse
Um? repart.img doesn't work... And the partitions are formatted but not corrupt or broken in any way. I've tried the parted binary before but it never asked to repair the partitions.
Here it is
http://forum.xda-developers.com/showthread.php?t=2179403
centenj said:
http://forum.xda-developers.com/showthread.php?t=2179403
Click to expand...
Click to collapse
In "some cases" it may work. But if the tablet is borked and you can't get the drivers (other than adb) to load, Then you pretty much have to boot with AdamOutlers ubuntu partition restore. There are times when you just can't get the drivers straight.
Info... It didn't work for me.
Not saying it works for all borked tab's. Everybody has to try things.
MD
First off, I am no expert so please be gentle! I previously rooted my old Samsung Galaxy S i9000 and installed ICS, which went OK, but the phone became quite slow and unstable. I was advised to install RemICS and downloaded all the zip files from this forum, and put them on the external SD card. I followed the developer's instructions to the letter, as well as reading everything I could find on the subject. The reset and data wiping went fine, but the installation of the ROM didn't. It halted with an error message -`ROM incompatible, trying to use an invalid partition'. I repeat that this is supposed to be the specific ROM for the i9000. The phone now won't boot into recovery. It stops with an orange Android logo and the text `Powered by Mackay Kernel'. It won't boot into download mode either. The Mackay screen stays there however long I leave it. I really need help from the ROM developer but I can't post to that forum. How can I either boot into recovery or into download mode? Is this ROM reliable? What could I have done wrong?
More info:
Presumably everyone is on holiday! But just in case anyone is reading, there is further news. The reason I could not start recovery mode was that the button sequence was different from what I had been told. It now boots reliably into Mackay (which of course is TWRP). I have found that the phone is unable to mount the partitions DATA and SYSTEM - they seem to be corrupted. Hence it has not wiped DATA, although TWRP wrongly reports success. I have tried updating the partitions to ext3 or ext4 but this fails every time. I could format the thing from Windows but that will wipe everything including recovery of course. I need a tool to repair these partitions, but have not found anything so far. This may well have been the reason the phone was getting creaky in the first place.
I have copied a new ROM to the external SD card, using a card reader, and inserted this into the phone. Strangely the TWRP file manager reports that EXTERNAL SD is a sub-folder of SD CARD, and that is empty. The file manager does not show the real external SD card. But the real external SD shows up on the Windows USB connection. What is going on?
When I try to mount the partitions, DATA and SYSTEM can't be checked - the other partitions (Cache, sdcard, and emmc are all checked).
kingGrn Copeland
Well for the benefit of anyone else with the same problem, I have managed to re-flash the ROM back to stock. It just took 3 days of intensive web browsing until I understood how to do it, and found software that worked - a lot of stuff out there has errors.
To summarise, the problem was:
1. Data and System partitions became damaged, so phone became unstable.
2. Attempt to upgrade ROM failed because of damaged partitions.
3. Could not boot phone into recovery or download because button combination was different from what I was told.
The solution was:
4. Boot into download mode using correct button combination.
5. Re-flash back to stock ROM and re-partition using Odin.
Yes, someone did tell me that, and I would have done that straight away if I could have gotten into download mode. We live and learn
The solution was:
4. Boot into download mode using correct button combination.
5. Re-flash back to stock ROM and re-partition using Odin.
Click to expand...
Click to collapse
Thanks this wa useful for me too.
Ok, without getting into the cascading series of screwiness along the way, I think I've managed to effectively brick my phone. I'm posting in hopes that the part of my brain screaming "No, you're missing something" is right.
e970, already rooted, running CyanogenMod 10.1 and TWRP 2.6.3.0. In pursuit of a "clean slate" to deal with remnants of sloppy uninstallations, I thought I'd clear everything with TWRP and just put CM back. So, I pulled out my SD card with my saved data, and had TWRP wipe everything, including the CM zip on the root of the built-in storage. I copied the newer CM and GAPPS to a spare SD card, plugged it in...
and I found the external SD card wasn't recognized by TWRP. There's only 1 storage location listed, which is the built-in area I just wiped.
I can't get the phone to be recognized by a desktop running Windows 8.1. I have freshly installed the drivers, downloaded the SDK, rebooted, etc. from that side. The phone is never recognized by either Windows or ADB. So, I dug out the laptop I originally installed CM from some time back (last year?). Same story - no Windows or ADB recognition.
Ok, fine - maybe the USB port is dying on me. I'll try formatting the SD card and see if that's the issue. FAT32, copy the files back, still no luck. Great. Maybe it's the card, so I copy my data and put the zips on the original card I had in the phone. Still no dice.
So, here I am. No OS installed, no image on the internal drive to recover from, TWRP won't recognize my external card(s), and I can't get anything to acknowledge the phone via USB to do a sideload.
Am I missing something, or did I completely hose myself?
I forgot to mention: I did try different cables and ports on both computers before arriving at the idea the e970 USB port may have having issues.
Have you tried a different SD card?
SD card have a finite lifespan, and I've seen them fail n the middle of normal use. The first thing I'd try would be a different SD.
If that doesn't work, you may have to just LGPNST back to bone stock.
(You may want to play with the "Partition SD Card" option under "Advanced" in TWRP. It'll wipe any data on the card so back up to your computer first, but this may kick the SD card into being recognized by the phone [though I dont know how windows would react to it])
OMGMatrix said:
Have you tried a different SD card?
SD card have a finite lifespan, and I've seen them fail n the middle of normal use. The first thing I'd try would be a different SD.
Click to expand...
Click to collapse
I did, in fact. I tried it on a spare first, so I didn't have to worry about erasing the data on the SD card I pulled out of the phone. When that failed, I tried copying the zips onto my original card, which was also not picked up. I've found other posts on here that suggest this particular version of TWRP had issues reading external cards, but I don't see any way to get a different one on the phone at this point.
OMGMatrix said:
(You may want to play with the "Partition SD Card" option under "Advanced" in TWRP. It'll wipe any data on the card so back up to your computer first, but this may kick the SD card into being recognized by the phone [though I dont know how windows would react to it])
Click to expand...
Click to collapse
I might be missing the mark here, but wouldn't this format the already-empty internal storage (since it's the one selected) rather than the external card?
elvinone said:
I did, in fact. I tried it on a spare first, so I didn't have to worry about erasing the data on the SD card I pulled out of the phone. When that failed, I tried copying the zips onto my original card, which was also not picked up. I've found other posts on here that suggest this particular version of TWRP had issues reading external cards, but I don't see any way to get a different one on the phone at this point.
Click to expand...
Click to collapse
If you can boot the phone into fastboot (should be VOL UP + Power), you should be able to flash the recover that way with:
fastboot flash recovery <name of recovery>.img
You'll need to get the .img instead of a flashable zip obviously, but that can be done even by grabbing the "recovery.img" file from a flashable recovery zip.
elvinone said:
I might be missing the mark here, but wouldn't this format the already-empty internal storage (since it's the one selected) rather than the external card?
Click to expand...
Click to collapse
I've honestly not messed with this option; I just know I've solved similar problems with flash drives in the past by formatting in different ways.
OMGMatrix said:
If you can boot the phone into fastboot (should be VOL UP + Power), you should be able to flash the recover that way with:
fastboot flash recovery <name of recovery>.img
You'll need to get the .img instead of a flashable zip obviously, but that can be done even by grabbing the "recovery.img" file from a flashable recovery zip.
Click to expand...
Click to collapse
How is he going to do that? He can't get a PC to recognize the phone.
Maybe try a Linux box? You could make an Ubuntu live USB stick with some extra storage space on it, and try running adb from there.
Sent from my LG Optimus G using Tapatalk
dandrumheller said:
How is he going to do that? He can't get a PC to recognize the phone.
Maybe try a Linux box? You could make an Ubuntu live USB stick with some extra storage space on it, and try running adb from there.
Sent from my LG Optimus G using Tapatalk
Click to expand...
Click to collapse
There's a thought... I think I have a Knoppix disk around here that I could boot from. I don't have high hopes, since it's not being recognized by the laptop I did this on originally, but I'll give anything a shot at this point. I'll let you know how it goes.
No dice. ADB gives me the same response whether the phone is at the fastboot screen or the sideload inside TWRP.
[email protected]:~/Documents/android-sdk-linux/platform-tools$ ./adb start-server
[email protected]:~/Documents/android-sdk-linux/platform-tools$ ./adb devices
List of devices attached
[email protected]:~/Documents/android-sdk-linux/platform-tools$
Click to expand...
Click to collapse
OMGMatrix said:
(You may want to play with the "Partition SD Card" option under "Advanced" in TWRP. It'll wipe any data on the card so back up to your computer first, but this may kick the SD card into being recognized by the phone [though I dont know how windows would react to it])
Click to expand...
Click to collapse
I tried this but didn't have any luck. It looks like it is trying to hit the external card, but still isn't recognizing it.
E: Unknown File System: 'datamedia'
Updatition partition details...
Partitioning SD Card...
E: Unable to locate device to partition.
Click to expand...
Click to collapse
Check ALL your cords
Another update. After presuming me e970 dead, going to Best Buy to shop for an AT&T Next upgrade, running the HTC One m8 for a couple days, I get a wild hair to try the HTC cord on the old phone. Oddly enough, it works and the phone was picked up immediately. I've already pushed CM over via adb, and and working on gapps now.
Apparently both of the cords I tried previously weren't up to spec for smartphone use. I'm going to have to come up with a labelling system on what's good for trickle charges and what's good for data.
I'm not sure what a return will do to my upgrade status, but I'd rather wait on a new phone. It even looks like I know what I'll get. Thanks for the ideas along the way.
Nice, glad you found a solution. Unless things have changed with the new plans, you should be OK to return the phone within 14 days and keep your upgrade.
Sent from my LG Optimus G using Tapatalk