Hey everyone,
I had recently rooted my kindle fire but found that for some reason TWRP seemed to have corrupted the video and music apps from the kindle os. I decided that there really was no good reason to root for me personally as most of the software could be accessed with the lousy os from amazon.
i made a poor mistake however when I went to the kindle os and chose to reset to factory settings. Now, what happens when I attempt to boot is I'm presented with the kindle fire (fire in blue) and then allowed to either
1. boot normal
2.recovery
3. boot to reset
So esentially I cannot access the normal OS from amazon nor the ice cream leaving me with a nice piece of fully-functional hardware that cannot turn on.
I thought I might be able to fix all this by uninstalling TWRP but now when I plug the system into my computer, but i don't know what to do after mounting it so that it can be recognized.
I really need help!! please guys I beg of you to send me some instructions i can work through....
sorry to take up ur time.
I hate it when I can't access the ice cream use Soupkit dunno there must be a trillion threads with me saying the same thing http://forum.xda-developers.com/showthread.php?t=1850038 or get a factory cable.
Josepho1997 said:
Nevermind. I see you cant mount. Just do as thepooch tells you and you should be fine.
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
actually, i can mount the device. I'm not sure i understood how soupkit will solve the problem.
just to confirm with you,
I have twrp but that is all I can access. how can i get back to normal usage of an OS?
Soupkit will fix mounting problems with your sdcard unless you can mount it otherwise by connecting to computer and select mount checks in boxes of sdcard and cache only then hit the big mount button , transfer a ROM flash it or restore a backup.
Thepooch said:
Soupkit will fix mounting problems with your sdcard unless you can mount it otherwise by connecting to computer and select mount checks in boxes of sdcard and cache only then hit the big mount button , transfer a ROM flash it or restore a backup.
Click to expand...
Click to collapse
hey thanks so much for all the help
I did exactly what you said. I actually downloaded MIU and the kindle fire update software
I first tried installing mui speciically for KF but it didn't work. many error messages kept popping up. So i tried installing the amazon OS, first changing the name to update.zip file. i then flashed it, and now when i boot i get the typical kindle OS.
however, the os continues to restart time and again every few seconds and i dont see a settings bar at the top of the screen
any thoughts on how to diagnose the problem? am i missing some sort of important software?
unstopable96 said:
hey thanks so much for all the help
I did exactly what you said. I actually downloaded MIU and the kindle fire update software
I first tried installing mui speciically for KF but it didn't work. many error messages kept popping up. So i tried installing the amazon OS, first changing the name to update.zip file. i then flashed it, and now when i boot i get the typical kindle OS.
however, the os continues to restart time and again every few seconds and i dont see a settings bar at the top of the screen
any thoughts on how to diagnose the problem? am i missing some sort of important software?
Click to expand...
Click to collapse
Wow I hate to say it "but out of the pan into the fire". No settings is a huge problem you still need fff and twrp to flash a rom preferably after a full wipe, if you could access setting it`s as simple as factory resetting it. The problem is you didnt wipe correctly when you flashed stock
Thepooch said:
Wow I hate to say it "but out of the pan into the fire". No settings is a huge problem you still need fff and twrp to flash a rom preferably after a full wipe, if you could access setting it`s as simple as factory resetting it. The problem is you didnt wipe correctly when you flashed stock
Click to expand...
Click to collapse
does that mean it is beyond repair? what do you suggest that I do? also, what is fff?
unstopable96 said:
does that mean it is beyond repair? what do you suggest that I do? also, what is fff?
Click to expand...
Click to collapse
It's pretty hard to make a kindle beyond repair although I have seen people do it. Have you tried using soupkit? You need fff and twrp, fff is the bootloader with the white kindle blue fire splash that you use to access recovery. Soupkit may let you resend the recovery and bootloader to the device so that you can do a full wipe minus the sdcard/external storage and flash a new ROM.
Thepooch said:
It's pretty hard to make a kindle beyond repair although I have seen people do it. Have you tried using soupkit? You need fff and twrp, fff is the bootloader with the white kindle blue fire splash that you use to access recovery. Soupkit may let you resend the recovery and bootloader to the device so that you can do a full wipe minus the sdcard/external storage and flash a new ROM.
Click to expand...
Click to collapse
ok, thats good news. I happen to not run linux on my pc though so soupkit is gonna be anoying to install. at present, since having installed amazon's flash, startup does not prompt me with twrp anymore. any thoughts? I'm soorry for all this bother.
if anyone feels comfertable and thinks they could easily solve this problem, i live in NYC and am willing to meet (even at small cost). I live in washington heights.
any links tellign me preceisely how to fix this problem would be greatly appreciated
You install Soupkit onto a live usb that is running ubuntu with persistent. The persistent allows the live usb to save data between reboots. What you need: Preferably Ubuntu 12.04 precise pangolin found here http://releases.ubuntu.com/precise/ use desktop cd image PC (intel X86) Desktop CD, Pendrive Universal USB installer found here http://www.pendrivelinux.com/universal-usb-installer-easy-as-1-2-3/ , a USB flash drive between 4-6 gigs.
Select 12.04 desktop from the dropdown in Universal Usb installer, select your usb by drive letter , select format, drag bar for persistent to 1500 mgs or so, then click create, when finished eject cruiser safely, unplug usb flash drive, shutdown computer, insert usb flash drive, power on computer, it will auto boot at startup on Windows 7 but XP takes more work for instance on my XP machine at first boot splash hit escape for advance startup options, then F9 for boot menu, then scandisk cruiser or whatever your USB is by name, it will then boot ubuntu without installing on your Windows machine.
when booted into Ubuntu: setup your network connection, download Soupkit move it from its containing folder to the desktop, right click select extract here, open folder, double click on the file marked installer, select run in terminal, select option 1 in terminal menu, hit enter for sudo password prompt as there isn`t one, when its finished working it will return you to the main menu, select option 2 it will detect a 32 bit operating system and skip the work for 64 bit then it will launch Soupkit, close all open windows, click the gear icon upper right, select restart, If on windows 7 it will simply restart the Ubuntu system, if on Xp hit Esc. at first computer splash, then select again the cruiser reboot is not near a clean an action on XP sadly.
When booted back back to Ubuntu open a terminal Ctrl+alt+t type soupkit.sh in the terminal now you can use all the features of Soupkit if everything went right and communication has been established with the Kindle.
Soupkit thread http://forum.xda-developers.com/showthread.php?t=1850038
Thepooch said:
You install Soupkit onto a live usb that is running ubuntu with persistent. The persistent allows the live usb to save data between reboots. What you need: Preferably Ubuntu 12.04 precise pangolin found here http://releases.ubuntu.com/precise/ use desktop cd image PC (intel X86) Desktop CD, Pendrive Universal USB installer found here http://www.pendrivelinux.com/universal-usb-installer-easy-as-1-2-3/ , a USB flash drive between 4-6 gigs.
Select 12.04 desktop from the dropdown in Universal Usb installer, select your usb by drive letter , select format, drag bar for persistent to 1500 mgs or so, then click create, when finished eject cruiser safely, unplug usb flash drive, shutdown computer, insert usb flash drive, power on computer, it will auto boot at startup on Windows 7 but XP takes more work for instance on my XP machine at first boot splash hit escape for advance startup options, then F9 for boot menu, then scandisk cruiser or whatever your USB is by name, it will then boot ubuntu without installing on your Windows machine.
when booted into Ubuntu: setup your network connection, download Soupkit move it from its containing folder to the desktop, right click select extract here, open folder, double click on the file marked installer, select run in terminal, select option 1 in terminal menu, hit enter for sudo password prompt as there isn`t one, when its finished working it will return you to the main menu, select option 2 it will detect a 32 bit operating system and skip the work for 64 bit then it will launch Soupkit, close all open windows, click the gear icon upper right, select restart, If on windows 7 it will simply restart the Ubuntu system, if on Xp hit Esc. at first computer splash, then select again the cruiser reboot is not near a clean an action on XP sadly.
When booted back back to Ubuntu open a terminal Ctrl+alt+t type soupkit.sh in the terminal now you can use all the features of Soupkit if everything went right and communication has been established with the Kindle.
Soupkit thread http://forum.xda-developers.com/showthread.php?t=1850038
Click to expand...
Click to collapse
wow! thanks so much. incredibly detailed. I'm currently waiting to get my hands on a usb/hard drive that has more than 2gb. I'll keep you posed if I run into any trouble.I love this forum
Thepooch said:
You install Soupkit onto a live usb that is running ubuntu with persistent. The persistent allows the live usb to save data between reboots. What you need: Preferably Ubuntu 12.04 precise pangolin found here http://releases.ubuntu.com/precise/ use desktop cd image PC (intel X86) Desktop CD, Pendrive Universal USB installer found here http://www.pendrivelinux.com/universal-usb-installer-easy-as-1-2-3/ , a USB flash drive between 4-6 gigs.
Select 12.04 desktop from the dropdown in Universal Usb installer, select your usb by drive letter , select format, drag bar for persistent to 1500 mgs or so, then click create, when finished eject cruiser safely, unplug usb flash drive, shutdown computer, insert usb flash drive, power on computer, it will auto boot at startup on Windows 7 but XP takes more work for instance on my XP machine at first boot splash hit escape for advance startup options, then F9 for boot menu, then scandisk cruiser or whatever your USB is by name, it will then boot ubuntu without installing on your Windows machine.
when booted into Ubuntu: setup your network connection, download Soupkit move it from its containing folder to the desktop, right click select extract here, open folder, double click on the file marked installer, select run in terminal, select option 1 in terminal menu, hit enter for sudo password prompt as there isn`t one, when its finished working it will return you to the main menu, select option 2 it will detect a 32 bit operating system and skip the work for 64 bit then it will launch Soupkit, close all open windows, click the gear icon upper right, select restart, If on windows 7 it will simply restart the Ubuntu system, if on Xp hit Esc. at first computer splash, then select again the cruiser reboot is not near a clean an action on XP sadly.
When booted back back to Ubuntu open a terminal Ctrl+alt+t type soupkit.sh in the terminal now you can use all the features of Soupkit if everything went right and communication has been established with the Kindle.
Soupkit thread http://forum.xda-developers.com/showthread.php?t=1850038
Click to expand...
Click to collapse
Thanks so much again.
Quick question ( i hope). I've been trying to use soupkit according to
the elaborate details listed above. One issue I have been
encountering making the entire process difficult is that my kindle
fire continues to reboot on its own every 30 seconds or so, making it
impossible to install certain programs. I (apparently) ave twrp and
fff installed according to soupkit but I find that I am unable to put
update.zip into the /sd because the KF restarts. Any suggestions how
to make it more stable and stop restarting randomly?
I think you need to charge your battery. Kindles can behave like this when they need charging.
Sent from my Amazon Kindle Fire using xda app-developers app
unstopable96 said:
Thanks so much again.
Quick question ( i hope). I've been trying to use soupkit according to
the elaborate details listed above. One issue I have been
encountering making the entire process difficult is that my kindle
fire continues to reboot on its own every 30 seconds or so, making it
impossible to install certain programs. I (apparently) ave twrp and
fff installed according to soupkit but I find that I am unable to put
update.zip into the /sd because the KF restarts. Any suggestions how
to make it more stable and stop restarting randomly?
Click to expand...
Click to collapse
I would not attempt to run update.zip this is a very bad idea when your device keeps rebooting and a possible flat battery. Put it in recovery and plug it to the wall charger till you battery is 100%.
Thepooch said:
I would not attempt to run update.zip this is a very bad idea when your device keeps rebooting and a possible flat battery. Put it in recovery and plug it to the wall charger till you battery is 100%.
Click to expand...
Click to collapse
I've charged the KF but no success. For some reason, now I cannot even get past the bootup screen where the classic white and orange 'kindle fire' logo glows. I don't know what to do. The problem I'm running into is that soupkit can't recognize a kindle plugged into the computer. As a result, I can't update, install or fix anything. Any suggestions on how to make soupkit work with this frozen system?
Hey guys. So I have the same problem like this guy. My situation is, It is rooted, has no OS, and it can communicate with my computer. I have tired to re-root it but nothing. The thing is that when i turn it on, TWRP works but, when it is rebooting it does not continue from that screen. It freezes with the Kindle Fire logo with Fire blue and booting in the bottom. Is there anything I can do or is there something i miss in the other posts?
unstopable96 said:
I've charged the KF but no success. For some reason, now I cannot even get past the bootup screen where the classic white and orange 'kindle fire' logo glows. I don't know what to do. The problem I'm running into is that soupkit can't recognize a kindle plugged into the computer. As a result, I can't update, install or fix anything. Any suggestions on how to make soupkit work with this frozen system?
Click to expand...
Click to collapse
In SoupKit, if you still have the stock bootloader installed, just choose an option and follow the instructions...even if it still says "offline".
potatos13324 said:
Hey guys. So I have the same problem like this guy. My situation is, It is rooted, has no OS, and it can communicate with my computer. I have tired to re-root it but nothing. The thing is that when i turn it on, TWRP works but, when it is rebooting it does not continue from that screen. It freezes with the Kindle Fire logo with Fire blue and booting in the bottom. Is there anything I can do or is there something i miss in the other posts?
Click to expand...
Click to collapse
Wipe system and factory reset then reinstall your ROM.
"That's a special kind of stupid. The kind that makes me laugh."
Ok I have a backup of 8.0 on a usb flash drive before I upgraded to 8.1 which I loved. I am very tech savvy and have flashed lots of roms, comfortable with Reg edits and hacks. I think I went too far now...
I remember a boot speed boost tweak I read on the internet which I thought I would try on my vivo tab. I ran msconfig and went to the boot menu. I checked No GUI boot and then went to advanced options and selected in number of processors - 4 (as it's a tegra quad core) and maximum memory as 2gig, I applied, got a warning message about bitlocker which was fine as I have recovery key and rebooted.
However.... upon starting I get Preparing Automatic Repair message, then Diagnosing PC message, then Your PC did not start correctly. So I click on Advanced options and have tried every option possibly listed. I used the Windows 8 recovery image in my usb drive to refresh, repair, reset, and nothing works. Says install media and I do and says not correct media. Unless it is expecting 8.1 backup which I don't have. I thought anyone could revert to 8.0 anyway.
So matter what I try I cannot get it to start. If only I could undo those boot changes. Maybe via command prompt?
Any help greatly appreciated.
tboy2000 said:
Maybe via command prompt?
Click to expand...
Click to collapse
Yes. Boot to command prompt mode, then extract the WinRT 8.0 WIM file from USB over the drive C:\ with the "dism /apply-image /imagefile:e:\...\your_recovery.wim /index:1 /applydir:c:\"
I'd recommend to format c: before doing this. Obviously you'll lose all your data.
You may also need to edit boot options with bcdedit.
If you have the 8.0 recovery image, you'll need to actually boot from the USB stick directly. I think that this is due to the invalidation of 8.0 signatures that happened in 8.1. I only know how you do this with Surface RT: with the USB stick connected and the Surface off, hold volume down, then press and hold the power button until you see the Surface logo. It'll then take noticeably longer to boot, since it's reading off USB instead of the built-in SSD.
I don't know how different this procedure would be on an Asus Vivo Tab.
Ok I solved it by downloading a different recovery image to the one I had. Managed to install and boot by volume down button. Strange because my recovery image worked before. All running fine ?
However I then ran into another problem. All of a sudden after a reset I got an error saying "unable to reset your pc. A required hard drive partition is missing". What the heck I did nothing. Also when I tried to use bitlocker recovery key it said the hard drive is locked. Unlock the drive and try again.
So after some hours of research, I booted to command prompt and typed:
bcdboot
and then...
bcdboot c:\windows
and it said boot files copied successfully. I rebooted with fingers crossed and it WORKED!!!
?
tboy2000 said:
Strange because my recovery image worked before.
Click to expand...
Click to collapse
This may be due to you've reformatted your USB stick to NTFS, then copied there your recovery image, since UEFI can boot only from FAT32 disks.
Glad to see the joys of Windows troubleshooting isn't lost on their tablets.
I'm really considering moving from Android based tablets to Windows 8 tablets once the platform matures a little bit. They run so smoothly (tried a few out at my local Staples). The OS is basically built for touchscreen anyway.
EDIT: 8/1/13 - GOT IT BACK TO WINDOWS 8 RT! :victory:
Not sure how I did it but I did
Original Post: 7/27/13
Device: Asus Vivo Tab RT
Background: Wanted to try out windows 8.1. I'm not a hacker by any means but knew I needed to put the 8.0 recovery image on a USB flash drive so that I could return to 8.0 if I wanted.
Problem: I hate 8.1 and need to go back to 8.0 ... yet, when I safe boot from the USB drive (by holding down the volume button when I press power) and click "troubleshoot" -> "reset" it goes through the motions and gives me an error saying
Unable to reset your PC. A required drive partition is missing
Click to expand...
Click to collapse
Question: What am I doing wrong?
Please help :crying:
When you made the recovery image, did you select the full backup one?
Myriachan said:
When you made the recovery image, did you select the full backup one?
Click to expand...
Click to collapse
Seem to be this case. How much you recovery drive used. If it < 512 MB that mean you create a recovery drive without checked "Copy the recovery partition from the PC to the recovery drive." It can use to boot device, some of boot menu and tool but can't reinstall OS.
Just for the future, pre releases can be buggy and unstable, you don't mess with them unless you know what you are doing.
Myriachan said:
When you made the recovery image, did you select the full backup one?
Click to expand...
Click to collapse
hisoft said:
Seem to be this case. How much you recovery drive used. If it < 512 MB that mean you create a recovery drive without checked "Copy the recovery partition from the PC to the recovery drive." It can use to boot device, some of boot menu and tool but can't reinstall OS.
Click to expand...
Click to collapse
I followed the exact steps in this Microsoft article when creating my USB recovery image (http://www.microsoft.com/surface/en-us/support/storage-files-and-folders/create-a-recovery-drive)
To create a USB recovery drive for your Surface
Make sure your Surface is plugged in and connected to power.
1.Insert your external USB drive into the USB port on your Surface.
2.Swipe in from the right edge of the screen, and then tap Search.
(If you're using a mouse, point to the upper-right corner of the screen, move the mouse pointer down, and then click Search.)
3.Enter Recovery in the search box, tap or click Settings, and then tap or click Create a recovery drive.
4.Tap or click Yes in the User Account Control dialog box to allow the recovery drive tool to open.
5.When the recovery drive tool opens, make sure the box is checked next to Copy the recovery partition from the PC to the recovery drive. Then, tap or click Next.
6.Select the USB drive you would like to use for your recovery disk by tapping or clicking on it. Tap or click Next.
7.Tap or click Create. The recovery image and necessary recovery tools will be copied to your USB drive. Your Surface must stay awake during the copy process, which will take 10-15 minutes.
8.When the recovery tools are copied, do one of the following:
If you want to keep the recovery tools on your Surface, tap or click Finish.
-Or-
If you want to remove the recovery tools from Surface and free up disk space, tap or click Delete the recovery partition. To confirm, tap or click Delete. This will free up approximately 3.5 GB of storage space on your Surface RT or approximately 7 GB on your Surface Pro. When the removal is complete, tap or click Finish.
Warning If you choose to delete your recovery partition, you will need your USB recovery drive to refresh or reset your Surface in the future.
9.Eject and remove your USB drive. This is now your Surface recovery drive, so keep it in a safe place and do not use it to store other files or data.
Click to expand...
Click to collapse
I even went ahead and downloaded the entire Asus Vivo RT recovery files on a different brand new flash drive from here (http://forum.xda-developers.com/showthread.php?t=2165831) and did the whole going into safe mode trying to reset, knowing for sure that I have the right files, but my Vivo RT still gives me the same "unable to reset your pc. a required drive partition is missing" error
I tried the above files both zipped and unzipped, made no difference :crying:
I even tried doing what this person did here (http://forum.xda-developers.com/showthread.php?p=43952563#post43952563) by going into command prompt and typing what he did but it didn't work.
What can I do?
I have not done this in a while, but I think that when you select recover it asks whether you want to repartition. I wish I could help, but my knowledge of this is limited.
Same thing happened to me - I've just downloaded a copy of the recovery knocking around the forums and I'm going to try with that...
Naffets said:
Same thing happened to me - I've just downloaded a copy of the recovery knocking around the forums and I'm going to try with that...
Click to expand...
Click to collapse
If you get it to work can you come back to let me know how you did it pls?
ap3604 said:
If you get it to work can you come back to let me know how you did it pls?
Click to expand...
Click to collapse
Downloaded a EN-GB recovery
formatted a pendrive with fat32
extracted iso of recovery onto root of pendrive
reboot into recovery (startup with vol down held down)
enter bitlocker key if asked
goto advanced
reset pc
"target os" = whatever version of windows you are on, not want to be on
run through the steps onscreen, it'll work fine..
Not sure why it worked today of all days but I was able to get my Asus Vivo Tab back to regular windows RT :victory:
1) Plugged in USB drive (which had the following 5 things on it from recovery image process which took up 2.78gb)
- boot folder
- efi folder
- storage folder
- bootmgr.efi
- reagent
2) Turned off computer
3) Turn on computer into safe mode by holding down volume button
4) Clicked U.S. keyboard
5) Clicked advanced
6) Clicked reset
7) Clicked on the windows 8.1 preview tile (not sure why it had the name windows 8.1 preview but it was in fact the regular windows 8 RT recovery image - later once windows 8 RT was back to normal I checked this process again and the tile now said windows RT)
I can guarantee I did these same steps above around 30 times when this problem first occurred and the windows 8.1 preview tile would not show up on step 7. Strange.
Either way I'm just happy to have my computer back to windows 8 RT :victory:
The trackpad was reversed and the scrolling speed on windows 8.1 preview was horrible and made me want to throw the thing through a ****ing window
ap3604 said:
Not sure why it worked today of all days but I was able to get my Asus Vivo Tab back to regular windows RT :victory:
1) Plugged in USB drive (which had the following 5 things on it from recovery image process which took up 2.78gb)
- boot folder
- efi folder
- storage folder
- bootmgr.efi
- reagent
2) Turned off computer
3) Turn on computer into safe mode by holding down volume button
4) Clicked U.S. keyboard
5) Clicked advanced
6) Clicked reset
7) Clicked on the windows 8.1 preview tile (not sure why it had the name windows 8.1 preview but it was in fact the regular windows 8 RT recovery image - later once windows 8 RT was back to normal I checked this process again and the tile now said windows RT)
I can guarantee I did these same steps above around 30 times when this problem first occurred and the windows 8.1 preview tile would not show up on step 7. Strange.
Either way I'm just happy to have my computer back to windows 8 RT :victory:
The trackpad was reversed and the scrolling speed on windows 8.1 preview was horrible and made me want to throw the thing through a ****ing window
Click to expand...
Click to collapse
Glad you got it sorted mate! High five!!!
I didn't like 8.1 purely due to lack of Jailbreak...why can't we run ARM compiled desktop apps natively?! It's daft!
ap3604 said:
7) Clicked on the windows 8.1 preview tile (not sure why it had the name windows 8.1 preview but it was in fact the regular windows 8 RT recovery image - later once windows 8 RT was back to normal I checked this process again and the tile now said windows RT)
Click to expand...
Click to collapse
It's not asking which recovery image you want to use - it's asking which Windows installation/partition you want to wipe to recover. That's why it showed 8.1 despite being the 8.0 recovery image. =^-^=
Finally, I managed to restore Asus Vivotab RT back to Windows 8.0 RT.
Here are some final clues that helped me:
1. Do press volume down much longer, even after device vibrated after pressing power button.
2. My device recognized USB flash recovery only when connected to tablet part (without dock) using adapter (which comes with the device).
The device booted from USB also when connected to the dock, but then after it freezes so you can't press/tap any item on screen.
Big thanks for everybody who helped to restore the device.
P.S.: Don't forget to press Thanks to the topic owner and to the guy who posted recovery files http://forum.xda-developers.com/showthread.php?p=38465868
Hi there. i've downloaded the restore files that you are mentioning from the forum but I can't locate the storage folder that you are reffering. Can you help me? Thanks in Advance
I have successfully managed to get vhdboot to work on my surface rt, using a seperate external USB hard drive.
The annoying thing was trying to figure out why setup bombed out, but I got past that!
You'll want a brand new drive, or anything where you have nothing to lose, as you need to repartition and reformat the USB hard drive you want to use.
1) Follow this technet article: hxxp://technet.microsoft.com/en-GB/library/hh825686.aspx#RecommendedConfiguration - to set up the partition layout and assign drive letters to the partitions. Remember to update the partition sizes as suits your hd. You don't need to follow the part about the recovery image.
2) Create a new vhd on drive W: (going by the drive letters in that technet article!) and mount it. Use diskpart or computer management.
3) Prepare the install.wim of whatever build of Windows RT you wish to install (add your driver pack using dism). Remember that the build of Windows RT you want to use needs to be signed with the PRODUCTION certificates, NOT the test ones, otherwise secureboot won't let it run! (if you're using any public preview or RTM, then you don't need to worry as it's obviously signed with the prod certs)
4) Apply the new install.wim to the vhd using dism.
5) bcdboot W:\windows /s S:
6) With your initial Windows RT install running, insert the drive into your Surface RT. Boot from that usb drive (use a reboot, not holding volume down). It should go right into second stage setup.
7) When it reboots again, make sure to boot to your initial RT install, then reboot back into the USB. If you get a BSOD here, and you have rebooted into the usb drive from a running Windows RT, you might need to mount the SYSTEM hive of the VHD (Windows\System32\config\SYSTEM) and change HKLM\[mounted SYSTEM hive]\ControlSet001\services\FsDepends\Parameters\VirtualDiskExpandOnMount from 1 to 4.
8) After rebooting successfully, third stage setup and oobe should go without a hitch.
After installation, remember you need to boot to your initial Windows RT install on C: and then reboot to the USB, not boot from USB by holding down volume down, or you'll most likely get a BSOD. I'm still not sure what causes the BSOD, and if you wanted you just install WinRT raw on the hd, instead of inside a vhd, there'd probably be no BSOD issues.
It's been a while since I last set up another VHD install on my surface RT, but if you have questions or problems reply and I'll do my best to help you!
Hi All, sorry this is a fairly long post.
i recently "Upgraded" my SM-P605 to Android 9 and it has been working fine.
i have, however, been experiencing connectivity issue with file transfer via USB.
i have tried several cables (3 Genuine) including a brand new "Generic" cable and keep getting the "device descriptor request failed" error.
i have also tried multiple PC's, loaded all recommended Samsung drivers and finally relented and replaced the USB port in the tablet itself, which still did not fix the problem.
Convinced after all of this it must be software related, i then decided to re-install and earlier version of Android which i copied over to the Tablets internal memory.
i logged into TWRP and wiped the tablet ready to reinstall Android 7. and when i tried it says the zip file is corrupted.
i now have a tablet that wont load the zip file i have, wont read from an SD card in the tablet or OTG (via TWRP) and is unable to connect to a PC via a usb cable..
if anyone could offer any suggestions i would be extremely grateful as i dont want to "Dump" this tablet as i use it daily for work..
Why it does not read the SD card? I would expect that should work and should be the safest bet here...
-Maybe the zip file really is corrupt, which can be easily told by unpacking via pc.
-If the tablet can still charge the battery usb is most likely okay.
-Sdcards can fail by becoming read-only. Most easy to tell by unsuccessfully trying to format them in the tablet or pc , but e. g. under Windows you seemingly can successfully delete and copy stuff, everything as it should even after forced refresh via F5. But after reinserting the card or rebooting the previous state is back.
-ADB has been enabled in developer settings? Then you normally get a notification where you can modify usb mode. Charge-only won't work, but most of the rest should do (Dcim/mtp/msp...) .
-And all the time Windows has to recognize the device via PnP and auto-install drivers for the current usb mode. Besides the aforementioned storage drivers for flashing and communication a modem driver and virtual COM ports must be auto-installed.
In this department i had lots of trouble with a phone based on an old TI OMAP SoC under any Windows newer than seven. Only Download mode invoked on the phone itself was still working and only zseful to restore stock rom, while in the more flexible Fastboot mode the phone wasn't recognized by Windows.
Samsung devices seem to support Fastboot only, but call it Download mode.
To come to an end, if everything fails i'd recommend to install stock rom in "download recovery" (Fastboot?) mode via Kies. If this also fails try to put the P605 manually into Download mode (Power and Volume minus or plus), no need to press home button, as often advised. After this, work your way back to Twrp, custom rom and root.
@crwzar80
Try connecting the tablet to a Windows 7 PC/laptop, making sure it's on an Administrator account (so it can autoload/download needed stuff). Not Windows 10 or even 8.1, but Windows 7.
I had the same problem a while back ago; if your attempt with this method succeeds then report back; I had an unconfirmed hypothesis about this issue.