After unsuccessfully attempt to flash identity crisis phone not able to flash any other rom seems to me bricked, any solution?
Sent from my MI PAD using XDA Free mobile app
Fastboot flash the XT1033 5.0.2 Firmware Image for your phone from here:
http://forum.xda-developers.com/mot...y-firmware-t3110795/post60792279#post60792279
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
If you have problems, provide a full and complete fastboot log (copy and paste the fastboot screen)
I am on cm 12.1 now.
I wanted to use your rom.
Sent from my MI PAD using XDA Free mobile app
Nishblueweapon said:
I am on cm 12.1 now.
I wanted to use your rom.
Click to expand...
Click to collapse
Something has happened to your phone. If you do what I describe above, any custom ROM should work.
Will try buddie
Sent from my MI PAD using XDA Free mobile app
lost101 said:
Something has happened to your phone. If you do what I describe above, any custom ROM should work.
Click to expand...
Click to collapse
in fastboot mode it says waiting for device.
To be sure i have installed latest drivers via motorola device manager.
Nishblueweapon said:
in fastboot mode it says waiting for device.
To be sure i have installed latest drivers via motorola device manager.
Click to expand...
Click to collapse
@lost101 i hope this could help him
it won't work that easy. On what window you are ?? I don't give a damn which driver you installed http://forum.xda-developers.com/showthread.php?t=2588979
just install the latest version from here.... Let it download and then i
MAKE SURE YOU HAVE USB DEBUGGING ON FROM DEVELOPERS SETTINGS
it will ask you for something like installing system wide adb and fastboot devices. Let it install at last skip the installing device software.
Now just go to c drive of your system or drive in which you have your window installed(drive) installed. Now you see adb named folder on the root of the drive.
Just press shift key first and right click then, you will see there a option of opening with command prompt or something.
Voila !!! you are now in adb .
To check you have right driver installed
give coomand like: adb devices this will show your device in the window...
if you see your device then type command: adb reboot bootloader this will bring you into bootloader menu...
TO check here that you are properly set yourself type command: fastboot devices
sachoosaini said:
@lost101 i hope this could help him
it won't work that easy. On what window you are ?? I don't give a damn which driver you installed http://forum.xda-developers.com/showthread.php?t=2588979
just install the latest version from here.... Let it download and then i
MAKE SURE YOU HAVE USB DEBUGGING ON FROM DEVELOPERS SETTINGS
it will ask you for something like installing system wide adb and fastboot devices. Let it install at last skip the installing device software.
Now just go to c drive of your system or drive in which you have your window installed(drive) installed. Now you see adb named folder on the root of the drive.
Just press shift key first and right click then, you will see there a option of opening with command prompt or something.
Voila !!! you are now in adb .
To check you have right driver installed
give coomand like: adb devices this will show your device in the window...
if you see your device then type command: adb reboot bootloader this will bring you into bootloader menu...
TO check here that you are properly set yourself type command: fastboot devices
Click to expand...
Click to collapse
I am on win. 7. It first gave me an error adpwinal.DLL file is missing from your PC while I was trying to flash those commands in cmd window, so I installed that file on my PC. Whenever I am in fastboot mode now it doesn't recognise me device. & normally it does. I think the problem with fastboot files, it shows USB connected. Will try what u said.
Sent from my Moto G using XDA Free mobile app
while flashing the system files it says file too large
To be sure i was on cm 12.1 (5.1.1) & i have flashed ASia retail 5.0.2?
Where i am wrong?
Nishblueweapon said:
while flashing the system files it says file too large
To be sure i was on cm 12.1 (5.1.1) & i have flashed ASia retail 5.0.2?
Where i am wrong?
Click to expand...
Click to collapse
Use mfastboot.exe: https://www.androidfilehost.com/?fid=24052804347778493
lost101 said:
Use mfastboot.exe: https://www.androidfilehost.com/?fid=24052804347778493
Click to expand...
Click to collapse
Got it to boot successfully. Thank u
What I did was flashed 1 more system I.e. 0 not mentioned in the op
Sent from my MI PAD using XDA Free mobile app
Related
The usual DISCLAIMER: Use at your own risk!
Fastboot mode usually comes up if something went wrong when trying to flash a recovery image, for example when flashing AmonRa recovery or ClockWorkMod. It happened to me several times so I tried to learn to revive it without reflashing the original firmware. Note: This tutorial works only if recovery is the only one broken. (If the ROM itself is broken, then that's a subject for another tut.) In this case, the most logical thing to do is just reflash the recovery image. So how do you do it in fastboot mode? Here's how:
Symptom
You tried flashing a custom recovery like ClockWorkMod or Thunderg, or you flashed an incorrect ROM, and when you rebooted, it showed this screen:
Code:
fastboot mode started
udc_start()
and the phone stays there. When you plugin the phone to your computer's USB, it is detected and the screen has this display:
Code:
fastboot mode started
udc.start()
-- suspend --
-- reset --
-- portchange --
-- reset --
-- portchange --
You will need
1) Your PC and your USB cable for the phone
2) USB drivers for your phone (use B2C from LG).
3) Android SDK (download from here)
4) Java, required to run the SDK (but right now I am not sure if this is required to run fastboot!)
5) ClockWorkMod or AmonRa Recovery.
Here's what to do
1) Assuming phone is turned on in fastboot mode, plug it in to the USB of your PC. You will know that it is detected if you see the the lines "suspend", "reset" and whatnot on the phone's screen.
2) Extract the recovery image from the zipfile downloaded from step#5 above (e.g. LGp500-recovery-v12.img). Place the image file in the same folder where fastboot.exe is (usually in the tools\ folder in the SDK). For your convenience, rename the img file as recovery.img
3) Fire up your command prompt and cd to the directory where fastboot.exe is located. Then type the following command:
Code:
fastboot erase recovery
Once you get the confirmation that it was successful, type this:
Code:
fastboot flash recovery recovery.img
Once you get the success confirmation, reboot the phone, or you can also type (optional):
Code:
fastboot reboot
The phone will reboot itself, and with any luck you should be able to go back to your same old Android bootscreen. Note that no settings were modified here, so this is extremely useful for those who do not want a clean slate after a fastboot nightmare.
Also, note that if this is successful, you can now boot to recovery with the usual button-combos, thus enabling you to flash ROMs and other recovery zips.
Note: On some SDK versions, fastboot may not be included. For your convenience, I have attached the fastboot binary I got from my downloaded SDK. I have also attached AdbWinApi.dll which some user reported is missing in the SDK. Place the DLL in the same folder where fastboot.exe is located.
Questions, just drop me a line here
thanks dude, its very usefull
Nice tutorial for newbies like me, thanks...
Sent from my LG-P500 using XDA Premium App
We already have a tut like this.
@arvinoids
Good tutorial, but you forgot to say that LG USB drivers are needed and that fastboot.exe must be downloaded before (it's no more included in android SDK)
thanks man
d3s3rt_eagle said:
@arvinoids
Good tutorial, but you forgot to say that LG USB drivers are needed and that fastboot.exe must be downloaded before (it's no more included in android SDK)
thanks man
Click to expand...
Click to collapse
You are right! I should add that here. Also, I got the latest SDK to verify and found fastboot.exe under the "tools" folder. Can tell me which SDK version you downloaded?
Usefull, thank you
Sent from my LG-P500 using XDA Premium App
Kudos to arvinoids.
This will be of great help in times of need.
Sent from my LG-P500 using Tapatalk
arvinoids said:
You are right! I should add that here. Also, I got the latest SDK to verify and found fastboot.exe under the "tools" folder. Can tell me which SDK version you downloaded?
Click to expand...
Click to collapse
I have SDK r10 and cannot found fastboot under tools
So i had to download it from htc's website.
d3s3rt_eagle said:
I have SDK r10 and cannot found fastboot under tools
So i had to download it from htc's website.
Click to expand...
Click to collapse
Wow, that's strange. I have r11 and it is included there. For your convenience, I have attached the fastboot.exe from r11 on the first post. Thanks for trying this out.
i have a question... if we don't see the fastboot line on our breaked phone and we see just stuck at LG Logo and the Recovery is broken too, what we can do?! how we can enter in fastboot mode in this situation?
hey
I run the CMD
executed cd command but the next command
"fastboot erase recovery"
gives the following error ( see the image)
Please help
@arvinoids:- mate your work acted as a GOD to me for now. I solved my above issue by just googling the AdbWinApi.dll, downloading it and putting it in the same directory as the fastboot.exe
Thanks mate
DJoptimus-One said:
@arvinoids:- mate your work acted as a GOD to me for now. I solved my above issue by just googling the AdbWinApi.dll, downloading it and putting it in the same directory as the fastboot.exe
Thanks mate
Click to expand...
Click to collapse
Did rom manager messed up your phone?
Sent from my LG-P500 using Tapatalk
lekhwani said:
Did rom manager messed up your phone?
Sent from my LG-P500 using Tapatalk
Click to expand...
Click to collapse
Yes. For the first time.
DJoptimus-One said:
Yes. For the first time.
Click to expand...
Click to collapse
How is your phone now?
Sent from my LG-P500 using Tapatalk
lekhwani said:
How is your phone now?
Sent from my LG-P500 using Tapatalk
Click to expand...
Click to collapse
Revived now
DJoptimus-One said:
Revived now
Click to expand...
Click to collapse
Good to hear that. I think this is your 2nd or 3rd day and you came across worst o1 modding scenario and overcame it. Kudos to you.
Sent from my LG-P500 using Tapatalk
AdbWinApi.dll is included in platform-tools
DJoptimus-One said:
@arvinoids:- mate your work acted as a GOD to me for now. I solved my above issue by just googling the AdbWinApi.dll, downloading it and putting it in the same directory as the fastboot.exe
Thanks mate
Click to expand...
Click to collapse
Hi. Sorry I was away for the weekend and just got back. Thanks for reporting this. I just did a search on my desktop and found out that AdbWinApi.dll is included in the platform-tools package. I will add the instructions to download the package from the SDK. I'm glad you were able to revive your phone. Thanks again!
pymebrahimi said:
i have a question... if we don't see the fastboot line on our breaked phone and we see just stuck at LG Logo and the Recovery is broken too, what we can do?! how we can enter in fastboot mode in this situation?
Click to expand...
Click to collapse
I'm afraid your issue may not be a subject for this tutorial. Fastboot mode is activated when the phone's recovery image is broken. May I know how you are sure that the recovery is actually broken?
Hi,
please help me! I hope it is not a brick.
I wanted to make full wipe. I made factory reset in recovery and then wiped sdcard.. Now I cannot boot ROM because there is no one and I have nothing on my SD. So I even cannot copy rom or backup back to phone.
Is there any way out? (
EDIT: I think I can push files (e.g. backup) through adb, right? I installed adb for dummies but when I want to execute SDKmanager.exe. it only opens black window and immediately closes it. I cannot continue
devcager said:
Hi,
please help me! I hope it is not a brick.
I wanted to make full wipe. I made factory reset in recovery and then wiped sdcard.. Now I cannot boot ROM because there is no one and I have nothing on my SD. So I even cannot copy rom or backup back to phone.
Is there any way out? (
EDIT: I think I can push files (e.g. backup) through adb, right? I installed adb for dummies but when I want to execute SDKmanager.exe. it only opens black window and immediately closes it. I cannot continue
Click to expand...
Click to collapse
Access your commands through a terminal window, like start > run > cmd to get into the prompt.
and from there work your way to your directory where you have placed it, and execute the command from that directory directly.
..
Thanks!
In the end I used adb to push backup in recovery...
All this I did because I wanted wipe my device - today I woke up and got a call and found out that my earphone stopped working I am afraid that it is due to condensation and next oxidation... I did not do anything wrong but when you come from cold winter weather into a warm flat it can happen Now I need to send it and hope the warranty will pass..
Anyway, I was looking for complete unroot process and found several advices. I am not clever from them. Is it enough to flash stock ROM? Recovery will be removed as well??
..
Election Day said:
Flash a stock ROM (this will also flash the stock recovery) and relock the bootloader with fastboot oem lock afterwards.
Click to expand...
Click to collapse
Ok. I have everything done but the relocking. Could you tell me how shall I do this? I tried to write "adb reboot bootloader" and then " fastboot oem lock" but both case the command line responded something like that it is not internal command etc. (I dont have it in English) Cannot lock it
devcager said:
Ok. I have everything done but the relocking. Could you tell me how shall I do this? I tried to write "adb reboot bootloader" and then " fastboot oem lock" but both case the command line responded something like that it is not internal command etc. (I dont have it in English) Cannot lock it
Click to expand...
Click to collapse
1.Switch off your phone
2.Connect your phone to your PC throught the USB cable
3.Switch on phone into fastboot
4.Provided that you have the driver for windows for the phone installed open Start/run/cmd (from your PC)
5.From the Android-SDK/platform-tools run the following "fastboot oem lock".
like :
C:\Android-sdk\platform-tools\fastboot oem lock
this will lock it immediately ...
mahanddeem said:
1.Switch off your phone
2.Connect your phone to your PC throught the USB cable
3.Switch on phone into fastboot
4.Provided that you have the driver for windows for the phone installed open Start/run/cmd (from your PC)
5.From the Android-SDK/platform-tools run the following "fastboot oem lock".
like :
C:\Android-sdk\platform-tools\fastboot oem lock
this will lock it immediately ...
Click to expand...
Click to collapse
it works only in "tools" and then it just says "waiting for device" and stucks When I tried "fastboot devices" it says nothing... I tried to reinstall drivers but maybe I have some old version? When I am in Windows copying files etc. it works well.
1. Make sure you open the command prompt IN in the folder with fastboot.exe.
2. Put the phone in fastboot mode.
3. In the command prompt type fastboot devices.
It will now show your serial number. If not its either you are such a noob that you managed to screw that up or the fastboot drivers are not installed. Or both.
albundy2010 said:
1. Make sure you open the command prompt IN in the folder with fastboot.exe.
2. Put the phone in fastboot mode.
3. In the command prompt type fastboot devices.
It will now show your serial number. If not its either you are such a noob that you managed to screw that up or the fastboot drivers are not installed. Or both.
Click to expand...
Click to collapse
OK. I really dont understand what could have been screwed up. Ok. It doesnt show anything. Just nothing. Cen you please send me the link for the drivers which should work? Maybe there is the problem. Fastboot drivers are something else than drivers for adb to be working? Because I dont know whats wrong. Thanks...
devcager said:
OK. I really dont understand what could have been screwed up. Ok. It doesnt show anything. Just nothing. Cen you please send me the link for the drivers which should work? Maybe there is the problem. Because I dont know whats wrong. Thanks...
Click to expand...
Click to collapse
If you have i9023 you need to add a line into the sdk for driver. You can search the tutorial threads for it.
Sent from my Nexus S using Tapatalk
try this
just check if you have fastboot and adb on the same folder, when I've rooted mine's got this issue, if cmd report "the command is an external one" simply means there is no such program in the folder you are in
copy both adb and fastboot in tools and platform-tools too, so you can run the command in both folder
cd>desktop > cd android>cd android-sdk> cd tools (then run adb or fastboot)
cd>desktop > cd android>cd android_sdk> cd platform-tools (thr run adb or fastboot)
1. Find out exactly what phone model you have if you don't know already.
2. Do the same for your computers os . Including 32 or 64 bit.
3. Combine that info and search the forum or just Google search. How to install fastboot drivers for phone model in step 1 with the os in step 2.
..
Thank you all. I decided to unroot it and relock it using Odin software which was great and quick. So I am done.... Adb has a lot of problems with drivers, commands, paths. This way was much easier
adb has no issues. User error.
albundy2010 said:
adb has no issues. User error.
Click to expand...
Click to collapse
+1
Sent from my GT-I9100 using XDA App
albundy2010 said:
adb has no issues. User error.
Click to expand...
Click to collapse
Maybe you are right. Maybe it was driver problem which I solved and then immediately used odin. Anyway, it is user friendly and I am finally done with what I wanted
albundy2010 said:
adb has no issues. User error.
Click to expand...
Click to collapse
Agreed, but not the user friendliest.
For the OP: Good luck having it repaired!
After lots of hard work by a great team of people (listed at the end), we have finally made a working Root for the Acer Iconia Tab A110.
Warning:
Code:
*I, nor any of the people involved in the rooting process of this
tablet are responsible for any damage you may cause to your device.
*If you brick your device, we are not to blame.
*Your warranty may be void after doing this.
*By using this guide, you acknowledge that you are fully responsible
for any damage you cause to your device and the device accessories.
ACER ICONIA TAB A110 ROOT GUIDE 4.1.2
UPDATED NOVEMBER 13, 2013; Most Recent Version
You will need to download/install the following before starting:
Acer Iconia Tab A110 USB Drivers (Should install on first connect of tablet)
Android SDK
SuperSU
a110-412-CWM-recovery.img Mirror: a110-412-CWM-recovery.img mirror
___________________________________________________________________________
Once downloaded, extract the Android SDK to a known location, such as the Desktop. (Use an extracting application such as Winrar)
Next, install the Nexus 7 Toolkit.
___________________________________________________________________________
Once that is complete, you can begin the rooting process.
On your device go to:
Code:
Settings > Developer Option
Turn Developer Options on at the top, and enable USB debugging.
Navigate to your Android SDK folder:
Code:
adt-bundle-windows-x86_x64\sdk\platform-tools
Copy and paste the recovery file in this directory, and copy the SuperSU files to the Tablet's SD Card. This will make the process easier later.
___________________________________________________________________________
Bootloader unlock:
The next step will wipe all your data. Remember to create a backup of anything you want to keep before attempting this.
Open a command promt (CMD) window in the directory above by holding shift while right clicking in the window and selecting "Open Command Window Here."
Type in CMD:
Code:
adb devices
Code:
adb reboot bootloader
Wait for the tablet to load into the bootloader, then type:
Code:
fastboot oem unlock
Accept on the tablet via volume and power buttons.
Your bootloader should now be unlocked.
___________________________________________________________________________
Root:
Type:
Code:
fastboot reboot-bootloader
Wait for it to reboot, once again.
Next, type:
Code:
fastboot devices
Code:
fastboot boot a110-412-CWM-recovery.img
Wait for the "OK" notification.
___________________________________________________________________________
Now, you will be booted into the custom recovery.
Right click on the Acer A110, and select install driver. Choose to point to your own path, and point it at the path for the Nexus 7 Toolkit install. (Make sure you have include subfolders checked)
Now, the device should be recognized and the root can continue.[/Code]
___________________________________________________________________________
On the device, use the volume buttons to navigate and power button to choose.
Select Install from SD.
Now type:
Navigate to the CWM-SuperSU-v0.99.zip file.
You should receive a complete message.
Once that is complete, on the tablet, navigate to reboot, select yes at the prompt, and the tablet will reboot.
You are now successfully rooted on 4.1.2!
___________________________________________________________________________
Special Thanks to the following people for their ongoing hard work:
fringle
FriedBacon
Skellums
posterz
heX79
blokenfeffer (New Recovery Image)
Stock Recovery
Here is a link to the Stock recovery pulled off of my tablet.
Not sure if it works or not, but if someone wants to try:
Stock Recovery
Installing Applications/Games to the External SD Card
I spent a long time looking for a program that allows me to do this, and finally found one that fully works.
DirectoryBind works wonders.
Here is a link to the guide:
DirectoryBind
Enjoy your extra storage space!
Reserved for further development..
Reserved for further development...
Reserved for further development
Thanks to the root method ? Could you tell me how to perform full system backup?
DjDom said:
Reserved for further development
Click to expand...
Click to collapse
I am a newbie to android. could anybody tell me how to perfrom full system backup for acer a110 4.1.2?
There is currently no way to make a full nandroid. However, if you want to back up the contents such as apps and data, use an app like my backup pro or titanium backup.
Make sure that it saves on external SD, not internal or you'll lose everything.
Sent from my Acer Iconia Tab A110 using XDA Premium HD app
root error! help!
DjDom said:
There is currently no way to make a full android. However, if you want to back up the contents such as apps and data, use an app like my backup pro or titanium backup.
Make sure that it saves on external SD, not internal or you'll lose everything.
Sent from my Acer Iconia Tab A110 using XDA Premium HD app
Click to expand...
Click to collapse
thanks!
it seems there is an error while i root:
-quote-
adb server is out of date. killing...
ADB server didnt ACK
*failed to start daemon*
error: unknown host service
-unquote-
give advise please.
thanks in advane.
cooltravis said:
thanks!
it seems there is an error while i root:
-quote-
adb server is out of date. killing...
ADB server didnt ACK
*failed to start daemon*
error: unknown host service
-unquote-
give advise please.
thanks in advane.
Click to expand...
Click to collapse
Did you download the most recent version of ADB?
Make sure you install all the drivers and follow the beginning of the guide.
Completed process but no root
I finished the process but it did not work with the first img I will try with the other one
francois2012morin said:
Does not work for my tablet. It does not unlock the bootloder so I don't get the recovery file to load.
Is it a problem with the version of my tablet software.
Here are the specifications
Android 4.1.2
Core 3.1.10
Image version Acer_AV051_A110_RV00RC09_WW_CUS1
BUILD NUMBER Acer_AV051_A110_1.049.00_WW_CUS1
Image ref FM.S1RA0.03E
Thank you if you can be of any help.
Francois
Click to expand...
Click to collapse
How did you try unlocking the bootloader?
after you type "fastboot oem unlock" look at your tab and use the buttons to select it. It gives you about 10 seconds until it reboots back to the bootloader
Oh and I can't get the sideload to kick in. I put in "CWM-SuperSU-v0.99.zip" but it doesn't do anything.
Im wondering if I can push it over using adb install bc adb sideload isn't working?
Thanks
running_onCode said:
after you type "fastboot oem unlock" look at your tab and use the buttons to select it. It gives you about 10 seconds until it reboots back to the bootloader
Oh and I can't get the sideload to kick in. I put in "CWM-SuperSU-v0.99.zip" but it doesn't do anything.
Im wondering if I can push it over using adb install bc adb sideload isn't working?
Thanks
Click to expand...
Click to collapse
I had the same problem with Sideload. Are you following the part where you need to install the drivers from the Nexus 7 toolkit?
DjDom said:
I had the same problem with Sideload. Are you following the part where you need to install the drivers from the Nexus 7 toolkit?
Click to expand...
Click to collapse
Yea. Everything. Anyway to get passed it?
Im trying to root my tablet with your guide but I can't find the A110 in the device manager after I boot the custom recovery
darthpilsner said:
Im trying to root my tablet with your guide but I can't find the A110 in the device manager after I boot the custom recovery
Click to expand...
Click to collapse
Yes i am having the same problem, mine does not see a110 but refers to google galaxy nexus adb interface. I have tried this about half a dozen times with the same result, no root. Oh well try try again. Do i need to factory restore after each failed attempt?
No Root....
Hello
I have tried this guide about 15 times... I factory reset after each try... I uninstall the drivers on the pc and make sure I install the Acer drivers.... Follow the guide to the letter... Install the google drivers... I do the sideload of su and it looks like works.... but not root... I am not sure why... Everything looks good... I am unlocked... the recovery image loads well... I replace the drivers..... I sideload.... no root.... So strange.... I guess I should just be happy it is not bricked .. .lol... Thanks for the work... Oh well... I am not looking for help... just making you aware.... thanks for all the work though...
rocy1971 said:
Hello
I have tried this guide about 15 times... I factory reset after each try... I uninstall the drivers on the pc and make sure I install the Acer drivers.... Follow the guide to the letter... Install the google drivers... I do the sideload of su and it looks like works.... but not root... I am not sure why... Everything looks good... I am unlocked... the recovery image loads well... I replace the drivers..... I sideload.... no root.... So strange.... I guess I should just be happy it is not bricked .. .lol... Thanks for the work... Oh well... I am not looking for help... just making you aware.... thanks for all the work though...
Click to expand...
Click to collapse
I'm having the exact same problem as you. Not sure if it'll help, but my firmware version has PA in it.
Same
justinnickovtime said:
I'm having the exact same problem as you. Not sure if it'll help, but my firmware version has PA in it.
Click to expand...
Click to collapse
Model a110
Android 4.1.2
Kernel 3.1.10
image acer_AV051_a110_rv00rc09_pa_cus1
Build acer_AV051_a110_1.049.00_pa_cus1
everytime I do it .... it looks like it will work... then check root with rootchecker or susuperuser.... no luck.....
If the root did work... would app2sd work... or do I have to wait for a custom rom?
Same result here!
justinnickovtime said:
I'm having the exact same problem as you. Not sure if it'll help, but my firmware version has PA in it.
Click to expand...
Click to collapse
Exactly the same results as the previous guys, every step appears successful, including sideload, but no SU after reboot. My Firmware has WW in name.
Only messages seen during sideload which imply errors are E: can't mount /cache/recovery/log etc etc.
Anyone any idea what may be wrong?
Accidentally wiped everything using TWRP and have no OS now. Can't use ADB or fastboot as when I boot to it it says device not found. Any suggestions PLEASE?
Is it a driver issue? You have to get the drivers loaded or you may be stuck. What steps have you taken so far.
I had this happen to me as well on another device but I loaded up drivers and then used adb to push files back over on a N4
playya said:
Is it a driver issue? You have to get the drivers loaded or you may be stuck. What steps have you taken so far.
I had this happen to me as well on another device but I loaded up drivers and then used adb to push files back over on a N4
Click to expand...
Click to collapse
Basically all you can do there is re-install the drivers, cause it seems they're non-existent or incorrect.
-reload the drivers [force them perhaps if on win 7]
-connect to pc with phone in fastboot
-in twrp go to advanced > sideload > start process
-add your rom to your adb folder
open a command window in your adb folder [shift + right click for short] then type adb sideload myfile.zip , and the phone will flash the file, and you can reboot.
Nosferatu1923 said:
Accidentally wiped everything using TWRP and have no OS now. Can't use ADB or fastboot as when I boot to it it says device not found. Any suggestions PLEASE?
Click to expand...
Click to collapse
teh roxxorz said:
Basically all you can do there is re-install the drivers, cause it seems they're non-existent or incorrect.
-reload the drivers [force them perhaps if on win 7]
-connect to pc with phone in fastboot
-in twrp go to advanced > sideload > start process
-add your rom to your adb folder
open a command window in your adb folder [shift + right click for short] then type adb sideload myfile.zip , and the phone will flash the file, and you can reboot.
Click to expand...
Click to collapse
I believe above post was meant for you OP
Sent from my A0001 using Tapatalk
Not needed..............
@jmz will this work on OS 4.5.2
krazyace35 said:
@jmz will this work on OS 4.5.2
Click to expand...
Click to collapse
I don't see why it wouldn't as I am on 4.5.3 and it worked.
jmz said:
I don't see why it wouldn't as I am on 4.5.3 and it worked.
Click to expand...
Click to collapse
Cool thanks I'll give it a try and thanks for this unlock tutorial
jmz said:
You will need a linux box or python installed on windows. Find instructions on the web for that.
Step 1: Download attachment
Step 2: Run command and make note of code return
Code:
adb shell cat /sys/block/mmcblk0/device/manfid
Step 3: Run command and make note of code return
Code:
adb shell cat /sys/block/mmcblk0/device/serial
Now you should have 2 sets of numbers. first should be in the format of 0x0000XX where XX is numbers. And the other is 0xSSSSSSSS.
So now use the downloaded file and execute (obivously replacing the entries with what was returned above.
Code:
./cublock.py XX SSSSSSSS
This will tell you you have unlock.signed now. So move that to your fastboot/adb directory and then reboot to bootloader and issue this command
Code:
adb reboot-bootloader
fastboot -i 0x1949 flash unlock unlock.signed
Once done, get back to android and do the following:
Code:
adb shell
su
idme print
You should now see unlock_code: AAAAAAAA and on and on.
Now go flash my TWRP build in OG dev
Original credit goes to @dpeddi & @vortox for the exploit. I did nothing to this code and it is all their work. So give them thanks
Click to expand...
Click to collapse
Sorry for the noob-ish question. How do you get adb to recognize the fire? When I type "adb devices" there are no devices present.
ryanyz10 said:
Sorry for the noob-ish question. How do you get adb to recognize the fire? When I type "adb devices" there are no devices present.
Click to expand...
Click to collapse
do steps 1 through 6 in this thread
http://forum.xda-developers.com/fire-hd/general/root-supersu-stable-appstore-custom-t3113311
Question
Sorry for another question. When I type ./cublock.py, I get ". is not recognized as an internal or external command".
Sorry again for being annoying lol
ryanyz10 said:
Sorry for another question. When I type ./cublock.py, I get ". is not recognized as an internal or external command".
Sorry again for being annoying lol
Click to expand...
Click to collapse
if on windows you need to get python installed
jmz said:
if on windows you need to get python installed
Click to expand...
Click to collapse
I've got python 3.4.2 installed. Which version would you recommend?
After some researching, people have said that python doesn't work very well on Windows 10, which is what I'm on right now.
jmz said:
You will need a linux box or python installed on windows. Find instructions on the web for that.
Step 1: Download attachment
Step 2: Run command and make note of code return
Code:
adb shell cat /sys/block/mmcblk0/device/manfid
Step 3: Run command and make note of code return
Code:
adb shell cat /sys/block/mmcblk0/device/serial
Now you should have 2 sets of numbers. first should be in the format of 0x0000XX where XX is numbers. And the other is 0xSSSSSSSS.
So now use the downloaded file and execute (obivously replacing the entries with what was returned above.
Code:
./cublock.py XX SSSSSSSS
This will tell you you have unlock.signed now. So move that to your fastboot/adb directory and then reboot to bootloader and issue this command
Code:
adb reboot-bootloader
fastboot -i 0x1949 flash unlock unlock.signed
Once done, get back to android and do the following:
Code:
adb shell
su
idme print
You should now see unlock_code: AAAAAAAA and on and on.
Now go flash my TWRP build in OG dev
Original credit goes to @dpeddi & @vortox for the exploit. I did nothing to this code and it is all their work. So give them thanks
Click to expand...
Click to collapse
Hi jmz,
I have a question here- all that was in your ZIP file was the cublock.py file.
Are we supposed to use this with the rest of draxie's tools in the HDX thread? If so, I was able to get an 'unlock.img' file, but nothing called 'unlock.signed'
maybe you didn't upload all the attachments we needed?
either way, thanks soooo much for your work !
edouble312 said:
Hi jmz,
I have a question here- all that was in your ZIP file was the cublock.py file.
Are we supposed to use this with the rest of draxie's tools in the HDX thread? If so, I was able to get an 'unlock.img' file, but nothing called 'unlock.signed'
maybe you didn't upload all the attachments we needed?
either way, thanks soooo much for your work !
Click to expand...
Click to collapse
sorry, with that tool you only get the unlock.img . I need to correct the post
In my linux box 'cuber' module, required by cublock.py, is not installed; is this the correct source? https://github.com/benesch/cuber
One more question: I forgot to block OTA update so my HD6 updated to 4.5.4, loosing root permissions. What I should do? Need to wait KingRoot supports the new software version or can I proceed to unlock bootloader and install twrp? Or could install, if available, a 4.5.3 recovery through dd? Very thanks.
I sense many roms being ported very soon...
Sure hope so!
I used the tools (cuber) in this post:
http://forum.xda-developers.com/kin...tools-create-unlock-img-fix-boot-img-t3050689
So i generated unlock.img, but i am still unable to enter fastboot mode,
i tried changing boot to 4002, i rooted and tried to execute fastboot file, nothing works tbh, how do you suppose i fix this?
thanks in advance
robert896 said:
So i generated unlock.img, but i am still unable to enter fastboot mode,
Click to expand...
Click to collapse
Need more info: Your computer OS, tablet device model (Settings>Device Options), Fire OS version (Device Options>System Updates). Tell exactly what happens when you run: adb reboot-bootloader.
DoLooper said:
Need more info: Your computer OS, tablet device model (Settings>Device Options), Fire OS version (Device Options>System Updates). Tell exactly what happens when you run: adb reboot-bootloader.
Click to expand...
Click to collapse
ok im on ubuntu 15.04 got full adb and fastboot (they work on other devices) --- fire os 4.4.3---device model, kfhd 3rd gen
i also have windows 7 x64 dual booted with full adb and fastboot set up also
when i do adb reboot-bootloader, it restarts but doesnt enter fastboot ,, it boots into normal mode
robert896 said:
device model, kfhd 3rd gen
Click to expand...
Click to collapse
These unlock instructions are for Fire HDs (4th gen). You need a fastboot cable for KFSOWI. Try G+ KFSOWI modding.
I am new to the tablet scene. This is my very first tablet. I would like to root the device and install custom recovery and hopefully custom Rom. Is this the first thing I do or should I start somewhere else?