Related
i have followed the guide for rooting sprint hero to a letter
when it tells me to do back up in recovery mode (step 8) i press home button and i get this error Run nandroid-mobile.sh via adb!
i searched and searched this forum for answer to no avail.
so can you please help me with this?
thanks!
try downloading the Fresh Kitchen and attemp to use it to do a backup. I have run into this a couple times and for some reason however the kitchen gets you into the recovery seems to get things to work properly.
The "with Google" phones have issues rooting straight to 1.5.2. Try 1.2.3., then update.
bossyman15 said:
i have followed the guide for rooting sprint hero to a letter
when it tells me to do back up in recovery mode (step 8) i press home button and i get this error Run nandroid-mobile.sh via adb!
i searched and searched this forum for answer to no avail.
so can you please help me with this?
thanks!
Click to expand...
Click to collapse
I ran across this issue recently myself. There was something wrong with my storage card. I manually backed up the storage card, formatted it, then I put the files back. After that, nandroid backup worked like a charm! ...and I have a "with Google" phone. Hope this helps...
Veldetta said:
I ran across this issue recently myself. There was something wrong with my storage card. I manually backed up the storage card, formatted it, then I put the files back. After that, nandroid backup worked like a charm! ...and I have a "with Google" phone. Hope this helps...
Click to expand...
Click to collapse
thanks that worked! expect i had to delete most of my stuff off my SD card.
I've had that a few times. I found that plugging my phone to the charger solves it every time.
I got that error once, and it was because I had renamed my Nandroid backup. Just rename it back to the original, and it'll be ok.
Also confirming that this worked, thanks alot.
Just a theory on why this might not work:
How much space do you have left on your SD cards?
Maybe there is not enough room to expand the zip file while it is restoring it.
bossyman15 said:
i have followed the guide for rooting sprint hero to a letter
when it tells me to do back up in recovery mode (step 8) i press home button and i get this error Run nandroid-mobile.sh via adb!
i searched and searched this forum for answer to no avail.
so can you please help me with this?
thanks!
Click to expand...
Click to collapse
I only got this error once when my sdcard did not have enough space for the backup. I would put money on that being your problem.
theresthatguy said:
I only got this error once when my sdcard did not have enough space for the backup. I would put money on that being your problem.
Click to expand...
Click to collapse
I can confirm that... make a space on your SD card to continue...
I just got this error and freeing up space on the SD card didn't work for me. I formated and everything. Still getting the same error. I am just gonna ruu and start over...
i was getting this error yesterday.fixed it though,the night before i changed the names of the backups...i renamed them back to somewhat the original name n it worked.
Just got this error message. Checked the size of my backups...about 181MB...checked the free space I had...about 101MB. Deleted 3 of the backup files I had to free up space, then it worked. So, for me...it was a space problem.
space problem
I was getting the run nandroid via adb error also... like you said... "not enough space..." that fixed it for me. so simple... thanks
I have the same error message...
My sdcard is empty... i have not a space problem...
I only get the error when my batter is below 40 percent or so and not on the charger. I believe its a safety measure to make sure your phone doesnt die and brick in the process.
I just had this same error, and read through the solutions. None were relevant.
However, I changed my spaces to underscores in my file names and now it works.
Hope this helps someone else. Just make sure everything is in "one word".
I had this issue about an hour ago. I had changed the names of my back ups (So I could remember what the heck they were backing up). I'm fairly certain that changing the name is what caused the issue. I had enough space on my SD card and I even tried plugging it into the charger (as reccommended in previous posts).
Putting underscores instead of spaces fixed this for me. Thank you kingkeld! I'm glad I never ran into this issue sooner, otherwise I would have been screwed (since you only posted this 4 days ago).
all you need to do is plug your phone in and restore
just had that issue and it's a fail safe to ensure no bricking in case your phone dies
I need a .img of the original rom, where can i find? Thanks
Aran83 said:
I need a .img of the original rom, where can i find? Thanks
Click to expand...
Click to collapse
You cant, every NST is unique and using an image from another NST will cause trouble for both you and the NST it came from.
Thanks, nook is bricked but I can read the main partition, which .img I install?
Sorry for my english.
Aran83 said:
Thanks, nook is bricked but I can read the main partition, which .img I install?
Sorry for my english.
Click to expand...
Click to collapse
There's no img you can install.
You can try booting n2T-Recovery (v0.2) from a SD card and see if that helps. (Do not write that image to your NST!)
If not, send me a PM and I'll try to help you out
Something else you can try:
1) Flash noogie.img to an sd card.
2) Hook up your nook to a pc via usb once it has booted, and you should see all the partitions exported there.
3) In one of those partitions (recovery maybe? I'm struggling to remember), there's a factory.zip, which you can then install using the "Install from zip" feature of clockwork mod.
If you go this route, you'll have to reflash your sd card with clockwork mod after you've extracted the factory.zip using noogie.
Seems like kind of a pain, but I just recovered my device using this.
Remains in the screen ROOTED FOREVER and i can't do anything
I think, for michaelwill's method, you need to have linux running. I suggest you to try ros87's suggestion.
if I use backup from nook of my friend?
Aran83 said:
if I use backup from nook of my friend?
Click to expand...
Click to collapse
That is not a good idea, since each NookTouch has a unique information to register. If you are thinking of full restore from your friend's image (1.8GB image), it will overwrite your unique information. In that case, you and your friend's devices cannot register to BnN (or just one device). People says the info is stored in /rom. If you want to know more, you need to dig more. Otherwise try factory reset suggested by ros.
herofmm said:
That is not a good idea, since each NookTouch has a unique information to register. If you are thinking of full restore from your friend's image (1.8GB image), it will overwrite your unique information. In that case, you and your friend's devices cannot register to BnN (or just one device). People says the info is stored in /rom. If you want to know more, you need to dig more. Otherwise try factory reset suggested by ros.
Click to expand...
Click to collapse
Correct!
Using a image from another NST is a very very bad idea!
There are a lot of stuff that's unique to your NST stored in /rom and in rombackup.zip on the Factory partition.
This includes:
Serial Number
Main Board Serial
Product ID
Manufacturing date
SHA hash of Private Key
Public Key in modulus form
WiFi Calibration file
Some unique binary file for your eInk screen
MAC Address
Battery Type
Duplicating the serial will make you or your friend unable to register with B&N
Duplicating / Faking the private/public key pair, will most likely make you unable to register with B&N (I'm currently testing this)
Duplicating a WiFi calibration can cause degraded WiFi performance
Duplicating that EPD vcom file (eInk screen).. well who knows
Duplicating the MAC will cause network troubles if used on the same network.
The wrong Battery Type (I've seen three different so far) can cause charging troubles, and will cause incorrect charge indication.
Don't go there!
NookRestore.img
Try writing NookRestore.img to an mSD card. (You can get a copy at my website: NootRoot)
Hard reset
I had issues rooting my NST and got stuck in a boot loop. After digging and digging through forums I finally discovered the secret to a hard reset. The instructions said to hold the power and the two bottom side buttons down together for over 20 seconds. That worked! My NST was back to when I pulled it out of the box. I then proceeded to re rooting. (my mistake was I did not upgrade the OS before rooting). My bad. Hope this helps someone recover from a stuck boot loop.
Good luck.
chucktate said:
My NST was back to when I pulled it out of the box.
Click to expand...
Click to collapse
No it wasn't, Factory Reset doesn't remove root files or system apps installed by root tools, it only clears custom apps and settings.
While you might think it's back to stock, there are still leftover files and changes in /boot and /system
ros87 said:
Correct!
Using a image from another NST is a very very bad idea!
There are a lot of stuff that's unique to your NST stored in /rom and in rombackup.zip on the Factory partition.
Click to expand...
Click to collapse
Hi, I've just found a way around this - it is possible to restore somebody else's .img file, provided you've backup up your rombackup.zip. Then after, using Noogie, you can overwrite rombackup.zip and the contents of it which are on a different partition. The only danger is that you would potentially overwrite battery type config file, as Nook has couple of them. I gave it a try on mine and it seems fine.
sokoow said:
Hi, I've just found a way around this - it is possible to restore somebody else's .img file, provided you've backup up your rombackup.zip. Then after, using Noogie, you can overwrite rombackup.zip and the contents of it which are on a different partition. The only danger is that you would potentially overwrite battery type config file, as Nook has couple of them. I gave it a try on mine and it seems fine.
Click to expand...
Click to collapse
That is correct.
Problem is that most people who end up in a state where Factory Restore doesn't work has usually managed to overwrite their partition tables and part of the /rom partition.
And at this point it is too late to backup rombackup.zip as it's usually fragmented and cannot be recovered by ext2 file recovery tools.
So.. do a full backup before you do anything to your NST
I found if you restore with holding the two lower buttons it will remove all rooted files.
Googie2149 said:
I found if you restore with holding the two lower buttons it will remove all rooted files.
Click to expand...
Click to collapse
Read post 13 by ros87!
ros87 said:
No it wasn't, Factory Reset doesn't remove root files or system apps installed by root tools, it only clears custom apps and settings.
While you might think it's back to stock, there are still leftover files and changes in /boot and /system
Click to expand...
Click to collapse
Go to my website, download nookRestore.img and write it to an mSD card, Erase and De register, Power Off, then insert mSD then power up, then follow on screen instructions!
[OT - Removed]
[OT - Removed]
Torimu.Joji said:
I'll update the website and post links to XDA.
Click to expand...
Click to collapse
Thank you sir!
By posting proper links you help ensure that people get the most recent software and information
Hello !
I am feeling really down today after been trying to get my phone working again.
There is a huge problem currently, I am really annoyed that it doesn't work at all.
First thing, my phone won't start after update it just boot loops and never seem to end it.
First thing I noticed /boot, /cache /system and most things are gone, I can load up recovery but nothing more. I have no idea what happened but the whole image folder was wiped and I had to myself put in the CWM recovery.
I can't do an upgrade "again" as it will be stuck @ the unpacking part without starting it at all.
I been trying with 2.3 V2 and with B133(My stock rom I got).
If anyone has a solution that can solve this problem please help out if you could. Also if you are about to tell me get this and that, please most cases I haven't seen any of the Firmware roms in @modaco wiki links work. Means I can't download them, so if you happen to have spare copy please upload it and link it to me. I have been googling and looking through this section twice, nothing really worked out.
Thanks in advance !
If you didn't erase the .cust_backup partition which contain the image folder with all system' s .img files, then maybe it' s damaged. I had some problems with this partition before and when I checked it with windows check disk it repairs it and I had no problems from then. So, try this, and if you still haven' t any file on image folder, you can find the original folder on X5' s forums. Is definately here, but I don't remember where is the link and I don't gonna search it for you. If you cannot find it, you can allways reflash the original rom. If you fix the partition(if this is the problem), I don't think that you'll have problems with update any more.
dancer_69 said:
If you didn't erase the .cust_backup partition which contain the image folder with all system' s .img files, then maybe it' s damaged. I had some problems with this partition before and when I checked it with windows check disk it repairs it and I had no problems from then. So, try this, and if you still haven' t any file on image folder, you can find the original folder on X5' s forums. Is definately here, but I don't remember where is the link and I don't gonna search it for you. If you cannot find it, you can allways reflash the original rom. If you fix the partition(if this is the problem), I don't think that you'll have problems with update any more.
Click to expand...
Click to collapse
Hello, thanks for the reply.
I have no idea about this .cust_backup partition and how I am supposedly to access it via windows. Also the thing you said about fixing partition within Windows, the check disk thing. I am not sure about that part either as I can load CWM and it can read the partitions but they are empty. Also there is nothing in this forums that contains original things, only way for me to fix this if someone have extra copy and can guide me on how and where to place the all needed files. I am pretty sure it's only things that are missing and I can't get a grip out of this.
So to sum up what my problem is.
I did an upgrade from 2.2 to 2.3 with official firmware, it worked out normally but after a reboot my phone became stuck in an endless loop, I can't do anything and it will not I repeat it will not allow me to "re flash" any firmware I tried so far, the 2.3 V2 and B133.
I am begging someone in this forum section, please if you have the knowledge about this problem care to help?
I can't get a refund out the phone warrenty is off and I do not have that much spare money.
Thanks in advance !
If you can get to recovery, wipe cache and data. It should be possible in stock recovery.
The cust partition has all the images for bootloader, recovery etc. You can get to it with the pink screen. Reformatting and then reinserting the images and files could help, but try that when nothing else works.
I can't give you good help via phone, but try wiping data first. Also, try if you can use some other sd card.
Sent from my U8800 using Tapatalk
Blefish said:
If you can get to recovery, wipe cache and data. It should be possible in stock recovery.
The cust partition has all the images for bootloader, recovery etc. You can get to it with the pink screen. Reformatting and then reinserting the images and files could help, but try that when nothing else works.
I can't give you good help via phone, but try wiping data first. Also, try if you can use some other sd card.
Sent from my U8800 using Tapatalk
Click to expand...
Click to collapse
The most common things I have already done, but do enlighten me what this "custom" parition is. Because in windows I do not see such partition I see a removable partition which I have now added a folder called image with these containing files.
http://forum.xda-developers.com/showthread.php?t=1370960
EDIT ** Also regarding to first person who said about Windows partition manager. The thing is I see a lot of partitions and there is no labeling for them, might be because they are ext2/3 or even something else? In anycase I can't do so much I just find it really odd I have many duplicates and I am guessing that must be errors... Because I am seeing the main recovery partition which has no label too... its at 240 MB where 135MB is used. Lastly there is my internal SD card empty and healthy still I can't reach it within Windows if I do not mount it...And can't now without going into the android OS. I Have loads of free space "partitions I don't understand why they are there".
**
Thanks for helping out, it feels not good to have a half dead phone, it's still not solved :'-(
The .cust_backup is the mount point on android for this removable partition with image folder. In windows haven' t this name. I didn't mean to use the windows partition manager, just to use windows explorer, right click on the partition and choose properties, then tools and then check disk. Of course you can use partition manager too, but because as you found there are all no labeled other partitions there and is a bit confused.
As you mentioned, you found the original image folder and you replaced the files. Did you tried to do the update again after that?
Also you can see and the internal sd partiton, but you need linux system. This partition is not fat32, so windows cannot see it.
dancer_69 said:
The .cust_backup is the mount point on android for this removable partition with image folder. In windows haven' t this name. I didn't mean to use the windows partition manager, just to use windows explorer, right click on the partition and choose properties, then tools and then check disk. Of course you can use partition manager too, but because as you found there are all no labeled other partitions there and is a bit confused.
As you mentioned, you found the original image folder and you replaced the files. Did you tried to do the update again after that?
Also you can see and the internal sd partiton, but you need linux system. This partition is not fat32, so windows cannot see it.
Click to expand...
Click to collapse
I have placed all things that I got from here.
http://forum.xda-developers.com/showthread.php?t=1370960
And I can't run the upgrade firmware, it gets stuck at first stage which is to unpack the the update.app thing.
It just stays like that not blinking and frozen.
Did you tried now that you have the original files, to go to recovery mode and wipe data etc?
Also when you try to do the upgrade do you have the device connected with the cable?
I had this problem once and I think that when I disconnected the cable(or maybe wasn' t connected and I connected it, I don't remember well), the proccess bar starts to moving after a while and the upgrade completed successfully.
dancer_69 said:
Did you tried now that you have the original files, to go to recovery mode and wipe data etc?
Also when you try to do the upgrade do you have the device connected with the cable?
I had this problem once and I think that when I disconnected the cable(or maybe wasn' t connected and I connected it, I don't remember well), the proccess bar starts to moving after a while and the upgrade completed successfully.
Click to expand...
Click to collapse
You are not understanding me :-(, I have wiped already millions of times in millions of different ways just to get it work. And no, I don't have the device connrected when I upgrade, it won't work properly then, I have tried to wait for the progress bar to "start" move it won't happen the battery will die, and nothing happened.
I can't go in with normal Recovery mode, can only go in with CWM, the normal recovery mode is really small, I mean only 3mb, while the froyo version is 5mb. Now I am asking if you have the time to upload the image files from 2.3 V2, the ones in forums are for V1. Which I don't know might conflict.
Thanks again for trying to help me out, this is really frustrating to get it to work.
**EDIT**
I worked it out !
I think I understood what you meant, I did as you told I started first with pluggin in the charger forced it to upgrade and now it's upgrading, thank you so much dancer_69. I was going to go tomorrow to buy a new 2nd hand smartphone. But now I can save my money for other things !
**EDIT of EDIT **
I seem to have downgraded to B133, I will try now with B158 2.3 V2 again and hopefully it will work now.
Yes, wasn't clear because I don' t remember what I've done and solve it. But I think that I did it like you discribed too.
Anyway I'm glad that was helpful(kind of)..
And don' t give up so soon with smartphone' s bricks, I've faced brick kind of problems many times and if the device it' s not completely dead, there is something you can do. Maybe need more search or many tries(sometimes the same things) but at the end(and of course If there isn't a hardware problem) device can unbrick.
Guys, I had quite bad experience rooting my glowlight nook with touchnooter . Basically messed smth up so it couldn't start (just kept flashing). didn't save my back up. had to do unrooting with the software 1.1 that I guess was from nook without glowlight. Unrooting went fine, but the glowlight function is not working anymore. does anyone know how to solve this or could give me a link to download the proper software? thanks!
dukenookem said:
Guys, I had quite bad experience rooting my glowlight nook with touchnooter . Basically messed smth up so it couldn't start (just kept flashing). didn't save my back up. had to do unrooting with the software 1.1 that I guess was from nook without glowlight. Unrooting went fine, but the glowlight function is not working anymore. does anyone know how to solve this or could give me a link to download the proper software? thanks!
Click to expand...
Click to collapse
you should read the instructions better next time...
but making errors is human and you have a cool nick
I'll hopefully receive my glow in two weeks and I'll upload my backup then
You should make an effort to salvage your personalized data in /rom.
There is all the info in the p2 partition (/rom).
There is also a backup copy in the p3 partition (/factory) as rombackup.zip
You might do this with noogie or CWR and ADB.
Zorkman said:
you should read the instructions better next time...
but making errors is human and you have a cool nick
I'll hopefully receive my glow in two weeks and I'll upload my backup then
Click to expand...
Click to collapse
I could use that backup too, to revive my nook =)
I have an open thread here with all the efforts done so far http://forum.xda-developers.com/showthread.php?t=1805936
Nook Glow Backup Image
I have a backup image of a NSTG that I am uploading right now ... and looks like it just finished. Here it is:
dl[dot]dropbox[dot]com/u/98836278/nook-glow-backup.img
When you have the image downloaded follow these instructions:
blog[dot]the-ebook-reader[dot]com/2012/05/02/how-to-backup-and-restore-nook-glow-and-nook-simple-touch/
As a new user I am not allowed to post outside links.
Downloading, thank you so much!!!
I'll post again with the results...
YES, YES, YES, YES !!!!!!
leadbella thank you a million times!!
I downloaded the image, and wrote it ot my nook.
By the end of the operation, which took some 9 minutes or so, the process ended abruptly:
error 27 writing to disk at sector 3825664
I opted to ignore it and reboot the nook, just to see what happened. The nook booted alright.
I then booted in CWR and replaced /rom with the contents of my own nook /rom which I had salvaged.
I then booted again, and performed all the process flawlessly.
So far I have registered the device again (no error here since /rom contains my sensitive data. Don't know if it would work if the data was from the original image, since MAC address, device SN and some other parameters would not match), loaded a couple of books and started reading again.
Just in time for another one week shift (leaving tomorrow)
Leadbella you saved my..... nook =)
Thank you, I owe you one.
No problem at all. Looks like it worked for srgarfi ... dukenookem please let me know when you have finished downloading the image. I need to use my dropbox for other things at some point, but I can keep it in there until you finish downloading the image. If the image link above no longer works and anyone needs a copy of this image feel free to send me a message and I will try to post it back up.
The image is from a just out of the box NSTG with no information and nothing added to it.
leadbella said:
No problem at all. Looks like it worked for srgarfi ... dukenookem please let me know when you have finished downloading the image. I need to use my dropbox for other things at some point, but I can keep it in there until you finish downloading the image. If the image link above no longer works and anyone needs a copy of this image feel free to send me a message and I will try to post it back up.
The image is from a just out of the box NSTG with no information and nothing added to it.
Click to expand...
Click to collapse
Thanks Leadbella. Downloaded the backup. Tried to follow the instructions, but the size of you file is almost 2 gb, too large for my microSD. Didn't expect the backup file to be that large. gonna go look for a larger sd card.
Renate NST said:
You should make an effort to salvage your personalized data in /rom.
There is all the info in the p2 partition (/rom).
There is also a backup copy in the p3 partition (/factory) as rombackup.zip
You might do this with noogie or CWR and ADB.
Click to expand...
Click to collapse
That totally didn't make any sence to me. Sorry for my ignorance. Are there any instructions to follow? thanks.
Could not register
Hey leadbella, thanks for uploading the backup image. I downloaded and worte it to my nook STG. However, I couldnt get pass the setup process. Everytime I reach the log in menu, it will have the error logging in msg. Do you know what might be wrong?
Zaotr0pe said:
Hey leadbella, thanks for uploading the backup image. I downloaded and worte it to my nook STG. However, I couldnt get pass the setup process. Everytime I reach the log in menu, it will have the error logging in msg. Do you know what might be wrong?
Click to expand...
Click to collapse
You should have saved your /rom files before ovewritting your nook with leadbella's image.
And I'm afraid there not anything you can do to recover your unique /rom files for your nook now.
Oh, I was concerned that Leadbella had posted an unedited backup...
so, what is going on?
first: if a post about partitions isn't comprehensible to you yet -- you probably shouldn't root your device until you do enough reading that you understand it a bit.
Putting leadbella's file onto an SD card probably won't work as a way to restore; when I recover from an image, I use a usb cable and write from my computer to my device.
Leadbella seems to have taken a complete backup image from the device - this will include the important /boot and /system partitions (which is good) but will also include the /rom partition, which unfortunately is unique to every device.
So, if you restore from that image and don't have access to your own /rom partition or recovery image, you're going to wind up attempting to register a second copy of Leadbella's Nook to your account. Fortunately for Leadbella, that won't work.
Now, what can you do to repair and get a corrected nook which can be registered?
I'm going to try an experiment - I'm going to start by backing my device up in its current state.
(I do this by making a Noogie disk
Booting from Noogie
Connecting to my computer
using the command dd if=/dev/sdX of=/dev/currentnookglow.img bs=1M
where X is the number of the device that pops up when I connect my NSTG to the USB port.)
That requires linux; if you don't have linux, you can install VMWare Player (Free) and then install linux in that.)
What I'm going to try doing:
- back my system up
- image with Bella's file
- delete the file /rom/devconf/MACAddress from the imaged device
- reboot the device
- see if I can now see the real, physical MAC address, either on the device (unlikely) or on my router (likelier)
If I can see the MAC address, recreate the file with the correct values for Mac and also create a correct file for serial number /rom/devconf/SerialNumber
Boot, and see if the device is registerable to my account.
BUT: right now, BN has blown out the Nook Touch register/deregister/register process. So I can't do the test until they fix that.
And if it does work, anyone trying it will need
- the noogie disk
- linux
For windows users, maybe, but I have not tried:
- a clockwork boot disk
- functioning ADB able to connect to your clockwork-booted device
(Some clockwork boots support ADB; some do not.)
as roustabout explains, you can write Leadbella's image to your nook (if in windows use win32diskimager or diskimage) and then take a look at the contents of /rom.
The fix the contents of macaddress and serialnumber, but only if you plan to use the nook with B&N services fix the rest of the necessary files.
If you just plan to use your nook as a standalone reader (yes, why not?) once registered you can just ignore the contents of /rom (at least until the next software update).
leadbella said:
I have a backup image of a NSTG that I am uploading right now ... and looks like it just finished. Here it is:
dl[dot]dropbox[dot]com/u/98836278/nook-glow-backup.img
When you have the image downloaded follow these instructions:
blog[dot]the-ebook-reader[dot]com/2012/05/02/how-to-backup-and-restore-nook-glow-and-nook-simple-touch/
As a new user I am not allowed to post outside links.
Click to expand...
Click to collapse
These links are both no longer available. Can someone post them to a mirror?
I'd really appreciate reup as well, since my backup is not working and I need to restore my NSTG.
before restoring from someone else's img, remember to salvage your own /rom partition since these files are unique to each device and you'll need them to register your nook prior to starting reading.
That said I can upload that IMG, but what's the best choice to do so? Any of the many filesharing services? Dropbox ? Google Drive?
require those images
Hi srgarfi, is it possible for you to please upload those images... i need them...
Please reupload the backup. I could really use it too.
the image I used, originally shared by LeadBella (thanks again!) is here:
https://www.dropbox.com/s/xikkjs627s9mw2r/nook-glow-backup.img
Remember to save your /rom files before applying the backup or you won't be able to register your nook on B&N to start reading.
Hi lovely people,
Ive managed to mess up my glowlight - Ive managed to have a look at the partition table using noogie and the rom partition is showing as unallocated. I've tried data recovery to no avail. I dont suppose anyone has a complete image of a uk nook simple touch glowlight by any chance, or even just a copy of the rom partition that I can copy back into place using minitool partition wizard?
Thanks for reading folks
cortexbomber said:
Hi lovely people,
Ive managed to mess up my glowlight - Ive managed to have a look at the partition table using noogie and the rom partition is showing as unallocated. I've tried data recovery to no avail. I dont suppose anyone has a complete image of a uk nook simple touch glowlight by any chance, or even just a copy of the rom partition that I can copy back into place using minitool partition wizard?
Thanks for reading folks
Click to expand...
Click to collapse
I don't have a full image, but I do have a copy of the /rom partition for you!
Here you go! :good:
thenookieforlife3 said:
I don't have a full image, but I do have a copy of the /rom partition for you!
Here you go! :good:
Click to expand...
Click to collapse
Thanks :0)
Umm how do I use the qr code on my pc? I dont have a webcam or decent mobile phone
cortexbomber said:
Thanks :0)
Umm how do I use the qr code on my pc? I dont have a webcam or decent mobile phone
Click to expand...
Click to collapse
You don't need the QR code to download the .zip. Just click the name of the file up there ^, it's to the left of the "Click for QR Code" text.
thenookieforlife3 said:
You don't need the QR code to download the .zip. Just click the name of the file up there ^, it's to the left of the "Click for QR Code" text.
Click to expand...
Click to collapse
Doh! i thought it was just the one link.
Ive been using computers since the early 80's - embarrasing!
cortexbomber said:
Doh! i thought it was just the one link.
Ive been using computers since the early 80's - embarrasing!
Click to expand...
Click to collapse
The eighties? Wow, you're an old pro, then! :good:
I, on the other hand, wasn't even alive in the eighties!
Let me know how that /rom partition treats you.
thenookieforlife3 said:
The eighties? Wow, you're an old pro, then! :good:
I, on the other hand, wasn't even alive in the eighties!
Let me know how that /rom partition treats you.
Click to expand...
Click to collapse
Ha! Old Pro indeed Old yes. Pro? Definitely questionable. :good:
Will do. Just having trouble now creating a fat32 partition. The various programs ive tried only let me make a 16mb fat16 partition and after putting the rom data on it, the nook still doesnt want to boot. There may be other problems with the rest of the software. Ah well. I'll either get there or buy another e-reader )) But the challenge is more entertaining.
cortexbomber said:
Ha! Old Pro indeed Old yes. Pro? Definitely questionable. :good:
Will do. Just having trouble now creating a fat32 partition. The various programs ive tried only let me make a 16mb fat16 partition and after putting the rom data on it, the nook still doesnt want to boot. There may be other problems with the rest of the software. Ah well. I'll either get there or buy another e-reader )) But the challenge is more entertaining.
Click to expand...
Click to collapse
lol :laugh:
Have you tried booting NookManager from your sdcard and using the "Restore factory.zip" function? That seems to work very consistently.
thenookieforlife3 said:
lol :laugh:
Have you tried booting NookManager from your sdcard and using the "Restore factory.zip" function? That seems to work very consistently.
Click to expand...
Click to collapse
Just trying that now
cortexbomber said:
Just trying that now
Click to expand...
Click to collapse
No joy sadly. More scouring the internet later i think - House chores to do now. SIgh.
Mayn thanks for the rom and the rest of your advice tho
cortexbomber said:
No joy sadly. More scouring the internet later i think - House chores to do now. *sigh*
Many thanks for the rom and the rest of your advice tho
Click to expand...
Click to collapse
If it was logical, I'd totally give you a full image, but the problem is that each device has its own serial number - if I give you an image of my device, then your device will have mine's serial number, which won't work out so well!
I'd love to keep trying to help you, though - Nook Touch related things are really my forte.
Let's start at the beginning - in your first post, you said that "you managed to mess up your GlowLight". What did you do to mess it up?
Is/was your Nook rooted?
Will your device boot and be used properly, but the GlowLight itself just doesn't work?
thenookieforlife3 said:
If it was logical, I'd totally give you a full image, but the problem is that each device has its own serial number - if I give you an image of my device, then your device will have mine's serial number, which won't work out so well!
I'd love to keep trying to help you, though - Nook Touch related things are really my forte.
Let's start at the beginning - in your first post, you said that "you managed to mess up your GlowLight". What did you do to mess it up?
Is/was your Nook rooted?
Will your device boot and be used properly, but the GlowLight itself just doesn't work?
Click to expand...
Click to collapse
Hi again, sorry for not getting back sooner - that damned thing called life always gets in the way
Yeah, it was rooted. I had used cwm and had adw running as a front end and had installed the screen lock bypass, but the bypass didnt work out so well - quite a bit of battery drain - even when left on a table(so no accidental waking up) - i tried to return it to stock - cant remember what i did tho - and now it just starts with the read forever screen and gets no further - it also seems that it doesnt power off and stays on till the battery is flattened. Trying to boot from the sd card using either nook manager or noogie works just fine tho.
I can see the partitions though minitool partition wizard and the Rom partition is "unallocated" there is also an unallocated space of 56mb at the end of the partitions.
I have tried recreating a fat32 rom partition and then copying the rom backup info from the factory partition, but no joy. For some reason, no partition software I have could create a fat32 partition directly on the nook, so I had to create one on the pc and then copy it over :-/
Thanks for the continued help btw
cortexbomber said:
Hi again, sorry for not getting back sooner - that damned thing called life always gets in the way
Yeah, it was rooted. I had used cwm and had adw running as a front end and had installed the screen lock bypass, but the bypass didnt work out so well - quite a bit of battery drain - even when left on a table(so no accidental waking up) - i tried to return it to stock - cant remember what i did tho - and now it just starts with the read forever screen and gets no further - it also seems that it doesnt power off and stays on till the battery is flattened. Trying to boot from the sd card using either nook manager or noogie works just fine tho.
I can see the partitions though minitool partition wizard and the Rom partition is "unallocated" there is also an unallocated space of 56mb at the end of the partitions.
I have tried recreating a fat32 rom partition and then copying the rom backup info from the factory partition, but no joy. For some reason, no partition software I have could create a fat32 partition directly on the nook, so I had to create one on the pc and then copy it over :-/
Thanks for the continued help btw
Click to expand...
Click to collapse
Are you interested in getting back the B&N functions? Because if not, then what I can do is back up my rooted GlowLight, factory wipe it back to 1.1.5, bypass Oobe (B&N registration), update to 1.2.1, and then make an image of that for you.
Beware, though, you won't be able to use any of the B&N functions if you want me to do that, because your device will have mine's serial number. But don't worry, it won't share anything except for that, so your device will be plenty usable.
thenookieforlife3 said:
Have you already tried booting into NookManager and restoring factory.zip?
Are you interested in getting back the B&N functions? Because if not, then what I can do is back up my rooted GlowLight, factory wipe it back to 1.1.5, bypass Oobe (B&N registration), update to 1.2.1, and then make an image of that for you.
Beware, though, you won't be able to use any of the B&N functions if you want me to do that, because your device will have mine's serial number. But don't worry, it won't share anything except for that, so your device will be plenty usable.
Click to expand...
Click to collapse
Yeah, i tried factory reset with nookmanager, but when I pressed the button to choose factory reset, it came up with the screen that showed the start of progress, but nothing else happened - even after several hours.
by b&n function i assume you mean the shop etc - cant say I'm worried about that bit, but if It will be back to stock, with just the stock software on, that would be cool. )
How would I transfer the complete image? I presume fire up noogie and partition wizard, wipe(err backup) all the partitions on my nook and then copy your partitions over?
cortexbomber said:
Yeah, i tried factory reset with nookmanager, but when I pressed the button to choose factory reset, it came up with the screen that showed the start of progress, but nothing else happened - even after several hours.
by b&n function i assume you mean the shop etc - cant say I'm worried about that bit, but if It will be back to stock, with just the stock software on, that would be cool. )
How would I transfer the complete image? I presume fire up noogie and partition wizard, wipe(err backup) all the partitions on my nook and then copy your partitions over?
Click to expand...
Click to collapse
It will be back to stock, but you won't be able to register with B&N and/or buy any books from them. The Social features also will not work.
If you're interested, I'll make that image for you. See the "back up you Nook" link in my signature for a guide on making and restoring Noogie images.
thenookieforlife3 said:
It will be back to stock, but you won't be able to register with B&N and/or buy any books from them. The Social features also will not work.
If you're interested, I'll make that image for you. See the "back up you Nook" link in my signature for a guide on making and restoring Noogie images.
Click to expand...
Click to collapse
Yep! Interested doesnt quite describe it tho More like biting your hand off
cortexbomber said:
Yep! Interested doesnt quite describe it tho More like biting your hand off
Click to expand...
Click to collapse
EDIT - See OverByter's post below, it has shown me that this wouldn't work out.
Try his method. I'll only give you an image of my device as a last resort.
Your image will also have your mac address besides the serial number, don't think that this is the way to go, basically he'll have an unworkable clone of your device. Why doesn't he use cwm to wipe the partition and then either adb push the rom or use a flashable image?
OB
Sent from my SPH-D710VMUB using Tapatalk 2
thenookieforlife3 said:
Ah. :laugh:
I'm kind of busy with school work right now, but I'll try to get it to you today.
Check for PMs from me in a few hours or so. :good:
Click to expand...
Click to collapse
Hehe. Absolutely no rush. I just appreciate the help.
cortexbomber said:
Hehe. Absolutely no rush. I just appreciate the help.
Click to expand...
Click to collapse
Okay, I may actually have solved your problem! Try the following steps - it's called the "eight interrupted boot" method.
1. I am expecting your Nook is still stuck at the "Read Forever" screen. If it's not, go ahead and turn your Nook all the way off.
2. Now, press the power button to take it to the "Read Forever" screen.
3. After it's there, press and hold the power button again to make the screen flash black and go back to the "Read Forever" screen.
4. Perform step 3 seven more times.
5. After the 8th interrupted boot, your Nook will restore itself to the factory image that it came with right out of the box.
6. Done!
Hope this works! :good: