Related
Hi there,
I've been searching around to find a specific firmware zip for my new tablet, the SKU: WW, Version: 10.26.1.7.
It appears that asus has pulled this file and was wondering if anyone still has this file available somehow.
I soft-bricked my tablet and am not capable of flashing any other (earlier) firmware zip.
Any help would be greatly appreciated.
Yours sincerely,
Rens "Ikkerens" Rikkerink
Ikkerens said:
Hi there,
I've been searching around to find a specific firmware zip for my new tablet, the SKU: WW, Version: 10.26.1.7.
It appears that asus has pulled this file and was wondering if anyone still has this file available somehow.
I soft-bricked my tablet and am not capable of flashing any other (earlier) firmware zip.
Any help would be greatly appreciated.
Yours sincerely,
Rens "Ikkerens" Rikkerink
Click to expand...
Click to collapse
Why can't you download an earlier firmware?
schmeggy929 said:
Why can't you download an earlier firmware?
Click to expand...
Click to collapse
I can, but it always ends up with some kind of error.
I basically tried following the steps you did:
schmeggy929 said:
i downloaded the asus firmware for 10.14.1.47. extract zip and you get a user.zip. extracted the boot.img. I fastboot erase boot, system, format system, data and cache(as you did)
fastboot -i 0x0B05 flash boot boot.img then
fastboot -i 0x0B05 flash system blob then
fastboot -i 0x0B05 flash system UL-K00C-US-10.14.1.47-user.zip
rebooted back into fastboot and bootloader showed 10.14.1.47 version.
Click to expand...
Click to collapse
But on when trying to flash the ***-user.zip, I get this error message:
Code:
$ fastboot -i 0x0B05 flash system UL-K00C-WW-10.14.1.47-user.zip
target reported max download size of 643825664 bytes
Invalid sparse file format at header magi
Edit: My bootloader version shows: WW_epad-10.26.1.7-20131108
Ikkerens said:
I can, but it always ends up with some kind of error.
I basically tried following the steps you did:
But on when trying to flash the ***-user.zip, I get this error message:
Code:
$ fastboot -i 0x0B05 flash system UL-K00C-WW-10.14.1.47-user.zip
target reported max download size of 643825664 bytes
Invalid sparse file format at header magi
Edit: My bootloader version shows: WW_epad-10.26.1.7-20131108
Click to expand...
Click to collapse
you are going to get that along with a few more errors. Wait until it is done. It will take like 10 mins and finish.
when it is done reboot in bootloader and you should see the version change.
schmeggy929 said:
you are going to get that along with a few more errors. Wait until it is done. I will take like 10 mins and finish.
Click to expand...
Click to collapse
You're getting this wrong, it does not do anything. The process immediately quits.
Ikkerens said:
You're getting this wrong, it does not do anything. The process immediately quits.
Click to expand...
Click to collapse
Ok when you get that message do you get a blinking curser?
Ikkerens said:
Hi there,
I've been searching around to find a specific firmware zip for my new tablet, the SKU: WW, Version: 10.26.1.7.
It appears that asus has pulled this file and was wondering if anyone still has this file available somehow.
I soft-bricked my tablet and am not capable of flashing any other (earlier) firmware zip.
Any help would be greatly appreciated.
Yours sincerely,
Rens "Ikkerens" Rikkerink
Click to expand...
Click to collapse
did you make any backup with cwm recovery?
try this:
unpack blob from 47 update
Code:
fastboot flash staging blob
fastboot flash recovery recovery.img
fastboot reboot-bootloader
load recovery, restore your backup
if you have not made any backup with cwm recovery, tell me.
btw fastboot flash system... is not needed here
lpdunwell said:
did you make any backup with cwm recovery?
try this:
unpack blob from 47 update
Code:
fastboot flash staging blob
fastboot flash recovery recovery.img
fastboot reboot-bootloader
load recovery, restore your backup
if you have not made any backup with cwm recovery, tell me.
btw fastboot flash system... is not needed here
Click to expand...
Click to collapse
I have not made a backup using cwm because there was no CWM available for my version.
My tablet was already updated to 4.3 and I (apparently) could not boot the cwm in the development section.
If I would be able to flash a usable recovery, I wouldn't be in this situation anyway as the asus update (.47) is flashable (found an updater-script in the zip).
Ikkerens said:
I have not made a backup using cwm because there was no CWM available for my version.
My tablet was already updated to 4.3 and I (apparently) could not boot the cwm in the development section.
If I would be able to flash a usable recovery, I wouldn't be in this situation anyway as the asus update (.47) is flashable (found an updater-script in the zip).
Click to expand...
Click to collapse
forget what I wrote here. I opened a thread with unbricking instructions. Good luck
lpdunwell said:
forget what I wrote here. I opened a thread with unbricking instructions. Good luck
Click to expand...
Click to collapse
Won't do me any good at the moment, I already managed to brick it even further (couldn't even get into fastboot mode anymore), so I RMA'd it.
Ikkerens said:
Won't do me any good at the moment, I already managed to brick it even further (couldn't even get into fastboot mode anymore), so I RMA'd it.
Click to expand...
Click to collapse
oh crap. sorry about that. I know there's the nvflash, too, but I have no idea how to use that so far...
would you mind telling what exactly happened?
lpdunwell said:
oh crap. sorry about that. I know there's the nvflash, too, but I have no idea how to use that so far...
would you mind telling what exactly happened?
Click to expand...
Click to collapse
Nvflash is inaccessible at the moment, it requires some preparation (you have to prepare it BEFORE you brick it)
Anyway, basically, I bought the tablet a few hours earlier.
Wanted to root it to remove some bloatware and restore some titanium backup thingies.
So I unlocked, rooted, basic stuff.
Went into TB, removed bloatware such as Amazon Kindle and some other irrelevant titles.
That action however, somehow caused it to be unbootable.
So I went into some basic repair stuff, as usual.
Tried to flash a recovery, only to find out, there is no working recovery. Only CWM, which required an earlier version of my bootloader.
So, what next. Restore stock? Downloaded the firmware, found out it was the earlier version of my device, because Asus removed the 4.3-EU version from their website.
So, I downloaded the .47-EU version, opened it. Saw there were no images, merely plain files meant for /system and an updater-script.
I ended up attempting to package my own system.img after that. Created an ext4 image on my computer, moved the files there. Followed the instructions in updater-script, which were mostly symlinks and stuff.
In the end of the updater-script they flashed blob to /staging and boot.img to /boot.
So, I flashed my custom system.img to /system.
Flashed boot
Flashed the blob
And beyond that point, I ended up in a bootloop of my bootloader. I could not hold down volume to enter fastboot or anything. All I could do was watch the asus logo as it constantly rebooted. (And ofcourse, no way to turn it off other than waiting for the battery to die)
Ikkerens said:
Nvflash is inaccessible at the moment, it requires some preparation (you have to prepare it BEFORE you brick it)
Anyway, basically, I bought the tablet a few hours earlier.
Wanted to root it to remove some bloatware and restore some titanium backup thingies.
So I unlocked, rooted, basic stuff.
Went into TB, removed bloatware such as Amazon Kindle and some other irrelevant titles.
That action however, somehow caused it to be unbootable.
So I went into some basic repair stuff, as usual.
Tried to flash a recovery, only to find out, there is no working recovery. Only CWM, which required an earlier version of my bootloader.
So, what next. Restore stock? Downloaded the firmware, found out it was the earlier version of my device, because Asus removed the 4.3-EU version from their website.
So, I downloaded the .47-EU version, opened it. Saw there were no images, merely plain files meant for /system and an updater-script.
I ended up attempting to package my own system.img after that. Created an ext4 image on my computer, moved the files there. Followed the instructions in updater-script, which were mostly symlinks and stuff.
In the end of the updater-script they flashed blob to /staging and boot.img to /boot.
So, I flashed my custom system.img to /system.
Flashed boot
Flashed the blob
And beyond that point, I ended up in a bootloop of my bootloader. I could not hold down volume to enter fastboot or anything. All I could do was watch the asus logo as it constantly rebooted. (And ofcourse, no way to turn it off other than waiting for the battery to die)
Click to expand...
Click to collapse
Since you are unlocked, you can try to flash the recovery (extract it first) of the US version 1.7, should be the same as wwe. Or just even try to flash the whole us update manually. And later change back to the wwe version when it comes available. The 47 update was only a minor ota for 4.2 so no image of recovery or bootloader there.
Sad story. What would have been the safe thing to do, if others wish to root their devices?
Snah001 said:
Since you are unlocked, you can try to flash the recovery (extract it first) of the US version 1.7, should be the same as wwe. Or just even try to flash the whole us update manually. And later change back to the wwe version when it comes available. The 47 update was only a minor ota for 4.2 so no image of recovery or bootloader there.
Click to expand...
Click to collapse
I still had the original recovery flashed, I never overwrote it actually. I needed a custom recovery (such as CWM, TWRP).
Flashing an US update is not possible alltogether, there are some minor differences with hardware compitability and such.
Problem is, I could've downloaded the .47 update, but I had already updated to 4.3 (BL 10.26.1.7)
Ikkerens said:
I still had the original recovery flashed, I never overwrote it actually. I needed a custom recovery (such as CWM, TWRP).
Flashing an US update is not possible alltogether, there are some minor differences with hardware compitability and such.
Problem is, I could've downloaded the .47 update, but I had already updated to 4.3 (BL 10.26.1.7)
Click to expand...
Click to collapse
I don't know if it isn't possible. On the TF700 it was only a line in the build.prop file that made the difference.
I would try it because now you have nothing and when it works you have the us version yes, but at least it works.
pelago said:
Sad story. What would have been the safe thing to do, if others wish to root their devices?
Click to expand...
Click to collapse
This guide worked fine for me; http://forum.xda-developers.com/showthread.php?t=2516215
It's only about what you do with the root ^^
Snah001 said:
I don't know if it isn't possible. On the TF700 it was only a line in the build.prop file that made the difference.
I would try it because now you have nothing and when it works you have the us version yes, but at least it works.
Click to expand...
Click to collapse
Already too late, it has been RMA'd, and then, I had nothing to flash it with.
Ikkerens said:
This guide worked fine for me; http://forum.xda-developers.com/showthread.php?t=2516215
It's only about what you do with the root ^^
Click to expand...
Click to collapse
Well I meant, what should a root user do to try and protect themselves against bricking their device like you did? Is it a matter of making sure that CWM or TWRP is on the device as a recovery partition? And are those available on TF701T yet?
Oh dear. That's a lot gone wrong.
Cwm is available and that works.
It's made by drgravy. I use it in my unbrick tut.
All i can say is, root --> cwm --> backup.
Sent from my GT-I9505 using xda app-developers app
That CWM wouldn't boot for me :/
I flashed 5.0 ages ago since I live in NZ and I heard that I can get the official version now so I need to return to stock somehow so I can install the latest update, so does anyone have a stock rom or a method to return to stock and still be able to receive the updates
See any response by the forum member "reefuge" - his signature contains a stock ROM link.
For example, in my thread http://forum.xda-developers.com/moto-g-2014/help/xt1068-ota-lollipop-update-failing-t3035150
try to flash the rom via fastboot, using the commands on 4.2 on this thread
You need a XML zip of the rom , to have the XML zip of yours rom search in here and download the file regards yours model and OS version that you wanna...
download is very slow, here a mirror but the mirror is incomplete.
download, unzip, to the some folder of mfastboot and give the commands a try, while the phone is conected via USB to the PC in the bootloader screen, you must have motorola driver update, to know if you have the drivers, just plug the phone on normal on mode, and see if you can copy and past files to the phone...
If you follow this procedure you will erase everything on the phone, so do a backup...
To receved a OTA update, you will need to have everything on stock so no root no custom recovery, the bootloader state don't matter. :fingers-crossed: :good:
Hello i was using this guide :
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
to root my phone i went and finished fastboot oem unlock step
the problem is after it and booted the phone i extracted the root files and clicked on it
then realized it said oem is not enabled in developer option
so now when i boot the phone a message says"Your Device is Corrupt. It can't be trusted and may not work properly."
and after it like 1-2 sec it turns off
i can still boot in bootloader
PLEASE SOME ONE HELP ME
Also it says device is unlocked in the bootloader statues code 3
extra information i was using android marshmallow 6 latest firmware
oudric said:
Hello i was using this guide :
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
to root my phone i went and finished fastboot oem unlock step
the problem is after it and booted the phone i extracted the root files and clicked on it
then realized it said oem is not enabled in developer option
so now when i boot the phone a message says"Your Device is Corrupt. It can't be trusted and may not work properly."
and after it like 1-2 sec it turns off
i can still boot in bootloader
PLEASE SOME ONE HELP ME
Also it says device is unlocked in the bootloader statues code 3
extra information i was using android marshmallow 6 latest firmware
Click to expand...
Click to collapse
The same thing happened to me when I tried to use a rootkit method for rooting the phone when it apparently knew nothing about the most recent updates (MRA58N or MRA58R). I ended up having to manual flash each individual image file from the MRA58N factory image (the flash-all script in the factory image zip wouldn't work). Even so, when I rebooted it still displayed the Your Device is Corrupt message. Then I went through the manual root process again (flashed the modified boot.img through fastboot, then flashed the latest TWRP recovery via fastboot, and then used TWRP to flash the latest SuperSU. Only then did the Your Device is Corrupt message go away and I also had root with everything else working fine.
It definitely made for an un-Godly horrible first 24-hours with my new phone! I hope this helps you.
internetpilot said:
The same thing happened to me when I tried to use a rootkit method for rooting the phone when it apparently knew nothing about the most recent updates (MRA58N or MRA58R). I ended up having to manual flash each individual image file from the MRA58N factory image (the flash-all script in the factory image zip wouldn't work). Even so, when I rebooted it still displayed the Your Device is Corrupt message. Then I went through the manual root process again (flashed the modified boot.img through fastboot, then flashed the latest TWRP recovery via fastboot, and then used TWRP to flash the latest SuperSU. Only then did the Your Device is Corrupt message go away and I also had root with everything else working fine.
It definitely made for an un-Godly horrible first 24-hours with my new phone! I hope this helps you.
Click to expand...
Click to collapse
can you please tell me steps i am so afraid to do anything to my phone now and i think my problem is same as yours
i downloaded 6.0.0 (MRA58R) and i used option in toolkit flash stock it gave me an error
"failed (data transfer failure (unknown error))
Its not so easy to brick nexus, but make sure you don't lock bootloader before your phone is working right. You can find the guide how to flash it on XDA.
You will need to flash the missing files by hand.
I was able to fix the erro i got by flashing by :
setting up environmental variable
copy all the flash files, all.bat bootloaderXXX.img... etc to platform tools folder
made sure i connected into usb 2.0 port not usb 3.0
then i flashed the stock firmware XD now my phone to point zero again
oudric said:
I was able to fix the erro i got by flashing by :
setting up environmental variable
copy all the flash files, all.bat bootloaderXXX.img... etc to platform tools folder
made sure i connected into usb 2.0 port not usb 3.0
then i flashed the stock firmware XD now my phone to point zero again
Click to expand...
Click to collapse
You don't need to move the files to the platform-tools folder.
Go to Nexus 6 General > Sticky rol-up thread > Adb and fastboot. What is it?
This will tell you how to set up and use adb or fastboot properly.
Folks,
I recently purchased a preowned HTC One M9 in good shape. The phone does not appear to have been rooted, s-offed or any such thing. It looks bone stock. It currently has Android 6.0 on it. and software number 3.39.531.41
It has been over a month since t-mobile has rolled out the nougat update for the HTC One-M9 and I have not received any update on the phone. I constantly keep checking if the phone has an update available but the phone always says no update available. I gave up on the OTA being rolled out for the phone so I downloaded the Nougat RUU which is 4.27.531.6 .
When I follow the procedure for installing the update I got a signature error 132 . Now I know that error shows up when the phone is rooted or is s-off or any such thing but my phone seems to be completely stock. Does anyone know why I cant install the RUU or receive OTA updates to Nougat for my phone?
I think I figured it out. I contacted T-Mobile support who told me to contact HTC since the HTC servers are responsible for pushing out updates. So I contacted HTC customer support and shared my IMEI with the representative. She looked up some information on the HTC database using the IMEI number and told me that my phone was a store demo phone and that demo phones are blocked from receiving updates from the HTC servers. Oh well.
Hello,
Just got the same phone with same error. If someone provides me with 0PJAIMG.ZIP, I can test and see how it goes. So far update from phone >> didn't work; RUU update >> didn't work. same error
Thanks
I had the same problem some time a go what you have to do is to check if its relock and has stock recovery. If yes first flash 3.39.531.41 RUU before you can flash the 4.27.531.6 or the OTA. But my receives the OTA alright but could neither install that or RUU
amptronic said:
I had the same problem some time a go what you have do is to check if its relock and has stock recovery. If yes first flash 3.39.531.41 RUU before you can flash the 4.27.531.6 or the OTA.
Click to expand...
Click to collapse
So it has to be locked with stock recovery? Then flash ruu 3.49 ad then the newest version?
Thanks
dohcvtec said:
So it has to be locked with stock recovery? Then flash ruu 3.49 ad then the newest version?
Thanks
Click to expand...
Click to collapse
did it work?? I'm having same problem..
smilesintears77 said:
did it work?? I'm having same problem..
Click to expand...
Click to collapse
Did anyone get any solution for this error? I am having the same issue
Thanks
vbcomer said:
Did anyone get any solution for this error? I am having the same issue
Thanks
Click to expand...
Click to collapse
i think first decrypt RUU then manually flash whole Nougat ROM.
vbcomer said:
Did anyone get any solution for this error? I am having the same issue
Thanks
Click to expand...
Click to collapse
i found a way i have demo set when i use 4.27.531.6 RUU its saying signature error so this is what i did
i download OTA from link here http://fotadl-az.htc.com/secure/OTA_HIMA_UL_N70_SENSE80_TMUS_MR_TMOUS_4.27.531.6-3.39.531.41_release_497409trrpztkwvabkx6lv.zip
after that i just boot into recovery mode and then select an opton Updae via ADB
rename file to OTA.zip then open command prompt located to where file is and then run below command
adb sideload ota.zip
let the process finish it will take a while. especially when HTC logo appears it took 5 min but i finally have nougat
for detail how to apply OTA here is link http://www.theandroidsoul.com/how-to-install-ota-updates-manually-using-recovery-and-adb-sideload/
m_abbas25 said:
i found a way i have demo set when i use 4.27.531.6 RUU its saying signature error so this is what i did
i download OTA from link here http://fotadl-az.htc.com/secure/OTA_HIMA_UL_N70_SENSE80_TMUS_MR_TMOUS_4.27.531.6-3.39.531.41_release_497409trrpztkwvabkx6lv.zip
after that i just boot into recovery mode and then select an opton Updae via ADB
rename file to OTA.zip then open command prompt located to where file is and then run below command
adb sideload ota.zip
let the process finish it will take a while. especially when HTC logo appears it took 5 min but i finally have nougat
for detail how to apply OTA here is link http://www.theandroidsoul.com/how-to-install-ota-updates-manually-using-recovery-and-adb-sideload/
Click to expand...
Click to collapse
Hi,
Thanks for the info. However, I couldn't get into the recovery mode. Either from bootloader -> "Boot to recovery mode" or via command "adb reboot recovery", after the phone reboots, the screen will show a phone icon with triangle. Then after awhile the phone will restart normally. I can't get to step to do sideload the zip file.
I also put the above ota.zip on a micro SD card and load the card in the phone, then boot to download mode. In that mode, it shows the following 2 lines:
FILE /mnt/media_rw/ext_sd/0PJAIMG.zip
File NOT FOUND
Where do I find that missing file?
Thanks
vbcomer said:
Hi,
Thanks for the info. However, I couldn't get into the recovery mode. Either from bootloader -> "Boot to recovery mode" or via command "adb reboot recovery", after the phone reboots, the screen will show a phone icon with triangle. Then after awhile the phone will restart normally. I can't get to step to do sideload the zip file.
I also put the above ota.zip on a micro SD card and load the card in the phone, then boot to download mode. In that mode, it shows the following 2 lines:
FILE /mnt/media_rw/ext_sd/0PJAIMG.zip
File NOT FOUND
Where do I find that missing file?
Thanks
Click to expand...
Click to collapse
I think your recovery file is damaged. Thou i am novice in this but i think you should run RUU of existing rom it may repair your recovery then try this method.
OK,
I found the 0PJAIMG.zip for version 3.39.531.7 in this forum "https://forum.xda-developers.com/tmobile-one-m9/general/please-read-rooting-using-twrp-t3069022"
I put that on my SD card and was able to update the phone from Lollipop to Marshmallow.
However, after that update, the phone still won't update from Marshmallow to Nougat using the file RUU_HIMA_UL_N70_SENSE80_TMUS_MR_TMOUS_4.27.531.6 downloaded from htc website nor the OTA.zip downloaded from this thread. The phone keeps having the same Error [132] Signature Error. Or it won't go into the Recovery mode to do sideload of the OTA.zip. If the original Recovery file (from Lollipop) was bad/corrupt, wouldn't the Marshmallow update correct/fix that file?
So, do we have any other idea to upgrade the phone from Android 6.0 to 7.0? Does anyone have a 0PJAIMG.zip for 7.0?
Thanks
vbcomer said:
OK,
I found the 0PJAIMG.zip for version 3.39.531.7 in this forum "https://forum.xda-developers.com/tmobile-one-m9/general/please-read-rooting-using-twrp-t3069022"
I put that on my SD card and was able to update the phone from Lollipop to Marshmallow.
However, after that update, the phone still won't update from Marshmallow to Nougat using the file RUU_HIMA_UL_N70_SENSE80_TMUS_MR_TMOUS_4.27.531.6 downloaded from htc website nor the OTA.zip downloaded from this thread. The phone keeps having the same Error [132] Signature Error. Or it won't go into the Recovery mode to do sideload of the OTA.zip. If the original Recovery file (from Lollipop) was bad/corrupt, wouldn't the Marshmallow update correct/fix that file?
So, do we have any other idea to upgrade the phone from Android 6.0 to 7.0? Does anyone have a 0PJAIMG.zip for 7.0?
Thanks
Click to expand...
Click to collapse
In order to OTA to work which is in this forum you have to be in 3.39.531.41 first find RUU of this version run it then go for OTA.
Noted that you wont be able to update from marshmallow to nougat using RUU you have to use OTA but for that you must be in version 3.39.531.41 .
Ok. I was able to install 3.39.531.41. I will try the OTA now
m_abbas25 said:
In order to OTA to work which is in this forum you have to be in 3.39.531.41 first find RUU of this version run it then go for OTA.
Noted that you wont be able to update from marshmallow to nougat using RUU you have to use OTA but for that you must be in version 3.39.531.41 .
Click to expand...
Click to collapse
I updated to version 3.39.531.41 but I am still unable to get to Recovery mode on my phone. It keeps showing the red triangle with exclamation mark.
So, is that correct that I am now having two choices (besides obviously stay with Marshmallow)
1. Need to somehow fix the recovery mode on the phone? It is a demo unit so I don't know if that has anything with the recovery not working
2. Try to download the 0PJAIMG for 4.27 (Nougat) and install from sd card. I did find the file from AndroidFileHost website, but the phone gave error when it tried to load the zip file from download mode:
12 RU_ZIP_ERROR
FAIL 12 RU_ZIP_ERROR
Do you have a reliable source for the OPJAIMG file for Nougat?
I did a research on the 12 RU_ZIP_ERROR and found an instruction for AT&T from developer Blueberry who suggested "If you're on Marshmallow base, first of all you need to upgrade your firmware and then flash this 0PJAIMG zip file via download mode in otherwise you'll be getting "12 RU_ZIP ERROR" during the flash process. No Wipe Firmware Link: https://www.androidfilehost.com/?fid=745425885120692233"
The above was for AT&T but I found the no_wipe zip for TMobile, however, I don't know how to upgrade the firmware on my phone using one of these files
the firmware no_wipe files are here:
https://www.androidfilehost.com/?w=files&flid=134381
The file I downloaded is "firmware_tmous_4.27.531.6_NoWipe.zip", but like I said above, I don't know how to update the firmware.... Can someone give me some directions?
Update: I renamed the file "firmware_tmous_4.27.531.6_NoWipe.zip" to "0PJAIMG.zip" and tried to update from download mode, but the phone gave error: 8 RU_SIGNATURE_FAIL.
Another research indicated that since the phone is S-ON and Locked, these firmware wouldn't install because they were not signed. Where can I find signed firmware for this phone?
Thanks
vbcomer said:
I updated to version 3.39.531.41 but I am still unable to get to Recovery mode on my phone. It keeps showing the red triangle with exclamation mark.
So, is that correct that I am now having two choices (besides obviously stay with Marshmallow)
1. Need to somehow fix the recovery mode on the phone? It is a demo unit so I don't know if that has anything with the recovery not working
2. Try to download the 0PJAIMG for 4.27 (Nougat) and install from sd card. I did find the file from AndroidFileHost website, but the phone gave error when it tried to load the zip file from download mode:
12 RU_ZIP_ERROR
FAIL 12 RU_ZIP_ERROR
Do you have a reliable source for the OPJAIMG file for Nougat?
I did a research on the 12 RU_ZIP_ERROR and found an instruction for AT&T from developer Blueberry who suggested "If you're on Marshmallow base, first of all you need to upgrade your firmware and then flash this 0PJAIMG zip file via download mode in otherwise you'll be getting "12 RU_ZIP ERROR" during the flash process. No Wipe Firmware Link: https://www.androidfilehost.com/?fid=745425885120692233"
The above was for AT&T but I found the no_wipe zip for TMobile, however, I don't know how to upgrade the firmware on my phone using one of these files
the firmware no_wipe files are here:
https://www.androidfilehost.com/?w=files&flid=134381
The file I downloaded is "firmware_tmous_4.27.531.6_NoWipe.zip", but like I said above, I don't know how to update the firmware.... Can someone give me some directions?
Update: I renamed the file "firmware_tmous_4.27.531.6_NoWipe.zip" to "0PJAIMG.zip" and tried to update from download mode, but the phone gave error: 8 RU_SIGNATURE_FAIL.
Another research indicated that since the phone is S-ON and Locked, these firmware wouldn't install because they were not signed. Where can I find signed firmware for this phone?
Thanks
Click to expand...
Click to collapse
I don't know much now but we can try RUU of 3.39.531.41. It should solve your recovery. But the question is where you can download that?? Try finding a link mean while i am uploading it to my google drive then i will share link. Since i am in third world country it will take time. I will update you as soon as it is uploaded
vbcomer said:
I updated to version 3.39.531.41 but I am still unable to get to Recovery mode on my phone. It keeps showing the red triangle with exclamation mark.
So, is that correct that I am now having two choices (besides obviously stay with Marshmallow)
1. Need to somehow fix the recovery mode on the phone? It is a demo unit so I don't know if that has anything with the recovery not working
Thanks
Click to expand...
Click to collapse
To continue on to recovery mode, try this:
" If a device with a red triangle and exclamation point appears, Hold Power while pressing and releasing Volume Up to continue."
As for the 3.39.531.41 RUU, put the zip from this link into your external SD then boot into fastboot/download mode. From that point on the phone should automatically recognize the .zip and install from there.
https://www.androidfilehost.com/?fid=24438995911969398,
Thank you much! I will try everything you suggested now. I really appreciate your help!
dbs25 said:
To continue on to recovery mode, try this:
" If a device with a red triangle and exclamation point appears, Hold Power while pressing and releasing Volume Up to continue."
As for the 3.39.531.41 RUU, put the zip from this link into your external SD then boot into fastboot/download mode. From that point on the phone should automatically recognize the .zip and install from there.
https://www.androidfilehost.com/?fid=24438995911969398,
Click to expand...
Click to collapse
I downloaded the RUU from above link [https://www.androidfilehost.com/?fid=24438995911969398], but after installing, the phone went from 3.39.531.41 back to 3.39.531.7. Was the above zip file really the 531.41 version?
I tried to reinstall the 0PJAIMG for 531.41 downloaded earlier, but the phone said signature error.
I tried to install using the OTA zip from this link [http://fotadl-az.htc.com/secure/OTA_...kwvabkx6lv.zip] from Recovery mode but the phone said "E3001: Package expects build fingerprint of htc/himaul_tmous/htc_himaul:6.0/MRA58K/690290.41:user/release-keys or htc/himaul_tmous/htc_himaul:7.0/NRD90M/869604.6:user/release-keys; this device has htc/himaul_tmous/htc_himaul:6.0/MRA58K/690290.7:user/relea
E:Error in /sideload/package.zip (Status 7)
Installation aborted
You have any idea to go back to 531.41? Since the OTA message seemed to indicate it expected a 531.41 version?
Thanks
Ok. I was able to get back to 3.39.531.41 by getting the 0PJAIMG from AndroidFileHost.
After that, I went to Recovery Mode (using pwr + vol up after seeing the red triangle), chose Apply Update from SDCard, selected the OTA file for 4.27.531.6. This time It didn't give any error, at the end it appeared to get stuck for a long time at the line Script Succeeded Result was [/preload]. After about an hour, I turned off the phone and on again, now it is stuck at HTC logo splash screen.
Questions here:
1. Was the phone really stuck at the "script succeeded" line?
2. Didn't I wait long enough?
3. What should I have done at that time when it stopped at that "script succeeded" line?
4. What should I do at this splash screen? It has been like that for the last 10 minutes
Thanks
I want to flash my phone with stock firmware, but I cannot find it anywhere.
I am looking for PRA-LX1C738B123.
I own Huawei p8 lite 2017
I wiped my system because I wanted to install other rom, it didn't work so I want to go back to the original.
Unfortunately I wasn't smart enough to do a backup before so I am stuck atm. The bootloader is unlocked and flashing works, I can boot into huawei eRecovery and TWRP. (eRecovery gives the getting package info failed error) I have tried the dload method with other app files, it fails at 5% every time tho.
I tried using Huawei Update Extractor and Firmware Finder but I cannot find the exact firmware.
Could someone help me with installing my firmware? Oh and I am kinda new and it would be nice to get some guides,
Thanks.
I have the same problem but with a different firmware.. now only thing i can do is use dc-phoenix paid software (15$ for 72h of use). I will try that tomorrow as i also can't find exact same firmware it was on my phone.
MobileTechArena said:
I have the same problem but with a different firmware. now only thing i can do is usedc-phoenix paid software (15$ for 72h of use). I will try that tomorrow as i also can't find exact same firmware it was on my phone.
Click to expand...
Click to collapse
Thanks for reply. I will take that into consideration, but from what I see you were looking for PRA-LX1C432B106 and they indeed have the c432 roms there, however they don't seem to have the ones that I have been looking for. They have a list of firmwares online. Anyway good luck.
barnabaXXX said:
Thanks for reply. I will take that into consideration, but from what I see you were looking for PRA-LX1C432B106 and they indeed have the c432 roms there, however they don't seem to have the ones that I have been looking for. They have a list of firmwares online. Anyway good luck.
Click to expand...
Click to collapse
Yes, but any PRA-LX1C432 i tried doesn't work for me, flashing by fastboot. I believe any PRA-LX1 should work on this phone, but i will need to use that dc phoenix software to flash it.
MobileTechArena said:
Yes, but any PRA-LX1C432 i tried doesn't work for me, flashing by fastboot. I believe any PRA-LX1 should work on this phone, but i will need to use that dc phoenix software to flash it.
Click to expand...
Click to collapse
Thanks for making it clear. Please tell me if it worked or not. Thanks.
barnabaXXX said:
I want to flash my phone with stock firmware, but I cannot find it anywhere.
I am looking for PRA-LX1C738B123.
I own Huawei p8 lite 2017
I wiped my system because I wanted to install other rom, it didn't work so I want to go back to the original.
Unfortunately I wasn't smart enough to do a backup before so I am stuck atm. The bootloader is unlocked and flashing works, I can boot into huawei eRecovery and TWRP. (eRecovery gives the getting package info failed error) I have tried the dload method with other app files, it fails at 5% every time tho.
I tried using Huawei Update Extractor and Firmware Finder but I cannot find the exact firmware.
Could someone help me with installing my firmware? Oh and I am kinda new and it would be nice to get some guides,
Thanks.
Click to expand...
Click to collapse
Hello ! I think I could be of some help since I encountered the exact same problem !
edit: well I just realized I can't find your ROM with firmware finder either, sorry for the failed attempt
In your case I'd try with each firmware until one would work or a I tried them all.
You need some utilities first :
- Firmware Finder
https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
It will allow you to find the stock ROM that fits your model
-Huawei UPDATE extractor
https://forum.xda-developers.com/showthread.php?t=2433454
It will allow you to extract the .img files from the firmware previously downloaded.
-fastboot and adb
https://forum.xda-developers.com/showthread.php?t=2317790
The programs that will allow you to flash the .img files.
Now:
1. Find your ROM using firmware finder (the model is usually on the box you received the android in).
2.Extract the necessary .img files : system.img, boot.img, recovery.img.
3.Reboot into the bootloader, connect your device to your computer, open a cmd exe (powershell in my case) by holding shift+right click on the folder containing the .img files and flash each .img file, e.g. for the system file:
"fastboot flash system system.img"
4.then use "fastboot reboot" and after that shutdown your device
(in my case even after flashing the .img files I was greeted by a blank screen, so I shutdown my device holding the power button).
5. Boot into recovery holding vol up + power buttons (be sure to disconnect your device before shutting down and powering it up again) and choose factory reset.
It should then reboot into ROM installation procedure where you will have to follow the same steps as when you booted your device for the first time.
edit: formatting
Also, as far as my limited knowledge goes, there is no custom ROM officially supported for our dear device.
JStrel said:
Hello ! I think I could be of some help since I encountered the exact same problem !
edit: well I just realized I can't find your ROM with firmware finder either, sorry for the failed attempt
In your case I'd try with each firmware until one would work or a I tried them all.
You need some utilities first :
- Firmware Finder
https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
It will allow you to find the stock ROM that fits your model
-Huawei UPDATE extractor
https://forum.xda-developers.com/showthread.php?t=2433454
It will allow you to extract the .img files from the firmware previously downloaded.
-fastboot and adb
https://forum.xda-developers.com/showthread.php?t=2317790
The programs that will allow you to flash the .img files.
Now:
1. Find your ROM using firmware finder (the model is usually on the box you received the android in).
2.Extract the necessary .img files : system.img, boot.img, recovery.img.
3.Reboot into the bootloader, connect your device to your computer, open a cmd exe (powershell in my case) by holding shift+right click on the folder containing the .img files and flash each .img file, e.g. for the system file:
"fastboot flash system system.img"
4.then use "fastboot reboot" and after that shutdown your device
(in my case even after flashing the .img files I was greeted by a blank screen, so I shutdown my device holding the power button).
5. Boot into recovery holding vol up + power buttons (be sure to disconnect your device before shutting down and powering it up again) and choose factory reset.
It should then reboot into ROM installation procedure where you will have to follow the same steps as when you booted your device for the first time.
edit: formatting
Also, as far as my limited knowledge goes, there is no custom ROM officially supported for our dear device.
Click to expand...
Click to collapse
Thanks for help! I tried but i dont' have factory reset option. All I have is Shutdown, reboot and "Download leastest version and recovery" and after I click that all it does is wants internet connection. I logged in to my wifi but it didn't work and I ended up with "getting package info failed screen".
barnabaXXX said:
Thanks for help! I tried but i dont' have factory reset option. All I have is Shutdown, reboot and "Download leastest version and recovery" and after I click that all it does is wants internet connection. I logged in to my wifi but it didn't work and I ended up with "getting package info failed screen".
Click to expand...
Click to collapse
Yes I had the exact same problem, but once I did what I described, by rebooting into recovery (without twrp), I finally had the option to restore factory settings.
I believe the issue is in the fact you don't have access to the stock ROM for your model.
JStrel said:
Yes I had the exact same problem, but once I did what I described, by rebooting into recovery (without twrp), I finally had the option to restore factory settings.
I believe the issue is in the fact you don't have access to the stock ROM for your model.
Click to expand...
Click to collapse
I got rom that allows me to do a factory reset, it's stuck at 99% for like 2 hours now, is it normal? If not what should I do?
barnabaXXX said:
I got rom that allows me to do a factory reset, it's stuck at 99% for like 2 hours now, is it normal? If not what should I do?
Click to expand...
Click to collapse
Unfortunately I can't help you further than what I already posted.
But keep updating in case someone more knowledgeable peeks in.
similar problem....I was fairly good but play store was stuck in pending download....
I did a wipe in TWRP, and ended with a black screen...
I can boot to eRecovery, but it fails.and also to TWRP.
when attached to PC it keeps being seen and unseen as if its stuck in a power on cycle
Any help would be greatly appreciated.
Already Tested
JStrel said:
Hello ! I think I could be of some help since I encountered the exact same problem !
edit: well I just realized I can't find your ROM with firmware finder either, sorry for the failed attempt
In your case I'd try with each firmware until one would work or a I tried them all.
You need some utilities first :
- Firmware Finder
https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
It will allow you to find the stock ROM that fits your model
-Huawei UPDATE extractor
https://forum.xda-developers.com/showthread.php?t=2433454
It will allow you to extract the .img files from the firmware previously downloaded.
-fastboot and adb
https://forum.xda-developers.com/showthread.php?t=2317790
The programs that will allow you to flash the .img files.
Now:
1. Find your ROM using firmware finder (the model is usually on the box you received the android in).
2.Extract the necessary .img files : system.img, boot.img, recovery.img.
3.Reboot into the bootloader, connect your device to your computer, open a cmd exe (powershell in my case) by holding shift+right click on the folder containing the .img files and flash each .img file, e.g. for the system file:
"fastboot flash system system.img"
4.then use "fastboot reboot" and after that shutdown your device
(in my case even after flashing the .img files I was greeted by a blank screen, so I shutdown my device holding the power button).
5. Boot into recovery holding vol up + power buttons (be sure to disconnect your device before shutting down and powering it up again) and choose factory reset.
It should then reboot into ROM installation procedure where you will have to follow the same steps as when you booted your device for the first time.
edit: formatting
Also, as far as my limited knowledge goes, there is no custom ROM officially supported for our dear device.
Click to expand...
Click to collapse
Hello did you already test ???
Here is the solution for every PRA-LX1: [http : // www . htcmania . com / showthread . php ? t=1326478] (sorry for the spaces, but I don't have enough posts written to post external links )
Unfortunately, it's from a spanish forum. I didn't found any problem to follow this tutorial, but maybe for someone it could be a little difficult.
Anyway, it works!
MobileTechArena said:
Yes, but any PRA-LX1C432 i tried doesn't work for me, flashing by fastboot. I believe any PRA-LX1 should work on this phone, but i will need to use that dc phoenix software to flash it.
Click to expand...
Click to collapse
Where did you find the C432 firmware? I can't succees to find it
Flashing to a completely empty phone via DC phoenix or manual via fastboot still didnt got my device started. Sometimes I end up in the eRecovery and sometimes its just stuck at boot.
I tried different version from the hicloud but none so far did the trick. Maybe someone can point me into the right direction so i can finally rescue this phone?
EDIT:
PRA-LX1C432
Sorry cant link to these files since i don't got 10 posts. Maybe PM ?
Copied the Mega TWRP backup (B100) to SD card
Flashed TWRP via fastboot
Disconnected the USB cable
Boot into TWRP
Restored TWRP backup
Restarted phone into fastboot
OEM unlocked it
Got booted into TWRP since no stock recovery there
Booted into fastboot again
flashed stock recovery
Android started to work!
Tried to update to B164 and failed
Reboot
Now it offered B110 and I tried to update to B110. Success.
Iocere said:
Flashing to a completely empty phone via DC phoenix or manual via fastboot still didnt got my device started. Sometimes I end up in the eRecovery and sometimes its just stuck at boot.
I tried different version from the hicloud but none so far did the trick. Maybe someone can point me into the right direction so i can finally rescue this phone?
EDIT:
PRA-LX1C432
Sorry cant link to these files since i don't got 10 posts. Maybe PM ?
Copied the Mega TWRP backup (B100) to SD card
Flashed TWRP via fastboot
Disconnected the USB cable
Boot into TWRP
Restored TWRP backup
Restarted phone into fastboot
OEM unlocked it
Got booted into TWRP since no stock recovery there
Booted into fastboot again
flashed stock recovery
Android started to work!
Tried to update to B164 and failed
Reboot
Now it offered B110 and I tried to update to B110. Success.
Click to expand...
Click to collapse
Yeah, that's the way! It worked for me too!
juanmemo said:
Yeah, that's the way! It worked for me too!
Click to expand...
Click to collapse
Also i noticed everytime a OTA fails you get the full version offered on next boot. So you should get a full B164 aswell after it failed
JStrel said:
Yes I had the exact same problem, but once I did what I described, by rebooting into recovery (without twrp), I finally had the option to restore factory settings.
I believe the issue is in the fact you don't have access to the stock ROM for your model.
Click to expand...
Click to collapse
how can you boot into recovery ? i can only boot into twrp or fastboot & rescue or if i plug the huawei to the pc erecovery ???
---------- Post added at 12:16 AM ---------- Previous post was at 12:13 AM ----------
i have an huawei pra-lx1 c530 it used to boot into pra-lx1c530b111 rooted and twrp but now it doens't boot anymore, i'd like to flash to c530b160 but i can't find the firmware images
tiagoggama said:
Hello did you already test ???
Click to expand...
Click to collapse
Thanks men
I CONFIRM IT WORK PERFECTLY
For the second part go to this link for more detail :
https://boycracked.com/2016/03/14/h...-unbrick-firmware-any-huawei-android-devices/