[FIRMWARE] Stock AT&T 1.32.502.31 RUU - One (M9) General

Directly from the HTC Website:
http://www.htc.com/us/support/htc-one-m9-att/news/
PLEASE BE SURE TO READ THE POST FIRST. THIS FIRMWARE WILL WIPE YOUR PHONE.
Direct link to download full RUU file here:
http://dl3.htc.com/application/RUU_...21_62.05.50320G_F_release_426950_signed_2.exe
UPDATE 4/23/15
Converted firmware update files in .zip format for other platforms courtesy of clsA to be found in post 7
clsA said:
RUU_HIMA_UL_L50_SENSE70_ATT_Cingular_US_1.32.502.3 1.rom.zip
htc_fastboot.exe >> https://www.androidfilehost.com/?fid=96042739161891970
fastboot-mac.zip >> https://www.androidfilehost.com/?fid=96042739161891971
I have not tested the fastboot-mac so I'm not sure it works with the above Ruu or not
Flash with
htc_fastboot oem rebootRUU
htc_fastboot flash zip RUU.zip
htc_fastboot flash zip RUU.zip <this may not be needed it might restart on it's own>
htc_fastboot reboot
Click to expand...
Click to collapse

I can confirm that the RUU downloaded from the HTC site (link above) at 2.1G works correctly.
You will NOT lose Unlock or S-off if you have done so already. However, the process WILL wipe your system, so you will need to reinstall TWRP 2.8.6.4 (unofficial), SuperSU beta and any custom ROM you want.
Have at it!

BillTheCat said:
I can confirm that the RUU downloaded from the HTC site (link above) at 2.1G works correctly.
You will NOT lose Unlock or S-off if you have done so already. However, the process WILL wipe your system, so you will need to reinstall TWRP 2.8.6.4 (unofficial), SuperSU beta and any custom ROM you want.
Have at it!
Click to expand...
Click to collapse
Hey, so right now I'm still running Sense. I understand that this will remove root and the custom recovery but will this also reset the device back to factory default settings and data? I know, dumb question, but I just want to make sure I'm able to keep all my messages, apps, data, ect. If not, then I'll just make a backup with HTC sync manager.
Thanks

anbrine said:
I just want to make sure I'm able to keep all my messages, apps, data, ect. If not, then I'll just make a backup with HTC sync manager.
Click to expand...
Click to collapse
Nope. They'll get blown away. You should ALWAYS have a backup saved to your PC.

BillTheCat said:
Directly from the HTC Website:
http://www.htc.com/us/support/htc-one-m9-att/news/
PLEASE BE SURE TO READ THE POST FIRST. THIS FIRMWARE WILL WIPE YOUR PHONE.
Direct link to download file here:
http://dl3.htc.com/application/RUU_...21_62.05.50320G_F_release_426950_signed_2.exe
Click to expand...
Click to collapse
are you going to upload the rom.zip from the RUU and the htc_fastboot for MAC and Linux users ? If not I'll add them to my thread

clsA said:
are you going to upload the rom.zip from the RUU and the htc_fastboot for MAC and Linux users ? If not I'll add them to my thread
Click to expand...
Click to collapse
I have no clue how to do that. I was hoping someone else would. If you're able, I'll NE happy to update my op with the corresponding links.

BillTheCat said:
I have no clue how to do that. I was hoping someone else would. If you're able, I'll NE happy to update my op with the corresponding links.
Click to expand...
Click to collapse
I'm uploading them now ..I'll post here
RUU_HIMA_UL_L50_SENSE70_ATT_Cingular_US_1.32.502.31.rom.zip
htc_fastboot.exe >> https://www.androidfilehost.com/?fid=96042739161891970
fastboot-mac.zip >> https://www.androidfilehost.com/?fid=96042739161891971
I have not tested the fastboot-mac so I'm not sure it works with the above Ruu or not
Flash with
htc_fastboot oem rebootRUU
htc_fastboot flash zip RUU.zip
htc_fastboot flash zip RUU.zip <this may not be needed it might restart on it's own>
htc_fastboot reboot
The other method to flash is to rename the RUU.zip to 0PJAIMG.zip and copy it to a fat32 sdcard and flash it in download mode

clsA said:
I'm uploading them now ..I'll post here
Click to expand...
Click to collapse
Works for me, or you could pm the links and I'll credit you in the 1st post.

Anyone has instruction to decrypt the ROM.zip on windows ?

yardi4life said:
Anyone has instruction to decrypt the ROM.zip on windows ?
Click to expand...
Click to collapse
sure do >> http://forum.xda-developers.com/one-m9/development/dev-how-to-extract-one-m9-rom-dump-image-t3062808

Stuck with 155 errors on the .exe RUU Utility from HTC. clsA, i tried the manual update using htc_fastboot zip RUU.zip and getting a FAILdata too large error.
Now I'm stuck locked and can't update or unlock my current version. Any ideas?

gnomish said:
Stuck with 155 errors on the .exe RUU Utility from HTC. clsA, i tried the manual update using htc_fastboot zip RUU.zip and getting a FAILdata too large error.
Now I'm stuck locked and can't update or unlock my current version. Any ideas?
Click to expand...
Click to collapse
are you sure you are doing it right and using htc_fastboot? Make sure you are not using fastboot or any mac ver of fastboot. You must be in download mode
htc_fastboot.exe oem rebootRUU
htc_fastboot.exe flash zip ruu.zip
htc_fastboot.exe flash zip ruu.zip
htc_fastboot.exe reboot
I have confirmed this working on my at&t m9
or if you have a 32gig or smaller sd card, rename file to 0PJAIMG.ZIP and put it in the root of your sd card and go to download mode, MUST be formatted in fat32 from a computer first.
btw for the op, I have confirmed the fastboot-mac nor fastboot for mac work with this. They have to be decrypted in order for it to work with plain old mac fastboot. It was like this on m7 and m8 too. wish someone would port the htc_fastboot to mac then I could take off this darn parallels

Yes, unfortunately can confirm I followed the above steps and am using htc_fastboot.exe. I continue to get the same error below.
I will continue trying as I don't have a small enough sd card for the other method.
C:\adb>htc_fastboot.exe flash zip ruu.zip
sending 'zip'... (2141801 KB) FAILdata too large, 2193204239 > 1430073344
FAILED (data size is too large(2141801 KB) for device to download ZIP file 'ruu.
zip'
Click to expand...
Click to collapse

gnomish said:
Yes, unfortunately can confirm I followed the above steps and am using htc_fastboot.exe. I continue to get the same error below.
I will continue trying as I don't have a small enough sd card for the other method.
Click to expand...
Click to collapse
This is the htc_fastboot from the AT&T RUU
https://www.androidfilehost.com/?fid=96042739161891970
If you using a different one try that one
Are you md5 checking your download ? are you starting the flash in download mode (black screen not the white bootloader)
try it without the htc_fastboot oem rebootRUU
just boot to download mode and flash it
fastboot flash zip RUU.zip
if the phone reboots during the process hold volume down to enter download mode again and let it finish

Related

[Q] HTC Magic 32A (No recovery only flash mode enabled almost bricked)

Hi,
I almost killed my HTC Magic when trying to upgrade it, Its locked with loop boot unable to enter recovery mode all i can do is just to get into fastboot mode
Help me to completely wash out the remaining stuff and write an new ROM to Magic
through flash boot i believe my usb drivers are detected in flash boot
Pls walk me through
Help me thx!!!!!!
You should go to fastboot and flash another recovery and then you can go to recovery.
hanntbk said:
You should go to fastboot and flash another recovery and then you can go to recovery.
Click to expand...
Click to collapse
Thanks for your support
It will be great if you can provide me the files required & tutorial it will be really helpfull
vijay2network said:
Thanks for your support
It will be great if you can provide me the files required & tutorial it will be really helpfull
Click to expand...
Click to collapse
Here: http://forum.xda-developers.com/showthread.php?t=1059911
this is the tutorial and files to flash recovery
danger_tweaker said:
Here: http://forum.xda-developers.com/showthread.php?t=1059911
this is the tutorial and files to flash recovery
Click to expand...
Click to collapse
Hey I'm seriously noob when its coming to HTC.
I dnt even know how fast boot mode works, If you can guide me through brief tutorial that should help me
Seriously dnt understand that tutorial, All i have done is boot phone to flash boot mode and waited PC to detect it, I dnt know what exactly should i do after connecting it
First open CMD.exe (command/ black box)
type cd and the go to were the files are located so if you put them in the map android on your c: drive it's cd c:\android
then connect your phone and copy/paste the codes from that post.
PowerPlop said:
First open CMD.exe (command/ black box)
type cd and the go to were the files are located so if you put them in the map android on your c: drive it's cd c:\android
then connect your phone and copy/paste the codes from that post.
Click to expand...
Click to collapse
Hey thanks for the quick post
I'm also wondering all the post abt flasboot has some tools like "SDK" "adb"
Do i need similar tools to proceed with this ??!!
Follow this tutorial to install what you need.
It's for installing ADB and Fastboot.
PowerPlop said:
Follow this tutorial to install what you need.
It's for installing ADB and Fastboot.
Click to expand...
Click to collapse
Do i need to install adb or flashboot to work on this scenario?
If anyone can guide me remotely it would be great.
vijay2network said:
Do i need to install adb or flashboot to work on this scenario?
If anyone can guide me remotely it would be great.
Click to expand...
Click to collapse
of course, guidance it already exists on the link provided by PowerPlop
I tried to flash the CWM recovery from my PC through CLI, Below is the error poped when i tried to boot or flash from image
C:\Downloads\Browser Download>fastboot boot recovery-clockwork-3.0.2.8-bravo.img
downloading 'boot.img'... FAILED (remote: not allow)
finished. total time: 0.002s
C:\Downloads\Browser Download>fastboot flash recovery-clockwork-3.0.2.8-bravo.im
g
unknown partition 'recovery-clockwork-3.0.2.8-bravo.img'
error: cannot determine image filename for 'recovery-clockwork-3.0.2.8-bravo.img
I tried downloading recovery img from "http://forum.xda-developers.com/showthread.php?t=1059911" thread but the link has expired
Hence i download this image from 4shared, Not sure this is the correct rom or not.
Help me after this
This happened because you flashed bravo recovery and not the 32a recovery.
follow the link provided by danger_tweaker post no. 4
everything is properly explained in and download your recovery "carz-clockworkmod-3.0.2.8-recovery.zip" only or if you are able to turn on device then download ROM Manager and flash recovery because htc magic are legacy(old,outdated) devices so file are removed from most of the sites.
BTW have you ever flashed the recovery???
I had searched for your recovery but all links are expired. View attachment 1161540 See if this recovery works for you. I had downloaded it long back and currently I don't have any previous version of carz mod :angel:, neither I remember its source link . It is the same clockwork mod-carz-recovery only version is different v4.0.1.4 see if it flashes through fastboot :fingers-crossed:.
vijay2network said:
C:\Downloads\Browser Download>fastboot flash recovery-clockwork-3.0.2.8-bravo.im
g
unknown partition 'recovery-clockwork-3.0.2.8-bravo.img'
error: cannot determine image filename for 'recovery-clockwork-3.0.2.8-bravo.img
Click to expand...
Click to collapse
That's not working because your command is wrong, you forgot one "recovery". He's telling you that there is no partition named "recovery-clockwork-3.0.2.8-bravo.img" because the correct name is "recovery". The correct command would be
Code:
fastboot flash [COLOR="Red"]recovery[/COLOR] recovery-clockwork-3.0.2.8-bravo.img
But i think you'll also get "FAILED (remote: not allow)".
I think you need to tell us what's written in your fastboot screen on the phone. Also a
Code:
fastboot getvar version-main
would be helpful.
C:\Android>fastboot flash recovery clockwork-3.0.2.8.img
sending 'recovery' (3806 KB)... FAILED (remote: not allow)
finished. total time: 0.001s
C:\Android>fastboot getvar version-main
version-main: 3.05.720.3
finished. total time: 0.002s
As u said i got the same error
I worked on gold card mode and try updating using "sappimg.zip"
I get "Incorrect CID" as error even after me making an exact gold card asper the tutorial @ http://wiki.cyanogenmod.com/wiki/Howto:_Create_a_Goldcard
Help me ASAP
You get this error "FAILED (remote: not allow)" because of your SPL-version - it seems to be a perfect one, you can't flash your phone with commandline.
Show us what's written in your fastboot-menu (everything, radio, hboot and so on, everything you can see).
Also give us the output of
Code:
fastboot getvar cid
please.
When did you get this error "Incorrect CID"?
Do you have some other Android-phone? Then create your Goldcard with GoldCardTool (for example as explained here).
Which sappimg.zip did you try? Don't just take one without knowing if you can take it!
1. Output for command
C:\Android>fastboot getvar cid
cid: HTC__038♦
finished. total time: 0.001s
2. Attached the screen shot of HBoot & Fastboot mode
3. I have an S2 i managed to fetch the CID using SimpleGoldCard_v1.zip from http://dl.xda-developers.com/attach...d6/4ff07379/5/2/8/8/9/6/SimpleGoldCard_v1.zip
4. I slected mmc1 in the tool to detect my MMC CID to be changed to gold card
5. I used ROM v2.16.707.3 (NON-Perfected stock SPL v1.33.0009 from this http://forum.xda-developers.com/showthread.php?t=548218
I believe i have provide u all information i have got. Please provide me support ASAP :highfive:
Snapshots
http://www.image-share.com/ijpg-1592-111.html
http://www.image-share.com/ijpg-1592-112.html
http://www.image-share.com/ijpg-1592-113.html
I can't open the screenshots you attached, sorry.
edit: You posted while i did - ok!
---------- Post added at 04:15 PM ---------- Previous post was at 03:52 PM ----------
As i said, because of the SPL-version you can't flash with commandline. You have to use sappimg.zip or nbh. To flash those, the rom needs to have a higher version than the installed one.
Your main-version is 3.05.720.3, as you see here a higher version would be "3.05.861.2 Hutchinson Australia". To flash this you need the Goldcard - it lets you install roms of different providers.
Download that rom, copy it to your SD-card (Goldcard) and rename it to SAPPIMG.zip and try to flash it. If it still tells you "CID incorrect" your Goldcard isn't created correct or the SD-card doesn't work as Goldcard.
If you finished this we're going on. Just short:
When you're done your phone should boot the normal way. Now you need to get the correct rom for your CID on it - 39) 3.05.720.3 1.76.0009H 6.35.08.29 N HTC__038 is for your phone, it's that one 3.05.720.3 India.
You can't flash this as sappimg.zip because the version of this rom is lower than the installed one. You need to install a custom-recovery on your phone to be able to install any rom-version - to install this you need to root your phone (there are some tutorials on XDA). With the custom-recovery you're going to install the stock-rom and you're done. If you like to you can also install custom-roms on your phone - you just need to install a custom-recovery again to install that.
I'm not an expert - i just know what i read and experienced when i debricked my HTC magic. If somebody thinks i'm wrong with my suggestions, just tell! :laugh:
matzehtc said:
I can't open the screenshots you attached, sorry.
edit: You posted while i did - ok!
---------- Post added at 04:15 PM ---------- Previous post was at 03:52 PM ----------
As i said, because of the SPL-version you can't flash with commandline. You have to use sappimg.zip or nbh. To flash those, the rom needs to have a higher version than the installed one.
Your main-version is 3.05.720.3, as you see here a higher version would be "3.05.861.2 Hutchinson Australia". To flash this you need the Goldcard - it lets you install roms of different providers.
Download that rom, copy it to your SD-card (Goldcard) and rename it to SAPPIMG.zip and try to flash it. If it still tells you "CID incorrect" your Goldcard isn't created correct or the SD-card doesn't work as Goldcard.
If you finished this we're going on. Just short:
When you're done your phone should boot the normal way. Now you need to get the correct rom for your CID on it - 39) 3.05.720.3 1.76.0009H 6.35.08.29 N HTC__038 is for your phone, it's that one 3.05.720.3 India.
You can't flash this as sappimg.zip because the version of this rom is lower than the installed one. You need to install a custom-recovery on your phone to be able to install any rom-version - to install this you need to root your phone (there are some tutorials on XDA). With the custom-recovery you're going to install the stock-rom and you're done. If you like to you can also install custom-roms on your phone - you just need to install a custom-recovery again to install that.
I'm not an expert - i just know what i read and experienced when i debricked my HTC magic. If somebody thinks i'm wrong with my suggestions, just tell! :laugh:
Click to expand...
Click to collapse
Hi thx for ur quick reponse, The latest image what u said "3.05.861.2 Hutchinson Australia" is in ".exe" format
how do i proceed with it :-/

HTC Magic - half bricked - RUU USB

Hello,
can anyone suggest how to recover HTC magic after flashing Rogers RUU official over custom rom.
ROM update was aborted on updating system partition.
Problem is that I can't upload any part of rom because phone is now S-ON. I'am getting signature error.
Flashed RUU: 42) [xda-ftp] [4shared] 3.54.631.3 Rogers Canada + [SAPPIMG.ZIP format]
ADB is no longer possible. Only FASTBOOT and RUU USB.
See attched photo for fastboot details.
Thanks in advance.
pero256 said:
Hello,
can anyone suggest how to recover HTC magic after flashing Rogers RUU official over custom rom.
ROM update was aborted on updating system partition.
Problem is that I can't upload any part of rom because phone is now S-ON. I'am getting signature error.
Flashed RUU: 42) [xda-ftp] [4shared] 3.54.631.3 Rogers Canada + [SAPPIMG.ZIP format]
ADB is no longer possible. Only FASTBOOT and RUU USB.
See attched photo for fastboot details.
Thanks in advance.
Click to expand...
Click to collapse
I went through a similar problem. My 32A was in the same state except for the radio; I had no system installed, S-ON, RUU mode, and a radio/spl mismatch. It looks like you at least have a proper radio/spl combo.
Before we do anything else, try flashing the RUU again. Were you using the ZIP file or the EXE? Use the ZIP, at least you won't have to load up that crappy HTC interface.
If the RUU fails again, see if you can find the log file from the installation. It'll be on your system's drive, probably in "C:\ruu_log" or something like that. It can tell us what error it found.
In my case, we (mumilover and I) had to upgrade HBOOT and "sort of unlock it" using HTCDEV's method. Then we were able to install a custom recovery, and then everything got very easy.
Let's see if the simple things work before we have to do the harder things
Thnak you very much for hint with HTCDEV. Now I have at least fastboot
RUU image allways fail at signature error. OI have tried three of them. Same error.
I have run RUU under fastboot usb.
Also I can't flash recovery image even I have successfully unlocked hboot with htcdev.
C:\ADB>fastboot flash recovery recovery-clockwork-2.5.0.7-magic.img
sending 'recovery' (2642 KB)... OKAY [ 0.923s]
writing 'recovery'... FAILED (remote: not allow)
finished. total time: 0.926s
Any other idea ?
pero256 said:
Thnak you very much for hint with HTCDEV. Now I have at least fastboot
RUU image allways fail at signature error. OI have tried three of them. Same error.
I have run RUU under fastboot usb.
Also I can't flash recovery image even I have successfully unlocked hboot with htcdev.
C:\ADB>fastboot flash recovery recovery-clockwork-2.5.0.7-magic.img
sending 'recovery' (2642 KB)... OKAY [ 0.923s]
writing 'recovery'... FAILED (remote: not allow)
finished. total time: 0.926s
Any other idea ?
Click to expand...
Click to collapse
Could you give me the new details of the fastboot page? Your HBOOT version will have changed, and it will say "UNLOCKED" or "RELOCKED" at the top and S-ON. If it says "RELOCKED", try running the HTCDEV unlock command from fastboot again (you should still have the Unlock_code.bin file in your email) and then reboot.
Let's see how that goes.
DasBub said:
Could you give me the new details of the fastboot page? Your HBOOT version will have changed, and it will say "UNLOCKED" or "RELOCKED" at the top and S-ON. If it says "RELOCKED", try running the HTCDEV unlock command from fastboot again (you should still have the Unlock_code.bin file in your email) and then reboot.
Let's see how that goes.
Click to expand...
Click to collapse
I have attached Fastboot details.Status is: UNLOCKED.
But when I try to flash recovery I get an error message which I already wrote.
I think it is because of S-ON which is checking signature.
pero256 said:
I have attached Fastboot details.Status is: UNLOCKED.
But when I try to flash recovery I get an error message which I already wrote.
I think it is because of S-ON which is checking signature.
Click to expand...
Click to collapse
Sounds reasonable. I wish I kept better notes That way I wouldn't have to re-learn things every time.
I just want to make sure I understand the timeline of events:
You said you tried to flash an RUU over an existing custom ROM install, right?
What was the configuration of your phone before you tried the RUU and ran into trouble? If you were running a custom ROM, did you have a magic SPL or a custom recovery in order to install that custom ROM?
Anyway, on to the work:
Let's see if we can get an RUU to work now.
Go to the command prompt and run "fastboot getvar version-main" and let us know what it is, for future reference.
Once we know that, we can find a higher-numbered RUU from this list of Official RUUs.
I think I ended up using BrightStar Brazil, but anything higher than your phone's reported main version should work.
Have you made a goldcard? If you try to use an RUU and it complains about your CID, this will help.
Before you try to install an RUU, you will need to relock the bootloader using "fastboot oem lock" (you'll be able to unlock it again using the Unlock_token.bin)
Place the SAPPIMG.zip of the RUU in the root folder of your SD card and reboot into HBOOT (or reboot to fastboot and select HBOOT).
After a few seconds it should start scanning your SD card and then it will try to use the SAPPIMG.
Let us know.
Yes I had custom rom with s-off. But can't remeber which version.
Than I tried to install RUU: 42) [xda-ftp] [4shared] 3.54.631.3 Rogers Canada + [SAPPIMG.ZIP format]
Than I get error while flashing.
Strange thing is that I get this now:
C:\ADB>fastboot getvar version-main
version-main: 3.54.0.0
finished. total time: 0.001s
So it seems that I have lower version than I tried to install
I didn't try to use goldcard for now.
I have created Gold Card using this link: http://theunlockr.com/2010/03/10/how-to-create-a-goldcard/
I have to use another HTC phone (Wildfire) to get CID from HTC Magic SD card
I have tried to put 3.54.631.3 Rogers Canada rom as SAPPIMG.zip but HBOOT claims that there is no image.
I get: Loading...(SAPPIMG.zip) No image!
I forget to say that I have set HBOOT to RELOCKED state before using GOLD CARD and SAPPIMG.zip
pero256 said:
I forget to say that I have set HBOOT to RELOCKED state before using GOLD CARD and SAPPIMG.zip
Click to expand...
Click to collapse
1) Check the filename. Make sure it is "SAPPIMG.zip" exactly, with SAPPIMG in capital letters.
2) Run these fastboot commands and then switch back to HBOOT mode.
Code:
fastboot oem enableqxdm 0
fastboot oem eraseconfig
This procedure has fixed SD card problems in the past.
3) Check the SD card using a computer or another phone to be sure that the file is on the card. I've had Windows unmount the card improperly a few times, so that's a possibility.
4) Compare a checksum of the original ZIP file to the checksum of the ZIP on your SD card. I use 7-Zip to get the checksum, but there are other ways.
5) You can download another copy of the SAPPIMG.zip file.
It also helps to wave a dead chicken over the phone as an offering to the phone god.
Unfortuntly can't get goldcard to work.
I have used 3 different SD card.
1. 2GB
2. 2GB
3. 1GB
Non of them works.
Also everything is fine in the process of creating them.
Problem is about loading to phone SAPPIMG.zip of 3.54.631.3 Rogers Canada rom.
Phone starts to Checking..(SAPPIMG.zip) and then after some period of time stops and waits to press:
1. (back) FastBoot Mode
2. (send) Simlock
I have try to start another flash but get the same result.
So it seems that the gold card is not working as it should because phone is still checking uploaded rom image.
Is there some SD card that works 100% ?
pero256 said:
你好,
任何人都可以建议如何在通过自定义 rom 刷新 Rogers RUU 官方后恢复 HTC 魔法。
ROM 更新在更新系统分区时中止。
问题是我无法上传 rom 的任何部分,因为手机现在是 S-ON。我收到签名错误。
闪烁的 RUU:42) [xda-ftp] [4shared] 3.54.631.3 Rogers Canada + [SAPPIMG.ZIP 格式]
亚行不再可能。只有 FASTBOOT 和 RUU USB。
有关快速启动的详细信息,请参阅随附的照片。
提前致谢。
Click to expand...
Click to collapse
You use what method to let it enter FASTBOOT

how to recover?

Since I lost everything from the boot to the recovery to the system part to anything, i haven't been able to boot the phone;
I can access erecovery but when I try to recover the phone it stops at downloading and then says couldn't connect to servers so that's dead;
I can access TWRP but when I try to flash MM, it returns errors saying that it couldn't mount partitions (Vendor, cust and other...)
I can access fastboot mode. Some people suggested that I should try recovering using dload but the transfert rate to the sd card is taking forever;
Now I extracted everything from update.app using huawei firmware extractor (see http://imgur.com/MWeCCXi ) what should I flash (via fastboot) and in what order?
I would really appreciate the help.
algnerd said:
Since I lost everything from the boot to the recovery to the system part to anything, i haven't been able to boot the phone;
I can access erecovery but when I try to recover the phone it stops at downloading and then says couldn't connect to servers so that's dead;
I can access TWRP but when I try to flash MM, it returns errors saying that it couldn't mount partitions (Vendor, cust and other...)
I can access fastboot mode. Some people suggested that I should try recovering using dload but the transfert rate to the sd card is taking forever;
Now I extracted everything from update.app using huawei firmware extractor (see http://imgur.com/MWeCCXi ) what should I flash (via fastboot) and in what order?
I would really appreciate the help.
Click to expand...
Click to collapse
Boot.img , recovery.img , cust.img , system.img.
Claleale said:
Boot.img , recovery.img , cust.img , system.img.
Click to expand...
Click to collapse
Are those the correct commands?
Fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
fastboot flash system system.img
?
algnerd said:
Are those the correct commands?
Fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
fastboot flash system system.img
?
Click to expand...
Click to collapse
Yes
Claleale said:
Yes
Click to expand...
Click to collapse
Flashing cust and system returned failes
For cust: (failed remote: partition error)
For syst: (failed remote: sparse flash write failure)
Since I was running nougat before messing up the phone, it had to be System and Boot extracted from the nougat update
By Nougat I assume you mean the file that has been digged out somewhere in the web and that is floating around here in the forums?
Well we all don't really know what this build exactly is, which makes it very hard to reconstruct your errors and give you advice... I would never flash that but okay, that's why we are here
Do you have a TWRP backup that you can restore (and if no, maybe somebody can upload you a clean TWRP restore file)?
Have you tried flashing CM / AICP?
Schlengge said:
By Nougat I assume you mean the file that has been digged out somewhere in the web and that is floating around here in the forums?
Well we all don't really know what this build exactly is, which makes it very hard to reconstruct your errors and give you advice...
Do you have a TWRP backup that you can restore (and if no, maybe somebody can upload you a clean TWRP restore file)?
Have you tried flashing CM?
Click to expand...
Click to collapse
Indeed, the same build that was floating in here.
I was able to resurect my phone from the dead by flashing boot, system and recovery from nougat build then I downgraded to MM untill a more stable release;
Thanks for your support anyway.
(If you know how to close this thread, you're more than welcome to do it )
algnerd said:
...
(If you know how to close this thread, you're more than welcome to do it )
Click to expand...
Click to collapse
You have to use the report button on your own OP. In the report text box, just ask mods to close your thread. The mod who is assigned to this forum will handle your request.
algnerd said:
Indeed, the same build that was floating in here.
I was able to resurect my phone from the dead by flashing boot, system and recovery from nougat build then I downgraded to MM untill a more stable release;
Thanks for your support anyway.
(If you know how to close this thread, you're more than welcome to do it )
Click to expand...
Click to collapse
Hi there. Earlier I spent a few painful hours in the same boat you were in. I've managed to get back to a fresh install of the Nougat build from this thread, but can't seem the downgrade to MM using the (translated from Spanish) instructions found here (linked from that first thread). How did you manage to get back to MM?
(I should add that I tried to flash boot, system and recovery via fastboot without any success).
Cheers
thomasedwardbullen1986 said:
Hi there. Earlier I spent a few painful hours in the same boat you were in. I've managed to get back to a fresh install of the Nougat build from this thread, but can't seem the downgrade to MM using the (translated from Spanish) instructions found here (linked from that first thread). How did you manage to get back to MM?
(I should add that I tried to flash boot, system and recovery via fastboot without any success).
Cheers
Click to expand...
Click to collapse
May god have mercy on your soul.
For the downgrade, I didn't use the b161 directly. I flashed some oeminfo provided in the same folder as the TWRP. Then used b150 ans the three boutons method. Worked like a charm.
Hope it will help you downgrade your phone.
I have the same problem, someone could explain it to me step by step, please
ask help
Hello
My name is EL HADJI MODOU SOW.I request your help concerning a big problem that I meet with my phone huawei P9 lite vns-l31c113b364 (these is the serial number 4TE0216B08004097) .in fact I wanted to activate the second sim then j I made a mistake handling the shot the system is corrupt and now I can not use my phone. I tried to flash it but I can not find a good frimeware. All the flash files that I find are working except the cust.img , vendor.img and product.img. what happens when I flash the cust.img (H: \ SRKToolHuawei-Lod-Chong-V2.0-20161002> fastboot flash cust CUST.img
target reported download size of 471859200 bytes
sending 'cust' (435462 KB) ...
OKAY [10.711s]
writing 'cust' ...
FAILED (remote: partition error)
finished. total time: 10.729s).
please help me I'm really teriified
this is my email:[email protected]

I can't fastboot any system Img any fix?

Every time I wanna flash Rom img files with fastboot
System partition failed to flash
Invalid sparse file format at header magic
Sending sparse 'system_b' 1/5 (773795 KB) OKAY [ 17.926s]
Writing 'system_b' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
My bootloader is unlocked
Does anyone know how to fix this problem?
rowihel2012 said:
Every time I wanna flash Rom img files with fastboot
System partition failed to flash
Invalid sparse file format at header magic
Sending sparse 'system_b' 1/5 (773795 KB) OKAY [ 17.926s]
Writing 'system_b' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
My bootloader is unlocked
Does anyone know how to fix this problem?
Click to expand...
Click to collapse
I get same issues trying to flash Lineage
Sounds like you need to update fastboot/adb. I get same message when I need to update.
dontbeweakvato said:
Sounds like you need to update fastboot/adb. I get same message when I need to update.
Click to expand...
Click to collapse
Could you gave me the updated version link please?
rowihel2012 said:
Every time I wanna flash Rom img files with fastboot
System partition failed to flash
Invalid sparse file format at header magic
Sending sparse 'system_b' 1/5 (773795 KB) OKAY [ 17.926s]
Writing 'system_b' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
My bootloader is unlocked
Does anyone know how to fix this problem?
Click to expand...
Click to collapse
Are you flashing with windows, Linux or mac. If on windows try right click and run as administrator. If on Linux type sudo su to gain root first. Not sure what the step is on mac but probably close if not the same as on Linux.
Aporzio said:
Are you flashing with windows, Linux or mac. If on windows try right click and run as administrator. If on Linux type sudo su to gain root first. Not sure what the step is on mac but probably close if not the same as on Linux.
Click to expand...
Click to collapse
Using windows 10
rowihel2012 said:
Using windows 10
Click to expand...
Click to collapse
I would try running powershell as administrator then.
I just downloaded the AIO tool, if you need drivers.
But I got an easier way to flash the custom ROM.
Download the AIO tool (https://forum.xda-developers.com/oneplus-8-pro/how-to/tool-tool-one-driversunlocktwrpfactory-t4103509),
download 10.5.9 (or whatever version you want) fastboot rom (https://forum.xda-developers.com/oneplus-8-pro/how-to/rom-stock-fastboot-roms-oneplus-8-pro-t4083997) , put all your custom rom parts (system.img etc.) in the downloaded stock.zip ROM, and flash it with AIO tool -> flash factory image, select zip and wait.
Worked for me with Lineage.
Lordofbirds said:
I just downloaded the AIO tool, if you need drivers.
But I got an easier way to flash the custom ROM.
Download the AIO tool (https://forum.xda-developers.com/oneplus-8-pro/how-to/tool-tool-one-driversunlocktwrpfactory-t4103509),
download 10.5.9 (or whatever version you want) fastboot rom (https://forum.xda-developers.com/oneplus-8-pro/how-to/rom-stock-fastboot-roms-oneplus-8-pro-t4083997) , put all your custom rom parts (system.img etc.) in the downloaded stock.zip ROM, and flash it with AIO tool -> flash factory image, select zip and wait.
Worked for me with Lineage.
Click to expand...
Click to collapse
Thank you bro
I will try it
Lordofbirds said:
I just downloaded the AIO tool, if you need drivers.
But I got an easier way to flash the custom ROM.
Download the AIO tool (https://forum.xda-developers.com/oneplus-8-pro/how-to/tool-tool-one-driversunlocktwrpfactory-t4103509),
download 10.5.9 (or whatever version you want) fastboot rom (https://forum.xda-developers.com/oneplus-8-pro/how-to/rom-stock-fastboot-roms-oneplus-8-pro-t4083997) , put all your custom rom parts (system.img etc.) in the downloaded stock.zip ROM, and flash it with AIO tool -> flash factory image, select zip and wait.
Worked for me with Lineage.
Click to expand...
Click to collapse
same problem
i cant flash any rom with fastboot and twrp too
rowihel2012 said:
same problem
i cant flash any rom with fastboot and twrp too
Click to expand...
Click to collapse
You downloaded AIO Tool, Fastboot Rom, replaced Stock Rom Images with the Images you wanted to flash over, repacked it as .ZIP archive and tried to flash it with the AIO Tool only? Not ADB, AIO Tool -> flash factory Image -> so it uses the flash all bat from inside the .ZIP archive? Don't try to do it manually. It wont work.
Lordofbirds said:
You downloaded AIO Tool, Fastboot Rom, replaced Stock Rom Images with the Images you wanted to flash over, repacked it as .ZIP archive and tried to flash it with the AIO Tool only? Not ADB, AIO Tool -> flash factory Image -> so it uses the flash all bat from inside the .ZIP archive? Don't try to do it manually. It wont work.
Click to expand...
Click to collapse
Tried with AIO too flash stock
Tried manually with Adb
Same problem
It won't flash system
Always failed
Tried to flash roms woth twrp
Same problem
Lordofbirds said:
You downloaded AIO Tool, Fastboot Rom, replaced Stock Rom Images with the Images you wanted to flash over, repacked it as .ZIP archive and tried to flash it with the AIO Tool only? Not ADB, AIO Tool -> flash factory Image -> so it uses the flash all bat from inside the .ZIP archive? Don't try to do it manually. It wont work.
Click to expand...
Click to collapse
So other files in stock zip besides img files
Should i remove ?
Or keep it ?
Just replaced all img files
And tried to flash with tool
Same problem
rowihel2012 said:
So other files in stock zip besides img files
Should i remove ?
Or keep it ?
Just replaced all img files
And tried to flash with tool
Same problem
Click to expand...
Click to collapse
found any fix?
You need to reinstall google USB drivers. Here's a link. https://developer.android.com/studio/run/win-usb
It's almost certainly the fastboot / adb drivers you're using.
Also use a USB 2 slot not 3
Win 10 not 7
Can you boot boot.img's? flash them? Does everything else via fastboot work?
If so then the flashing of system images may be the issue.
did you found any solution?
I'm facing the same problem bro.
At first this problem was not exist until I have used the MSM tool.
After I have used the MSM tool for unbrick my device I'm facing the same problem.
If you find any solution please let me know. It will be helpful.

Stock ROM to UPDATE IN 2021

Hello, good day. I just wanted to ask, (Im using custom rom now and my old backup is nowhere to be found) If I am going to flash my device to official stock rom, like if I flashed the older version (lets say the MM) can I still update my device today (up to nougat) through OTA update?
i think huawei cloud is the site where we download OTA updates from but I think is already dead.
(sorry if my poiint is confusing, I just really don't know how to explain it clearly)
emmanueldlauron said:
Hello, good day. I just wanted to ask, (Im using custom rom now and my old backup is nowhere to be found) If I am going to flash my device to official stock rom, like if I flashed the older version (lets say the MM) can I still update my device today (up to nougat) through OTA update?
i think huawei cloud is the site where we download OTA updates from but I think is already dead.
(sorry if my poiint is confusing, I just really don't know how to explain it clearly)
Click to expand...
Click to collapse
Hi,
in fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
and post results.
thanks for resonding
(bootloader) :Elite ROM v7.7
(bootloader) HUAWEI VNS-L31
vendorcountry: hw/spcseas
FAILED (remote: 'invalid command')
emmanueldlauron said:
thanks for resonding
(bootloader) :Elite ROM v7.7
(bootloader) HUAWEI VNS-L31
vendorcountry: hw/spcseas
FAILED (remote: 'invalid command')
Click to expand...
Click to collapse
Okay, last question - single SIM or dual SIM?
Dual Sim
emmanueldlauron said:
flash my device to official stock rom
Click to expand...
Click to collapse
So if I not mistaken, your build number is VNS-L31C185 EMUI 5 (correct me if I'm wrong).
Firmware finder and Huawei old server are down, so download service ROM.
IMO now you have two possibilities:
A) flash Service ROM using dload method, guide can be found in ReleaseDoc folder. The process will erase all your data and lock the BL again!
B)
- from downloaded ROM extract BOOT.img
RECOVERY.img
SYSTEM.img
CUST.img via 'Huawei update extractor' , follow Guide
(Note: CUST.img on Nougat can be found in the second archive)
- In fastboot mode flash extracted partitions using commands
fastboot flash boot BOOT.img
fastboot flash recovery RECOVERY.img
fastboot flash system SYSTEM.img
fastboot flash cust CUST.img
- fastboot reboot
- Factory reset in stock recovery
-Alf- said:
So if I not mistaken, your build number is VNS-L31C185 EMUI 5 (correct me if I'm wrong).
Firmware finder and Huawei old server are down, so download Service ROM
IMO now you have two possibilities:
A) flash Service ROM using dload method, guide can be found in ReleaseDoc folder. The process will erase all your data and lock the BL again!
B)
- from downloaded ROM extract BOOT.img
RECOVERY.img
SYSTEM.img
CUST.img via 'Huawei update extractor' , follow Guide
(Note: CUST.img on Nougat can be found in the second archive)
- In fastboot mode flash extracted partitions using commands
fastboot flash boot BOOT.img
fastboot flash recovery RECOVERY.img
fastboot flash system SYSTEM.img
fastboot flash cust CUST.img
- fastboot reboot
- Factory reset in stock recovery
Click to expand...
Click to collapse
I don't have sd card on me right now. is there any way I can flash service rom without sd card?
Edit: and also this device is C636xxx.
neverming the first paragraph I said. I'm confused with CUST.img thing, I donwloaded the C635 update but there's no second archive on what I had downloaded
emmanueldlauron said:
flash service rom without sd card?
Click to expand...
Click to collapse
Nope.
emmanueldlauron said:
this device is C636xxx.
Click to expand...
Click to collapse
Okay, then download C636
-Alf- said:
Nope.
Okay, then download C636
Click to expand...
Click to collapse
Thanks for the tips and ideas, I somehow understand something new today.
emmanueldlauron said:
there's no second archive on what I had downloaded
Click to expand...
Click to collapse
VNS-L31_hw_xxxxx
-Alf- said:
VNS-L31_hw_meafnaf
Click to expand...
Click to collapse
Oh yeah. I just figured it out but had to rename that to update.app so update extractor can accept the file. Thanks by the way.
for now SYSTEM and CUST takes time to finish extracting.
-Alf- said:
So if I not mistaken, your build number is VNS-L31C185 EMUI 5 (correct me if I'm wrong).
Firmware finder and Huawei old server are down, so download service ROM.
IMO now you have two possibilities:
A) flash Service ROM using dload method, guide can be found in ReleaseDoc folder. The process will erase all your data and lock the BL again!
B)
- from downloaded ROM extract BOOT.img
RECOVERY.img
SYSTEM.img
CUST.img via 'Huawei update extractor' , follow Guide
(Note: CUST.img on Nougat can be found in the second archive)
- In fastboot mode flash extracted partitions using commands
fastboot flash boot BOOT.img
fastboot flash recovery RECOVERY.img
fastboot flash system SYSTEM.img
fastboot flash cust CUST.img
- fastboot reboot
- Factory reset in stock recovery
Click to expand...
Click to collapse
UPDATE: I did the B. they're all finished without any errors, but I ended with bootloop, like I can't go to recovery and when I tried to it vibrates twice and show nothing but just the huawei logo with "powered by android" texts.
emmanueldlauron said:
UPDATE: I did the B. they're all finished without any errors, but I ended with bootloop, like I can't go to recovery and when I tried to it vibrates twice and show nothing but just the huawei logo with "powered by android" texts.
Click to expand...
Click to collapse
Try command
fastboot erase userdata
and reboot.
Check your current build number etc.
https://forum.xda-developers.com/t/stock-rom-to-update-in-2021.4320501/post-85489493
-Alf- said:
Try command
fastboot erase userdata
and reboot.
Check your current build number etc.
https://forum.xda-developers.com/t/stock-rom-to-update-in-2021.4320501/post-85489493
Click to expand...
Click to collapse
emmanueldlauron said:
(bootloader) :Elite ROM v7.7
(bootloader) HUAWEI VNS-L31
vendorcountry: hw/spcseas
FAILED (remote: 'invalid command')
Click to expand...
Click to collapse
still the same with these
emmanueldlauron said:
still the same with these
Click to expand...
Click to collapse
Bro try this way out...
Download and install TWRP (if possible) and let me know
Upd.: nevermind, I forgot you don't have an sd card,.
Upd.2.: without SD you can try to flash Service ROM (or B361 firmware) using TWRP and sideload method. Unfortunately, sideload is Greek to me , so google it.
-Alf- said:
Bro try this way out...
Download and install TWRP (if possible) and let me know
Upd.: nevermind, I forgot you don't have an sd card,.
Upd.2.: without SD you can try to flash Service ROM (or B361 firmware) using TWRP and sideload method. Unfortunately, sideload is Greek to me , so google it.
B361 firmware is a fullOTA-MF-PV version, download and instructions here
Click to expand...
Click to collapse
I can still go fastboot mode and install everything without any errors but I don't why, it confuses me that let say I just flashed recovery (custom or stock) but when I'm going to access it (volume up + power button) phone just vibrates twice but nothing will happen.
emmanueldlauron said:
I can still go fastboot mode and install everything without any errors but I don't why, it confuses me that let say I just flashed recovery (custom or stock) but when I'm going to access it (volume up + power button) phone just vibrates twice but nothing will happen.
Click to expand...
Click to collapse
Flash TWRP over eRecovery, run command
fastboot flash recovery2 twrp.img
fastboot reboot
when a yellow warning appears on the screen, pres and hold Vol Up for 3 sec.
Edit: maybe your data partition is formatted with f2fs (after installing Elite ROM) , it should be ext4. I'm out of ideas bro, sorry.
-Alf- said:
Flash TWRP over eRecovery, run command
fastboot flash recovery2 twrp.img
fastboot reboot
when a yellow warning appears on the screen, pres and hold Vol Up for 3 sec.
Edit: maybe your data partition is formatted with f2fs (after installing Elite ROM) , it should be ext4. I'm out of ideas bro, sorry.
Click to expand...
Click to collapse
No problem. I think I hard bricked my phone, I just got boot logo and fastboot but I can't find any fix or solution or anything to do with this.
Flashing recovery or recovery2 finished w/o any errors but I can't boot to recovery.
Thanks for your help by the way. I appreciate it! Kudos and have a nice day. Keep safe.
emmanueldlauron said:
I think I hard bricked my phone,
Click to expand...
Click to collapse
IMO you only need an SD card and flash the Service ROM.

Categories

Resources