Related
I'm having trouble getting this POS rooted. Got it unlocked with little problem, but now that it comes to rooting, it's extremely confusing to follow the tutorials. Is there any working one-click methods? I'm no stranger to Android OS, I had my Dinc2 rooted in about 5 minutes after unboxing. But this abomination is really working my nerves. Help please?
There is no "One-Click Root"
But rooting using the given instructions is not difficult at all.
Its as simple as downloading a few files, and typing a few codes.
what have you tried so far? and what firmware are you running?
Since you unlocked your bootloader,here is how you get Root
http://forum.xda-developers.com/sho...m.xda-developers.com/showthread.php?t=1130639
download the .img ,put it in your fastboot folder
download the rootxperia.zip to your SD card
Turn phone off,plug into your PC/Laptop and hold search button ( might take some tries) ,you should get BLUE LED
SHIFT+RIGHTCLICK on fastboot folder and open in command window (assuming your usiing vista/win7) and type
fastboot boot recoveryPLAY.img
wait 2 minutes,it takes time.
Apply zip from SDcard and you are rooted
Cat_On_Droid said:
Since you unlocked your bootloader,here is how you get Root
http://forum.xda-developers.com/sho...m.xda-developers.com/showthread.php?t=1130639
download the .img ,put it in your fastboot folder
download the rootxperia.zip to your SD card
Turn phone off,plug into your PC/Laptop and hold search button ( might take some tries) ,you should get BLUE LED
SHIFT+RIGHTCLICK on fastboot folder and open in command window (assuming your usiing vista/win7) and type
fastboot boot recoveryPLAY.img
wait 2 minutes,it takes time.
Apply zip from SDcard and you are rooted
Click to expand...
Click to collapse
the wait for recovery to load is HORRIBLE!! lol. push the menu button once in a while if you are unsure. i did. it makes the wait (for me) less painful but installing the .zip and rebooting successfully with a rooted phone is AWESOME!!
Thanks for simplifying it for me Cat. I'm sitting here with my blue LED, my blank screen and my command window that now says "waiting for device" so that's what I'm doing. Waiting. Smoke break time.
chattguy said:
Thanks for simplifying it for me Cat. I'm sitting here with my blue LED, my blank screen and my command window that now says "waiting for device" so that's what I'm doing. Waiting. Smoke break time.
Click to expand...
Click to collapse
God this is painful. It's doing nothing. Should I unplug and try it again? it's been over 10 minutes.
chattguy said:
God this is painful. It's doing nothing. Should I unplug and try it again? it's been over 10 minutes.
Click to expand...
Click to collapse
are you sure that you installed the "S1Boot Fastboot" driver completely ?
cause i had some problem like yours ... just go to my computer=> right clik => manage=> devicce manager
and check if it's already install or not (( other devices ))
mehdi.moha said:
are you sure that you installed the "S1Boot Fastboot" driver completely ?
cause i had some problem like yours ... just go to my computer=> right clik => manage=> devicce manager
and check if it's already install or not (( other devices ))
Click to expand...
Click to collapse
Sony Ericsson sa0102 is installed, but I'm not seeing anything in my device manager about S1 Fastboot. Hmm...how would one go about installing it? I have the fastboot folder on my desktop. It has two subfolders, Fastboot and USB_drivers .
chattguy said:
God this is painful. It's doing nothing. Should I unplug and try it again? it's been over 10 minutes.
Click to expand...
Click to collapse
In this case if it's either still 'waiting for device' or trying to boot recoveryPLAY.img, then you're safe to try again since nothing is being flashed
When connected next time, in fastboot mode, before booting the .img, type this:
fastboot devices 'enter'
It will show a list of devices attached.
It might be that your missing some drivers so fastboot is not working correctly and won't detect your device. Have you pc companion installed? I don't remember if there came any drivers with the fastboot download but check that, there might be some drivers you didn't install.
Regards Dousan...
This is what happens. I just get another prompt. Here's a screenshot of that, along with the drivers folder.
chattguy said:
This is what happens. I just get another prompt. Here's a screenshot of that, along with the drivers folder.
Click to expand...
Click to collapse
That means no device is connected. Unlike ADB, fastboot does not return the usuall "list of attached devices" line. Have you installed fastboot drivers?
Sent from my R800i using Tapatalk
AndroHero said:
That means no device is connected. Unlike ADB, fastboot does not return the usuall "list of attached devices" line. Have you installed fastboot drivers?
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
I don't know, I just installed what the guy told me to when he did the remote bootloader unlock. Fastboot IS in my device manager, however, it says there are no drivers installed. I've got the blasted things on my desktop with some DPInst.exe installer, but it says I need the 64-bit version, which I can't find. Microsoft tried to have me download some silly .ISO file but I really think there must be an easier way than to burn some DVD installation disk.
chattguy said:
I don't know, I just installed what the guy told me to when he did the remote bootloader unlock. Fastboot IS in my device manager, however, it says there are no drivers installed. I've got the blasted things on my desktop with some DPInst.exe installer, but it says I need the 64-bit version, which I can't find. Microsoft tried to have me download some silly .ISO file but I really think there must be an easier way than to burn some DVD installation disk.
Click to expand...
Click to collapse
Ok these are the x32/x64 fastboot drivers.
http://www.multiupload.com/0XZV1LXRVA
Download them and unpack them. Connect your device in fastboot mode. Then navigate to device manager on windows, Find the S1 Fastboot thats not installed correctly. go to update driver and navigate to the driver package you just unpacked. Done
AndroHero said:
Ok these are the x32/x64 fastboot drivers.
http://www.multiupload.com/0XZV1LXRVA
Download them and unpack them. Connect your device in fastboot mode. Then navigate to device manager on windows, Find the S1 Fastboot thats not installed correctly. go to update driver and navigate to the driver package you just unpacked. Done
Click to expand...
Click to collapse
Mother. Of. God.
I did it. No, f**k that, you did it. All of you, thank you so much. You guys really helped me out bigtime, without berating me and calling me a noob lol. I sincerely appreciate it.
Also a special thanks to Alejandrissimo for unlocking the bootloader. Without you, this wouldn't have even been possible. Yay this blasted phone is finally rooted...
...and nobody had to die in the process.
That's what we are all here for. Learning about things through each other. We were all without knowledge at one point
Sent from my R800i using XDA App
Ok, I am COMPLETELY lost and have read this forum here from start to finish and still have no idea how to fix my Kindle Fire.
http://forum.xda-developers.com/showthread.php?t=1428428
My KF is stuck at the "Kindle Fire" screen, not the triangle screen, or any other screen. I can shut it "off" and turn it "on" but it never gets past that screen. I have installed and tried to run "the Kindle Fire Unbrick Utility V1.1" and it always always always gets to the "waiting on device" part. I don't understand how to download or install new drivers or anything of that nature.
If someone could please give me a step by step guide on how to fix my problem that would save me a lot (more) hours of search and failure. I just want it back to normal (un-rooted) and I never should have rooted it in the first place. That was a HUGE mistake from someone who doesn't completely understand this stuff. Any help is greatly appreciated.
Bumpity bump bump.
Did you install the drivers using the kfu? Is your kindle showing up in device manager on your computer?
Sent from my SPH-D710 using xda premium
First thing....scrap the KFU. It's time to learn to use command line tools.
Plug your device into the computer, turned off.
Locate the folder that comes with KFU that has the files called "adb" and "fastboot" and place it on your desktop.
Open your command prompt and type:
cd Desktop/NameofFolderYouPlacedOnDesktop
Turn on your Kindle
In your command prompt type:
fastboot devices
If you see a bunch of numbers move on. If not, reinstall drivers and try again.
Then type:
fastboot -i0x1949 oem idme 4000
Hold down power button until device shuts off
It should restart normally
Then see this thread to find out why you did that:
http://forum.xda-developers.com/showthread.php?p=24039339
Sent from my Kindle Fire using xda premium
Let me know how it works out.
[EDIT:] The cool thing about the Kindle Fire is that its virtually unbrickable, short of screwing up the bootloader...which you didn't. So don't worry, its fixable.
If it works out for you and you want to re-root it, I can help you out so you don't get left in the dark. You might even learn something.
Sent from my Kindle Fire using xda premium
Thank you for the reply and assistance in this problem. I am stuck in the middle of the process. Maybe I am doing something wrong. My exact steps I am taking are listed below. To get into the command prompt I type into the "run" section of my computer "cmd" and then it opens up the command prompt.
-Plugged my KF into the desktop turned off
-Drag the entire folder called "tools" from the KU onto the desktop which has the "adb" and "fastboot" files.
-typed in "cd Desktop/tools" and now it shows this on the cmd C:\Users\myname\Desktop\tools>
-I then turn on my KF and type in "fastboot devices"
nothing shows up except C:\Users\myname\Desktop\tools>
-If I just type "fastboot" I get a whole explanation of commands I can input, but no numbers.
-To uninstall my driver and try agian I do the following: go to "device manager" and find my KF which is shown by an exclamation mark. Right click and "Uninstall" Rinse and repeat.
Should I be doing something differently? Thank you again for the help!
No, that's exactly what you should do. You need to get fastboot to connect. In order to do that your drivers need to be working.
Sent from my Kindle Fire using xda premium
Ok, should I just keep uninstalling and reinstalling the drivers until it works or is there another way to fix the driver problem?
When installing your drivers, did you make sure to choose "I'll select which drivers to install"?
Sent from my Kindle Fire using xda premium
I am clicking on the "install drivers" from the KF utility and then uninstalling from the "device manager" Guess there's more to this driver thing that I'm even more unaware about lol.
Ok , forget about the KFU for a second. Go to your device manager and select update driver.
Then select I'll choose which drivers to install
Browse to the tools folder on your desktop and select...I think it is called adb_driver.ini
Sent from my Kindle Fire using xda premium
There are no compatable drivers in the "tools" folder. The only one is in the KF utility under drivers and it is called android_winusb.
I am also experiencing a new problem... It is now in a constant state of quick restarts. It turns on, shows the KF start up screen for 4 or so seconds and then shuts down. It is doing this non-stop.
Ok go here and download and unzip this file:
http://downloadandroidrom.com/file/KindleFire/root/KindleFireRoot.zip
look for a file called adb_usb.ini
open it with text editor and type:
0x1949
then save and install it
---------- Post added at 01:48 AM ---------- Previous post was at 01:43 AM ----------
For your android_winusb.inf open it in text editor and make sure you have these 3 lines at [Google.NTx86] and [Google.NTamd64].
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
I had the same charging issue. B63 help me with this issue. Basically your kindle is not charging successfully. Try using the charger that came with the kindle. It worked for me.
Sent from my SPH-D710 using xda premium
Im no dev but this is what I did. Plug in your kindle and check if the drivers are installed. If your device shows up as unknown in device manager then that means the drivers are not installed. That's perfectly fine. Now unplug your kindle and power it off. Go to the kfu folder that you extracted and install drivers. Now plug in your device and it should automically power up and your device should show up as kindle in your device manager. If it is showing up go back to to the kfu folder and click run. After clicking the run button your device should show up as offline in adb status and unknown in boot status. That is perfectly fine. Now click on 1. Bootmode menu. Then click on 1 again which is Normal (4000). Your device should reboot after that. That's what worked for me. By the way I'm assuming your using kfu 0.9.5. Good luck and I hope this helps you.
Sent from my SPH-D710 using xda premium
It's working now!!! Thank you so much EVERYONE!!!
Now the next thing I am wanting to acomplish is "unrooting" it and restoring it to factory settings. How would I go about doing this? I don't think I have any recovery installed..
bjg020683 said:
Im no dev but this is what I did. Plug in your kindle and check if the drivers are installed. If your device shows up as unknown in device manager then that means the drivers are not installed. That's perfectly fine. Now unplug your kindle and power it off. Go to the kfu folder that you extracted and install drivers. Now plug in your device and it should automically power up and your device should show up as kindle in your device manager. If it is showing up go back to to the kfu folder and click run. After clicking the run button your device should show up as offline in adb status and unknown in boot status. That is perfectly fine. Now click on 1. Bootmode menu. Then click on 1 again which is Normal (4000). Your device should reboot after that. That's what worked for me. By the way I'm assuming your using kfu 0.9.5. Good luck and I hope this helps you.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Ugh so many questions to ask (I'm sorry)
1. "If your device shows up as unknown in device manager then that means the drivers are not installed." Mine does not show up as an unknown but it shows up as an android phone and when clicked it is "Android ADB Interface".
2. "your device should show up as kindle in your device manager." I installed the driver but it didn't show up as Kindle in device manager
3. "After clicking the run button your device should show up as offline in adb status and unknown in boot status"
ADB Status: Online
Boot Status: Unknown
4. When I clicked bootmode menu, and typed 1:
"The system cannot find the drive specified"
Sorry for these noobie questions but please help me
Okay guys here's the dealio-
I recently got my transformer prime and I *loved* it. It came pre-loaded with the .21 version of ICS, which can't be rooted as of now so I downgraded to stock .15 with a modified ViperMod and then rooted and installed CWM. Next, I installed the Gummy custom ROM onto my prime (still .15). Well, I started to experience some weird -probably ROM related- issues and I ended up deciding to flash back to stock. ...BIG MISTAKE on my part I found out! I used the modified ViperMod to flash back to the stock .15 and it ran through the process but stopped at the ASUS boot logo with the little loading circle going around and around and around. First I let it sit for a VERY long time-stuck on boot. Then, I tried turning it off and back on-stuck on boot. Next, I tried pushing down the little recovery button-stuck on boot. I tried booting into CWM, but obviously, since I flashed back to the stock .15, all I get is the android guy laying in his side with the red triangle.
I am really really hoping that this is not a hard brick because the error that people are describing is the tablet stuck in the screen with "EeePad" in the middle and then getting something about an "unrecoverable bootloader error". My tablet boots past the EeePad screen and there is no error message-just the endless loading circle.
I am hoping that one of you smart guys could have a clue on how to revive my tablet. Any help would be greatly appreciated, and maybe I can buy you a beer if you bring my baby back to life
Here is a picture of what it looks like (circle is still spinning):
http://img838.imageshack.us/img838/276/img20120322182429.jpg
so you can get into recovery? I saw you said you tried to flash cm9 again. if you caught in a bootloop, jemaine made a zip file you can flash to get you out of it. you have to search for it though in developement section. does your computer still recognize your prime when you hook it up to your computer? you may need to adb commands into prime.
good luck getting it back running.
demandarin said:
so you can get into recovery? I saw you said you tried to flash cm9 again. if you caught in a bootloop, jemaine made a zip file you can flash to get you out of it. you have to search for it though in developement section. does your computer still recognize your prime when you hook it up to your computer? you may need to adb commands into prime.
good luck getting it back running.
Click to expand...
Click to collapse
I no longer have cwm installed, it is just the stock recovery so I cannot install any .zip's. Also, when I plug the tablet in wile its on the Asus loading screen, the computer DOES recognize it. Maybe there is some way to get into it and reflash?
Any suggestions guys?
seanyuan62 said:
Any suggestions guys?
Click to expand...
Click to collapse
When you say your pc can see the prime can you see it with adb? If not go here:
http://forum.xda-developers.com/showthread.php?t=1426502
Once you have adb figured out you should be able to reflash recovery. See this thread:
http://forum.xda-developers.com/showthread.php?t=1576937
I used method 2. You will need to push the blob file to your prime using adb. Hope that helps.
Won't turn off and stuck on Boot screen PANIC!!!!
I'm running CM9 nightlies on my 64gb TF201 and have had no issues with it. I'm using GooManger and Teamwin for recovery and have not had any issues in that department either. Until now.
So 2 days ago a nightly was released that I flashed with out issues. The updated ROM however wanted to open the virtual keyboard when I started typing so I decided to revert back. I did this by just flashing an earlier released nightly. It went through the process and then restarted. The boot screen came on and then never left. If I try and turn it off it just restarts. I can't get it into recovery but I can get into fastboot. However I don't have a little Android symbol just the wipe data and USB. I don't have a backup on my computer that I can push through. I flashed CWM recovery through fastboot in hopes of then being able to get into recovery but with no luck. I used transformerprimerecovery.zip followed all the instructions got an "OK" and "finished" on CMD. At the same time the little progress bar on the TF showed that it did something but no change with my condition.
When I'm connected with fastboot it doesn't show up on my computer as I found to be expected. In device manager Android Phone is listed and when I click on it ASUS Android Bootloader Interface shows up stating device is working properly. If I open CMD and type "cd" it just replies C:\users\Josh>. I tried to wipe data to see if it would and it said it did but still no change. I've been reading for the past two days and haven't found the same set of problems yet. I've found similar issues but not all together.
Please if anybody has a suggestion for me I would be most Thankful. I've not had any luck with my searches
Thanks
Lifewithsuzy, try this, it's what I did when I screwed up my tablet, and it's helped a few others.
geo.z said:
Lifewithsuzy, try this, it's what I did when I screwed up my tablet, and it's helped a few others.
Click to expand...
Click to collapse
I haven't been able to try this yet for I seem to be having ADB issues. SDK is updated and current and I have the latest universal driver setup. I show up in device manager but not in the CMD prompt.
---------- Post added at 08:10 AM ---------- Previous post was at 07:44 AM ----------
I seem to be falling further down the rabbit hole. I mentioned above that I was able to flash CWM recovery via fastboot was not able to access it. I tried the same process with TeamWin recovery. It just stated that the specified path could not be found. So I'm losing features now.
lifewithsuzy said:
I haven't been able to try this yet for I seem to be having ADB issues. SDK is updated and current and I have the latest universal driver setup. I show up in device manager but not in the CMD prompt.
---------- Post added at 08:10 AM ---------- Previous post was at 07:44 AM ----------
I seem to be falling further down the rabbit hole. I mentioned above that I was able to flash CWM recovery via fastboot was not able to access it. I tried the same process with TeamWin recovery. It just stated that the specified path could not be found. So I'm losing features now.
Click to expand...
Click to collapse
When you are trying to flash anything in adb or in fastboot, put the file in the same folder as those .exe files. Manytimes it is a typing mistake on the path that kills you. Also remember to add the.zip at the end of the file name if applicable.
Gage_Hero said:
When you are trying to flash anything in adb or in fastboot, put the file in the same folder as those .exe files. Manytimes it is a typing mistake on the path that kills you. Also remember to add the.zip at the end of the file name if applicable.
Click to expand...
Click to collapse
No luck. I've tried rearranging all the files associated with adb and fastboot I can think of. I've opened the CMD window from about every file as well as from the start menu and I can't get CMD prompt to recognize the tablet. The tablet allows me to get to the point where it states that it is "starting fastboot USB download protocol". Device manager shows Android Phone > ASUS Android Bootloader Interface. And when I remove the device it shows it listed as "fastboot device". I'm stumped on getting into CMD and can't do anything until I do. It just stays on the boot screen until I force it off. And if I'm not holding down the volume up button when I do it, it just recycles on. I've found post regarding the boot screen locked on but everybody has been able to fix it through a properly functioning fastboot/ADB.
lifewithsuzy said:
No luck. I've tried rearranging all the files associated with adb and fastboot I can think of. I've opened the CMD window from about every file as well as from the start menu and I can't get CMD prompt to recognize the tablet. The tablet allows me to get to the point where it states that it is "starting fastboot USB download protocol". Device manager shows Android Phone > ASUS Android Bootloader Interface. And when I remove the device it shows it listed as "fastboot device". I'm stumped on getting into CMD and can't do anything until I do. It just stays on the boot screen until I force it off. And if I'm not holding down the volume up button when I do it, it just recycles on. I've found post regarding the boot screen locked on but everybody has been able to fix it through a properly functioning fastboot/ADB.
Click to expand...
Click to collapse
The command window should be opened from the same window (folder) you have adb.exe or fastboot.exe in otherwise it isn't going to work unless you have the exact path which is easy to kame a mistake on. I would try the following:
If your not on twrp I would fastboot install it first.
Install universal naked driver
Download and unzip nvflash file
In the folder window where adb.exe is, press and hold shift, and right click and select open command prompt here.
Now do adb devices
You should see you device
put you rom in the same folder and push it to the table
reboot to recovery and install
Flashed the Broccoli nightly rom I can no longer boot or get back into CWM. Computer cannot start the device. Can someone please help me? Tried all the tools and methods. It won't work unless I can get the device to start when connected to my computer.
RIght now when I press Vol Up and power, it brings me to cold boot linux. Cannot select anything or do anything. When connected to comp, it says device cannot start Code 10. Don't know what else to do. Help please
Looks like you're having an issue similar to mine. You'll need to setup ADB and push another rom to your Prime.
Can you get into recovery?
Sent from my WabiSabiGeek'd out Transformer Prime using the Interweb
This thing is completely frozen no matter what. I can power off and on but that's about it. The device won't start according to windows. I'm praying I won't have to RMA or something.
You shouldn't be getting that screen pressing vol up and power.....that should be vol down and power, then doing nothing.
Sent from my WabiSabiGeek'd out Transformer Prime using the Interweb
Thats pretty strange. You kinda screwed unless you can get into recovery or fastboot
Sent from my WabiSabiGeek'd out Transformer Prime using the Interweb
Hi,
where it says press down to change mode you should be able to highlight the middle icon. If so that is fastboot and you have a chance.
I had a very bricked Prime and it only got that far. Then I followed this post.
You must download the fastboot and adb from the links given. I had some from elsewhere and they didn't work so well.
Also, I am not an Android hacker and I think that the dd command is somehow dangerous. At the end of the day, on my machine, I'm back with AndroWook and latest Motley kernel
Best of luck.
Tritium
Thanks let me try now. I hope it works. How did you get the computer to recognize the prime? Do I need to enable asus sync?
Tritium3.016 said:
Hi,
where it says press down to change mode you should be able to highlight the middle icon. If so that is fastboot and you have a chance.
I had a very bricked Prime and it only got that far. Then I followed this post.
You must download the fastboot and adb from the links given. I had some from elsewhere and they didn't work so well.
Also, I am not an Android hacker and I think that the dd command is somehow dangerous. At the end of the day, on my machine, I'm back with AndroWook and latest Motley kernel
Best of luck.
Tritium
Click to expand...
Click to collapse
It's alive!!! Thanks for the help. :good:
wao i have the same problem but i only go on CWM and not fastboot and still cant get it on fastboot and its not reconized the drivers any ideas??
klutch said:
wao i have the same problem but i only go on CWM and not fastboot and still cant get it on fastboot and its not reconized the drivers any ideas??
Click to expand...
Click to collapse
So when your device turns on its in a recovery loop right? You try to reboot and it goes right back to recovery?
It's ok don't worry, we will get it fixed. If that's what your problem is its referred to brick 1a in the unbrick your prime sticky thread.
We just need to setup ADB if you haven't already, and run one command. PM me if you need some help and ill try my best to get you through it or remotely connect to your computer to help you.
I highly suggest TWRP recovery after you get rebooted.
Sent from my ADR6425LVW using xda premium
klutch said:
wao i have the same problem but i only go on CWM and not fastboot and still cant get it on fastboot and its not reconized the drivers any ideas??
Click to expand...
Click to collapse
This is what I did while in CWM. Below is a copy of an insert from this thread.
http://forum.xda-developers.com/showthread.php?p=24923189#post24923189
Anyhow, so after you have that version installed:
1. Download "ROOTED 9.4.2.21 CWM compatible signed US version"
d - h . s t / r 4 4 -> WITH NO SPACE! (This is from the Primeval: The STOCK stock rom) Thread.
2. EXTRACT IT to the same directory where your ADB is! We only need the BLOBFILE from that zip folder!
3. Once you have the files extracted just run the following on your Command line:
adb push blobfile /sdcard/ ---> Its going to look like its not doing
nothing but dont worry its doing it in the background after 401 or some
seconds the command line will returned to you with a message like this:
1275kb, dadadada...
4. VERY IMPORTANT!: enter:
adb shell
dd if=/sdcard/blobfile of=/dev/block/mmcblk0p4
(Same as the previews step it will take forever but it will work dude!)
5. DONE! at least this is what worked for me man!
Im so happy now my Asus is freaking Brand NEw again! i was JUST about to through this garbage away but im so happy "dklue" gave me the BLOB concept idea! heheheh i guess i learned something new now..
the thing is the computer is not picking it up i tried diffrent drivers and still nothing i try doing ADB Shell device not found in order to do some commands i have to have it mount and thats the problem what ever i do wont move nothing so basicly is still on CWM only reboot and back again to CWM
Hold power and vol down to boot into CWM. Then you can do the blobfile push. It worked for me
ok so i am sorry for not posting in the correct thread because i am not allowed yet. so anyway i used the flatline jellybean edition and after some time have gone through the whole process and am now in the nvflash recovery mode. i have ran the required commands but foor some odd reason the resum--go command which gets you to normal android, does nothing please help me get out of this, its still connected to pc and i dont want to touch it and i dont want the battery to run out
also i would like to know where the bricksafe img and others are stored cause i cannot find them what soever
thanks
Androphile said:
ok so i am sorry for not posting in the correct thread because i am not allowed yet. so anyway i used the flatline jellybean edition and after some time have gone through the whole process and am now in the nvflash recovery mode. i have ran the required commands but foor some odd reason the resum--go command which gets you to normal android, does nothing please help me get out of this, its still connected to pc and i dont want to touch it and i dont want the battery to run out
also i would like to know where the bricksafe img and others are stored cause i cannot find them what soever
thanks
Click to expand...
Click to collapse
You can exit APX mode by pressing power button for a few seconds and allow to reboot to android.
The .img files will have been created in the folder from which you are running the command window.
Restorer said:
You can exit APX mode by pressing power button for a few seconds and allow to reboot to android.
The .img files will have been created in the folder from which you are running the command window.
Click to expand...
Click to collapse
ok thanks, i got the exiting apx mode. see now the thing with the bricksafe files, those files were not in the command windoe folder, i even ran it multiple times. and when it was run it showed the receiving and said sucess, i looked everywhere and cant find said files. i do however have the initial blob files, but the bricksafe files are not present, thanks for the help