I always keep getting this no matter how or which way I try to apply the original Ota 30o in recovery:
assert failed: apply_patch_check("/System/framework/apache-xml.jar", "44e4ac783bd6fd314bc8be982d44e972da0abe1f", "eab54a24a53732ddccbe83ff3e8e690fa253ced6")
E: Error in /tmp/sideload/Package.zip
(status 7)
Installation aborted.
I have tried Reinstalling stock, tried twrp, tried cyanogen recovery, all I can think of, still getting this error when applying OTA 30o through recovery.
Sent from my SGP512 using Tapatalk
Running stock
zabih107 said:
I always keep getting this no matter how or which way I try to apply the original Ota 30o in recovery:
assert failed: apply_patch_check("/System/framework/apache-xml.jar", "44e4ac783bd6fd314bc8be982d44e972da0abe1f", "eab54a24a53732ddccbe83ff3e8e690fa253ced6")
E: Error in /tmp/sideload/Package.zip
(status 7)
Installation aborted.
I have tried Reinstalling stock, tried twrp, tried cyanogen recovery, all I can think of, still getting this error when applying OTA 30o through recovery.
Sent from my SGP512 using Tapatalk
Click to expand...
Click to collapse
What rom are you running ..when trying to update to 300.. Do you have xposed framework installed?..Go back to your stock nandroid back up if you have one and update from there..
---------- Post added at 05:03 PM ---------- Previous post was at 05:00 PM ----------
Or update your recovery..whatever you are using..
paztine said:
What rom are you running ..when trying to update to 300.. Do you have xposed framework installed?..Go back to your stock nandroid back up if you have one and update from there..
---------- Post added at 05:03 PM ---------- Previous post was at 05:00 PM ----------
Or update your recovery..whatever you are using..
Click to expand...
Click to collapse
Cyanogen ROM xnph25r (taken from here)
No exposed framework.
No stock nandroid backup.
Sent from my One using Tapatalk
No modified system files at all? No volume mod? No ok Google fix?
Transmitted via Bacon
flash image
paztine said:
What rom are you running ..when trying to update to 300.. Do you have xposed framework installed?..Go back to your stock nandroid back up if you have one and update from there..
---------- Post added at 05:03 PM ---------- Previous post was at 05:00 PM ----------
Or update your recovery..whatever you are using..
Click to expand...
Click to collapse
Or you can just flash the latest cm11S image..its the same as were your are updating to 300..check CM website and download from there..
paztine said:
Or you can just flash the latest cm11S image..its the same as were your are updating to 300..check CM website and download from there..
Click to expand...
Click to collapse
Hmm k i will give this a try later on. Just have to find all those command lines needed to flash all the files within the zip.
Sent from my SGP512 using Tapatalk
no modification
zabih107 said:
Hmm k i will give this a try later on. Just have to find all those command lines needed to flash all the files within the zip.
Sent from my SGP512 using Tapatalk
Click to expand...
Click to collapse
I just dont get it you said you have done nothing to your phone and you get this message when updating to 300..Normally if you have done nothing it will just install with no problem like mine..I update mine to 300 thru stock recovery ..I just flash the update zip from android authority and get the second update after it boots up..Maybe you have done something to your phone..
I have unlocked installed twrp and tried a few different ROMs,
Sent from my One using Tapatalk
rom
zabih107 said:
I have unlocked installed twrp and tried a few different ROMs,
Sent from my One using Tapatalk
Click to expand...
Click to collapse
so what rom are you in now?..One thing you can do is format data thru twrp this will erase everything inside your phone ..but not your OS..Clean install of your current OS..And then try to sideload again..or flash the stock rooted 300..In twrp go to wipe ..format data..it will ask you yes or no..just type yes..This will erase everything insde your phone..Just make sure you are running a good stock or custom rom..
I have tried the wipe data thing. No success. Right now I'm stock locked urooted cyanogen xnphr25r. My suspesions are that the xnphr25r flushable zip that I have got from here is faulty. I will try to flash the original cyanogen image from their site through fastboot I just need those command lines that allows to flash the zip through fastboot.
Sent from my SGP512 using Tapatalk
zabih107 said:
I always keep getting this no matter how or which way I try to apply the original Ota 30o in recovery:
assert failed: apply_patch_check("/System/framework/apache-xml.jar", "44e4ac783bd6fd314bc8be982d44e972da0abe1f", "eab54a24a53732ddccbe83ff3e8e690fa253ced6")
E: Error in /tmp/sideload/Package.zip
(status 7)
Installation aborted.
I have tried Reinstalling stock, tried twrp, tried cyanogen recovery, all I can think of, still getting this error when applying OTA 30o through recovery.
Sent from my SGP512 using Tapatalk
Click to expand...
Click to collapse
I am having the exact same problem. Although I did have xposed installed, but I uninstalled it before attempting the update. Does the exposed launcher make any permanent changes?
Related
hey guys,
I just randomly checked for updates from my stock 1.33 EU ROM and it finds me a 1.54 OTA with Android 2.3.5 update.
Since i am using a ClockworkMod Recovery Image as of now, I would need to shift back to Stock Recovery In order to check out this OTA Update..
I googled a lot to find if this update file was ever noticed before, but i did not find any results on any of the forums.. So i think its kinda new
So, anybody running Stock Recovery can update this from a (unrooted?) S-OFF with a superCID chacha device i think..
Correct me if i am wrong..
Or if you want to shift back from CWM to Stock Recovery, check this >>
http://forum.xda-developers.com/showthread.php?t=1164468
(Credits to Mikevhl and Alex C. for their contributions)
Here is the link to the OTA file >>
http://www.mediafire.com/?111mjddqzda8u2p
Before it gets deleted from the mediafire servers, and if this OTA was worth the find, i would like Alex C. t upload the file to his server for further use of the users here..
INSTRUCTIONS :
1. Install Stock Recovery using CWM
>> Download http://www.mediafire.com/?c39i9ubm11ukggn and rename it to PH06IMG.ZIP and place it in sd card root and install via bootloader
{OR}
install a fresh 1.33 ROM using http://alex.swtesting.ro/downloads/....3033H_7.48.35.14_2_release_204385_signed.exe
2.Rename the OTA_Chacha_HTC_blabla.zip file to update.zip and place it on the SD card root folder.
3. Boot into Bootloader menu (Vol DWN+Power) and select recovery using VOL keys and power button to select.
4. Press Vol Up+Power and install update.zip
5. Wait till update completes.
DEVS, pls post in your comments and changes in this update..
I just found out the OTA file, its upto you guys to find out whats in it and i hope it will be of use to you guys in some way..
thanks again
UPDATE :
you can download a CWM backup of 1.54 here:
http://www.schoelli.cc/media/ChaCha1.54CWM.zip
extract it and put it into root of your sd and restore it via CWM
(CREDITS : schölli)
Will this OTA take my S-OFF..?
sathara said:
Will this OTA take my S-OFF..?
Click to expand...
Click to collapse
I dont think so.. Can any f the DEVs there confirm this pls ??
sathara said:
Will this OTA take my S-OFF..?
Click to expand...
Click to collapse
why should it?
and if it would really happens, just S-OFF it again ))
btw....the download link doesn't work for the 1.33 rom file
confirmed.. it DOES NOT S-ON !!
i am not able to install this update
i installed fresh 1.33 with 1.33....exe
installed afterwards cwm, because the fresh installed wiped it away.
booted into bootloader and then into recovery
wiped dalvik cache and made factory reset
but when i try to install it via zip file it aborts after some time with error 7
It says
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
schölli said:
i am not able to install this update
i installed fresh 1.33 with 1.33....exe
installed afterwards cwm, because the fresh installed wiped it away.
booted into bootloader and then into recovery
wiped dalvik cache and made factory reset
but when i try to install it via zip file it aborts after some time with error 7
It says
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
you cannot install this update via CWM..
Read the OP carefully..
Boot into STOCK RECOVERY.. Not CWM..
ie, install 1.33...exe again and you will get back stock recovery..
abraham89 said:
you cannot install this update via CWM..
Read the OP carefully..
Boot into STOCK RECOVERY.. Not CWM..
ie, install 1.33...exe again and you will get back stock recovery..
Click to expand...
Click to collapse
aaaah now i now what you mean by stock recovery...sry, didn't got it. you mean the original htc recovery with the android figurine and the exclemation mark )
ups my fault
schölli said:
aaaah now i now what you mean by stock recovery...sry, didn't got it. you mean the original htc recovery with the android figurine and the exclemation mark )
ups my fault
Click to expand...
Click to collapse
yea !!! exactly.. u're right
device is back up....now i did it correctly... 1.54 is on the device
CWM is also installable and superuser through CWM works also
su binary update also works this time (which didn't work correctly on 1.52)
i am trying to upload a factory reseted CWM backup
---------- Post added at 01:12 PM ---------- Previous post was at 01:07 PM ----------
you can download a CWM backup of 1.54 here:
http://www.schoelli.cc/media/ChaCha1.54CWM.zip
extract it and put it into root of your sd and restore it via CWM
schölli said:
device is back up....now i did it correctly... 1.54 is on the device
CWM is also installable and superuser through CWM works also
su binary update also works this time (which didn't work correctly on 1.52)
i am trying to upload a factory reseted CWM backup
---------- Post added at 01:12 PM ---------- Previous post was at 01:07 PM ----------
you can download a CWM backup of 1.54 here:
http://www.schoelli.cc/media/ChaCha1.54CWM.zip
extract it and put it into root of your sd and restore it via CWM
Click to expand...
Click to collapse
ill update that to the OP..
Did you notice any changes on this build ??
abraham89 said:
ill update that to the OP..
Did you notice any changes on this build ??
Click to expand...
Click to collapse
nope....everything is a little bit smoother, but i think that was also with the 1.52 version....seems that they only fixed some bugs so far
Oh yeah, nice one.. I'll have to test this as it's official, unlike the leaked ones we had. Great job!
As a side note, you won't get S-ON if you have S-OFF'ed via XTC Clip when doing ROM updates. So it's safe
Alex C. said:
Oh yeah, nice one.. I'll have to test this as it's official, unlike the leaked ones we had. Great job!
As a side note, you won't get S-ON if you have S-OFF'ed via XTC Clip when doing ROM updates. So it's safe
Click to expand...
Click to collapse
we need devs like you to try it out..
I've been using it for two days..
And i feel a very bad WiFi performance.. I dont know if this is ROM dependent..
Can you check that out ??
abraham89 said:
hey guys,
I just randomly checked for updates from my stock 1.33 EU ROM and it finds me a 1.54 OTA with Android 2.3.5 update.
Since i am using a ClockworkMod Recovery Image as of now, I would need to shift back to Stock Recovery In order to check out this OTA Update..
I googled a lot to find if this update file was ever noticed before, but i did not find any results on any of the forums.. So i think its kinda new
So, anybody running Stock Recovery can update this from a (unrooted?) S-OFF with a superCID chacha device i think..
Correct me if i am wrong..
Or if you want to shift back from CWM to Stock Recovery, check this >>
http://forum.xda-developers.com/showthread.php?t=1164468
(Credits to Mikevhl and Alex C. for their contributions)
Here is the link to the OTA file >>
http://www.mediafire.com/?111mjddqzda8u2p
Before it gets deleted from the mediafire servers, and if this OTA was worth the find, i would like Alex C. t upload the file to his server for further use of the users here..
INSTRUCTIONS :
1. Install Stock Recovery using CWM
>> Download http://www.mediafire.com/?c39i9ubm11ukggn and rename it to PH06IMG.ZIP and place it in sd card root and install via bootloader
{OR}
install a fresh 1.33 ROM using http://alex.swtesting.ro/downloads/....3033H_7.48.35.14_2_release_204385_signed.exe
2.Rename the OTA_Chacha_HTC_blabla.zip file to update.zip and place it on the SD card root folder.
3. Boot into Bootloader menu (Vol DWN+Power) and select recovery using VOL keys and power button to select.
4. Press Vol Up+Power and install update.zip
5. Wait till update completes.
DEVS, pls post in your comments and changes in this update..
I just found out the OTA file, its upto you guys to find out whats in it and i hope it will be of use to you guys in some way..
thanks again
UPDATE :
you can download a CWM backup of 1.54 here:
http://www.schoelli.cc/media/ChaCha1.54CWM.zip
extract it and put it into root of your sd and restore it via CWM
(CREDITS : schölli)
Click to expand...
Click to collapse
are there any changes in the new version???
carstenheuer said:
are there any changes in the new version???
Click to expand...
Click to collapse
y do u need to quote the whole post & size5 your words? i felt it kinda rude...
---------- Post added at 11:08 PM ---------- Previous post was at 11:06 PM ----------
schölli said:
device is back up....now i did it correctly... 1.54 is on the device
CWM is also installable and superuser through CWM works also
su binary update also works this time (which didn't work correctly on 1.52)
i am trying to upload a factory reseted CWM backup
---------- Post added at 01:12 PM ---------- Previous post was at 01:07 PM ----------
you can download a CWM backup of 1.54 here:
http://www.schoelli.cc/media/ChaCha1.54CWM.zip
extract it and put it into root of your sd and restore it via CWM
Click to expand...
Click to collapse
so su binary 3.0.3,3.05,3.07 works? gonna give a try thx mate
e.japonica said:
y do u need to quote the whole post & size5 your words? i felt it kinda rude...
---------- Post added at 11:08 PM ---------- Previous post was at 11:06 PM ----------
so su binary 3.0.3,3.05,3.07 works? gonna give a try thx mate
Click to expand...
Click to collapse
sorry!!!
is the default android lockscreen still faulty?
is the default android lockscreen still faulty?
Click to expand...
Click to collapse
what do you mean by faulty? as i don't face any problem with the lock screen in previous version?
---------- Post added at 01:07 AM ---------- Previous post was at 12:48 AM ----------
can i request a clean 1.54 zip without su/or a backup without su? (without any modification) Thanks in advance :0
e.japonica said:
what do you mean by faulty? as i don't face any problem with the lock screen in previous version?
---------- Post added at 01:07 AM ---------- Previous post was at 12:48 AM ----------
can i request a clean 1.54 zip without su/or a backup without su? (without any modification) Thanks in advance :0
Click to expand...
Click to collapse
I am getting another ChaCha today (those are now our new company phones) and i will s-off it, update it to 1.54 and will zip it without any modification tonight.
hope you can wait a little bit )
I'm unable to Install Stock Recovery img, everytime after the bootloader loading the file,
a line saying "parsing PH06IMG.zip" then nothing happened, retun to bootloader,
and cwm image still there
Help,
I rooted my VZW s3 and all was good until i tried to update to a CM10 rom..
It would not install the zip file.. I followed all the guides about backing up the imei file ect.. and I used the correct recovery.. it would not install..I kept getting erros with the ROM zip files I downloaded. so i tried the ez recovery app and installed TWRP.. I like that and have used it in the past.. well I forgot that I cant restore a backup from CWM. so now im stuck bootlooping into TWRP recovery.
Any help?
I was installing TWRP while my GF was talking to me. Not that I'm blaming her or anything but I failed to add the "dd" during the manual install. Now I'm downloading the stock rom and going to try Odin to get my phone functioning again.
Twrp doesn't support kexec, so it will only boot stock based ROM's
sent from locked bootloadrer SGS3 running a custom kernel
wera750 said:
Twrp doesn't support kexec, so it will only boot stock based ROM's
sent from locked bootloadrer SGS3 running a custom kernel
Click to expand...
Click to collapse
can somebody send me a link to a stock rom so I can start this over?
I cant even get adb to recognize my device when its on.. I only have TWRP bootlooping into recovery...
Thanks..
sidn3y said:
I was installing TWRP while my GF was talking to me. Not that I'm blaming her or anything but I failed to add the "dd" during the manual install. Now I'm downloading the stock rom and going to try Odin to get my phone functioning again.
Click to expand...
Click to collapse
Not saying this will help you, but it did with me. I have no idea how.
Tried vol down/home/power and it booted into the custom rom screen. Cancelled that. It rebooted normally..
---------- Post added at 09:48 PM ---------- Previous post was at 09:48 PM ----------
kwiksilvr said:
can somebody send me a link to a stock rom so I can start this over?
I cant even get adb to recognize my device when its on.. I only have TWRP bootlooping into recovery...
Thanks..
Click to expand...
Click to collapse
http://stockroms.net/file/GalaxyS3/SGH-I535/StockROMS.net-SCH-I535_VZW_Verizon.zip
Hi,
Sorry for my english,
I have a HTC one X endeavoru and I try to install viper ROM, and I bricked It.
I can enter to the fastboot menu but when I take the recovery opcion the cellphone reboot...
I try to reflash the clockwork but I keep getting the same
Any idea how I can get my cellphone back?
Btw I have S-OFF.
Thanks
I flash TWRP and I saw the screen of the TWRP for 0.2 seg and then it reboot again and again, the same thing happens with the clockwork, I see it for 0.2 seg and then It reboot
Flash an ruu then unlock your bootloader and reflash your recovery
Sent from my HTC One X using xda app-developers app
---------- Post added at 11:27 AM ---------- Previous post was at 11:27 AM ----------
johnnyp12321 said:
Flash an ruu then unlock your bootloader and reflash your recovery
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Sorry you don't have to unlock your s-off
Sent from my HTC One X using xda app-developers app
rakax said:
Hi,
Sorry for my english,
I have a HTC one X endeavoru and I try to install viper ROM, and I bricked It.
I can enter to the fastboot menu but when I take the recovery opcion the cellphone reboot...
I try to reflash the clockwork but I keep getting the same
Any idea how I can get my cellphone back?
Btw I have S-OFF.
Thanks
I flash TWRP and I saw the screen of the TWRP for 0.2 seg and then it reboot again and again, the same thing happens with the clockwork, I see it for 0.2 seg and then It reboot
Click to expand...
Click to collapse
You're in the wrong forum, that could be why you bricked. You want the international one x forum. The one xl forums are for the dual core version.
For the ENDEAVORU, you want to be here: http://forum.xda-developers.com/forumdisplay.php?f=1533
This forum is for the EVITA. Its a good thing you mentioned you had the ENDEAVORU. It saved some frustration and confusion of us possibly giving you the wrong advice.
If the screen comes on, you almost certainly aren't bricked. You can recover, its just a matter of heading to the correct forum, and getting the proper direction.
Doesn't Enter in Recovery Mode
Hello Sir,
i just install twrp on my evita. bt when i enter in d recovery mode there's a red colored error comes. THIS BUILD IS FOR DEVELOPMENT PURPOSE ONLY. wat to do now?
i had also install GOO Manager. and when i enters in reboot recovery it says "attempting to reboot recovery,it fails.. yo may want to perform the operation manually. please help me out of this problem.
mkumar55533 said:
Hello Sir,
i just install twrp on my evita. bt when i enter in d recovery mode there's a red colored error comes. THIS BUILD IS FOR DEVELOPMENT PURPOSE ONLY. wat to do now?
i had also install GOO Manager. and when i enters in reboot recovery it says "attempting to reboot recovery,it fails.. yo may want to perform the operation manually. please help me out of this problem.
Click to expand...
Click to collapse
The red text you see when the phone boots up is normal for a modified device, don't worry about that. To get to recovery follow these steps: turn phone off, hold volume down then hold power so you're holding both buttons together, after a few seconds let go of power but keep holding volume down until you reach the white screen with text, this is your bootloader, from here you can use the volume buttons to scroll and the power button to select recovery.
Sent from my Evita
timmaaa said:
The red text you see when the phone boots up is normal for a modified device, don't worry about that. To get to recovery follow these steps: turn phone off, hold volume down then hold power so you're holding both buttons together, after a few seconds let go of power but keep holding volume down until you reach the white screen with text, this is your bootloader, from here you can use the volume buttons to scroll and the power button to select recovery.
Sent from my Evita
Click to expand...
Click to collapse
Sir I've done this process and wat about written above is d issue. when i go in the recovery option under bootloader that error comes...
so plz tell me any other way to resolve this problem
You don't have TWRP recovery installed then. Do you have an unlocked bootloader? What method did you use to try to install recovery?
Sent from my Evita
mkumar55533 said:
Sir I've done this process and wat about written above is d issue. when i go in the recovery option under bootloader that error comes...
Click to expand...
Click to collapse
That is not an error message. That message will always come up once you have modified the phone. That screen is a boot splash screen that comes up normally, but you are frozen or stuck there either by absence of recovery, or a damaged recovery.
How did you originally install TWRP, where did you get the file from, and what was the file named?
redpoint73 said:
That is not an error message. That message will always come up once you have modified the phone. That screen is a boot splash screen that comes up normally, but you are frozen or stuck there either by absence of recovery, or a damaged recovery.
How did you originally install TWRP, where did you get the file from, and what was the file named?
Click to expand...
Click to collapse
[TOOL] [10.25.13] WinDroid HTC One XL Toolkit v1.1 | Unlock | Root | Flash | S-OFF
from
http://forum.xda-developers.com/showthread.php?t=2470972
Do it manually instead. Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now try entering recovery.
Sent from my Evita
mkumar55533 said:
[TOOL] [10.25.13] WinDroid HTC One XL Toolkit v1.1 | Unlock | Root | Flash | S-OFF
from
http://forum.xda-developers.com/showthread.php?t=2470972
Click to expand...
Click to collapse
No one have any solution of this problem??
Did you not read my post directly above yours??
Sent from my Evita
timmaaa said:
Did you not read my post directly above yours??
Sent from my Evita
Click to expand...
Click to collapse
it stucks on command promt
written only <waiting for device>
??
Is your phone connected in fastboot mode? Do you have the correct drivers installed?
Sent from my Evita
timmaaa said:
Is your phone connected in fastboot mode? Do you have the correct drivers installed?
Sent from my Evita
Click to expand...
Click to collapse
hey thank u so much TWRP successfully installed n works. Bt in TWRP first i had backup my stock rom. then i go to wipe n wiped successfully. and then when i installed custom ROM ( cm-10.1.3-evita, downloaded from cyanogen official site) it fails.. and i had also installed SuperSu
Which version of TWRP did you install? Exactly what error do you get when flashing the ROM?
Sent from my Evita
timmaaa said:
Which version of TWRP did you install? Exactly what error do you get when flashing the ROM?
Sent from my Evita
Click to expand...
Click to collapse
TWRP 2.6 provided by someone posted above..
---------- Post added at 11:58 PM ---------- Previous post was at 11:51 PM ----------
mkumar55533 said:
TWRP 2.6 provided by someone posted above..
Click to expand...
Click to collapse
Checking for MD5 file....
Skipping MD5 check: no MD5 file found.
assert failed:getprop("ro.bootloader") == "2.14.0000"
E:Error executing updater binary in zip '/sdcard/Roms/cm-10.1.3-evita.zip
Error flashing zip '/sdcard/Roms/cm-10.1.3-evita.zip'
Updating partition details....
Failed
---------- Post added 8th December 2013 at 12:14 AM ---------- Previous post was 7th December 2013 at 11:58 PM ----------
mkumar55533 said:
TWRP 2.6 provided by someone posted above..
---------- Post added at 11:58 PM ---------- Previous post was at 11:51 PM ----------
Checking for MD5 file....
Skipping MD5 check: no MD5 file found.
assert failed:getprop("ro.bootloader") == "2.14.0000"
E:Error executing updater binary in zip '/sdcard/Roms/cm-10.1.3-evita.zip
Error flashing zip '/sdcard/Roms/cm-10.1.3-evita.zip'
Updating partition details....
Failed
Click to expand...
Click to collapse
can u plz answer?
---------- Post added at 01:10 AM ---------- Previous post was at 12:14 AM ----------
mkumar55533 said:
TWRP 2.6 provided by someone posted above..
---------- Post added at 11:58 PM ---------- Previous post was at 11:51 PM ----------
Checking for MD5 file....
Skipping MD5 check: no MD5 file found.
assert failed:getprop("ro.bootloader") == "2.14.0000"
E:Error executing updater binary in zip '/sdcard/Roms/cm-10.1.3-evita.zip
Error flashing zip '/sdcard/Roms/cm-10.1.3-evita.zip'
Updating partition details....
Failed
---------- Post added 8th December 2013 at 12:14 AM ---------- Previous post was 7th December 2013 at 11:58 PM ----------
can u plz answer?
Click to expand...
Click to collapse
HBOOT details
*** UNLOCKED ***
EVITA PVT SHIP S-OFF
CID-HTC_044
HBOOT-2.15.0000
Your problem is that the ROM requires a certain set of firmware to be installed on your device for the ROM to install. You need to run the 3.18 RUU, this will install the correct firmware on your device for that particular ROM you want to flash.
Sent from my Evita
timmaaa said:
Your problem is that the ROM requires a certain set of firmware to be installed on your device for the ROM to install. You need to run the 3.18 RUU, this will install the correct firmware on your device for that particular ROM you want to flash.
Sent from my Evita
Click to expand...
Click to collapse
Can u please tell me the process to install 3.18 RUU... or some videos??
Hello all,
I have been going slightly mad today trying to get my mate 7 2GB back from CWM to stock recovery. The main problem is that I do not have a stock recovery image. But after being shown where to find one, I noticed that I could not get it successfully flashed either.
Since I do not really know how to do this, I used flashify, but that did not work and either returned me to the CWM or sent me to rescue.
Can someone help me to a) get a stock recovery image for the Mate 7 version MT7-L09 and b) show me how to properly flash it?
Find stock recovery is easy.. only a question why flashify don't work for you? It work fine for me... your device is rooted?
djzero86 said:
Find stock recovery is easy.. only a question why flashify don't work for you? It work fine for me... your device is rooted?
Click to expand...
Click to collapse
Hi @dzjero86, my device is rooted and I am on the B137SP03 version atm, using CWM. Don't know why Flashify is not working for flashing a recovery image. It works fine to flash a CWM recovery. Maybe I have the wrong stock recovery... If you can find it, can you send me the link or add it as an attachment here?
Please guys help me to . i have that same problem i have been trying to flash the stock recovery again but i couldn't even with flashify after i flash i takes me to bootloader screen and it shows me a fun_error message
I have a tl-10 device
dekraan said:
Hi @dzjero86, my device is rooted and I am on the B137SP03 version atm, using CWM. Don't know why Flashify is not working for flashing a recovery image. It works fine to flash a CWM recovery. Maybe I have the wrong stock recovery... If you can find it, can you send me the link or add it as an attachment here?
Click to expand...
Click to collapse
A way to find the stock recovery is : download the whole B137SP03 Rom from the Huawei site , and use a tool called "Firmware unpacker for Huawei" whit this tool you can extract the recovery.img from the Rom and try to flash it using flashify
Firmware unpacker
http://forum.xda-developers.com/mate-7/development/firmware-unpacker-huawei-t2879754
Rom
http://forum.xda-developers.com/mate-7/general/firmware-huawei-ascend-mate-7-b137sp03-t3041629
Pd : I am not a developer or anything similar but I have some years of experience rooting and etc ...
---------- Post added at 10:12 AM ---------- Previous post was at 10:00 AM ----------
Ali_adel_medo said:
Please guys help me to . i have that same problem i have been trying to flash the stock recovery again but i couldn't even with flashify after i flash i takes me to bootloader screen and it shows me a fun_error message
I have a tl-10 device
Click to expand...
Click to collapse
You have a unlocked bootloader???
Yes i have unlocked and rooted the phone using the cwm recovery and now a i can't flash the stock recovery any more
Ali_adel_medo said:
Yes i have unlocked and rooted the phone using the cwm recovery and now a i can't flash the stock recovery any more
Click to expand...
Click to collapse
Do you tried flash via fastboot ?
fastboot flash recovery recovery.img
Or try to use this tool
http://forum.xda-developers.com/mat...custom-recovery-tool-mt7-l10-l10-mt7-t3022424
This should work.
The fast boot just stucks at waiting for device
And the tool you send says that the stock recovery works only on tl_09 and my device is tl_10
djzero86 said:
A way to find the stock recovery is : download the whole B137SP03 Rom from the Huawei site , and use a tool called "Firmware unpacker for Huawei" whit this tool you can extract the recovery.img from the Rom and try to flash it using flashify
Firmware unpacker
http://forum.xda-developers.com/mate-7/development/firmware-unpacker-huawei-t2879754
Rom
http://forum.xda-developers.com/mate-7/general/firmware-huawei-ascend-mate-7-b137sp03-t3041629
Pd : I am not a developer or anything similar but I have some years of experience rooting and etc ...
---------- Post added at 10:12 AM ---------- Previous post was at 10:00 AM ----------
You have a unlocked bootloader???
Click to expand...
Click to collapse
Ok, I couldnt access your firmware unpacker, but I did manage to use the tool you suggested.
I have a different recovery screen, but is this the right one? It has EMUI large in centre screen and the options reboot system now, wipe data/factory reset and wipe cache partition.
If this is the correct one, and I am already on the D137SP03 ROM, I should be able to locally update right?
I tried this, and got a lot further this time, but my phone gave an error message during the update. Do I need to flash the original B137SP03 rom again, even though I am already on it?
I think you maybe can flash using adb commands and also you need adb drivers working
---------- Post added at 11:23 AM ---------- Previous post was at 11:15 AM ----------
dekraan said:
Ok, I couldnt access your firmware unpacker, but I did manage to use the tool you suggested.
I have a different recovery screen, but is this the right one? It has EMUI large in centre screen and the options reboot system now, wipe data/factory reset and wipe cache partition.
If this is the correct one, and I am already on the D137SP03 ROM, I should be able to locally update right?
I tried this, and got a lot further this time, but my phone gave an error message during the update. Do I need to flash the original B137SP03 rom again, even though I am already on it?
Click to expand...
Click to collapse
Ok.... you have the stock recovery now???
djzero86 said:
I think you maybe can flash using adb commands and also you need adb drivers working
---------- Post added at 11:23 AM ---------- Previous post was at 11:15 AM ----------
Ok.... you have the stock recovery now???
Click to expand...
Click to collapse
I think so. If stock looks like I described: black screen, large EMUI logo, and the options reboot system now, wipe data/factory reset and wipe cache partition?
That's right... you have stock recovery... sometimes the update fail if the UPDATE.APP is on the internal storage.. try to flash from a micro sd card or re-download the update ....
English is not my first language...
djzero86 said:
That's right... you have stock recovery... sometimes the update fail if the UPDATE.APP is on the internal storage.. try to flash from a micro sd card or re-download the update ....
English is not my first language...
Click to expand...
Click to collapse
Great, thank you for your fantastic help!
I will get a new micro-sd card tomorrow, and will try it right away!
Good luck... come back to report
djzero86 said:
Good luck... come back to report
Click to expand...
Click to collapse
No luck so far.... I've downloaded the update.zip, put it in my mnt/ext_sdcard/dload folder and start the local update. It begins OK, as the progress bar moves along. But after about 25% it shoots to the end, and then I get an update failed screen with a red exclamation mark.
What could I try to get it to work??
dekraan said:
No luck so far.... I've downloaded the update.zip, put it in my mnt/ext_sdcard/dload folder and start the local update. It begins OK, as the progress bar moves along. But after about 25% it shoots to the end, and then I get an update failed screen with a red exclamation mark.
What could I try to get it to work??
Click to expand...
Click to collapse
Ok, I just reinstalled the B137P03 version from the how to install lollipop thread, and that went successful. Now going to try the update.zip! Keep you posted
Ah, now we're talking It seems to have worked. Phone is now showing 'Android is upgrading' and 'optimising app.....'
Great! It does seem strange I had to reinstall the B137SP03 rom, but that did the trick!
after trying to flash with twrp merlin .img file my phone is stuck on the warning bootloader unlocked screen . please help me as this is the only device that i have right now.
Merlin is the codename for Moto G Turbo, is that your device?
siredux said:
Merlin is the codename for Moto G Turbo, is that your device?
Click to expand...
Click to collapse
yes that is . motorola g turbo. what am i supposed to do now with my phone stuck on warning screen??
Are you hit ok when twrp ask to install supersu? If yes , restore your twrp backup and install supersu by your own , supersu 2.62.3 has no bootloops.
antonyjude30 said:
Are you hit ok when twrp ask to install supersu? If yes , restore your twrp backup and install supersu by your own , supersu 2.62.3 has no bootloops.
Click to expand...
Click to collapse
the only thing my phone does it stops on the bootloader screen i can only access only the recovery mode somehow and nothing else. it shows the teamwin screen. i dont knw wat to do after that. it was the latest supersu zip and i dont know wat went wrong.
flash the stock recovery or flash stock firmware.
xlr8sonic said:
the only thing my phone does it stops on the bootloader screen i can only access only the recovery mode somehow and nothing else. it shows the teamwin screen. i dont knw wat to do after that. it was the latest supersu zip and i dont know wat went wrong.
Click to expand...
Click to collapse
Did you make a TWRP back up before flashing SuperSU?
MrTooPhone said:
Did you make a TWRP back up before flashing SuperSU?
Click to expand...
Click to collapse
no i did not.
what can i do now
HelpMeruth said:
flash the stock recovery or flash stock firmware.
Click to expand...
Click to collapse
how can i do that ?
xlr8sonic said:
no i did not.
what can i do now
Click to expand...
Click to collapse
Without a backup, your only option is to re-flash stock firmware.
xlr8sonic said:
yes that is . motorola g turbo. what am i supposed to do now with my phone stuck on warning screen??
Click to expand...
Click to collapse
If I were you I would download stock firmware and flash it via fastboot to avoid any further inconviniences
I recommend flashing your factory firmware, which can easily be found on the forums here
siredux said:
If I were you I would download stock firmware and flash it via fastboot to avoid any further inconviniences
Click to expand...
Click to collapse
its is showing baseband error .. will it be gone if if i flash its firmware
xlr8sonic said:
its is showing baseband error .. will it be gone if if i flash its firmware
Click to expand...
Click to collapse
Sorry man , baseband errors normally result in no mobile network and ability to make phone calls :/. When I flashed marshmallow on my phone , it said not found next to baseband. You may want to fully flash MM then when it gets to bootloader unlocked screen , wait a few minutes. If it does nothing, try flashing twrp recovery and flashing a lollipop custom rom.
---------- Post added at 12:47 PM ---------- Previous post was at 12:47 PM ----------
xlr8sonic said:
its is showing baseband error .. will it be gone if if i flash its firmware
Click to expand...
Click to collapse
Also what baseband error are you getting ?
therealduff1 said:
Sorry man , baseband errors normally result in no mobile network and ability to make phone calls :/. When I flashed marshmallow on my phone , it said not found next to baseband. You may want to fully flash MM then when it gets to bootloader unlocked screen , wait a few minutes. If it does nothing, try flashing twrp recovery and flashing a lollipop custom rom.
---------- Post added at 12:47 PM ---------- Previous post was at 12:47 PM ----------
Also what baseband error are you getting ?
Click to expand...
Click to collapse
i attatched the imafe of the screen . i dnt knw exactluy wat baseband error it is
xlr8sonic said:
i attatched the imafe of the screen . i dnt knw exactluy wat baseband error it is
Click to expand...
Click to collapse
i also tried to flash the firmware .. but that showed zip signature varification. i also attatched the image for that
xlr8sonic said:
i also tried to flash the firmware .. but that showed zip signature varification. i also attatched the image for that
Click to expand...
Click to collapse
I had that error when flashing a new logo, I simply unchecked "check zip signature" in TWRP. All flashed OK.
MrTooPhone said:
I had that error when flashing a new logo, I simply unchecked "check zip signature" in TWRP. All flashed OK.
Click to expand...
Click to collapse
it says could not find ,META-INF/com/google/android/update-binary, int the zip file
error installing zip file xt1557_merlin_ritasia_6.0
Mate , no one noticed that you are trying to flash the ota zip in recovery. you are not meant to do that. Flash it using Fastboot. Go download Motorola device manager to get the right drivers, and get minimal adb and fastboot, when you have done that, come back here !
---------- Post added at 10:21 PM ---------- Previous post was at 10:20 PM ----------
xlr8sonic said:
i also tried to flash the firmware .. but that showed zip signature varification. i also attatched the image for that
Click to expand...
Click to collapse
You do realise you are trying to flash firmware files via recovery right..?
You are meant to extract the zip on the pc and then flash the files using fastboot commands
---------- Post added at 10:22 PM ---------- Previous post was at 10:21 PM ----------
MrTooPhone said:
I had that error when flashing a new logo, I simply unchecked "check zip signature" in TWRP. All flashed OK.
Click to expand...
Click to collapse
that trying to flash ota firmware files in twrp . that's why it failed
xlr8sonic said:
i also tried to flash the firmware .. but that showed zip signature varification. i also attatched the image for that
Click to expand...
Click to collapse
Try using mfastboot instead of fastboot, go with 6.0 firmware, make sure you flash all sparsechunks included. Baseband should be restored