Related
*ALL THE USUAL DISCLAIMERS AND WARNINGS*
*THIS IS FOR VERSION 1.1 ONLY, DON’T TRY ON 1.0.0 OR 1.0.1*
Credit goes to: GabrialDestruir for the original auto-nooter, GLa’DOS for the boot animation, pokey9000 for nooter, Mistar Muffin for Market and GTalk Fix, clockworx for the “non-ugly” patch that is used to get androidID, mastapsi for testing and coding of the original auto-nooter, lewellyn for coding, [mbm] for ABI Fix, Hotaru for the Gingerbread keyboard, rpollard00 for DroidX keyboard with bigger font, bpk for Soft Keys, Ben74 for NookColor Tools which enables Non Market Installs and re-enable of ADB , Freenode's #nookcolor chat for code checking. A special thanks to all developers out there, without all of you this community would not be as great as it is.
Please Note: If you are the developer of an app that is included in this work, and would like me to remove it, feel free to contact me.
*I am copying the following step from the original auto-nooter, because they are tried and true, and people are already familiar with seeing them*
What it does:
Installs su and Superuser.apk
Installs Busybox with whoami
Installs Softkeys 3.0.6
Installs NookColor Tools (To Enable Non-Market Installs, and re-enable ADB)
Installs Calendar and Calculator.
Installs Android Market, Gmail, Youtube
Installs Gingerbread Keyboard
Enable ADB
Enable Multi-touch for Android Apps
Enables Live Wallpapers
Enables Android Market and Gmail.
App Auto Install (Open up NooterFiles from sdcard drop in /data/app)
Known Problems:
With the version 1.1 update, ADB will not stay active after a reboot or unplug of the cable. To enable each time you want to use it, you will have to go into NookColor Tools /All Settings/Development/USB debugging, you will have to uncheck the box and then recheck it.
How to Use:
Before you begin:
* To update to 1.1 you must do a complete wipe.
* You must update to 1.1 to use Auto-Nooter 3.0.0 Instructions HERE.
1 You must already have a registered NOOKcolor
2 You must have a Gmail/Youtube linked Account. IF you used a Gmail account for B&N Registration you should use that one for this process.
3 You must either have dd (Linux) or WinImage (Windows) software.
4 You must have an external microSDCard reader or this will not work. Do NOT use the NC.
5 You must have enough intelligence to follow instructions.
Let's get started:
1 Download Auto-Nooter from here: MultiUpload or MediaFire
*MD5 FB74865663B8D797A486A85022FAD9B2*
2 Linux: Unzip and use dd if=auto-nooter-3.0.0.img of=/dev/sdcard
2 Windows: Unzip and use WinImage to "Restore Virtual Hard Disk Image" to your SDcard.
2 Windows Alternative: https://launchpad.net/win32-image-writer/+download
3 Unplug your NOOKcolor from computer. (If Plugged in.)
4 Insert AutoNooter SDcard into your NOOKcolor.
5 Plug the USB cable into your computer and your NOOKcolor. (This will boot up the NOOKcolor.)
6 Your NookColor will reboot when it's done.
That was the hard part, now to the simple stuff.
7 Upon boot unlock your screen.
8 At the Android Welcome Screen skip Sign In.
9 Enable Location Services when given the option.
10 Connect to Wifi and launch Youtube from "Extras".
11 Click the Menu button (The one RIGHT of the Up Arrow).
12 Select "My Channel" and Login using your Gmail Account.
13 Exit Youtube and Launch Gmail from "Extras".
14 Sync your Gmail Account and Exit. (If it fails to sync that is fine.)
15 Open up Market and Accept Terms and Service.
If you made it this far your nook should be successfully Rooted. Go Download an App to make sure.
16 Enable Non-Market Installs by running the NookColor Tools App.
17 If your Youtube fails to launch, download the attached EVO HQ, and follow this code in adb
Code:
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
adb uninstall com.google.android.youtube
adb push YouTube.apk /system/app
adb reboot
18 Go to Settings > Device Info > SdCard > UnMount > Format
Complete Wipe:
1 8 Failed Boots > Wipes /system
2 Factory ResetFactory Reset > Wipes /data
*You must do both of these to completely wipe clean your NOOKcolor.*
*Before anyone starts to say that I took this project away from GabrialDestruir, I posted this file in the original post, and sent the OP a PM asking to update the current project. I have yet to hear back, and the post was not updated. My post can be found HERE, dated February 2, 2011. I felt that this would be of a benefit to the community, so I am posting it now. If I am asked at some point to take it down I will do so at that time.*
Forgive my ignorance here, but I thought you were never supposed to use the NC to format your SD card? (last step)
I thought I read somewhere that it messes up something in the emmc?
Hopefully I'm wrong and just paranoid
danbutter said:
Forgive my ignorance here, but I thought you were never supposed to use the NC to format your SD card? (last step)
I thought I read somewhere that it messes up something in the emmc?
Hopefully I'm wrong and just paranoid
Click to expand...
Click to collapse
I have never really seen an explanation as to why you don't format on the NC. I have formated via the NC and the card works fine both in the NC and my PC. When I want to burn an image, I have been able too. Been able to flash other images on it too.
Excellent!
Can you please add an MD5 to the first post?
Homer
danbutter said:
Forgive my ignorance here, but I thought you were never supposed to use the NC to format your SD card? (last step)
I thought I read somewhere that it messes up something in the emmc?
Hopefully I'm wrong and just paranoid
Click to expand...
Click to collapse
Formatting the SDcard doesn't touch the onboard storage. It is one of the easier ways to remove bonus partitions to recover the full card. UPDATE: I should clarify this: when running Eclair internally.
Homer
Any benefit of this over the 1.1r2 many of us did from autonootered 1.0.1?
danbutter said:
Forgive my ignorance here, but I thought you were never supposed to use the NC to format your SD card? (last step)
I thought I read somewhere that it messes up something in the emmc?
Hopefully I'm wrong and just paranoid
Click to expand...
Click to collapse
You're thinking of Nookie Froyo. The stock B&N system is fine for formatting the card.
I think formatting the SD card is an issue when you use one of the Froyo images and boot from eMMC. When you format the SD card it actually formats the internal boot partition or some such. I remember reading it in one of the threads which led me to only boot the Froyo images from an external card.
I am at 1.1.0. When did 1.1.1 appear & how do I get it?
BTW Is this exactly the same as the interim A-N 2.12.25 modified for 1.1?
k
I'd say it's a typo and should be v1.1?
Canadoc said:
Any benefit of this over the 1.1r2 many of us did from autonootered 1.0.1?
Click to expand...
Click to collapse
also interested to know that!
And if there is benefits, can we use the auto nooter?
Just for clarification, in steps 3 & 4 should the NC be turned off? I have never been sure if it matters, but the following statement makes me think that it should be off,
"5 Plug the USB cable into your computer and your NOOKcolor. (This will boot up the NOOKcolor.)"
Thanks,
kev
danbutter said:
Forgive my ignorance here, but I thought you were never supposed to use the NC to format your SD card? (last step)
I thought I read somewhere that it messes up something in the emmc?
Hopefully I'm wrong and just paranoid
Click to expand...
Click to collapse
Only with the froyo image.
Canadoc said:
Any benefit of this over the 1.1r2 many of us did from autonootered 1.0.1?
Click to expand...
Click to collapse
The main difference I see is that Clockwork recovery is not involved.
johnny054 said:
also interested to know that!
And if there is benefits, can we use the auto nooter?
Click to expand...
Click to collapse
I guess it should be the same, but I had a couple of games break after up'ing with 1.1_r2. So I wanted to try stock/clean 1.1 and then root...hoping this would bring them back.
help please
I'm having a problem rooting my nook color. 2 weeks ago I was fully rooted and for some reason I forget why? but I went back to stock. recently I updated to the newest Barnes & noble firmware. seeing the recent developments of honeycomb I wanted to root my nook again. so I tried downgrading to firmware before the most recent update and using that version of auto nooter. I followed the instructions exactly to a tee. the problem is my nook wont load the disk image from the sd card. I made sure to fully format the sd card before writing the img with Win32DiskImager. I made sure the nook was completely off then plugging in the usb to into the pc to wake up the nook. but nothing? the nook boots up like normal then says sd card damaged. I've formatted the sd card again and have used the newest nooter for my current 1.1. but nothing. the only difference is the first time I rooted I was at my mothers and used her pc. it was a windows vista 64 bit. my computer is windows seven 64 bit. anyone have any idea's as to why the nook wont load the sd card with the nooter image? I'm using the same sd card I was able to root from before. so I seriously doubt its the sd card. I am properly formatting it before writing the img. I am having no problem writing the img. any help would be appreciated
danbutter said:
Forgive my ignorance here, but I thought you were never supposed to use the NC to format your SD card? (last step)
I thought I read somewhere that it messes up something in the emmc?
Hopefully I'm wrong and just paranoid
Click to expand...
Click to collapse
brianf21 said:
Only with the froyo image.
Click to expand...
Click to collapse
Ok thanks for that clarification. I was pretty sure I read it somewhere!!
trentmaynard said:
I'm having a problem rooting my nook color. 2 weeks ago I was fully rooted and for some reason I forget why? but I went back to stock. recently I updated to the newest Barnes & noble firmware. seeing the recent developments of honeycomb I wanted to root my nook again. so I tried downgrading to firmware before the most recent update and using that version of auto nooter. I followed the instructions exactly to a tee. the problem is my nook wont load the disk image from the sd card. I made sure to fully format the sd card before writing the img with Win32DiskImager. I made sure the nook was completely off then plugging in the usb to into the pc to wake up the nook. but nothing? the nook boots up like normal then says sd card damaged. I've formatted the sd card again and have used the newest nooter for my current 1.1. but nothing. the only difference is the first time I rooted I was at my mothers and used her pc. it was a windows vista 64 bit. my computer is windows seven 64 bit. anyone have any idea's as to why the nook wont load the sd card with the nooter image? I'm using the same sd card I was able to root from before. so I seriously doubt its the sd card. I am properly formatting it before writing the img. I am having no problem writing the img. any help would be appreciated
Click to expand...
Click to collapse
You probably have a bad burn on the sdcard. Are you writing to the sdcard from the sd card reader or from the nook? Also, if you return to stock, (8 failed boots, then Power+N) You should be on firmware 1.0.0 or 1.0.1. Then root using one of the two original auto nooters, download rom manager from the market and flash the 1.1 pre-rooted firmware.
Thanks buddy, I try doing that. and I don't have an sd card reader so I just put the sd card that I'm going to write into my cell phone. then mount the sd card and write the img to the same storage device that represents the sd card. I'm sure this is the wrong way of doing it but I have gotten root doing the same thing before
Giving this a go now, coming from auto-nootered 1.0.1.
I apologize if this has been covered in another thread but I have been doing multiple searches on XDA and in google trying to find a solution but so far no luck. Long time reader of XDA but first time poster.
Details -
I successfully used NVFLASH, loaded Clockworkmod 0.8 and loaded Vega-Ntab gingerbread edition (stable RC1 I believe its called). I have been running this for a month or so with no major issues but I want to test out Vega-Ntab 5.1 and Brilliant Corners. Thinking of going with 5.1 for the hardware acceleration for gaming etc. Oh I also received my new Gtab with bootloader 1.2 and I downgraded that to 1.1 successfully before loading Vega-Ntab gingerbread. I think I can handle loading the new roms etc (may have to switch to 1.2 for Brilliant Corners I believe) but I want to do a full backup before doing so with clockworkmod so I can go back to gingerbread if I decide I liked it the best. But clockworkmod will not do a backup for me. I have tried multiple times and it always freezes/hangs at the same point. On the screen I see
ClockworkMod Recovery v2.5.1.1-bekit-0.8
SD card space free: 9697MB
Backing up boot...
Backing up recovery...
Backing up system... and here it will go no further
I have let it set at that point for hours but nothing changes. I checked the clockworkmod backup folder and it has a folder dated the current date of the backup but the contents is only boot.img and recovery.img and nothing else so I think that confirms it really isnt completing the backup.
I am unsure what the cause or solution to this is. I thought about reloading clockworkmod 0.8 but I don't think I can do this since it's already loaded. I thought about loading a newer version but from what I have read gingerbread and the other 1.1 roms will not work with anything but 0.8. I could just do a melt and repour and just go back to stock level and load 5.1 or Brilliant Corners but then I lose any apps I have loaded. I am not concerned about the majority of them but I have loaded a couple good ones as of late from Amazon that were the free app of the day and I am unsure whether I can "reload" these at a later date without being forced to pay. I have also paid for a couple games but I am assuming I can reload those without issue. I did back up all of the apps I paid for and amazon games that I loaded that I got for free (normally have to pay) with titanium backup. So assuming I can restore these with titanium backup after loading brilliant corners or vegan 5.1 then I guess the only thing that I lose by not being able to do a full backup/restore with clockwork is that if I want to go back to gingerbread then I have to start from scratch for reloading the rom.
So is the problem I am having running the back up successfully a known issue that I just can't seem to find a discussion thread about?
Thanks in advance for any help or advice.
Boot into ClockworkMod Recovery and get me a dmesg output (kernel messages) using adb. See this post for how.
Attach the dmesg.txt to your next post.
thanks for the reply. Unfortunately I am not having any luck getting the dmesg.txt file for you. I downloaded the iso image for Knoppix 6 but when I boot off the disc it starts processing everything but then it gives an error "the file /mnt-system/knoppix/knoppix is broken. then after about 30 secs it gives the following
/sbin/init: line 76: syntax error near unexpected token '/usr/share/fonts/type1/gsfonts/a010013l.pfb'
/sbin/init: line 76: '/URWGothicL-Book (usr/share/fonts/type1/gsfonts/a010013l.pfb);
I will try and download the iso from a different site and burn another disc.
I also tried a different route and loaded SDK manager to get to ADB by that route. I am running windows 7 if that makes a difference. I am not 100% sure when I am supposed to run the adb command line you listed. Do I have my gtab running clockworkmod and then mount USB so it will show up on my pc? Do I have to try and perform a backup and then run the adb command when it freezes? I don't think I can do that because if I navigate away from the mount USB it automatically unmounts it. Anyway adb doesn't appear to be seeing the gtab anyway. When I run the SDK manager it does not find any android devices. If I run the "adb devices" command it comes back with no devices. So I am not sure what basic thing I am missing to get adb or SDK to recognize the gtab.
I apologize for my lack of knowledge on adb. Your first link says if I have adb already set up to run adb shell dmesg > dmesg.txt while in clockworkmod so I am assuming I do this after mounting USB to get the pc to recognize the gtab.
I will try download and burn another iso image from a different location and see if I can boot off a disc. Assuming this time it is successful do I run the ADB command you listed in the second link while the GTab is mounted to USB and recognized by the pc? Hopefully ADB will see it if I can get this to work.
*update* I downloaded the ISO image from a different location. When I went to the folder it was downloaded to I noticed that the first ISO image I downloaded was only approx 100MB in size instead of 700+ mb. So I am re-burning another disc. Hopefully this will allow me to boot properly.
*update #2* I was able to successfully boot off of the new disc. Now I just need to figure out how and where to enter the adb command line in your link ($ sudo ./adb shell dmesg > dmesg.txt) i tried this using the Shell option but it says command not found. If I choose the File Manager option and navigate to where the adb file is that was in your linked zip file it just prompts me to edit/copy/move/rename or delete the file. I am out of time tonight so I will work on it more tomorrow. The good news though is that when I use File Manager the Gtab is listed so it is at least recognized. Now I just need to figure out how to get the dmesg.txt file you request but making some progress... I think
ashton555 said:
*update #2* I was able to successfully boot off of the new disc. Now I just need to figure out how and where to enter the adb command line in your link ($ sudo ./adb shell dmesg > dmesg.txt)
Click to expand...
Click to collapse
Step by step instructions in this post.
thanks a bunch. Those instructions were easy to follow and made sense. I have never used linux before but alot of it reminded me back of my old unix days (terminal commands that is).
Anyway I think I did everything correct and I am now attaching the txt file.
Thanks again for your help and patience with this Linux newbie let me know if I need to provide any additional information.
ashton555 said:
Anyway I think I did everything correct and I am now attaching the txt file.
Click to expand...
Click to collapse
You did indeed. And I can't see any obvious problems with the NAND-flash device, judging from the kernel messages.
Since you've already tried to take backups using CWM before, that action should've created a log file. This file might be useful. Retrieve it. Inside an xterm window on Linux, run:
Code:
hostpc$ [B]sudo ./adb pull /cache/recovery/log recovery.log[/B]
Attach this "recovery.log" file.
Next, try to read, one by one, the NAND flash partitions that CWM usually backs up. Here's an example run on my gTablet:
Code:
hostpc$ [B]sudo ./adb shell[/B] [I]Get into the shell in CWM[/I]
~ # [B]dump_image boot /dev/null[/B]
~ # [B]dump_image recovery /dev/null[/B]
~ # [B]dump_image system /dev/null[/B]
mtd: read error at 0x029a0000 (I/O error)
mtd: read error at 0x02da0000 (I/O error)
~ # [B]dump_image cache /dev/null[/B]
~ #
Type in only the commands in bold.
As you can see, my "system" partition on the NAND flash has errors (and the kernel also report this when it boots), but, the command will not hang. According to the kernel message that you just supplied, you don't have any errors on your onboard NAND flash, so, theoretically, you shouldn't get any errors at all. But, we'll see if the dump_image command hangs when reading system just like CWM does.
And if the dump_image command does hang somewhere, we can see if formatting just that system partition will get it working again. There is a utility on this board which we could use for doing that, though I've never tried it.
I successfully completed the next two tasks. I am attaching the recovery.log file. Note I had an issue copying the .log file to where I could access it in win7 (for some reason I cant attach a file while in linux). I opened it with a word processor and then saved it to my c drive which messed up the formatting. So I opened it in Word to get the formatting correct and saved it as a txt file so thats why the attached file is recovery.txt. Let me know if it messed it up to where its not useable.
On the second task
~ # dump_image boot /dev/null
this worked fine and quick
~ # dump_image recovery /dev/null
this worked fine and quick
~ # dump_image system /dev/null
this worked but took maybe 10-15 seconds
~ # dump_image cache /dev/null
this one gave an I/O error but completed the dump
mtd: read error at 0x00080000 (I/O error)
ashton555 said:
Let me know if it messed it up to where its not useable.
Click to expand...
Click to collapse
The file is just fine... and I can't see any error messages in it.
~ # dump_image system /dev/null
this worked but took maybe 10-15 seconds
Click to expand...
Click to collapse
This is normal -- "system" partition is ~200MB.
~ # dump_image cache /dev/null
this one gave an I/O error but completed the dump
mtd: read error at 0x00080000 (I/O error)
Click to expand...
Click to collapse
This also looks like normal behaviour, but, I'm puzzled that the kernel did not report any bad blocks on this partition. Check if this is a transient error:
1. Repeat the "dump_image cache ..." command a few times and see if the I/O error location is the same.
2. Try to "fix" the error on the cache partition by using the "wipe cache partition" menu item in CWM. Do this a couple of times.
3. Run the "dump_image cache ..." command again.
4. Attempt another full system backup using CWM.
If step 4 fails, we'll see if the writing of the backup to the sdcard is the problem, because the reading seems to be completing without any hangs as of now.
BTW, the most important partitions are all being read fine. The "cache" partition is not that important -- it can be empty (but not corrupt) each time the system boots and only the initial bootup might go a little slower.
And, if, in the end of all this, you can't use CWM at all, you can still make a full system backup using nvflash and a few Unix commands.
1. Repeat the "dump_image cache ..." command a few times and see if the I/O error location is the same
....i did the dump 4 times and it always gave the same I/O location
2. Try to "fix" the error on the cache partition by using the "wipe cache partition" menu item in CWM. Do this a couple of times
.... I wiped the cache 4 times successsfully
3. Run the "dump_image cache ..." command again.
.... same I/O error location
4. Attempt another full system backup using CWM
.... still freezing at backing up system
So I guess I need to try and do the backup with NVFlash and unix/linux commands? If you have a link on how to do that I will give it a try or I can search for it and see if there is a discussion thread on it.
Thanks again for your help and trying to resolve this
Question - if I started over from scratch and went back to stock and then loaded vegan gingerbread would this issue possibly correct itself? Also more importantly if I back up some apps using titanium backup before I go back to stock can I then restore them with Titanium once I have vegan ginger back loaded? Also if I loaded vegan 5.1.1 could I restore the same apps I backed up in vegan ginger? Hopefully that made sense. I don't mind starting from scratch if I need to I just wasnt sure if I would permanently lose certain apps I have loaded. It's only about 10 apps I care about
*update* - well I think I am going to be forced to start over anyway. After wiping the cache a couple times and attempting another backup (froze again at backing up system) I now can't get the gtab to boot completely. It is stuck at the flashing vegan ginger edition screen. It flashes for awhile then the screen goes black then it goes back to the flashing screen again. I know you said it would take longer to boot up the first time after wiping the cache but was doing the flash cycling for over an hour which I assume is too long? I tried wiping the cache again and I also wiped the davlik cache as someone suggested in another thread but it is back to being stuck in the flashing screen loop. Assuming I do have to start over can I at least boot to CWM, mount ext USB and copy off the titanium backup files I made so I can restore some of the paid for apps?
ashton555 said:
3. Run the "dump_image cache ..." command again.
.... same I/O error location
Click to expand...
Click to collapse
Looks like a permanent I/O error in the cache partition, then. But, I don't understand why it is "system" which is hanging on backup.
4. Attempt another full system backup using CWM
.... still freezing at backing up system
Click to expand...
Click to collapse
Get me the recovery.log.
So I guess I need to try and do the backup with NVFlash and unix/linux commands?
Click to expand...
Click to collapse
I'll think this over during the weekend. In the mean-time, read through this thread. You can safely take a complete backup of your tablet while I do a bit of experimentation on a clockworkmod-like solution. But, I suspect that you may not be able to backup "cache" using nvflash going by the I/O errors. I have errors on my "system" partition and a nvflash backup fails on it, but CWM doesn't have any problems backing up and restoring.
Question - if I started over from scratch and went back to stock and then loaded vegan gingerbread would this issue possibly correct itself?
Click to expand...
Click to collapse
Probably not. But, see this thread. It shows you how to wipe all the partitions on the NAND flash device. We don't need to format the entire NAND flash. We can see if doing a few repeated formats of the "system" and "cache" partitions gets CWM working again, if you're willing to wipe "system"--you will have to load Vegan-Ginger right after this.
Also more importantly if I back up some apps using titanium backup before I go back to stock can I then restore them with Titanium once I have vegan ginger back loaded? Also if I loaded vegan 5.1.1 could I restore the same apps I backed up in vegan ginger? Hopefully that made sense. I don't mind starting from scratch if I need to I just wasnt sure if I would permanently lose certain apps I have loaded. It's only about 10 apps I care about
Click to expand...
Click to collapse
I haven't used Titanium backup so I can't say how well it works, but, judging from the reports that other users have made, what you're suggesting should work without any problems. User downloaded applications are stored either on /data or on /mnt/sdcard (for apps moved to SD card). Since your SD cards don't seem to be affected, you can go ahead with Titanium backup.
ashton555 said:
Assuming I do have to start over can I at least boot to CWM, mount ext USB and copy off the titanium backup files I made so I can restore some of the paid for apps?
Click to expand...
Click to collapse
Yeah, copy the files in CWM, then just do a "wipe data/factory reset" and see if it boot loop goes away.
But, before you do that, gimme a half-hour and I'll send you commands which you can use to save the files in /data and /sdcard. I just have to compile and test a new version of busybox. The tar command already present in CWM doesn't seem to work properly for me.
Attaching the recovery file
I am running the nvflash back up right now.
It successfully did part-1.img through part-11.img with no errors. The last thing it said though is
"rem CACHE PARTITION BACKUP NOT NEEDED
"nvflash.exe" -r --read 12 part-12.img
press enter to continue
Is this maybe because I wiped the cache and it's empty?
I looked on my ext SD card and the titanium backup files are there (except for a couple I had forgotten do ....) so I think I am okay for going back to square one if need be.
I will go ahead (tomorrow probably) try doing what is described thread about wiping partitions on the NAND device and just formating the system and cache partitions. I am assuming that at this point I guess its okay to go ahead and try to load vegan tab 5.1.1 instead of ginger again since I wanted to try out 5.1.1 anyway or if you have any experience with it would you recommend Brilliant Corners instead since its a newer rom. I think I will have to reload the 1.2 bootloader which is okay.
ashton555 said:
Attaching the recovery file
Click to expand...
Click to collapse
No errors in there.
The last thing it said though is
"rem CACHE PARTITION BACKUP NOT NEEDED
"nvflash.exe" -r --read 12 part-12.img
press enter to continue
Is this maybe because I wiped the cache and it's empty?
Click to expand...
Click to collapse
I think so. The cache partition isn't that important anyway, so it can be skipped.
I will go ahead (tomorrow probably) try doing what is described thread about wiping partitions on the NAND device and just formating the system and cache partitions.
Click to expand...
Click to collapse
I would suggest that you copy the Titanium backed-up apps safely away immediately, then format just the system and cache partitions as per that thread. You will need to be in APX mode to use nvflash.
Immediately after the nvflash, (since the system partition is now gone), boot into CWM, then do a factory reset, repartition the internal sdcard, copy the Vegan-5.1.1 update file onto the now clean sdcard through the PC and then flash it. This should give you a clean slate.
Then check if you can do a backup using CWM. If you still can't, then I'll see if a solution can be devised to do partial backups.
And, I have tried neither Vegan* nor Brilliant Corners, so the choice is up to you.
Sorry, my test commands aren't working so I can't send you those commands I promised to back up your /data and /system--I suspect a bad USB cable.
Hi,
I have a Nook Tablet in version 1.4.1 reset it back to 1.4.0, root it, tried to put cm9 in it...messed up royally, format a whole bunch of things that I shouldn't.
Now it's stuck in CWM v5.5.0.4
Tried just about everything, but can't get out. can't access adb, not very familiar with it anyway...but downloaded sdk, jkd, etc...but can't see device...tried recovery image also...doesn't work.
Is there any method aside from adb method? Is there an SD method...think I messed up the partitions or whatever...
tried this method:
http://forum.xda-developers.com/showthread.php?t=1555832
but doesn't work...
again can't see devices in adb...tried this & other methods...nothing..
http://forum.xda-developers.com/showthread.php?t=1363652
please help...
I actually have 2 Nook Tablets...one for my kids & another I'll give to a nun friend...1 is correctly rooted & has cm9...can I image one & flash it on another? If so, how?
Thank you & God bless
Have you tried making a bootable CM7 or CWM microSD card?
Solar.Plexus said:
Have you tried making a bootable CM7 or CWM microSD card?
Click to expand...
Click to collapse
I have a recovery.img...tried that didn't work
have boot.img tried that...CWM microSD
tried to flash SD_ROOT_NT16gbV4_6 onto microSD, but after that can't add anything else to it...the directions to partition microSD is somewhat confusing to me...don't quite know what to do or where to put boot file, etc...after I partitioned it...any advice is greatly appreciated...
"format a whole bunch of things that I shouldn't." BAD IDEA. Can you tell us what exactly you formatted?
Is always good to have adb working so you should troubleshoot it. In my FAQ there is a link for a how-to i made to install and use adb tool, run the runmefirst.bat from the package i provide is a must.
As an alternative (to non use of adb, etc tools) you can use Adam's total wipe (sdcard), which has been fixed by Adam to not affect serial ID's and MAC address from ROM partition.
~ Veronica
lavero.burgos said:
"format a whole bunch of things that I shouldn't." BAD IDEA. Can you tell us what exactly you formatted?
Is always good to have adb working so you should troubleshoot it. In my FAQ there is a link for a how-to i made to install and use adb tool, run the runmefirst.bat from the package i provide is a must.
As an alternative (to non use of adb, etc tools) you can use Adam's total wipe (sdcard), which has been fixed by Adam to not affect serial ID's and MAC address from ROM partition.
~ Veronica
Click to expand...
Click to collapse
I formatted....
bootdata, cache, data, emmc, rom, system, sd-ext....everything with the format in front of it...I did it...I know...not smart...
did the acclaim_update...doesn't work...CWM seems to be working...but just can't install acclaim_update or SD_ROOT_NT16gbV4_6...again can't access adb at all
What does it say when in CWM when you try to flash something?
thungrac221 said:
I formatted....
bootdata, cache, data, emmc, rom, system, sd-ext....everything with the format in front of it...I did it...I know...not smart...
did the acclaim_update...doesn't work...CWM seems to be working...but just can't install acclaim_update or SD_ROOT_NT16gbV4_6...again can't access adb at all
Click to expand...
Click to collapse
they won't work because you formatted most of your partitions, use Adam's total wipe as i said before or soshite unbrick method but for that one you need adb working.
~ Veronica
lavero.burgos said:
they won't work because you formatted most of your partitions, use Adam's total wipe as i said before or soshite unbrick method but for that one you need adb working.
~ Veronica
Click to expand...
Click to collapse
I don't have ubuntu, think I saw a link from you to create a virtual ubuntu? Please post that again...Thank you
nevermind...found the link...will try...thanks again
thungrac221 said:
I don't have ubuntu, think I saw a link from you to create a virtual ubuntu? Please post that again...Thank you
Click to expand...
Click to collapse
I use virtual box: https://www.virtualbox.org/wiki/Downloads
If he has cwm he has adb.
Just guide him to install correct drivers for it.
Solar.Plexus said:
What does it say when in CWM when you try to flash something?
Click to expand...
Click to collapse
tried to install recover.img, but Error mounting /sdcard..tried mounting, but can't
thungrac221 said:
I don't have ubuntu, think I saw a link from you to create a virtual ubuntu? Please post that again...Thank you
nevermind...found the link...will try...thanks again
Click to expand...
Click to collapse
Well, I download the adam's image for windows, but in CWM cannot mount sd card...oddly, when I plug it into my computer, it sees the nook but cannot start adb...tried methods to recognize usb, but can't...
please advise....thank you
Go here, https://github.com/succulent/acclaim_recovery_sdcard
Make a new recovery card from the instruction. Forget your old recovery card.
Install these two,
flash-restore-stock.zip (use it to restore partition 1-6)
flash_stock_1.4.2.zip (use it to restore to stock 1.4.2)
Then install whatever rom you want after.
succulent said:
Go here, https://github.com/succulent/acclaim_recovery_sdcard
Make a new recovery card from the instruction. Forget your old recovery card.
Install these two,
flash-restore-stock.zip (use it to restore partition 1-6)
flash_stock_1.4.2.zip (use it to restore to stock 1.4.2)
Then install whatever rom you want after.
Click to expand...
Click to collapse
Thank you, thank you...used only this flash-restore-stock.zip & was able to find my way back... thanks a lot...my friend who is a nun will enjoy this when she goes to Ghana on her mission...she wanted this instead of carrying loads of spiritual books...thanks again... & God bless
I second that succulent with your post I was able to find my way back after flash-restore-stock.zip. My issue was Nook kept on booting CWM. Now I have to figure out how to boot CWM via USB again to flash stock rom. For now it takes me up to B&N member setup page, but only shows error when I enter info
Okay I wiped my internal emmc, so there is no OS. When I turn it on I get B&N stock setup menu. Than after account sign in it gives me error message with device info.
I can boot on SD CWM, but when I try to flash any zip it aborts and also I can't seem to find the right CWM SD that leaves me enough room to copy the OS.zip on the SD.
I was doing a factory reset to clean install one of the CM10.1 release candidates and I went into Mounts and Storage and I accidentally formatted ROM instead of System. Now Cyanoboot keeps going into CWM and won't boot my rom. I flashed a different rom and I also restored from backup but neither did the trick. Any tricks that can get my dear old Nook booted? Any help would be greatly appreciated. (My last resort is one of those lengthy unbrick posts if there's no way to fix it. I've done these before but if there is an easier solution I'd like to try that first.)
I am familiar with adb (and ubuntu if need be).
Do you know the serial number? Like when you use adb, and you type adb devices, it shows a serial number. Did you write it down? I have a backup of the ROM partition and it includes a few files in there containing serial and mac address, etc. The serial number is important for it to boot AFAIK, so I hope you have that somewhere.
sagirfahmid3 said:
Do you know the serial number? Like when you use adb, and you type adb devices, it shows a serial number. Did you write it down? I have a backup of the ROM partition and it includes a few files in there containing serial and mac address, etc. The serial number is important for it to boot AFAIK, so I hope you have that somewhere.
Click to expand...
Click to collapse
I have the serial number (behind the microsd card slot)..but not the mac address
Also, I only wiped the ROM and system partitions. The factory partition is still there untouched and I've read somewhere that it contains a backup of the information in the ROM partition.
adb devices shows a serial number of abcdef123456789.
Not exactly a good sign...Should I try so****e's serial number recovery thing through ubuntu?
If what you had re-formatted by mistake is /rom but your /factory is still intact then not all was lost, as /factory holds romdata.zip which is a backup archive of data files in /rom (see http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31 for more elaboration).
What you can try is to flash stock recovery (e.g., flash_stock_recovery.zip from Succulent's repo https://github.com/succulent/acclaim_recovery_sdcard), then do the "8 failed reboots" to trigger a "factory reset to stock".
Can you try to use adb from CWM? Try "adb pull /factory" and see if it copies over the factory folder to your computer.
digixmax said:
If what you had re-formatted by mistake is /rom but your /factory is still intact then not all was lost, as /factory holds romdata.zip which is a backup archive of data files in /rom (see http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31 for more elaboration).
What you can try is to flash stock recovery (e.g., flash_stock_recovery.zip from Succulent's repo https://github.com/succulent/acclaim_recovery_sdcard), then do the "8 failed reboots" to trigger a "factory reset to stock".
Click to expand...
Click to collapse
Factory is definitely in tact; only rom was formatted (I figured factory was important so I didn't want to format it.) I'll try this after and let you know. I'm going to manually flash partition 5 onto my nook through adb and see if that can get me up and running.
sagirfahmid3 said:
Can you try to use adb from CWM? Try "adb pull /factory" and see if it copies over the factory folder to your computer.
Click to expand...
Click to collapse
pull: building file list...
0 files pulled. 0 files skipped.
This was through command prompt/adb in Windows 7. Should I try Ubuntu?
topdawg7793 said:
pull: building file list...
0 files pulled. 0 files skipped.
This was through command prompt/adb in Windows 7. Should I try Ubuntu?
Click to expand...
Click to collapse
You need to mount the /factory partition before you can access it.
Why not do it the easy way: just flash stock recovery and let it restore the missing data as part of the "8 failed boots" factory reset process?
digixmax said:
You need to mount the /factory partition before you can access it.
Why not do it the easy way: just flash stock recovery and let it restore the missing data as part of the "8 failed boots" factory reset process?
Click to expand...
Click to collapse
I had no clue it fixed the missing data! Just did it and I'm back to a working nook. Appreciate the help everybody!
So what did you do to finally get it fixed? Flash stock recovery and do the 8 failed reboots method?
sagirfahmid3 said:
So what did you do to finally get it fixed? Flash stock recovery and do the 8 failed reboots method?
Click to expand...
Click to collapse
I know I'm slightly late on this, but I figure I should at least respond so any poor soul who gets into the same situation and sees this thread can have some go-to solution. I never got to do the partition thing through adb (use somebody's ROM partition and change the serial number and mac address to that of my Nook) so I booted an SDcard version of some CM10 nightly and then used the touchscreen firmware flasher to restore to the factory firmware. Then I took out the SDcard and did the 8 reboots thing and that finally fixed it.
NOTE: NEVER GO BACK TO STOCK WHILE ON THE 10-TOUCH FIRMWARE. YOUR TOUCHSCREEN WILL NOT WORK AND YOU WILL EFFECTIVELY BE STUCK UNTIL YOU BOOT OFF AN SDCARD AND RESTORE THE FACTORY TOUCHSCREEN FIRMWARE.
topdawg7793 said:
I had no clue it fixed the missing data! Just did it and I'm back to a working nook. Appreciate the help everybody!
Click to expand...
Click to collapse
lol well now i know wut to do if i accidentally format rom. cheers every1 who helped topdawg :highfive:
[Q] stock unrooted at&t sgh-i777 stuck in boot loop. can I pull contacts, sms, memos
Hello folks,
I have a stock, unrooted AT&T SGH-i777 which is stuck in a 'boot loop' - on power on, I see 'Samsung Galaxy SII' blink infinitely.
The good news is that I can go into download mode as well as recovery mode. I can also connect via adb from my win7 machine.
I was able to pull camera files (pics/vids) from /sdcard/DCIM and whatsapp data (/sdcard/WhatsApp/) using adb pull.
I want to backup (or pull) my contact and sms data (it wasn't synced on phone) as well. However I'm not able to. Do I need to root the phone to use adb for this? If so, how do I root the phone?
Alternatively is there is another way to restore the phone to working condition without losing my contacts and sms data?
I tried rooting it using the 'Easy Rooting Toolkit' v2.0 by DooMLoRD modified by Max Lee @ GalaxyS2Root.com but the runme.bat starts adb and then hangs there indefinitely.
Any help would be appreciated.
Thank you,
Hammad.
...Whether this works on an Unrooted device, I am not sure, but the goal is to install custom firmware onto a stock device without formatting the data partition (where your sms/contacts/other data are kept)...
Use desktop ODIN to flash a custom kernel/recovery
perform a nandroid backup (via custom kernel/recovery)**
install Samsung-based firmware (cooked or shostock) via custom recovery***
**creates a snapshot of the nand memory module, where everything is stored. Once a working setup is established, Titanium backup (among other tools) can extract contacts, wifi settings, sms & mms messages, etc from this nandroid backup even if you have to conduct a factory reset, in the process of restoring the device.
***this "dirty flash" approach which will hopefully allow you to boot into the device, and backup what you need.
This process has been used recently in a similar scenario, and is fully detailed in another thread:
http://forum.xda-developers.com/galaxy-s2-att/help/phone-wont-boot-to-restore-deleted-file-t2827622
-Cyril
hsophie said:
Hello folks,
I have a stock, unrooted AT&T SGH-i777 which is stuck in a 'boot loop' - on power on, I see 'Samsung Galaxy SII' blink infinitely.
The good news is that I can go into download mode as well as recovery mode. I can also connect via adb from my win7 machine.
I was able to pull camera files (pics/vids) from /sdcard/DCIM and whatsapp data (/sdcard/WhatsApp/) using adb pull.
I want to backup (or pull) my contact and sms data (it wasn't synced on phone) as well. However I'm not able to. Do I need to root the phone to use adb for this? If so, how do I root the phone?
Alternatively is there is another way to restore the phone to working condition without losing my contacts and sms data?
I tried rooting it using the 'Easy Rooting Toolkit' v2.0 by DooMLoRD modified by Max Lee @ GalaxyS2Root.com but the runme.bat starts adb and then hangs there indefinitely.
Any help would be appreciated.
Thank you,
Hammad.
Click to expand...
Click to collapse
Thank you Cyril279 for your response. I had a few questions/clarifications since I'm a complete newbie when it comes to flashing/ROMs/rooting/android:
My Android version is Gingerbread 2.3.x. I never upgraded it since I bought it in mid Feb 2012.
cyril279 said:
...Whether this works on an Unrooted device, I am not sure, but the goal is to install custom firmware onto a stock device without formatting the data partition (where your sms/contacts/other data are kept)...
Click to expand...
Click to collapse
I'm new to this stuff so I want to make sure that I state things correctly. By unrooted, I mean my device has never ever been rooted. It is stock in all ways from AT&T. Does that change anything?
cyril279 said:
Use desktop ODIN to flash a custom kernel/recovery
perform a nandroid backup (via custom kernel/recovery)**
install Samsung-based firmware (cooked or shostock) via custom recovery***
**creates a snapshot of the nand memory module, where everything is stored. Once a working setup is established, Titanium backup (among other tools) can extract contacts, wifi settings, sms & mms messages, etc from this nandroid backup even if you have to conduct a factory reset, in the process of restoring the device.
***this "dirty flash" approach which will hopefully allow you to boot into the device, and backup what you need.
This process has been used recently in a similar scenario, and is fully detailed in another thread:
http://forum.xda-developers.com/galaxy-s2-att/help/phone-wont-boot-to-restore-deleted-file-t2827622
-Cyril
Click to expand...
Click to collapse
I read through the thread that you linked to. I want to make sure I understand what I need to do is in:
A. message #5: get ODIN and siyah kernels.
Questions: The Siyah website says that the kernel is for i9100 on JB. Should I still use that one even though my phone is the SGH-I777 and on Gingerbread? Will this upgrade the kernel to JellyBean?
B. message #7: do steps 1,2,3,6,7; (skip 4,5).
Question: Step 6 states '...rooted android'. My phone is not rooted. Will it get rooted as part of A?
Thank you for your patience with me.
Hammad.
Hey guys I'm looking for help with the same issue.. If I had twrp or cwm I'd be good but this phone is my daughters and has not been brought over to the dark side..
This is the problem. Yesterday she came to me and her phone was bootlooping the samsung logo. So I've tried to pull the battery, master reset and call att with no luck. :thumbdown:
I'm wondering since I'm in bootloop and no custom recovery can I maybe flash a custom rom or stock rom to this with the same method..
Thanks Any advice is well appreciated...
I need to get this fixed ASAP. My daughter is two young to be home alone with no phone.....
Sent from my SM-G900A using Xparent BlueTapatalk 2
In this case, we are only using the recovery portion of the kernel, so it doesn't matter that it's for an i9100. There are other .tar versions that are designed specifically for the i777, I just didn't search for them.
I haven't tried this procedure on a never-rooted device, but I expect that it works. Perhaps one of our peers will chime in if they know better, otherwise if you're willing to wait a couple days, I will try the complete procedure out on my own i777, starting from gingerbread.
As long as you can get into download mode, and you DO NOT perform a factory reset, then the prognosis for data recovery is good.
In the meantime, in may be helpful to familiarize yourself with the use of desktop odin.
-Cyril
hsophie said:
Thank you Cyril279 for your response. I had a few questions/clarifications since I'm a complete newbie when it comes to flashing/ROMs/rooting/android:
My Android version is Gingerbread 2.3.x. I never upgraded it since I bought it in mid Feb 2012.
I'm new to this stuff so I want to make sure that I state things correctly. By unrooted, I mean my device has never ever been rooted. It is stock in all ways from AT&T. Does that change anything?
I read through the thread that you linked to. I want to make sure I understand what I need to do is in:
A. message #5: get ODIN and siyah kernels.
Questions: The Siyah website says that the kernel is for i9100 on JB. Should I still use that one even though my phone is the SGH-I777 and on Gingerbread? Will this upgrade the kernel to JellyBean?
B. message #7: do steps 1,2,3,6,7; (skip 4,5).
Question: Step 6 states '...rooted android'. My phone is not rooted. Will it get rooted as part of A?
Thank you for your patience with me.
Hammad.
Click to expand...
Click to collapse
---------- Post added at 04:51 PM ---------- Previous post was at 04:47 PM ----------
"master reset"? = factory reset?
If so, then you're not worried about the recovery of any data, and the easiest path is to use desktop Odin to flash the stock i777UCMD8 firmware onto your I777. That firmware can be found here:
http://forum.xda-developers.com/showpost.php?p=20229527&postcount=46
JEZZEJAMEZ said:
Hey guys I'm looking for help with the same issue.. If I had twrp or cwm I'd be good but this phone is my daughters and has not been brought over to the dark side..
This is the problem. Yesterday she came to me and her phone was bootlooping the samsung logo. So I've tried to pull the battery, master reset and call att with no luck. :thumbdown:
I'm wondering since I'm in bootloop and no custom recovery can I maybe flash a custom rom or stock rom to this with the same method..
Thanks Any advice is well appreciated...
I need to get this fixed ASAP. My daughter is two young to be home alone with no phone.....
Sent from my SM-G900A using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
cyril279 said:
In this case, we are only using the recovery portion of the kernel, so it doesn't matter that it's for an i9100. There are other .tar versions that are designed specifically for the i777, I just didn't search for them.
I haven't tried this procedure on a never-rooted device, but I expect that it works. Perhaps one of our peers will chime in if they know better, otherwise if you're willing to wait a couple days, I will try the complete procedure out on my own i777, starting from gingerbread.
As long as you can get into download mode, and you DO NOT perform a factory reset, then the prognosis for data recovery is good.
In the meantime, in may be helpful to familiarize yourself with the use of desktop odin.
-Cyril
Click to expand...
Click to collapse
Thank you once again Cyril279. I'll familiarize myself with ODIN. I'm not in a hurry since I have a replacement phone. I just want to make sure I can get my data and restore my device. Where can I find kernel for i777?
Hammad.
Thanks, my wife is all over my azz. School is about to start, with our busy schedules she's(daughter) home alone alot. As many others we don't have a land phone.. ...
Sent from my SM-G900A using Xparent BlueTapatalk 2
hsophie said:
Where can I find kernel for i777?
Click to expand...
Click to collapse
Siyah for 2.3.x. There is a tar version.
hsophie said:
Thank you Cyril279 for your response. I had a few questions/clarifications since I'm a complete newbie when it comes to flashing/ROMs/rooting/android:
My Android version is Gingerbread 2.3.x. I never upgraded it since I bought it in mid Feb 2012.
I'm new to this stuff so I want to make sure that I state things correctly. By unrooted, I mean my device has never ever been rooted. It is stock in all ways from AT&T. Does that change anything?
Click to expand...
Click to collapse
No, that does not change anything for this excersize.
hsophie said:
I read through the thread that you linked to. I want to make sure I understand what I need to do is in:
A. message #5: get ODIN and siyah kernels.
Questions: The Siyah website says that the kernel is for i9100 on JB. Should I still use that one even though my phone is the SGH-I777 and on Gingerbread? Will this upgrade the kernel to JellyBean?
Click to expand...
Click to collapse
The initial kernel flash (step 1) is only for the custom recovery. It will be overwritten by a more appropriate kernel later, when we flash the firmware.
Regarding kernel choice, there are usually two major considerations: what device, and what firmware version is it designed for. An i9100 kernel will boot an i777 into recovery without issue. Since this process won't be using the initial kernel to boot into android, we are not limited to specific versions of i9100 or i777 kernels. We only need to find a .tar version for use with desktop Odin.
--that said--
If you do use an i777 version that is designed for android 2.3.x (thanks @creepyncrawly), then you have the option of booting into Android once the kernel is flashed.
hsophie said:
B. message #7: do steps 1,2,3,6,7; (skip 4,5).
Question: Step 6 states '...rooted android'. My phone is not rooted. Will it get rooted as part of A?
[...]
Click to expand...
Click to collapse
Desktop Odin uses root-level access to install firmware (whether stock or custom), so establishing root-access prior, or as a separate step is not necessary when using this method to install custom firmware.
Our process will be different than that shown in message #7, since we are not trying to manually repair the system. We will be attempting the dirty-flash method which involves the first few steps of message #7, and more from message #11.
Process:
0.5) Save custom Samsung-based firmware (cooked v2.2 or shostock3) onto internal memory or sdcard
1) Use desktop Odin to flash Siyah kernel
^^ Installs a kernel/recovery that will allow you to perform a nandroid backup, and flash firmware.
^^This WILL change the initial boot screen (can be corrected later, but does not affect the function of the firmware), and will notch the flash counter (simply doesn't matter).
2) Boot to recovery
3) Create nandroid backup
^^ If things go sideways, you have a snapshot of where you are. If you have to start from scratch, there are apps that can restore Apps, settings, and more, from a backup.
4) Install custom Samsung-based Firmware
^^ Restores the original file-system, without overwriting the /data partition.
5) Attempt boot into android
-Success?
Thank you for your detailed response Cyril279.
For confirmation, I will:
0. use the shostock3 v2.3a firmware from here. I'm assuming that getting it onto the device will require connecting via adb, use adb shell to mkdir and then push the unzipped contents to a directory such as /sdcard/shostock3v23a/
1a. install Desktop ODIN 1.85 or 3.07.
b. use Odin to flash the Siyah-v2.6.14-att.tar mentioned by creepyncrawly [have to read how to do this]
2. boot to recovery
3. create nandroid backup.
Q: Is there a way to exclude the DCIM folder during backup or delete all my pics from the camera before backup since I already have backed all content from /sdcard/DCIM (camera). It was 5.5gb? I'm also assuming that the backup will be created on the phone itself so it has to have enough space on it to hold the backup.
4. Install shostock3 v2.3a [have to read how to do this]
5. hopefully boot successfully into my phone.
cyril279 said:
Process:
0.5) Save custom Samsung-based firmware (cooked v2.2 or shostock3) onto internal memory or sdcard
1) Use desktop Odin to flash Siyah kernel
^^ Installs a kernel/recovery that will allow you to perform a nandroid backup, and flash firmware.
^^This WILL change the initial boot screen (can be corrected later, but does not affect the function of the firmware), and will notch the flash counter (simply doesn't matter).
2) Boot to recovery
3) Create nandroid backup
^^ If things go sideways, you have a snapshot of where you are. If you have to start from scratch, there are apps that can restore Apps, settings, and more, from a backup.
4) Install custom Samsung-based Firmware
^^ Restores the original file-system, without overwriting the /data partition.
5) Attempt boot into android
-Success?
Click to expand...
Click to collapse
Close, you're close.
Regarding getting the firmware onto the device, the easiest method is to save the files on a micro sd card via PC (formatted as fat32), then insert the card into the device. Otherwise yes, adb push will get it there as well.
0 Use the shostock from the first post of that thread (420mb). The "version 2.3a" that you mention is just a kernel.
1a. install Desktop ODIN 1.85 or 3.07
1b Use Odin to flash the siyah.tar mentioned by creepyncrawly.
desktop Odin use: http://forum.xda-developers.com/showpost.php?p=53669365&postcount=360
2. boot to recovery
3. create nandroid backup.
Don't worry about DCIM, the nandroid does not backup the internal memory partition (aka internal sd card) where your photos are stored.
A factory reset also does not touch this partition. <-- BUT DO NOT FACTORY RESET
You are correct that the backup is stored on the device, so it IS important that there is enough space for the backup.
4. Install shostock3 v4.0 [have to read how to do this]
^^It's fairly straight forward while in recovery. If not, we're here to help.
5. hopefully boot successfully into my phone.
hsophie said:
Thank you for your detailed response Cyril279.
For confirmation, I will:
0. use the shostock3 v2.3a firmware from here. I'm assuming that getting it onto the device will require connecting via adb, use adb shell to mkdir and then push the unzipped contents to a directory such as /sdcard/shostock3v23a/
1a. install Desktop ODIN 1.85 or 3.07.
b. use Odin to flash the Siyah-v2.6.14-att.tar mentioned by creepyncrawly [have to read how to do this]
2. boot to recovery
3. create nandroid backup.
Q: Is there a way to exclude the DCIM folder during backup or delete all my pics from the camera before backup since I already have backed all content from /sdcard/DCIM (camera). It was 5.5gb? I'm also assuming that the backup will be created on the phone itself so it has to have enough space on it to hold the backup.
4. Install shostock3 v2.3a [have to read how to do this]
5. hopefully boot successfully into my phone.
Click to expand...
Click to collapse
Thank you Cyril279 once again.
I started the process last night... have some more questions. Please see below:
cyril279 said:
Close, you're close.
Regarding getting the firmware onto the device, the easiest method is to save the files on a micro sd card via PC (formatted as fat32), then insert the card into the device. Otherwise yes, adb push will get it there as well.
0 Use the shostock from the first post of that thread (420mb). The "version 2.3a" that you mention is just a kernel.
Click to expand...
Click to collapse
For step 0:
I downloaded the full shostock rom as specified. Since I don't have a microSD card available I'm going to copy shostock to the internal sdcard (/sdcard) using adb push.
Do I need to copy the unzipped contents of shostock or just put the single zip file there?
cyril279 said:
1a. install Desktop ODIN 1.85 or 3.07
1b Use Odin to flash the siyah.tar mentioned by creepyncrawly.
desktop Odin use: http://forum.xda-developers.com/showpost.php?p=53669365&postcount=360
2. boot to recovery
3. create nandroid backup.
Don't worry about DCIM, the nandroid does not backup the internal memory partition (aka internal sd card) where your photos are stored.
A factory reset also does not touch this partition. <-- BUT DO NOT FACTORY RESET
You are correct that the backup is stored on the device, so it IS important that there is enough space for the backup.
Click to expand...
Click to collapse
I wanted to make sure I have enough space for step 3 so I connected via adb and checked disk space using df. I get this:
Code:
D:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell df
Filesystem Size Used Free Blksize
/dev 418M 76K 418M 4096
/tmp 418M 56K 418M 4096
/system 503M 472M 31M 4096
/mnt/.lfs: Function not implemented
/cache 246M 4M 241M 4096
/sdcard 11G 8G 3G 32768
Questions:
1. Which filesystem will get backed up from above using nandroid?
2. Do I have enough space given the information above?
3. I wasn't able to figure out whether you can specify where to save your nandroid backup from my research. Does it allow you specify a backup location? [I would want to put it under the /sdcard partition since its got the most space].
cyril279 said:
4. Install shostock3 v4.0 [have to read how to do this]
^^It's fairly straight forward while in recovery. If not, we're here to help.
5. hopefully boot successfully into my phone.
Click to expand...
Click to collapse
Thanks for the encouragement, I'll probably try the process tonight. Will post update once done unless I have other questions.
Hammad.
hsophie said:
[...]
For step 0:
I downloaded the full shostock rom as specified. Since I don't have a microSD card available I'm going to copy shostock to the internal sdcard (/sdcard) using adb push.
Do I need to copy the unzipped contents of shostock or just put the single zip file there?
Click to expand...
Click to collapse
Copy the entire zip file onto the device.
hsophie said:
I wanted to make sure I have enough space for step 3 so I connected via adb and checked disk space using df. I get this:
Code:
D:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell df
Filesystem Size Used Free Blksize
/dev 418M 76K 418M 4096
/tmp 418M 56K 418M 4096
/system 503M 472M 31M 4096
/mnt/.lfs: Function not implemented
/cache 246M 4M 241M 4096
/sdcard 11G 8G 3G 32768
Questions:
1. Which filesystem will get backed up from above using nandroid?
2. Do I have enough space given the information above?
3. I wasn't able to figure out whether you can specify where to save your nandroid backup from my research. Does it allow you specify a backup location? [I would want to put it under the /sdcard partition since its got the most space].
Click to expand...
Click to collapse
1. A nandroid backup will typically backup /system, /data, and /boot(/kernel) partitions (Your partition report is missing a few items). -stock i777 partition table-
2. 3GB is enough for a nandroid
3.Typically, from the first screen of ClockworkMod recovery you would select {backup & restore}, and the submenu will provide options to {backup to internal sdcard} or {backup to external sdcard} (among others)
hsophie said:
Thanks for the encouragement, I'll probably try the process tonight. Will post update once done unless I have other questions.
Hammad.
Click to expand...
Click to collapse
:fingers-crossed:
---------- Post added at 04:13 PM ---------- Previous post was at 03:32 PM ----------
I have never used that shell df command, and I'm not yet sure about all of what it returns, but I certainly got different results when booted into android, than when I was booted into recovery. Were you booted into the stock 3e recovery when you performed the shell df command?
Code:
List of devices attached
001952750d598e recovery
C:\Android\sdk\platform-tools>adb shell df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 404636 136 404500 0% /dev
tmpfs 404636 12 404624 0% /tmp
/dev/block/mmcblk0p7 251968 4276 247692 2% /cache
/dev/block/mmcblk0p11
11901568 6185360 5716208 52% /emmc
/dev/block/mmcblk0p11
11901568 6185360 5716208 52% /and-sec
Code:
List of devices attached
001952750d598e device
C:\Android\sdk\platform-tools>adb shell df
Filesystem Size Used Free Blksize
/dev 395.2M 136.0K 395.0M 4096
/sys/fs/cgroup 395.2M 12.0K 395.1M 4096
/mnt/asec 395.2M 0.0K 395.2M 4096
/mnt/obb 395.2M 0.0K 395.2M 4096
/mnt/fuse 395.2M 0.0K 395.2M 4096
/system 503.9M 320.2M 183.8M 4096
/cache 246.1M 4.2M 241.9M 4096
/efs 19.7M 9.2M 10.5M 4096
/data 2.0G 1.0G 941.5M 4096
/preload 503.9M 293.6M 210.3M 4096
/mnt/media_rw/sdcard0: Permission denied
/mnt/secure/asec: Permission denied
/storage/sdcard0 11.4G 5.9G 5.5G 8192
cyril279 said:
1. A nandroid backup will typically backup /system, /data, and /boot(/kernel) partitions (Your partition report is missing a few items).
I have never used that shell df command, and I'm not yet sure about all of what it returns, but I certainly got different results when booted into android, than when I was booted into recovery. Were you booted into the stock 3e recovery when you performed the shell df command?
Click to expand...
Click to collapse
Yes, I was in the stock 3e recovery when I connected via adb and ran the command. Since I'm not root perhaps its not showing me the /data partition. I can cd into /data but ls doesn't show anything.
I'll send you an update tonight. Thanks for all of your help so far! I really appreciate it.
OK, here is what I did:
1. I wasn't able to copy/push shostock to my phone via adb. I kept getting "failed to copy ? to ?: Read-only file system."
I tried remounting, but it also failed, probably because I don't have root access.
So I've deferred this step to later.
2. I ran ODIN 1.85 desktop, put the phone in ODIN mode and flashed the siyah kernel. ODIN ran successfully and my phone rebooted successfully!
The boot screen shows a yellow triangle and I9100 on it though.
At this point I have access to my phone again. I was able to copy whatsapp history using the guide on their website.
I decided that I'll just sync contacts to google, but lo and behold, I just discovered that wifi isn't working. When I turn it on, it turns off after a few seconds. It doesn't bring up any wifi networks on scan.
Is there a way to make the wifi work again?
Thanks
Hammad.
Update:
1. I copied the shostock ROM through USB/windows
2. I created a nandroid backup from CWMR Touch Recovery onto internal sdcard. I got the following messages on backup:
Code:
SD Card space free: 8645MB
Backing up boot image...
Backing up system...
Backing up data...
[I]No /sdcard/.android_secure found. Skipping backup of applications on external storage.[/I]
Backing up cache...
[I]No sd-ext found. Skipping backup of sd-ext.[/I]
Generating md5 sum...
Backup complete!
Are the two messages in italics a problem?
Update #2:
I decided to install shostock. Installation went smoothly. My wi-fi issue was also resolved with the upgrade and I have Android 4.1.2 on my phone.
Thank you Cyril279 for all of your help on this. I couldn't have done it without your guidance!
hsophie said:
[...]
1. I wasn't able to copy/push shostock to my phone via adb. I kept getting "failed to copy ? to ?: Read-only file system."
I tried remounting, but it also failed, probably because I don't have root access.
So I've deferred this step to later.
Click to expand...
Click to collapse
When I tried the process, as soon as I rebooted to the siyah kernel, I was able to ADB push to the device, but I don't know what command you issued, or what path you chose.
Code:
adb push c:\path\to\file.zip /storage/sdcard0/
Code:
adb push c:\path\to\file.zip /sdcard/
Ultimately this didn't matter since you were able to boot into android, and the file could be copied via USB.
hsophie said:
2. I ran ODIN 1.85 desktop, put the phone in ODIN mode and flashed the siyah kernel. ODIN ran successfully and my phone rebooted successfully!
Click to expand...
Click to collapse
Darn right it did!
Thanks again @creepyncrawly, using this specific kernel made this portion of the process possible.
hsophie said:
The boot screen shows a yellow triangle and I9100 on it though.
Click to expand...
Click to collapse
The method of recovery that we used tripped the device's custom-flash monitor (voids service under warranty). It doesn't affect the functionality of the firmware at all, but if you prefer to have the correct initial boot animation, then you'll need to follow an additional procedure.
http://forum.xda-developers.com/gal...to-restore-deleted-file-t2827622/post54521059
hsophie said:
At this point I have access to my phone again. I was able to copy whatsapp history using the guide on their website.
I decided that I'll just sync contacts to google, but lo and behold, I just discovered that wifi isn't working. When I turn it on, it turns off after a few seconds. It doesn't bring up any wifi networks on scan.
Is there a way to make the wifi work again?
Thanks
Hammad.
Update:
1. I copied the shostock ROM through USB/windows
2. I created a nandroid backup from CWMR Touch Recovery onto internal sdcard. I got the following messages on backup:
Code:
SD Card space free: 8645MB
Backing up boot image...
Backing up system...
Backing up data...
[I]No /sdcard/.android_secure found. Skipping backup of applications on external storage.[/I]
Backing up cache...
[I]No sd-ext found. Skipping backup of sd-ext.[/I]
Generating md5 sum...
Backup complete!
Are the two messages in italics a problem?
Click to expand...
Click to collapse
No they are not a problem at all. Both of those messages are the result of the fact that you simply didn't have an external sd card installed, so it's informing you that it skipped the backup of the cache files there-on. /boot, /system and /data are what really matter.
hsophie said:
Update #2:
I decided to install shostock. Installation went smoothly. My wi-fi issue was also resolved with the upgrade and I have Android 4.1.2 on my phone.
Thank you Cyril279 for all of your help on this. I couldn't have done it without your guidance!
Click to expand...
Click to collapse
Our pleasure, although the process wasn't quite as expected, I'm certainly glad to hear that it worked out.
As mentioned earlier, if the i9100 bootscreen bothers you, then there's another (easier) adventure with your name all over it!
Happy flashing
-Cyril
cyril279 said:
When I tried the process, as soon as I rebooted to the siyah kernel, I was able to ADB push to the device, but I don't know what command you issued, or what path you chose.
Code:
adb push c:\path\to\file.zip /storage/sdcard0/
Code:
adb push c:\path\to\file.zip /sdcard/
Ultimately this didn't matter since you were able to boot into android, and the file could be copied via USB.
-Cyril
Click to expand...
Click to collapse
Just to clarify, I tried adb pushing it before flashing the siyah kernel. The phone wasn't rooted so thats why it didn't work.
My next challenge is to figure out how to copy my calendar to google calendar and then sync it so that it copies to my replacement phone (HTC One M8). I was using the samsung calendar, without it being linked to my google account.
Whatsapp data transfer was a cinch. Just copy the folder to the same location on new phone and install whatsapp and you're done.
I transferred memos from the S2 to M8 but I think the memo files are samsung proprietary format. I'll need to figure out how to transfer that info.
The other issue would be transferring my sms as well.
Any recommendations on tools for this would be appreciated.
Thanks.
Hammad.
hsophie said:
Just to clarify, I tried adb pushing it before flashing the siyah kernel. The phone wasn't rooted so thats why it didn't work.
Click to expand...
Click to collapse
Got it, makes sense.
hsophie said:
My next challenge is to figure out how to copy my calendar to google calendar and then sync it so that it copies to my replacement phone (HTC One M8). I was using the samsung calendar, without it being linked to my google account.
Whatsapp data transfer was a cinch. Just copy the folder to the same location on new phone and install whatsapp and you're done.
I transferred memos from the S2 to M8 but I think the memo files are samsung proprietary format. I'll need to figure out how to transfer that info.
The other issue would be transferring my sms as well.
Any recommendations on tools for this would be appreciated.
Thanks.
Hammad.
Click to expand...
Click to collapse
I can't recommend titanium backup highly enough for backup and restoration of apps and their data -including contacts, calendar content, wifi connections, sms/mms, etc. It might not be able to get the memo data to a different program, but remember, all of this info is captured in your nandroid backup as well, and titanium backup can extract it directly from the nandroid into the new firmware.
-Cyril
cyril279 said:
I can't recommend titanium backup highly enough for backup and restoration of apps and their data -including contacts, calendar content, wifi connections, sms/mms, etc. It might not be able to get the memo data to a different program, but remember, all of this info is captured in your nandroid backup as well, and titanium backup can extract it directly from the nandroid into the new firmware.
-Cyril
Click to expand...
Click to collapse
I could have sworn that I've read on here multiple times that restoring data to apps, even with TIB, results in problematic operations. If I jumped ROMs but had backed up my apps and data with TIB, if I restore the data ONLY in the new ROM, that should be no problem?