Hi there guys,
I'm new to the forum so apologies if this has been posted in the wrong place.
So I was directed to this forum to attempt to solve a different problem but in my hast, I have caused an even bigger problem!
So initially I was having problems with the new Android Wear update with regards to rooting, so I wanted to find a way to roll the software back or restore the device to stock.
I came across this post http://forum.xda-developers.com/g-watch/development/tool-lg-g-watch-return-to-stock-t3158349 and attempt to do as advised, but half way through the process, the program froze. I then tried to reset the watch from the button at the back, but the watch is now stuck on the fastboot menu. I used ADB to see if I could still connect to the device but no devices can be found.
I have checked the device manager and can see the device as "Android Bootloader Interface" but can't seem to get it past the fastboot menu.
Any help would be much appreciated.
Thanks in advance.
just do it again, as long you can get fastboot, you are safe.
Jaocagomez said:
just do it again, as long you can get fastboot, you are safe.
Click to expand...
Click to collapse
The problem is, the program requires a connection via ADB, but ADB can no longer see the device. So when I try to run it again, nothing happens :/
Montezz1 said:
The problem is, the program requires a connection via ADB, but ADB can no longer see the device. So when I try to run it again, nothing happens :/
Click to expand...
Click to collapse
F the program it is outdated as **** get adb minimal here and the last 5.1.1 images here
Extract to the same folder you put adb minimal and open a terminal here.
do these commands:
Code:
fastboot flash boot nameofboot.img
fastboot flash system nameofsystem.img
(optional) fastboot flash recovery recovery.img
fastboot format/erase data
fastboot format/erase cache
Oh yeah btw if the only problem you had was with rooting just use my guide here and system images from here instead
Xmaster24 said:
F the program it is outdated as **** get adb minimal here and the last 5.1.1 images here
Extract to the same folder you put adb minimal and open a terminal here.
do these commands:
Code:
fastboot flash boot nameofboot.img
fastboot flash system nameofsystem.img
(optional) fastboot flash recovery recovery.img
fastboot format/erase data
fastboot format/erase cache
Oh yeah btw if the only problem you had was with rooting just use my guide here and system images from here instead
Click to expand...
Click to collapse
Hi there,
Thanks for the response.
I have just completed the steps as advised, download the minimal ADB and fastboot and extracted the G Watch images into that file. I opened ADB and ran the following command:
Code:
fastboot flash boot nameofboot.img
But received the following error:
http://i.imgur.com/URh0IsF.png
Any ideas on how to solve that error?
Thanks in advance
Montezz1 said:
Hi there,
Thanks for the response.
I have just completed the steps as advised, download the minimal ADB and fastboot and extracted the G Watch images into that file. I opened ADB and ran the following command:
Code:
fastboot flash boot nameofboot.img
But received the following error:
http://i.imgur.com/URh0IsF.png
Any ideas on how to solve that error?
Thanks in advance
Click to expand...
Click to collapse
Check the bootloader lock status and report back
Xmaster24 said:
Check the bootloader lock status and report back
Click to expand...
Click to collapse
Secure boot - Enabled
Lock state - unlocked.
I did try to unlock it again just to make sure and it is showing that is it unlocked.
Montezz1 said:
Secure boot - Enabled
Lock state - unlocked.
I did try to unlock it again just to make sure and it is showing that is it unlocked.
Click to expand...
Click to collapse
Do this command:
flashing get_unlock_ability
and also try and flash another partition eg system and report back what happens
Xmaster24 said:
Do this command:
flashing get_unlock_ability
and also try and flash another partition eg system and report back what happens
Click to expand...
Click to collapse
Hi,
The result from the flashing get_unlock_ability command is provided here:
http://i.imgur.com/jczJRST.png
I attempted to flash the system image and received the following error:
http://i.imgur.com/83RXdFi.png
The watch responses the same as when attempting to flash the boot image and is stuck on "Downloading".
I also tried to flash the recovery image and received the same error as shown when flashing the boot image.
Thanks
Montezz1 said:
Hi,
The result from the flashing get_unlock_ability command is provided here:
http://i.imgur.com/jczJRST.png
I attempted to flash the system image and received the following error:
http://i.imgur.com/83RXdFi.png
The watch responses the same as when attempting to flash the boot image and is stuck on "Downloading".
I also tried to flash the recovery image and received the same error as shown when flashing the boot image.
Thanks
Click to expand...
Click to collapse
Looks like it is either that adb minimal is messed up (I use the full 1gb sdk) or there is a driver problem or you can try running cmd as administrator instead
Xmaster24 said:
Looks like it is either that adb minimal is messed up (I use the full 1gb sdk) or there is a driver problem or you can try running cmd as administrator instead
Click to expand...
Click to collapse
I did try adb from the SDK that you've mentioned and have had the same results.
I also run in Administrator every time.
What I have just noticed with regards to the drivers is the change in the name of the device in device manager. Previously it showed as "Android Composite ADB Interface" but now it is showing as "Android Bootloader Interface".
I believe that might just be because the watch is stuck on the bootloader menu so that is how it is displayed, but it could be the cause.
Montezz1 said:
I did try adb from the SDK that you've mentioned and have had the same results.
I also run in Administrator every time.
What I have just noticed with regards to the drivers is the change in the name of the device in device manager. Previously it showed as "Android Composite ADB Interface" but now it is showing as "Android Bootloader Interface".
I believe that might just be because the watch is stuck on the bootloader menu so that is how it is displayed, but it could be the cause.
Click to expand...
Click to collapse
Your pc seems to be having trouble writing anything to the watch so if it is not the sdk then it must be your driver or bootloader
---------- Post added at 12:49 PM ---------- Previous post was at 12:43 PM ----------
Just checked the tool and it shouldn't do any harm at all to your watch unless you tried the bootloader lock so it must be your drivers
Xmaster24 said:
Your pc seems to be having trouble writing anything to the watch so if it is not the sdk then it must be your driver or bootloader
---------- Post added at 12:49 PM ---------- Previous post was at 12:43 PM ----------
Just checked the tool and it shouldn't do any harm at all to your watch unless you tried the bootloader lock so it must be your drivers
Click to expand...
Click to collapse
Hi there,
I've just tried to update the drivers but they seem to be up to date.
Yeah, the only reason I thought the program had done some damage is because it froze which resulted in getting stuck on the fastboot menu, but you've more knowledge so I guess that's not the issue.
I'm not entirely sure what else can be done here. I think I might have to just get another watch and stop the update as that is when all the problems occurred.
If you can think of anything else to try, I would be willing to give it a go but don't worry yourself too much if you're out of ideas.
I really appreciate your help up to this point anyways
Thanks
Montezz1 said:
Hi there,
I've just tried to update the drivers but they seem to be up to date.
Yeah, the only reason I thought the program had done some damage is because it froze which resulted in getting stuck on the fastboot menu, but you've more knowledge so I guess that's not the issue.
I'm not entirely sure what else can be done here. I think I might have to just get another watch and stop the update as that is when all the problems occurred.
If you can think of anything else to try, I would be willing to give it a go but don't worry yourself too much if you're out of ideas.
I really appreciate your help up to this point anyways
Thanks
Click to expand...
Click to collapse
Try and lock your watch with
fastboot oem lock
then try again with
fastboot oem unlock
Also when was the first time you flashed anything anyway?
Xmaster24 said:
Try and lock your watch with
fastboot oem lock
then try again with
fastboot oem unlock
Also when was the first time you flashed anything anyway?
Click to expand...
Click to collapse
I was able to lock and then unlock, and the device notified me that it was erasing, but when I try to start the device, it still brings be back to the fastboot menu.
Do you mean flashing devices in general or flashing this specific device?
Montezz1 said:
I was able to lock and then unlock, and the device notified me that it was erasing, but when I try to start the device, it still brings be back to the fastboot menu.
Do you mean flashing devices in general or flashing this specific device?
Click to expand...
Click to collapse
This device I just want to know if you ever actually successfully flashed anything to this device
Xmaster24 said:
This device I just want to know if you ever actually successfully flashed anything to this device
Click to expand...
Click to collapse
The first attempting of flashing anything to this device I believe was when using the Return to Stock tool.
I choose the "Install ROM" option which I can see from the script attempts to flash.
So I guess it's never been successful on this device.
Montezz1 said:
The first attempting of flashing anything to this device I believe was when using the Return to Stock tool.
I choose the "Install ROM" option which I can see from the script attempts to flash.
So I guess it's never been successful on this device.
Click to expand...
Click to collapse
This whole problem started due to the fact that I couldn't see the device using ADB, so I tried to look for a method to solve that which then caused the problem I'm having now.
The only variable I can put it down to is an update that was pushed to the watch as prior to that, I had no problems at all.
Montezz1 said:
This whole problem started due to the fact that I couldn't see the device using ADB, so I tried to look for a method to solve that which then caused the problem I'm having now.
The only variable I can put it down to is an update that was pushed to the watch as prior to that, I had no problems at all.
Click to expand...
Click to collapse
Yup sounds like a driver problem for sure uninstall the watch drivers and download the google drivers here
Xmaster24 said:
Yup sounds like a driver problem for sure uninstall the watch drivers and download the google drivers here
Click to expand...
Click to collapse
I do not believe it...
After all of this, it was the drivers...
I don't get it though!! I tried to reinstall them before and nothing changed!
It's only when I completely deleted them and reinstalled that it worked.
Honestly dude, thank you so much for your help and patience. My watch is now working and paired with my phone.
I'm waiting for it to sync but hopefully I will be able to run ADB and all will be well again
Thanks you so much again.
Related
Hello All,
I posted this on the post for Android Revolution and seem to have run out of interest. This was my post.
Hello,
I messed up and flashed the boot file before I installed the rom file in the internal storage. Now the phone wont boot at all. Can you help me fix this please.
I've tried to search for answers but cant find anything.
I can get into fastboot mode and into CMW mode. So I am able to enter sideload mode but cant get the phone to take the sideload.
I'm afraid I may have formatted the storage too.
Can anyone help me please?
Steve the noob.
Right now I am completely bricked. Tried everything, reinstalled SDK, tried sideloading in a couple of ways, stuck in bootloader or CMW. Try to load and sticks on white HTC page.
PLEASE HELP. I followed all of the directions except for loading the boot first.
Is there a factory reset like the old Oden system that could save me?
Can you get into fastboot?
If so you need to then flash the boot.img via fastboot.
Type fastboot flash (name of file).img in command prompt and you should be good to go!
which boot image?
Looks like you took the wrong version for your phone. You have an AT&T / Telus phone. You can not take an International ROM for your phone.
Only AT&T / TELUS ROMs will work on your phone.
I forgot, you can not bricked your phone since our HTC ONE X+ are S-ON, you just missed something to have it going.
stevespens said:
which boot image?
Click to expand...
Click to collapse
Which CWM are you on? Lloir or the other guys? VERIFY YOU HAVE THE PROPER RECOVERY INSTALLED. IF YOU ARE ON THE AT&T MODEL USE THE AT&T RECOVERY
You can run an RUU (verify proper carrier and model) while at the fastboot screen, or install TWRP and try to sideload using that from the SDK PLATFORM TOOLS FOLDER. You mentioned you have the SDK installed but I need to stress DO NOT USE THE TOOL KIT IT IS WORTHLESS. Make sure you have the official HTC drivers installed that come with HTC SYNC using generic drivers from the tool kit usually yields worthless resutls.
I cant get the rom on the phone. It's completely stuck in a boot loop. Only thing I can do is go into bootloader or CWM. I need to sideload a rom. But it wont let me.
stevespens said:
I cant get the rom on the phone. It's completely stuck in a boot loop. Only thing I can do is go into bootloader or CWM. I need to sideload a rom. But it wont let me.
Click to expand...
Click to collapse
I looked at your android revolution thread. STOP USING THE TOOL KIT. It is a POS.
Kraizk said:
I looked at your android revolution thread. STOP USING THE TOOL KIT. It is a POS.
Click to expand...
Click to collapse
OK. Gotcha. Thanks for the help.
Now what do I do? I am bricked.
stevespens said:
OK. Gotcha. Thanks for the help.
Now what do I do? I am bricked.
Click to expand...
Click to collapse
Read my previous post I gave you instructions. http://forum.xda-developers.com/showpost.php?p=39261003&postcount=5
OK...
Let's start with the correct Recovery for your phone, download link -> Click me!
N.B. -> Rename this file like this -> TWRP2recovery
Put this file in your platform-tools of SDK folder.
Put your phone in bootloader (fastboot USB)
Type this : fasboot devices (Enter... you should have your serial in return)
Then type : fastboot flash recovery TWRP2recovery.img (Enter)
Again type : fastboot erase cache (Enter)
Unplug your USB cable and hit Power button one time
Select Recovery
Hit Power button one time to reboot in Recovery
Try to sideload an ATT&T / TELUS ROM ONLY
Go for Elegancia AT&T/TELUS ROM for this time. (Choose one of your choice in the Download section here)
What are the results?
Well, thanks for all your efforts, but it's a lost cause. I tried the last posters suggestions and it wont let me flash the recovery at all. It's done. I have insurance so I'm just going to smash it and file a claim. I give up. I wont do that again.
Which error you have when you try to flash the recovery? Is your phone recognized at least when you are typing : adb devices ?
stevespens said:
Well, thanks for all your efforts, but it's a lost cause. I tried the last posters suggestions and it wont let me flash the recovery at all. It's done. I have insurance so I'm just going to smash it and file a claim. I give up. I wont do that again.
Click to expand...
Click to collapse
Have you tried just running the RUU? People say it takes a few times. Your phone is not bricked if you can get into fastboot.
Sent from my HTC One X+ using xda premium
thanks for coming back.
Lets give this a try.
Lucky Thirteen said:
Which error you have when you try to flash the recovery? Is your phone recognized at least when you are typing : adb devices ?
Click to expand...
Click to collapse
I got this when I typed "fastboot devices",,,
Then when I typed fastboot recovery to load the file, it showed this
just tried a dif file path and got this
Oh, by the way, my bootloader has been relocked. Can I fix this through bootloader?
First let's install your SDK folder correctly then you will see, it will work flawlessly.
Have a look at my screenshot, see how mine look simple compare to yours.... Yes, I have two devices plugged.
Install your SDK tool like it is explained in this thread.
The version numbers are different but the installation stay the same.
EDIT : What is your computer OS? I will point you to the good htc drivers.
Hello everyone, This is my first post on this forum, as I only rooted my prime a few months ago, and had not had any problems. I was running Hairybean 1.55 and decided to upgrade to the new 2.11 rom. I followed the instructions very closely and first upgraded to the 4.2.1 bootloader/ recovery. This step seemed to go fine. However, duing the install of the 2.11 rom, my Prime completely froze on the screen where you select the Asus options/apps/wallpapers/etc. I had no choice but to hard boot the Prime.
Now it boots directly into TWRP.
Since cache/dalvik, system, were all wiped, and Format Data was performed, there is no OS on the device. The major problems are that:
External SD card will not mount and is not recognized by device
When going into the "Mount" function in TWRP, only System can be mounted with the toggle. Data, Cache, or SDCard will not mount.
I am able to ADB push the "Upgrade Hairybean 4.2.1 Bootloader & Recovery.zip" file to /SDCard, but when I try to install it on the device it fails due to the fact "cache" will not mount.
I am trying to push the "Hairybean 2.11.zip" file to the Prime using ADB, but I get a "Protocol Failure" from the push command (the full command syntax I am using is: adb push "Hairybean 2.11.zip" /sdcard/"Hairybean 2.11.zip")
I do have a reasonable amount of experience rooting. This is the 5th Android device I have rooted. However, I am not very skilled in ADB.
Any advice anyone could give would be greatly appreciated. If I am totally hosed, does anyone have any experience sending an out-of-warranty unlocked Prime back to Asus for repair (if this is even repairable)?
Thank you
cficklin31 said:
Hello everyone, This is my first post on this forum, as I only rooted my prime a few months ago, and had not had any problems. I was running Hairybean 1.55 and decided to upgrade to the new 2.11 rom. I followed the instructions very closely and first upgraded to the 4.2.1 bootloader/ recovery. This step seemed to go fine. However, duing the install of the 2.11 rom, my Prime completely froze on the screen where you select the Asus options/apps/wallpapers/etc. I had no choice but to hard boot the Prime.
Now it boots directly into TWRP.
Since cache/dalvik, system, were all wiped, and Format Data was performed, there is no OS on the device. The major problems are that:
External SD card will not mount and is not recognized by device
When going into the "Mount" function in TWRP, only System can be mounted with the toggle. Data, Cache, or SDCard will not mount.
I am able to ADB push the "Upgrade Hairybean 4.2.1 Bootloader & Recovery.zip" file to /SDCard, but when I try to install it on the device it fails due to the fact "cache" will not mount.
I am trying to push the "Hairybean 2.11.zip" file to the Prime using ADB, but I get a "Protocol Failure" from the push command (the full command syntax I am using is: adb push "Hairybean 2.11.zip" /sdcard/"Hairybean 2.11.zip")
I do have a reasonable amount of experience rooting. This is the 5th Android device I have rooted. However, I am not very skilled in ADB.
Any advice anyone could give would be greatly appreciated. If I am totally hosed, does anyone have any experience sending an out-of-warranty unlocked Prime back to Asus for repair (if this is even repairable)?
Thank you
Click to expand...
Click to collapse
What you describe with nothing being able to mount normally only happens if you install a different TWRP than the one provided in the Upgrade zip.
Are you sure you didn't try to install another recovery after installing the "Upgrade Hairybean 4.2.1 Bootloader & Recovery.zip" ?
flumpster said:
What you describe with nothing being able to mount normally only happens if you install a different TWRP than the one provided in the Upgrade zip.
Are you sure you didn't try to install another recovery after installing the "Upgrade Hairybean 4.2.1 Bootloader & Recovery.zip" ?
Click to expand...
Click to collapse
Thanks for responding, Flumpster. No, I installed the "Upgrade Hairybean 4.2.1 Bootloader & Recovery.zip" and then went straight to installing the "Hairybean 2.11". That is when it froze at the Asus options screen. Another interesting thing I didn't mention before is that is completely wiped my microSD card. Luckily I had backed up all the contents to a pc. I hadn't even downloaded another recovery, so there is no way I could have. Is this pretty much a hopeless case?
cficklin31 said:
Thanks for responding, Flumpster. No, I installed the "Upgrade Hairybean 4.2.1 Bootloader & Recovery.zip" and then went straight to installing the "Hairybean 2.11". That is when it froze at the Asus options screen. Another interesting thing I didn't mention before is that is completely wiped my microSD card. Luckily I had backed up all the contents to a pc. I hadn't even downloaded another recovery, so there is no way I could have. Is this pretty much a hopeless case?
Click to expand...
Click to collapse
Well the wiping the SDcard part is written in the requirements of the hairybean OP so you're to blame for that one for not reading
As for the big problem at moment can you still get into bootloader?
If so can you try the first fix on the following link please.
Also can you tell me what the long number is on the top left of the bootloader screen.
http://forum.xda-developers.com/showpost.php?p=40149294&postcount=8
flumpster said:
Well the wiping the SDcard part is written in the requirements of the hairybean OP so you're to blame for that one for not reading
As for the big problem at moment can you still get into bootloader?
If so can you try the first fix on the following link please.
Also can you tell me what the long number is on the top left of the bootloader screen.
http://forum.xda-developers.com/showpost.php?p=40149294&postcount=8
Click to expand...
Click to collapse
Sorry, I guess I didn't read it correctly that the external microSD would get wiped in the process as well as the internal "SDcard" storage. I always make sure my internal and external storage are backed up anyway, so it wasn't a big deal.
I can not get my prime to boot into the bootloader. Not matter what I try, the first thing I see after the Asus screen is the TeamWin splash screen. It then goes to TWRP and wants me to put in my "password" even though I have never used that. I hit cancel and it goes into TWRP. Perhaps there is something I'm doing wrong? I hold "volume down and power" until the "unlocked message appears in the top left and then release both buttons.
If I am able to ABD push the blob file in your other post onto my internal SD, can I then run the file using an ADB shell or the TWRP terminal or something? If so, is there anyway you can give me some quick instructions on doing so?
I really appreciate you taking the time to help me out. You are going above and beyond.
cficklin31 said:
Sorry, I guess I didn't read it correctly that the external microSD would get wiped in the process as well as the internal "SDcard" storage. I always make sure my internal and external storage are backed up anyway, so it wasn't a big deal.
I can not get my prime to boot into the bootloader. Not matter what I try, the first thing I see after the Asus screen is the TeamWin splash screen. It then goes to TWRP and wants me to put in my "password" even though I have never used that. I hit cancel and it goes into TWRP. Perhaps there is something I'm doing wrong? I hold "volume down and power" until the "unlocked message appears in the top left and then release both buttons.
If I am able to ABD push the blob file in your other post onto my internal SD, can I then run the file using an ADB shell or the TWRP terminal or something? If so, is there anyway you can give me some quick instructions on doing so?
I really appreciate you taking the time to help me out. You are going above and beyond.
Click to expand...
Click to collapse
AH.. my bad mate.. I thought you was talking about the internal being wiped..
It definitely should not have wiped your external sd card.. There isn't even an option there to do that I don't think.
Are you sure it has been wiped. Have you tried looking at it on your computer?
As for your other problem can you make sure you have adb drivers installed and then try adb reboot bootloader while in twrp.
flumpster said:
AH.. my bad mate.. I thought you was talking about the internal being wiped..
It definitely should not have wiped your external sd card.. There isn't even an option there to do that I don't think.
Are you sure it has been wiped. Have you tried looking at it on your computer?
As for your other problem can you make sure you have adb drivers installed and then try adb reboot bootloader while in twrp.
Click to expand...
Click to collapse
Yeah, I checked it on my PC and it was as clear as it was new. No worries though. Probably just a fluke of the install freezing and my hardbooting (which was maybe a massive mistake?)
Just to clarify, do you mean have ADB drivers installed on my PC or on the prime? I have them on my pc and am able to open a terminal and do "ADB Devices" and it finds the prime. Are you saying to do an "ADB reboot bootloader" command from my PC while the Prime is connected and in TWRP? Or do I need to install ADB drivers on the Prime somehow?
Sorry for my ignorance on some of this stuff.
cficklin31 said:
Yeah, I checked it on my PC and it was as clear as it was new. No worries though. Probably just a fluke of the install freezing and my hardbooting (which was maybe a massive mistake?)
Just to clarify, do you mean have ADB drivers installed on my PC or on the prime? I have them on my pc and am able to open a terminal and do "ADB Devices" and it finds the prime. Are you saying to do an "ADB reboot bootloader" command from my PC while the Prime is connected and in TWRP? Or do I need to install ADB drivers on the Prime somehow?
Sorry for my ignorance on some of this stuff.
Click to expand...
Click to collapse
Yes.. while in twrp connect the cable to pc and type adb reboot bootloader from command prompt.
flumpster said:
Yes.. while in twrp connect the cable to pc and type adb reboot bootloader from command prompt.
Click to expand...
Click to collapse
Ok. The ADB command worked to get into the bootloader. Here is what it says at the top left of the bootloader screen:
Key driver not found.. Booting OS
Android cardhu-user bootloader (1.00 e) released by "WW_epad-10.6.1.8-20130225" A03
Starting Fastboot USB download protocol
Given this, should I go ahead and try installing the TWRP.blob file from your other thread link?
cficklin31 said:
Ok. The ADB command worked to get into the bootloader. Here is what it says at the top left of the bootloader screen:
Key driver not found.. Booting OS
Android cardhu-user bootloader (1.00 e) released by "WW_epad-10.6.1.8-20130225" A03
Starting Fastboot USB download protocol
Given this, should I go ahead and try installing the TWRP.blob file from your other thread link?
Click to expand...
Click to collapse
That is really your only option. If that doesn't work it looks like you might be hard bricked.
Quite a lot of people over on the TF300 forums ended up in the same position after their normal Asus update and only some could unbrick.
Best of luck mate.
flumpster said:
That is really your only option. If that doesn't work it looks like you might be hard bricked.
Quite a lot of people over on the TF300 forums ended up in the same position after their normal Asus update and only some could unbrick.
Best of luck mate.
Click to expand...
Click to collapse
Thanks,
Just to make sure I know what I'm doing. I have put the blob file in my ADB directory. Now are these the commands? :
adb shell
fastboot -i 0x0b05 flash recovery twrp.blob
Then if that doesn't work, I try:
adb shell
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
In that post you say to reboot normally, not to recovery. But since I have no rom installed, I need to go back to recovery and try to flash the Hairybean 2.11 rom again. Is that correct?
Well, I don't know if that is going to work anyway. When I try to open an ADB shell it says "device not found" while the prime is at the bootloader screen. My pc shows it connecting though, and in device manager it says "device is working properly". Any thoughts?
And if I boot back into TWRP using the RCK button, it will then find the device in ADB and open a shell.
cficklin31 said:
Well, I don't know if that is going to work anyway. When I try to open an ADB shell it says "device not found" while the prime is at the bootloader screen. My pc shows it connecting though, and in device manager it says "device is working properly". Any thoughts?
And if I boot back into TWRP using the RCK button, it will then find the device in ADB and open a shell.
Click to expand...
Click to collapse
Fastboot is not adb. You need the Fastboot.exe
---------- Post added at 08:11 PM ---------- Previous post was at 08:04 PM ----------
flumpster said:
Fastboot is not adb. You need the Fastboot.exe
Click to expand...
Click to collapse
I am going to brick my tablet like yours to try and get out of it.
Try the Fastboot method for now from bootlader.
flumpster said:
Fastboot is not adb. You need the Fastboot.exe
Click to expand...
Click to collapse
Ok, so option one does not seem to work in this case. Is this what I need to do for option 2?
In Twrp: ADB push twrp.blob to the /sdcard directory.
Then open an "ADB shell"
type "su" then return.
type "dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4" then return?
Then try to go back into TWRP and install Hairybean 2.11?
Thanks again. There will be a donation headed your way for all your trouble.
cficklin31 said:
Ok, so option one does not seem to work in this case. Is this what I need to do for option 2?
In Twrp: ADB push twrp.blob to the /sdcard directory.
Then open an "ADB shell"
type "su" then return.
type "dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4" then return?
Then try to go back into TWRP and install Hairybean 2.11?
Thanks again. There will be a donation headed your way for all your trouble.
Click to expand...
Click to collapse
Well option 2 is mainly for if you can still get into the tablet but I will try it from inside twrp now.
I am now in the same position as you with the password screen and no mounts.
Back soon.
---------- Post added at 08:35 PM ---------- Previous post was at 08:21 PM ----------
Unfortunately I pushed the twrp to the /cache folder and then managed to run dd if=/cache/twrp.blob of=/dev/block/mmcblk0p4 ok and it looked like it had completed ok but on restart it does not flash the recovery.
flumpster said:
Well option 2 is mainly for if you can still get into the tablet but I will try it from inside twrp now.
I am now in the same position as you with the password screen and no mounts.
Back soon.
---------- Post added at 08:35 PM ---------- Previous post was at 08:21 PM ----------
Unfortunately I pushed the twrp to the /cache folder and then managed to run dd if=/cache/twrp.blob of=/dev/block/mmcblk0p4 ok and it looked like it had completed ok but on restart it does not flash the recovery.
Click to expand...
Click to collapse
Well, bricking your own tablet is a little extreme, haha. I do appreciate all the effort you are making on my part to troubleshoot this issue though. Good luck. I'm confident you'll figure something out. You do great work with the HairyBean roms.
cficklin31 said:
Well, bricking your own tablet is a little extreme, haha. I do appreciate all the effort you are making on my part to troubleshoot this issue though. Good luck. I'm confident you'll figure something out. You do great work with the HairyBean roms.
Click to expand...
Click to collapse
I have nvflash backups.. I can unbrick at any time mate.
When you tried it the bootloader way with fastboot what was happening?
flumpster said:
I have nvflash backups.. I can unbrick at any time mate.
When you tried it the bootloader way with fastboot what was happening?
Click to expand...
Click to collapse
This is what is diplayed in the cmd window on the PC
sending 'recovery' (7966kb)...
OKAY [ 2.172s]
writing 'recovery'...
OKAY [ 3.167s]
finished. total time:: 5.345s
However, nothing happens on the prime. It seems to freeze the bootloader such that pushing the up-volume button will not select RCK to go back into TWRP. I have to do a reboot from ADB.
I don't suppose there is a way to do a NVFlash back to stock or something (or you would have mentioned that already :laugh: ) I am not familiar at all with NVFLash. But it sounds like I should make myself familiar with it.
cficklin31 said:
This is what is diplayed in the cmd window on the PC
sending 'recovery' (7966kb)...
OKAY [ 2.172s]
writing 'recovery'...
OKAY [ 3.167s]
finished. total time:: 5.345s
However, nothing happens on the prime. It seems to freeze the bootloader such that pushing the up-volume button will not select RCK to go back into TWRP. I have to do a reboot from ADB.
I don't suppose there is a way to do a NVFlash back to stock or something (or you would have mentioned that already :laugh: ) I am not familiar at all with NVFLash. But it sounds like I should make myself familiar with it.
Click to expand...
Click to collapse
You can only use nvflash if you created backups with it while on ICS.
You know when it says that sending recovery/writing recovery in fastboot, do you see a blue line filling?
No, there is no blue line. Nothing on the bootloader screen seems to change at all.
Sent from my SCH-I535 using xda app-developers app
HELP Please !
My htc explorer initially got stuck at the htc logo at boot and won't go any further.
I searched for solutions on xda and tried to install Cyanogenmod 10.2 on it. Now the device gets stuck at cyanogenmod boot animation (was going on until half -an-hour ! )
Next i searched some more, caught TWRP recovery on a glance. Tried installing it, but my Laptop ( Win8.1 x64 ) doesnt recognize the device whatsover, even after installing the adb drivers and HTC SYNC. !
Now i finally installed FLYROM v4 refined, and the phone is stuck at htc 'quietly brilliant' logo . !
PLEASE get me out of this misery ! I want my little buddy back in action
Please .. Anybody ?
Nobody to help ?
I dont have an HTC phone or knowledge. but in our phone. we use tool to flash stock firmware. as in pure stock. removing anything. give it a try
---------- Post added at 08:04 PM ---------- Previous post was at 08:00 PM ----------
http://forum.xda-developers.com/showthread.php?t=1816836 this link shows tutorials on how to unbrick your phone. hope i helped
Thanks, but no luck
pjohn23 said:
I dont have an HTC phone or knowledge. but in our phone. we use tool to flash stock firmware. as in pure stock. removing anything. give it a try
---------- Post added at 08:04 PM ---------- Previous post was at 08:00 PM ----------
http://forum.xda-developers.com/showthread.php?t=1816836 this link shows tutorials on how to unbrick your phone. hope i helped
Click to expand...
Click to collapse
I tried many custom ROMs and ended up bootlooping all of them ( Indefinite cyanogenmod animation , for about 48 minutes on average) !
I want to do a full erase of the device and reinstall these ROMs , bu i don't know how to do it .. searched for quite long but no proper instuctions on that
DrSakethReddy said:
I tried many custom ROMs and ended up bootlooping all of them ( Indefinite cyanogenmod animation , for about 48 minutes on average) !
I want to do a full erase of the device and reinstall these ROMs , bu i don't know how to do it .. searched for quite long but no proper instuctions on that
Click to expand...
Click to collapse
dont you have flashtools?
More INFO needed.
pjohn23 said:
dont you have flashtools?
Click to expand...
Click to collapse
I didn't get you.
I have these tools mentioned in almost every HTC explorer resuscitation page :
1. HTC Sync
2. adb drivers
3. Fastboot driver
4. TWRP 2.x.x
5. Stock ROM and
6. 6 varieties of Custom ROMs ! (all get stuck in bootloop )
DrSakethReddy said:
I didn't get you.
I have these tools mentioned in almost every HTC explorer resuscitation page :
1. HTC Sync
2. adb drivers
3. Fastboot driver
4. TWRP 2.x.x
5. Stock ROM and
6. 6 varieties of Custom ROMs ! (all get stuck in bootloop )
Click to expand...
Click to collapse
what i mean is windows tool that can flash stock rom on your phone. if it has. you should use that and wipe everything
It's almost certainly an issue with a locked or semi-locked bootloader. If you are just HTC Dev unlocked on most HTCs, you need to flash the boot.img (kernel) via fastboot or when booted, with an app like Flashify. The reason you are having issues with getting it to connect is because Win 8.1 has issues with the HTC fastboot driver, especially on USB 3.0 ports on some makes of PCs. Grab another computer that has Win 7, if possible. Linux is an option as well, depending on how comfortable you are using it. But anyway, get to a PC that doesn't have Win 8+, get the HTC Sync program installed to get all of the drivers properly set up, then extract the boot.img from rom zip you last attempted to install and put it into the folder you extract from this https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc/edit?usp=sharing . Open a CMD prompt and change directories to the adb+fastboot folder and then you'll want to be in bootloader mode and plugged in (make sure fastboot is selected and it should change to fastboot usb when recognized by PC) then copy and paste this without qoutes: "fastboot flash boot.img" and hit enter. This should send the kernel that you'll need to boot to the phone. Then just to be certain everything gets back in place, boot to recovery and factory reset and flash the rom again. Should be back up and running in no time.
es0tericcha0s said:
It's almost certainly an issue with a locked or semi-locked bootloader. If you are just HTC Dev unlocked on most HTCs, you need to flash the boot.img (kernel) via fastboot or when booted, with an app like Flashify. The reason you are having issues with getting it to connect is because Win 8.1 has issues with the HTC fastboot driver, especially on USB 3.0 ports on some makes of PCs. Grab another computer that has Win 7, if possible. Linux is an option as well, depending on how comfortable you are using it. But anyway, get to a PC that doesn't have Win 8+, get the HTC Sync program installed to get all of the drivers properly set up, then extract the boot.img from rom zip you last attempted to install and put it into the folder you extract from this https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc/edit?usp=sharing . Open a CMD prompt and change directories to the adb+fastboot folder and then you'll want to be in bootloader mode and plugged in (make sure fastboot is selected and it should change to fastboot usb when recognized by PC) then copy and paste this without qoutes: "fastboot flash boot.img" and hit enter. This should send the kernel that you'll need to boot to the phone. Then just to be certain everything gets back in place, boot to recovery and factory reset and flash the rom again. Should be back up and running in no time.
Click to expand...
Click to collapse
Thank you very much, for your reply
I hit thanks button too
I'll get back to you soon as i perform the steps you've stated in a Win 7 PC.
sadly NO
pjohn23 said:
what i mean is windows tool that can flash stock rom on your phone. if it has. you should use that and wipe everything
Click to expand...
Click to collapse
i appreciate your help, but sadly there is no software specific to HTC explorer such as ODIN for samsung.
I'll try the procedure in a Win 7 PC and get back to you guys.
Thanks
DrSakethReddy said:
i appreciate your help, but sadly there is no software specific to HTC explorer such as ODIN for samsung.
I'll try the procedure in a Win 7 PC and get back to you guys.
Thanks
Click to expand...
Click to collapse
Goodluck bro. sorry for no help. i dont have HTC and everythings waay more easier on a xperia phone
DrSakethReddy said:
i appreciate your help, but sadly there is no software specific to HTC explorer such as ODIN for samsung.
I'll try the procedure in a Win 7 PC and get back to you guys.
Thanks
Click to expand...
Click to collapse
Not true. Their tool is called RUU (Rom Update Utility). I'm assuming your phone is the Indian version from your location. If that is so, you'll find your download for the RUU here: http://www.4shared.com/mp3/JRRnTB2c/file.htm?cau2=s403 or http://uploaded.net/file/yan28lnl . They aren't the fastest downloads, but should work. Need to have more than 30% battery life, antivirus off, and drivers installed. Boot to bootloader / fastboot mode, then just double click the RUU exe and follow the instructions and accept all the terms. If the exe doesn't work, there are a couple of other ways to flash, but as long as your cord / drivers / PC are all working properly, you should be back to stock, if that's what you would rather do. This method could wipe internal storage if you have one.
pjohn23 said:
Goodluck bro. sorry for no help. i dont have HTC and everythings waay more easier on a xperia phone
Click to expand...
Click to collapse
Hey ! C'mon. Don't say u didn't help !
Providing a light to this thread for others to answer it too was the read deal you made !
Thanks again, bro
AWESOME !
es0tericcha0s said:
Not true. Their tool is called RUU (Rom Update Utility). I'm assuming your phone is the Indian version from your location. If that is so, you'll find your download for the RUU here: http://www.4shared.com/mp3/JRRnTB2c/file.htm?cau2=s403 or http://uploaded.net/file/yan28lnl . They aren't the fastest downloads, but should work. Need to have more than 30% battery life, antivirus off, and drivers installed. Boot to bootloader / fastboot mode, then just double click the RUU exe and follow the instructions and accept all the terms. If the exe doesn't work, there are a couple of other ways to flash, but as long as your cord / drivers / PC are all working properly, you should be back to stock, if that's what you would rather do. This method could wipe internal storage if you have one.
Click to expand...
Click to collapse
Great ! I love getting things done easier with tools !
I'll give this a shot too, and then if this doesn't work, i'll head for the recovery.img flashing .
Thanks
Unsuccessful ! (error)
es0tericcha0s said:
It's almost certainly an issue with a locked or semi-locked bootloader. If you are just HTC Dev unlocked on most HTCs, you need to flash the boot.img (kernel) via fastboot or when booted, with an app like Flashify. The reason you are having issues with getting it to connect is because Win 8.1 has issues with the HTC fastboot driver, especially on USB 3.0 ports on some makes of PCs. Grab another computer that has Win 7, if possible. Linux is an option as well, depending on how comfortable you are using it. But anyway, get to a PC that doesn't have Win 8+, get the HTC Sync program installed to get all of the drivers properly set up, then extract the boot.img from rom zip you last attempted to install and put it into the folder you extract from this https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc/edit?usp=sharing . Open a CMD prompt and change directories to the adb+fastboot folder and then you'll want to be in bootloader mode and plugged in (make sure fastboot is selected and it should change to fastboot usb when recognized by PC) then copy and paste this without qoutes: "fastboot flash boot.img" and hit enter. This should send the kernel that you'll need to boot to the phone. Then just to be certain everything gets back in place, boot to recovery and factory reset and flash the rom again. Should be back up and running in no time.
Click to expand...
Click to collapse
Hello, i followed the exact steps that you provided, but i got an error in the cmd saying :
"unknown partition 'boot,img'
error: cannot determine image filename for 'boot.img' !
I'll try the RUU method now.
Alas ! Error again
es0tericcha0s said:
Not true. Their tool is called RUU (Rom Update Utility). I'm assuming your phone is the Indian version from your location. If that is so, you'll find your download for the RUU here: http://www.4shared.com/mp3/JRRnTB2c/file.htm?cau2=s403 or http://uploaded.net/file/yan28lnl . They aren't the fastest downloads, but should work. Need to have more than 30% battery life, antivirus off, and drivers installed. Boot to bootloader / fastboot mode, then just double click the RUU exe and follow the instructions and accept all the terms. If the exe doesn't work, there are a couple of other ways to flash, but as long as your cord / drivers / PC are all working properly, you should be back to stock, if that's what you would rather do. This method could wipe internal storage if you have one.
Click to expand...
Click to collapse
I've done the adb command method and failed, now i've even performed updating it with RUU, but i have this result :
ERROR 155: unkown error
The ROM Update Utility cannot update your android phone.
Please get the correct ROM Update Utility and update your phone.
DrSakethReddy said:
Hello, i followed the exact steps that you provided, but i got an error in the cmd saying :
"unknown partition 'boot,img'
error: cannot determine image filename for 'boot.img' !
I'll try the RUU method now.
Click to expand...
Click to collapse
I'm so sorry! I left out something in that command! It's:
fastboot flash boot boot.img
Sorry, poor proofreading skills.
As far as the 155 error, I think you also might need to do this in bootloader / fastboot mode (if the previous command doesn't get you going with the rom you are already on - it should):
fastboot oem lock
Then re-run RUU.
Sorry guys, for a very late reply.
I tried all the methods you said, with the new command too, but alas ! The device didn't get a life.
I'm gonna use it as a very costly paperweight now !
hi guys, i hope you can help me.
I install android sdk and usb google drivers.
when my n9 is on adb recognise it and i can find it in list of device attacched.
when i reboot in recovery my device insn't listed anymore and when i try to sideload the ota it says "device not found"
i tried to reinstall drivers but it hasn't fixed anything.
What can i do?
zera89 said:
hi guys, i hope you can help me.
I install android sdk and usb google drivers.
when my n9 is on adb recognise it and i can find it in list of device attacched.
when i reboot in recovery my device insn't listed anymore and when i try to sideload the ota it says "device not found"
i tried to reinstall drivers but it hasn't fixed anything.
What can i do?
Click to expand...
Click to collapse
When booted into recovery go to device manager on your pc. Do you see an icon with a yellow exclamation mark? If so, right click on it and go to where it lets you choose a driver from a list on the computer. Choose android adb composite interface.
Sent from my Nexus 5 using XDA Free mobile app
zera89 said:
hi guys, i hope you can help me.
I install android sdk and usb google drivers.
when my n9 is on adb recognise it and i can find it in list of device attacched.
when i reboot in recovery my device insn't listed anymore and when i try to sideload the ota it says "device not found"
i tried to reinstall drivers but it hasn't fixed anything.
What can i do?
Click to expand...
Click to collapse
jd1639 said:
When booted into recovery go to device manager on your pc. Do you see an icon with a yellow exclamation mark? If so, right click on it and go to where it lets you choose a driver from a list on the computer. Choose android adb composite interface.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
In addition to what @jd1639 said, once your device is recognized by your PC, if you continue to have problems when in recovery menu, try to unplug and replug in your USB cable.
jd1639 said:
When booted into recovery go to device manager on your pc. Do you see an icon with a yellow exclamation mark? If so, right click on it and go to where it lets you choose a driver from a list on the computer. Choose android adb composite interface.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
EDIT
i found it and i install composite adb driver even if windows was saying me that it can't verify driver's signature.
installing ota with sideload is safe?
zera89 said:
EDIT
i found it and i install composite adb driver even if windows was saying me that it can't verify driver's signature.
installing ota with sideload is safe?
Click to expand...
Click to collapse
Yes. I would add that it's a good idea to unlock your bootloader first. If something goes wrong and your bootloader is locked, you're pretty much screwed.
cam30era said:
Yes. I would add that it's a good idea to unlock your bootloader first. If something goes wrong and your bootloader is locked, you're pretty much screwed.
Click to expand...
Click to collapse
are you talking about OEM UNLOCK in developer options?
zera89 said:
are you talking about OEM UNLOCK in developer options?
Click to expand...
Click to collapse
Actually two steps. 1st check that box in developer options. 2nd, boot to bootloader and enter this command > fastboot oem unlock
NOTE: This will wipe the contents of your SDcard.
cam30era said:
Actually two steps. 1st check that box in developer options. 2nd, boot to bootloader and enter this command > fastboot oem unlock
NOTE: This will wipe the contents of your SDcard.
Click to expand...
Click to collapse
i was looking for a way to force ota without wipe or unlocking...
do you suggest me OTA sideload procedure or wait for official ota?
zera89 said:
i was looking for a way to force ota without wipe or unlocking...
do you suggest me OTA sideload procedure or wait for official ota?
Click to expand...
Click to collapse
Your choice. Process and likely outcomes do not differ. My point is regarding risk and reward. I understand that you don't want to unlock or wipe. My caution to you is this: the OTA package sometimes fails to install, part way through the process. If your bootloader is locked, your device will probably be bricked and your only option will be RMA. I'm not trying to scare you into doing something you don't want to do, just pointing out the facts. And it doesn't matter whether you sideload the OTA, or wait for it to show up on your device. The risk is the same.
On the other hand, if your bootloader is unlocked, and the OTA fails, you can easily recover from it. In fact, you don't even need to sideload the OTA. You can then fastboot flash the Google factory image.
uhm... ok... i'm understanding...
don't you think a bricking ota is almost a paradox?
i mean... Htc & Google make a update with errors or problems? it's foolish.
I can understand a custom rom but two giants like 'em...
i don't know what to do... i'm gonna think about it
thanks for your help!
zera89 said:
uhm... ok... i'm understanding...
don't you think a bricking ota is almost a paradox?
i mean... Htc & Google make a update with errors or problems? it's foolish.
I can understand a custom rom but two giants like 'em...
i don't know what to do... i'm gonna think about it
thanks for your help!
Click to expand...
Click to collapse
I'm certainly not debating the paradox with you. I'm just providing advice based on my own experience, and the (unfortunate) experience of other users on this forum. Good luck with what ever you decide to do here....
I did a search on XDA and didn't find anyone quite with this problem. I have other HDX both 7" and 8.9" that I have unlocked bootloader, installed TWRP, and installed ROM's on so I am not new to it.
However, I acquired an 8.9" HDX and it is stuck on the Nougat logo and just stays there. I can boot into fastboot as well as TWRP. When I booted into TWRP I tried factory reset (as it will come up on my computer to where I can access the storage using my Windows 10 machine) as well as Advanced Wipe but it will not wipe the Internal Storage. It still shows all the files that were on there before. How do I go about completely getting it clean to install a nice fresh custom ROM on it?
Any help would be greatly appreciated thanks all!
alias4ever said:
I did a search on XDA and didn't find anyone quite with this problem. I have other HDX both 7" and 8.9" that I have unlocked bootloader, installed TWRP, and installed ROM's on so I am not new to it.
However, I acquired an 8.9" HDX and it is stuck on the Nougat logo and just stays there. I can boot into fastboot as well as TWRP. When I booted into TWRP I tried factory reset (as it will come up on my computer to where I can access the storage using my Windows 10 machine) as well as Advanced Wipe but it will not wipe the Internal Storage. It still shows all the files that were on there before. How do I go about completely getting it clean to install a nice fresh custom ROM on it?
Any help would be greatly appreciated thanks all!
Click to expand...
Click to collapse
There's a chance the eMMC is damaged or a prior owner botched an unlock attempt. Might try booting a freshly downloaded TWRP image from fastboot in case the one that is installed has an issue. This will only work if the bootloader is unlocked.
fastboot boot <twrp.img>
Davey126 said:
There's a chance the eMMC is damaged or a prior owner botched an unlock attempt. Might try booting a freshly downloaded TWRP image from fastboot in case the one that is installed has an issue. This will only work if the bootloader is unlocked.
fastboot boot <twrp.img>
Click to expand...
Click to collapse
If the bootloader is indeed still locked and I have access to the bootloader can I unlock it still and start fresh? I take it the above I do inside the platform-tools folder correct? Thanks Davey so much for your help. I did this multiple times but it's been a while so I'm just trying to refresh my brain!
alias4ever said:
If the bootloader is indeed still locked and I have access to the bootloader can I unlock it still and start fresh? I take it the above I do inside the platform-tools folder correct? Thanks Davey so much for your help. I did this multiple times but it's been a while so I'm just trying to refresh my brain!
Click to expand...
Click to collapse
Consider following the steps in this post which nicely sumarizes the unlock procedure. Not for the faint of heart nor excessively difficult. Ability to closely follow instructions and troubleshoot issues are the keys to success...assuming hardware is ok.
Before jumping in try booting a twrp image to rule out a borked install in the recovery partition. Unlikely, but also easy to check.
Davey126 said:
Consider following the steps in this post which nicely sumarizes the unlock procedure. Not for the faint of heart nor excessively difficult. Ability to closely follow instructions and troubleshoot issues are the keys to success...assuming hardware is ok.
Before jumping in try booting a twrp image to rule out a borked install in the recovery partition. Unlikely, but also easy to check.
Click to expand...
Click to collapse
So to check I would just do what you suggested above with the Fire HDX in Fastboot and connected to my PC correct? Which was:
fastboot boot apollo_twrp-3.2.3-1.img in CMD correct? I just want to make sure I have "all my ducks in a row."
alias4ever said:
So to check I would just do what you suggested above with the Fire HDX in Fastboot and connected to my PC correct? Which was:
fastboot boot apollo_twrp-3.2.3-1.img in CMD correct? I just want to make sure I have "all my ducks in a row."
Click to expand...
Click to collapse
Yup. No damage can come from this attempt. It will either work or not.
Davey126 said:
Yup. No damage can come from this attempt. It will either work or not.
Click to expand...
Click to collapse
This is what I get when I try that:
FAIL: boot not allowed for locked hw.
Any suggestions please? Thanks again!
alias4ever said:
This is what I get when I try that:
FAIL: boot not allowed for locked hw.
Any suggestions please? Thanks again!
Click to expand...
Click to collapse
Indicates bootloader is locked. See previous posts for path forward. Note cautions; don't expect a lot of hand holding if uncomfortable with tools/procedures. Good luck.
Davey126 said:
Indicates bootloader is locked. See previous posts for path forward. Note cautions; don't expect a lot of hand holding if uncomfortable with tools/procedures. Good luck.
Click to expand...
Click to collapse
Hey Davey, one last question I hope. I can't boot into a ROM (I can do either Fastboot or TWRP) to get the unlock code doing the following from the instructions:
2. Turn on ADB-Debuging Mode in Developer Mod by tapping 7 times the build numbers in settings and connect to your computer + trust your device.
3. Excecute "get_code.bat" in the folder above, you will get a new file: unlock.code in the folder.
I can't copy a ROM to TWRP as it won't let me. I have searched and searched and I am stuck again. Please if you don't mind helping me as I remember how to do most everything (it is coming back to me more and more the more I read and what not) but I have never been stuck with the unlock code. Thanks so much.
alias4ever said:
Hey Davey, one last question I hope. I can't boot into a ROM (I can do either Fastboot or TWRP) to get the unlock code doing the following from the instructions:
2. Turn on ADB-Debuging Mode in Developer Mod by tapping 7 times the build numbers in settings and connect to your computer + trust your device.
3. Excecute "get_code.bat" in the folder above, you will get a new file: unlock.code in the folder.
I can't copy a ROM to TWRP as it won't let me. I have searched and searched and I am stuck again. Please if you don't mind helping me as I remember how to do most everything (it is coming back to me more and more the more I read and what not) but I have never been stuck with the unlock code. Thanks so much.
Click to expand...
Click to collapse
Don't worry about the unlock code; you can grab that later. The more immediate task is to install a vulnerable bootloader (aka 'aboot') and update twrp. Keep in mind this may not help if your newly acquired device is severely borked or has a hardware issue.
Davey126 said:
Don't worry about the unlock code; you can grab that later. The more immediate task is to install a vulnerable bootloader (aka 'aboot') and update twrp. Keep in mind this may not help if your newly acquired device is severely borked or has a hardware issue.
Click to expand...
Click to collapse
Well so I followed this thread: https://forum.xda-developers.com/showpost.php?p=75284993&postcount=1006
Then I started here (just past the unlock code):
5. On the Computer go to Device-Manager and change driver in "Other Android" to "Fire Devices - Android Adb Composite Driver" . It should say "Ready" on the Kindle.
6. Now we need to enter Bulk-Mode like the instruction in this thread: Bulk Mode
Type:
Quote:
Code:
fastboot -i 0x1949 erase aboot
fastboot -i 0x1949 reboot
CMD shows that everything was successful but upon the reboot it just tried to boot into the OS instead of Bulk Mode that is installed that it can't boot into. I can still boot back into TWRP 3.1.1-1 as well as Fastboot.
ARGH! Any other suggestions Davey? I'm sorry to keep bugging you I just don't understand what is happening.
alias4ever said:
Well so I followed this thread: https://forum.xda-developers.com/showpost.php?p=75284993&postcount=1006
Then I started here (just past the unlock code):
5. On the Computer go to Device-Manager and change driver in "Other Android" to "Fire Devices - Android Adb Composite Driver" . It should say "Ready" on the Kindle.
6. Now we need to enter Bulk-Mode like the instruction in this thread: Bulk Mode
Type:
Quote:
Code:
fastboot -i 0x1949 erase aboot
fastboot -i 0x1949 reboot
CMD shows that everything was successful but upon the reboot it just tried to boot into the OS instead of Bulk Mode that is installed that it can't boot into. I can still boot back into TWRP 3.1.1-1 as well as Fastboot.
ARGH! Any other suggestions Davey? I'm sorry to keep bugging you I just don't understand what is happening.
Click to expand...
Click to collapse
Sounds like the device/firmware is borked. You can try to issue the erase cmd wothout "-i 0x1949" (fastboot erase aboot) although that too will likely fail. At that point you're pretty much out of options short of a deep technical dive that is fraught with risk. Such travels are above my pay grade; you'd want to reach out to @draxie.
Davey126 said:
Sounds like the device/firmware is borked. You can try to issue the erase cmd wothout "-i 0x1949" (fastboot erase aboot) although that too will likely fail. At that point you're pretty much out of options short of a deep technical dive that is fraught with risk. Such travels are above my pay grade; you'd want to reach out to @draxie.
Click to expand...
Click to collapse
I did send a PM to @draxie so hopefully he can help me and we can get this Fire HDX up and running. Thanks for all your help though @Davey. I really appreciate it. I am going to keep my fingers crossed still though in hopes that draxie can help me. :good::fingers-crossed: