Not working got to made another one when i be back home.
I have a problem with the computer at work all my zip file are no more working.
I don't know why.
I will make another zip soon
Re: [delete this thread]Flashable zip of Bootloader 4.18 for grouper & tilapia
Yeah works well!
Edit: thought it worked. Stayed on 4.13
Sent from my Nexus 7 using xda premium
[email protected]_OC said:
Not working got to made another one when i be back home.
I have a problem with the computer at work all my zip file are no more working.
I don't know why.
I will make another zip soon
Click to expand...
Click to collapse
Thanks man!
Gave up on fastboot. Dunno why cant get it running!
I tried using fastboot but cant get it to work.
1) Create a folder called fastboot, copy the 4 files + bootloader img into it, and move the folder into C drive.
2) run cmd
3) enter cd C:\fastboot\
4) adb devices. check correct.
5) adb reboot-bootloader
6) fastboot devices. check correct.
7) fastboot flash bootloader bootloader-grouper-4.18.img
8) nth happened.
what went wrong?
o0boiboi0o said:
Thanks man!
Gave up on fastboot. Dunno why cant get it running!
I tried using fastboot but cant get it to work.
1) Create a folder called fastboot, copy the 4 files + bootloader img into it, and move the folder into C drive.
2) run cmd
3) enter cd C:\fastboot\
4) adb devices. check correct.
5) adb reboot-bootloader
6) fastboot devices. check correct.
7) fastboot flash bootloader bootloader-grouper-4.18.img
8) nth happened.
what went wrong?
Click to expand...
Click to collapse
I think you forgot unlock bootloader typing
fastboot oem unlock
Enviado de meu Nexus 7 usando o Tapatalk 2
eric-filth said:
I think you forgot unlock bootloader typing
fastboot oem unlock
Enviado de meu Nexus 7 usando o Tapatalk 2
Click to expand...
Click to collapse
oh! coz i saw there stated unlocked.
is it a must to type that?
o0boiboi0o said:
oh! coz i saw there stated unlocked.
is it a must to type that?
Click to expand...
Click to collapse
No, if are unlocked you dont need
Enviado de meu Nexus 7 usando o Tapatalk 2
o0boiboi0o said:
Thanks man!
Gave up on fastboot. Dunno why cant get it running!
I tried using fastboot but cant get it to work.
1) Create a folder called fastboot, copy the 4 files + bootloader img into it, and move the folder into C drive.
2) run cmd
3) enter cd C:\fastboot\
4) adb devices. check correct.
5) adb reboot-bootloader
6) fastboot devices. check correct.
7) fastboot flash bootloader bootloader-grouper-4.18.img
8) nth happened.
what went wrong?
Click to expand...
Click to collapse
This worked for me fine. How adb devices is working for you? I think when you are in fastboot adb doesnt work.......Maybe i am wrong.
nickporwal said:
This worked for me fine. How adb devices is working for you? I think when you are in fastboot adb doesnt work.......Maybe i am wrong.
Click to expand...
Click to collapse
I think you hit sth!
when tablet is on, adb devices give me return (serial number+device). But, when i adb reboot-bootloader, adb devices give me nth, instead fastboot devices give me return.
When you type in adb devices it returns your device but you'll notice that it says offline next to it.
Therefore you can't send any adb commands to it.
It's a new security measure apparently, the solutions can be found in the forums.
Sent from my Incredible S using xda app-developers app
where are the zips
o0boiboi0o said:
Thanks man!
Gave up on fastboot. Dunno why cant get it running!
I tried using fastboot but cant get it to work.
1) Create a folder called fastboot, copy the 4 files + bootloader img into it, and move the folder into C drive.
2) run cmd
3) enter cd C:\fastboot\
4) adb devices. check correct.
5) adb reboot-bootloader
6) fastboot devices. check correct.
7) fastboot flash bootloader bootloader-grouper-4.18.img
8) nth happened.
what went wrong?
Click to expand...
Click to collapse
You must make sure to put the files you are flashing in the same folder that fastboot is located, and also to cd to that folder in command prompt.
What error were you getting exactly?
[email protected]_OC said:
Not working got to made another one when i be back home.
I have a problem with the computer at work all my zip file are no more working.
I don't know why.
I will make another zip soon
Click to expand...
Click to collapse
I too tried to create a flashable zip from the OTA, but it doesn't stick. I had to use fastboot
Sent from my Nexus 7
o0boiboi0o said:
I think you hit sth!
when tablet is on, adb devices give me return (serial number+device). But, when i adb reboot-bootloader, adb devices give me nth, instead fastboot devices give me return.
Click to expand...
Click to collapse
I am experiencing the same problem. Guess I'll have to wait for the zip version...
I used this guide for the adb: http://forum.xda-developers.com/showthread.php?t=1830108
Adinaky said:
I am experiencing the same problem. Guess I'll have to wait for the zip version...
I used this guide for the adb: http://forum.xda-developers.com/showthread.php?t=1830108
Click to expand...
Click to collapse
I am in the same boat as well. I am having weird adb issues that won't allow me to fastboot either. I am gonna reinstall SDK and see if i can adb working.
Sent from my Nexus 7 using xda premium
Tone_Capone said:
You must make sure to put the files you are flashing in the same folder that fastboot is located, and also to cd to that folder in command prompt.
What error were you getting exactly?
Click to expand...
Click to collapse
Dont think there is any error. It kept stating waiting for device but nth happened on my device side. Seems like the command get thru but nth is done.
Oo more and more ppl are having the same prob as me! :victory: Lol
Lets wait for TS's flashable file!
http://forum.xda-developers.com/showpost.php?p=37989110&postcount=1650
waiting for a linux version, i hate windows
If you don't have a working adb, you should try this guide: http://www.teamandroid.com/2012/07/30/how-to-set-up-adb-fastboot-with-android-sdk/ , it's the only one that worked for me.
Sent from my Nexus 7 using xda premium
weird.
I tried fastboot again. Ok, running smoothly at first, but in the end, i got this error:
writing 'bootloader'...
FAILED <status read failed <too many links>>
So i closed the cmd (bcoz when i tried fastboot devices, it shows ????? devices. Then when i forced closed my device and reboot into bootloader, it showed 4.18 as the bootloader version but under SIGNING, it is not defined yet.
Is this correct?
o0boiboi0o said:
weird.
I tried fastboot again. Ok, running smoothly at first, but in the end, i got this error:
writing 'bootloader'...
FAILED <status read failed <too many links>>
So i closed the cmd (bcoz when i tried fastboot devices, it shows ????? devices. Then when i forced closed my device and reboot into bootloader, it showed 4.18 as the bootloader version but under SIGNING, it is not defined yet.
Is this correct?
Click to expand...
Click to collapse
This happened to me when my adb was not working properly, it showed 4.18, but I fixed the adb and installed the bootloader again, just to be sure.
Sent from my Nexus 7 using xda premium
Anyone an idea, why flashing the bootloader does not work with the zip files?
I am somewhere in nowhere and can not fastboot, have only my Nexus 3G with me. Its on 4.2.2 but bootloader still 4.13. Used this ROM:
[ROM][Factory Image][4.2.2] Nakasig -::- Odex, Deodex, Rooted -::- teshxx (02/14/13)
to update. Worked apart of bootloader and radio.
Related
I stupidly showed my teenage son how to use ROM Manager and CWM on my phone.
He has now completely deleted (and I feel formatted) ALL Data etc on the phone.
So, as I cannot use any software on my MAC to transfer ROMs to the phone CAN Someone please advise how to get a ROM on the phone?
I can still access CWM Recovery. I have Android SDK installed, including Eclipse.
Please remember I am using a MAC, when you helpfully pass on ideas or solutions
Go to adb and fastboot folder, boot into recovery and use the command from terminal:
Code:
adb push name-of-rom.zip /sdcard/
.
Remember to put the rom into adb/fastboot folder
Hey, thank you.
I will try that soon
Hmm, trouble getting this done
I keep getting "command not found" message. Everything is in the folder.
I have done a CD to the folder etc
aussie_boi said:
Hmm, trouble getting this done
I keep getting "command not found" message. Everything is in the folder.
I have done a CD to the folder etc
Click to expand...
Click to collapse
Are you doing it while in recovery?
Try 'adb devices' and see if it sees your device
Type exactly the command you're typing to try push your ROM so we can see if you've made a slight mistake...
Sent from my HTC One using xda premium
redbull123 said:
Are you doing it while in recovery?
Try 'adb devices' and see if it sees your device
Type exactly the command you're typing to try push your ROM so we can see if you've made a slight mistake...
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Okies, I have tried adb devices and it comes back with no device listing. I was in CWM Recovery mode.
This is what I typed - /Users/Greg/Downloads/Android/sdk/platform-tools/adb push AR10.1.zip /sdcard/ for the push, and
I typed this for the adb devices command - /Users/Greg/Downloads/Android/sdk/platform-tools/adb devices
aussie_boi said:
Okies, I have tried adb devices and it comes back with no device listing. I was in CWM Recovery mode.
Click to expand...
Click to collapse
What does your adb folder have in it? I use a Mac and all I have is 2 files:
adb
fastboot
Try going into fastboot it should say FASTBOOT USB then try 'fastboot devices'
Also, try a different usb port...
Sent from my HTC One using xda premium
redbull123 said:
What does your adb folder have in it? I use a Mac and all I have is 2 files:
adb
fastboot
Try going into fastboot it should say FASTBOOT USB then try 'fastboot devices'
Also, try a different usb port...
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
This is the response this time - homelatform-tools Greg$ /Users/Greg/Downloads/Android/sdk/platform-tools/fastboot devices
HT34LW912007 fastboot
aussie_boi said:
This is the response this time - homelatform-tools Greg$ /Users/Greg/Downloads/Android/sdk/platform-tools/fastboot devices
HT34LW912007fastboot
Click to expand...
Click to collapse
Now try recovery again
adb devices
Sent from my HTC One using xda premium
redbull123 said:
Now try recovery again
adb devices
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
It's not playing ball at all - this is the response after "adb devices"
home:Android Greg$ /Users/Greg/Downloads/Android/adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
home:Android Greg$
aussie_boi said:
It's not playing ball at all - this is the response after "adb devices"
home:Android Greg$ /Users/Greg/Downloads/Android/adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
home:Android Greg$
Click to expand...
Click to collapse
Try finding the two files I said earlier in your sdk and make a new folder just with those two files and your ROM.zip and try opening your terminal window from that new folder.
Sent from my HTC One using xda premium
redbull123 said:
Try finding the two files I said earlier in your sdk and make a new folder just with those two files and your ROM.zip and try opening your terminal window from that new folder.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Okies, I have already done that. I copied the "adb and fastboot" files from the sdk and added the "ROM.zip" file there also.
In recovery, I still get no devices listed with "adb devices"
I have opened a terminal window from within the case folder ... etc etc
I'm in the same spot and I don't have acess to a windows computer, tried doing this for almost 3 hours last night
Sent from my HTC VLE_U using xda premium
rizzxx7 said:
I'm in the same spot and I don't have acess to a windows computer, tried doing this for almost 3 hours last night
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
Its much easier on a Mac. Have you downloaded the adb and fastboot files? Once you have those, navigate to their folder using cd in Terminal, add the rom zip and then use
Code:
./adb push rom.zip /data/media/
I've seen this happen on my friend's HTC One a week ago. I was able to fix it by using the ALL IN ONE TOOL that was posted in this forum. I SIDELOADED a ROM, but only AFTER flashing the stock Boot.img and kernel. I dunno if this helps, but it certainly fixed the problem for me.... oh and also, I did this on a Windows 7 lappy and I'm not familiar with Macs.
MacHackz said:
Its much easier on a Mac. Have you downloaded the adb and fastboot files? Once you have those, navigate to their folder using cd in Terminal, add the rom zip and then use
Code:
./adb push rom.zip /data/media/
Click to expand...
Click to collapse
I will try this once again when I get home, I've got a nandroid file from a stock tmobile Rom that I will try to install
Sent from my HTC VLE_U using xda premium
MacHackz said:
Its much easier on a Mac. Have you downloaded the adb and fastboot files? Once you have those, navigate to their folder using cd in Terminal, add the rom zip and then use
Code:
./adb push rom.zip /data/media/
Click to expand...
Click to collapse
When I do this, I still get the error: device not found
This is what I did when in the directory using Terminal within that directory. I was in Fastboot USB for the ADB push
home:Android Greg$ ./adb push ar10.1.zip /data/media/
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
And when I do Fastboot Devices and ADB Devices, I get this in Fastboot USB mode
home:Android Greg$ ./fastboot devices
HT34LW912007 fastboot
home:Android Greg$ ./adb devices
List of devices attached
home:Android Greg$
This has really got me puzzled
shinobix37 said:
I've seen this happen on my friend's HTC One a week ago. I was able to fix it by using the ALL IN ONE TOOL that was posted in this forum. I SIDELOADED a ROM, but only AFTER flashing the stock Boot.img and kernel. I dunno if this helps, but it certainly fixed the problem for me.... oh and also, I did this on a Windows 7 lappy and I'm not familiar with Macs.
Click to expand...
Click to collapse
@shinobix37
Can you give me the link for the AllInOne Tools etc and where to download the Stock Kernel etc and how you did the side load.
Seems the SDK ADB is not working for me. Fastboot obviously is. This is all really strange
aussie_boi said:
@shinobix37
Can you give me the link for the AllInOne Tools etc and where to download the Stock Kernel etc and how you did the side load.
Seems the SDK ADB is not working for me. Fastboot obviously is. This is all really strange
Click to expand...
Click to collapse
When you use the command make sure your in cwm not fastboot.
So go into cwm then use command that you said before
Sent from my HTC One using xda premium
Android The Greek said:
When you use the command make sure your in cwm not fastboot.
So go into cwm then use command that you said before
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Thanks. I had been in CWM earlier, and the same as just now, when I try ./adb devices ... while in CWM, terminal returns no listing of devices.
It seems to me that ADB does work, as it identifies the "daemon is out of date" and restarts it successfully.
It is just that ADB does not recognise the HTC One, whilst "Fastboot devices" does, while not in fast boot usb.
I am still lost. CWM works. ADB cannot connect ...
Help
After i have put in the Superuser-3.1.3-arm-signed.zip in the phone så did i get the app Superuser.
Type in adb.exe shell and press enter
You should get $ meaning adb has connected to your phone.
This is the problem
The commond promt say that i not are connected to the phone,is this normal
I restart the phone to normal mode with the sim card in.
The problem is now that i can not call with the phone,is this normal
Do i need to put up a new rom ex Lacoste_ModV5Incredible S_03.05
Would need more details.. ROM??? Bootloader?? Etc etc..
Sent from my HTC Incredible S
mafie said:
Would need more details.. ROM??? Bootloader?? Etc etc..
Sent from my HTC Incredible S
Click to expand...
Click to collapse
The phone is unlocked (that did i fix)
Vivo pvt ship s-on
Hboot-2.02.0002
Radio-3831.18.00.11_m
emmc-boot
May 22 2012314,22:08
I have done everything and even 5. Install Superuser and Test Root Access
Is this something i need to do,to get the phone working
"EXTREMELY IMPORTANT IF YOU ARE PLANNING TO STOP GUIDE HERE. LIKE REALLY IMPORTANT!!!!!!!!!!!!!!!!!!!!!!!
At this point you will be able to flash most ROMs. The exceptions are the one that require S-OFF (the ROM requirements in the thread will state so). Also you will have to flash the boot.img manually
To do this download your select ROM. Extract the boot.img to where you have the fastboot.exe, adb.exe, and AdbWinApi.dll (you should have gotten these 3 files when you unlocked the bootloader). Then open the command window (shift, right click, open command window here) and type:
fastboot flash boot boot.img
the boot.img can be renamed to whatever you would like. I keep all my boot images and the fastboot.exe, adb.exe, and AdbWinApi.dll in 1 folder because i download a lot of ROMs. If you do rename the boot.img, i suggest renaming it to the name of the ROM its for. When you type in the fastboot command, just remember to put the .img at the end. This is necessary or it will not work.
If you want to gain S-OFF continue through the guide.
Is this what you want to know"
If i should to that what room are then talking about (it is ex Lacoste that i want to have)
Thanks for the help you are so kind
Factasy said:
After i have put in the Superuser-3.1.3-arm-signed.zip in the phone så did i get the app Superuser.
Type in adb.exe shell and press enter
You should get $ meaning adb has connected to your phone.
This is the problem
The commond promt say that i not are connected to the phone,is this normal
I restart the phone to normal mode with the sim card in.
The problem is now that i can not call with the phone,is this normal
Do i need to put up a new rom ex Lacoste_ModV5Incredible S_03.05
Click to expand...
Click to collapse
It means there is an issue with your ADB drivers.
Did you flash the .zip in recovery?
Did you navigate to the right file in command prompt?
Does your device have Android Debugging enabled?
Is your phone connected to the computer?
Guess u must have not installed the HTC sync drivers..try doing that..
Sent from my HTC Incredible S
mafie said:
Guess u must have not installed the HTC sync drivers..try doing that..
Sent from my HTC Incredible S
Click to expand...
Click to collapse
I took the driver from this page http://forum.xda-developers.com/showthread.php?t=2089508
I have Windows 7
C:\android>adb.exe shell
error: device not found
072665995 said:
It means there is an issue with your ADB drivers.
Did you flash the .zip in recovery?
Did you navigate to the right file in command prompt?
Does your device have Android Debugging enabled?
Is your phone connected to the computer?
Click to expand...
Click to collapse
Yes Debugging enabled
No Did you flash the .zip in recovery?
Yes Did you navigate to the right file in command prompt?
Yes Is your phone connected to the computer?
I did Everything in the guide http://forum.xda-developers.com/showthread.php?t=2118187
And i did 5. Install Superuser and Test Root Access
It is here the problems came
I have solved the
C:\android>adb.exe shel
[email protected]:/ $ su Now
But i cant dail with the phone why
Factasy said:
Yes Debugging enabled
No Did you flash the .zip in recovery?
Yes Did you navigate to the right file in command prompt?
Yes Is your phone connected to the computer?
I did Everything in the guide http://forum.xda-developers.com/showthread.php?t=2118187
And i did 5. Install Superuser and Test Root Access
It is here the problems came
Click to expand...
Click to collapse
Factasy said:
I have solved the
C:\android>adb.exe shel
[email protected]:/ $ su Now
But i cant dail with the phone why
Click to expand...
Click to collapse
The guide says to flash the superuser zip in recovery... Let's start with that first.
As to your dialer not working, reflash the ROM if its custom. If its stock, don't bother with it and just flash a custom ROM later.
072665995 said:
The guide says to flash the superuser zip in recovery... Let's start with that first.
As to your dialer not working, reflash the ROM if its custom. If its stock, don't bother with it and just flash a custom ROM later.
Click to expand...
Click to collapse
I noticed a funny thing.
I only have 3 g on your mobile now no gsm networks
And how do i flash the superuser zip in recovery. Maby i are blind
I have allready the superuser installed in the phone
Ok here is the skinny. I have the Sprint HTC 1. Currently rooted and running Beanstalk 4.3 and TWRP 2.5 ... I have read, re read, and read again how to update my TWRP to 2.6.3 and have no luck.
I have tried Terminal Emulator
I have tired Goo Manager. It actually down loads the file. Runs through the process. Never reboots or updates
I have tried Fastboot. For what ever reason my computer does not pick up and adb devices. It shows Fastboot USB
Any thoughts. I had some unlock this one for me and throw TWRP on. All my others I have done myself.
I love TWRP..but if I cannot fix...what is the easiest way to put Philz or CWM on instead?
Want to update a ROM to 4.4 Kitkat but cannot with out an updated recovery
jaykspokane said:
Ok here is the skinny. I have the Sprint HTC 1. Currently rooted and running Beanstalk 4.3 and TWRP 2.5 ... I have read, re read, and read again how to update my TWRP to 2.6.3 and have no luck.
I have tried Terminal Emulator
I have tired Goo Manager. It actually down loads the file. Runs through the process. Never reboots or updates
I have tried Fastboot. For what ever reason my computer does not pick up and adb devices. It shows Fastboot USB
Any thoughts. I had some unlock this one for me and throw TWRP on. All my others I have done myself.
I love TWRP..but if I cannot fix...what is the easiest way to put Philz or CWM on instead?
Want to update a ROM to 4.4 Kitkat but cannot with out an updated recovery
Click to expand...
Click to collapse
While in fastbootusb check your drivers
Device not recognized? (If you are using Windows 8.1 this will most likely not work)
On your PC go to device manager and find your phone(usually M7WLS), right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good
BD619 said:
While in fastbootusb check your drivers
Device not recognized? (If you are using Windows 8.1 this will most likely not work)
On your PC go to device manager and find your phone(usually M7WLS), right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good
Click to expand...
Click to collapse
Updated the drives. In Fastboot now. on my cmd prompt c:\user\user wont tried typing and ADB Devices and nothiing
In fastbootusb type fastboot devices
BD619 said:
In fastbootusb type fastboot devices
Click to expand...
Click to collapse
Now I am thinking it it my computer. Just re enstalled the SDK packet. Changed path to all c:/Android-ADB and says not a recognizable internal or external file
At this point I need some sleep. Eyes are going crossed.
jaykspokane said:
Now I am thinking it it my computer. Just re enstalled the SDK packet. Changed path to all c:/Android-ADB and says not a recognizable internal or external file
At this point I need some sleep. Eyes are going crossed.
Click to expand...
Click to collapse
PM me tomorrow and I'll help you out
BD619 said:
PM me tomorrow and I'll help you out
Click to expand...
Click to collapse
Sorry been a crazy new year. Still need help.
So downloaded SDK pack. I have tried ADB shell. Fastboot ... etc etc. When in Fastboot I run ADB Devices and nothing is found. however if i have the phone on it works.
at this point...maybe a new recovery?
jaykspokane said:
Sorry been a crazy new year. Still need help.
So downloaded SDK pack. I have tried ADB shell. Fastboot ... etc etc. When in Fastboot I run ADB Devices and nothing is found. however if i have the phone on it works.
at this point...maybe a new recovery?
Click to expand...
Click to collapse
While in bootloader/fastbootusb type fastboot devices
adb devices =OS and recovery
fastboot devices = bootloader/fastbootusb
BD619 said:
While in bootloader/fastbootusb type fastboot devices
adb devices =OS and recovery
fastboot devices = bootloader/fastbootusb
Click to expand...
Click to collapse
Ok... recognized a device was attached. So type the following
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img
and I got error cannot open 'openrecovery-twrp-2.6.3.0-m7wls.img'
This is TWRPS guidelines
Download the above file into your platform-tools dir. Turn off your device. Turn on the device and keep holding volume down until a menu shows up. Select fastboot from the menu list. Plug the device into your computer. If you have the right drivers installed, your screen should now say FASTBOOT USB. Run the following command via the command line:
fastboot flash recovery recoveryfilename.img
Note that you will need to change the last part to match the name of the file that you just downloaded. This method requires that you have the drivers installed that come with the HTC Sync software that are available here. You will also need adb and fastboot for your computer.
jaykspokane said:
Ok... recognized a device was attached. So type the following
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img
and I got error cannot open 'openrecovery-twrp-2.6.3.0-m7wls.img'
This is TWRPS guidelines
Download the above file into your platform-tools dir. Turn off your device. Turn on the device and keep holding volume down until a menu shows up. Select fastboot from the menu list. Plug the device into your computer. If you have the right drivers installed, your screen should now say FASTBOOT USB. Run the following command via the command line:
fastboot flash recovery recoveryfilename.img
Note that you will need to change the last part to match the name of the file that you just downloaded. This method requires that you have the drivers installed that come with the HTC Sync software that are available here. You will also need adb and fastboot for your computer.
Click to expand...
Click to collapse
Try
fastboot erase cache <enter>
then
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img <enter>
You did install the android sdk right?
BD619 said:
Try
fastboot erase cache <enter>
then
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img <enter>
You did install the android sdk right?
Click to expand...
Click to collapse
I did. Just to make certain the other night...I down loaded the Android SDK pack. i can run ADB and Fastboot. Pulls all the info etc.
Will try erase cache
jaykspokane said:
I did. Just to make certain the other night...I down loaded the Android SDK pack. i can run ADB and Fastboot. Pulls all the info etc.
Will try erase cache
Click to expand...
Click to collapse
What does this mean?
BD619 said:
What does this mean?
Click to expand...
Click to collapse
Sorry. Meant it just lists all the available command for each respectively...lists the commands etc.
So did the erase and still same error.
All my apps and data are backed up on Titanium. How hard would it be to just have a new recovery installed?
jaykspokane said:
Sorry. Meant it just lists all the available command for each respectively...lists the commands etc.
So did the erase and still same error.
All my apps and data are backed up on Titanium. How hard would it be to just have a new recovery installed?
Click to expand...
Click to collapse
Navigate to the platform tools folder
Press shift and right click inside the folder and choose open cmd here
jaykspokane said:
Sorry. Meant it just lists all the available command for each respectively...lists the commands etc.
So did the erase and still same error.
All my apps and data are backed up on Titanium. How hard would it be to just have a new recovery installed?
Click to expand...
Click to collapse
May be a moot point. I am upgrading to a Team Nocturnal_xR1 which is a 4.4 ROM. So far it has been loading and allowed the file on a TWRP 2.5.0.0 version. I still need to upgrade the TWRP version. Right now looks like it may work.
jaykspokane said:
May be a moot point. I am upgrading to a Team Nocturnal_xR1 which is a 4.4 ROM. So far it has been loading and allowed the file on a TWRP 2.5.0.0 version. I still need to upgrade the TWRP version. Right now looks like it may work.
Click to expand...
Click to collapse
back to square one. LOL.
and no opening cmd from there did not work either
Check PM
I had a similar issue where I needed the updated twrp. I ended up using the original AIO toolkit that I used to root the phone/unlock the phone to begin with.
I found the latest version of the AIO (made by Hasoon: http://www.hasoon2000.info/getdownl...obile,ATT,Sprint)/One_All-In-One_Kit_v3.1.rar) and the latest image of TWRP from here: http://teamw.in/twrp_view_all_devices.
After installing hasoon, stick the downloaded image in the data/recoveries folder w/in the folders from the AIO. Next use the "Your Own Recovery" option under the flash a recovery option and choose that image instead. Worked great for me several times. Hopefully it does for you. Let me know if you have question.
BD619 said:
Check PM
Click to expand...
Click to collapse
I've been struggling for a week with this.
Trying to unlock the bootloader but whenever I get to the stage of using command prompt I get this message;
'fastboot' is not recognized as an internal or external command,
operable program or batch file
The PC just will not recognise the phone when in fastboot mode although it does when not.
Windows 7
Android 4.3
HTC Sense Version 5.5
Software number 3.62.401.1
HTC SDK API Level 5.65
USB Debugging ticked
Fast boot deticked
HTC cable used
Latest drivers installed
Any help would be appreciated, the only previous experince I have is rooting a Galaxy note and tablet with no trouble whatsoever.
tj
tjpearson said:
I've been struggling for a week with this.
Trying to unlock the bootloader but whenever I get to the stage of using command prompt I get this message;
'fastboot' is not recognized as an internal or external command,
operable program or batch file
The PC just will not recognise the phone when in fastboot mode although it does when not.
Windows 7
Android 4.3
HTC Sense Version 5.5
Software number 3.62.401.1
HTC SDK API Level 5.65
USB Debugging ticked
Fast boot deticked
HTC cable used
Latest drivers installed
Any help would be appreciated, the only previous experince I have is rooting a Galaxy note and tablet with no trouble whatsoever.
tj
Click to expand...
Click to collapse
Do you have fastboot.exe on your computer? It looks like CMD isn't finding fastboot.exe 1-because you don't have it 2- because you have not started your cmd prompt from your fastboot.exe folder
can you post a screenshot of your cmd prompt when you get this error?
ADB Installer
Installed ADB Installer and now been able to copy and been able to submit my token.
Recieved email reply with unlock code and it came as a VLC icon, still put this onto my phone but now get message 'unable to open bin file'
Got one step further but now unable to open file.
Below is the message I get:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\tjpearson>fastboot flash unlocktoken Unlock_code.bin
error: cannot open 'Unlock_code.bin'
C:\Users\tjpearson>
Your help is very much appreciated but my wife fails to understand my pannick and she thinks out tea is more important so may not get back to you straight away.
tj
tjpearson said:
Installed ADB Installer and now been able to copy and been able to submit my token.
Recieved email reply with unlock code and it came as a VLC icon, still put this onto my phone but now get message 'unable to open bin file'
Got one step further but now unable to open file.
Below is the message I get:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\tjpearson>fastboot flash unlocktoken Unlock_code.bin
error: cannot open 'Unlock_code.bin'
C:\Users\tjpearson>
Your help is very much appreciated but my wife fails to understand my pannick and she thinks out tea is more important so may not get back to you straight away.
tj
Click to expand...
Click to collapse
Think you need to open the command prompt in the adb folder, and also have the unlock_code.bin in that same folder.
mb_guy said:
Think you need to open the command prompt in the adb folder, and also have the unlock_code.bin in that same folder.
Click to expand...
Click to collapse
OK, I'll try this tomorrow, thanks for the help.
Originally Posted by mb_guy
Think you need to open the command prompt in the adb folder, and also have the unlock_code.bin in that same folder.
Click to expand...
Click to collapse
OK, I'll try this tomorrow, thanks for the help.
Click to expand...
Click to collapse
Like mb_guy said, you MUST place the bin file in the same folder where adb and fastboot are. Every time you want to flash a file to your phone it must be in that folder, otherwise fastboot won't find it and it will output you that error (can't open file). That rule apply to recovery, unlock code, rom, kernel, ruu, firmware etc etc.
Sent from my HTC One using xda app-developers app
alray said:
Like mb_guy said, you MUST place the bin file in the same folder where adb and fastboot are. Every time you want to flash a file to your phone it must be in that folder, otherwise fastboot won't find it and it will output you that error (can't open file). That rule apply to recovery, unlock code, rom, kernel, ruu, firmware etc etc.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thanks for the help because at least I've now been able to unlock bootloader.
My problem now is 'fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img' command line and yet again I'm getting error unable to open as below;
C:\Users\tjpearson>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
error: cannot open 'openrecovery-twrp-2.6.3.0-m7.img'
Even placing zip on root of phone and in adb folder still no joy.
tj
tjpearson said:
Thanks for the help because at least I've now been able to unlock bootloader.
My problem now is 'fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img' command line and yet again I'm getting error unable to open as below;
C:\Users\tjpearson>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
error: cannot open 'openrecovery-twrp-2.6.3.0-m7.img'
Even placing zip on root of phone and in adb folder still no joy.
tj
Click to expand...
Click to collapse
''error: cannot open'' is caused because fastboot don't find the file. Is the recovery file you are trying to flash is named exactly <openrecovery-twrp-2.6.3.0-m7.img> ?
Btw I'll recommend you to flash twrp 2.6.3.3 not 2.6.3.0 as you could have issur flashing newer 4.4 rom
Code:
fastboot flash recovery <name_of_file.img>
fastboot erase cache
fastboot reboot-bootloader
alray said:
''error: cannot open'' is caused because fastboot don't find the file. Is the recovery file you are trying to flash is named exactly <openrecovery-twrp-2.6.3.0-m7.img> ?
Btw I'll recommend you to flash twrp 2.6.3.3 not 2.6.3.0 as you could have issur flashing newer 4.4 rom
Code:
fastboot flash recovery <name_of_file.img>
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
Yes, named exactly the same.
It's driving me mad, if the bootloader is now unlocked is there an easier way to flash twrp and then root.
Whats the best way to check adb is actually communicating with the phone
tj
tjpearson said:
Yes, named exactly the same.
It's driving me mad, if the bootloader is now unlocked is there an easier way to flash twrp and then root.
Whats the best way to check adb is actually communicating with the phone
tj
Click to expand...
Click to collapse
Do you have a Sprint phone ? and can you post a screen shot of your adb / fastboot folder containing the files or at least post your results for dir
open command prompt from your adb / fastboot folder (shift+right click - command prompt here)
type
adb devices
your device SN will be here
type
adb reboot bootloader
you should be in fastboot usb
type
fastboot devices
again your serial no should be here
type dir
you should see the contains of the folder your in
now
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
if error change the twrp name to match the one in the dir command above
clsA said:
Do you have a Sprint phone ? and can you post a screen shot of your adb / fastboot folder containing the files or at least post your results for dir
open command prompt from your adb / fastboot folder (shift+right click - command prompt here)
type
adb devices
your device SN will be here
type
adb reboot bootloader
you should be in fastboot usb
type
fastboot devices
again your serial no should be here
type dir
you should see the contains of the folder your in
now
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
if error change the twrp name to match the one in the dir command above
Click to expand...
Click to collapse
I seem to have a problem adb detecting the connected phone, I'll unistall and start again and if I can then get back to you later I'd appreciate it very much.
The phone is UK on 02 Android 4.4 HTC Sense version 5.5
tj
tjpearson said:
I seem to have a problem adb detecting the connected phone, I'll unistall and start again and if I can then get back to you later I'd appreciate it very much.
The phone is UK on 02 Android 4.4 HTC Sense version 5.5
tj
Click to expand...
Click to collapse
can you check my guide under faq #2, if that solves it
Well, think I'll give up with rooting my HTC One, I have never had so much trouble routing a divice as this. My bootloader is now unlocked and that's about as far as I get.
My phone seems to have been detected once through adb that then allowed me to run unlock token but everything else just fails.
In one last attempt I've attached image of ADB folder and below is result from command line.
It must be my age because evertybing seems so complex nowadays
C:\Android>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
target reported max download size of 1526722560 bytes
error: cannot load 'openrecovery-twrp-2.6.3.3-m7.img': No error
C:\Android>
tjpearson said:
Well, think I'll give up with rooting my HTC One, I have never had so much trouble routing a divice as this. My bootloader is now unlocked and that's about as far as I get.
My phone seems to have been detected once through adb that then allowed me to run unlock token but everything else just fails.
In one last attempt I've attached image of ADB folder and below is result from command line.
It must be my age because evertybing seems so complex nowadays
C:\Android>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
target reported max download size of 1526722560 bytes
error: cannot load 'openrecovery-twrp-2.6.3.3-m7.img': No error
C:\Android>
Click to expand...
Click to collapse
cannot load = MyFileNameIsWrong
and from the screenshot you posted the filename is: openrecovery-twrp-2.6.3.3-m7.img.img <- yes, double extension, next time do a "dir" in command prompt to see your filenames, not in Windows Explorer.
d -darrrrr
nkk71 said:
cannot load = MyFileNameIsWrong
and from the screenshot you posted the filename is: openrecovery-twrp-2.6.3.3-m7.img.img <- yes, double extension, next time do a "dir" in command prompt to see your filenames, not in Windows Explorer.
Click to expand...
Click to collapse
I love you nkk71, I really can't tell you how much I love you but I do !!!!! :victory:
Did what you said and fumbled through flashing twrp and then adding superuser after to the phones root, did recovery again and installed superuser via twrp and bingo, rooted and confirmed.
Been struggling 2 weeks with this and non stop all weekend, my wife wants a divorce but I don't care cos I'M ROOTED !!
Thanks so much for all the help, nice one :good:
tj
tjpearson said:
I love you nkk71, I really can't tell you how much I love you but I do !!!!! :victory:
Did what you said and fumbled through flashing twrp and then adding superuser after to the phones root, did recovery again and installed superuser via twrp and bingo, rooted and confirmed.
Been struggling 2 weeks with this and non stop all weekend, my wife wants a divorce but I don't care cos I'M ROOTED !!
Thanks so much for all the help, nice one :good:
tj
Click to expand...
Click to collapse
Lol
Now that the phone is good, go spend some time with your better half!!!
No guides on xda, on "how to return my marriage to stock"
Put the phone on the charger or something, and spend time with your significant other.
Sent from my HTC One using Tapatalk
One last question
nkk71,
Can I uninstall Superuser now and install SuperSU instead cos I've already purchased that when had the Note rooted or will it cause me more time away from the mrs with issues.
tj
tjpearson said:
nkk71,
Can I uninstall Superuser now and install SuperSU instead cos I've already purchased that when had the Note rooted or will it cause me more time away from the mrs with issues.
tj
Click to expand...
Click to collapse
Shouldn't be a problem, use the flashable zip from the thread: http://forum.xda-developers.com/showthread.php?t=1538053
Yeah , sorted.
Thanks again for all your help.
tj
Hello,
i unlocked Bootloader and wanted to configure twrp.
I used this tutorial: unofficialtwrp.com/nubia-red-magic-3-nx629j-root-twrp/
And from the point where it says "now open cmd in the adb tools folder and type below code" nothing works!
I always get an error that it couldnt the needed files/folder whatever.
What am i doing wrong?
My Phone is connected by cable to my PC and USB Debugging is turned on.
dre11111 said:
Hello,
i unlocked Bootloader and wanted to configure twrp.
I used this tutorial: unofficialtwrp.com/nubia-red-magic-3-nx629j-root-twrp/
And from the point where it says "now open cmd in the adb tools folder and type below code" nothing works!
I always get an error that it couldnt the needed files/folder whatever.
What am i doing wrong?
My Phone is connected by cable to my PC and USB Debugging is turned on.
Click to expand...
Click to collapse
Copy you abd folder location
Open cmd
Type:
Cd {your adb file location}
And now you can flash ur TWRP
em902566 said:
Copy you abd folder location
Open cmd
Type:
Cd {your adb file location}
And now you can flash ur TWRP
Click to expand...
Click to collapse
Thank you for helping me but it knows my adb location but doesnt accept an comands i type. Unlocking bootloader worked perfectly by using cmd but using adb doesnt. I dont understand why...
I just dont get it done to get to twrp launcher.
Maybe it doesnt work because i got a Global Rom and only found one for japanese/US Version?!
dre11111 said:
Thank you for helping me but it knows my adb location but doesnt accept an comands i type. Unlocking bootloader worked perfectly by using cmd but using adb doesnt. I dont understand why...
I just dont get it done to get to twrp launcher.
Maybe it doesnt work because i got a Global Rom and only found one for japanese/US Version?!
Click to expand...
Click to collapse
Yes.
TWRP only works on CN version
Not working on global Version
Does someone know if a twrp global will be available some day?