Related
Tis operation IS EASIEST AS you thinking about.
Just download this zip and make all by instruction:
1. Burn noogie.img [2] to microSD card (from 128Mb)with win32diskimager [1].
2. Turn off (10-20 second on power button) NOOK2E and plug in microSD with noogie.img.
3. Turn on NOOK2E
4. When Rooted Forever appear on screen - connect with cable to PC.
5. Wait for a wile.
6. Install Mini tools partition [3] (free).
7. Delete all partition from NOOK2E (Disk size - 1.82Gb)with Mini tools partition (first "Delete" - than "Apply" in top left corner).
8. Install Roadkil's Disk Image [4].
9. Run Roadkil's Disk Image select backup.img and burn on Nook (Physical Disk with 1,82Gb size)
10. After all - turn off NOOK, pull the noogie sd card from it.
Thanks for all who create root for Nook2E & forum.xda-developers.com.
P.S. NOOK image was made from CLEAR NOOK without registration.
Now working on changing s/n and mac. Need public key generator
Need help:
For now - find ./rom/devconf directory with lot of info:
for me are interesting 4:
DeviceID - same as S/N (on motherboard/on box)
MACAddress - as is (write on motherboard)
PublicKey - I don't know is this the same for all nooks or personal for each?
SerialNumber - the S/N as is (on motherboard/on box)
If change sn+id+mac - will work fine with new info.
But what about public key?
Waiting for you replays.
Find more - there are:
HashOfPrivateKey - some thing to use with PublicKey
ProductID - I don't know were to find
MainBoardSN - (write on motherboard)
Yep - there is 3 piece for making all works:
ProductID, HashOfPrivateKey, PublicKey
NEEED HELP
I'm trying to download this, but there are no seeds on the torrent. Any way you could hop back on and seed?
I can leave it seeding for a while after it's done.
So does this work or not ? I read somewhere that every nook has its own very personal default ROM. Since I didn't backup before rooting I suppose my own clean rom is gone, and I think it is impossible to do the other method which uses ADB wireless to do the 8 consecutive boots.
Can you host the file to another location, because it can not be downloaded.
Thanks.
vacano said:
So does this work or not ? I read somewhere that every nook has its own very personal default ROM. Since I didn't backup before rooting I suppose my own clean rom is gone, and I think it is impossible to do the other method which uses ADB wireless to do the 8 consecutive boots.
Can you host the file to another location, because it can not be downloaded.
Thanks.
Click to expand...
Click to collapse
The wireless ADB method worked for me. Much better than trying to 'catch' the boot 8 times in a row.
*first post on XDA, btw!
For me the ADB method didn't work. The process froze at the very end without completing the whole procedure. I got scared that I had f****d the device, but happily it booted again, but with the rooted shell.
Guess I will have to be stuck with the Rooted Forever
Hi,
Thanks very much for the instructions - I've managed to brick my NOOK and I'm desperate for help. But as others have mentioned, the file is no longer available. I cannot stress the amount of gratitude I'd have if you could possibly transfer the image to me via dropbox. I'm flying soon and really need my nook to work.
If you don't have dropbox, you can leave me some mail address and I'll invite you - you'll only have to copy & paste the file within your file system. If you do have dropbox - my mail is [email protected].
an image is nowhere to be found - please, please find it in your heart to transfer me your image.
alternatively, you can upload it to some file server and post it as a reply for the others in need of this file.
Thanks so very much in advance
Dan
I too screwed up and forgot to make a backup. I have acces to (and made a copy of) all the partitions I can view using a noogie bootable. On the factory partition, I noticed a zip file that has all the info for my nook (S/N, MAC address, etc...) in it. Is there any way you could try to put the backup img out, say with the files individual to each nook out, and instructions on where to replace them. Thanks
Warning: Do not use the image and method outlined in the first post!
It will replace data that are unique to _your_ Nook Touch, like your serial number and MAC address.
There are better options for restoring your Nook Touch, like this one.
Please let this thread die.
can you put direct download of (Just download this zip and make all by instruction):
I cant download it
Thanks
uuuuuuuuuuuuuuu hooooooooooooooooo
I am not responsible for any damage your nook suffers.
Officially supported by The Nooter Project for Nook Simple Touch
http://code.google.com/p/nooter/
MinimalTouch 1.1beta5
Information:
What it does:
Enables ADB via uRamdisk
Installs su and Superuser.apk
Installs Busybox and sqlite3
All zips install ADW launcher + NookColorTools + MinimalisticBlack theme + Minimalistic Text Widget + Button Savior with eink friendly skins.
Bugs:
Two step method (necessary to avoid the 1+ day wait time on market).
Future updates:(In order of priority)
Block automatic updates (Accidentally taken off on last update).
Officially make it compatible with 1.1.2
Check /system version and proceed install, if not force update to 1.1.2
Make a 1 step process.
Automatically backup and zip /factory to SDcard, to avoid having to make a full backup before rooting, and to use in conjunction with Touch-Formatter
Minimal zips install my stripped down repack of Gapps.
Fulltouch zips include the complete package of Gapps.
All W zips install ADB wireless Uramdisk.
All U zips install ADB USB Uramdisk + ADB widget to enable wireless adb at need.
All X zips include NookTouchTools + Xorzone's mods, for more details on this, read (http://forum.xda-developers.com/showthread.php?t=1289894).
All beta5 in conjunction with Unroot.zip include a way to backup and restore the original files modified by the rooting process, and delete all apps installed after rooting.
Unroot restores the original files modified and deletes all installed programs after or during the rooting process (only use with beta5).
Files that get Modified:
/boot/uRamdisk - enables ADB over wifi or usb
/system/build.prop - enables google check-in service and fakes signature, to enable protected apps on market
/data/system/packages.xml - enables Gapps to work correctly once installed
/system/framework/framework.jar - generates Android ID
/data/data/com.android.providers.settings/databases/settings.db - enables Non-Market Installs
Also on X files:
/system/framework/services.jar
/system/framework/android.policy.jar
User manual:
Things you will need before rooting:
Update your NST to 1.1 (http://nooter.googlecode.com/files/nook_1_1_update.zip)
CWM: Thread: http://forum.xda-developers.com/showthread.php?t=1360994
Direct download links:
http://forum.xda-developers.com/attachment.php?attachmentid=806435&d=1323121399
http://forum.xda-developers.com/attachment.php?attachmentid=806434&d=1323121315
Download it and burn it to an sd-card, (windows users use this to burn the image https://launchpad.net/win32-image-writer/+download)
(If the last version dosn't work, try the first).
You must have an external microSDCard reader to burn CWM, not the NST.
Understand the button layout of CWM:
Both Buttons on the left: BACK
Upper button on the right: UP
Lower button on the right: DOWN
n button: SELECT
Power button: TOGGLE DISPLAY
Download 2 zips from one of the different releases listed underneath:You can choose what first part to use on each folder, which can be the original MinimalTouch (coreGapps+launcher,etc), or the Fulltouch(fullGapps+launcher,etc).
The second part zip is obligatory.
Select the package version to use:
NW files include Normal + adb Wifi zips.
(Download one of the "START" zips and the "END" one).
NWFullTouchPART-1-START
NWMinimalTouch-PART-1-START.zip
XWU-NWU-MFTouch-PART-2-END-1.zip
NU files include Normal + adb Usb zips.
(Download one of the "START" zips and the "END" one).
NUFullTouch-PART-1-START.zip
NUMinimalTouch-PART-1-START.zip
XWU-NWU-MFTouch-PART-2-END-1.zip
XW files include Normal + Xorzone's mods + adb Wifi zips.
(Download one of the "START" zips and the "END" one).
XWFullTouch-PART-1-START
XWMinimalTouch-PART-1-START
XWU-NWU-MFTouch-PART-2-END-1.zip
XU files include Normal + Xorzone's mods + adb Usb zips.
(Download one of the "START" zips and the "END" one).
XUFullTouch-PART-1-START
XUMinimalTouch-PART-1-START
XWU-NWU-MFTouch-PART-2-END-1.zip
beta5 folder has the most popular zips above, with an extra security layer for those who forget to make a backup. Beta5 backups all the used files to /data/backup.
(Download one of the "START" zips and the "END" one).
beta5-2 XUFullTouch-PART-1-START
beta5-2 XWFullTouch-PART-1-START
beta5-1 XWUMFTouch-PART-2-END
Unroot(only for beta5) You can revert back to the original state by flashing Deletebeta5-1.zip through CWM, let it run then pull the SD and reboot. Beta5 files also have the progress bar fixed.(testing)
beta5-4Unroot
Installing instructions:
Copy the zips onto the root directory of the sdcard you burned the CWM.(Don't extract them)
Insert the sdcard on your nook, and boot it.
On CWM select Choose install from zip, choose zip from sdcard, MinimalTouch-PART-1-START.zip, click yes and wait 1+ minute, (or FullTouch-PART-1-START.zip)
Go back, eject the sd card, and click reboot.
If you selected the extended package with Touchnooter apps:
At the Android Welcome Screen skip Sign In
Enable Location Services when given the option.
Select ADW launcher as default.
Log in on YouTube, by clicking options, my channel, add acount, use a complete Gmail account not just the username, accept the messages, open Gmail but dont add any account to it, just click options and force sync it, force sync it until it fails to sync and closes (FC), it may take some tryes and time, dont desist, then open market and it will fail to sync, DO IT, dont skip this steps as they are necessary for building correctly the databases.
Easy steps from here on.
Shut down your Nook.
Insert the sdcard on your nook, and boot it.
On CWM select Choose install from zip, choose zip from sdcard, MinimalTouch-PART-2-END.zip, click yes and wait.
Go back remove the SD-card, reboot.
The system will load, open Gmail let it sync, wait a bit, if it dosn't, force it to sync, it will work.
Open market, accept policies, and you are ready to go .
File list:
All the available files are listed here:
http://code.google.com/p/nooter/downloads/list
or
http://bit.ly/uqxM99
Index
Automatic Methods:
[NST]MinimalTouch 1.1beta5
[NST]Touch-Formatter
Manual Tutos:
Skip registration (OOBE)
Making the manual process LESS PAINFULL
Setting up adb manually on the nook touch
Setting up root access on NST through adb and installing busybox
Improve battery life(testing)
Backup bookmarks and annotations(testing)
Enable non market app installs
Installing XorZone's B&N button modifier
Change the powered off screen image
Blocking OTA updates
Installing new fonts for your nook (testing)
Installing Gapps (+launcher, etc)
Totally uninstall Gapps (my repack), unrooting, erasing and restoring
Interesting or useful specific apps or hacks for Nook Simple Touch
nook 1.1 update
Thanks to:
GabrialDestruir for his hard work, making easy to root the NST creating the Touchnooter (http://forum.xda-developers.com/showthread.php?t=1343143) (http://forum.xda-developers.com/showthread.php?t=1132693)
ros87 for the update on uramdisk and the how to modify boot/charging images and usb drivers. (http://forum.xda-developers.com/showthread.php?t=1337653) (http://forum.xda-developers.com/showpost.php?p=17882146&postcount=11) (http://forum.xda-developers.com/showpost.php?p=19342931&postcount=12)
XorZone for NookTouchTools and his jars, book button menu and the orientation Switch (http://forum.xda-developers.com/showthread.php?t=1289894)
nookdevs for noogie and making all this possible (http://nookdevs.com/NookColor_Rooting)
mali100 for the update on framework. (http://forum.xda-developers.com/showpost.php?p=19201466&postcount=352)
xboxexpert for the working market. (http://forum.xda-developers.com/showpost.php?p=15084704&postcount=51)
Kralik for his findings. (http://www.mobileread.com/forums/showthread.php?t=156539)
jerryfan2000 for Button savior (http://forum.xda-developers.com/showthread.php?t=865525)
OMGWTF_BBQ for the Button Savior eink friendly mod (http://forum.xda-developers.com/showthread.php?t=1250278)
met67 for the permissions and ownership on Gapps (http://forum.xda-developers.com/showpost.php?p=19658259&postcount=109)
mali100 for portin CWM to NST (http://forum.xda-developers.com/showthread.php?t=1360994)
salsichad2 for pointing out that the X files where corrupt and his adw theme config (http://forum.xda-developers.com/showpost.php?p=19720053&postcount=139)
kneeldug for sugesting extra steps on the automatic tuto.
bisbal for helping me beta test.
dobbing for the copy of the 1.1 update.
Hi,
thanks for the guide. I have a dumb question. Could you please provide the correct sqlite3 url to use for the download?
Thanks.
Eded,
All I can say is that I am truly sorry. The nooter didn't work because I was dumb enough not to read instructions properly. Now I added the uramdisk to the nooter/boot directory, not root directory!!!!!!!!!!!
Now it worked, and I restored the apps I downloaded with titanium backup pro.
Thing is: market (with vending.apk installed over original market) doesn't reach the server properly when I press "my apps", and I am still not able to find my device on the android market in my computer.
On the rest, it works! Thanks for everyone who gave tips!!!
I already rooted my nook with touchnooter for 1.1 can I use the instructions to just install market or do I have to start from scratch.
Dopedangel said:
I already rooted my nook with touchnooter for 1.1 can I use the instructions to just install market or do I have to start from scratch.
Click to expand...
Click to collapse
You have no need to start from scratch
You can use this method to install gapps.
Just remember to delete the other apps as launcher, etc, that you have allready installed from the package I posted.
apeine said:
Eded,
All I can say is that I am truly sorry. The nooter didn't work because I was dumb enough not to read instructions properly. Now I added the uramdisk to the nooter/boot directory, not root directory!!!!!!!!!!!
Now it worked, and I restored the apps I downloaded with titanium backup pro.
Thing is: market (with vending.apk installed over original market) doesn't reach the server properly when I press "my apps", and I am still not able to find my device on the android market in my computer.
On the rest, it works! Thanks for everyone who gave tips!!!
Click to expand...
Click to collapse
Dont worry, **** happens It's easy to mess up if you are in a hurry, it happens to me alot.
Can you still search and install from market, even if it dosnt appear en the pc?
beber75 said:
Hi,
thanks for the guide. I have a dumb question. Could you please provide the correct sqlite3 url to use for the download?
Thanks.
Click to expand...
Click to collapse
I will when I get home.
Is it possible to modify the partition to enlarge the 250mb partition? I heard that 750 mb is reserved to b&n contents and i find it a waste of space.
user4242 said:
Is it possible to modify the partition to enlarge the 250mb partition? I heard that 750 mb is reserved to b&n contents and i find it a waste of space.
Click to expand...
Click to collapse
Not sure what you mean?
Nook partition (6) is 252MB and Data partition (8) is 841MB
There's no partition "reserved" for B&N contents, it uses both and so can you.
Code:
Number Start End Size Type File system Flags
1 16.4kB 79.7MB 79.7MB primary fat32 boot, lba
2 79.7MB 96.5MB 16.8MB primary fat32 lba
3 96.5MB 296MB 199MB primary ext2
4 296MB 1942MB 1646MB extended
5 296MB 598MB 302MB logical ext2
6 598MB 849MB 252MB logical fat16 lba
7 849MB 1101MB 252MB logical ext3
8 1101MB 1942MB 841MB logical ext3
Yes but i can't put my files on the b&n reserved partition.
So if i want to put only my contents on the nook i have only 250 mb.
Right?
user4242 said:
Yes but i can't put my files on the b&n reserved partition.
So if i want to put only my contents on the nook i have only 250 mb.
Right?
Click to expand...
Click to collapse
Sure you can, but only the Nook partition is auto mounted trough USB.
If you want to put files in /data/media you can use adb or some filemanager app.
thanks Ros87, thats just another reason to nooter my NST.
I'm still on 1.0 and my plan is to:
1. backup 1.0 with the help of the link in your sig.
2. upgrade to 1.1. from B&N servers
3. Follow the guide in this thread and nooter it manually...
Smart? or do you have any tips for me?
Thanks a lot for the root.
Just got my nook touch and I'm eager to root it.
Quick question, what's the difference between this root and touchnooter.
Thanks.
dark_hawk said:
Quick question, what's the difference between this root and touchnooter.
Click to expand...
Click to collapse
This root is manual bút it adds android Market. Touchnooter does this all with a script, so its automatic BUT it doesnt add Android Market because it can't.
tomic22 said:
This root is manual bút it adds android Market. Touchnooter does this all with a script, so its automatic BUT it doesnt add Android Market because it can't.
Click to expand...
Click to collapse
Can you use touchnooter to root and then use the part of this guide to add market and apps?
Can you use touchnooter to root and then use the part of this guide to add market and apps?
Click to expand...
Click to collapse
Of course
user4242 said:
Yes but i can't put my files on the b&n reserved partition.
So if i want to put only my contents on the nook i have only 250 mb.
Right?
Click to expand...
Click to collapse
If you still want to resize the Nook partition, here's a Linux way:
As always, make sure you backup your Nook before fiddling with stuff like this
Prerequisites:
1: NST booted with Noogie
2: USB attached and recognized in Linux (usually /dev/sdb)
Make a copy of Nook and Data files (ignore socket warnings)
Code:
#mkdir tmpnook tmpdata
#mount /dev/sdb6 tmpnook
#mount /dev/sdb8 tmpdata
#tar cf tmpnook.tar tmpnook
#tar cf tmpdata.tar tmpdata
#umount tmpnook
#umount tmpdata
Delete existing and create new partitions:
Code:
# fdisk /dev/sdb
Command (m for help): d
Partition number (1-8): 8
Command (m for help): d
Partition number (1-7): 7
Command (m for help): d
Partition number (1-6): 6
Command (m for help): n
First cylinder (286-926, default 286):
Using default value 286
Last cylinder, +cylinders or +size{K,M,G} (286-926, default 926): +840M
Command (m for help): n
First cylinder (707-926, default 707):
Using default value 707
Last cylinder, +cylinders or +size{K,M,G} (707-926, default 926): +252M
Command (m for help): n
First cylinder (834-926, default 834):
Using default value 834
Last cylinder, +cylinders or +size{K,M,G} (834-926, default 926):
Using default value 926
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
Syncing disks.
Create filesystems:
Code:
# mkfs.vfat -F 16 -n Nook /dev/sdb6
# mkfs.ext3 /dev/sdb7
# mkfs.ext3 /dev/sdb8
Write back your data:
Code:
# mount /dev/sdb6 tmpnook
# mount /dev/sdb8 tmpdata
# tar xf tmpdata.tar tmpdata
# tar xf tmpnook.tar tmpnook
tar: tmpnook: implausibly old time stamp 1970-01-01 01:00:00 (just ignore)
# umount tmpnook
# umount tmpdata
Remove sdcard and reboot
Eded,
Even though I am unable to download through my computer, I can perfectly download from Nook. A few weeks ago, I lost that capacity on 1.0.1, and that is why I was so interested in running the 1.1.0 rooted.
Once again, thank you all (Gabrial, Eded, Xorzone - great nooktouchtools comeback, Ros, and everyone else that helped me).
eded333 said:
[*]When the NST reboots select go launcher as your predefined launcher, skip google registration and try first to open and register on Youtube (Youtube may fail, dont worry) then GMail and then Market, if Gmail fails, dont panic, reboot and try again, dont start all the proces agian, just power cycle, allways use the same google account.
Click to expand...
Click to collapse
I was able to register on YouTube, but I keep getting the register your google account screens with both Gmail and Market over and over again. I've rebooted and tried registering about a dozen times, no success.
I followed directions exactly, could there be something I'm missing?
Hi,
If I well remember, this is a know issue I already faced off on my notion ink adam. You have to delete your registered account in your settings.
Power off then power on again your device.
Register again.
beber75 said:
Hi,
If I well remember, this is a know issue I already faced off on my notion ink adam. You have to delete your registered account in your settings.
Power off then power on again your device.
Register again.
Click to expand...
Click to collapse
Thank you for the suggestion. I tried to do this but got a message "Barnes and Noble failed to deregister device" or something. Then I tried to return to the launcher and my Button savior failed.
Restoring with nookRestore.img and starting from scratch.
This is real Windows 8 bootable on USB not setup.
Is't Windows 7 script modified by me.
Its require 8go Stick minimum :
Unzip it in Desktop
Format your Stick NTFS 512KB (faster)
Right clic on installer.cmd run as administrator
Then follow instruction
Exemple if your stick is E: then you need to choose E: 2 times in asking. No C: !!!
After you get desktop dont forget change your usb drive to write-cache enable on device manager > disk drive.
https://rapidshare.com/files/1872298681/Win2USB.zip
Do you have another link or can you email me the Win2USB.zip file? The download link provided isn't working. My email is [email protected]
Thanks,
Ken
kendick01 said:
Do you have another link or can you email me the Win2USB.zip file? The download link provided isn't working. My email is [email protected]
Thanks,
Ken
Click to expand...
Click to collapse
Ive tested now its work verry well
Tigrouzen said:
This is real Windows 8 bootable on USB not setup.
Is't Windows 7 script modified by me.
Its require 8go Stick minimum :
Unzip it in Desktop
Format your Stick NTFS 512KB (faster)
Right clic on installer.cmd run as administrator
Then follow instruction
Exemple if your stick is E: then you need to choose E: 2 times in asking. No C: !!!
After you get desktop dont forget change your usb drive to write-cache enable on device manager > disk drive.
https://rapidshare.com/files/1872298681/Win2USB.zip
Click to expand...
Click to collapse
Hi there.
Looking into this, need your guide.
Wanting to ask you, what is the drive letter for boot partition to choose?
Wondering if it is C or the USB Drive letter?
CHECK IF THIS IS CORRECT PLEASE:::
Path of your Win file: "I:\Sources\install.wim"
The index number: 1
Drive letter for OS partition: h:
Drive letter for boot partition: c:
USB hard disk or not: YES
The above info correct???
PEACE!!!
Hi, I installed Windows 8.1 Preview on my ARM tablet. before installing it I created a recovery USB drive as I thought I would hate Windows 8.1 and want to go back to 8.0.
So I did but before recovering I had the stupidest idea to wipe clean the disk.
there were 3 partitions in it before:
• recovery (around 300mb)
• EFI (I don't remember its size)
• C: (around 54, 55GB).
I can still get access to the blue screen with the big buttons. in Troubleshoot, "Reset your PC" won't work. it gives me a message saying "Unable to reset your PC. A required drive partition is missing"
I still have access to command line and could recreate the partitions but I don't know what would be the correct sizes and file systems for EFI and Recovery. and even if I did I have a feeling that just creating the partitions might not make much difference.
Any ideas, please?
VIDEO: http://youtu.be/KdDLy23CAGk
You cant restore from your USB? In troubleshoot, "reset your PC" tries to reset it from the internal recovery partition, not an external one. There would be a different option for that.
Sent from my SCH-I535 using xda app-developers app
jtg007 said:
You cant restore from your USB? In troubleshoot, "reset your PC" tries to reset it from the internal recovery partition, not an external one. There would be a different option for that.
Click to expand...
Click to collapse
no, buddy... that's what I assumed it would happen before wiping the disk.
once I'm in I get the blue screen where I pick the keyboard layout then the second screen has two buttons "Troubleshoot" and "Turn off your PC". In "Troubleshoot" I have "Refresh your PC", "Reset your PC" and "Advanced Options". In "Advanced Options" I have "Automatic Repair" and "Command Prompt".
none of these options do anything even though I can see the recovery drive is being accessed.
If you have a full (~3 GB) recovery image on USB, boot your system from USB and it should be able to restore.
With the USB stick plugged in and the Surface off, hold the "volume down" button and press and release the power-on button. Hold down "volume down" until you see the Surface logo. It will take a while, since it's loading from USB. Once you get to *that* menu, do a reset. When it asks, make sure that you choose to repartition your drives. Don't do the full wipe option--that'll take forever. Just use the "delete my files" or whatever button.
You can know that it's the 8.0 recovery image rather than 8.1 because it will ask for your language before asking for your keyboard layout. (This is because RT 8.1 preview was only released in English. It'll likely change for final.)
Myriachan said:
If you have a full (~3 GB) recovery image on USB, boot your system from USB and it should be able to restore.
With the USB stick plugged in and the Surface off, hold the "volume down" button and press and release the power-on button. Hold down "volume down" until you see the Surface logo. It will take a while, since it's loading from USB. Once you get to *that* menu, do a reset. When it asks, make sure that you choose to repartition your drives. Don't do the full wipe option--that'll take forever. Just use the "delete my files" or whatever button.
You can know that it's the 8.0 recovery image rather than 8.1 because it will ask for your language before asking for your keyboard layout. (This is because RT 8.1 preview was only released in English. It'll likely change for final.)
Click to expand...
Click to collapse
yep... I tried that. check this video. it shows exactly what is going on.
http://youtu.be/KdDLy23CAGk
try destroy your os partition first.rebuild or format it.
windowsrtc said:
try destroy your os partition first.rebuild or format it.
Click to expand...
Click to collapse
the disk has been wiped clean. I have created the partitions manually. it didn't make any difference.
Try this CMD script. Thanks go to a person in the original "windows RT unlocking" thread, he've uploaded his recovery taken from a developer-unlocked device. Unfortunately I don't remember his nick
Code:
rem These commands are used with DiskPart to
rem erase the drive and create five partitions
rem for a UEFI/GPT-based computer.
rem Adjust the partition sizes to fill the drive as necessary.
convert gpt
rem === 1. Windows RE tools partition ===========
create partition primary size=350
format quick fs=ntfs label="WinRE"
set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"
assign letter="T"
gpt attributes=0x8000000000000001
rem === 2. System partition =====================
create partition efi size=200
rem *** NOTE: For 4KB-per-sector drives, change this value to 260
format quick fs=fat32 label="System"
assign letter="S"
rem === 3. Microsoft Reserved (MSR) partition ===
create partition msr size=128
rem === 4. Windows partition ====================
rem == a. Create Windows partition ===========
create partition primary
rem == b. Create space for recovery image ====
shrink minimum=3600
rem == c. Prepare the Windows partition ======
format quick fs=ntfs label="Windows"
assign letter="W"
rem === 5. Recovery image partition =============
create partition primary
format quick fs=ntfs label="Recovery Image"
set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"
assign letter="R"
gpt attributes=0x8000000000000001
exit
You should create a CMD file (say, "CreatePartitions-UEFI.cmd"), put it into the root dir of your recovery USB and boot into the command-line mode. Then run it from CMD.
Of cause you can modify the script as you like - for example as you already have the pratitions created, you may need only to use "gpt attributes" commands.
And don't forget that the boot partition (the EFI partition that contains bootmgr.efi file) should be FAT32, not NTFS.
After the script finished - disk W: would be your Windows partition. You should try to extract the recovery WIM file there:
Code:
Dism /apply-image /imagefile:U:\sources\Install.Wim /index:1 /ApplyDir:W:\
U: here is a drive letter of your recovery USB. I think that it should be D: or E:. You can determine it with the "list vol" command in diskpart.
S: is your EFI partition. You may need to copy the \EFI subdirectory from your recovery USB to S:\EFI dir and then use BCDEDIT tool to recreate boot entries. read technet or more info, for example here: http://technet.microsoft.com/en-us/library/hh265131(v=ws.10).aspx
P.S. I have not tried this script myself - but it looks like being correct. For more info look here: http://technet.microsoft.com/en-us/library/hh825686.aspx and here: http://technet.microsoft.com/en-us/library/hh825221.aspx
mamaich said:
Try this CMD script. Thanks go to a person in the original "windows RT unlocking" thread, he've uploaded his recovery taken from a developer-unlocked device. Unfortunately I don't remember his nick
Click to expand...
Click to collapse
fella... you are a star, an angel.
you saved me from sending the tablet to Czech Republic to do what took me 20 minutes.
I really, really, really appreciate it. the damn thing is working again.
:laugh::laugh::laugh:
Although not completely related to this thread...
I have trouble with restoring from USB on 8.1, though 8.0 works fine. When restored from USB instead of upgraded from 8.0, the OS goes into a mode where the desktop is always black and won't let you change it. This is due to Windows not having a valid product key.
I did some registry trickery to retrieve my 8.0 product key. =) Basically, I copied the Windows NT\CurrentVersion to my Windows 8 PC as a different name, then hacked an existing product key retrieval program to use that name. It seemed to work; it gave a key that my RT accepts.
Myriachan said:
Although not completely related to this thread...
I have trouble with restoring from USB on 8.1, though 8.0 works fine. When restored from USB instead of upgraded from 8.0, the OS goes into a mode where the desktop is always black and won't let you change it. This is due to Windows not having a valid product key.
I did some registry trickery to retrieve my 8.0 product key. =) Basically, I copied the Windows NT\CurrentVersion to my Windows 8 PC as a different name, then hacked an existing product key retrieval program to use that name. It seemed to work; it gave a key that my RT accepts.
Click to expand...
Click to collapse
I would just wipe clean the hard drive with diskpart.
the steps our friend posted worked for me but I ignored the parts it refers to a Windows RE Tools partition. also I used 4000 instead of 3600 for the Recovery Partition.
after the
Code:
Dism /apply-image /imagefile:U:\sources\Install.Wim /index:1 /ApplyDir:W:\
step (which is lengthy as it rebuilds the entire windows partition) copy the boot files to the EFI partition from the newly rebuilt Windows partition with
Code:
bcdboot W:\Windows
and finally set the location of the Windows partition with
Code:
W:\Windows\System32\reagentc /setosimage /path R: /target W:\Windows /index 1
and you're done. don't bother with drive letters and visible drives as they'll sort themselves out when Windows launches for the first time.
I am having the same exact issue after formatting my Samsung XE700T and then trying to restore my laptop with a recovery usb
Can someone please give me a hand with this process, I have tried the script but it isn't working, so I am wondering what I am doing wrong.
A more simple explanation for someone who isn't use to using CMD would be great
Thank you
iSlaker said:
I would just wipe clean the hard drive with diskpart.
the steps our friend posted worked for me but I ignored the parts it refers to a Windows RE Tools partition. also I used 4000 instead of 3600 for the Recovery Partition.
after the
Code:
Dism /apply-image /imagefile:U:\sources\Install.Wim /index:1 /ApplyDir:W:\
step (which is lengthy as it rebuilds the entire windows partition) copy the boot files to the EFI partition from the newly rebuilt Windows partition with
Code:
bcdboot W:\Windows
and finally set the location of the Windows partition with
Code:
W:\Windows\System32\reagentc /setosimage /path R: /target W:\Windows /index 1
and you're done. don't bother with drive letters and visible drives as they'll sort themselves out when Windows launches for the first time.
Click to expand...
Click to collapse
hI! at the last step you mentioned with setting location of windows partition, i got this error:
"reagentc.exe the recovery image file cannot be placed in the root directory of a volume"
any ideas?
iSlaker said:
I would just wipe clean the hard drive with diskpart.
the steps our friend posted worked for me but I ignored the parts it refers to a Windows RE Tools partition. also I used 4000 instead of 3600 for the Recovery Partition.
after the
Code:
Dism /apply-image /imagefile:U:\sources\Install.Wim /index:1 /ApplyDir:W:\
step (which is lengthy as it rebuilds the entire windows partition) copy the boot files to the EFI partition from the newly rebuilt Windows partition with
Code:
bcdboot W:\Windows
and finally set the location of the Windows partition with
Code:
W:\Windows\System32\reagentc /setosimage /path R: /target W:\Windows /index 1
and you're done. don't bother with drive letters and visible drives as they'll sort themselves out when Windows launches for the first time.
Click to expand...
Click to collapse
also, did you have to do anything with the S: efi partition?
Yze said:
hI! at the last step you mentioned with setting location of windows partition, i got this error:
"reagentc.exe the recovery image file cannot be placed in the root directory of a volume"
any ideas?
Click to expand...
Click to collapse
Same error ... no news ?
studio37 said:
Same error ... no news ?
Click to expand...
Click to collapse
Ok, before the last command line I create new directory on R:
mkdir r:\osimage
and finally :
W:\Windows\System32\reagentc /setosimage /path R:\osimage /target W:\Windows /index 1
Thanks to all on this thread...!!!
I was able to completely re-format and downgrade to Win RT 8.0.
Fantastic !!
chappatti said:
Thanks to all on this thread...!!!
I was able to completely re-format and downgrade to Win RT 8.0.
Fantastic !!
Click to expand...
Click to collapse
How? Please write for me a full instruction how you downgrade it? Or video. Thanks!
P.S. sorry for my bad English.:highfive:
ayuda please
hola necesito ayudaa mi me sale ese error k se faata particion para poder recuperra mi tablet ..... me podrias poner paso por paso como lo hiciste soy novato en esto y me sale muy caro mandarlo a servicio tecnico gracias
Take a look at this link for info: eightforums.com/installation-setup/44021-need-help-reinstalling-windonws-8-usb-2.html#post368623
Greets all,
Apologies in advance for the longer post.
TLDR: Writing the debrick-n910p.img image to SDcard using Windows (10 x86_64) for me caused my hard bricked SM-N910P / Sprint Samsung Galaxy Note 4 to endlessly boot-loop (displaying BOOT RECOVERY MODE / CHECK BOOT PARTITIONS.. / COPY FROM T-FLASH.. / BOOT RECOVERY / WRITE 188416 sectors / REBOOT). I found my solution for this issue to be that as long as I wrote the debrick-n910p.img image in Windows (10 x86_64), then booted into Linux and wiped the GPT data structures on the SDcard only to convert the SDcard to basic MBR (+DOS compatible flag), then created & formatted a single 32GB partition as FAT32, then and only then, write the debrick-n910p.img image file to the SDcard in this way, I was able to save my hard-bricked phone flawlessly!
I ran into the "mmc_read failed" issue that many posters to this site have experienced. I wanted to add the solution that worked for me along with the issues I ran into, as a reference for myself if I ever need it again in the future, and to pass on the information in the event others may find it helpful.
In all my trials and research I never found a point-by-point / exact instructions for the SM-N910P / Sprint Samsung Galaxy Note 4, nor anyone running into the same issue(s) that I did. that's what this post is => links to others solutions, my experience, and my solution for a hard-bricked SM-N910P / Sprint Samsung Galaxy Note 4.
SCENARIO: After ~6months of owning my phone I bought from craigslist it started experiencing random lagging, then random reboots, and ultimately the phone failed to boot into the OS one day. So I booted up TWRP, did a full-wipe and fresh OS load. after the OS flash (like I've done a million times, nothing different/strange) the device was set to reboot, then the screen went dark, and never came back on. just poof. it would flat-out not boot again; no LED during charging, nothing would happen when attempting to power on the phone, or any attempt to try booting recovery (Home+Vol-Up+Power) or to Odin/Kies download-mode (Home+Vol-Down+Power). To me the phone was dead, I considered it the "true brick". Yet, I wondered at the most curious thing that would happen when I connected the phone to my computer via the microUSB cable without the battery; I would hear the "new device attached" Windows chime, and Device Manager would list a new "Qualcomm HS-USB QDLoader 9008" device. otherwise, the phone remained dark, and completely void of any life.
At this point I started researching to purchase a replacement cellphone when a website caught my eye with the title "Qualcomm Snapdragon Unbrick Guide, Snapdragon’s are UNBRICKABLE".
I skimmed over the text, and began thinking it possible to revive my (broken?) phone - I just desired a straight-forward HOWTO describing the procedure how I could resurrect my phone, and I figured I would be on my way.
In the end, I found some promising posts, and the very SM-N910P debrick image itself (see below for links), but never found a step-by-step for my exact model of phone.
N910P Debrick Image + Useful Links
Mega Link to the N910P debrick image (128MB)
Samsung N910P Galaxy Note 4 Sprint USA Repair Firmware (N910PVPU4COG5_SPT4COG5_Sprint_USA_v5.1.1_Repair_Firmware.zip)
Win32DiskImager (Project Homepage) (v0.9 binary)
dd for windows
Galaxy Note 4 Unbrick/Debrick.img for N910G/F/T/W8 [unbrick] [unbrick image]
[*]- Inside, a reference For N910P refer this thread
Galaxy Note 4 N910T FIXED HARD BRICKED
SM-N910P (US-Sprint) debrick.img
All instructions seemed to state I needed a 16GB or larger SDcard, so I went out and purchased a brand new 128GB MicroSDXC card, specifically Samsung MicroSDXC EVO Memory Card w/ Adapter 128GB (2017 Model) - Model: MB-MP128G / Model Code: MB-MP128GA/AM
The gist of all the reports on how to fix my issue was to write the N910P debrick image to a micro SDcard and magically the phone would come back to life. And so, I did just that. In my case using Windows 10 x86_64 - using the suggested applications to write the image to the SDcard: Win32DiskImager and/or dd for windows, then popping the SDcard into the "dead" phone, attaching the battery to the phone and pushing power - or one of the 3 finger salutes (recovery/download-mode) - then the magic would happen, the screen would show the following text:
Code:
BOOT RECOVERY MODE
CHECK BOOT PARTITIONS..
COPY FROM T-FLASH..
BOOT RECOVERY
WRITE 188416 sectors
REBOOT
But, unfortunately for me, that is all it would do, I would keep seeing that text over and over... If I let the "COPY FROM T-FLASH.." appear then press one of the 3 finger salutes (recovery -or- download-mode), the phone would just reboot before it displayed the rest, and continue back in it's loop:
Code:
BOOT RECOVERY MODE
CHECK BOOT PARTITIONS..
COPY FROM T-FLASH..
BOOT RECOVERY
WRITE 188416 sectors
REBOOT
This just kept occurring over, and over with infinite reboots. Yet, ALL the documentation said it would ultimately boot into download-mode, I just had to "put it in the freezer to let the phone cool" (never mind that the phone wasn't hot AT ALL) for an hour or something similar?? All my searching found nobody else with this issue (at least no one reporting it). So I am reporting it and also reporting how I fixed my sorry state of affairs.
As I noted above, I was using Windows 10 x86_64 as the OS and Win32DiskImager, as well as dd for windows, to write the debrick image to the SDcard up to this point. This was my process:
:: Windows 10 ::
place SDCARD in drive
format the SDCARD (drive d:/f:, whichever) through Windows Explorer (explorer.exe) via RIGHT-CLICK on drive -> Format ...
capacity 119GB / Filesystem: exFAT / Allocation Size: drop-down = Default Allocatio-- n Size
CHECK Quick Format
click Start button
click OK
click OK when finished
click Close button
in Windows Explorer (explorer.exe), RIGHT-CLICK on SDCARD drive -> Eject
eject SDCARD from computer
- EITHER Win32DiskImager OR dd for windows, only do 1.
:: Win32DiskImager ::
run Win32DiskImager as Administrator
DEVICE = drive of the SDCARD (D:/F:, whichever)
IMAGE FILE = click FOLDER icon, select "debrick-n910p.img"
click WRITE button
click OK
at Write Successful = click OK
more then likely (win10) a ****-ton of Explorer screens pop up, with errors like "You need to format the disk in Drive ? before you can use it" pops up
IGNORE ALL THIS, ALT-F4 to close ALL the pop-ups and errors
OR just REBOOT, as at this point we are done
Shutdown Windows (10) -> REBOOT
:: dd for windows ::
open "cmd" as Administrator
dd --list
dd if=debrick-n910p.img of=\\.\Volume{3fde94fa-d22d-11e7-b791-806e6f6e6963} bs=1M
Once the debrick-n910p.img file is finished being written to the SDcard, 27 partitions (what appears to be mostly duplicate) will show up and all drive letters will get filled, being displayed as mostly unreadable, that is just the nature of what the debrick image is.
My Solution to this situation was as follows:
:: LINUX ::
boot linux from USB -or- CD (I booted a handy USB stick with Qubes OS v4-rc3, choose Troubleshooting -> Rescue a Qubes System)
upon boot, choose "3" to be dropped to shell
mount windows folder that holds the debrick N910P image = mount /dev/sda2 /mnt/sysimage
place SDCARD in drive
fdisk -l << make sure your SDcard shows up (/dev/mmcblk0) is there
cgdisk /dev/mmcblk0
delete ALL paritions (using "d" on each highlighted partition)
"New"
Fist sector = hit ENTER (choose default = 2048 for me)
Size in sectors = 32G
Hex code = 0700 (Microsoft basic data)
Partition name = hit ENTER
"Write"
type "yes"
"Quit"
gdisk /dev/mmcblk0
should display = "Found valid GPT with protective MBR; using GPT"
"x" (extra functionality (experts only))
"z" (zap (destroy) GPT data structures and exit)
"Y" (Yes to continue)
"N" (blank out MBR)
fdisk /dev/mmcblk0
"p" (print parition table)
"c" (toggle dos compatibility flag)
should show DOS COMPATABILITY FLAG SET (DEPRICATED)
"d" (delete partition)
MAKE SURE NO PARTITIONS EXIST!
"n" (new partition)
"p" (primary)
hit ENTER (default = "1")
hit ENTER (first sector, my default was 63)
"+32G" (last sector, this creates 32GB partition)
"a" (toggle bootable flag, should show "the bootable flag on partition 1 is enabled now")
"t" (partition type)
"c" (W95 FAT32 (LBA))
"w" (write table to disk and exit)
Format the new partition, FAT32
mkfs.fat -F 32 /dev/mmcblk0p1
Goto the folder containing the debrick N910P image
cd /mnt/sysimage/Users/$USER/Downloads/SM-N910P-trltespr
dd if=debrick-n910p.img of=/dev/mmcblk0 bs=1M
sync
Eject sdcard and place in your Note 4 phone
This time, when I put the battery in the phone, I got the same text as before:
Code:
BOOT RECOVERY MODE
CHECK BOOT PARTITIONS..
COPY FROM T-FLASH..
BOOT RECOVERY
WRITE 188416 sectors
REBOOT
And then, it did a REAL reboot, and went directly to download-mode!
I tested this multiple times - as long as I wrote the debrick image in Win10, and then erased the SDcard and formatted it as Fat32 without using GPT just a basic MBR, and wrote the debrick image that way in linux it worked flawlessly!
let it boot, then do it's reboot
should be able to go into RECOVERY = Home+Vol-Down+Power !!!
:: Boot Windows ::
unzip "N910PVPU4COG5_SPT4COG5_Sprint_USA_v5.1.1_Repair_Firmware.zip"
run Odin3 3.09
click PIT button -> select "TRLTE_USA_SPR.pit" -> click OPEN
click AP button -> select "ALL_SPT_N910PVPU4COG5_N910PSPT4COG5_CL5303209_QB5691107_REV00_user_low_ship_MULTI_CERT.tar.md5" -> click OPEN
phone should be in DOWNLOAD mode (home+vol-down+power -> UP to continue) and connected via microUSB, Odin3 should be detecting it with a BLUE ID:COM lit up on top-left
click START button in Odin3
when finished it will reboot, and all should be well
- One last note, about the "mmc read fail" error, I took this gentleman's advice:
As a side note....
IF YOU HAVE THE MMC READ FAIL MESSAGE!!!
Which consists of Random Reboots, Heating Issues when theirs hardly no apps on, or even Lag or Glitchyness.
The Temp FiX that I've been using everyday and haven't had these issues since was downloading this app
WakeLock Manager and setting to PARTIAL LOCK! on Level 4.
Click to expand...
Click to collapse
And am currently running Wake Lock - PowerManager from Google Play as suggested, just to be safe - and so far, I have not YET had to deal with that horrid business again (so far, fingers crossed).
And there ye have it, that is my story, my tribulations, and my fix. Thank you to all who came before me, and for everyone's good advice = Good luck to all, and have a great rest of 2017.
XORr0 said:
[*]mount windows folder that holds the debrick N910P image = mount /dev/sda2 /mnt/sysimage
Click to expand...
Click to collapse
Hi man, thank you for the post, but can´t mount the sysimage
Help me please!!!
Mega Link a la imagen de debrick N910P ( 128MB )
the files are not there if it is not too much trouble to provide me with the: confusing files: confusing