Related
How to Access HPA
How to access HPA Partiton and extract all driver
Hello all.
I need Recovery Partition on English.
I talk with Pof he say that me must English Recovery partiton.
Please Send to my.
Thanks in advance!!!
I have sent the copy of my HPA partition to danielherrero which was hagving the same problem as you, and he could recover his vista with it, the problem is that my recovery partition installs a Spanish language Vista, which will not be good for you (as you might not understand spanish), so if someone could dump an HPA in english, this would be useful to people who lost it.
Instructions to dump and restore the recovery partition are on my blog:
http://pof.eslack.org/blog/2008/04/...re-the-vista-recovery-partition-on-htc-shift/
I can if acess to FTP/HTTP server for upload a Image and all software for HTC Shift and access for all people needet
pof said:
I have sent the copy of my HPA partition to danielherrero which was hagving the same problem as you, and he could recover his vista with it, the problem is that my recovery partition installs a Spanish language Vista, which will not be good for you (as you might not understand spanish), so if someone could dump an HPA in english, this would be useful to people who lost it.
Instructions to dump and restore the recovery partition are on my blog:
http://pof.eslack.org/blog/2008/04/...re-the-vista-recovery-partition-on-htc-shift/
Click to expand...
Click to collapse
hello
i dont mind doing that on my english shift..ive had quick look at the page discribing how to do it but being a bit of a thicko it would great if you could send step by step destructions for me..i have the capability of loading it onto external drive where i could give you access to upload..please advise me if you wish
pof said:
I have sent the copy of my HPA partition to danielherrero which was hagving the same problem as you, and he could recover his vista with it, the problem is that my recovery partition installs a Spanish language Vista, which will not be good for you (as you might not understand spanish), so if someone could dump an HPA in english, this would be useful to people who lost it.
Instructions to dump and restore the recovery partition are on my blog:
http://pof.eslack.org/blog/2008/04/...re-the-vista-recovery-partition-on-htc-shift/
Click to expand...
Click to collapse
Yes, It saved my shift from SAT and several weeks out of home. Thanks again Pau
pd: Remove SD when dumping/restoring....
It takes 4 hours to dump or restore.
Pau....Maybe when I copied your fist MB did the trick?
plasticplanet said:
hello
i dont mind doing that on my english shift..ive had quick look at the page discribing how to do it but being a bit of a thicko it would great if you could send step by step destructions for me..i have the capability of loading it onto external drive where i could give you access to upload..please advise me if you wish
Click to expand...
Click to collapse
Basically you need:
~1Gb USB stick
~3,5 Gb of free space on your Vista partition
1) Install Slax on the USB pendrive, follow instructions here:
http://www.pendrivelinux.com/2006/09/20/all-in-one-usb-slaxzip/
2) Reboot your Shift
3) Press Fn+F10 to choose the boot device, select USB pen drive
4) Slax boot menu will appear, choose the first option (KDE)
5) Open a Konsole (Terminal program), right next to the "K" menu in the menu bar.
6) Type the following command:
Code:
# dd if=/dev/hda of=/dev/hda1/shift-vista-recovery.bin bs=1 skip=36773560320
7) This will last about 4 hours, keep your Shift on charger and wait until it finishes. When it finishes you'll see something similar to this:
Code:
3226976256+0 records in
3226976256+0 records out
3226976256 bytes (3.2 GB) copied, 11938 s, 270 kB/s
8) Now reboot into Vista again, the backup of the HPA holding the vista recovery will be in c:\shift-vista-recovery.bin
9) Zip or Rar the 'shift-vista-recovery.bin' file and upload it somewhere, keep in mind this is a big file so you might want to split it in several volumes before uploading it.
10) There is no 10
That's all, feel free to ask if some point is not clear enough.
On Privet messegi send to Pof and plasticplanet FTP access for upload a HPA Partition on English or ES.
pof said:
6) Type the following command:
Code:
# dd if=/dev/hda of=/dev/hda1/shift-vista-recovery.bin bs=1 skip=36773560320
7) This will last about 4 hours
Click to expand...
Click to collapse
not really 4 hours, for me that only did 98MB in 4 hours, and I had to use /mnt/hda1 anyway.
so tell me why is bs set to 1?
is bs=16384 fine? because that's how i did it in the end.
any way to verify the contents?
P.S: oh yes and my shift is hardspl'ed man!!
Probably I am in wrong but that command is dumping the last 3GiB of hda disk to the first partition of the same partition. Wouldnt be safer to dump to the sd or a usb pen?
no, the source is /dev so the hw device, like the whole hdd on windows
and the dest is /mnt/hda1 so the partition like C: on windows
the HPA "partition" is not part of the visible partition. no risk....
and the proper and FAST command is (if you are using the slack usb distro that pof linked to in his description) :
dd if=/dev/hda of=/mnt/hda1/shift-vista-recovery.bin bs=16384 skip=2244480
I assume similar method works for copying it back (the point is bs=16384).
if you want to be sure your shift has a partition of the exact same size, then read dmesg until you find the HPA (host protected area) information, should say what it said for pof and for me:
sda: Host Protected Area detected.
current capacity is 71826615 sectors (36775 MB)
native capacity is 78126048 sectors (40000 MB)
sda: Host Protected Area disabled.
sda: 78126048 sectors (40000 MB), CHS=16383/255/63
(ignore the "sda" part of course)
someone downloaded the backup I uploaded and confirmed it works.
cmonex said:
so tell me why is bs set to 1?
is bs=16384 fine? because that's how i did it in the end.
Click to expand...
Click to collapse
"bs" was set to 1 because I was too lazy to do the maths
Yes, you can increase it as long as you change the "skip" part too.
I have a problem.
I have two shift devices, one got screwed trying to install ubuntu MID and the other one is fine
I've tried your method with dd to the to copy the recovery partition from the working shift however it always fails during the fn f3(same failure that I got even before restored the image). IT starts the restore but fails somewhere along the line at 2%.
I noticed my hpa is at a slightly different location to yours using dmesg. Probably because it has office in it. How do I calculate the seek/skip
Also I tried doing a dd from higher on the drive just to see if I can atleast pick it up as excess got the same error.
Any help guys
btw good work on everything else you all have done
ok i got it..you guys were slightly off in your calculations so i wasn't sure that the address you got was by 512. Anyhow I have the .bin dump for anyone who needs it for the vista with office demo or those who partition size is different to that of the above postings. I also took it a little higher just to ensure i don't miss any of the partition
BTW posting from the previously bricked shift
Could you please stick this thread.
pof
Could you please stick this thread too. It has a lot of useful information.
Thanks
Ram
Hi there
if someone have a german Recovery partition Image for me, please let me know
My new HTC Shift has a Recovery Partiton but don´t boot with this. Don´t know why.
Maybe a recover of this partition may be work
But only for testing, i have made (before starting the Shift first time) a complete Acronis Image
I have a somewhat related question. I've basically busted my Vista recovery partition, long story short, I decided to try out ubuntu mid and didn't realize it was going to wipe my whole hdd (installed on my other laptops the regular images of ubuntu hardy and it asked me to specify partitions etc., but the mid didn't and I was half awake or vice versa).
I have now installed XP, and even though ubuntu mid appears to have wiped the HPA, it is still hidden from windows. I don't plan on going back to Vista (if I have to, I will just throw the thing out, xp just gave it a new lease on life). Is there a safe and easy way to unhide the hidden partition and use it, without having to install linux and without affecting my XP install (took too long to get it running and I'd rather give up the 3GB than have a go at it again, at least not until I really have to)?
I suppose I managed to unhide it, whiped it out and put it together with the rest of my HDD. Though now I used about 3GB with Acronis and created my own hidden/protected partition with XP completely set-up and some essential software. Worked like a charm.
Restore recovery partition
What is the correct command for restoring the rescovery partition bin file?
I used "dd if=/dev/hda of=/mnt/hda1/shift-vista-recovery.bin bs=16384 skip=2244480" to create the dump file.
I need you.
Hello.
I had installed ubuntu 8.04 and it run good, but the resolution was horrible.
With vista, the virtual resolution permits work without external panel, for not very long time, of course.
I don't now what i do wrong, and now i can't recovery the Vista by the recovery partition. I have installd a Vista Bussiness from a copy and with the activation key from my htc shift and it works good.
I wouid like recovery the recovery partition of my htc.
know you where i could get the "shift-vista-recovery.bin" image from?
thanks. and "help" me please
Disclaimer
Before even consider reading this, know that I cannot be held responsible if following these steps will: brick your device, make your girl friend break up with you, start third world war or do any other kind of damage.
Motivation
This tutorial is intended to help people who did not make a full backup of their device and applied the Alpha-FormatTouch-2.zip to their device and as a result lost the GlowLight feature. It took me a couple of days to figure out how to revert to factory settings, and thus, I hope that I can save others time.
Preliminary
You need
Nook Simple Touch Glowlight, semibricked
SD Card
SD card reader
Downloads
Download the following files:
factory.zip - downloads[dot]nanophysics[dot]dk/nstg/factory[dot]zip (if you have a copy of your own factory.zip -- found on the partition /factory/ -- use that instead)
[ClockworkMod - downloads[dot]nanophysics[dot]dk/nstg/sd_128mb_clockwork-rc2[dot]zip
Install Clockworkmod on SD card
On Mac OS X, plug in the SD card and find the device using
Code:
$ diskutil list
I will assume that your device is /dev/disk1. Unmount the disk
Code:
sudo diskutil unmountDisk /dev/disk1
and write the ClockworkMod to it
Code:
sudo dd if=128mb_clockwork-rc2.img of=/dev/disk1
Copy the factory.zip to the disk and eject it.
On Windows you can use Win32Imager.
Install factory image
Power off your Nook and insert the SD card. Then power it up. After a while the CWM menu will appear (if you get a white screen press right-down). Select "install zip from sdcard" using the right side navigation to go up and down and u to enter. If you enter the wrong menu you can go back on right up. Now select "choose zip from sdcard" and choose factory.zip. Finally, click the option saying "yes - install factory.zip"
After a few minutes the installation is complete and if everything went ok, you should now be back to the original factory software.
Reset user settings (optional)
If you want your Nook to be completely reset, you can optionally do a reset of your settings. Power off you Nook. Power it up again and hold left and right down simultaneously for around 30 s. Answer yes twice. After a while your Nook has been reset.
Backup
Finally, it is time to do what you should have done in the first place (and probably also the reason why you are following this tutorial): Make a full backup of your Nooks internal SD card. See blog[dot]the-ebook-reader[dot]com/2012/05/02/how-to-backup-and-restore-nook-glow-and-nook-simple-touch for more information.
Thanks for the tutorial. However i just had a few queries.
1. My NSTG is rooted and functioning normally. Only glowlight does not work. Does your tutorial apply to such a device too.
2. How can i take backups of my current /rom and /factory partitions so that i can restore them in case of any eventuality.
Thanks a bunch in advance.
i just erase every thing . now my nook is completely messed up.
I can't find your factory.zip would you mind resend it please ?
shank21101985 said:
Thanks for the tutorial. However i just had a few queries.
1. My NSTG is rooted and functioning normally. Only glowlight does not work. Does your tutorial apply to such a device too.
2. How can i take backups of my current /rom and /factory partitions so that i can restore them in case of any eventuality.
Thanks a bunch in advance.
Click to expand...
Click to collapse
If your NSTG is rooted, this may remove rooting - at least I think, I did not try. However, you can always reroot.
Regarding backup, I would make a full image backup before starting. If you have a Windows box, follow the instruction on blog[dot]the-ebook-reader[dot]com/2012/05/02/how-to-backup-and-restore-nook-glow-and-nook-simple-touch and make a full backup of your system.
I have only done backup of individual partitions on Linux: Boot the device with noogie.img and plug it in. On Ubuntu,t 6-8 partitions should immediately appear.
jjinkou2 said:
i just erase every thing . now my nook is completely messed up.
I can't find your factory.zip would you mind resend it please ?
Click to expand...
Click to collapse
There was missing a slash in the URL. It has been fixed.
Are you able to register a device reimaged using this factory.zip to your BN account?
If not, it's a bit of a pain for folks.
I have a disk image made via
dd if=/dev/block/mmcblk0p1 of=/part1.img bs=1M
This contains teh whole of a US NSTG's first partition; restoring it using
dd if=part1.img of=/dev/block/mmcblk0p1 bs=1M
allows me to boot my device, and the glow still works.
This seems to be more likely to restore the glow function yet preserve the ability to register with BN - the factory.zip method is not generic, as far as I know, it will restore some other person's NST serial number, mac address and other identifiers to your device, won't it?
If someone will PM me, I'll send a zipped copy of my .img file to them and let them try using it to recover glow function and their own registration in a nook glow. If that works, it can be posted more widely.
roustabout said:
This seems to be more likely to restore the glow function yet preserve the ability to register with BN - the factory.zip method is not generic, as far as I know, it will restore some other person's NST serial number, mac address and other identifiers to your device, won't it?
If someone will PM me, I'll send a zipped copy of my .img file to them and let them try using it to recover glow function and their own registration in a nook glow. If that works, it can be posted more widely.
Click to expand...
Click to collapse
Remark that I recommend that people use their own factory.zip image. Nevertheless, all these data you mention are stored on the rom partition. To my awareness this partition is only overwritten if one applies rombackup.zip, but not by factory.zip. Thus, your B&N shop should be fully functional afterwards. I did apply someone elses factory.zip first, and I had no problems registering my device. However, if anyone would experience such an issue, please drop a line in this thread.
In any case, you should always do a full system image before following tutorials like this one, or for that matter, before apply someone elses partition images to your own device.
roustabout said:
Are you able to register a device reimaged using this factory.zip to your BN account?
If not, it's a bit of a pain for folks.
I have a disk image made via
dd if=/dev/block/mmcblk0p1 of=/part1.img bs=1M
This contains teh whole of a US NSTG's first partition; restoring it using
dd if=part1.img of=/dev/block/mmcblk0p1 bs=1M
allows me to boot my device, and the glow still works.
Click to expand...
Click to collapse
Judging from your other post (http://forum.xda-developers.com/showthread.php?t=1836188&page=4), the partition you have made a copy of, is the boot partition? If glow was already working, it will still work after overwriting the boot image.
However, if it was not working already, it is very unlikely that installing a new boot image will resolve the issue described here, since it is a consequence having downgraded the OS.
I had not understood that the device you're targeting with this thread is an NSTG running 100% noo simple touch software - the thread refers to a problem with the alpha touch formatter, but I had not realized that was the outcome of the tool.
I've seen a few people describe their NSTGs as "fine, but not glowing any more" and had not seen those folks explain that they were running NST software on the NSTG.
For those folks, I had thought copying in the boot environment and kernel would be helpful. My understanding was that the kernel in the NSTG at software 1.1.5 was different than the NST kernel; I was thinking that getting the kernel and other boot hooks ready was what was really missing.
Fortunately, there's now a 1.2.0 updater out, and I suspect that soon there will be a CWM installable 1.2.0 update which will be super helpful. (Though folks will still need a partition table - I think that would be another use of writing in a viable first partition followed by a restart, to get the partition table straightened out before proceeding.)
roustabout said:
I had not understood that the device you're targeting with this thread is an NSTG running 100% noo simple touch software - the thread refers to a problem with the alpha touch formatter, but I had not realized that was the outcome of the tool.
I've seen a few people describe their NSTGs as "fine, but not glowing any more" and had not seen those folks explain that they were running NST software on the NSTG.
For those folks, I had thought copying in the boot environment and kernel would be helpful. My understanding was that the kernel in the NSTG at software 1.1.5 was different than the NST kernel; I was thinking that getting the kernel and other boot hooks ready was what was really missing.
Fortunately, there's now a 1.2.0 updater out, and I suspect that soon there will be a CWM installable 1.2.0 update which will be super helpful. (Though folks will still need a partition table - I think that would be another use of writing in a viable first partition followed by a restart, to get the partition table straightened out before proceeding.)
Click to expand...
Click to collapse
Ok. No this thread is not intended for people who have destroyed partition tables etc., but only for people who have downgraded their software by using NST recovering guides on their NSTG device. I found it relevant to explain how this is done, since many people complain that their NSTG works, except that glow light no longer works. If they look into the software version they find something below 1.1.5, like 1.1 which was my case. I could not find a guide which explained me what to do after screwing up the software, hence this guide.
Partition tables and "accidently formatting" is a completely other issue. In the end, here the main problem is that people do not make a backup as they assume that everything is going to be fine. I assumed that myself. However, at some point I will have a look at the rom partition, because I think it is quite limited amount of information you find their. It should be possible to restore your Nooks serial number -- it is written on the package of the Nook -- after applying another Nooks image. I just received my second Nook so I am going to try this at some point.
Thank you so much for sharing the solution.. finally my glowlight works now !!
shank21101985 said:
Thank you so much for sharing the solution.. finally my glowlight works now !!
Click to expand...
Click to collapse
Hic, I cannot download the image file, my backup file was deleted, anyone can upload that image for me?
Thanks so much:crying:
factory.zip
I know it's a long shot, but if anyone has a copy of the factory.zip from a glowlight I'd really appreciate it. I've installed a non-glowlight one for now, but would really love my backlight back!
Cheers!
john2k10 said:
I know it's a long shot, but if anyone has a copy of the factory.zip from a glowlight I'd really appreciate it. I've installed a non-glowlight one for now, but would really love my backlight back!
Cheers!
Click to expand...
Click to collapse
So did you actually replace the factory.zip with one for the NST or did you just run a restore from, say, NookManager? I'm not too sure about this, but I think it's kind of difficult to wipe the factory.zip. Anyway, since I'm not familiar with the NTG, and you seem to have done something that others have also done before, have a look at this old thread and see if it gets you anywhere:
http://forum.xda-developers.com/showthread.php?t=1936458
john2k10 said:
I know it's a long shot, but if anyone has a copy of the factory.zip from a glowlight I'd really appreciate it. I've installed a non-glowlight one for now, but would really love my backlight back!
Cheers!
Click to expand...
Click to collapse
Mmm......have a look at this:
http://waveswirl.blogspot.com/2013/01/xda-developers-tutorial-how-to.html
nmyshkin said:
Mmm......have a look at this:
http://waveswirl.blogspot.com/2013/01/xda-developers-tutorial-how-to.html
Click to expand...
Click to collapse
Its dead I need a glowlight factory image
can someone please re-upload the glowlight factory image please.... Thank you in advance
I've managed to softbrick my nexus 10 by trying to disable extra services (was getting about 1.5 hours battery life with media services running the processor 100% all the time). It worked wonderfully (no negative side effects, went back to 10+ hours with the screen on, or days on standby) until I reboot it and now it won't load past the moving colors (Android 4.4.3, unlocked and all that).
I have TWRP, I was hoping to backup everything possible via usb, but it seems it's incapable of doing so. ADB backup can't be done using TWRP since there's no unlock function (reaaal useful there, recovery mode that doesn't support backups) and adb pull fails if I try to pull everything since there are files and folders with invalid file names (who puts ":" in folder names? they should be shot), and I don't know specifically what to pull, I was just going to get everything put back what I found was missing that I needed. There's no room to do a backup onto the device, and since the N10 has to sd/microsd, well... Useless options are useless.
Is there anyway to just do a proper backup with TWRP over USB? Or is the "recovery" mode as useless as I think it is when it comes to backups? (I'm aware I can get the tablet back to working order if I disregard the data on it, this is a question about backing things up before doing so)
Edit: Also, I have a pro version of SkipSoft ToolKit, but unless you can actually load into the OS the toolkit can't do anything at all.
Just really frustrated with the lack of doing something as basic as copying files from one place to another. Been messing with this all morning.
Diet6 said:
I've managed to softbrick my nexus 10 by trying to disable extra services (was getting about 1.5 hours battery life with media services running the processor 100% all the time). It worked wonderfully (no negative side effects, went back to 10+ hours with the screen on, or days on standby) until I reboot it and now it won't load past the moving colors (Android 4.4.3, unlocked and all that).
I have TWRP, I was hoping to backup everything possible via usb, but it seems it's incapable of doing so. ADB backup can't be done using TWRP since there's no unlock function (reaaal useful there, recovery mode that doesn't support backups) and adb pull fails if I try to pull everything since there are files and folders with invalid file names (who puts ":" in folder names? they should be shot), and I don't know specifically what to pull, I was just going to get everything put back what I found was missing that I needed. There's no room to do a backup onto the device, and since the N10 has to sd/microsd, well... Useless options are useless.
Is there anyway to just do a proper backup with TWRP over USB? Or is the "recovery" mode as useless as I think it is when it comes to backups? (I'm aware I can get the tablet back to working order if I disregard the data on it, this is a question about backing things up before doing so)
Edit: Also, I have a pro version of SkipSoft ToolKit, but unless you can actually load into the OS the toolkit can't do anything at all.
Just really frustrated with the lack of doing something as basic as copying files from one place to another. Been messing with this all morning.
Click to expand...
Click to collapse
Do you still need help? What about mtp mounting? You can pull * for a whole folder
Why not adb sideload a new rom?
I don't think I can MTP mount a Nexus 10, at least not in recovery mode. What I ended up doing was buying a OTG usb drive and making a backup to that. Problem was it split the tar over 4 files, which corrupted them (or at least made them not work with 7zip or tartool) fortunately I was able to get them to work with cygwin enough to get the files I wanted. I didn't want to sideload a new rom until I had backed up certain application data just in case it removed it.
All in all, had to buy a OTG usb drive (I would have just bought a cable but all the stores around here had was this "Dane 16gb OTG drive". So 20 bucks later I had the files I needed. Still annoyed that you can't do a ADB backup from fastboot or recovery mode, it seems like those would be the best places because no system files are in use, but who knows maybe the developers know something I don't.
In summary:
TWRP recovery cannot confirm a ADB backup over USB. ADB backups can only be done from the operating system.
TWRP recovery mode can only backup to OTG (if your device supports it, Nexus 10 does), but if the backup is larger than 2gb it will split the file and you will need some form of linux to extract it.
ADB cannot copy every file in recovery mode over USB due to certain file names being invalid for NTFS (this is probably not a problem on other file system types), this is problematic since the "pull" command has no skip option, it just fails when it hits one of these files.
Well you can easily flash latest rwrp that does well on my Linux mount internal storage but another solution is just flashing a rom with abd sideload and the'the back up from pc the content
---------- Post added at 04:24 AM ---------- Previous post was at 04:23 AM ----------
Or that will just un brick your tablet
Diet6 said:
Still annoyed that you can't do a ADB backup from fastboot or recovery mode
Click to expand...
Click to collapse
adb doesn't work in fastboot mode, only recovery or Android itself.
Diet6 said:
In summary:
TWRP recovery cannot confirm a ADB backup over USB. ADB backups can only be done from the operating system.
Click to expand...
Click to collapse
Maybe because /data (not talking about /data/media) wasn't mounted?
Diet6 said:
TWRP recovery mode can only backup to OTG
Click to expand...
Click to collapse
Huh?
Diet6 said:
ADB cannot copy every file in recovery mode over USB due to certain file names being invalid for NTFS (this is probably not a problem on other file system types), this is problematic since the "pull" command has no skip option, it just fails when it hits one of these files.
Click to expand...
Click to collapse
That's NTFS' problem, not TWRP's.
beekay201 said:
1. adb doesn't work in fastboot mode, only recovery or Android itself.
2. Maybe because /data (not talking about /data/media) wasn't mounted?
3. Huh?
4. That's NTFS' problem, not TWRP's.
Click to expand...
Click to collapse
1. I was just covering that you can't actually do a ADB backup unless you have access to android OS, in case anyone else came across this. (I didn't know when I started, and it took awhile to find it said concretely anywhere)
2. I made sure everything was mounted, the issue is when you send a backup command over ADB it says the "Now unlock your device and confirm the backup operation" message in terminal which you can't do from recovery mode on the device, thus you cannot do a ADB backup command over TWRP (or other recovery modes I'd imagine).
3. I should have been more specific. TWRP can do a backup to the device itself (built in storage), SD card (if your device has one and you mount it), or a OTG (on the go) device via usb directly to media like a flash drive. It cannot issue a backup over USB to a computer.
4. Completely agree it's a NTFS issue, but it could be mostly avoided by allowing files that error to be skipped or renamed rather than terminating the process. (I understand that's on the android devs since pull is made by them, and I doubt they would care to improve the command for a file system I doubt they use). Again I mostly included that so if anyone else is trying to figure it out they can stop looking for "a way" and just accept it can't be done.
Ultimately Khaon is right in that sideloading a rom would have unbricked it and I could have done the ADB backup then, I just wasn't sure how that might affect the app data storage so I was looking for a way to back it up before doing that.
Diet6 said:
1. I was just covering that you can't actually do a ADB backup unless you have access to android OS, in case anyone else came across this. (I didn't know when I started, and it took awhile to find it said concretely anywhere)
2. I made sure everything was mounted, the issue is when you send a backup command over ADB it says the "Now unlock your device and confirm the backup operation" message in terminal which you can't do from recovery mode on the device, thus you cannot do a ADB backup command over TWRP (or other recovery modes I'd imagine).
3. I should have been more specific. TWRP can do a backup to the device itself (built in storage), SD card (if your device has one and you mount it), or a OTG (on the go) device via usb directly to media like a flash drive. It cannot issue a backup over USB to a computer.
4. Completely agree it's a NTFS issue, but it could be mostly avoided by allowing files that error to be skipped or renamed rather than terminating the process. (I understand that's on the android devs since pull is made by them, and I doubt they would care to improve the command for a file system I doubt they use). Again I mostly included that so if anyone else is trying to figure it out they can stop looking for "a way" and just accept it can't be done.
Ultimately Khaon is right in that sideloading a rom would have unbricked it and I could have done the ADB backup then, I just wasn't sure how that might affect the app data storage so I was looking for a way to back it up before doing that.
Click to expand...
Click to collapse
I'd just 'tar' what I wanted on the device and then pull that with adb.
Yeah, I just had no idea what I wanted. I'm not 100% familiar with how the system stores application data, I figured if I copy everything than anything I "miss" after I formated it I'll be able to just research where it was and dig in the backup and pull it out.
Yeah adb sideload a rom will only affect system partition thus your data would not have been modified in any way. So you are done with your issue?
Sent from my Xiaomi MI2s
Khaon said:
Yeah adb sideload a rom will only affect system partition thus your data would not have been modified in any way. So you are done with your issue?
Sent from my Xiaomi MI2s
Click to expand...
Click to collapse
Yes, sorry for the slow reply. I've completed my update, just wanted to follow up on everything I did incase the information is useful for anyone else new to this like I am.
For work I need to have 75 Samsung Galaxy Tab A6 Tablets all programmed the exact same way. They all need the same wifi, passwords, apps and everything. I would rather not have to program them one by one. What would you guys recommend to do this the fastest easiest way? Any help would be appreciated.
cspez said:
For work I need to have 75 Samsung Galaxy Tab A6 Tablets all programmed the exact same way. They all need the same wifi, passwords, apps and everything. I would rather not have to program them one by one. What would you guys recommend to do this the fastest easiest way? Any help would be appreciated.
Click to expand...
Click to collapse
Set up a Google Account on the first one and install everything and turn on "backup" for the account. Then use that same account on the other 74 and let google "restore" the apps and data to them. Not the only way but a fairly easy one.
cspez said:
For work I need to have 75 Samsung Galaxy Tab A6 Tablets all programmed the exact same way. They all need the same wifi, passwords, apps and everything. I would rather not have to program them one by one. What would you guys recommend to do this the fastest easiest way? Any help would be appreciated.
Click to expand...
Click to collapse
Hello,
Did you get any solution?
The best way is to install TWRP make a backup and restore this backup to ur tablets one by one using a usb key i do 3 to 4 at the same time,
It's not that long seriously
If you need more infos let me know
IET_DEMO said:
The best way is to install TWRP make a backup and restore this backup to ur tablets one by one using a usb key i do 3 to 4 at the same time,
It's not that long seriously
If you need more infos let me know
Click to expand...
Click to collapse
Thank you, but with the TWRP, I am able to restore only the same device from which i took the backup.
Jasmin74 said:
Thank you, but with the TWRP, I am able to restore only the same device from which i took the backup.
Click to expand...
Click to collapse
First of all:
I like to use an ssd usb key to put my backups on, because they are pretty fast(for mass production)
When you create your backup, ONLY use /SYSTEM and /DATA partition.
What i do for mass production with twrp is I setup my first tablet with all the settings i want then i backup this tablet.
Then for the next tablet, you note the serialno with this adb shell command: getprop ro.serialno
Then you go in the backup folder you just did -> /TWRP/BACKUPS/SERIALNO and you change the serialno with the one you just noted from your new tablet.
it should look like this(16 alphanumeric serial no):52XXXXXXXXXXX4e1.
I have a small .bat file that does this manipulation for me.
Then boot your new tablet in twrp, go in Restore and select your usb storage or internal depending on where your backup is stored.
Boom it appears!
This method is good only if your flashing on the SAME exact model of tablet, so be careful.
I used this method for more then 500 devices as of now.
Let me know how it goes.
yes, it works!
IET_DEMO said:
First of all:
I like to use an ssd usb key to put my backups on, because they are pretty fast(for mass production)
When you create your backup, ONLY use /SYSTEM and /DATA partition.
What i do for mass production with twrp is I setup my first tablet with all the settings i want then i backup this tablet.
Then for the next tablet, you note the serialno with this adb shell command: getprop ro.serialno
Then you go in the backup folder you just did -> /TWRP/BACKUPS/SERIALNO and you change the serialno with the one you just noted from your new tablet.
it should look like this(16 alphanumeric serial no):52XXXXXXXXXXX4e1.
I have a small .bat file that does this manipulation for me.
Then boot your new tablet in twrp, go in Restore and select your usb storage or internal depending on where your backup is stored.
Boom it appears!
This method is good only if your flashing on the SAME exact model of tablet, so be careful.
I used this method for more then 500 devices as of now.
Let me know how it goes.
Click to expand...
Click to collapse
Yes, it works well. thank you for your help.
I noticed my hard drive had been running very sluggish as of late so, I decided to do a swap between my SSHD to an SSD. I had a Toshiba 512gb SSD drive laying around after watching a few different youtube videos I took my shield pro apart and regreased the cpu and replaced the sshd. When I plugged my sshd into my computer it showed as "unallocated" so, I assumed it's because of the OS that is not readable on it and I did a raw copy over to my ssd with HHDRAWCOPY ver 11.10. After it completed which took about 3 hours I plugged everything back in and then turned on my shield to have a completely black screen. I've been doing a search on the forums, youtube, Nvidia shield forums but everything seems too old, most links don't even work. Is there anyone that can help me restore an image to an ssd or try to recover what I had on the hard drive? I would really appreciate it! I plugged my shield into my computer with a micro USB cable and it was detected as "APX". So, I am not sure if the sshd died or if it's something else. It had the latest firmware on it so, trying to find step-by-step instructions on how to recover and reinstall the os seems impossible. I plugged my controller in and held the A and B buttons immediately after plugging the power cable back into my shield to get the fastboot screen but that doesn't seem to work either. I really don't know what to do at this point and hoping most of you who have had this issue in the past would be able to shine some light. Thanks in advance!
So first off you should swap with a 500gb drive not a 512, although there are guides on how to get it to work with larger drives.
I had a similar issue after cloning my drive and just got a black screen from both drives. I used this guide to get me back up to a working image on 7.2.3. Keep in mind I have never done any of this before.
How to recover Shield TV Pro (2015) after an error while flashing a boot.img
Hello, I was flashing the Nvidia Shield Pro (2015) 8.0.1 official Developer image as per the instructions on Nvidia developer site. The device is unlocked already, the latest drivers are used, a fully functional usb cable is used, latest...
forum.xda-developers.com
After getting back up using this guide I updated to 8.0, don't do the 8.2.3 upgrade.
After doing this though I had L3 level DRM so netflix, prime video didn't work.
I searched more and found this thread on using a hex editor to copy the data for my wedivine keys.
Bricked Shield TV pro 2015 version - stuck in APX mode.
Yep, I know :( - stupidly I flashed the wrong image to the Shield TV pro (2015) and am stuck in apx mode. I read somewhere I can flash a hard drive image and lose access to netflix etc due to keys. Can someone point me the way to the guide/image...
forum.xda-developers.com
Specifically this part
Edit: OK I found them in broken image dump at address 0x2200000
I copied the hex from 0x2200000 (2178336 bytes) and then flashed that to the fixed drive at the same location, now Widevine is back to Level 1, so I guess that's me back up and running to the state before I bricked now.
so I used dd to make my own firstpart.bin from my old drive
dd if=\\?\Device\HarddiskX\Partition0 of=firstpart.bin count=6899870 --progress
HarddiskX is your hard disk for me that was Harddisk1
I then used a hex editor HxD (googled free hex editors)
and navigated to 2200000. I highlighted all the way until i started hitting 00 00 00 00 00. noted where I stopped and copied it to the clipboard
I then made a copy of the firstpart.bin that got me working from the first post. highlighted the same area in the hex editor and replaced it with my info.
I also replaced the serial number with my serial number. This was at offset: 0xa0400C so A0400C
your serial number is on the back of your shield. This isn't necessary but I wanted mine to match.
I then followed the first guide but used my new firstpart.bin file
Once I got up to 8.0 I turned on usb debugging so i didn't have to hardware reboot to get into fastboot
I used adb reboot bootlader and i was back in fastboot
I had some internet issues a couple of times so you may need to do a factory reset at some point. I just did a quick reset to get by in android.
i then erased userdata and cache
fastboot erase userdata
fastboot erase cache
fastboot reboot
erasing userdata takes a while be patient, took almost 2hours
Once I rebooted i was greeted with the newer shield experience. I set up using my phone when promted and was forced tio upgrade to 8.2.3. To my surprise it updated normally and I am now on a SSD with a fresh 8.2.3 and all Apps working like Netflix and Prime Video
This whole ordeal lasted several days and many hours of searching, watching videos and staying up to all hours of the night. In the end it was worth the satisfaction of succeeding.
afal_22 said:
So first off you should swap with a 500gb drive not a 512, although there are guides on how to get it to work with larger drives.
I had a similar issue after cloning my drive and just got a black screen from both drives. I used this guide to get me back up to a working image on 7.2.3. Keep in mind I have never done any of this before.
How to recover Shield TV Pro (2015) after an error while flashing a boot.img
Hello, I was flashing the Nvidia Shield Pro (2015) 8.0.1 official Developer image as per the instructions on Nvidia developer site. The device is unlocked already, the latest drivers are used, a fully functional usb cable is used, latest...
forum.xda-developers.com
After getting back up using this guide I updated to 8.0, don't do the 8.2.3 upgrade.
After doing this though I had L3 level DRM so netflix, prime video didn't work.
I searched more and found this thread on using a hex editor to copy the data for my wedivine keys.
Bricked Shield TV pro 2015 version - stuck in APX mode.
Yep, I know :( - stupidly I flashed the wrong image to the Shield TV pro (2015) and am stuck in apx mode. I read somewhere I can flash a hard drive image and lose access to netflix etc due to keys. Can someone point me the way to the guide/image...
forum.xda-developers.com
Specifically this part
Edit: OK I found them in broken image dump at address 0x2200000
I copied the hex from 0x2200000 (2178336 bytes) and then flashed that to the fixed drive at the same location, now Widevine is back to Level 1, so I guess that's me back up and running to the state before I bricked now.
so I used dd to make my own firstpart.bin from my old drive
dd if=\\?\Device\HarddiskX\Partition0 of=firstpart.bin count=6899870 --progress
HarddiskX is your hard disk for me that was Harddisk1
I then used a hex editor HxD (googled free hex editors)
and navigated to 2200000. I highlighted all the way until i started hitting 00 00 00 00 00. noted where I stopped and copied it to the clipboard
I then made a copy of the firstpart.bin that got me working from the first post. highlighted the same area in the hex editor and replaced it with my info.
I also replaced the serial number with my serial number. This was at offset: 0xa0400C so A0400C
your serial number is on the back of your shield. This isn't necessary but I wanted mine to match.
I then followed the first guide but used my new firstpart.bin file
Once I got up to 8.0 I turned on usb debugging so i didn't have to hardware reboot to get into fastboot
I used adb reboot bootlader and i was back in fastboot
I had some internet issues a couple of times so you may need to do a factory reset at some point. I just did a quick reset to get by in android.
i then erased userdata and cache
fastboot erase userdata
fastboot erase cache
fastboot reboot
erasing userdata takes a while be patient, took almost 2hours
Once I rebooted i was greeted with the newer shield experience. I set up using my phone when promted and was forced tio upgrade to 8.2.3. To my surprise it updated normally and I am now on a SSD with a fresh 8.2.3 and all Apps working like Netflix and Prime Video
This whole ordeal lasted several days and many hours of searching, watching videos and staying up to all hours of the night. In the end it was worth the satisfaction of succeeding.
Click to expand...
Click to collapse
Hey thanks for the info Afal I really appreciate it! I searched through the forums and couldn't really find anything substantial. I just got a 1tb samsung evo 860 drive and I'd like to get that to work if possible. Also, I have reformatted my original sshd from my nvidia shield unit do you think I can still pull those widevine keys?
did you ever save your image to your PC? Does your 512gb drive still have the image on it?
afal_22 said:
did you ever save your image to your PC? Does your 512gb drive still have the image on it?
Click to expand...
Click to collapse
Unfortunately, no.
HookedonHD said:
Unfortunately, no.
Click to expand...
Click to collapse
I think you're out of luck then. Sorry. I got lucky and made a backup first which is the only way I could get mine.
afal_22 said:
I think you're out of luck then. Sorry. I got lucky and made a backup first which is the only way I could get mine.
Click to expand...
Click to collapse
That's ok, as long as I get my shield working again and I can record shows from live tv app and use kodi I am good with that. Now, I just need to figure out how I can get it to work with the 1tb drive and up and running again.
HookedonHD said:
That's ok, as long as I get my shield working again and I can record shows from live tv app and use kodi I am good with that. Now, I just need to figure out how I can get it to work with the 1tb drive and up and running again.
Click to expand...
Click to collapse
try here
Guide[Linux][Windows]: Migrate to SSD/HDD of any size, only for SATV Pro
I am not responsible for bricked devices, dead HDDs, animals activist campaigns, or any H/W damage caused by you following these directions. YOU are choosing to make these modificiations, and you, yourself take responsibility for doing these...
forum.xda-developers.com
afal_22 said:
try here
Guide[Linux][Windows]: Migrate to SSD/HDD of any size, only for SATV Pro
I am not responsible for bricked devices, dead HDDs, animals activist campaigns, or any H/W damage caused by you following these directions. YOU are choosing to make these modificiations, and you, yourself take responsibility for doing these...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks, this is where I get confused. So, I downloaded the the 1tb.bin version 1 and 2. However, what should the command line be for my 1tb ssd and do I use version 1 or 2? Thanks in advance!
Unfortunately I have not done a larger drive so I can't assist, I honestly don't know. read through the thread and maybe someone else had the same question.
afal_22 said:
Unfortunately I have not done a larger drive so I can't assist, I honestly don't know. read through the thread and maybe someone else had the same question.
Click to expand...
Click to collapse
I did that's why I haven't been able to figure it out but thanks for the input.
afal_22 said:
So first off you should swap with a 500gb drive not a 512, although there are guides on how to get it to work with larger drives.
I had a similar issue after cloning my drive and just got a black screen from both drives. I used this guide to get me back up to a working image on 7.2.3. Keep in mind I have never done any of this before.
How to recover Shield TV Pro (2015) after an error while flashing a boot.img
Hello, I was flashing the Nvidia Shield Pro (2015) 8.0.1 official Developer image as per the instructions on Nvidia developer site. The device is unlocked already, the latest drivers are used, a fully functional usb cable is used, latest...
forum.xda-developers.com
After getting back up using this guide I updated to 8.0, don't do the 8.2.3 upgrade.
After doing this though I had L3 level DRM so netflix, prime video didn't work.
I searched more and found this thread on using a hex editor to copy the data for my wedivine keys.
Bricked Shield TV pro 2015 version - stuck in APX mode.
Yep, I know :( - stupidly I flashed the wrong image to the Shield TV pro (2015) and am stuck in apx mode. I read somewhere I can flash a hard drive image and lose access to netflix etc due to keys. Can someone point me the way to the guide/image...
forum.xda-developers.com
Specifically this part
Edit: OK I found them in broken image dump at address 0x2200000
I copied the hex from 0x2200000 (2178336 bytes) and then flashed that to the fixed drive at the same location, now Widevine is back to Level 1, so I guess that's me back up and running to the state before I bricked now.
so I used dd to make my own firstpart.bin from my old drive
dd if=\\?\Device\HarddiskX\Partition0 of=firstpart.bin count=6899870 --progress
HarddiskX is your hard disk for me that was Harddisk1
I then used a hex editor HxD (googled free hex editors)
and navigated to 2200000. I highlighted all the way until i started hitting 00 00 00 00 00. noted where I stopped and copied it to the clipboard
I then made a copy of the firstpart.bin that got me working from the first post. highlighted the same area in the hex editor and replaced it with my info.
I also replaced the serial number with my serial number. This was at offset: 0xa0400C so A0400C
your serial number is on the back of your shield. This isn't necessary but I wanted mine to match.
I then followed the first guide but used my new firstpart.bin file
Once I got up to 8.0 I turned on usb debugging so i didn't have to hardware reboot to get into fastboot
I used adb reboot bootlader and i was back in fastboot
I had some internet issues a couple of times so you may need to do a factory reset at some point. I just did a quick reset to get by in android.
i then erased userdata and cache
fastboot erase userdata
fastboot erase cache
fastboot reboot
erasing userdata takes a while be patient, took almost 2hours
Once I rebooted i was greeted with the newer shield experience. I set up using my phone when promted and was forced tio upgrade to 8.2.3. To my surprise it updated normally and I am now on a SSD with a fresh 8.2.3 and all Apps working like Netflix and Prime Video
This whole ordeal lasted several days and many hours of searching, watching videos and staying up to all hours of the night. In the end it was worth the satisfaction of succeeding.
Click to expand...
Click to collapse
I had a 500gb ssd but I couldn't get it to work at all after that one time so, my beloved nvidia shield pro has been sitting on my shelf since then. I am hoping someone will come up with updated step-by-step instructions on how to revive the 2015 series 500gb pro because I think that was the best model they ever made IMHO.
I’m stuck in apx mode too. After the latest update
Even if I put in the original hhd my shield tv pro 2015 does nothing. Only powers on.