Related
Hey everyone! Not a huge poster here however, I've been watching the threads in this forum for the past week or so awaiting root and attempting root myself. After days of attempts I have finally achieved root! I will lay down some of the specifics of what I was working with here and then give some helpful tips that will hopefully help others.
Computer OS - Windows 7 64bit (Installed HTC Sync previously and SDK)
Phone - Hboot .77 (Installed OTA accidently last week) w/ Kingston 2gb microsd
For days I had been trying every single method that I had come across and here is what had worked for me.
**Combined methods from other XDA forum members**
Power off phone with usb plugged in (usb debugging enabled previously)
Ran a batch file called root.bat that I made to run in command prompt consisting of the following (I ran this file before I turned on the phone)
:hello
adb shell
GOTO Hello
Click to expand...
Click to collapse
Hold the optical trackpad button while powering on
Press power once to enter fastboot
Wait for the fastboot to check the sdcard
Press volume down to highlight recovery
Press power to select recovery
Clicked the sdcard in and out
Eventually I entered the recovery screen on the incredible and the command window running my root.bat kept saying
- exec '/system/bin/sh' failed: No such file or directory (2) -
Click to expand...
Click to collapse
I pressed control-C then Y to end the batch file and continued on with the methods listed here
androidforums.com/all-things-root-incredible/98180-prs-complete-rooting-guide.html
Click to expand...
Click to collapse
**KEY NOTES**
I had been cracking at this for the past few days and had plugged the usb from my incredible into the BACK of the computer instead of the front and the FIRST TIME I had done this I was able to obtain root and adb recovery had worked (These are usb ports that are DIRECTLY connected to the mobo and this might have been a huge impact in my success)
Also, I kept running across my drivers detecting my phone in recovery as disk drives so I used the method here
addictivetips.com/windows-tips/how-to-disable-automatic-driver-installation-in-windows-vista/
Click to expand...
Click to collapse
To uninstall the disk drives and the USB Mass storage device and prevent them from automatically installing everytime I uninstalled. Then I went ahead and did a "Update driver manually" and pointed it to the drivers in SDK\USB
One trick I just did that seemed to work was I booted the phone and went into recover (black screen with the red logo). At that point, Device Manager showed two HTC devices listed under 'disk drives'. I uninstalled both of those devices, pulled the battery, popped it back in and went in with down arrow+power. At that point Windows loaded the 'Android 1.0' driver unsuccessfully. Uninstalled that from Device Manager, then did the down arrow + power (and held it down) to go into the black recover screen and *poof* it loaded.
I'm using Windows 7 32bit.
quagmire0 said:
One trick I just did that seemed to work was I booted the phone and went into recover (black screen with the red logo). At that point, Device Manager showed two HTC devices listed under 'disk drives'. I uninstalled both of those devices, pulled the battery, popped it back in and went in with down arrow+power. At that point Windows loaded the 'Android 1.0' driver unsuccessfully. Uninstalled that from Device Manager, then did the down arrow + power (and held it down) to go into the black recover screen and *poof* it loaded.
I'm using Windows 7 32bit.
Click to expand...
Click to collapse
WOW. N1. Proof that worrying about drivers is pointless!
rynosaur said:
WOW. N1. Proof that worrying about drivers is pointless!
Click to expand...
Click to collapse
I think that to an extent it doesn't matter.
It seemed to refuse to work with me if the drivers were being loaded at disk drives. Therefore if the drivers weren't loaded at all and there was nothing installed it could work and if the CORRECT drivers were installed then it would work. But again, for me in my experience it was refusing to work if it had the disk drives were installed as the drivers for recovery.
kentoe said:
I think that to an extent it doesn't matter.
It seemed to refuse to work with me if the drivers were being loaded at disk drives. Therefore if the drivers weren't loaded at all and there was nothing installed it could work and if the CORRECT drivers were installed then it would work. But again, for me in my experience it was refusing to work if it had the disk drives were installed as the drivers for recovery.
Click to expand...
Click to collapse
Ok, but if you look at Unrevoked's newest DIY post, they show a logcat which starts at a card check and ends at adb starting, a five second gap. This is internal stuff, not going to the host/usb -- at least not listed in the logcat. If this exploit depended on host intervention at all, I'm guessing someone would have written a linux or windows script/program to talk to the DI. Rather, all the PC can do is try to open an adb session, it's like knocking at a door -- you can't make the person home no matter how well or correctly you knock, you just hope they'll answer.
When I obtained adb shell, had all three devices show up in Device Manager: ADB Composite (I used the API 8 driver), Generic Volume G:\ and Generic Volume H:\ -- drive letter specific to my windows install, of course. All hands were on deck. The glitch happens between the software, hardware and sdcard.
In any case, I'm glad you were successful!
rynosaur said:
Ok, but if you look at Unrevoked's newest DIY post, they show a logcat which starts at a card check and ends at adb starting, a five second gap. This is internal stuff, not going to the host/usb -- at least not listed in the logcat. If this exploit depended on host intervention at all, I'm guessing someone would have written a linux or windows script/program to talk to the DI. Rather, all the PC can do is try to open an adb session, it's like knocking at a door -- you can't make the person home no matter how well or correctly you knock, you just hope they'll answer.
When I obtained adb shell, had all three devices show up in Device Manager: ADB Composite (I used the API 8 driver), Generic Volume G:\ and Generic Volume H:\ -- drive letter specific to my windows install, of course. All hands were on deck. The glitch happens between the software, hardware and sdcard.
In any case, I'm glad you were successful!
Click to expand...
Click to collapse
Ahh, okay. Well whatevs, yeah I'm glad I'm rooted now! =D It was probably the connection with the front usb ports vs the back usb ports on my computer since the back are directly on the mobo. It worked the first time I switched it to the direct USB ports.
So glad I got lamppu, wifi tether, and removed city id along with obtaining titanium backup!
I was also trying to get root for a few days and had some issues. I eventually got in on my 4th MicroSD card try- which was a junky 1GB that wasn't even labeled for speed...
I tried a16GB Class 2, 8GB class 4, 4GB class 4 and none would stay with 'device not found'- even after trying for 20+ times on each. My next step was to buy a class 6, but a random 1GB I had laying around worked. It connected after the 1st attempt with the 1GB card.
Another note- I got the '/system/bin/sh' message about 30 seconds after it went into recovery mode- not right at the start as I see it happening in the videos.
Easiest way is to yank the battery and start over if you don't get it; I used the vol down + power start up option.
Nothing worked for me. Tried all methods with lots of cards.
Stock SanDisk 2gb C4
Lexar 8gb C4
Lexar 8gb C6
DaneElec 4gb C4 (same as PNY 4/4 and Kingston 4/4)
As I was about to put my Inc for sale on Ebay. NiX threw out a suggestion on IRC. I tried it w/ the DaneElec and it worked.
It worked first try and every try since. Tried it with the stock sandisk 2/2 and no go. Haven't tried the Lexars.
Give it a shot. Good luck.
loop shell / Vol- + Power. / Hboot / wait for 4secs / insert card / highlight recovery / hit power + count to 3 or 5 and insert usb / wait till 10secs after /!\
Thanks OP - Using the oldest/slowest card I have (old 1gb Corsair card formatted Fat32), enabling the driver local policy you mentioned, pulling the battery while phone was on, and the eject method described above - I finally got in. I have no idea if it was pure luck or if it had anything to do with the above, but yours was the last thread I read so you get a thanks.
**EDIT**
After trying to get back in after realizing I needed to remove any apps before rebooting, I once again have zero luck getting in... so I'm leaning towards the complete chance/luck idea.
seanmcd72 said:
Thanks OP - Using the oldest/slowest card I have (old 1gb Corsair card formatted Fat32), enabling the driver local policy you mentioned, pulling the battery while phone was on, and the eject method described above - I finally got in. I have no idea if it was pure luck or if it had anything to do with the above, but yours was the last thread I read so you get a thanks.
Click to expand...
Click to collapse
You're welcome! I'm glad my information has helped!
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."
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
Wondering if any of you guys can advise me - having strange problems with fastboot (windows 8.1 and Zenfone 2 ze550ml). Wanted to flash the pre-rooted image to my device so downloaded it and extracted to the flashtools folder and renamed system.img then hooked up my phone. Checked adb drivers were installed and adb devices command returns a code string, so assumed all was good to go with flashing. However, on entering any fastboot command it just sits at "waiting for device". Tried manually starting the phone in fastboot and then connecting it, and this did enable me to execute fastboot commands (reboot or reboot-bootloader work). However, fastboot flash system system.img just results in a message about file size and then "failed to load system.img"
kanagawaben said:
Wondering if any of you guys can advise me - having strange problems with fastboot (windows 8.1 and Zenfone 2 ze550ml). Wanted to flash the pre-rooted image to my device so downloaded it and extracted to the flashtools folder and renamed system.img then hooked up my phone. Checked adb drivers were installed and adb devices command returns a code string, so assumed all was good to go with flashing. However, on entering any fastboot command it just sits at "waiting for device". Tried manually starting the phone in fastboot and then connecting it, and this did enable me to execute fastboot commands (reboot or reboot-bootloader work). However, fastboot flash system system.img just results in a message about file size and then "failed to load system.img"
Click to expand...
Click to collapse
You need to rename the system image to system.img and put it where the fastboot file is. It's looking for it but can't find it.
No, don't think that is my problem - as I said I extracted it to the flashtools folder, so it is already where the fastboot file is. And anyway, though I'd like to solve the problem of flashing the system.img, I am kind of more interested in why I can't get past "waiting for device" without first manually entering the fastboot mode.
Cause Windows sucks. I'm on Linux and no issues. Maybe someone on Windows can chip in?
I can easily do a quick ubuntu install and try it that way if you think it might work better. At the weekend maybe. Could you give me some pointers on how to do it in linux if I do? Would be much appreciated!
kanagawaben said:
No, don't think that is my problem - as I said I extracted it to the flashtools folder, so it is already where the fastboot file is. And anyway, though I'd like to solve the problem of flashing the system.img, I am kind of more interested in why I can't get past "waiting for device" without first manually entering the fastboot mode.
Click to expand...
Click to collapse
I have encountered that problem with the "waiting for device" while I was flashing pre root rom.
Try the cmd adb devices
Then it will list the device connected to the computer...if it says not authorized, then you need to check the phone which is turned on and a pop up window with the RSA key and tap on trust this computer or something..
Then repeat adb devices and it should say allow or something..then it will allow you to flash.
(double check the commands online, I might missed something)
Nah, don't blame Windows... I flashed mine with Windows 10 and worked wonders.
Also... could it be that PC isn't USB 3.0? Perhaps system.img transfer is stopped somewhere during the copying phase?
Thanks, but actually the first time I tried it I did the adb devices command and authorised my pc on the phone. When I connect and do adb devices now it shows the string of numbers code for the device. However, still can't get past "waiting for device"
My pc has both usb 3 and usb 2 ports. Tried on all of them and with various different cables including the asus issued ones, all to no avail.
Can u post a pic of your flashtool folder?
Sent from my Nexus 7
Here is a snap of my platform-tools folder and cmd window
Did you manage to find a solution to this?
I updated the zenfone 2 via OTA to the latest system update.
Ive read and downloaded all relevant files to install the pre root img from the correct sources.
Now when I hold power + vol up. I can see the droid on its back. I choose the RECOVERY option and press power button to select.
When phone reboots it goes to droid icon and says installing system upgrade.................then error appears! No recovery mode!
All the correct drivers are installed into Windows 7, the phone asks me to allow RSA key connection to laptop.
Ive tried the flash tool installer 1.0.7 with phone connected and system img (renamed) and still nothing.
Anyone got any ideas?
Ive factory reset twice in a row and allowed debugging.
Ive placed the (renamed) system.img into the fastboot folder and tried the open command with line ' fastboot flash system system.img' and the reply is usually unable to read system.img or device waiting.
Ive installed the latest android sdk develppment kit and still unable to root using this pre root image.
Im familiar with android and how to follow instructions on rooting, but this zenfone 2 is mind boggling.
Thanks for reading. I know its someone else post. I didnt want to start a fresh post with the same dilemma.
Any advice on whats going wrong would be appreciated.
tsam19 said:
When phone reboots it goes to droid icon and says installing system upgrade.................then error appears! No recovery mode!
Click to expand...
Click to collapse
Hit power and vol up again, just really quickly. Don't hold it, just press and let go. Sometimes it takes several attempts.
hkdmjack, yes your right managed to do it at last.
Cheers
Hi guys, I am facing quite a difficult problem at the moment.
My friend has "accidentally" attempted to use an Asus Zenfone 5 rooting method to root his zenfone 2 550ML.
When I received it to take a look at it, I instantly noticed that I could not get into fast boot (or droidboot). I expected to see usual droid with text on the left side and also expected to be able to select from a number of options using the volume keys (i have some past experience), but instead am met with this solid usb logo. One like this: h ttp://zenfo ne-blog-forum.2 8820.n7.nabble.c om/file/n4 5/P_20140728_051139 .jpg (remove spaces)
I did some research, and found that there were many "bricked" zenfone 5's which were stuck on this usb logo, however this zenfone 2 can start up normally and be used throughout the day normally. Only when I try to enter fast boot, by either ADB commands or by power + volume up, I cannot get past the usb logo.
I have linked up the ZenFone to my computer, and confirmed that ADB devices correctly lists the device (I have usb debugging enabled), however, when I try to go to fast boot and am met with the usb logo, my computer does register and detect the phone, however, under device manager it has a yellow triangle with the device named "" MOOREFIELD". When the ZenFone 2 is in this usb logo state, I cannot access any fast boot commands. I am quite stumped at the moment.
Any help please? By the way, I use a windows 8.1 computer with usb 3 ports. However, I have tested using different cables, and on a windows 7 laptop with usb 2 ports, still to no avail. Should I try and update the firmware using Asus' software? Or is there a better solution?
Thanks
Edit: My friend claims that he did not see at any point in time, the flashing on the zenfone 2 start. He was faced with a "<waiting for devices>" or something similar message, telling me that the phone was not fully in fast boot yet. If I can get it into fast boot, I am sure I can reflash the custom stock onto the phone, and most issues will be resolved.
same error
i have the same error by my zenfone2 after update
please help
amohammadiazar said:
i have the same error by my zenfone2 after update
please help
Click to expand...
Click to collapse
Could you specify which update you did? From your computer? Or via Asus update on ur phone?
pkvk9122 said:
Could you specify which update you did? From your computer? Or via Asus update on ur phone?
Click to expand...
Click to collapse
my orginal firmware is CN and i wanted to change to WW mode i tried by pc .... now when i conect phone t pc it want moorefeild driver for conection and i dont have those ,,
Whenever I try to flash system.img it gets stuck on "writing 'system'..." and just hangs there. I have left it for over half an hour and it still didn't work. Does anyone know a solution to this problem?
Hey guys,
So after a while without any responses, I headed over to Asus customer service to receive a very unhelpful reply.
I gave up hope of finding an answer online and so I decided to take a leap of faith by updating the firmware via the Asus Update app on the phone.
I upgraded from 2.14 to 2.15 and miraculously fastboot seemed to have restored itself. I am not sure whether or not every single update restores fastboot, or whether the update to 2.15 does, but I'm glad that it has been fixed.
My previous problems of being unable to detect fast boot devices has been resolved. Hopefully others who have experienced the same issue can find this post helpful.
Hi,
I had a running N2AOS with CM12 install, then did a return2stock but something went wrong
I have orange/blue boot sequence and can get into TWRP without a problem, can boot into fastboot etc. from TWRP. Battery is 100% - ok, too
But system seems empty now. Maybe wiped wrong. I see a lot of empty folders incl. sdcard etc. I've basic ux knowledge - can use TWRP terminal or file manager.
Is there a chance pulling a rom in the twrp using the usb? On win 8.1 I can delete the adb/amazon drivers. then it gets recognized as "Kindle" or "Tate", but can't connect.
My primary system is macOS Sierra, but have a running windows 8.1/ubuntu laptop with usb 2/3.
I think I'm equipped perfectly and the KF7HD2 is not hard bricked, but leaking adb/kindle knowledge. and the most trys end up with "< waiting for device >"
update: when I try TWRP > mount (anything) it gets recognized by win 81 or ubuntu for a short time, but I can't read or write a thing
maybe someone could help?! I read and tried as much as possible, but don't want to kill my old kindle because my girlfriend wants to read with it
thank you very much!
best
tom
addition: can I connect via twrp console and usb or wifi to a local ip or sth to use ftpget
really nobody an idea?