[Guide] Encryption Unsuccessful - Reset Android [ICS Issue] - Captivate Android Development

Note: This guide is geared toward the Samsung Captivate. If you have a different device, try your device's forum, or search this thread.
Are you using ICS and pulled your phone out of your pocket only to find that it had this screen, saying "Encryption unsuccessful" and your only option a button that said "Reset Phone"? Don't press it! Try rebooting a few times with your external sdcard out first. Sometimes that will fix the issue. If not, take a deep breath and follow the guide below to get your phone usable again:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Too late? Already hit the button? Then you know this screen:
Here's the bad news:
Your partitions for /data and /sdcard are no longer accessible. Latest news points to a bug in the firmware for the memory card in your phone. ICS uses a new function that doesn't work correctly with the affected phones.
Good news:
I found a *workaround* to get my phone to at least work again. Note: You will need to perform steps 9-11 every time you flash a ROM or ROM update, because flashing overwrites the vold.fstab file.
Here were my steps to get your phone working again:
Realize that you may have just lost whatever was on your sdcard and it's your own fault. For me, this was acceptance that *I* installed ICS on my phone and now CWM backups, photos, and more were gone. Once your realization has set in, move forward.
Acquire an micro SD card that you will put into your phone. This will contain your new /data partition as well as your new /sdcard partition. I recommend at least 8GB. If you already have a card, backup whatever is currently on your micro SD card - you *WILL LOSE* everything on this card in the next few steps.
Boot into clockwork mod, using either 'adb reboot recovery', or some other combination of buttons.
Partition your mircosd card through CWM. This will be 'advanced' then 'Partition SD Card'. The first size you choose will be the size of your /data partition. I have a 16GB card and chose 2GB for /data. This will leave me with (16GB-2GB) 14GB for /sdcard. You can choose a different size if you like, depending on how big you want your internal data partition to be. Choose 0M for swap. This process will take a few minutes, so keep waiting, you impatient jerk.
Download the latest build of ICS for your phone and put it on your micro SD card. (You can mount it to your computer at this point in CWM with 'mounts and storage' 'Mount USB storage')
Create a full backup. Just in case. Put it on a computer, dropbox, whatever. Your phone isn't a safe place for backups.
Wipe user data, cache, & system. Now install the ICS package you just put on your card and reboot.
The first boot will take a while, as all first boots do, but after a while you should be back in ICS. Exhale (If you're not exhaling at this point, post something in this thread and I or someone else will help get you running)
Check Settings > Storage and see if your new /sdcard partition (For me it was about 14GB) shows up as 'USB Storage' or 'SD Card' If it's USB storage, then your micro sd mounted to /sdcard successfully and you're done. You should be able to take a picture and have it save. If not...
Edit etc/vold.fstab with whatever you use personally (root explorer for me) and swap paths for /emmc and /sdcard (the part that starts with /devices/platform...). Someone more intelligent than me can probably make this a CWM zip. This step is telling ICS to swap your /sdcard (broken internal sdcard) and your /emmc (working external sdcard). It will probably look like this when you're done:
Code:
# internal sdcard that is no longer working
dev_mount emmc /mnt/emmc 1 /devices/platform/s3c-sdhci.0/mmc_host/mmc0
# external sdcard
dev_mount sdcard /mnt/sdcard auto /devices/platform/s3c-sdhci.2/mmc_host/mmc2
Reboot with your new vold.fstab and check your storage amount in ICS and test your camera (easy test to see if Android can write to the sdcard). Hopefully now this is working for you.
Let me know if you have any questions or (hopefully not) problems!
Notes for myself and devs:
ICS is a lot pickier about mounting filesystems, and if it can't mount /data correctly, it assumes it is encrypted. It really isn't, firing off https://source.android.com/tech/encryption/android_crypto_implementation.html an misleading encryption message.
In ICS and in CWM, when I look at /dev/block/platform/ I only see s3c-sdhci.2 and s5pc110-onenand. The s3c-sdhci.0 block is missing completely. I'm not sure how to even touch the /data or /sdcard filesystem at *ALL*
Oh well.

the camera does not work. The main memory is corrupt.
Using 8gb memory card. Do you have any suggestions for the camera?

edecan said:
the camera does not work. The main memory is corrupt.
Using 8gb memory card. Do you have any suggestions for the camera?
Click to expand...
Click to collapse
#1 dont quote a post that is un-related (especially huge 1st posts)
#2 dont ask unrelated questions in a thread
#3 dont ask questions PERIOD in development threads.

edecan said:
the camera does not work. The main memory is corrupt.
Using 8gb memory card. Do you have any suggestions for the camera?
Click to expand...
Click to collapse
This is happening because your phone is still trying to use your internal sdcard, but it isn't accessible. You will need to trick your phone to use the external sdcard as if it was the internal.
You will need ADB working and your phone in USB Debugging mode (Options>Development) for this part:
Code:
adb pull /system/etc/vold.fstab
This will put your vold.fstab file in the directory you have command prompt running. Open this file and swap the references of 'mmc2' with 'mmc0' and 's3c-sdhci.2' with 's3c-sdhci.0'. It should look something like the example in step 10 of post #1 when you're done. Save and close the file.
Now use these commands:
Code:
adb remount
adb push vold.fstab /system/etc/vold.fstab
if you get permission denied error when doing adb remount then try the following instead :
Code:
adb push vold.fstab /emmc/vold.fstab
adb shell
su
mount -o remount rw /system
cp /emmc/vold.fstab /system/etc/vold.fstab
chmod 644 /system/etc/vold.fstab
mount -o remount ro /system
exit
exit
adb reboot

TRusselo said:
#1 dont quote a post that is un-related (especially huge 1st posts)
#2 dont ask unrelated questions in a thread
#3 dont ask questions PERIOD in development threads.
Click to expand...
Click to collapse
Actually, the question he asked is extremely relevant to my post, specifically step 9. I agree with you #1, though.

cgugino said:
This is happening because your phone is still trying to use your internal sdcard, but it isn't accessible. You will need to trick your phone to use the external sdcard as if it was the internal.
You will need ADB working and your phone in USB Debugging mode (Options>Development) for this part:
Code:
adb pull /system/etc/vold.fstab
This will put your vold.fstab file in the directory you have command prompt running. Open this file and swap the references of 'mmc2' with 'mmc0' and 's3c-sdhci.2' with 's3c-sdhci.0'. It should look something like the example in step 10 of post #1 when you're done. Save and close the file.
Now use these commands:
Code:
adb remount
adb push vold.fstab /system/etc/vold.fstab
if you get permission denied error when doing adb remount then try the following instead :
Code:
adb push vold.fstab /emmc/vold.fstab
adb shell
su
mount -o remount rw /system
cp /emmc/vold.fstab /system/etc/vold.fstab
mount -o remount ro /system
exit
exit
adb reboot
Click to expand...
Click to collapse
Thank you! Everything is working now thank you.
ICS currently using 4.0.3 version of the Onecosmic's ROM version 2.1.
I want to use version 3.1 or CM9 KANG, this time when the boot screen remains. Have his solution

when i follow the steps to pull the file through adb, i get "remote object '/system/etc/void.fstab' does not exist"
phone boots, but when changing via root explorer, the files revert back when I reboot

kwhee07 said:
when i follow the steps to pull the file through adb, i get "remote object '/system/etc/void.fstab' does not exist"
phone boots, but when changing via root explorer, the files revert back when I reboot
Click to expand...
Click to collapse
Make sure you're using vold and not void, as in VOLume Daemon.
OR
Make sure you're remounting the file system with Root Explorer (press the button to change R/O to R/W)

roms kernel glitch does not work.
Boot screen does not turn on the device remains.

edecan said:
roms kernel glitch does not work.
Boot screen does not turn on the device remains.
Click to expand...
Click to collapse
What ROM are you on?
Did you flash a ROM update? If so, this overwrites the vold.fstab and you'll have to fix it. If you're on CM9, try reinstalling the latest update package, then perform steps 9 and on from the first post.

cgugino: i tried again via root explorer(both of the things I did wrong, you called out perfectly, thanks for keeping me in check!), but now the phone wont leave boot animation. I guess I'll flash again, and try to edit the document on my computer via adb

kwhee07 said:
cgugino: i tried again via root explorer(both of the things I did wrong, you called out perfectly, thanks for keeping me in check!), but now the phone wont leave boot animation. I guess I'll flash again, and try to edit the document on my computer via adb
Click to expand...
Click to collapse
Let me know if it doesn't work. Did you partition your external sd card?

no, have not understood me.
Just set up onescomics rom. Install another rom.

Thanx!! I was starting to think i was the only person in the world i have this issue.
In my case, I found several weeks ago my first "encrypted unsuccessful" screen and of course, I push de button. However, I didnt loose all the information in the internal sd card, only system one. I did all wipes and factory reset, but issue continued there. I fixed it connecting the phone to PC during boot.
Nowadays, the problem happens always the phone boots and conecting to the PC is enough to fix it and restart normally.
I understand your guide is in the case you have lost TOTALLY your access to internal Sd Card, isnt it?
However, this is not a permanent solution.

edecan said:
no, have not understood me.
Just set up onescomics rom. Install another rom.
Click to expand...
Click to collapse
The only way I know how to make this work is with the CM9 ROM -- I don't know what onescomics is and if you can't get your phone working, I would recommend staying on ICS.

iperezru said:
Thanx!! I was starting to think i was the only person in the world i have this issue.
In my case, I found several weeks ago my first "encrypted unsuccessful" screen and of course, I push de button. However, I didnt loose all the information in the internal sd card, only system one. I did all wipes and factory reset, but issue continued there. I fixed it connecting the phone to PC during boot.
Nowadays, the problem happens always the phone boots and conecting to the PC is enough to fix it and restart normally.
I understand your guide is in the case you have lost TOTALLY your access to internal Sd Card, isnt it?
However, this is not a permanent solution.
Click to expand...
Click to collapse
That is the case for me where the internal sdcard and data partition is totally lost.
I cannot say for sure how the guide would affect you if you followed it. If CWM thinks that your partitioned external sdcard has the /data partition on it (you could use the mount command and see), when you install ICS, it would install to your actual external sdcard. You may have to edit the vold.fstab in the installer zip file before you install, so that on the first boot, the phone won't try to boot to your internal partitions. Honestly, if you're still under warranty, I'd just flash to stock and try and exchange it.
I know that the 'Encryption unsuccessful' message is triggered because the phone has trouble mounting the /sdcard partition, and with ICS, it assumes that the partition is encrypted. It may be that your partition is taking too long to load, or that it is having issues reading. Either way, I'd make regular backups of *everything* onto your computer, in case one day the whole thing craps out.
As for me, even after I went back to stock Eclair, up to Froyo, and up to GB, I could never get the /sdcard or /data partitions to recognize.
See the section on 'Booting an encrypted system' here for more about how ICS detects 'encrypted' filesystems: https://source.android.com/tech/encryption/android_crypto_implementation.html

cgugino said:
I found a *workaround* to get my phone to at least work again. Note: You will need to perform steps 9 and on every time you flash a ROM or ROM update, because flashing overwrites the vold.fstab file.
Click to expand...
Click to collapse
Do you mean to say that the phone will thereon permanently have to use a microSD when updating ROMs?

raz123 said:
Do you mean to say that the phone will thereon permanently have to use a microSD when updating ROMs?
Click to expand...
Click to collapse
Sadly, yes. You will have to use a microSD card for *everything.* With my phone, I basically don't have an internal SDcard anymore. Completely inaccessible.
I keep a modified vold.fstab file in my /backup folder, and whenever I update CM9, I replace the one that is included and installed in the update with my modified one. This weekend, I might make a CWM-flashable zip file that does this as a side project.

cgugino said:
Sadly, yes. You will have to use a microSD card for *everything.* With my phone, I basically don't have an internal SDcard anymore. Completely inaccessible.
I keep a modified vold.fstab file in my /backup folder, and whenever I update CM9, I replace the one that is included and installed in the update with my modified one. This weekend, I might make a CWM-flashable zip file that does this as a side project.
Click to expand...
Click to collapse
Hmm.
How strange.. Just a few hours ago, this phone was rocking under ICS and the internal SDcard was great.
EDIT: Do you think using AdamOutler's (HW) unbricking method could help?
http://forum.xda-developers.com/showthread.php?t=1242466

raz123 said:
Hmm.
How strange.. Just a few hours ago, this phone was rocking under ICS and the internal SDcard was great.
EDIT: Do you think using AdamOutler's (HW) unbricking method could help?
http://forum.xda-developers.com/showthread.php?t=1242466
Click to expand...
Click to collapse
I agree with you on the strangeness! I wish I could offer a solution to get your internal sdcard files back, but there doesn't seem to be one at the moment. The other interesting thing is that the encryption guide for 3.0 says that encryption isn't even usable with the YAFFS file system, which I believe the Captivate uses.
If your phone is under warranty...there may be another option for you. I contacted about 3 other people that had threads related to this issue and everyone that responded said that Samsung replaced the motherboard.
What's your phone build? Mine is 1012 Rev 0.4
Edit: I haven't tried Adam's unbricking mod, and don't think I will. For me, the phone is now working perfectly and has full functionality, outside of the loss of the original /data and /sdcard partitions. I'm not going to crack it open and start soldering. However, if you do try his mod, please let us know the results!

Related

Hero's Kryptonite?

I tried to flash the Hero rom by partitioning my stock micro sd (the 1 that came with the phone)
...yeah i know it says not recommended but my 16gb card is being mailed and i couldnt wait.
anyway...now it will show the boot image and play the sound and then it will just be a black screen and wont go any further.
would i able to salvage this when my 16 gig card comes somehow?
could i flash back to an older rom? is the app_s folder in the ext partition going to interfere with that at all?
Please help!!!
Unbelievable
CC CEO said:
I tried to flash the Hero rom by partitioning my stock micro sd (the 1 that came with the phone)
...yeah i know it says not recommended but my 16gb card is being mailed and i couldnt wait.
anyway...now it will show the boot image and play the sound and then it will just be a black screen and wont go any further.
would i able to salvage this when my 16 gig card comes somehow?
could i flash back to an older rom? is the app_s folder in the ext partition going to interfere with that at all?
Please help!!!
Click to expand...
Click to collapse
i would recommend to go back to your backup (you did do a backup right?)
just flash the data, system, and boot .img files back
since you're doing Hero im guessing you have the newer SPL
you might run into a roadblock trying to fastboot so if you cant get the fastboot to work then boot into recovery mode and then go into a command prompt and run the following:
adb shell
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
Click to expand...
Click to collapse
this will let you access your memory card
get the HardSPL from here
copy it into your card as "update.zip"
now apply the update with ALT+S
after its done you can reboot back into the bootloader with ALT+X and typing
reboot bootloader
Click to expand...
Click to collapse
now you should be able to flash you backups like usual
nope didnt make a backup...i know..
but...
i was able to format my sdcard back to its original state and i flashed google ion back on the phone. question is are there any lingering affects to the phone itself? in setting up the ext2 or anything on the stock card might i have pushed or pulled something i shouldnt have from the internal storage if i didnt create a backup??
if so. how would i fix this?
if you Alt+W'd the phone there wont be any lingering effects,,,, its wiped and wont bother you no sunder!
I was having the same problem as you, as I too am only using the stock 1gb sdhc that came w/ the g1.
just did searching on here and I got it up n running.
I'm thinking maybe you did like me and pushed the /app_s/ folder while the SD was mounted to your pc, this is what I am guessing was my issue.
I've come to that conclusion since I've done the push w/o mounting the SD
Also I found that I had to be in the app_s folder on my computer to push it right, at first I was pushing it and it was going into /system/sd/app_s/app_s
Here's Haykuro's original instruction's
Installation:
1. Download http://www.droiddeveloper.com/hrbuilds/app_s.zip
2. extract "app_s" into your sdcard's ext2 partition.
3. Download http://www.droiddeveloper.com/hrbuilds/hero-signed.zip
4. Place on regular sd card.
5. Reboot into recovery, wipe and flash.
6. Enjoy.
--
for step 2... make sure you are in the actual app_s folder when you do the following command and make sure the sd card is NOT mounted.
adb push app_s /system/sd/app_s
--
follow the rest of the instruction's as stated and you should be fine.
now, to get it running smoother...
follow the tutorial here...
http://forum.xda-developers.com/showthread.php?t=521251
also within the thread there's tip's on moving the Rosie.apk along w/ widget's to internal memory, I just focused on the larger widget's, the largest being the weather one.
hope this help's.
just one noob tryna help another noob out ;-)
please help
When i am doing the update.. i am getting this error.. .
E: Can't chown/mod /system/xbin (not such file or dir)
E: Failure at line 12: set_perm_recursive 0 2000 0755 06755 SYSTEM:xbin
installation aborted."
please help!!

Partitioning microSD card

After setting up my wife's A7 and using it for three weeks, I have decided to open mine up. I waited because I wanted to see if CES had anything I wanted more. I decided they didn't.
So, I am starting from scratch again.
The main issue I've had with my wife's A7 has been the lack of storage space for apps, especially the big games.
Bazbob seems to have a solution by partioning the microSD card and using Apps2sd.
I took a new Class 10 16GB microSD card.
I downloaded and burned Ubuntu onto a CD from here: http://www.ubuntu.com/desktop/get-ubuntu/download
Put the card in my laptop, restarted it into Ubuntu.
Ran gparted.
Shrunk the Fat32 partition to just under 8GB and added another partion as ext2 primary.
When I restarted my laptop, my sd reader in the laptop doesn't work.
When I put it into the A7, it says the SD card has Total Space of 7.73GB.
At this point, I'm not sure what to do next.
Help is appreciated!
jazzbone said:
After setting up my wife's A7 and using it for three weeks, I have decided to open mine up. I waited because I wanted to see if CES had anything I wanted more. I decided they didn't.
So, I am starting from scratch again.
The main issue I've had with my wife's A7 has been the lack of storage space for apps, especially the big games.
Bazbob seems to have a solution by partioning the microSD card and using Apps2sd.
I took a new Class 10 16GB microSD card.
I downloaded and burned Ubuntu onto a CD from here: http://www.ubuntu.com/desktop/get-ubuntu/download
Put the card in my laptop, restarted it into Ubuntu.
Ran gparted.
Shrunk the Fat32 partition to just under 8GB and added another partion as ext2 primary.
When I restarted my laptop, my sd reader in the laptop doesn't work.
When I put it into the A7, it says the SD card has Total Space of 7.73GB.
At this point, I'm not sure what to do next.
Help is appreciated!
Click to expand...
Click to collapse
You needed to make a second partition EXT2 and format it. You then need to mount the partition. I did this by using the install-recovery.sh that it located in /system/etc. I used the following tutorial and it worked. I got over 12gb of space to install apps.
http://forum.xda-developers.com/showthread.php?t=832799
I did try to mount the new partition to /storage which is also /sdcard and i was still not able to use titanium backup to move apps. The only way i have alot of space is use this method.
I'm also mounting the fat32 partition to location /storage so that when i download apps thats where they are stored until you install them. Also Titanium backup dumps the backups here. This is done with a custom mod of Dexters 1.0c mod.
I did not use adb, i used a app called quicksshd which allows you secure ftp into the tablet and make changes. I suggest using a windows programs called winscp and putty.
Thanks for replying rfisher.
Turns out that my laptop lost the drive letter for the sd card. That's fixed now. When I insert the card into my laptop, it says that you need to format the card in the drive to use it. Any idea why?
I am confused by your instructions.
You said
You needed to make a second partition EXT2 and format it.
Click to expand...
Click to collapse
I did that. First partition is FAT 32, and second partition is EXT2, primary.
Maybe I didn't format the partition? I just created it.
I'll install busybox and see how far I can get with it.
With the other A7, I was never able to work with ADB.
This device really makes me feel like an idiot.
Still can't believe I was the first to get Google Apps working on my wife's tablet!
no adb
Well, the hours of frustration have returned...
I can't get adb running on my laptop.
I installed Android SDK.
When I type adb in the cmd window on my laptop, I get
"adb" is not recognized as an internal or external command, operable program or batch file"
I have tried moving the ADK folder to c:\
and
to:
C:\Users\Bucks HP
No luck.
I added the path c:\android-sdk-windows\platform-tools
to the environment variables in my system properties.
My head is going to explode!
Well, I got adb working, I think...
Problem was in the cmd window. I had to change the path.
Now, I can't install busybox. I followed the instructions from the wiki.
When I type "adb push busybox /data/local"
it returns: cannot stat 'busybox' : no such file or directory.
I pasted the busybox file in the
C:\android-sdk-windows\platform-tools
folder.
Was that the right place for it?
Is the busybox file just a text file?
Also, mine is named busybox-armv6l
Should it be renamed? I tried "adb push busybox-armv6l /data/local"
and got the same result...
I gave up on installing busybox via the wiki instructions.
I installed Titanium Backup and installed busybox through it.
Now, when I type: cd /system
mkdir sd
I get :
mkdir failed for sd, read-only file system
What does that mean and how do I fix it?
Thanks
The saga continues...
With the busybox from Titanium Backup installed,
I needed to type:
adb shell
su
mount -o remount,rw /dev/block/mmcblk3p1 /system
exit
exit
Then, following the tutorial, I am up to step 12:
12) Now comes the tricky part: making Android mount your new partition at boot time. All the hard work would be useless if Android discarded the mount points every time we restarted our phones. To do this we’ll need to create 2 scripts and store then into /system/etc. Obviously the scripts should be started by init.rc and need to run as root. Fortunately Android’s init.rc have a gap that makes this possible. The scripts are named install-recovery.sh and init-sd2.sh.
My question is: How do you create scripts?
You would create them with notepad++ which is a windows program. Then using adb push them to the /system/etc directory.
I used a app called quicksshd and a windows program called winscp to copy the files to the directory. If you used my method you first need to make the /system directory rw before it will let you copy the files. It worked for me, the only thing i did differently is edit init.rc to mount the first partition of the sd card to /storage, but this was creating a modded 1.0c rom. So the result is about 4gb for my sd memory and 12gb for installing apps.
jazzbone said:
The saga continues...
With the busybox from Titanium Backup installed,
I needed to type:
adb shell
su
mount -o remount,rw /dev/block/mmcblk3p1 /system
exit
exit
Then, following the tutorial, I am up to step 12:
12) Now comes the tricky part: making Android mount your new partition at boot time. All the hard work would be useless if Android discarded the mount points every time we restarted our phones. To do this we’ll need to create 2 scripts and store then into /system/etc. Obviously the scripts should be started by init.rc and need to run as root. Fortunately Android’s init.rc have a gap that makes this possible. The scripts are named install-recovery.sh and init-sd2.sh.
My question is: How do you create scripts?
Click to expand...
Click to collapse
Hi rfisher
Thanks for replying!
While waiting, I opened Notepad++, copied the text in the tutorial window into it and saved the file as Unix.
Then, I copied it to a USB drive, put it in the A7, and copied to the system/etc folder.
Is that acceptable?
Then, I followed steps 13-15.
I think I did something wrong. I am not seeing it in Root Explorer. What should I be looking for?
Was I supposed to install Apps2SD already?
I got winscp and quicksshd working. YEAH!
Used them to copy the files as you did.
Restarted A7.
Still don't see the other partition.
PS. I was just rereading your earlier post and you mentioned:
I did try to mount the new partition to /storage which is also /sdcard and i was still not able to use titanium backup to move apps. The only way i have alot of space is use this method.
I'm also mounting the fat32 partition to location /storage so that when i download apps thats where they are stored until you install them. Also Titanium backup dumps the backups here. This is done with a custom mod of Dexters 1.0c mod.
Looking on my A7, I don't see a location that is /storage
My tablet is fresh out of the box, without any firmware updates yet.

[Q] Can I have partitions that can be accessed from both NC Stock and CM7 on SD card?

Hi everyone!
I just got CM7 (latest stable release) installed on on external sdhc card. I have wifi issues with CM7 (and looking around the forums tells me that CM7 can be finicky with certain routers) so I would love to be able to use Nook's stock ROM (4.1.4) when I am having issues.
But, when I am on NC ROM, I don't see anything except the small boot partition on the SD and when I am on CM7, I don't get access to this boot partition. I am wondering if there is a way to either create another partition or make the currently existing partitions accessible on both ROMS so that I can share data between them.
I am a n00b without any Android experience so thanks in advance for your patient responses.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
andrandom said:
Hi everyone!
I just got CM7 (latest stable release) installed on on external sdhc card. I have wifi issues with CM7 (and looking around the forums tells me that CM7 can be finicky with certain routers) so I would love to be able to use Nook's stock ROM (4.1.4) when I am having issues.
But, when I am on NC ROM, I don't see anything except the small boot partition on the SD and when I am on CM7, I don't get access to this boot partition. I am wondering if there is a way to either create another partition or make the currently existing partitions accessible on both ROMS so that I can share data between them.
I am a n00b without any Android experience so thanks in advance for your patient responses.
Click to expand...
Click to collapse
Look in my signature for a link to my tips thread. I explain there how to make the SD media partition available to both ROMs (item B3).
leapinlar said:
Look in my signature for a link to my tips thread. I explain there how to make the SD media partition available to both ROMs (item B3).
Click to expand...
Click to collapse
*That's* the one I wanted to point them to.
leapinlar said:
Look in my signature for a link to my tips thread. I explain there how to make the SD media partition available to both ROMs (item B3).
Click to expand...
Click to collapse
Thanks.
Do you mean step #3 in Section B? I could edit it without running your script too, can't I?
andrandom said:
Thanks.
Do you mean step #3 in Section B? I could edit it without running your script too, can't I?
Click to expand...
Click to collapse
If whatever you have on emmc is rooted, you can manually edit it. If you have unrooted stock, then you need to flash the zip since without root you cannot edit those files manually. And I did mean item B3. Each item is a different topic, they are not steps. One topic does not depend on another. Just do B3 and no others if you want.
Yes, item B3. My mistake...
I should be able to do flash the zip from my current CM7 SD card's boot partition, shouldn't I?
So I put the update-stockemmc-vold-fstab-modified-for-partition4.zip file in the boot partition of the SD card, rebooted to Recovery mode and then booted to NC's stock ROM. NC is still using the tiny boot partition on the SD card as my external storage instead of the much larger CM7 partition. This was the same partition that was under 'My Files / Memory card' before I flashed so nothing has changed. I did this twice to double-check.
Am I doing this wrong?
andrandom said:
Yes, item B3. My mistake...
I should be able to do flash the zip from my current CM7 SD card's boot partition, shouldn't I?
So I put the update-stockemmc-vold-fstab-modified-for-partition4.zip file in the boot partition of the SD card, rebooted to Recovery mode and then booted to NC's stock ROM. NC is still using the tiny boot partition on the SD card as my external storage instead of the much larger CM7 partition. This was the same partition that was under 'My Files / Memory card' before I flashed so nothing has changed. I did this twice to double-check.
Am I doing this wrong?
Click to expand...
Click to collapse
Yes you are doing it wrong. You need to flash that file with a CWM card, not put in the boot partition of your SD. And since you did that, you need to re-flash your latest ROM on SD to correct your mistake. (I will edit my instructions to make it a little clearer that you use CWM to flash that file.)
I got NC stock ROM to see my SD card partition by following item A10. That is most excellent and thanks again!
Unfortunately, I no longer see the boot partition when I attach NC to my computer whether NC is running off stock ROM or CM7. My guess is that this is due to my failed attempt to flash from my CM7 SD card yesterday. Am I right?
I thought I could reverse that by copying the update-stockemmc-vold-fstab-return-to-stock.zip file to CM7's boot (and then booting to the recovery mode) but that seemed to have nothing.
If I understand your previous message correctly, I should re-do my entire SD card but... I have already spent a few hours downloading and customizing the Android apps. Is there a way to preserve all that before Win32diskimager destroys the contents of the SD card?
Is there a way to manually mount the /etc folder from a unix prompt and alter the file?
Does it even matter if I don't see boot while I attach NC to a computer? Are there any caveats to 'let it be'?
Questions, questions and more questions...
That leads me to the obvious question, is there a book that explains Android to someone who is not interested in programming it but wants to understand the architecture and design of the OS (and custom ROMs)?
Thanks for being patient with all these n00b questions.
andrandom said:
I got NC stock ROM to see my SD card partition by following item A10. That is most excellent and thanks again!
Unfortunately, I no longer see the boot partition when I attach NC to my computer whether NC is running off stock ROM or CM7. My guess is that this is due to my failed attempt to flash from my CM7 SD card yesterday. Am I right?
I thought I could reverse that by copying the update-stockemmc-vold-fstab-return-to-stock.zip file to CM7's boot (and then booting to the recovery mode) but that seemed to have nothing.
If I understand your previous message correctly, I should re-do my entire SD card but... I have already spent a few hours downloading and customizing the Android apps. Is there a way to preserve all that before Win32diskimager destroys the contents of the SD card?
Is there a way to manually mount the /etc folder from a unix prompt and alter the file?
Does it even matter if I don't see boot while I attach NC to a computer? Are there any caveats to 'let it be'?
Questions, questions and more questions...
That leads me to the obvious question, is there a book that explains Android to someone who is not interested in programming it but wants to understand the architecture and design of the OS (and custom ROMs)?
Thanks for being patient with all these n00b questions.
Click to expand...
Click to collapse
You do not need or want to re-set up the whole SD installation. Just put the same CM7 zip file back in the boot partition and boot to SD recovery. It will put the correct vold.fstab back on the SD. You will not lose any settings or apps you have already set up. (And putting the return to stock zip there was also the wrong thing to do. The vold.fstab for stock and CM7 are different. But don't worry, it will fix that too.)
You are not supposed to see the boot partition on the PC when you plug the nook in with the cable. You are only supposed to see 'emmc' and 'sdcard'. Under the original setup, your stock system thought the boot partition was 'sdcard' and that was why you saw it on your PC. Since you modified stock to see partition 4 as 'sdcard', partition 4 is what the PC sees, not the boot partition.
Most people have to physically take the card out of the nook and put it in the PC to see the boot partition on the PC. If you don't want to do that, use my script in item B4. But since you are on CM7, you will not be adding many things to the boot partition to install with SD recovery in the future. So it is probably best to leave things be.
And I don't know of any books to help you.
Sent from my Nook Color running ICS and Tapatalk
That is excellent news!
A bit of playing around with Astro tells me that I was wrong about seeing the 'CM7 SDCARD' partition when I was on CM7 ROM. I am only seeing the boot. Anyway, I am going to flash the CM7 ROM again and I am hoping it would fix everything.
Also, yes, I can see the boot partition when I put the SD card directly on my computer but I was also able to see it when I hooked up the NC to my computer via USB before I did my unintended tweaks but... I'll survive.
I'll be back after I flash. (Famous last words??)
Mission accomplished!
Thanks again for all your help.
For future reference after you alter stock's fstab... all you have to do is:
mkdir /sdcard/boot (only have to do this one time)
mount /dev/block/mmcblk1p1 /sdcard/boot (do this every time you want to put something on the boot partition)
put anything you want on boot partition in /sdcard/boot
DizzyDen said:
For future reference after you alter stock's fstab... all you have to do is:
mkdir /sdcard/boot (only have to do this one time)
mount /dev/block/mmcblk1p1 /sdcard/boot (do this every time you want to put something on the boot partition)
put anything you want on boot partition in /sdcard/boot
Click to expand...
Click to collapse
Yes, there is one big advantage to using that method. I think it allows the boot partition to be seen not only on the nook, but also on the PC when you plug in the usb.
leapinlar said:
Yes, there is one big advantage to using that method. I think it allows the boot partition to be seen not only on the nook, but also on the PC when you plug in the usb.
Click to expand...
Click to collapse
We could probably come up with a symlink to /dev/block/mmcblk1p1 to /sdcard/boot and avoid having to mount it everytime as well.
DizzyDen said:
We could probably come up with a symlink to /dev/block/mmcblk1p1 to /sdcard/boot and avoid having to mount it everytime as well.
Click to expand...
Click to collapse
Thank you Dizz, your suggestion got me to thinking and I was able to come up with an init.d bash script that does the trick. I just temporarily mounted sdcard and created the sdcard/boot directory and the mounted the boot partition to it, then unmounted sdcard so it could be mounted again by the system later in the boot sequence.
The only problem is now sdcard will not mount on the PC using UMS mass storage. Must be because of having a second mount within the mount. But it does mount with MTP. But that may be acceptable. I will test some more, including using Goo Manager tomorrow.
EDIT (6-21): Goo Manager works. But I think I have figured out why sdcard is not mounting in UMS. Once it is mounted in my script and the boot partition mounted under it, it cannot be unmounted. And since it cannot be unmounted, it cannot be mounted later by the system as vold. If it cannot be mounted as vold, it does not show in UMS. For now I think I will leave it as I have it in Rev 2 of my script (symlinking to the root directory with full r/w permissions). If people want to see the boot partition on the PC, just use my modified for CM9 NookColorUMS available in my tips thread.
Sent from my Nook Color running ICS and Tapatalk
Help!
When CM7 is running, my computer is no longer mounting any of the partitions when I connect NC to my computer via the USB cable.
If the NC stock ROM is running, my computer mounts all three partitions (MyNook..., boot and CM7SDcard) but calibre is not recognizing the external partitions for transfers.
Further, when I boot to my NC stock ROM, I am no longer seeing my SD card's contents in the NC's library.
This may have something to do with the fact that NC stock ROM seemed to have updated itself to 4.1.3.
Should I re-run the scripts again or am I missing something else?
When it was updated to 1.4.3, you lost the emmc mods. Just re-flash my zip with the CWM SD. You may have lost CWM on emmc too.
On CM7, you have to select the turn on storage button after you plug it in. It is not automatic like stock. Pull up the notification area and touch the turn on button.
Darn, I forgot about that 'USB' option under notifications. Enabling it allows me to find the partitions. I will run your scripts again when I find a spare mUSB card.
Thanks again for your help!

[GUIDE] External2Internal Ultimate

I thought about this idea more than a month ago when i came to know that the partitions could freely be altered, but i could not put into practice until i got my 32 gb card yesterday.
so basically, after following my guide you will have:
* supersized data partition (12 gigs): no more move to sd needed unless for huge games (i'm thinking fifa12 and asphalt7) and then again the stock move to sd feature will work as expected (it will move data to the actual external sd card)
* external sd card mounted as internal sd card: nothing to say here, just does what is expected
* real internal sd (ums partition) shrinked to minimum (half gig) because it needs to stay present: used to mount a swap file (optional)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What you will need:
* g.lewarne hydracore 4.3b kernel: you don't need it for anything special, but it's the most amazing kernel, and gavin is the most devoted developer ive seen on the n7000. cheers gavin and keep up the good work :good:
* swapper2: if you want to use the swap file (see at the end)
so be warned, i'm no real specialist here, so i'm not aware of the no dos, i just got my guide to work through trial and error and getting information from other threads.
so if you follow my guide you're almost good, if not you may cause an atomic bomb to fall over your city, not my problem :silly:
enough chit chat for now let's head directly for the guide:
1. reboot to recovery, and connect your phone to your pc
2. run a command prompt and type the following (wait a little bit until the adb server starts on the phone, you can verify it by typing "adb devices" if you get a serie of digits then you're good to go.
Code:
adb shell
parted /dev/block/mmcblock0
you'll get into the parted interactive shell, this is where serious work done
Code:
did i remind you to backup your system,
this is your last stop before the no back point
so you just might wanna "move" all your internal sd stuff to the external sd,
and backup your system to the external sd also
(you just need to restore the data partition afterwards the rest of the system is safe but who knows :p)
ps: you can do your backup on cwm without leaving adb shell on the pc just like you will do the format later thanks to cwm
remove the partitions
Code:
rm 10
rm 11
make the new changed size partitions
Code:
unit b
mkpart primary 1174405120 14680064511
mkpart primary 14680064512 15216934911
name 10 DATAFS
name 11 UMS
now in cwm go to mounts and storage and select "format /emmc" and "format /data"
in parted type "print" and you should see this output
Code:
Number Start End Size File system Name Flags
1 4194304B 25165823B 20971520B ext4 EFS
2 25165824B 26476543B 1310720B SBL1
3 27262976B 28573695B 1310720B SBL2
4 29360128B 37748735B 8388608B PARAM
5 37748736B 46137343B 8388608B KERNEL
6 46137344B 54525951B 8388608B RECOVERY
7 54525952B 264241151B 209715200B ext4 CACHE
8 264241152B 281018367B 16777216B MODEM
9 281018368B 1174405119B 893386752B ext4 FACTORYFS
10 1174405120B 14680064511B 13505659392B ext4 DATAFS
11 14680064512B 15216934911B 536870400B fat32 UMS
12 15216934912B 15753805823B 536870912B ext4 HIDDEN
now the hardest part is over, restore your data partition and you will be able to boot you system normally. and you go to your storage information you will find that your app storage is now 13gigs and the usb storage is just 500 megs yay
to switch the sd with the internal you will have to modify vold.fstab file(thanks to ciphray for his guide on how to do so)
you can use the modified file from ciphray thread here which i didn't beacuse his file was smaller
so i just pulled the file to my pc
Code:
adb pull /etc/vold.fstab vold.fstab
modified it with notepad++ or any dev text editor (don't use windows notepad it will mess the file)
Code:
# internal sdcard
{
storage_struct = cover, "/mnt/sdcard/external_sd","/mnt/sdcard/usbStorage"
ums_sys_path = /sys/class/android_usb/f_mass_storage/lun0/file
discard = enable
}
dev_mount sdcard /mnt/sdcard auto /devices/platform/s3c-sdhci.2/mmc_host/mmc1
# external sdcard
{
ums_sys_path = /sys/class/android_usb/f_mass_storage/lun1/file
android_secure_containers = enable
}
dev_mount sdcard1 /mnt/sdcard/external_sd 11 /devices/platform/dw_mmc/mmc_host/mmc0/mmc0 encryptable_nonremovable
and push it back to phone + change permissions
Code:
adb push vold.fstab /etc/vold.fstab
chmod 644 /etc/vold.fstab
restart your phone and voila
as a final step you can use the now pretty useless internal space (500megs remember) as a swap sapce
download swapper2 from the play store here https://play.google.com/store/apps/details?id=lv.n3o.swapper2
run it and go to settings
set swap place as /sdcard/external_sd/swapfile.swp
set swap size to the max
set the swappiness to 20 ( you can rise the value a little but don't put a high value or the system will do much swapping all the time -value of 100 means any memory not used actively will be swapped- )
wait until the process finishes then reboot your phone
you can verify that swap is working by typing "free" in the shell if the line beginning with swap is not all zeros then you're swap is working.
hope my guide will be usefull, and don't hesitate to ask me any question
Awesome, thanks! Will try it out when I get some time
If you want more app space you can erase the hidden partition and get more space.
Sent from my GT-N7000 using Tapatalk 2
Okay, I've performed the whole thing, and just a few remarks on my experience
If you want to modify the vold.fstab straight from recovery without having to reboot first, you can simply mount the system partition, and retrieve the file from /system/etc/vold.fstab instead of /etc/fstab
More importantly, following your instructions, I ended up in a situation where my apps previously moved to the sd card weren't recognized. I've solved this by modifying my vold.fstab as follows:
Code:
# internal sdcard
{
storage_struct = cover, "/mnt/sdcard/external_sd","/mnt/sdcard/usbStorage"
ums_sys_path = /sys/class/android_usb/f_mass_storage/lun1/file
android_secure_containers = enable
}
dev_mount sdcard /mnt/sdcard auto /devices/platform/s3c-sdhci.2/mmc_host/mmc1
# external sdcard
{
ums_sys_path = /sys/class/android_usb/f_mass_storage/lun0/file
discard = enable
}
dev_mount sdcard1 /mnt/sdcard/external_sd 11 /devices/platform/dw_mmc/mmc_host/mmc0/mmc0 encryptable_nonremovable
That way, all my apps were properly recognized without issues. I'll probably be moving them back to phone now though.
Will be trying this setup over the next few days and see how it performs, but one caveat I missed is that you may not be able to install the whole of some apps on the data partition, as some the data will always be stored in the sdcard/Android folder, which would make the 12GB on /data less useful than I initially thought, unless I'm missing something of course
Hi
Could you post a screenshot of the Storage page (under Settings)?
I'm interested to see what these look like after this mod.
Internal
USB Storage
SD Storage
Thanks!
zongamin said:
Hi
Could you post a screenshot of the Storage page (under Settings)?
I'm interested to see what these look like after this mod.
Internal
USB Storage
SD Storage
Thanks!
Click to expand...
Click to collapse
here you are, look at the OP
i didn't realize the screenshot like was corrupt
if you read the op i mentioned the resulting sizes after the mod
sd storage will be mentioned as 500 megs (actually taken from the internal emmc) that i use for swap space
Why isn't it possible to use the rest of the space for apps and reroute the ums to the ext sdcard so it reads it as the internal?
Sent from my GT-N7000 using Tapatalk 2
As far as I know, the HydraCore kernel doesn't allow swap, so it's unuseful to setup a swap file with swapper. Also, presently no Note kernel has swap enabled.
Carefully crafted on my Galaxy Note, for your eyes only
Hydracore 4.1 since has swap enabled in its kernel.
Sent from my GT-N7000 using Tapatalk 2
I'm sorry, I didn't know Gavin had listened to what I had asked oh so many times
Carefully crafted on my Galaxy Note, for your eyes only
travis82 said:
Why isn't it possible to use the rest of the space for apps and reroute the ums to the ext sdcard so it reads it as the internal?
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
i was fearing that the phone won't boot if the partition isn't available after a clean setup.
so i decided to leave the small size partition and make it useful for swap instead.
btw does anyone know how to use a bigger swap file with swapper2?
I guess, this method is only working for a "healthy" note, which never got a mmc cap bricks, right ?
And if a note got brick before, and recovered by hg42 pit revival method, I think the repartition command for the start-end of the DATA and UMS will be different.
Hmmpppfff... Do you have a way on how to read the partition setting of the note ? :fingers-crossed:
Send from the corner of this rounded earth
antique_sonic said:
I guess, this method is only working for a "healthy" note, which never got a mmc cap bricks, right ?
And if a note got brick before, and recovered by hg42 pit revival method, I think the repartition command for the start-end of the DATA and UMS will be different.
Hmmpppfff... Do you have a way on how to read the partition setting of the note ? :fingers-crossed:
Send from the corner of this rounded earth
Click to expand...
Click to collapse
just type print on the parted shell
and then you can recalculate new sizes for the data partitions, it should work like a charm
So... Im a USER, and there are part I am a bit confused about... BUT ill ask anyway!
It seems that if I wanted to resetup the partitions, I wouldnt need to mess with the pit files correct?
OR, because I want to totally KILL USB Storage, dedicate the entire internal memory to /data, and make /sdcard TRULY my sdcard, would I truly need to mess with the pit file?
Has anyone tried with killing off /ums completely?
Any help is appreciated. Also, I am using the i717 (AT&T GNote version), but my desire is the same so I figured Id post here...
EDIT: im not too worried about rom flashing, I normally slim down ROM's before I flash them, so Im not afraid of changes that have to be made (in txt files) in order to have them work properly on a UMS'less modded device. However, I do need to find out how to properly backup the pit file before I even THINK Of messing with it.
do i have to redo the whole procedure if i flashing nightly every time?
Anyone tried this on JB roms?
Hello?
Sent from my GT-N7000 using Tapatalk 2
jaguaralani said:
Anyone tried this on JB roms?
Click to expand...
Click to collapse
+1
I get 64 gb sandisk microsd card. I want to use this mod on jb stock LSC rom.
Can we use on jb roms?
GT-N7000 cihazımdan Tapatalk 2 ile gönderildi
Helpppppp
Envoyé depuis mon GT-N7000 avec Tapatalk
JB ready
I've tried it worked fine on Ultimate and Alliance ROM. Just edit vold.fstab in /etc after install new ROM. Replace 11 to auto and { } to { }. Now I need help if anyone have the original partition info, incase I wanted to restore.

Restore Rom Install Failed (Simple Touch) Tried Everything - no Dice. Please Help :)

The Issue
Hi, I have a Nook Simple Touch that gets stuck trying to boot. First I see the Barnes and Noble Screen, Next for a brief moment it tries to load a Rom and shows a small nook icon with a loading bar. Next it says "Install Failed". I am unable to do anything other than a factory reset, which doesn't help.
Background
I should add that the device previously was working fine, then one day it froze as I was highlighting some text. When I tried to boot it, it was stuck in the scenario described above. I believe it was already updated to 1.2.2 with seemingly no issues.
What I've tried:
I have tried restoring it back with noogie and a backup, and I have also tried the Nook Manager- Rescue from .zip and Rescue from backup to no avail. Still get that same blasted "Rom Restore Image" Screen followed by "Install Failed".
I have an update from Barnes and Noble called "nook_1_2_update.zip" which I tried to copy over to the nook but the file is too large.
Any ideas? I love this thing and don't want to let it go!:crying::good:
I guess You can insert an SD card with NookManager back and boot properly?
If so lets connect to Your nook via ADB, mount /boot partition and prepare copy of its files.
Code:
mount -o rw,remount rootfs /
mkdir boot
mount -t vfat /dev/block/mmcblk0p1 /boot
[B]...
copy files inside boot partition from
...[/B]
mount -o ro,remount rootfs /
umount /boot
Then put this exact copy onto new (vfat formatted) SD card, and try to boot from new card.
Let us know whats happen.
Is this booting from new SD, showing same fail screens?
Thanks so much for the assistance! I will give it a try and report back.
Also , to note, I do have an old glowlight here that has a cracked screen. Wonder if I could get a copy of it's IMG and use that too?
Trigrammaton said:
... I do have an old glowlight here that has a cracked screen. Wonder if I could get a copy of it's IMG and use that too?
Click to expand...
Click to collapse
Im not quite sure. Another version, etc...
You can use NST boot partition image from this post
For preparing another booting SD card too...
Trigrammaton said:
Thanks so much for the assistance! I will give it a try and report back.
Also , to note, I do have an old glowlight here that has a cracked screen. Wonder if I could get a copy of it's IMG and use that too?
Click to expand...
Click to collapse
If you restore the image from a different device the serial number, MAC address, etc. will be messed up. You will never be able to register the device. This may not be an issue, but just so you are aware.
nmyshkin said:
If you restore the image from a different device the serial number, MAC address, etc. will be messed up.
Click to expand...
Click to collapse
The serial number is written inside the little door for the SD card (if you haven't worn it off).
The serial number and the MAC are also on a sticker in the inside.
ucy74 said:
I guess You can insert an SD card with NookManager back and boot properly?
If so lets connect to Your nook via ADB, mount /boot partition and prepare copy of its files.
Code:
mount -o rw,remount rootfs /
mkdir boot
mount -t vfat /dev/block/mmcblk0p1 /boot
[B]...
copy files inside boot partition from
...[/B]
mount -o ro,remount rootfs /
umount /boot
Then put this exact copy onto new (vfat formatted) SD card, and try to boot from new card.
Let us know whats happen.
Is this booting from new SD, showing same fail screens?
Click to expand...
Click to collapse
Ucy - It boots from nook manager and I am able to use that utility just fine without the failed rom screen. What do you mean by "new" sd? If i put a blank sd into the slot and boot?
When you talk about ADB above and using that - I just download the sdk then use the code you pasted above to copy over the boot partition you linked to my nook (not sd) and try booting like that, correct?
Thanks! I can figure things out with a little guidance, I'm just not really well versed on some of this. Appreciate your help very much!
Trigrammaton said:
Ucy - It boots from nook manager and I am able to use that utility just fine without the failed rom screen.
Click to expand...
Click to collapse
Super, it means so You can connect to Your Nook and dump boot partition files to PC using ADB.
What do you mean by "new" sd? If i put a blank sd into the slot and boot?
Click to expand...
Click to collapse
You can copy files dumped above onto vfat formated SD card. Then try to boot from this "new" - freshly prepared card. Check whats happen.
When you talk about ADB above and using that - I just download the sdk then use the code you pasted above to copy over the boot partition you linked to my nook (not sd) and try booting like that, correct?
Click to expand...
Click to collapse
NOT SO FAST!!! Do not put linked partinion into nook! There are different cases and commands to do that. If You are new to ADB lets try to dump boot partition first, as mentioned before. Maybe there will be not necessary to replace whole partition rather than single file.
Thanks! I can figure things out with a little guidance, I'm just not really well versed on some of this. Appreciate your help very much!
Click to expand...
Click to collapse
Prepare this dumped SD first. We try to heal it to make bootable...
Thanks! I will give it a whirl this weekend and report back. Really appreciate you taking time to respond - Very kind of you!

Categories

Resources