Related
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
I tried to make a ROM, and it is not installing properly.:crying:
I data-resetted everything and formatted system, but this ROM is not installing correctly because I had removed some system apps and also added a few of them. But after a reboot I saw the system apps which I removed.
Please help me.
Thanks in advance
Noobwithabrickedsgy said:
I tried to make a ROM, and it is not installing properly.:crying:
I data-resetted everything and formatted system, but this ROM is not installing correctly because I had removed some system apps and also added a few of them. But after a reboot I saw the system apps which I removed.
Please help me.
Thanks in advance
Click to expand...
Click to collapse
Can you post updater script you are using under [ hide ] tags?
Was your /system mounted before you flashed your rom?
A Hero Can Be Anyone
Noobwithabrickedsgy said:
I tried to make a ROM, and it is not installing properly.:crying:
I data-resetted everything and formatted system, but this ROM is not installing correctly because I had removed some system apps and also added a few of them. But after a reboot I saw the system apps which I removed.
Please help me.
Thanks in advance
Click to expand...
Click to collapse
How did u make a rom??
Give the uodater scriot...
.................I Walk In Shadows...!..................
sanny5 said:
How did u make a rom??
Give the uodater scriot...
.................I Walk In Shadows...!..................
Click to expand...
Click to collapse
I made it without kitchen . I used a sample updater script given by hell_lock/prototype U.
Its attached.
I guess its some prob with my sd card cuz i could not install the same hyperion 7 which used to work before.
Could anyone test it???????
Here is my ROM-http://www.mediafire.com/download.php?3pk413hrcq1ze27
Here is my updater script-http://www.mediafire.com/download.php?paknyyfkebb6ybw
Noobwithabrickedsgy said:
I made it without kitchen . I used a sample updater script given by hell_lock/prototype U.
Its attached.
I guess its some prob with my sd card cuz i could not install the same hyperion 7 which used to work before.
Could anyone test it???????
Here is my ROM-http://www.mediafire.com/download.php?3pk413hrcq1ze27
Here is my updater script-http://www.mediafire.com/download.php?paknyyfkebb6ybw
Click to expand...
Click to collapse
first question, how did u make ur rom?
how did u make the zip file?
how are the files placed inside ur zip?
I think he just grab someone else's ROM and edited it as much as he wanted and then grab the Updater-script from Hell-lock and thinking "hey, this must be works!" and now, look the result. No one has success to make a Custom ROM without a kitchen (Editing the .zip).
If i helped you, Press the thanks button. don't say it
GermanyGSG said:
I think he just grab someone else's ROM and edited it as much as he wanted and then grab the Updater-script from Hell-lock and thinking "hey, this must be works!" and now, look the result. No one has success to make a Custom ROM without a kitchen (Editing the .zip).
If i helped you, Press the thanks button. don't say it
Click to expand...
Click to collapse
to be honest,
i never used kitchen to make my rom,
i had to code the updater script manually,
@OP.
you need to study the codes first and know what you are doing,
you can't build a house without proper procedures, same with ROM building,
you must learn to research and be patient when you fail,
it happens all the time,
in most instances the phone won't boot and what i always do is to go back and think over what went wrong and what must i do to resolve the issue,
we can help you as much as you can but please try to help yourself understand the situation a bit more.
deathnotice01 said:
to be honest,
i never used kitchen to make my rom,
i had to code the updater script manually,
@OP.
you need to study the codes first and know what you are doing,
you can't build a house without proper procedures, same with ROM building,
you must learn to research and be patient when you fail,
it happens all the time,
in most instances the phone won't boot and what i always do is to go back and think over what went wrong and what must i do to resolve the issue,
we can help you as much as you can but please try to help yourself understand the situation a bit more.
Click to expand...
Click to collapse
Thanks for motivating me. I know what is the problem now. I did not mount /system before flashing?. Added that to my script... All working fine now.
@GermanyGSG-
How the heck could you create ROMs before kitchen was made .. Eh? Its a matter of bash and edify... No kitchen needed.
Sent from my Nexus 7 using Tapatalk
Backup TA for Sony Xperia™ (Mac OS X version)
With this app you can backup and restore the TA partition of your device.
This can be useful, for example, when you want to unlock your bootloader and not lose your DRM keys and most importantly, your warranty. Before unlocking your bootloader, backup your TA with this app and you will be able to restore it to a factory state (locked bootloader, DRM keys intact, etc).
The app is based on TA Backup v9.10 by DevShaft (thanks !), which can be found here.
View attachment 2573685
Downloads
Frequently asked questions
Source code
Issues
Thanks a lot for bringing this to Mac OS X and make it open source as well! Will have a look at the source and your work at a later time.
Stuck on requesting root on the first try, successful in the second time.
stanley321 said:
Stuck on requesting root on the first try, successful in the second time.
Click to expand...
Click to collapse
Did SuperSU ask you to grant permissions to "shell" when it hanged ?
limiter121 said:
Did SuperSU ask you to grant permissions to "shell" when it hanged ?
Click to expand...
Click to collapse
I have granted SU permission to shell, so it won't prompt anyway.
The app is then not responding and I have to force close it.
stanley321 said:
I have granted SU permission to shell, so it won't prompt anyway.
The app is then not responding and I have to force close it.
Click to expand...
Click to collapse
Yeah, the app will appear to hang but it actually waits for adb to work it's magic.
Is there any chance you could send me a copy of the system log ?
To do so, open the Console app, enter "Backup TA" in the search field in the top right corner (to filter the logs) and make sure that "All Messages" is selected in the Log list (sidebar) on the left side of the window. At this point there should be lots of messages from Backup TA shown. You can now go to File -> Save a copy as... and send that file to me so I can look at what went wrong.
Thanks :fingers-crossed: !
limiter121 said:
Yeah, the app will appear to hang but it actually waits for adb to work it's magic.
Is there any chance you could send me a copy of the system log ?
To do so, open the Console app, enter "Backup TA" in the search field in the top right corner (to filter the logs) and make sure that "All Messages" is selected in the Log list (sidebar) on the left side of the window. At this point there should be lots of messages from Backup TA shown. You can now go to File -> Save a copy as... and send that file to me so I can look at what went wrong.
Thanks :fingers-crossed: !
Click to expand...
Click to collapse
Tried but nothing show up after the search!?
So I think it is just a case that I'm too hurry to check the app and closed it earlier than I should while it is working.
stanley321 said:
Tried but nothing show up after the search!?
So I think it is just a case that I'm too hurry to check the app and closed it earlier than I should while it is working.
Click to expand...
Click to collapse
Try selecting system.log in the sidebar and then search for Backup TA, it should work.
Anyway, I'll implement a better way to get logs from the app soon
limiter121 said:
Try selecting system.log in the sidebar and then search for Backup TA, it should work.
Anyway, I'll implement a better way to get logs from the app soon
Click to expand...
Click to collapse
I find it but can't get it up here...
We are sorry, your post was flagged by our system and was blocked from submitting. If you believe this was in error, please contact an admin to report this.
Looking at it, I think I just closed it too early. Nothing wrong with your part!
stanley321 said:
I find it but can't get it up here...
We are sorry, your post was flagged by our system and was blocked from submitting. If you believe this was in error, please contact an admin to report this.
Looking at it, I think I just closed it too early. Nothing wrong with your part!
Click to expand...
Click to collapse
Too bad about the log, but thanks a lot for testing and helping
limiter121 said:
Too bad about the log, but thanks a lot for testing and helping
Click to expand...
Click to collapse
Checking the timestamp, maybe you should add a message to ask the user to wait for at least a minute to prevent nervous users like me from closing it too early.
Sorry for being new to this TA thing, I don't know how long I should expect.
stanley321 said:
Checking the timestamp, maybe you should add a message to ask the user to wait for at least a minute to prevent nervous users like me from closing it too early.
Sorry for being new to this TA thing, I don't know how long I should expect.
Click to expand...
Click to collapse
No problem, will add it in the next version
Thanks for bringing this in a simple form to MacOS
Already backup up, but did another backup and did the test; all seemed well.
New version 1.1 (2) available !
Download it here.
Changelog :
Added better log handling. You can now see the log files using Help -> Open logs folder
UI does not lock (beachball) anymore during lengthy backup/restore operations
limiter121 said:
New version 1.1 (2) available !
Download it here.
Changelog :
Added better log handling. You can now see the log files using Help -> Open logs folder
UI does not lock (beachball) anymore during lengthy backup/restore operations
Click to expand...
Click to collapse
make it for linux please :angel:
thanks
imen27 said:
make it for linux please :angel:
thanks
Click to expand...
Click to collapse
I will take a look, but don't get your hopes up
limiter121 said:
I will take a look, but don't get your hopes up
Click to expand...
Click to collapse
sounds great,many thanks
New version available
New version 1.1.1 (3) available !
Download it here.
Changelog:
Enabled verbose logging (for tracking down issues)
Big update
New version 1.2 (4) available !
Download it here.
Changelog:
Added auto-update support
Improved reliability (by using bundled BusyBox commands)
Bug fixes
limiter121 said:
New version 1.2 (4) available !
Download it here.
Changelog:
Added auto-update support
Improved reliability (by using bundled BusyBox commands)
Bug fixes
Click to expand...
Click to collapse
Thanks, mate. I think it worked. Just one question: is it normal that a 2MB TA partition gets zipped into few KB? Something like 77KB. Are those sizes (for both TA partition and zip file) normal?
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:
Hi all,
I made this small update script because sometime when you try a rom and use a backup to restore the previous one the authentification get broken, so this script will just remove all locks and allow you to start your phone without any data lost.
I'm not responsible if something is going wrong.
Flash using any twrp will probably work.
great. will try
thanks!
animehq said:
Hi all,
I made this small update script because sometime when you try a rom and use a backup to restore the previous one the authentification get broken, so this script will just remove all locks and allow you to start your phone without any data lost.
I'm not responsible if something is going wrong.
Flash using any twrp will probably work.
Click to expand...
Click to collapse
well we can delete gatekeeper files manually from the TWRP file manager, and everything is fine, no data lost.
Great will try
c_/\/\_k said:
well we can delete gatekeeper files manually from the TWRP file manager, and everything is fine, no data lost.
Click to expand...
Click to collapse
Yep probably, but for most of people here it's safer to use a script than let them find the files manualy.
And maybe faster
animehq said:
Yep probably, but for most of people here it's safer to use a script than let them find the files manualy.
And maybe faster
Click to expand...
Click to collapse
you deserve compliment for your work , but it takes only one file to delete to remove passwords or lock. and its neither lengthy nor unsafe, i have seen your script, it deletes to many things.. which is not required i think. And your updater script has spelling mistakes too bro..
Does it also removes the mi account? Device locked because mi account think the device is stolen.
c_/\/\_k said:
you deserve compliment for your work , but it takes only one file to delete to remove passwords or lock. and its neither lengthy nor unsafe, i have seen your script, it deletes to many things.. which is not required i think. And your updater script has spelling mistakes too bro..
Click to expand...
Click to collapse
Which file do you think is the only one to delete?
Rohit DK said:
Does it also removes the mi account? Device locked because mi account think the device is stolen.
Click to expand...
Click to collapse
Nop sorry and there is no easy way to do it as far i know.
Bogeyof said:
Which file do you think is the only one to delete?
Click to expand...
Click to collapse
If its patternlock, then its gatekeeper.pattern.key, if its password then its gatekeeper.password.key, you can delete both.
Successful Using RX & Deletion of /data/validity/template.db
Doesn't work for me! Ran rx from recovery, wiped caches, & rebooted. Typed in backup password, unlocked (same as b4). Went to the Settings for fingerprint this time it constantly rejects any attempt saying too many incorrect pls wait. Prior it wouldn't take fingerprint or password.
Any suggestions for this?
PS: Would be nice to list what each file does /is for. I am also an advanced user...
After running This Rx use (root) X-plore/etc F. M. Then DELETE:
[*W/Rx SUCCESS*] /data/validity/template.db [*W/Rx SUCCESS*]
Reboot. Type in Previously Used BackUp Password. Go to Fingerprint Settings & setup new fingerprint & backup password!
[*MIA*] data/system/users/0/settings_fingerprint.xml [*MIA*] Could not find this file, so I assume not needed.
This was done on Stock Base Marshmallow ROM N915 (Note Edge).
BTW Thanks for RX & Could You Please add the above file to RX?