Related
Okay so I'm new to Android. I have been trying to update to a new rom but have pretty much got stuck at the first hurdle. I have been trying to follow http://forum.xda-developers.com/showthread.php?t=552591
MoDaCo Custom ROM is here (2 versions based on the 'new update')!
As stated in the first thing to do for a newbie is to Download the patched recovery image linked above and install as detailed in that post.
I have not been able to get pasted this stage
Please please please can someone write an idiots guide for this as by the end of tonight I’m going to be bald as I’m pulling my hair out.
robboy said:
Okay so I'm new to Android. I have been trying to update to a new rom but have pretty much got stuck at the first hurdle. I have been trying to follow http://forum.xda-developers.com/showthread.php?t=552591
MoDaCo Custom ROM is here (2 versions based on the 'new update')!
As stated in the first thing to do for a newbie is to Download the patched recovery image linked above and install as detailed in that post.
I have not been able to get pasted this stage
Please please please can someone write an idiots guide for this as by the end of tonight I’m going to be bald as I’m pulling my hair out.
Click to expand...
Click to collapse
1. make a full nandroid backup
2.download the recovery image
3.turn off your phone and turn on by pressing the on button+the back key (to get into bootloader)
4.open a terminal from the folder which contains the recovery image.
5. type 'fastboot boot cm-hero-recovery.img'
6.type 'adb shell mount /sdcard'
7.type 'adb push cm-hero-recovery.img /sdcard/cm-hero-recovery.img'
8.type 'adb shell flash_image recovery /sdcard/cm-hero-recovery.img'
now whenever you want to access the recovery console, you just have to switch your phone on+home key and u'll enter.
To install the rom,
9. download the radio and rom from modaco
10. plug in ur usb and mount sd card
11. copy radio into sd card and rename to update.zip.
12. switch off phone and enter recovery console
13.if you never upgraded the phn , then a wipe is necessary
14. then, select update.zip..
15. u repeat the steps from step9 onwards the same way to update the rom.
hope ie helped.
i mentioned nandroid backup as from step 1 itself.
just came to realise that maybe u have never accessed recovery image from pc.
well dont worry, u can ignore step one but be sure to make the backup after step 8 ..... before installing the new rom
cheers and good luck
Okay so number 4 is my problem. Do o do this from the phone or pc?
robboy said:
Okay so number 4 is my problem. Do o do this from the phone or pc?
Click to expand...
Click to collapse
From the pc. A DOS terminal, if you are on windows.
should I allready have partitioned my sd card before i do this?
This is the error message i get
robboy said:
This is the error message i get
Click to expand...
Click to collapse
As far as I can see, you opened the command-line in the system32 dir from youre PC?! You should open the commandline in the dir where the image-file is. Should look like C:\SDK\tools
See this post to guide you further.
http://forum.xda-developers.com/showpost.php?p=4257045&postcount=38
robboy said:
This is the error message i get
Click to expand...
Click to collapse
To open a terminal( command prompt) from a folder,
1.go to accesories in Windows, copy the command prompt.
2. Go to your folder and paste it there.
3.right click on the command prompt, go on prope
rties.
4. U will find a line containing ' start in : %homedrive%%homepath....'
5. Delete that line so that 'start in' remains blank
6. Apply. And u r good to go
By the way. I supposed u already installed HTC sync right.
okay I thought HTC sync might be causing me problems so i removed it
robboy said:
okay I thought HTC sync might be causing me problems so i removed it
Click to expand...
Click to collapse
You will need to install HTC sync cause it contains the drivers for you phone.
Okay so I have put HTC sync back on. My hero connects to the sync in normal mode as an android USB devices - My HTC . What I'm unsure of now is when I press 'on and back buttons to go into bootloader' should the hero still sync as My HTC or should it be syncing to a different driver. I have been going round in circles all day. I have also removed the android development software as before the hero was syncing as and adb device??
When going to the cdm I now get the error device not found. USB debugging is selected on my device.
I think I’m on the brink of giving up.
okay so now when I'm in the bootloader my device connects as a ADB Interface - HTC Bootloader.
BTW I'm on Vista and i selected the driver that was in x86 folder that I was advised to download. However still no device found
robboy said:
Okay so I have put HTC sync back on. My hero connects to the sync in normal mode as an android USB devices - My HTC . What I'm unsure of now is when I press 'on and back buttons to go into bootloader' should the hero still sync as My HTC or should it be syncing to a different driver. I have been going round in circles all day. I have also removed the android development software as before the hero was syncing as and adb device??
When going to the cdm I now get the error device not found. USB debugging is selected on my device.
I think I’m on the brink of giving up.
Click to expand...
Click to collapse
Yes if your device is recognised as adb ... it's good.
That's how it should be.
Try installing HTC sync before plugging ur phone, then enter bootloader on the phn, plug it in, and then perform the command from the prompt.
P.s try entering bootloader first and only afterwards u plug in ur phone
Try to get the latest driver HTC sync from HTC site. If that doesnt work, try downloading the latest sdk plus drivers. U can find it somewhere on the forum . I think that there is a link on the rooting guide by daysee
I'm a total noob at Android too but theunlockr.com was the easiest and fastest way for me to install the custom Modacco ROM. Check out their site; it'll show you step by step with videos :]
Hi,
the last days, I read a lot about flashing custom ROMs and wanted to do so with my HTC Legend. I'm not really new to flashing ROMs in general.I already flashed several other devices, but I'm stuck with unlocking the bootloader. My problem is, that the CMD is either reacting with "CommandError" or "waiting for device". I'm not able to get the token for unlocking the bootloader. Another problem is, that the SDK Manager won't start for me. So I just grabbed the 3 files out of the filesystem and tried it with them. Using HTCs recommended fastboot.exe doesn't change anything. I hope you can help me with a few details:
1. Do I have to install something else than HTC Sync? (I think, it already installed the driver, too)
2. Which connection mode should i choose, when connecting the legend? (recharging/hdd/htc sync/tethering)
3. Which version of the SDK should I use? Is it possible, that someone just gives me a zip with those 3 files?
I'm looking forward to your answers!
Regards
OdlG
SOLUTION:
The solution was a too old version. My phone had version 3.15.405.3.
First I updated to version 3.15.405.6 (found via google here at xda-dev).
Then I patched the new ROM I downloaded from htc-dev (step 0 at unlocking; must connect phone for that hint!) 3.30.0.0.
Then I could receive the token via CMD at a Windows 7 PC (Win8 PC still said "waiting for device", obviously because the driver wasn't installed correctly so the phone wasn't recognised in fastboot mode).
I followed the last steps rom htc-dev and now unlocked the bootloader
Click to expand...
Click to collapse
(pardon my english, it's not my mothertongue)
AW: Difficulties with unlocking the Bootloader
You should use charging mode and you have to activate usb debugging in settings
Sent from my HTC One using xda app-developers app
Thanks for the reply!
I already enbled USB Debugging, and now tried it in charging mode. I created a BAT-File with the following command:
cd C:\Android\
fastboot oem get_identifier_token
But it still says "waiting for device" Any suggestions?
Did you follow these instructions? especcially selecting "fastboot"?
http://www.htcdev.com/bootloader/unlock-instructions
if yes and it still didn't work i've no idea at the moment
I tried it once more:
I connected the phone, "fastboot usb" is written there. the cmd still writes "waiting for device". after a few seconds, the pc reports, that the usb device could not be recognised. then there is written "fastboot" instead of "fastboot usb", though the cable is still connected.
a few hours ago i also got a guide at htc dev, that i should install da RUU (what does it mean btw?). i downloaded the german vodafone version and tried to install it. I will try that once more, hopefully the unlock will be successful afterwards!
thanks for your advice!
EDIT:I'm using the following software btw.
Android SDK (adt-bundle-windows-x86_64-20130219)
Java RE 7 Update 17
HTC Sync (3.3.X or something like that)
The RUU installer is starting the setup without problems. It's rebooting the phone o install version 3.30 (hboot1.02). But when the Phone starts in the bootloader mode and displays "RUU", the PC is unable to detect the USB device and the setup fails caused by missing usb connection
Can I somehow influence the detection of the phone in fastboot/bootloader mode?
Normally it should be enough to install the HTC USB Drivers...
You can grab the newest for example from this thread: http://forum.xda-developers.com/showthread.php?t=2191279
The second what you need is an actual adb.exe, fastboot.exe, AdbWinApi.dll & AdbWinUsbApi.dll... grab it for example from here: http://d-h.st/RvD (Thanx to torxx (http://forum.xda-developers.com/member.php?u=3828647))
After u've installed the drivers and extracted the adb file do the folowing
Turn off your phone completly
Push Vol down & Power ...device will start
Navigate with vol+- to fastboot press power
connect with usb-cable (possible that windows will install drivers...wait till its complete)
now "fastboot usb" should be read in the display of your phone
open a shell (cmd)
navigate to your fastboot.exe
type: "fastboot oem get_identifier_token"
it seems, that my htc firmware is far too old (3.15.405.3). i installed all the stuff on my win7 laptop instead of win8 desktop pc and could install the RUU... at least untill the notification, that i needed to update the firmware first, and update hboot1.02 (3.30.0.0) afterwards. the big update is also 150MB, the small one only 5MB. i'll give it a try and report back here, if i am able to manage all the stuff^^
btw autoupdating via options doesn't work ("phone is up to date"). do i have to sign in via google to get a better result?
I managed to unlock the bootloader!
The solution was a too old version. My phone had version 3.15.405.3.
First I updated to version 3.15.405.6 (found via google here at xda-dev).
Then I patched the new ROM I downloaded from htc-dev (step 0 at unlocking; must connect phone for that hint!) 3.30.0.0.
Then I could receive the token via CMD at a Windows 7 PC (Win8 PC still said "waiting for device", obviously because the driver wasn't installed correctly so the phone wasn't recognised in fastboot mode).
I followed the last steps rom htc-dev and now unlocked the bootloader
now i will try the rest Thanks for the helpful hints!
AW: [solved] Difficulties with unlocking the Bootloader
Okay nice to hear that it now works:thumbup:
I would say... Have fun while flashing and trying new roms
Sent from my HTC One using xda app-developers app
esco27 said:
Okay nice to hear that it now works:thumbup:
I would say... Have fun while flashing and trying new roms
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Already flashed CM10.1 It's not as smooth as on my Ainol Aurora 2 Tablet, but the Legend hasn't got the power by far. But if you have a look at the specs, it is amazing, how good it runs on the legend
Thanks for all the help! That was definately worth it^^ I only have minor problems with my SIM-card up to now.
Hi!
I'm an unhappy owner of HTC Legend with Android 2.2 and HBoot 1.01.0000. I tried to root and S-OFF my device, but I can't do that. I spent a lot of time to find a solution of my problem.
How to root and S-OFF HTC Legend with HBoot 1.01.0000?
My English is not very good, but I understand everything I see.
Greetings.
1st you can't s-off hboot 1.01
Just goto htcdev website, register, and carefully follow ALL directions to unlock your bootloader for HTC legend, this is all you really need.
You will also need to read up about how to flash custom recovery and flash custom Rom.
Sent from my HTC Desire HD using xda app-developers app
I also try to root my Legend with HBoot 1.01.0000 so i thought it would be better to unite instead of starting a new thread.
I am facing the problem that the device is not recognized when i am in the bootloader (power button + volume down).
When the Android it boot up normally the devices is recognized.
Code:
adb devices
The same problem occur when i try to update HBoot to 1.02.
I tried this on my Windows 8 x64 PC, i did read more people have problems with Windows 8. Te be sure it isn't Windows 8 i did download a live cd of ubuntu 12.04lts and installed the ppa:nilarimogard/webupd8.
Code:
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb
sudo apt-get install android-tools-fastboot
After this i connect my Legend with android loaded. And the phone is recognized.
Code:
adb devices
When i go to the bootloader the phone is not recognized.
Anyone who could help me out?
Have you got debugging turned on on your phone? Have you got your drivers correctly installed? (check via device manager on windows 8 p.s, don't ask where or how cause I will never use windows 8!)
You may need android v1 drivers too, I dont know...
At the end of the day I reckon it's all down to win 8 issue.
What about the cable your using, it's not stuffed is it?
Sent from my HTC Desire HD using xda app-developers app
ranger4740 said:
Have you got debugging turned on on your phone? Have you got your drivers correctly installed? (check via device manager on windows 8 p.s, don't ask where or how cause I will never use windows 8!)
You may need android v1 drivers too, I dont know...
At the end of the day I reckon it's all down to win 8 issue.
What about the cable your using, it's not stuffed is it?
Sent from my HTC Desire HD using xda app-developers app
Click to expand...
Click to collapse
I am using a USB 2.0 port. And i HTC Sync 3.3.53
HTC BMP USB Driver 1.0.5375 (64-Bit)
HTC Driver Installer 4.1.0.001
If i have HTC Sync installed, the device is showing up in the device manager: Android USB Devices > My HTC
When i do not have HTC Sync installed, i see it also appear under device manager: ADB Bootloader > HTC Bootloader
Both give the same error: (Code 10) A request for the USB BOS descriptor failed.
When i update the driver (Android 1.0) i get the message: The best driver is already installed.
USB debugging is enabled.
Edit:
I think i found the problem, i used the USB 2.0 port from the front of the case, which also has USB 3.0.
Now i tried a 2.0 port directly on my motherboard and i see it coming up without a problem. I however did try that before without succes, i already did read about USB 3.0 problem.
It looks like i first need to update HBoot before i am able to get this token:
Code:
fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.008s
When i download a HBOOT i get the message i first need to upgrade to at least: 3.15.405.3 but i am running 3.15.405.7
Now i am on my Macbook Pro.
Downloaded the Google Android SDK for mac, and copied it to my home folder.
I still get the damn error:
Code:
fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.007s
When i change to bootloader and do:
Code:
adb devices
List of devices attached
nothing is showing up.
And when i boot up the HTC legend normally. And attach the USB cable (charge only)
And do:
Code:
adb devices
List of devices attached
HT06NNX00571 device
So this is exactly the same as what happend on my Windows 8 PC.
If I remember correctly you can't use adb from bootloader anyway, only fastboot.
I suggest using blay0s method by extracting the Rom.zip from the exe this is done by running the ruu, letting it extract its temp files, then do a harddrive search for Rom.zip you have to include hidden and system folders in the search it will be in a temp folder some where.
Copy the Rom.zip to another folder them rename it to LEGEIMG.ZIP I think it is, copy it to the root of the sdcard from your phone then turn on phone with vol down and power, the bootloader should find it and ask to install.
Sent from my HTC Desire HD using xda app-developers app
ranger4740 said:
If I remember correctly you can't use adb from bootloader anyway, only fastboot.
I suggest using blay0s method by extracting the Rom.zip from the exe this is done by running the ruu, letting it extract its temp files, then do a harddrive search for Rom.zip you have to include hidden and system folders in the search it will be in a temp folder some where.
Copy the Rom.zip to another folder them rename it to LEGEIMG.ZIP I think it is, copy it to the root of the sdcard from your phone then turn on phone with vol down and power, the bootloader should find it and ask to install.
Sent from my HTC Desire HD using xda app-developers app
Click to expand...
Click to collapse
Still no luck. I found the howto of blay0s.
I have tried this versions:
PB7610000_Legend_Froyo_S_hboot_1.02.0000_R.exe
PB7610000_Legend_Froyo_S_hboot_1.02.0000_R2.exe
PB7611000_Legend_Froyo_S_hboot_1.02.0000_R.exe
It does not ask me to upgrade the bootloader Or as explained in post 74 it will upgrade automatically and ask to reboot.
Edit:
Finally it did ask me. Problem is the SD card needed to be FAT32 instead of FAT.
Hi Everyone / Anyone,
Got this HTC ONE X+ (64GB) (Not AT&T as only has "HTC" logo on phone) phone from another user who i think spoil the
phone with Cyanogenmod as it keeps reboot and stuck in CYM screen with spining arrows.
Read some posts here and managed to reboot into recovery screen and get some data. It cannot charge properly,
so flash with latest TWRP v2.6.3.0 and now can fully charge to LED turns green.
Some of info of this phone are:
*** UNLOCKED ***
ENRC2B_U PVT SHIP S-ON RL
HBOOT : 1.72.0000
CPLD : None
MICROP : None
RADIO : 3.1204.171.33
eMMC-bootmode : disabled
CPU-bootmode : disabled
HW Secure boot : enabled
MODEM PATH : OFF
Jun 21 2013, 17:36:36
Run fastboot getvar all and some info are:
Version-main : 2.18.707.5
Platform : HBOOT-T30S
Modelid : PM3511000
Cidnum : HTC__044
Battery-status : good
dev-power : 91
partition-layout : None
commitno-bootloader : None
My problem now its seem the HBOOT is very new and not able to find suitable version of 2.18.707.5 image.
Tried run RUU from various sources (WWE, EUROPE,..) cannot flash into the phone. I do not know where
is the reliable ones now and not sure what's next? Have used Hansoon AIO kit and WinDroid, these are helpful
but my phone status does not allow the kit to execute fully.
Now the CYM screen is gone and only show HTC logo screen and cannot proceed to boot further. Of course it
seem the ROM (Custom or stock) are gone as previous user did not make any backup and spoil it.
Summary of what i can do with the phone now:
Reboot phone into recovery mode or Fastboot. Can link PC and phone show FastBoot USB. Can fastboot to phone for lock / unlock.
Observed feedback from TWRP there is no root folder as suggest to install SuperUSR but not sure is it successful.
HELP, Need advice and help to find and load back factory stock ROM or any version suitable for it.
Think it does not have a proper root loaded too.
Installing a custom ROM will be easy
Wipe all excluding the Internal Storage from TWRP
Just "adb push" the ROM file to the SDCARD once the installation is done
boot into fastboot
flash the kernel from the fastboot........
that should get ur phone booted refer to this tutorial for installing a custom ROM
GoRiLaz301 said:
Hi Everyone / Anyone,
Got this HTC ONE X+ (64GB) (Not AT&T as only has "HTC" logo on phone) phone from another user who i think spoil the
phone with Cyanogenmod as it keeps reboot and stuck in CYM screen with spining arrows.
Read some posts here and managed to reboot into recovery screen and get some data. It cannot charge properly,
so flash with latest TWRP v2.6.3.0 and now can fully charge to LED turns green.
Some of info of this phone are:
*** UNLOCKED ***
ENRC2B_U PVT SHIP S-ON RL
HBOOT : 1.72.0000
CPLD : None
MICROP : None
RADIO : 3.1204.171.33
eMMC-bootmode : disabled
CPU-bootmode : disabled
HW Secure boot : enabled
MODEM PATH : OFF
Jun 21 2013, 17:36:36
Run fastboot getvar all and some info are:
Version-main : 2.18.707.5
Platform : HBOOT-T30S
Modelid : PM3511000
Cidnum : HTC__044
Battery-status : good
dev-power : 91
partition-layout : None
commitno-bootloader : None
My problem now its seem the HBOOT is very new and not able to find suitable version of 2.18.707.5 image.
Tried run RUU from various sources (WWE, EUROPE,..) cannot flash into the phone. I do not know where
is the reliable ones now and not sure what's next? Have used Hansoon AIO kit and WinDroid, these are helpful
but my phone status does not allow the kit to execute fully.
Now the CYM screen is gone and only show HTC logo screen and cannot proceed to boot further. Of course it
seem the ROM (Custom or stock) are gone as previous user did not make any backup and spoil it.
Summary of what i can do with the phone now:
Reboot phone into recovery mode or Fastboot. Can link PC and phone show FastBoot USB. Can fastboot to phone for lock / unlock.
Observed feedback from TWRP there is no root folder as suggest to install SuperUSR but not sure is it successful.
HELP, Need advice and help to find and load back factory stock ROM or any version suitable for it.
Think it does not have a proper root loaded too.
Click to expand...
Click to collapse
---------- Post added at 02:55 PM ---------- Previous post was at 02:48 PM ----------
GoRiLaz301 said:
Hi Everyone / Anyone,
Summary of what i can do with the phone now:
Reboot phone into recovery mode or Fastboot. Can link PC and phone show FastBoot USB. Can fastboot to phone for lock / unlock.
Observed feedback from TWRP there is no root folder as suggest to install SuperUSR but not sure is it successful.
HELP, Need advice and help to find and load back factory stock ROM or any version suitable for it.
Think it does not have a proper root loaded too.
Click to expand...
Click to collapse
The Stock Nandroid backup of ur frimware can be found here
To use this u have to put that in the TWRP backups folder which will be a one hectic process to do
Best is to install a custom rom and copy the files to the TWRP folder through MTP......if u want to have Stock ROm
[email protected] said:
Installing a custom ROM will be easy
Wipe all excluding the Internal Storage from TWRP
Just "adb push" the ROM file to the SDCARD once the installation is done
boot into fastboot
flash the kernel from the fastboot........
that should get ur phone booted refer to this tutorial for installing a custom ROM
---------- Post added at 02:55 PM ---------- Previous post was at 02:48 PM ----------
The Stock Nandroid backup of ur frimware can be found here
To use this u have to put that in the TWRP backups folder which will be a one hectic process to do
Best is to install a custom rom and copy the files to the TWRP folder through MTP......if u want to have Stock ROm
Click to expand...
Click to collapse
--------------
in the link regarding "installing a custom ROM" instruction, it seem the phone status permit booting into the phone to "Enable USB Debuggin"
However my case now it will not boot into the normal phone interfaces, it will stuck at "HTC" logo screen and nothing happens afterwards.
I can not only access the Fastboot / Recovery / HBOOT screen of the phone. Any normal reboot will stuck in HTC screen.
also running "adb devices" does not detect the phone and report a serial no. It did run and show opening a port no. 50xx and end successfully.
please advice
i install the Android SDK and followed all instructions carefully but "adb devices" did not return any serial no. of the phone.
in fact the result return blank, nothing is listed.
NOTE the phone can only be connected via USB through recovery mode in Fastboot USB link.
Even when reboot the phone as normal while showing the stucked HTC screen logo, the usb link cannot be established.
please advice.
In CUSTOM Recovery the USB debugging is enabled by default...so that step of booting into phone and enabling the USB debugging doesn't matter...
the device won't get recognized if u had not installed the HTC drivers...
try installing the latest drivers from here
Install this and try
Code:
adb devices
And what are u planning on do install a custom ROM or Flash the Stock Nandroid backup from the thread I provided.....????
I can only help u knowing what u are trying to do.....
GoRiLaz301 said:
--------------
in the link regarding "installing a custom ROM" instruction, it seem the phone status permit booting into the phone to "Enable USB Debuggin"
However my case now it will not boot into the normal phone interfaces, it will stuck at "HTC" logo screen and nothing happens afterwards.
I can not only access the Fastboot / Recovery / HBOOT screen of the phone. Any normal reboot will stuck in HTC screen.
also running "adb devices" does not detect the phone and report a serial no. It did run and show opening a port no. 50xx and end successfully.
please advice
Click to expand...
Click to collapse
GoRiLaz301 said:
i install the Android SDK and followed all instructions carefully but "adb devices" did not return any serial no. of the phone.
in fact the result return blank, nothing is listed.
NOTE the phone can only be connected via USB through recovery mode in Fastboot USB link.
Even when reboot the phone as normal while showing the stucked HTC screen logo, the usb link cannot be established.
please advice.
Click to expand...
Click to collapse
I am trying to get this phone to get to normal functional phone for any region.
Since i got this phone from previous owner, think without any proper ROM backup and got loop in cym logo so am trying to bring this phone "alive" again. It seem not getting anywhere or my procedure is wrong with lack of real ROM in sdcard. At least i managed to figure out somehow get the latest CWM or TWRP and let the phone charge fully. Previously it always show "low battery to flash" message when powered using [ POWER + VOL ] combination.
Not trying to do anything funny to this phone, rather to try my best revive it back to a fully functional phone as the original HTC ONE X+ 64GB International edition. Think this phone is a ASIA WWE edition as it bought locally and with the HTC printed silkscreen, not AT&T.
Sincerely hope u or anyone can help me. I will try to use the "adb device" command again, seem with this way to communicate and push ROM inside the phone, nothing else can get it pass the HTC logo screen now... I am puzzled using Fastboot seem communicating ok with the phone but not adb command.... Keep update....
GoRiLaz301 said:
I am trying to get this phone to get to normal functional phone for any region.
Since i got this phone from previous owner, think without any proper ROM backup and got loop in cym logo so am trying to bring this phone "alive" again. It seem not getting anywhere or my procedure is wrong with lack of real ROM in sdcard. At least i managed to figure out somehow get the latest CWM or TWRP and let the phone charge fully. Previously it always show "low battery to flash" message when powered using [ POWER + VOL ] combination.
Not trying to do anything funny to this phone, rather to try my best revive it back to a fully functional phone as the original HTC ONE X+ 64GB International edition. Think this phone is a ASIA WWE edition as it bought locally and with the HTC printed silkscreen, not AT&T.
Sincerely hope u or anyone can help me. I will try to use the "adb device" command again, seem with this way to communicate and push ROM inside the phone, nothing else can get it pass the HTC logo screen now... I am puzzled using Fastboot seem communicating ok with the phone but not adb command.... Keep update....
Click to expand...
Click to collapse
Fine and clear..
have u tried the drivers I have put in the previous post.........????
Try different USB ports to on ur PC too.......that will work sometimes.......:fingers-crossed:
have install drivers from "installing a custom ROM" page... maybe will try a different USB port after checking and re-install the drivers again.
GoRiLaz301 said:
have install drivers from "installing a custom ROM" page... maybe will try a different USB port after checking and re-install the drivers again.
Click to expand...
Click to collapse
These are the latest HTC drivers can u try this and report whether ur device is recognized in adb recovery mode......
Please try by uninstalling the previous driver u had.........
BTW is it Windows 8.......????????
ok noted but how to uninstall the previous HTC drivers ?
by the way, i also noted that if left the phone to boot after power on, connecting it to PC will be detected but windows cannot install any drivers to it. it will be recognized as HTC MP DEVICE or something similar but with unknown drivers. This normal and ok?
Yesterday feedback in POWER + VOL mode, phone can be recognized as HTC device without USB driver device installation problem.
mine now using Win 7 Home Premium 64-Bit Ed. with latest service packs and updates. Have another PC running Win Vista Biz 32-Bit ed. but not using this one as slower and many software think will affect the phone n PC connection.
Earlier before your help, have found and load TWRP version 2.6.3.0 whereas now the version is 2.4.4.0, will earlier or this 2.4xx version be any difference and affect the connection with adb?
Later will try again the USB drivers and other set up and adb too, not free to do it now...
keep update....
GoRiLaz301 said:
ok noted but how to uninstall the previous HTC drivers ?
by the way, i also noted that if left the phone to boot after power on, connecting it to PC will be detected but windows cannot install any drivers to it.
it will be recognised as HTC MP DEVICE or something similar but will unknown drivers. This normal and ok?
Yesterday feedback in POWER + VOL mode, phone can be recognised as HTC device without USB driver problem.
mine now using Win 7 Home Premium 64-Bit Ed. with latest service packs and updates. Have another PC running Win Vista Biz 32-Bit ed. but not using this one as slower and many software think will affect the phone n PC connection.
Later will try again the USB drivers and other set up and adb too, not free to do it now...
keep update....
Click to expand...
Click to collapse
From the control panel OFC
If u had installed HTC drivers u must be able to see it like this uninstall that...
O Haa haa )
Blunder me ! That's right ! Think bit exhaust after a few sleepless nights figuring out why and hows on this phone....
Now that u mentioned on HTC Driver, before u I have read post on recommended SDK Manager installation.
It is suggested to install SDK Manager with only "Android SDK Platform Tools" + "Google USB Driver" only.
did install these and later use your method to install with "USE AN EXISTING IDE" option of "installer_r22.3-windows.exe" (latest version)
But now did not see the SDK MANAGER program in Control Panel - Programs list... Should have uninstalled.
Think should uninstall the following:
[Windows Mobile Device Center], [Windows Mobile Device Center Driver Update]?
These 2 should be default software of windows or HTC Sync for sync with mobile / usb devices...
Also have installed "Universal Adb Driver" from other post too, think to uninstall this too...
Any recommendation?
GoRiLaz301 said:
Now that u mentioned on HTC Driver, before u I have read post on recommended SDK Manager installation.
It is suggested to install SDK Manager with only "Android SDK Platform Tools" + "Google USB Driver" only.
did install these and later use your method to install with "USE AN EXISTING IDE" option of "installer_r22.3-windows.exe" (latest version)
But now did not see the SDK MANAGER program in Control Panel - Programs list... Should have uninstalled.
Also have installed "Universal Adb Driver" from other post too, think to uninstall this too...
Any recommendation?
Click to expand...
Click to collapse
SDK Manager wont show up on Control panel AFAIK....
it will be a zip file which u have to extract.....
in the extracted folder u will be able to see android-sdk-windows\platform-tools from where u have to open the cmd to execute the abd/fastboot commands
I have the setup of android-sdk-windows and the HTC drivers I pointed to....
It works flawlessly so i recommend to uninstall Universal Adb driver since that isn't helping ur phone recognized anyways.....
Install the Drivers I pointed to and try wether ur phone is getting recognized....:fingers-crossed:
Note : Alternately u can try this installer also which is a small package with the necessary adb and fastboot files......
---------- Post added at 06:43 PM ---------- Previous post was at 06:32 PM ----------
GoRiLaz301 said:
Think should uninstall the following:
[Windows Mobile Device Center], [Windows Mobile Device Center Driver Update]?
These 2 should be default software of windows or HTC Sync for sync with mobile / usb devices...
Also have installed "Universal Adb Driver" from other post too, think to uninstall this too...
Any recommendation?
Click to expand...
Click to collapse
[Windows Mobile Device Center], [Windows Mobile Device Center Driver Update]?
these drivers can be there ...they are or the installation of bluetooth drivers for our phones I guess....
Just uninstall the Universal USB driver .....
If you have HTC Sync I beleive u must be having the HTC driver as I showed on the Screen shot.....
Anyways if u dont see that in the control panel install the one I gave.....U must be fine
ok these r my latest updates:
1) Uninstall HTC SYNC, HTC DRIVER, HTC BMP DRIVER, IPT INSTALLER (Internet Pass-Thru), Universal ADB Driver
2) Install latest Java JRE 7u51 (32 & 64 Bit), Java JDK 7u51 (32 & 64 Bit), detected no older java versions, reboot PC;
3) installer_r22.3-windows.exe (for SDK Manager), created C:\AndroidSDK for SDK Manager and Platform_tools, uninstall default SDK Manager in C:\Program files, Reboot PC;
4) Created Start SDK.bat and run from desktop successfully into directory C:\AndroidSDK\Platform_tools, reboot PC;
5) Install latest HTC Driver using provided link and downloaded with filename HTCDriver_4.10.0.001.msi , reboot PC
Next is to test the USB connection to phone, Q?
1) My phone cannot power on to normal JellyBean OS (as think no ROM);
2) Can only ON to POWER + VOL-DWN mode, to HBOOT > FastBoot, is this right way to test as given in the instruction of http://http://forum.xda-developers.com/showthread.php?t=2213910
2A) If need to let PC detect a working phone and install drivers, have another model [HTC ONE X], can connect USB to this working phone first to test drivers / USB?
Pause here before proceed as concern might spoil the flow of progress if taken wrong step before testing ADB command, please advice.
GoRiLaz301 said:
ok these r my latest updates:
1) Uninstall HTC SYNC, HTC DRIVER, HTC BMP DRIVER, IPT INSTALLER (Internet Pass-Thru), Universal ADB Driver
2) Install latest Java JRE 7u51 (32 & 64 Bit), Java JDK 7u51 (32 & 64 Bit), detected no older java versions, reboot PC;
3) installer_r22.3-windows.exe (for SDK Manager), created C:\AndroidSDK for SDK Manager and Platform_tools, uninstall default SDK Manager in C:\Program files, Reboot PC;
4) Created Start SDK.bat and run from desktop successfully into directory C:\AndroidSDK\Platform_tools, reboot PC;
5) Install latest HTC Driver using provided link and downloaded with filename HTCDriver_4.10.0.001.msi , reboot PC
Next is to test the USB connection to phone, Q?
1) My phone cannot power on to normal JellyBean OS (as think no ROM);
2) Can only ON to POWER + VOL-DWN mode, to HBOOT > FastBoot, is this right way to test as given in the instruction of http://http://forum.xda-developers.com/showthread.php?t=2213910
2A) If need to let PC detect a working phone and install drivers, have another model [HTC ONE X], can connect USB to this working phone first to test drivers / USB?
Pause here before proceed as concern might spoil the flow of progress if taken wrong step before testing ADB command, please advice.
Click to expand...
Click to collapse
FIne....
From bootloader boot into recovery.....
try whether u r device is recognized.......
If recognized PROFIT for the hectic work done......
then u can push a rom to ur SDCARD using adb push command......
then install as usual from the recovery........
ok, this is what the usb detected after boot into Recovery (TWRP screen) and captured a screen shot,
is it ok?
JACK POT !!!!
ADB DEVICES listed my device s/n. in recovery mode.!
GoRiLaz301 said:
ok, this is what the usb detected after boot into Recovery (TWRP screen) and captured a screen shot,
is it ok?
Click to expand...
Click to collapse
Absolutely Fine........
What I meant in While in TWRP connect ur phone to PC
double click on your Start SDK shortcut and in the CMD type
Code:
adb devices
Ur result must be like this
YES, it did show the device listed with serial no.
Now i into the [Recovery Installation] section and at the BACKUP part (pt. 15), now should i also tick Recovery + Cache to perform full backup of actual ROM? (this seem not applicable to me, is it?)
I’ve been lurking on these forums for a while and I have decided that I’m willing to take the risk to unlock my Thor’s potential. I have made sure to read through advised reading materials, and searching through other posts before posting. (I tried figuring out how to quote multiple posts to make this thread easier to navigate but I couldn't, sorry)
Device: Kindle Fire HDX 7” 3rd Generation running Fire OS 4.5.5.3
I will be using a Windows 10 Home machine to do this.
Purpose: Allow for the device to work well in Google’s ecosystem so I can have a useful device for medical school.
I am currently trying to learn the steps outlined here, but I have some concerns:
Does it matter whether or not I factory reset my device before I begin?
Will my computer’s OS cause any issues? According to this, there might be some driver issues? Should I download the “Motorola Device manager”?
Where is the “aboot_vuln.mbn” file? Do I obtain it once I follow the steps in order?
I want to use “Minimal ADB and Fastboot” instead of the attached “15 seconds ADB Installer v1.4.3” because the later has not been updated in a while and the former was updated this month. According to the install instructions for the former, I need to have my device already plugged in and the “kindle fire USB driver” already installed. Will this affect step 4 of the procedure or anything else?
On step 5, am I correct in my assumption that changing the driver will be a simple few click process?
On step 6, do I follow the directions as they are quoted, or the ones on the original forum? If the later, does “change to the directory with the extracted dd.exe” mean to type the directory or something else? Also, a poster here stated that he got error message on the second 2 commands instead of the first, is the concerning at all? Should I take any precautionary measures?
Once step 9 is completed, can the kindle run as normal if I don’t flash anything? And what does it mean “get into the TWRP”? I’ll simply be in the recovery menu on the kindle? How do I flash my chosen ROM using TWRP?
What ROM do you recommend for my needs? And could you provide me a link to the correct download/discussion board? I would prefer a ROM running at least Nougat that has long-term support planned. I read that “Fire Nexus ROM” is pretty basic, so I don’t think I want it. As of now, I’m looking at CM/Lineage 14.1, but I don’t know what ROM would work on my device from the website. AospExtended seems like a good option but apparently, there are wi-fi issues which are a deal-breaker.
Thank you so much for reading through this. Hopefully all my research and proves to be useful for anyone trying to help. If I’m able to get this working cleanly, I would be willing to make a cleaned up guide for this version and device to better aid future people.
hwwof said:
I’ve been lurking on these forums for a while and I have decided that I’m willing to take the risk to unlock my Thor’s potential. I have made sure to read through advised reading materials, and searching through other posts before posting. (I tried figuring out how to quote multiple posts to make this thread easier to navigate but I couldn't, sorry)
Device: Kindle Fire HDX 7” 3rd Generation running Fire OS 4.5.5.3
I will be using a Windows 10 Home machine to do this.
Purpose: Allow for the device to work well in Google’s ecosystem so I can have a useful device for medical school.
Click to expand...
Click to collapse
Hello @hwwof -
You have done your homework (thank you!) and presented reasonable questions. I'm going to answer the first five 'in-line' below. Responses will be brief to keep the thread serviceable for those accessing XDA content on small screens; don't read anything into that. Bounce back on any items that need further elaboration.
hwwof said:
I am currently trying to learn the steps outlined here, but I have some concerns:
Does it matter whether or not I factory reset my device before I begin?
Click to expand...
Click to collapse
No; however, it would be better if you did NOT reset the device.
hwwof said:
Will my computer’s OS cause any issues? According to this, there might be some driver issues? Should I download the “Motorola Device manager”?
Click to expand...
Click to collapse
Nope. Drivers installed via the Motorola Device manager are properly signed which mitigates any potential issues on 64-bit Win 10 builds (yet another reason to use the Moto drivers vs others that have been posted)
hwwof said:
Where is the “aboot_vuln.mbn” file? Do I obtain it once I follow the steps in order?
Click to expand...
Click to collapse
It's contained within aboot-13-thor.zip; just named differently.
hwwof said:
I want to use “Minimal ADB and Fastboot” instead of the attached “15 seconds ADB Installer v1.4.3” because the later has not been updated in a while and the former was updated this month. According to the install instructions for the former, I need to have my device already plugged in and the “kindle fire USB driver” already installed. Will this affect step 4 of the procedure or anything else?
Click to expand...
Click to collapse
Good idea. Your device does not need to be tethered while installing Minimal ADB and Fastboot. Take note of where the package is installed (typically "C:\Program Files (x86)\Minimal ADB and Fastboot") and practice opening a command window focused in that folder. To make life simpler you can direct the installer to place the files in "c:\work" which is a lot easier to type.
hwwof said:
On step 5, am I correct in my assumption that changing the driver will be a simple few click process?
Click to expand...
Click to collapse
Yes - but here's were it gets interesting and a bit frustrating. Even with the Moto drivers Windows can be very fussy communicating with HDX devices. To complicate matters there are two modes to deal with: ADB and Fastboot. You'll learn which is which as time goes on and will likely have to switch Windows drivers for each mode. Sometimes a reboot is needed to get everyone talking. Note there is no danger involved simply tethering your device and issuing basic queries.
To test basic ADB communications:
- execute step #2 (only) from the linked procedure
- open a Windows command prompt as outlined above
- boot HDX into FireOS and move past the screen lock
- tether device to windows; take note of any noises and/or confirmation messages
- in the window command prompt issue the command "adb devices" and press Enter. What happens?
Post back results and we'll go from there.
Thank you @Davey126 . I appreciate you taking the time to help me out. Answers to the other questions would be very appreciated as well!
Here are my results that you requested:
The kindle beeped, and the internal storage popped up on my computer. I ran the minimal adb and fastboot program, and got this output:
Code:
C:\adb>adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
D0FBA0A0351401GB unauthorized
C:\adb>
And on the kindle, I got a “Allow USV debugging” popup on the kindle and it showed my computer’s RSA Fingerprint. I then pressed allow. I took note of the fingerprint just in case. I then tried ejecting my device but it wouldn’t let me because a program was still using it. I ran “adb devices” again and got this output:
Code:
C:\adb>adb devices
List of devices attached
D0FBA0A0351401GB device
C:\adb>
hwwof said:
Thank you @Davey126 . I appreciate you taking the time to help me out. Answers to the other questions would be very appreciated as well!
Click to expand...
Click to collapse
Second response is positive. Next issue the following command: 'adb reboot bootloader'. This will place your device in fastboot mode. If you are very lucky a 'Ready' prompt will appear on the device below the word 'fastboot'. Most likely you will need to head to Windows Device Manager, identify which entry is associated with the tethered HDX and then change the device driver to 'Moto Composite' or something similar (might not have the wording exactly right). Once you get a 'Ready' prompt issue the following command: 'fastboot devices'. If you get a response similar to 'adb devices' then you are good to go.
Hints/tips:
- to help determine which entry(s) are associated with your HDX tether/untether your device while Windows Device Manager is open
- right click an entry to change the device driver; navigate 'Browse my computer ...' -> 'Let me pick ...'; do not choose any of the automated options
- if you can't get a Ready prompt and/or an response to 'fastboot devices' reboot both devices and try again
- if still no joy change USB ports and cables; the latter are especially problematic (people never believe that until trying 1821 other things - ugh!)
Report back and we'll go from there. I know you prefer the rest of your questions answered up front. Experience suggests an incremental approach is more productive - for you, me and future readers.
Davey126 said:
Second response is positive. Next issue the following command: 'adb reboot bootloader'. This will place your device in fastboot mode. If you are very lucky a 'Ready' prompt will appear on the device below the word 'fastboot'. Most likely you will need to head to Windows Device Manager, identify which entry is associated with the tethered HDX and then change the device driver to 'Moto Composite' or something similar (might not have the wording exactly right). Once you get a 'Ready' prompt issue the following command: 'fastboot devices'. If you get a response similar to 'adb devices' then you are good to go.
Hints/tips:
- to help determine which entry(s) are associated with your HDX tether/untether your device while Windows Device Manager is open
- right click an entry to change the device driver; navigate 'Browse my computer ...' -> 'Let me pick ...'; do not choose any of the automated options
- if you can't get a Ready prompt and/or an response to 'fastboot devices' reboot both devices and try again
- if still no joy change USB ports and cables; the latter are especially problematic (people never believe that until trying 1821 other things - ugh!)
Report back and we'll go from there. I know you prefer the rest of your questions answered up front. Experience suggests an incremental approach is more productive - for you, me and future readers.
Click to expand...
Click to collapse
Thank you! Now it says "ready" but I'm concerned about how to unplug it without messing anything up. here's the output:
Code:
Microsoft Windows [Version 10.0.16299.248]
(c) 2017 Microsoft Corporation. All rights reserved.
C:\adb>adb reboot bootloader
C:\adb>fastboot devices
D0FBA0A0351401GB fastboot
C:\adb>
You are correct that I would prefer having all the answers upfront, but it's only so I can then question the answers to get a better understanding before messing with the device. A quick reply would be appreciated!
hwwof said:
Thank you! Now it says "ready" but I'm concerned about how to unplug it without messing anything up. here's the output:
{content removed}
You are correct that I would prefer having all the answers upfront, but it's only so I can then question the answers to get a better understanding before messing with the device. A quick reply would be appreciated!
Click to expand...
Click to collapse
Great!! The purpose of this exercise was to validate connectivity in two different modes and, if needed, provide a safe 'test' environment for remediation. No worries about breaking the tether if there is no active data transfer taking place. Simply unplug and then long press <power> until the device shuts down.
In response to your other questions:
Q: On step 6, do I follow the directions as they are quoted, or the ones on the original forum? If the later, does “change to the directory with the extracted dd.exe” mean to type the directory or something else? Also, a poster here stated that he got error message on the second 2 commands instead of the first, is the concerning at all? Should I take any precautionary measures?
A: Follow the steps as quoted
Q: Once step 9 is completed, can the kindle run as normal if I don’t flash anything? And what does it mean “get into the TWRP”? I’ll simply be in the recovery menu on the kindle? How do I flash my chosen ROM using TWRP?
A1: You should assume all content on your device will be erased following completion of Step #9 (although it will likely remain intact)
A2: The two files you will be 'flashing' with the dd command should be located in the same folder as "Minimal ADB and Fastboot"
A3: Deal with that later (flashing ROM)
Q: ROMs:
A: All of the Nougat based custom ROMs for HDX are stable and feature complete. Nuances are subtle and probably not worth worrying about now; you can always change later. My personal preference is AEX (AospExtended). That said, Lineage 14.1 and Slim 7 are both excellent alternatives.
Davey126 said:
Great!! The purpose of this exercise was to validate connectivity in two different modes and, if needed, provide a safe 'test' environment for remediation. No worries about breaking the tether if there is no active data transfer taking place. Simply unplug and then long press <power> until the device shuts down.
In response to your other questions:
Q: On step 6, do I follow the directions as they are quoted, or the ones on the original forum? If the later, does “change to the directory with the extracted dd.exe” mean to type the directory or something else? Also, a poster here stated that he got error message on the second 2 commands instead of the first, is the concerning at all? Should I take any precautionary measures?
A: Follow the steps as quoted
Q: Once step 9 is completed, can the kindle run as normal if I don’t flash anything? And what does it mean “get into the TWRP”? I’ll simply be in the recovery menu on the kindle? How do I flash my chosen ROM using TWRP?
A1: You should assume all content on your device will be erased following completion of Step #9 (although it will likely remain intact)
A2: The two files you will be 'flashing' with the dd command should be located in the same folder as "Minimal ADB and Fastboot"
A3: Deal with that later (flashing ROM)
Q: ROMs:
A: All of the Nougat based custom ROMs for HDX are stable and feature complete. Nuances are subtle and probably not worth worrying about now; you can always change later. My personal preference is AEX (AospExtended). That said, Lineage 14.1 and Slim 7 are both excellent alternatives.
Click to expand...
Click to collapse
So I completed the instructions, booted to TWRP, turned it off, booted up, did the unlock batch, but I didn't get "unlock code is correct". I got a lot of green lines "getvar slot-count...OK getvar:slot-suffixes...OK getvar:has-slot:unlock...OK getvarartition-type:unlock...OK getvar:max-download-size...[[0x20000000 ]] download:00000000..." Here's the cmd when I try running unlock.bat https://gyazo.com/a041dc49c786f9846d706c049eacbbf3
Did I mess something up or am I unlocked? I'm not sure what to do from here. I was still able to get back to TWRP. It's telling me to swipe to allow modifications or to keep read only. Where do I proceed from here? I'm reading in some places to wipe before installing, and a lot of other conflicting information. I downlaoded the AEX november build and would like to flash it. Do I have any need for rooting or SuperSU?
Again, Thank you so much for all your help
*deleted*
*deleted*
hwwof said:
So I completed the instructions, booted to TWRP, turned it off, booted up, did the unlock batch, but I didn't get "unlock code is correct". I got a lot of green lines "getvar slot-count...OK getvar:slot-suffixes...OK getvar:has-slot:unlock...OK getvarartition-type:unlock...OK getvar:max-download-size...[[0x20000000 ]] download:00000000..." Here's the cmd when I try running unlock.bat https://gyazo.com/a041dc49c786f9846d706c049eacbbf3
Did I mess something up or am I unlocked? I'm not sure what to do from here. I was still able to get back to TWRP. It's telling me to swipe to allow modifications or to keep read only. Where do I proceed from here? I'm reading in some places to wipe before installing, and a lot of other conflicting information. I downlaoded the AEX november build and would like to flash it. Do I have any need for rooting or SuperSU?
Again, Thank you so much for all your help
Click to expand...
Click to collapse
Device is NOT unlocked. Tied up for the next hour or two; will respond then. Do not wipe or attempt to flash anything. Sorry for wait ...
Davey126 said:
Device is NOT unlocked. Tied up for the next hour or two; will respond then. Do not wipe or attempt to flash anything. Sorry for wait ...
Click to expand...
Click to collapse
Thank you for being on top of this! I'm glad I was patient and didn't immediately try flashing anything. I'll try to wait up! I apologize if I fall asleep.
hwwof said:
Thank you for being on top of this! I'm glad I was patient and didn't immediately try flashing anything. I'll try to wait up! I apologize if I fall asleep.
Click to expand...
Click to collapse
Quick activity while you wait:
- boot into TWRP (power down; press <power>+<vol-up> for ~3 sec then release)
- swipe to allow modifications
- tap the backup option, select all partitions except cache, swipe to execute
- when complete tether device; should connect in adb mode
- from look for a new device/drive in Windows File Explorer
- click <device ID> -> Internal Storage; should see a folder named TWRP
- drag or right-click folder to a storage location on your Win 10 machine
- congrats! You have just made a backup of your device -and- placed a reserve copy on your Windows machine
Comment: prior to backing up you had completed the most risky tasks (stuff that could have yielded a soft/hard brick). It's all downhill from here. Will post more info on unlocking and installing a new ROM in a bit; real-life is calling . Fully understand if you need to sleep; post will be waiting in the morning. Penning this from Northeast USA; timezone UTC-5.
Davey126 said:
Quick activity while you wait:
- boot into TWRP (power down; press <power>+<vol-up> for ~3 sec then release)
- swipe to allow modifications
- tap the backup option, select all partitions except cache, swipe to execute
- when complete tether device; should connect in adb mode
- from look for a new device/drive in Windows File Explorer
- click <device ID> -> Internal Storage; should see a folder named TWRP
- drag or right-click folder to a storage location on your Win 10 machine
- congrats! You have just made a backup of your device -and- placed a reserve copy on your Windows machine
Comment: prior to backing up you had completed the most risky tasks (stuff that could have yielded a soft/hard brick). It's all downhill from here. Will post more info on unlocking and installing a new ROM in a bit; real-life is calling . Fully understand if you need to sleep; post will be waiting in the morning. Penning this from Northeast USA; timezone UTC-5.
Click to expand...
Click to collapse
I appreciate you so much! And I completely understand. I hope everything you're working on gets resolved!
I have backed it up as you suggested! Since the back-up is also on the internal drive, it will be deleted later, correct? It's 5gbs out of the already small storage space.
hwwof said:
I appreciate you so much! And I completely understand. I hope everything you're working on gets resolved!
I have backed it up as you suggested! Since the back-up is also on the internal drive, it will be deleted later, correct? It's 5gbs out of the already small storage space.
Click to expand...
Click to collapse
With the 5GB TWRP backup folder safely copied off-device you can delete the local copy at any time...although there is no immediate reason to do so.
Next step is to unlock the bootloader:
- verify 'get_code.bat' & 'unlock.bat' reside in the same folder as adb.exe and fastboot.exe
- look around to see if you have a file called 'unlock.code' from a previous run of 'get_code.bat'; if so place it in the same folder
- tether device and boot into fastboot (easiest way: boot into TWRP and then use reboot menu to boot the bootloader) [<--what an awkward sentence!]
- enter 'fastboot devices' to validate communication between host and device
- execute unlock.bat; if you get a green 'OK' the bootloader is unlocked!
- if not boot into FireOS (get past unlock screen), tether, verify adb communication is working and then run 'get_code.bat' to (re)create the 'unlock.code' file
- repeat steps 2-4 (above)
If that doesn't work and/or you are unable to boot into TWRP then a bit of extra work will be needed to generate a valid unlock code. Brief outline:
- download legacy Fire Nexus ROM from here (it does NOT require an unlocked bootloader)
- tether device and into TWRP
- from Windows copy downloaded ROM to a folder on the device (suggest creating a new folder with your initials as the name)
- from the TWRP main menu tap Wipe then swipe to perform a 'factory reset'
- from the TWRP main menu tap Install
- navigate to the folder where you stored the downloaded ROM
- select the ROM zip and then click to install
- when complete allow the device to restart; after a 3-5 min it should boot into Fire Nexus; skip the Google config (not needed)
- enable developer options and adb bridge
- tether device and verify adb connectivity
- run 'get_code.bat' to generate a fresh unlock.code file
I will be traveling much of Sunday with irregular network access. I'll try to respond to an questions/problems as time permits. Apologies in advance for any delays.
Davey126 said:
With the 5GB TWRP backup folder safely copied off-device you can delete the local copy at any time...although there is no immediate reason to do so.
Next step is to unlock the bootloader:
- verify 'get_code.bat' & 'unlock.bat' reside in the same folder as adb.exe and fastboot.exe
- look around to see if you have a file called 'unlock.code' from a previous run of 'get_code.bat'; if so place it in the same folder
- tether device and boot into fastboot (easiest way: boot into TWRP and then use reboot menu to boot the bootloader) [<--what an awkward sentence!]
- enter 'fastboot devices' to validate communication between host and device
- execute unlock.bat; if you get a green 'OK' the bootloader is unlocked!
- if not boot into FireOS (get past unlock screen), tether, verify adb communication is working and then run 'get_code.bat' to (re)create the 'unlock.code' file
- repeat steps 2-4 (above)
If that doesn't work and/or you are unable to boot into TWRP then a bit of extra work will be needed to generate a valid unlock code. Brief outline:
- download legacy Fire Nexus ROM from here (it does NOT require an unlocked bootloader)
- tether device and into TWRP
- from Windows copy downloaded ROM to a folder on the device (suggest creating a new folder with your initials as the name)
- from the TWRP main menu tap Wipe then swipe to perform a 'factory reset'
- from the TWRP main menu tap Install
- navigate to the folder where you stored the downloaded ROM
- select the ROM zip and then click to install
- when complete allow the device to restart; after a 3-5 min it should boot into Fire Nexus; skip the Google config (not needed)
- enable developer options and adb bridge
- tether device and verify adb connectivity
- run 'get_code.bat' to generate a fresh unlock.code file
I will be traveling much of Sunday with irregular network access. I'll try to respond to an questions/problems as time permits. Apologies in advance for any delays.
Click to expand...
Click to collapse
Welp, device won't boot into FireOS. It boots straight to Fastboot. I tried Installing nexus ROM but I got "can't install this package over newer build updater process ended with error:7".
hwwof said:
Welp, device won't boot into FireOS. It boots straight to Fastboot. I tried Installing nexus ROM but I got "can't install this package over newer build updater process ended with error:7".
Click to expand...
Click to collapse
Error 7 is pretty generic and can be due to a conflict between install package and TWRP or an issue with the system partition. It's a solvable issue without too much work. They the following in the order listed.
1) In TWRP tap wipe -> advanced. Tick system, data, dalvik and cache; leave internal storage unticked. Tap the appropriate button to execute. Return to main menu and reboot back into recovery. Then try to install the Nexus ROM.
2) Download an older build of TWRP from here and transfer to adb/fastboot folder on Windows. Boot device into fastboot mode and issue the following command to install:
sudo fastboot -i 0x1949 flash recovery <recovery-image>
Will check back in 5-6 hours on progress.
Davey126 said:
Error 7 is pretty generic and can be due to a conflict between install package and TWRP or an issue with the system partition. It's a solvable issue without too much work. They the following in the order listed.
1) In TWRP tap wipe -> advanced. Tick system, data, dalvik and cache; leave internal storage unticked. Tap the appropriate button to execute. Return to main menu and reboot back into recovery. Then try to install the Nexus ROM.
2) Download an older build of TWRP from here and transfer to adb/fastboot folder on Windows. Boot device into fastboot mode and issue the following command to install:
sudo fastboot -i 0x1949 flash recovery <recovery-image>
Will check back in 5-6 hours on progress.
Click to expand...
Click to collapse
First one didn't work, second one put this out:
C:\adb>sudo fastboot -i 0x1949 flash recovery signed-thor-twrp-2870.img
'sudo' is not recognized as an internal or external command,
operable program or batch file.
hwwof said:
First one didn't work, second one put this out:
C:\adb>sudo fastboot -i 0x1949 flash recovery signed-thor-twrp-2870.img
'sudo' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
Drop the sudo prefix ...
Davey126 said:
Drop the sudo prefix ...
Click to expand...
Click to collapse
"
C:\adb>fastboot devices
D0FBA0A0351401GB fastboot
C:\adb>fastboot -i 0x1949 flash recovery signed-thor-twrp-2870.img
target reported max download size of 536870912 bytes
sending 'recovery' (9220 KB)...
OKAY [ 0.361s]
writing 'recovery'...
FAILED (remote: flashing not allowed for locked hw)
finished. total time: 0.424s
C:\adb>
"
hwwof said:
"
C:\adb>fastboot devices
D0FBA0A0351401GB fastboot
C:\adb>fastboot -i 0x1949 flash recovery signed-thor-twrp-2870.img
target reported max download size of 536870912 bytes
sending 'recovery' (9220 KB)...
OKAY [ 0.361s]
writing 'recovery'...
FAILED (remote: flashing not allowed for locked hw)
finished. total time: 0.424s
C:\adb>
"
Click to expand...
Click to collapse
This suggest the vulnerable bootloader was not properly installed. You will probably need to repeat the installation procedure from the point of placing the device in 'bulk' mode. Be sure to pay attention to file indexes and file identifiers that follow "if=".
@draxie - would you agree with this assessment? Poster is following this guide and using the files attached to that post.