Related
Hey guys, I'm currently trying to flash back to the new 4.3 factory image that I downloaded from Google, however, it all goes fine, I flashed the bootloader, flashed the radio and it all says it has been updated properly, then when I try and flash the system.img files and boot.img files they just say no such file or directory exists and stops, meaning the phone is unusable at the moment until I flash something.
Anyone know why this is happening?
BTW I'm using a mac.
Issue fixed, see below!
************************************************************************************************
Ok guys, the problem was solved in an odd way!
I got annoyed with the flashing errors, and flashed the old kernel and radio I was using with my Illusion rom which thankfully got me back to that even though I had lost all of my data (backed up though).
For anyone having this problem and wants to unroot to go back to 4.3 or is trying to flash the legit 4.3 rom from Google and then maybe unroot or just use the 4.3 rom direct from Google...
DOWNLOAD THE LEAKED 4.3 ROM AND FLASH USING STANDARD CWM METHOD.
DOWNLOAD THE .84/.83 KERNEL AND FLASH THIS AS WELL.
After this I got the legitimate OTA update which was only 3.4mb and it even fixed root so I am now back to complete stock, locked bootloader and no root!
Hope this helps
Click to expand...
Click to collapse
Easiest way of flashing the system image is to just use the flash-all script included in the TGZ - just extract it out and run it when the phone is connected in fastboot mode. Personally, I do the following:
1. Extract the entire TGZ (including the update.zip)
2. Move all the IMG files into one folder
3. Rename them to easy names, e.g. bootloader, radio, system, userdata, boot, recovery, etc.
4. Flash them all in turn, rebooting the bootloader each time
5. Once all done, erase/format the cache (fastboot erase cache and fastboot format cache)
6. Boot into recovery and clear cache again and then do a factory reset (this makes sure the unit see all the internal memory)
7. Reboot the phone
Should all work now
siravarice said:
Hey guys, I'm currently trying to flash back to the new 4.3 factory image that I downloaded from Google, however, it all goes fine, I flashed the bootloader, flashed the radio and it all says it has been updated properly, then when I try and flash the system.img files and boot.img files they just say no such file or directory exists and stops, meaning the phone is unusable at the moment until I flash something.
Anyone know why this is happening?
BTW I'm using a mac.
Click to expand...
Click to collapse
Maybe you have corrupted files? Retry the download from google and unpack all with 7zip.
I did that yesterday and all works fine.
4.3 (JWR66V)
https://dl.google.com/dl/android/aosp/occam-jwr66v-factory-08d2b697.tgz
7zip
http://www.7-zip.de/
[HOW-TO] How to flash a factory image / return to stock / unlock / root #
http://forum.xda-developers.com/showthread.php?t=2010312
EddyOS said:
Easiest way of flashing the system image is to just use the flash-all script included in the TGZ - just extract it out and run it when the phone is connected in fastboot mode
Click to expand...
Click to collapse
How would I do that on a mac? I tried typing:
./fastboot flash flash-all.bat
but do I need to use the .sh version?
info.brandenburg said:
Maybe you have corrupted files? Retry the download from google and unpack all with 7zip.
I did that yesterday and all works fine.
Click to expand...
Click to collapse
Did that, same thing happened. I tried flashing the entire .zip and then I tried separately and it still didn't work.
Ok so I know it is just the system.img file that doesn't work, as all the other files have just flashed fine! Going to re-download and see if that helps.
siravarice said:
How would I do that on a mac? I tried typing:
./fastboot flash flash-all.bat
but do I need to use the .sh version?
Click to expand...
Click to collapse
You just run the script, you don't flash it. It's a batch file which then does all the fastboot commands. You also use flash-all.sh as you don't have Windows
EddyOS said:
You just run the script, you don't flash it. It's a batch file which then does all the fastboot commands. You also use flash-all.sh as you don't have Windows
Click to expand...
Click to collapse
Still doesn't work.
I used: bash flash-al.sh
And it just said fastboot not found in certain lines for the command and did nothing. I thought it fixed itself when I swapped USB ports but when it got to the system.img it just gave me the same error again. It flashes everything else ok but not this file, it's the third time I have downloaded it and now I have no way to get it back to being useable as when I press start it just gives me a black screen
HELP PLEASE!
I would but I use Windows and it's all fine. Might be worth downloading the factory image again, checking the md5 and trying to flash the system image again
EddyOS said:
I would but I use Windows and it's all fine. Might be worth downloading the factory image again, checking the md5 and trying to flash the system image again
Click to expand...
Click to collapse
Im trying to install some Samsung Android Drivers on my old laptop but the thing is so slow it's basically impossible to work from now
I've redownloaded the files, I don't know how to check the MD5Sum though. Still nothing doing. I get this error:
checking product... OKAY
checking version-bootloader... OKAY
checking version-baseband... OKAY
sending 'boot' (6166 KB)... OKAY
writing 'boot'... OKAY
sending 'recovery' (6664 KB)... OKAY
writing 'recovery'... OKAY
sending 'system' (531281 KB)... ERROR: usb_write failed with status e00002be
FAILED (data transfer failure (No such file or directory))
edue3e4:4.2unrootnexus4 Simon$
It really doesn't want to write the system.img file, or maybe it doesn't want to write to system?
What happens if you extract the system.img file and flash it via fastboot manually?
fastboot flash system system.img
I always use this guide if I forget:
efrant said:
D. Type in the commands into the command prompt
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept. Note: you use the volume keys to change the option and the power button to accept. You cannot use the touch screen.
4) Reboot by typing: fastboot reboot-bootloader
5) Flash the bootloader: fastboot flash bootloader bootloader-mako-makoz10o.img (or whatever the name of the bootloader image that you downloaded).
6) Reboot: fastboot reboot-bootloader
7) Flash the radio: fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img (or whatever the name is of the radio image that you downloaded).
8) Reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system system.img
10) Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked. See note 2 below.
11) Flash the kernel/ramdisk: fastboot flash boot boot.img
12) Flash the recovery partition: fastboot flash recovery recovery.img
13) Erase the cache partition: either a) fastboot erase cache OR b) fastboot format cache <<== the second option seems to work better for most people. Thanks joostburg.
14) Reboot: fastboot reboot
15) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the Dalvik cache.
Now you have a fully stock image on your device. The only thing that is different from out-of-the-box condition is that your bootloader is unlocked. See the notes section at the end of this post for information on re-locking the bootloader.
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset.
If you have a 16GB device, and it now shows up as 8GB, reboot into recovery (hold power and press volume up when you are at the screen with the android and the red exclamation mark), and wipe cache. If that still doesn't work, boot back into recovery and do a factory reset. Or do this
Click to expand...
Click to collapse
EddyOS said:
What happens if you extract the system.img file and flash it via fastboot manually?
fastboot flash system system.img
I always use this guide if I forget:
Click to expand...
Click to collapse
That's exactly what I have been doing, I prefer doing it manually as I don't like using Toolkits and finding a good one for mac is hard enough.
It just says that it cannot send it because the file or directory does not exist, yet if I unplug the phone it does go back into my old rom I was using before that, even though I flashed a new radio and recovery.img, boot.img, user data.img, everything except system.img as it doesn't work
Something clearly wrong with the partition but no idea what...
I know right, I've gone back to the ROM I had previously and downloaded the leaked 4.3 rom and flashed it through flashify. If it works I will simply lock the bootloader again and it should be good to go!
i did the same way through nexus tool kit 2.0 n p.s i guess the file was corrupted that y it failed in the mid. ill try it again
Hmmy 4444 said:
i did the same way through nexus tool kit 2.0 n p.s i guess the file was corrupted that y it failed in the mid. ill try it again
Click to expand...
Click to collapse
Let me know if you get anywhere with it!
it worked.. jst copy the image n dont rename it n go to google nexus 4 toolkit folder n there u would see a folder named *put googlr factory image here* paste it there n before starting ur bootloader must be unlocked.. so thats that.. after that that open the nexus 4 toolkit n then click on number 9 whch says download extract + flash google factore stock rom n then after that type 2 whch says flash google factory image... n thats it. it will automatically flash it.... gv me thanks too
Sent from my Nexus 4 using xda app-developers app
Hi there, same issue with me on a mac
Plus can you tell me how you went back to the previous rom, my phone is unusable right now and i do have a nandroid backup so.
Have either of your tried to flash the 4.2.2 factory image? Would be interested to see if it works
Sent from my Nexus 4 using xda premium
EddyOS said:
Have either of your tried to flash the 4.2.2 factory image? Would be interested to see if it works
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I dont mind, can you direct me towards a post where they show how to, i m not sure of all this and dont want to mess around with wrong files.
UPDATE: I tried and that works just fine. Rebooted to 4.2.1
N4 is broken, but I can use adb commands by going into recovery mode. I'd like to fully wipe the device and install the JWR66Y factory image (which is currently saved on my PC as a .tar file). I'm kind of an adb newb/idiot. I would greatly appreciate any guidance here.
Thanks!
Can you use fastboot to flash stock?
http://androidforums.com/android-sy...e-how-flash-nexus-factory-image-manually.html
Swyped from my Nexus 4 using Tapatalk 4
ddb540 said:
N4 is broken, but I can use adb commands by going into recovery mode. I'd like to fully wipe the device and install the JWR66Y factory image (which is currently saved on my PC as a .tar file). I'm kind of an adb newb/idiot. I would greatly appreciate any guidance here.
Thanks!
Click to expand...
Click to collapse
Hey you might want to look at the Google Nexus Toolkit. You can sideload a file if you already have a custom recovery installed.
http://forum.xda-developers.com/showthread.php?t=1995688
Good luck!
Lord Yurij said:
Can you use fastboot to flash stock?
http://androidforums.com/android-sy...e-how-flash-nexus-factory-image-manually.html
Swyped from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Thank you for the response. Was able to push the jwr66y image to the device using adb in recovery mode. Then, did the following:
fastboot boot boot.imdg
fastboot system jwr66y.imdg
fastboot erase userdata
fastboot erase cache
fastboot reboot
Now device is stuck in boot loop. Suggestions?
Thanks!
ddb540 said:
Thank you for the response. Was able to push the jwr66y image to the device using adb in recovery mode. Then, did the following:
fastboot boot boot.imdg
fastboot system jwr66y.imdg
fastboot erase userdata
fastboot erase cache
fastboot reboot
Now device is stuck in boot loop. Suggestions?
Thanks!
Click to expand...
Click to collapse
How did the command "fastboot system" even work?
When you flash an image, the command is the following:
Fastboot flash boot boot.img
Fastboot flash system system.img
Fastboot flash userdata userdata.img
Etc.
Anyways, you could have simply downloaded a rom, boot in recovery, use "adb push" to copy the file on your phone, then install it normally through your recovery.
abaaaabbbb63 said:
How did the command "fastboot system" even work?
When you flash an image, the command is the following:
Fastboot flash boot boot.img
Fastboot flash system system.img
Fastboot flash userdata userdata.img
Etc.
Anyways, you could have simply downloaded a rom, boot in recovery, use "adb push" to copy the file on your phone, then install it normally through your recovery.
Click to expand...
Click to collapse
Sorry, I typed incorrectly. Yes, I did fastboot flash system system.img, etc.
ddb540 said:
Thank you for the response. Was able to push the jwr66y image to the device using adb in recovery mode. Then, did the following:
fastboot boot boot.imdg
fastboot system jwr66y.imdg
fastboot erase userdata
fastboot erase cache
fastboot reboot
Now device is stuck in boot loop. Suggestions?
Thanks!
Click to expand...
Click to collapse
Try to go into recovery and wipe the caches and do a data factory reset, that will probably work.
Convert a tar.md5 file to .img
gee2012 said:
Try to go into recovery and wipe the caches and do a data factory reset, that will probably work.
Click to expand...
Click to collapse
Most flashable files come as a tar.md5 for use with odin. What do you do with a tar.md5 file if you want to flash it with adb? It appears that adb requires .img files.
My reason for wanting an .img file is that I tried flashing a stock recovery with odin and got an "MD5 Error, Binary is invalid". I have no idea what that means. I just figured I would try the adb approach since I need to learn adb anyway.
I would rather solve the "MD5 Error, Binary is invalid" error and proceed with odin. Since I am a noob, I don't know exactly how to proceed. Can anyone help me resolve this?
Thanks,
AHLASSICH said:
Most flashable files come as a tar.md5 for use with odin. What do you do with a tar.md5 file if you want to flash it with adb? It appears that adb requires .img files.
My reason for wanting an .img file is that I tried flashing a stock recovery with odin and got an "MD5 Error, Binary is invalid". I have no idea what that means. I just figured I would try the adb approach since I need to learn adb anyway.
I would rather solve the "MD5 Error, Binary is invalid" error and proceed with odin. Since I am a noob, I don't know exactly how to proceed. Can anyone help me resolve this?
Thanks,
Click to expand...
Click to collapse
Odin? That's for samsung mate. Won't work here. You need to download the factory images and extract it to get stock recovery. Or just head over to general section and there are thread for flashable stock recovery/modem/kernel. There is also a guide on how to use adb, a very detailed one at that. I'm sure you won't have trouble following it. Just read carefully and do it. All the things you need are given in that thread.
Edit: Guide - http://forum.xda-developers.com/showthread.php?t=2010312
AHLASSICH said:
Most flashable files come as a tar.md5 for use with odin. What do you do with a tar.md5 file if you want to flash it with adb? It appears that adb requires .img files.
My reason for wanting an .img file is that I tried flashing a stock recovery with odin and got an "MD5 Error, Binary is invalid". I have no idea what that means. I just figured I would try the adb approach since I need to learn adb anyway.
I would rather solve the "MD5 Error, Binary is invalid" error and proceed with odin. Since I am a noob, I don't know exactly how to proceed. Can anyone help me resolve this?
Thanks,
Click to expand...
Click to collapse
1. Make sure you have Android SDK installed. if not download here.
2. Download Nexus 4 factory rom from here.
3. Unzip the factory rom [occam-kot49h-factory]. If you dont know how to unzip. Download and install Winrar. Open the file with Winrar and Extract it somewhere in your computer.
4. Turn off your phone
3. Hold Volume up + Power; once it loads up to bootloader; connect it to your computer
5. The file [occam-kot49h-factory] you extract it early; in there you should see a file flash-all-bat. Open it [run it as admin if you are running Vista/7/8] and let it do its magic. Your phone will factory reset.
http://www.wugfresh.com/nrt/
go to this website, download the toolkit, and connect your nexus to computer on fastboot mode, do some few clicks, and boom, done
(SOLVED) Hello, today i decided to root my phone( Galaxy Grand Prime SM-G530F)using odin but i guess i used the wrong file. Odin said ''Restart'' and nothing happened, then i unplugged my phone. I wish I hadnt done this
When i try to turn my phone on, I only can see download mode and i guess it is called ''bootloop''. It says ''could not do normal boot''. I couldnt solve this problem using Odin because Odin doesnt see/recognise/find my phone. I checked the USB port drivers and my wire but i still cant fix the problem. Please help me, I am so desperate and cant afford a new phone :crying:
Does your Phone have fastboot and is your phone recognized by fastboot?
If yes Download your Firmware from sammobile.com (Registration needed) and unpack it
At this point I want to state, that I'm not Responible for any Hard- or Software-Damage. I'm just trying to help, because I think, that it can't get any worse
Windows:
Open up cmd as Administrator
Go into the Folder where fastboot is installed
Copy all the extracted .img files into the fastboot-folder
Run the following commands:
fastboot.exe flash boot boot.img
fastboot.exe flash recovery recovery.img
fastboot.exe flash system system.img
fastboot.exe flash data data.img
If there are any other img files than these four, or if one of those four didn't exist, you are free to ask
Linux:
Open up terminal as root (or use sudo before every command)
Go into the folder, where all the img files are stored
Run the following commands:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash data data.img
If there are any other img files than these four, or if one of those four didn't exist, you are free to ask
Sent from my SM-G350 using XDA-Developers mobile app
TimSchumi said:
Does your Phone have fastboot and is your phone recognized by fastboot?
If yes Download your Firmware from sammobile.com (Registration needed) and unpack it
At this point I want to state, that I'm not Responible for any Hard- or Software-Damage. I'm just trying to help, because I think, that it can't get any worse
Windows:
Open up cmd as Administrator
Go into the Folder where fastboot is installed
Copy all the extracted .img files into the fastboot-folder
Run the following commands:
fastboot.exe flash boot boot.img
fastboot.exe flash recovery recovery.img
fastboot.exe flash system system.img
fastboot.exe flash data data.img
If there are any other img files than these four, or if one of those four didn't exist, you are free to ask
Linux:
Open up terminal as root (or use sudo before every command)
Go into the folder, where all the img files are stored
Run the following commands:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash data data.img
If there are any other img files than these four, or if one of those four didn't exist, you are free to ask
Sent from my SM-G350 using XDA-Developers mobile app
Click to expand...
Click to collapse
Wot? Samsung phones don't have fastboot lol
Anyway try to remove the battery and enter ODIN mode normally, this should do it.
Oh, crap, i forgot
Sent from my SM-G350 using XDA-Developers mobile app
fabiossilva21 said:
Wot? Samsung phones don't have fastboot lol
Anyway try to remove the battery and enter ODIN mode normally, this should do it.
Click to expand...
Click to collapse
I tried to remove the battery but it didnt work
tunasdf said:
I tried to remove the battery but it didnt work
Click to expand...
Click to collapse
OMG IT WORKED AFTER TRYİNG THOUSAND TİMES thank you so much
tunasdf said:
OMG IT WORKED AFTER TRYİNG THOUSAND TİMES thank you so much
Click to expand...
Click to collapse
No problem! Glad you managed to fix it! Now remember to flash the right file
Hi,
I made this post/thread because i couldn't find a solution to my problem through this forum and google.
Here is my trouble:
I was trying to install a twrp recovery and was following the instructions of a tutorial.
-So first i installed flashify and proceeded to a back up of the current kernel and current recovery
-Then downloaded a custom recovery image through TWRP release for my nexus 4
-After this i accidentally flashed the recovery image to boot instead of recovery
Now as you can guess the trouble is that my phone only boots to TWRP recovery instead of usual boot.
I tried to find aswers on this forum and google and yet i didn't find a solution.
I tried this post but without results:
http://forum.xda-developers.com/tmobile-lg-g3/general/fix-recovery-loop-twrp-computer-t2873386
I would be grateful for any help and wish to recover this mistake without using a factory reset if possible.
Thank you, as you can see i am pretty new to this environment.
Can you get into fastboot mode? If yes, try flashing a stock Google rom and perform a factory wipe after installing the stock rom.
audit13 said:
Can you get into fastboot mode? If yes, try flashing a stock Google rom and perform a factory wipe after installing the stock rom.
Click to expand...
Click to collapse
Thank you for your answer, yes i can get into fastboost mode. As i am pretty new can you explain me how i can flash the stock Google rom (i guess it is the factory rom provided ?). Will this operation erase my data on the phone ?
Boot into fastboot and flash boot.img and recovery.img file from stock rom. Make sure you use the stock rom that matches the rom currently installed on your phone.
Ilovkos said:
Thank you for your answer, yes i can get into fastboost mode. As i am pretty new can you explain me how i can flash the stock Google rom (i guess it is the factory rom provided ?). Will this operation erase my data on the phone ?
Click to expand...
Click to collapse
Once in fastboot, extract the downloaded zip you got from Google. There you will find flash-all.bat Execute it as admin and wait. If it doesn't work, then extract the zip within the first zip and you should get loads of .img files. You will manually have to flash them. The commands are a bit different for each partition. They go like this:
Code:
fastboot flash system system.img
fastboot flash recovery recovery. img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash data userdata.img
Note that if your cmd/terminal isn't open from the directory where the files are you will have to input it's location, for example
Code:
fastboot flash recovery C:\Users\YOURUSER\Desktop\recovery.img
Also note that there must be no spaces neither in the file name or the directories where the file is located, otherwise it probably won't flash.
Also yes, doing this will completely revert you to stock, and you WILL loose all your data. You could try just reflashing recovery.img and then flashing TWRP over it. If you can get to TWRP after this, then connect the USB cable to your PC and transfer all the data you need, after which I recommend flashing to stock. You can root and/or flash custom ROMs after this.
However in your case I think you don't have to completely go back to stock. Just try flashing the proper boot and recovery images over fastboot like I explained above and try booting then.
nerotNS said:
Once in fastboot, extract the downloaded zip you got from Google. There you will find flash-all.bat Execute it as admin and wait. If it doesn't work, then extract the zip within the first zip and you should get loads of .img files. You will manually have to flash them. The commands are a bit different for each partition. They go like this:
Code:
fastboot flash system system.img
fastboot flash recovery recovery. img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash data userdata.img
Note that if your cmd/terminal isn't open from the directory where the files are you will have to input it's location, for example
Code:
fastboot flash recovery C:\Users\YOURUSER\Desktop\recovery.img
Also note that there must be no spaces neither in the file name or the directories where the file is located, otherwise it probably won't flash.
Also yes, doing this will completely revert you to stock, and you WILL loose all your data. You could try just reflashing recovery.img and then flashing TWRP over it. If you can get to TWRP after this, then connect the USB cable to your PC and transfer all the data you need, after which I recommend flashing to stock. You can root and/or flash custom ROMs after this.
However in your case I think you don't have to completely go back to stock. Just try flashing the proper boot and recovery images over fastboot like I explained above and try booting then.
Click to expand...
Click to collapse
Thanks to both of you I managed to fix this just by flashing the boot.img of the Google factory img. It didn't erase my data except my messages which is nice.
I accidentally wiped off everything with TWRP.
I have no backups.
I'm really having trouble finding ANY rom for this phone,custom or stock.
I've only found firmware that can update my OS not install it completely.
Could anyone find the correct ROM for me?
Anything will do.
Please help!
If you have a second device, donwload Huawei firmware finder from Play store. Enter your model number and donwload a full package. Doesn't really matter which one. Then just flash it in TWRP without extracting.
Vinnipinni said:
If you have a second device, donwload Huawei firmware finder from Play store. Enter your model number and donwload a full package. Doesn't really matter which one. Then just flash it in TWRP without extracting.
Click to expand...
Click to collapse
Is there any way to know my exact phone model number without having access to the OS?
Using the pc version I have to enter some kind of G and F values,what should i put in there?
EDIT:I've narrowed it down to WAS-LX1 and WAS LX1A,any way of distinguishing between those?
EDIT 2 : I seem to fail to flash literally any ROM,I get a zip verification error if i try to check that,if not I just get:
Updater process edned with ERROR : 9,and E: unknown command [errno] before that
Justkill43 said:
Is there any way to know my exact phone model number without having access to the OS?
Using the pc version I have to enter some kind of G and F values,what should i put in there?
EDIT:I've narrowed it down to WAS-LX1 and WAS LX1A,any way of distinguishing between those?
Click to expand...
Click to collapse
Shouldn't your phone model number be beneath the battery?
Michael24884 said:
Shouldn't your phone model number be beneath the battery?
Click to expand...
Click to collapse
Well yeah,it should.
But this is one of those phones that can't really be opened with special tools that I don't really have,and even if i did have them I wouldn't mess with the phone's insides because it's one of those types of phone....
Update:It may have something to do with the roms i have downloaded,I've tried 3 of them and none of them had ANY .img files
No boot.img no recovery.img etc,what am I doing wrong?
Justkill43 said:
Update:It may have something to do with the roms i have downloaded,I've tried 3 of them and none of them had ANY .img files
No boot.img no recovery.img etc,what am I doing wrong?
Click to expand...
Click to collapse
Huawei uses some special archiving, there should be an UPDATE.APP inside the downloaded files. You need a tool called Huawei Update Extractor to get the .img files.
Vinnipinni said:
Huawei uses some special archiving, there should be an UPDATE.APP inside the downloaded files. You need a tool called Huawei Update Extractor to get the .img files.
Click to expand...
Click to collapse
Oh I see,and should I just get the .imgs out of the update.app and then flash the rom?
Because so far I can't flash any of them,I get these errors:
E: unknown command [errno]
And
Updater process ended with ERROR : 9
Justkill43 said:
Oh I see,and should I just get the .imgs out of the update.app and then flash the rom?
Because so far I can't flash any of them,I get these errors:
E: unknown command [errno]
And
Updater process ended with ERROR : 9
Click to expand...
Click to collapse
What did you type?
Ohh and where are you from?
Vinnipinni said:
What did you type?
Ohh and where are you from?
Click to expand...
Click to collapse
What did i type??
Serbia.
Justkill43 said:
What did i type??
Serbia.
Click to expand...
Click to collapse
Yeah, mean the fastboot command you used
Vinnipinni said:
Yeah, mean the fastboot command you used
Click to expand...
Click to collapse
Kinda confused now,as I don't think I've used any fastboot commands at all.
Justkill43 said:
Kinda confused now,as I don't think I've used any fastboot commands at all.
Click to expand...
Click to collapse
If you want to flash the .img files, you have to enter your Bootloader. Do this by booting TWRP and type adb reboot bootloader. Then, out the .img files into the adb/ fastboot folder and type
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cust cust.img
Instead of system.img you need to use the exact filename of the system.img file. I think you need to only use these three commands, but I'll have another look.
Edit: you could also replace your current recovery and then try to flash the update file with the stock recovery. Do this by typing fastboot flash recovery recovery.img
Vinnipinni said:
If you want to flash the .img files, you have to enter your Bootloader. Do this by booting TWRP and type adb reboot bootloader. Then, out the .img files into the adb/ fastboot folder and type
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cust cust.img
Instead of system.img you need to use the exact filename of the system.img file. I think you need to only use these three commands, but I'll have another look.
Edit: you could also replace your current recovery and then try to flash the update file with the stock recovery. Do this by typing fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Oh so I should just flash those 3 imgs instead of the whole zip?
Also there is no cust.img
I'll list all the imgs here so you can see what i should be able to flash:
-Boot
-Crc.img
-Curver.img
-DTS.img
-EFI.img
-FASTBOOT.img
-FW_HIFI.img
-FW_LPM3.img
-MODEM_FW.img
-PACKAGE_TYPE.img
-PRODUCT.img
-RECOVERY.img
-RECOVERY2.img
-SENSORHUNB.img
-SHA256RSA.img
-SYSTEM.img
-TEEOS.img
-TRUSTFIRMWARE.img
-VENDOR.img
-VERLIST.img
-XLOADER.img
Justkill43 said:
Oh so I should just flash those 3 imgs instead of the whole zip?
Also there is no cust.img
I'll list all the imgs here so you can see what i should be able to flash:
-Boot
-Crc.img
-Curver.img
-DTS.img
-EFI.img
-FASTBOOT.img
-FW_HIFI.img
-FW_LPM3.img
-MODEM_FW.img
-PACKAGE_TYPE.img
-PRODUCT.img
-RECOVERY.img
-RECOVERY2.img
-SENSORHUNB.img
-SHA256RSA.img
-SYSTEM.img
-TEEOS.img
-TRUSTFIRMWARE.img
-VENDOR.img
-VERLIST.img
-XLOADER.img
Click to expand...
Click to collapse
Yes! You can't flash most of it, it's not possible.
Flash Boot, Recovery, System and Vendor. Of that doesn't work, Put the UPDATE.APP into the dload folder on your SD and hold Power, Volume + and Volume -. That should force the flash of the update.
And if that still doesn't work, ask for a TWRP update on the P10 Forums. Then Restore everything except Data.
Vinnipinni said:
If you want to flash the .img files, you have to enter your Bootloader. Do this by booting TWRP and type adb reboot bootloader. Then, out the .img files into the adb/ fastboot folder and type
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cust cust.img
Instead of system.img you need to use the exact filename of the system.img file. I think you need to only use these three commands, but I'll have another look.
Edit: you could also replace your current recovery and then try to flash the update file with the stock recovery. Do this by typing fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Alright,I'm getting the hang of this.
But what did you mean with the exact filename of system.img?How do i find that out?
Justkill43 said:
Alright,I'm getting the hang of this.
But what did you mean with the exact filename of system.img?How do i find that out?
Click to expand...
Click to collapse
Just the name of the file. Don't know if it's sytsem.img or SYSTEM.IMG
Vinnipinni said:
Just the name of the file. Don't know if it's sytsem.img or SYSTEM.IMG
Click to expand...
Click to collapse
Got it,flashed system,recovery and boot
Trying to flash vendor I get an error when it's trying to write vendor:
FAILED (remote:Command not allowed)
Still stuck in a boot loop.
I'm gonna put the update.app in the sdcard.
I just create a dload folder in the sd card,put it in,wipe off everything I've flashed and do the 3 button thing,right?
Vinnipinni said:
Just the name of the file. Don't know if it's sytsem.img or SYSTEM.IMG
Click to expand...
Click to collapse
UPDATE: Failed the 3 button thing,maybe I got the wrong ROM,i'll try it with another one,I have a question though
My friend has the same phone as me(p10 lite) and when he goes to about phone and checks out the model number he only sees WAS-LX1
I'm pretty sure i have that same model number now but I can't find a ROM that's specifically WAS-LX1,it's always WAS-LX1 And something added on there like WAS-LX1C02,should I even worry about that?
Vinnipinni said:
Yes! You can't flash most of it, it's not possible.
Flash Boot, Recovery, System and Vendor. Of that doesn't work, Put the UPDATE.APP into the dload folder on your SD and hold Power, Volume + and Volume -. That should force the flash of the update.
And if that still doesn't work, ask for a TWRP update on the P10 Forums. Then Restore everything except Data.
Click to expand...
Click to collapse
After trying the first 2 methods I can't even boot into twrp anymore,I'm super screwed...