Trying to get myself from Tron 1.2 to Infection 2.2 and finally got to the last step of sending the boot.img with [fastboot flash boot boot.img]. Getting an error message that I can't get past. I've shut down every application, no HTC sync installed. Drivers refreshed. Tried recopying the boot.img from the zip. What am I missing? I included a screenshot of my platform-tools folder and the command prompt. Maybe I'm missing something?
JayToTheMo said:
Trying to get myself from Tron 1.2 to Infection 2.2 and finally got to the last step of sending the boot.img with [fastboot flash boot boot.img]. Getting an error message that I can't get past. I've shut down every application, no HTC sync installed. Drivers refreshed. Tried recopying the boot.img from the zip. What am I missing? I included a screenshot of my platform-tools folder and the command prompt. Maybe I'm missing something?
Click to expand...
Click to collapse
I take it boot.img is in the same directory as fastboot?
In windows explorer when you're at the window thats in the screenshot, click on organize, folder and search options. Change to the "view" tab up at the top of the new window and then uncheck "hide extensions for known file types"
That will make your life a lot easier, and I think you wont have any problem naming boot.img with the right extension and flashing.
Related
I flashed pudding on my 1.83 ATT atrix. This worked fine, and I am trying to get CWM for unlocked bootloaders now. I am following the instructions directly from the thread: http://forum.xda-developers.com/showthread.php?t=1138541
Problem is, after extracting the zip to C: and running "fastboot flash recovery C:\(image name).img", I get "fastboot is not recognized as an internal or external command..."
This leads me to believe that I don't have adb set up properly. I have standard adb set up for pushing apk's, but am I missing something specific for fastboot?
All i have under android-sdk-windows>platform-tools is adb.exe adbwinapi.dll and adbwinusbapi.dll. I DO have USB debugging on lol.
I seem to remember having more stuff under platform tools at an earlier date. All the threads for setting up adb are LONG buried, and after exhaustive searching, I finally gave up and decided to post (at least not in dev ). Even turning to google for adb help, I only get a bunch of the ad-farming tip websites that are outdated.
Please help me out guys. I can usually help myself after enough research, but I admit defeat on this one :/
Thanks much,
-omni
omni_angel7 said:
I flashed pudding on my 1.83 ATT atrix. This worked fine, and I am trying to get CWM for unlocked bootloaders now. I am following the instructions directly from the thread: http://forum.xda-developers.com/showthread.php?t=1138541
Problem is, after extracting the zip to C: and running "fastboot flash recovery C:\(image name).img", I get "fastboot is not recognized as an internal or external command..."
This leads me to believe that I don't have adb set up properly. I have standard adb set up for pushing apk's, but am I missing something specific for fastboot?
All i have under android-sdk-windows>platform-tools is adb.exe adbwinapi.dll and adbwinusbapi.dll. I DO have USB debugging on lol.
I seem to remember having more stuff under platform tools at an earlier date. All the threads for setting up adb are LONG buried, and after exhaustive searching, I finally gave up and decided to post (at least not in dev ). Even turning to google for adb help, I only get a bunch of the ad-farming tip websites that are outdated.
Please help me out guys. I can usually help myself after enough research, but I admit defeat on this one :/
Thanks much,
-omni
Click to expand...
Click to collapse
If your on linux it's "./moto-fastboot" not just fastboot.
Windows 7 64 bit. sorry, should have specified.
Nobody with win 7 knowledge/advice?
Alrighty, let us see here...
Try this.
1: Create a folder named fastboot (or whatever you prefer, just something simple like that) on the root of your C drive.
2: Download this file, http://www.mediafire.com/?yl17mz8l7w9h687
3: Unzip contents of said file into the folder you created in step 1
4: Click on Start, type cmd into the bar at the bottom and hit enter
5: Type cd C:\fastboot (or whatever you named the folder in step one)
6: Type moto-fastboot flash recovery recovery-en-goapk-0630-1029.img
That should work. The recovery included in the flash is current AS OF THIS POST. Obviously, the instructions will change if you download a newer copy of CWM as they are released, since the filename of the recovery file will change.
If you are wondering why it is moto-fastboot, the fastboot I included is the modified one that allows for larger img flashing. Not particularly useful anymore, with CWM working well now and all... but hey.
Diviance said:
Alrighty, let us see here...
Try this.
1: Create a folder named fastboot (or whatever you prefer, just something simple like that) on the root of your C drive.
2: Download this file, http://www.mediafire.com/?yl17mz8l7w9h687
3: Unzip contents of said file into the folder you created in step 1
4: Click on Start, type cmd into the bar at the bottom and hit enter
5: Type cd C:\fastboot (or whatever you named the folder in step one)
6: Type moto-fastboot flash recovery recovery-en-goapk-0630-1029.img
That should work. The recovery included in the flash is current AS OF THIS POST. Obviously, the instructions will change if you download a newer copy of CWM as they are released, since the filename of the recovery file will change.
If you are wondering why it is moto-fastboot, the fastboot I included is the modified one that allows for larger img flashing. Not particularly useful anymore, with CWM working well now and all... but hey.
Click to expand...
Click to collapse
Thanks SO much for the quick response and all the effort I'd actually updating OTA from 1.26 because I flashed back, thinking no one was gonna help! Well, when I feel up to it another night. I'll give this another shot. Thanks for the custom fastboot, too!
i get < waiting for device >
did i do something wrong?
Me too. ^^^^^^^
I figured it out, i forgot to put it into fastboot mode!
did not work for me
when I do what you told the other guy it says system cant find the path specified couls you please help I have spent a couple of days trying different things and also when I try to erase the recovery installer file it want let me
OK so I put the BAMF Cubed Kernel on my phone and now I can't flash other kernels.
Many of us are having this problem, and I am having trouble installing new kernels when I try new ROMs.
Would someone please tell me step by step how to do this?
My understanding is that the boot.img file should be placed in the same folder on my PC as adb.exe, Fastboot, etc...
Is this correct? If so, what is the command line I should use to push the kernel to the phone?
Example: I want to try the new RezROM ICS from lllboredlll.
I downloaded the ROM, and have the zip on my phone's SD card. I also have it on my PC.
When I open it, I see a folder called Kernel. In that folder, there is a boot image. Also in that folder is a PH98IMG file containing a second boot image.
Which one is the correct kernel file to push via PC?
The way I understand it and have been doing it. Open up the zipped rom and you will see a boot image , extract or copy it to the folder that you have fastboot in . Then in Hboot..pull up a CMD box.. and either change location or if you have abd in your path.. the instructions are fastboot flash boot boot.img
then that should flash the kernel .. then boot to recovery ..wipe data/factory reset and then flash the rom .
BBEgo said:
OK so I put the BAMF Cubed Kernel on my phone and now I can't flash other kernels.
Many of us are having this problem, and I am having trouble installing new kernels when I try new ROMs.
Would someone please tell me step by step how to do this?
My understanding is that the boot.img file should be placed in the same folder on my PC as adb.exe, Fastboot, etc...
Is this correct? If so, what is the command line I should use to push the kernel to the phone?
Click to expand...
Click to collapse
Boot the phone into fastboot. Plug in the USB cable, open a CMD window on your computer. Set the current directory to the folder with adb.exe, fastboot.exe, and your new boot.img file.
enter the command:
fastboot flash boot boot.img
How come no one sets up their path to include the android-SDK folder with adv, fastboot...etc? I did and makes life so much easier since you never have to cd to anything to run those commands.
Sent from my ADR6425LVW using Tapatalk
I never noticed that CWM was different for 1.2 and 1.1. I currently have 1.2 and tired to install CWM which was the wrong one.
When I try to enter recovery, I get a message of " booting recovery kernel image"
I can turn it off and enter into the stock rom no problem.
Any help would be great to how I can undo this and install CWM.
Used the link for CWM from step 1 from this LINK
Thanks very much.
Tap UI Version : 1.2-5699
Kernal - 2.6.32.9-svn4979
Build - FRF91
Here is a link to a .zip I built for you. You will need to have root access for this.
fix-recovery.zip
Download this to your Gtablet and unzip it to /sdcard. Iif you can't make that work, download to your PC and unzip, then transfer the files over to /sdcard. Using a root file manager (I like ES File Explorer), move the file 'flash_image' into /system/bin, overwrite or rename the existing version if there is one, and change the permissions to make it executable (match the other executable files in the /system/bin folder). Then move the file 'cwm5502.img' into /system/etc/recovery (you might have to create the 'recovery' folder). Next, go back to /sdcard and change permissions on 'fixrecovery.sh' to make it executable as well.
Now open Terminal Emulator (install from the Play store or by other means if you don't already have it) and enter the following commands:
Code:
su
sh /mnt/sdcard/fixrecovery.sh
If the second command won't run, bypass the script by running this instead:
Code:
su
/system/bin/flash_image recovery /system/etc/recovery/cwm5502.img
That will install a version of CWM that is compatible with the 1.2 boot loader. Reboot and you should be able to enter the new recovery. Post back if you cannot get this to work for you, and we can try another way. This would be easier if you have ADB installed and working, but I assume most people do not.
Rochey21 said:
I never noticed that CWM was different for 1.2 and 1.1. I currently have 1.2 and tired to install CWM which was the wrong one.
When I try to enter recovery, I get a message of " booting recovery kernel image"
I can turn it off and enter into the stock rom no problem.
Click to expand...
Click to collapse
Since you have the stock VS ROM, you'll have to use nvflash. See this thread.
---------- Post added at 08:05 PM ---------- Previous post was at 08:02 PM ----------
DaggerDave said:
Here is a link to a .zip I built for you. You will need to have root access for this.
...
Click to expand...
Click to collapse
Good try, but, there's no su on stock ROM; and the process to get one correctly installed is slightly involved.
The user will have to resort to nvflash.
rajeevvp said:
Since you have the stock VS ROM, you'll have to use nvflash. See this thread.
---------- Post added at 08:05 PM ---------- Previous post was at 08:02 PM ----------
Good try, but, there's no su on stock ROM; and the process to get one correctly installed is slightly involved.
The user will have to resort to nvflash.
Click to expand...
Click to collapse
Ok thanks, but I can not find the drivers for APX Mode, using Windows vista 32 bit?
Also just to make sure what Files would I need to use. Just want to make sure exactly what to do, and get it right.
Download the TeamDRH_350M_Prep.zip file from this post. It should have both the nVidia APX drivers and CWM-5.5.0.4 for a 1.2 bootloader (in part9.img).
Read the README file for the APX driver installation, but, don't run the NVFlash_gTablet.bat batch file. Instead, just write a new CWM using the commands in the link in my previous post.
EDIT: Note that you cannot install or upgrade the stock VS ROM using CWM. That can only be done using the stock recovery. For everything else, however, you can use CWM.
Feel like a total N00b :crying:
I have the drivers installed for AXB. I have downloads the zip folder with the img files and drivers etc. I renamed this folder to NVFlash for short.
Do I leave this folder on my laptop or put in on the tablet.
Could you please explain a bit more how to use the command window. I open it but cant seem to get it to work.
I have the folder I download unzipped and saved as C:\NVFlash
Not sure how to do step 2
2. Run this command to determine the partition no. of the recovery (SOS) partition--usually, it is 9: Open a CMD.exe window, then change into the directory containing both the nvflash.exe and the bootloader.bin files. Then run:
You have been very helpful thanks again.
Rochey21 said:
Do I leave this folder on my laptop or put in on the tablet.
Click to expand...
Click to collapse
It's meant to be used on an x86 system (desktop, laptop, ...) running Windows or Linux. You can't run .dll and .exe files--Intel binaries--on an ARM tablet, right?
Could you please explain a bit more how to use the command window. I open it but cant seem to get it to work.
I have the folder I download unzipped and saved as C:\NVFlash
Click to expand...
Click to collapse
Change to the directory containing the nvflash executable and bootloader.bin like this (only type in the stuff in bold):
Code:
[I]C:\SOME\PATH[/I]> [B]cd c:\NVFlash[/B] [I]Change to NVFlash directory[/I]
C:\NVFlash> [I] Note the changed prompt[/I] [I]now[/I]
After that, substitute C:\NVFlash\part9.img instead of C:\SOME\PATH\recovery.img in the given command line.
I understand I cant run the files on the tablet, just meant do I need to transfer any files to the tablet during the process or is it all done through the command window.
I have attached the command window. I typed cd c:\NVFlash and the directory changed to NVFlash.
Not sure how I substitute img 9 then?
EDIT* I got the p.txt file. How would I read this file?
Just looking to get CWM running so I can update to a new custom rom.
Rochey21 said:
I understand I cant run the files on the tablet, just meant do I need to transfer any files to the tablet during the process or is it all done through the command window.
Click to expand...
Click to collapse
No need to transfer anything.
EDIT* I got the p.txt file. How would I read this file?
Click to expand...
Click to collapse
Any editor will read that file. Just double-click on the filename.
Just looking to get CWM running so I can update to a new custom rom.
Click to expand...
Click to collapse
Which one?
rajeevvp said:
No need to transfer anything.
Any editor will read that file. Just double-click on the filename.
Which one?
Click to expand...
Click to collapse
JellyBean Smoother Seems to be good?
Sorry which editor would that be? I opened it in wordpad/notepad and it is all just symbols.
Would something like Hex editor read it?
Rochey21 said:
JellyBean Slim Seems to be good?
Click to expand...
Click to collapse
In that case, shut off the tablet; put it back into APX mode using Power and Vol [-]; then double-click the NVFlash_gTablet.bat batch file. It will do all the prep steps (including installing CWM) needed for a Jellybean ROM install. After the tablet boots into CWM, transfer the ROM install zip file onto the tablet and follow the instructions given in the ROM's first post to install the ROM.
Sorry which editor would that be? I hope it in wordpad/notepad and it is all just symbols.
Click to expand...
Click to collapse
Ah! You've got one of the screwey nvflash executables which produce a binary output. Ignore all this, then.
Ok So do I ignore everything or click the NVFlash_gTablet.bat file?
Rochey21 said:
click the NVFlash_gTablet.bat file?
Click to expand...
Click to collapse
Yes.
(Turn the tablet off, then put it back into APX mode again, though. Otherwise, the batch file will error out.)
rajeevvp said:
Yes.
(Turn the tablet off, then put it back into APX mode again, though. Otherwise, the batch file will error out.)
Click to expand...
Click to collapse
Finally :victory:
Thanks very much for all your help.
I have Smoother Bean installed, doesn't seem to be running correctly but il figure that out myself.
Thanks again.
I use hassoon2000's one x+ all in one kit, and whenever I try to install a new kernel's boot.img, I can never know if a kernel is successfully flashed.
The bootloader screen stays the same and when I reboot the phone, WiFi is broken!
Please help, what should I do? How can I tell if the boot.img is successfully flashed? and How can I install a boot.img?
Edit: I noticed that CMD is opened and the first line says:
'C:Users\(computername) is not recognized as an internal or external command, operable program or batch file.
JustinBieber said:
I use hassoon2000's one x+ all in one kit, and whenever I try to install a new kernel's boot.img, I can never know if a kernel is successfully flashed.
The bootloader screen stays the same and when I reboot the phone, WiFi is broken!
Please help, what should I do? How can I tell if the boot.img is successfully flashed? and How can I install a boot.img?
Edit: I noticed that CMD is opened and the first line says:
'C:Users\(computername) is not recognized as an internal or external command, operable program or batch file.
Click to expand...
Click to collapse
Copy the hasoon's toolkit folder to C:\ and try.
It appears that the path has spaces (you have colored them, so not sure) - this is the most common mistake...
Hope this helps.
Addicted2xda said:
Copy the hasoon's toolkit folder to C:\ and try.
It appears that the path has spaces (you have colored them, so not sure) - this is the most common mistake...
Hope this helps.
Click to expand...
Click to collapse
There are no spaces in the path actually. BUT, copying the toolkit to C:\ helped!
Hi,
I made a mistake installing Cyanogenmod on my phone, forgot to make a backup in TWRP.
This Cyanogenmod version requires me to delete my former EMUI fingerprints for the fingerprint function to work. I forgot to do that also...
So now I'm trying to reinstall my custom ROM. I found the UK PLK-L01 firmware on Huawei support page, downloaded that and put it on my (not external sd)sdcard/dload/UPDATE.APP.
Then I try the Volume UP+Volume Down+Power for it to install the rom, but only thing that happens is that the phone boots into TWRP, and in there, there is no option to install a .APP file.
Please help
frederikahrenst said:
Hi,
I made a mistake installing Cyanogenmod on my phone, forgot to make a backup in TWRP.
This Cyanogenmod version requires me to delete my former EMUI fingerprints for the fingerprint function to work. I forgot to do that also...
So now I'm trying to reinstall my custom ROM. I found the UK PLK-L01 firmware on Huawei support page, downloaded that and put it on my (not external sd)sdcard/dload/UPDATE.APP.
Then I try the Volume UP+Volume Down+Power for it to install the rom, but only thing that happens is that the phone boots into TWRP, and in there, there is no option to install a .APP file.
Please help
Click to expand...
Click to collapse
couldnt you just locate files and delete in root explorer or similar app?
You can open the update.app in Huawei update extractor and use adb to manually flash the system, custom, cache, boot and recovery partitions back to stock then once you boot into the stock emui os you can reflash twrp. I'm busy atm but I'll write you a proper guide soon. Or you could Google it but be careful becuase there are a lot of guide that don't work anymore
Edit: This won't require you to wipe your user data so you can keep your setting contacts apps etc.
---------- Post added at 09:07 PM ---------- Previous post was at 08:28 PM ----------
Here is my guide it's a bit long but should be easy. I recommend reading it all first before following it just so you know what each step is doing.
Ok step one. Go to This link and download the emui version for you phone.
step two. You need to download Huawei update extractor from This link and install it on your pc.
Step three. unzip the update you extracted to a new folder on your desktop (It can be called anything bu I recommend calling it "EMUI") and put the update.app file in this folder.
Step four. open Huawei update extractor and select profile "Unknown (worstenbrood)" if it is not selected already.
Step five. Under the section where it says update file click on the ".." button navigate to the folder you made on your desktop and double click the update.app file.
Step six. Right click on the file named "BOOT.img" and click extract selected then once the green loading bar has gotten to 100% click close on the extracting window since it does not automatically do it its self.
Step seven. Repeat step six for the files named "CACHE.img", "CUST.img", "RECOVERY.img", "SYSTEM.img" and "USERDATA.img" (Only extract USERDATA.img if you want to wipe all of you apps, setting, contacts and messages)
Step eight. Open the folder you create on your desktop and copy all of the files you extracted (Only the .img files since Huawei update extractor also create some other files which you don't need) and paste them into the folder which you have adb installed into (It should be "C:\Program Files (x86)\Android\android-sdk\platform-tools" if you used the sdk version but if you have a diffrent version of adb paste them into the folder which you have that installed to)
Step nine. Boot your phone into bootloader mode on you phone. There are a few ways to do this but use whatever way you used when you flashed twrp.
step ten. In widowns explorer (Your pc's file manager) Shift click in the folder you have adb installed into and click "Open cmd window here"
Step eleven. type the following commands into cmd "fastboot flash boot BOOT.img", "fastboot flash cust CUST.img", "fastboot flash recovery RECOVERY.img", "fastboot flash system SYSTEM.img" and if you decided to reset all of you data (Like apps, contacts, messages, setting, etc) "fastboot flash userdata USERDATA.img" Some of these may take a long time (Especially SYSTEM.img but it shouldn't take more than 10 minute if it doesn't finish within 20 minute press ctrl + c in the cmd windows and start again).
Step twelve. Type "fastboot reboot" into cmd and you will boot into stock emui. Now you can reflash TWRP if you want and re install root.
Feel free to message me if you need help.