***This is an unofficial and early build of TWRP that has not been updated since 2021. If you want a functional custom recovery, get the official LineageOS Recovery from the LineageOS Thread.***Disclaimer:
Code:
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
Warning: This build is still WIP in early stages. I posted this version so everyone can at least flash magisk and other standard zips without too much hassle. Expect bugs and possibly other unexpected behaviors, especially if you attempt to use any features not listed below. Currently working on encryption and getting the other TWRP features online.
=========
Update (10/14/2021): I am taking a hiatus from this unofficial TWRP build. With that being said, you are welcome to fork the device tree at the bottom of the post or submit PRs. I may continue working on this when I have more time, but I'm sure another experienced developer will be able to pick up and accomplish what I had trouble with before.
=========
What Works:* Booting to TWRP.
* Installing ZIPs.
* System, Product, Vendor, ODM, opluslog, Metadata, Persist, modem.
* a/b slot
* sdcard
What doesn't work:* userdata decryption. Requires forceencrypt disabler.
* Backup for any partition besides Super.
* Restore
* Factory Reset
* CPU temperature
Downloads:0.2.0: https://www.androidfilehost.com/?fid=7161016148664790178
0.1.0: https://www.androidfilehost.com/?fid=7161016148664789523
Installation:
1. Run
Code:
fastboot boot twrp-3.5.2-11-holi.img
. This will not boot you to twrp, but you should see the device boot to system successfully. If it boots properly, run adb reboot bootloader. If it bootloops or freezes, STOP. Leave your model number in the comments and force reboot your device.
Click to expand...
Click to collapse
2. Run
Code:
fastboot getvar current-slot
to get your current active partition slot. If it's A, then run
Code:
fastboot flash boot_a twrp-3.5.2-11-holi.img
. If it's B, run
Code:
fastboot flash boot_b twrp-3.5.2-11-holi.img
Click to expand...
Click to collapse
3. Run
Code:
fastboot reboot
to get back to the system
Click to expand...
Click to collapse
This release is built w/ the stock kernel (5.4.61-qgki-gf8e532b).
Source
Manifest: https://github.com/minimal-manifest-twrp/platform_manifest_twrp_aosp
Device Tree: https://github.com/EnumC/android-OnePlusN200TMO-TWRP
Pull requests to the device tree are welcome!
Changelog:
0.2.0: Add external SD card support & crypt libraries
0.1.0: Initial device support
i replied to your post in the other thread, perhaps maybe this can help with decryption/encryption .... https://forum.xda-developers.com/t/rooting-stock-firmware-w-magisk.4321575/#post-85504141
Enumc, thanks for the contribution and your time
@EnumC You da best! Really appreciate what you have done for us!
First, thank you @EnumC great work. Second, anyone know how would I go about installing a zip if TWRP can't see anything in downloads and can't see the SD card. TIA
Link575 said:
First, thank you @EnumC great work. Second, anyone know how would I go about installing a zip if TWRP can't see anything in downloads and can't see the SD card. TIA
Click to expand...
Click to collapse
Push to /tmp or /sdcard.
EnumC said:
Push to /tmp or /sdcard.
Click to expand...
Click to collapse
Thank you
Link575 said:
First, thank you @EnumC great work. Second, anyone know how would I go about installing a zip if TWRP can't see anything in downloads and can't see the SD card. TIA
Click to expand...
Click to collapse
Added SD card support in 0.2.0 if you need to store larger files, Check the Mount tab and make sure sdcard 1 is checked, then it should be mounted under /sdcard-1/. If you have more than one partition, then it will show up as sdcard 2, 3, etc.
Please let me know if anything is not working correctly.
Wow been working a lot of overtime the last couple of days and left with the rom had been dumped and now we have twrp.... Sucks I'm on call and can't unlock my bootloader until Monday just in case.......
EnumC said:
Added SD card support in 0.2.0 if you need to store larger files, Check the Mount tab and make sure sdcard 1 is checked, then it should be mounted under /sdcard-1/. If you have more than one partition, then it will show up as sdcard 2, 3, etc.
Please let me know if anything is not working correctly.
Click to expand...
Click to collapse
Oh wow nice, I'll try it out tomorrow and let you know if I run into any issues. Thanks
Tried out new build of TRWP, everything worked fine.
@EnumC
1I tried 0.2.0 but my storage is weird.
1) I did not see internal storage.
2) SD card (0mb)
I am still able to boot into the system with no issue. Not sure if this is the issue for TWRP?
And I tried to reboot to the recovery. It says no OS installed? why?
MOUNT: "sdcard1" is checked.
but System is not checked. I manually checked it and rebooted. But when I go back in, SYSTEM is still unchecked.
And Recovery will be FROZEN once a while. Need to use Hard reboot to get out of Recovery mode.
Anything I did wrong? (was trying to flash Magisk from SD card).
Please advise. Thanks!
ttar ttar said:
@EnumC
1I tried 0.2.0 but my storage is weird.
1) I did not see internal storage.
2) SD card (0mb)
I am still able to boot into the system with no issue. Not sure if this is the issue for TWRP?
And I tried to reboot to the recovery. It says no OS installed? why?
MOUNT: "sdcard1" is checked.
but System is not checked. I manually checked it and rebooted. But when I go back in, SYSTEM is still unchecked.
And Recovery will be FROZEN once a while. Need to use Hard reboot to get out of Recovery mode.
Anything I did wrong? (was trying to flash Magisk from SD card).
Please advise. Thanks!
Click to expand...
Click to collapse
That's mostly correct! When you mounted SD card 1, the mounting point is /sdcard-1. Don't press "Select Storage". When you mount anything, it mounts immediately -- no reboot needed. Ignore the "No OS Installed" warning, and don't reboot to Recovery from recovery. That causes freezing at the moment. userdata decryption is not working at the moment, so that's why you can't mount internal storage.
EnumC said:
That's mostly correct! When you mounted SD card 1, the mounting point is /sdcard-1. Don't press "Select Storage". When you mount anything, it mounts immediately -- no reboot needed. Ignore the "No OS Installed" warning, and don't reboot to Recovery from recovery. That causes freezing at the moment. userdata decryption is not working at the moment, so that's why you can't mount internal storage.
Click to expand...
Click to collapse
Cool. So what should I do now if I want to flash Magisk? Wait for your 0.3.0 version?
ttar ttar said:
Cool. So what should I do now if I want to flash Magisk? Wait for your 0.3.0 version?
Click to expand...
Click to collapse
Flash it! If you have an SD card, then put the zip in the SD card, and flash from /sdcard-1. If not, connect it to your computer and run "adb push yourmagisk.zip /tmp" and flash from /tmp.
@EnumC, while the SD was able to be seen, it had the same issue as internal storage where no files could be seen and had to be pushed. I just kinda assumed this was how it was supposed to be but if not then yea, it's not working right.
Link575 said:
@EnumC, while the SD was able to be seen, it had the same issue as internal storage where no files could be seen and had to be pushed. I just kinda assumed this was how it was supposed to be but if not then yea, it's not working right.
Click to expand...
Click to collapse
Did you format the card as exfat/fat/ext3/ext4?
EnumC said:
Did you format the card as exfat/fat/ext3/ext4?
Click to expand...
Click to collapse
I did not format it so I'd have to check what it is formatted for. It used to be in my Note 4 so I just took it out and put in this phone. System normally reads it fine. What format should it been in?
Link575 said:
I did not format it so I'd have to check what it is formatted for. It used to be in my Note 4 so I just took it out and put in this phone. System normally reads it fine. What format should it been in?
Click to expand...
Click to collapse
Preferably fat or exfat since those are the ones I've tested on my end. If that doesn't work, please run "adb logcat > twrp.log" and attach the file.
EnumC said:
Preferably fat or exfat since those are the ones I've tested on my end. If that doesn't work, please run "adb logcat > twrp.log" and attach the file.
Click to expand...
Click to collapse
SD is in FAT32, ran adb logcat then twrp.log so assuming this is what you wanted. If not let me know.
Related
Due to popular demand I have created a size-agnostic SDCard CM7 installer.
Also allows to install unmodified CM7 builds on SD card.
Current version: 1.3
Grab the installer image here:
http://crimea.edu/~green/nook/generic-sdcard-v1.3.img.gz
it's a ~9M image that would unpack into ~130M disk image.
Also note - not all SD cards are created equal. Here is a thread of interest is you have not bought one yet: http://forum.xda-developers.com/showthread.php?p=12964262
Short version: buy Sandisk-branded class 4 microSD cards.
Write the image on your SD card. I tested with 2G, 4G and 8G cards and all worked.
Any uSD card of 1G or bigger in size should work if it is recognized by your nook.
Write on Windows by using WinImage and on Linux/MacOS X by using dd (to the entire device, not one of the partitions. The device name should not have any numbers at the end. The command is something like dd if=/somewhere/generic-sdcard.img of=/dev/sdX bs=1024k)
After done with writing, eject and then re-insert the uSD card into your computer.
Download a CM nightly build from here http://download.cyanogenmod.com/?device=encore (It is recommended to choose -87 nightly or later. If you plan to use prior version for initial install, stick with installer 1.2.1 for a different u-boot version)
Or just use your own update-cm-*-KANG-signed.zip file that is produced if you do your own builds.
The image would correctly detect unmodified CM7 builds and would make necessary adjustments to make them work on SD card.
Put the file to the SD card (there is only one partition). Don't change the name of the file.
unmount the uSD card and insert it into the nook.
Boot from this SD card. It'll boot and will update you on progress.
When it's done, it'll power off.
That's it, you now have CM7 on your SD card.
How to install market and gapps:
After you have booted into the CM7 on SD card for the first time and set up wifi access (important!)
Go to http://wiki.cyanogenmod.com/index.php?title=Latest_Version and at the end there is a table with various google apps versions. Get the one suitable for your cyanogen version (CM7 is the latest for now). The file is named gapps-....zip
shutdown your nook and take the SD card out, insert it into your computer.
Copy the gapps-... file to the SD card on the first partition (titled boot) without changing the file name.
Insert the uSD card back into the NOOK and boot into "Recovery mode" (hold nook N key and then press and hold power until the "Loading..." message appears and then disappears with screen going blank. Release power button, then press it again and hold for ~5 seconds, the bootloader "Loading..." message should be on the screen for three seconds or so before you release power button, keep holding N button until screen blanks again. If the screen went off while you were holding the power key, that means you were holding it for too long).
Alternatively if you do not want to fight the timing, boot normally into Android, then from desktop hold power key until a poweroff menu appears, In the poweroff menu choose "reboot", in the next menu choose "recovery" and press "OK". The nook would reboot straight into recovery.
How to update to a new build:
put the new build you want to try on the first partition. (the name must be update-cm-*.zip or cm_encore_full*.zip or just update-*.zip)
Boot from the SDcard in the recovery mode (see above) and the new snapshot would be installed.
The partition layout would be preserved, filesystems are NOT reformatted, so your data should be safe.
Installing other stuff:
Booting in recovery mode would install all files that are named "update-..." and end with .zip The files would then be deleted! Most of the packages should work, but I only tested a subset and not entire syntax of updater script is implemented. Certainly format and delete are not implemented.
OC Kernel installation instructions:
Starting with v1.2.1 there are no special instructions, install normally as described above.
Partition layout for the SD cards depends on size:
Less than 600M - unsupported.
up to 1G cards gets: system of ~300M and data of the rest of space. No FAT partition
2G cards (more than 1G up to 1800M) gets: 300M system, 612M data, rest is FAT sdcard
more than 2G cards gets: 460M system, 975M data, rest is FAT for sdcard.
How to update if you already installed using older version of the installer and don't want to reinstall (understandably):
Get update zip from http://crimea.edu/~green/nook/update-genimage-1.3.zip
Put the zip file as is onto the first partition of your sdcard..
reboot into recovery (triggered by the keys, the reboot into recovery does not work yet).
The new version would be installed and you are done.
You can combine this installation together with updating to .32 kernel in one step. Just put the update-cm file and the update-genimage-1.3.zip to the first partition. Make sure there is still at least 1M of space left!
Changes in 1.3
Install u-boot.bin and MLO loaders if provided.
Fixed a problem that led to overwrite of recovery kernel if a nightly was installed more than once)
(only in full image) updated u-boot to ignore BCB as that was a common source of problems. (that's why this version is not recommended for initial install with older nightlies, those don't provide a more correct u-boot for later operations. It's fine to do the update from older installer release, though)
Changes in 1.2.1
Really fixed dalingrin kernel packages installation
A bit more robust handling of install scripts
Changes in 1.2
Updated to new u-boot from B&N 1.2 update
Ability to obey BCB in eMMC (allows reboot into recovery from CM7)
Hopefully simplified the timing to trigger recovery boots from keyboard
Added support for Dalingrin's kernel update packages
The v1.1 version that is known good to work with 2.6.29 kernel releases is located at http://crimea.edu/~green/nook/generic-sdcard-v1.1.img.gz
This is very cool, thanks! My father bought a nook color after seeing mine, and after hearing what I have been able to get mine to do (thanks to the efforts of all the devs here) he has wanted to play a little more with his. Thanks to you, I have an easy way to set up the SD card and then ship it up to him. I can give him a taste without having to force him to even root his yet. Thanks again!
Very nice! Thanks.
Care to share the dates and differences between your build and say CM's? or perhaps a link to your builds progress?
I know you have done great work with BT, didn't want to get off topic, but I'm curious.
Thanks again.
12paq said:
Very nice! Thanks.
Care to share the dates and differences between your build and say CM's? or perhaps a link to your builds progress?
I know you have done great work with BT, didn't want to get off topic, but I'm curious.
Thanks again.
Click to expand...
Click to collapse
I did not work on BT (other than helping with testing), so I don't claim any credits there.
The difference between standard build and my build so far is only that my build has patched init files to boot from SD right in the zip file. (CM7 checkout as of today ~12pm), it was only created for testing, before I rolled the code that could update vanilla builds to work on SD cards.
You can use unmodified CM7 nightlies with this sdcard image now. The image itself does not contain any CM7 code, you need to copy zip file with it after writing the image to the SD card, but before attempting to boot.
Verygreen, I believe you have won the game. Congratulations!
Ah yes, I stand corrected, you created the first CM7 sd bootable for testing of BT.
Thanks again for your time on this latest project!
First off, this works very well! Thanks!
Now, after getting CM7 running on the sdcard, I plug the device into the usb port on my computer and instruct it to mount the sdcard. But, instead of the sdcard partition being mounted, the emmc partition is mounted.
Was that intentional or is it a bug?
Thanks
Thanks very easy to setup!
atomclock said:
First off, this works very well! Thanks!
Now, after getting CM7 running on the sdcard, I plug the device into the usb port on my computer and instruct it to mount the sdcard. But, instead of the sdcard partition being mounted, the emmc partition is mounted.
Was that intentional or is it a bug?
Thanks
Click to expand...
Click to collapse
New code in CM7 actually should cause both internal MMC AND sdcard to be mounted.
That is unless you used 1G sdcard, 1G sdcard does not have any mountable free space and then you'd only see emmc content as mountable.
verygreen said:
New code in CM7 actually should cause both internal MMC AND sdcard to be mounted.
That is unless you used 1G sdcard, 1G sdcard does not have any mountable free space and then you'd only see emmc content as mountable.
Click to expand...
Click to collapse
I'm using an 8Gb sdcard and I can access both the emmc and sdcard partitions through ADB but only the emmc partition is mounted.
So, I just need to try this with a different nightly build until I find one where the issue is corrected?
Well, I tried it with both cm_encore_full-25 and cm_encore_full-26 and still only the emmc partition is mounted.
atomclock said:
I'm using an 8Gb sdcard and I can access both the emmc and sdcard partitions through ADB but only the emmc partition is mounted.
So, I just need to try this with a different nightly build until I find one where the issue is corrected?
Well, I tried it with both cm_encore_full-25 and cm_encore_full-26 and still only the emmc partition is mounted.
Click to expand...
Click to collapse
As long as everything is mounted internally I don't think my changes broke anything else, so if there is a bug it's in the CM7 build itself.
I don't actually mount my nook on the computer, so I don't even know how to enable it by default come think of it.
I just know there was an ongoing work in this area to allow simultaneous mounting of multiple volumes and I heard it was already included, though I am not 100% sure about that.
To verygreen:
Well, I'm certainly doing something wrong here:
1. Using Win32DiskImager release 0.2 r23, i burnt my 2 GB with your generic.... .img image.
2. Copied your update.... .zip (on a second attempt an original cm_encore... .zip, plus gapps-GB-20110307-...zip, as installer was asking for it, at least to inflate), now I suspect your "put" is not equal to my "copy".
3. Tried to boot, enjoyed the penguin and boot scroll, but after everything was finished and prepared to "really" boot the boot was executed from my eMMC instead.
aludal said:
To verygreen:
Well, I'm certainly doing something wrong here:
1. Using Win32DiskImager release 0.2 r23, i burnt my 2 GB with your generic.... .img image.
2. Copied your update.... .zip (on a second attempt an original cm_encore... .zip, plus gapps-GB-20110307-...zip, as installer was asking for it, at least to inflate), now I suspect your "put" is not equal to my "copy".
3. Tried to boot, enjoyed the penguin and boot scroll, but after everything was finished and prepared to "really" boot the boot was executed from my eMMC instead.
Click to expand...
Click to collapse
Yes, the automatic reboot boots into eMMC for now, I am looking into it.
So just reboot again with the card in.
also, don't put gapps on the card at the first try. This combination does not boot for me into the desktop for some reason that I did not get to the root of. Possibly because it want internet connection setup that still is not if you try it on your first boot.
Thanks verygreen! This is a fantastic build! I was able to quickly and easily install this on my sd card.
Thanks again!
verygreen said:
Yes, the automatic reboot boots into eMMC for now, I am looking into it.
So just reboot again with the card in.
also, don't put gapps on the card at the first try. This combination does not boot for me into the desktop for some reason that I did not get to the root of. Possibly because it want internet connection setup that still is not if you try it on your first boot.
Click to expand...
Click to collapse
Somehow I went into non-booting phase, lol. My guess is after booting into my rooted Eclair with bookmarks-and-other-stuff-to SD I've got me an SD card not really good for "second" boot. Just have no idea what Eclair might do to that EXT4.
Anyways, repeated the experiment, now with pressing Power for >5 sec. Has booted into CyanogenMod 7 without a problem.
Can't do whatever testing: missing GAPPS very mucho! Please, Mr. verygreen, compile it into your image. In any case, I'm not really interested in swapping nightlies on this card -- by the last commits they didn't change much/significantly since n18. Just a static SD image of CM7 n26 + latest (03072011) Gapps will be a very desirable "mod" of yours. In any case you did exactly that (minus Gapps) for n17. Sure, there's a complete procedure of building SD image, but it's obviously much better followed when with a Linux box, and I don't have it.
aludal said:
Somehow I went into non-booting phase, lol. My guess is after booting into my rooted Eclair with bookmarks-and-other-stuff-to SD I've got me an SD card not really good for "second" boot. Just have no idea what Eclair might do to that EXT4.
Click to expand...
Click to collapse
Supposedly nothing. I routinely boot into eclair and then insert CM7 sdcard and it's fine.
aludal said:
Can't do whatever testing: missing GAPPS very mucho! Please, Mr. verygreen, compile it into your image. In any case, I'm not really interested in swapping nightlies on this card -- by the last commits they didn't change much/significantly since n18. Just a static SD image of CM7 n26 + latest (03072011) Gapps will be a very desirable "mod" of yours. In any case you did exactly that (minus Gapps) for n17. Sure, there's a complete procedure of building SD image, but it's obviously much better followed when with a Linux box, and I don't have it.
Click to expand...
Click to collapse
I can't distribute gapps, like I said
Well, until I figure out why recovery boot does not work what you can try to do is this:
after initial install was successful (and you setup your wireless), power off the nook, get the sd card.
Download gapps-gb-...zip and put it on the first partition.
move the uImage file to uImage.bak and uRamdisk to uRamdisk.bak.
Copy uRecImage to uImage and uRecRam to uRamdisk.
boot with the resulting image. It should say that it found the gapps archive and unpack it.
After it flushes caches and reboots, power off, put the sd card back into the computer
move uImage.bak to uImage and uRamdisk.bak to uRamdisk
boot off the card again, hopefully the gapps are working after that.
Please let me know if any problems arise.
verygreen said:
Supposedly nothing. I routinely boot into eclair and then insert CM7 sdcard and it's fine.
I can't distribute gapps, like I said
Well, until I figure out why recovery boot does not work what you can try to do is this:
after initial install was successful (and you setup your wireless), power off the nook, get the sd card.
Download gapps-gb-...zip and put it on the first partition.
move the uImage file to uImage.bak and uRamdisk to uRamdisk.bak.
Copy uRecImage to uImage and uRecRam to uRamdisk.
boot with the resulting image. It should say that it found the gapps archive and unpack it.
After it flushes caches and reboots, power off, put the sd card back into the computer
move uImage.bak to uImage and uRamdisk.bak to uRamdisk
boot off the card again, hopefully the gapps are working after that.
Please let me know if any problems arise.
Click to expand...
Click to collapse
I just tried following your directions for installing the gapps zip file. After renaming the uImage and the uRamdisk files the nook boots to your recovery with the penguin shows up with the follow:
Populating /dev using udev: done
Initializing random number generator....done
modprobe: chdir (2.6.32.9): No such file or directory
Starting network...
Detected Standard B&N nook layout, emmc first
It appears the SD card is already properly formatted
Skipping format
Mounting /dev/mmcblk1p1 as /boot
Looking for the install images....
Initial Install files not found
Please download it from nook.linuxhacker.ru
and put on first partition of this SD card
the name should start with updatei-cm and end with .zip
Then the cursor just sits. No installation of the .zip file. Do I have to have the original cm zip file on the sd card with the gapp zip file? I thought it was posted that doesn't work.
Also thanks for the great work on this so far.
Absolutely Fantastic and pain free. You have done a great service.
Thanks
verygreen -
Would this work with an Android 3.0 Honeycomb Preview build, instead of a CM7 build ?
Modra76 said:
I just tried following your directions for installing the gapps zip file. After renaming the uImage and the uRamdisk files the nook boots to your recovery with the penguin shows up with the follow:
Populating /dev using udev: done
Initializing random number generator....done
modprobe: chdir (2.6.32.9): No such file or directory
Starting network...
Detected Standard B&N nook layout, emmc first
It appears the SD card is already properly formatted
Skipping format
Mounting /dev/mmcblk1p1 as /boot
Looking for the install images....
Initial Install files not found
Please download it from nook.linuxhacker.ru
and put on first partition of this SD card
the name should start with updatei-cm and end with .zip
Then the cursor just sits. No installation of the .zip file. Do I have to have the original cm zip file on the sd card with the gapp zip file? I thought it was posted that doesn't work.
Also thanks for the great work on this so far.
Click to expand...
Click to collapse
Seeing the same. Also tried naming the gapps file "update.zip", to no avail.
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.
Hello All,
I can see my files are all there (on the external sd card located permanently inside the TF201) when look via the pc but recovery doesn't seem to be able to mount the internal sdcard so I cannot get at the zip files I put on the internal sdcard to flash from recovery.
I was running a very happy TF201 running Virtuous Prime until I decided to change a font a few days ago. That was a bad move. On reboot everything was stuck on the intro splash screen. I managed to get into recovery & somehow managed to get my new rom (CM10 ish) flashed & i thought all was well until I realised that in all the 'heat of battle' the usual wipe re wipe/wipe dalvick/reset privileges routine had been omitted from my routine. Worse still I had flashed the rom but not yet flashed the Jelly Bean GAPPS.
So the system was still hanging at the splash screen (although this time at least it was the CM10 splash screen (progress is so sweet) but now, just when I thought it couldn't get any worse, when I go into recovery to apply a zip from an sdcard I get told that E:Can't mount /sdcard/ so I cant get at my file to flash!
I'm 3 days into this now & I am definitely loosing the plot so please please give me a nudge in the right direction .A have adb up & running & have just fastbooted a new recovery img over onto the prime because I read that this might sort my problem. Well, it didn't so here I am. Please assume I am a noob 1st class although I may surprise you with some of my knowledge that I've picked up over the last few days & years working in systems (though not Android) so maybe I wont!
Get this sorted with me & I'll be forever in your debt. Please let me know what other information you may need to give me a push in the right direction. Thanks for reading this & thanks for deciding to help me hang on to that thread of sanity that is left.
I have also asked for help on TransformerForums; because I'm new to this site I cannot provide you with the link. Sorry.
correct me if i got this wrong; so you are able to get into CWM und you see your device via
Code:
adb devices
right?
now can you push files via
Code:
adb push
to your device?
If so we had the exact same problem don't worry theres a fix for this:
first if you're in adb type:
Code:
adb shell
now you should see this "#" somewhere in front of your command line
type
Code:
ls
now it should show you the folders on your device, try to navigate to the directory /data/media via
Code:
cd /data/media/
now push the rom you want to flash in this directory, for example:
Code:
adb push ROM.zip /data/media/ROM.zip
the rom should be in the same folder as your adb.exe
essentially /data/media is your internal storage so you should now be able to flash the rom of your choice.
I hope i could help because I had almost exactly the same problem and was about to go crazy until i found this solution
success...
s0undless said:
correct me if i got this wrong; so you are able to get into CWM und you see your device via
Code:
adb devices
right?
now can you push files via
Code:
adb push
to your device?
If so we had the exact same problem don't worry theres a fix for this:
first if you're in adb type:
Code:
adb shell
now you should see this "#" somewhere in front of your command line
type
Code:
ls
now it should show you the folders on your device, try to navigate to the directory /data/media via
Code:
cd /data/media/
now push the rom you want to flash in this directory, for example:
Code:
adb push ROM.zip /data/media/ROM.zip
the rom should be in the same folder as your adb.exe
essentially /data/media is your internal storage so you should now be able to flash the rom of your choice.
I hope i could help because I had almost exactly the same problem and was about to go crazy until i found this solution
Click to expand...
Click to collapse
This has sorted the problem. Thank you very much for this. Could you please tell me the significance of the 'ls' line?
I followed your instruction which resulted in my being able to flash a ROM which still hung at the intro flash screen. Since I could now see the internal file system was mounting (& accessible) I decided to attempt to replace the recovery package with TWRP which is absolutely fantastic; you are able to access both internal & external sdcards + there's a very intuitive 'touch' UI.
I was beginning to wonder if I was going to get out of this one, but, thanks to you all is well.
ls is just to ensure you are in the right directory. the next time your rom is stuck at the boot screen try to give it some more time if this doesn't work wipe the dalvik and cache via recovery and it should be able to boot if flashing was successful. and yes you are absolutly right TWRP is waaay better than CWM. Glad I was able to help you get this sorted.
Enjoy your Weekend
soundless
No dice
I have same issue as user above. I connect my TF201 to my computer and I get Driver issues saying This device cannot start. (Code 10). I did everything restared computer, deleted drivers scan hardware changes reinstalled drivers, and everything. I can't get the adb working. I keep scanning and it says there isn't any devices.
I had a bad ROM flash and my TF201 will no longer boot. I can get it into the CWM v5.8.3.4 but it will not read my SD card. I tried 3 SD cards and none of them will read. I formatted them FAT32 from what I read and even tried FAT and NTFS just to see if that made a difference and that didn't work. WHen I click to install zip from sdcard it points to my internal storage. I created a backup but again just my luck the first time while reading on ways to fix the issue I ended up in the Asus fastboot load screen and being use to the CWM commands I hit volume down (moved cursor to the left hovering over wipe data) and hit volume up thinking it would go back to the USB symbol but that wiped all the data off the device.
I restared and booted back into CWM and selected install zip from SD card now nothing shows up since it no longer reads any internal data (accidently deleted) and it doesn't read my SD card.
So, at this point I feel I'm out of ideas. ADB doesn't work to try transfering a file directly to the device and CWM doesn't read SDcards so I can't flash a new ROM on the device to get it working again.
Any help would be much appreciated.
Why is CWM still used !!!!!
All recent bricks I've seen here were CWM related!!
See here: http://forum.xda-developers.com/showthread.php?t=1841001 second post for replacing cwm by twrp.
Just had this issue with the bad cm10 rom. TWRP saved the day!
---------- Post added at 02:04 PM ---------- Previous post was at 02:02 PM ----------
Crezabek said:
I have same issue as user above. I connect my TF201 to my computer and I get Driver issues saying This device cannot start. (Code 10). I did everything restared computer, deleted drivers scan hardware changes reinstalled drivers, and everything. I can't get the adb working. I keep scanning and it says there isn't any devices.
I had a bad ROM flash and my TF201 will no longer boot. I can get it into the CWM v5.8.3.4 but it will not read my SD card. I tried 3 SD cards and none of them will read. I formatted them FAT32 from what I read and even tried FAT and NTFS just to see if that made a difference and that didn't work. WHen I click to install zip from sdcard it points to my internal storage. I created a backup but again just my luck the first time while reading on ways to fix the issue I ended up in the Asus fastboot load screen and being use to the CWM commands I hit volume down (moved cursor to the left hovering over wipe data) and hit volume up thinking it would go back to the USB symbol but that wiped all the data off the device.
I restared and booted back into CWM and selected install zip from SD card now nothing shows up since it no longer reads any internal data (accidently deleted) and it doesn't read my SD card.
So, at this point I feel I'm out of ideas. ADB doesn't work to try transfering a file directly to the device and CWM doesn't read SDcards so I can't flash a new ROM on the device to get it working again.
Any help would be much appreciated.
Click to expand...
Click to collapse
Use Fastboot and flash TWRP Recovery. CWM still cannot use external sd cards! There are simple instructions on their website.
TWRP will give you the option to install from either the internal sd card or external sd card. I've found it to be a better bet all round than clockwork mod recovery. It uses a touch interface which saves more time than you'd imagine. Just one tip; occasionally the contents of the external sd card don't show. If that happens, just reboot into recovery (again) & everything will be as it should be. Hope this helps.!...
Sent from my GT-I9100 using xda premium
Crezabek said:
I have same issue as user above. I connect my TF201 to my computer and I get Driver issues saying This device cannot start. (Code 10). I did everything restared computer, deleted drivers scan hardware changes reinstalled drivers, and everything. I can't get the adb working. I keep scanning and it says there isn't any devices.
I had a bad ROM flash and my TF201 will no longer boot. I can get it into the CWM v5.8.3.4 but it will not read my SD card. I tried 3 SD cards and none of them will read. I formatted them FAT32 from what I read and even tried FAT and NTFS just to see if that made a difference and that didn't work. WHen I click to install zip from sdcard it points to my internal storage. I created a backup but again just my luck the first time while reading on ways to fix the issue I ended up in the Asus fastboot load screen and being use to the CWM commands I hit volume down (moved cursor to the left hovering over wipe data) and hit volume up thinking it would go back to the USB symbol but that wiped all the data off the device.
I restared and booted back into CWM and selected install zip from SD card now nothing shows up since it no longer reads any internal data (accidently deleted) and it doesn't read my SD card.
So, at this point I feel I'm out of ideas. ADB doesn't work to try transfering a file directly to the device and CWM doesn't read SDcards so I can't flash a new ROM on the device to get it working again.
Any help would be much appreciated.
Click to expand...
Click to collapse
Did updating recovery sort this out? If not, shout & I may be able to help.
Some people act this way: come to ask for help, and never come back...
Hi all,
I was using latest Revolver and gave a try on CM10 Beta4
I can open a adb shell but could not execute adb push file /dir propertly
EE:Can't mount /sdcard
damn!
wish restore my Revolver4 backup :good:
rafael_mfr said:
Hi all,
I was using latest Revolver and gave a try on CM10 Beta4
I can open a adb shell but could not execute adb push file /dir propertly
EE:Can't mount /sdcard
damn!
wish restore my Revolver4 backup :good:
Click to expand...
Click to collapse
push it to /data/media
sent from my i9250
bk201doesntexist said:
push it to /data/media
sent from my i9250
Click to expand...
Click to collapse
I tried to push it already, but I can't as mentioned before.
ADB recognizes my device, open 'adb shell' but push command don't work.
push file.zip /data/media/file.zip
*file is on the same folder as adb.exe
EDIT: Resolved using EasyFlasher Tool. As described on this post.
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
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