Hello,
I have Huawei MediaPad 7 Youth 2. I builded a CWM 6.0 from CM10.2 repositories. When i apply update.zip via recovery, its going to middle , then loading and then says "installation failed" without any more informations. How to get more infos?
Thanks
GAMELASTER said:
Hello,
I have Huawei MediaPad 7 Youth 2. I builded a CWM 6.0 from CM10.2 repositories. When i apply update.zip via recovery, its going to middle , then loading and then says "installation failed" without any more informations. How to get more infos?
Thanks
Click to expand...
Click to collapse
So, you're trying to flash an update.zip with your CWM on the stock recovery? This would explain it, as you can not install updates not signed by Huawei in the stock recovery.
es0tericcha0s said:
So, you're trying to flash an update.zip with your CWM on the stock recovery? This would explain it, as you can not install updates not signed by Huawei in the stock recovery.
Click to expand...
Click to collapse
Well, maybe u are right. Actually, im new to this.
But, when i updating a Signed recovery, its going to middle, then loading bar and installation failed. Unsigned package is at start failed.
Well, how to flash it? I have available just root, and fastboot i cant execute (when i holding volume up and power, its just boot up a tablet). Is another way to flash it? (inside android or how?)
And another question, where i can test my recovery if is something broken or similiar to be secured?
Thankie
http://forum.xda-developers.com/android/development/alpha-clockworkmod-huawei-mediapad-7-t2967318
Some info there and a link to another site that claims to have recovery working and a LP rom. Definitely proceed with caution and make sure you have access to the original firmware and know how to reload before you proceed. Good luck.
es0tericcha0s said:
http://forum.xda-developers.com/android/development/alpha-clockworkmod-huawei-mediapad-7-t2967318
Some info there and a link to another site that claims to have recovery working and a LP rom. Definitely proceed with caution and make sure you have access to the original firmware and know how to reload before you proceed. Good luck.
Click to expand...
Click to collapse
Okey, thank you. But you think, this will be work too on Youth 2 too?
Ah, my mistake! I thought it was the same one. Don't try that then. Lol
Related
I accidentally flashed TWRP to the boot instead of recovery. Whenever I turn on the phone it goes straight to TWRP. As it stands the phone is unsuable! AS far I understand it the way to fix this is to flash the phone's original boot.img to the boot. Is this correct? If so my phone is MT2L03 with the 5.1 update. Does anynone know of any link or could anyone PLEASE share their stock boot.img with me. I really need help!
Thank You.
Boot image is part of OS. If you want to install CM12, while you are in twrp, just transfer the cm12 rom and gapp from pc to your sdcard, then flash both. You get complete cm12 with its boot image.
But if you want stock boot image back, you can just flash the stock firmware using the 3 button boot. It is available in the "official stock firmware" section in the INDEX page: http://forum.xda-developers.com/showthread.php?t=3149530
If you have difficulties doing that, let us know. I maybe can find it somewhere, but to be honest, I don't use stock anymore once CM is out.
Thanks. CM12 flash problem
I was able to find a b321 boot.img online so problem solved. The cm 12 flash is not working for me I keep getting an error while flashing TWRP keeps telling me that the cm 12.1mt2 file is specifically for the b322 bootloader but that my bootloader is "unknown" so its unable to flash.
Still haven't figured out what the problem is. I tried to install the specific 2.8.7.0 TWRP for the mt2l03 via the app but it gives me an error. When I try to flash it in recovery it still has no effect on the cm install. Maybe someone would be kind enough to guide me.
fcbfan2k said:
I was able to find a b321 boot.img online so problem solved. The cm 12 flash is not working for me I keep getting an error while flashing TWRP keeps telling me that the cm 12.1mt2 file is specifically for the b322 bootloader but that my bootloader is "unknown" so its unable to flash.
Still haven't figured out what the problem is. I tried to install the specific 2.8.7.0 TWRP for the mt2l03 via the app but it gives me an error. When I try to flash it in recovery it still has no effect on the cm install. Maybe someone would be kind enough to guide me.
Click to expand...
Click to collapse
Try reading the OP for that ROM. It clearly states you have to be in b322.... Reading is key.
Moody66 said:
Try reading the OP for that ROM. It clearly states you have to be in b322.... Reading is key.
Click to expand...
Click to collapse
i do have b322. So the problem is not that. the problem was already there even before i booted with the b321.img. In any case the img is for boot only. It is not the build.
Also twrp, have you install the twrp listed in that same page? other twrp version doesn't work.
Edit, saw you mentioned already that install twrp error using app. So try install the correct twrp in bootloader.
fcbfan2k said:
i do have b322. So the problem is not that. the problem was already there even before i booted with the b321.img. In any case the img is for boot only. It is not the build.
Click to expand...
Click to collapse
If you flashed b321 boot image you are not on b322 boot... And the correct twrp is found in the same OP....
I have a Nexus 6P that has some weird issue where it is not being recognized by any PC or any USB port as a USB device. So I can't get it to work with fastboot as an adb device. It has stock android 6.0.1 on it and TWRP. This is how I got it. I think there is something wrong with the software not allowing the USB mode to work properly so I wanted to flash to another stock image. I've already downloaded the stock anglr image and uses Google Drive to transfer the files over, both the complete image and also the independent IMG files. Is it possible to use TWRP to flash the phone back to stock?
Two questions before I venture an answer -
a. When you mean flash back to stock, I am assuming you mean your TWRP stays and all you want is to flash stock android. Right?
b. Your custom recovery is TWRP right?
tropicanapure said:
Two questions before I venture an answer -
a. When you mean flash back to stock, I am assuming you mean your TWRP stays and all you want is to flash stock android. Right?
b. Your custom recovery is TWRP right?
Click to expand...
Click to collapse
a: Yes, unrooted and a different stock image to see if maybe this version on the phone is buggy with the USB connection not working.
b: Yes, TWRP 2.8.7.2
Great. Then the simple answer is yes. Subject to the fact that whatever you trying to flash is "flashable" (i.e. usable by TWRP). To be honest I have been flashing using TWRP for last 3 years and never once have I used a PC.
Slightly longer answer. To do this
a. (ALWAYS) Backup original Android install using TWRP
b. Factory reset (NOT wipe - unless you know what you are doing!)
c. Look for the Flashable ZIP containing your stock image - and flash.
and voila! You are back to stock!
Good luck!
tmar89 said:
a: Yes, unrooted and a different stock image to see if maybe this version on the phone is buggy with the USB connection not working.
b: Yes, TWRP 2.8.7.2
Click to expand...
Click to collapse
tropicanapure said:
Two questions before I venture an answer -
a. When you mean flash back to stock, I am assuming you mean your TWRP stays and all you want is to flash stock android. Right?
b. Your custom recovery is TWRP right?
Click to expand...
Click to collapse
tropicanapure said:
Great. Then the simple answer is yes. Subject to the fact that whatever you trying to flash is "flashable" (i.e. usable by TWRP). To be honest I have been flashing using TWRP for last 3 years and never once have I used a PC.
Slightly longer answer. To do this
a. (ALWAYS) Backup original Android install using TWRP
b. Factory reset (NOT wipe - unless you know what you are doing!)
c. Look for the Flashable ZIP containing your stock image - and flash.
and voila! You are back to stock!
Good luck!
Click to expand...
Click to collapse
Thanks. So if I download the stock android image from google developers page, I can copy that over to the device and use TWRP to flash it?
Actually, I've been reading that I cannot flash a factory image with recovery, only fastboot. But fastboot doesn't work for me because device won't recognize when connected with USB (trust me, I tried everything with drivers and cables, computers, etc). I think I need to find a flashable stock image for my device.
tmar89 said:
Thanks. So if I download the stock android image from google developers page, I can copy that over to the device and use TWRP to flash it?
Click to expand...
Click to collapse
No. Which is why I said - "flashable". I dont have a Nexus 6p so I dont know where you can find a TWRP flashable stock image for that device. But a quick search of your device specific sub-forum on XDA yielded this link.
The link in the first para should help you find a "flashable factory/ stock image". I would suggest you follow instructions on that post and ask further questions there as the folks in there will have the same device as you and provide better help.
Again, good luck!
Thanks, I appreciate this advice as it helps.
tmar89 said:
Thanks, I appreciate this advice as it helps.
Click to expand...
Click to collapse
No worries. Pass it on
PS: Here's another XDA thread that has a flashable version of the STOCK rom.
PPS: Found via Google search terms nexus 6p stock rom flashable
Hi, I need help with my phone, I accidentally changed the permissions (using ROM Toolbox Lite) from the system folder making the phone crash shortly after. Now it shows the Alcatel logo and shuts off and back on in recovery mode.
I'm new with adb and CWM/TWRP stuff, but I can't find the device using adb (I installed the usb drivers correctly) , it only finds on sideload and even then I get "error: closed"...and with CWM/TWRP I can't use sideload because:
"You need adb 1.0.32 or newer to sideload to this devices" (and I used 1.0.36)
And with zip file (CWM) method I get:
"E:failed to verify whole-file signature
E:signature verification failed
Installation aborted"
Please help, I can't find the stock rom for this phone
Did you find a solution? HAve a Bootloop too
Prestnaut said:
Did you find a solution? HAve a Bootloop too
Click to expand...
Click to collapse
Nope unfortunately
Any news ?
HAve a Bootloop too , after trying to unroot with kingo .
Need stock boot.img or recovery.img in order to build custom rom from source
VTRF8FF.TMP said:
Hi, I need help with my phone, I accidentally changed the permissions (using ROM Toolbox Lite) from the system folder making the phone crash shortly after. Now it shows the Alcatel logo and shuts off and back on in recovery mode.
I'm new with adb and CWM/TWRP stuff, but I can't find the device using adb (I installed the usb drivers correctly) , it only finds on sideload and even then I get "error: closed"...and with CWM/TWRP I can't use sideload because:
"You need adb 1.0.32 or newer to sideload to this devices" (and I used 1.0.36)
And with zip file (CWM) method I get:
"E:failed to verify whole-file signature
E:signature verification failed
Installation aborted"
Please help, I can't find the stock rom for this phone
Click to expand...
Click to collapse
Hi, My 6044d also in boot loop, not rooted so I can't get stock boot.img or recovery.img in order to compile CWM and CM from source for this particular phone. Please someone post it and of course, when compiled I'll post back de results for all of us that need a custom ROM for this phone. It's crazy that this phone is not so popular and the common custom roms don't have one for it out of the box, that's why I decided to compile it myself, but I can't get my boot.img or recovery.img to configure build environment for this especific phone.
Thanks in advance!
miuserdexda said:
Hi, My 6044d also in boot loop, not rooted so I can't get stock boot.img or recovery.img in order to compile CWM and CM from source for this particular phone. Please someone post it and of course, when compiled I'll post back de results for all of us that need a custom ROM for this phone. It's crazy that this phone is not so popular and the common custom roms don't have one for it out of the box, that's why I decided to compile it myself, but I can't get my boot.img or recovery.img to configure build environment for this especific phone.
Thanks in advance!
Click to expand...
Click to collapse
Hey, sorry for taking so long to answer, i actually got 2 mega.co.nz links for this, another user gave them to me ^^
https://mega.nz/#F!XAkUDajB!EaYNGGsABPapaVFkeGNqTw
and
https://mega.nz/#!Ncx2VASY!gfxVbnQj9HK9WUGiidKY83pJZA7ToTQu5RFDfu2miWE
I found your other post too, and given that im a noob i tried to reply there, then i was trying to private message you (failed cause im not smart xD) and now im here :3
Tell me if something goes wrong, i didnt check this myself cause i sent my phone to repair, it was so broken they didnt knew it was rooted xD
Best of Luck ^^
And yeah, this phone is not popular at all, not even Alcatel cares, i emailed them to see if they were gonna release some updates, didnt even got a reply until now
But well, im gonna check out what youre doing, sowwie im a copycat xD
Good luck again ^^
I'm a little bit late but if you still need or someone else needs it just let me know as I have Carliv Touch and stuck recovery for this device.
Little late as well, but do you still have that recovery? i picked up my phone again and i wanna mess with it
https://android.googleapis.com/pack.../e7adc4a02314908bfdc7a3eea85214e67b4e8e39.zip
Enjoy
matt1515 said:
https://android.googleapis.com/pack.../e7adc4a02314908bfdc7a3eea85214e67b4e8e39.zip
Enjoy
Click to expand...
Click to collapse
Please could you post the build.prop. I'm interested in the ro.build.date of the beta.
matt1515 said:
https://android.googleapis.com/pack.../e7adc4a02314908bfdc7a3eea85214e67b4e8e39.zip
Enjoy
Click to expand...
Click to collapse
Is this a full or incremental OTA?!
I know that it's a big file, but still...
Sent from my Nexus 6P using Tapatalk
https://developer.android.com/preview/download-712.html
Still nothing...
Sent from my Nexus 6P using Tapatalk
xdatastic said:
Please could you post the build.prop. I'm interested in the ro.build.date of the beta.
Click to expand...
Click to collapse
Here you go
Also I wasn't able to get this OTA to install via ADB sideload. Failed at
"serving: 'update.zip' (~47℅) * failed to read command: No error
Even after flashing stock system, boot, recovery, and vendor. Just wondering if anyone got it to work I noticed when installing the beta through Google's intended process it seemed to have a three part process and rebooted each step.
Is this ota or full image?
I usually flash full images with flashfire
matt1515 said:
Also I wasn't able to get this OTA to install via ADB sideload. Failed at
"serving: 'update.zip' (~47℅) * failed to read command: No error
Even after flashing stock system, boot, recovery, and vendor. Just wondering if anyone got it to work I noticed when installing the beta through Google's intended process it seemed to have a three part process and rebooted each step.
Click to expand...
Click to collapse
I got the same error. I was hoping this build would get me out of the bootloop that N4F260 has me stuck in.
thegios said:
Is this ota or full image?
I usually flash full images with flashfire
Click to expand...
Click to collapse
OTA. There is a working TWRP flashable zip here.
Thanks but gonna wait for full image to be uploaded by Google on beta site
SubuHyd said:
I got the same error. I was hoping this build would get me out of the bootloop that N4F260 has me stuck in.
Click to expand...
Click to collapse
Try formatting cache and then factory reset in recovery and see if it boots (assume you have locked bootloader). If no boot try and sideload this again. Might work if not try full OTA zip when released good luck hope you get it figured out
matt1515 said:
Also I wasn't able to get this OTA to install via ADB sideload. Failed at
"serving: 'update.zip' (~47℅) * failed to read command: No error
Even after flashing stock system, boot, recovery, and vendor. Just wondering if anyone got it to work I noticed when installing the beta through Google's intended process it seemed to have a three part process and rebooted each step.
Click to expand...
Click to collapse
Those of you getting errors, did you happen to check the SHA-1 hash of the downloaded OTA file? It should match the file name (E7ADC4A02314908BFDC7A3EEA85214E67B4E8E39). I downloaded it just to check, not going to install myself due to no new features. Weird that Google is going with the SHA1 hash on this as recently Google has been using SHA256.
Also, are you using most recent version of Platform Tools, 25.0.3? https://developer.android.com/studio/releases/platform-tools.html
Flash this .zip ， need modify updater.script。fastboot lock couldn't flash it
When you sideload ,the script run
package_extract_file("recovery-two-step.img", "/dev/block/platform/soc.0/f9824900.sdhci/by-name/boot");
set_stage("/dev/block/platform/soc.0/f9824900.sdhci/by-name/misc", "2/3");
reboot_now("/dev/block/platform/soc.0/f9824900.sdhci/by-name/misc", "");
Click to expand...
Click to collapse
But after reboot . it isn't continue. I think because recovery couldn't find zip file.. but it is flashing recovery to boot .
hey! i accidentally deleted a backup for my device and now i have no system to boot off of
are there any roms available for mya-l11? all the ones i see on this sub are for the 2015 models. thanks
lbxda said:
hey! i accidentally deleted a backup for my device and now i have no system to boot off of
are there any roms available for mya-l11? all the ones i see on this sub are for the 2015 models. thanks
Click to expand...
Click to collapse
I could not find any custom Roms for your device.
I could find an stock Rom for the Mya-l41 trough.
Here is an link: https://mega.nz/#!wKpT1ZaS!CV-2E4sNnUwIurskAdqCDpDawWlZD2UeABtSELk_ffc
That should be an update.app or an flashable zip.
You may get Huawei Update Extractor and extract the system.img and boot.img of the update.app
After that flash system.img and boot.img from fastboot.
Warning. This may soft brick your device.
Good luck.
If i helped press the Thanks button
Thespartann said:
I could not find any custom Roms for your device.
I could find an stock Rom for the Mya-l41 trough.
That should be an update.app or an flashable zip.
You may get Huawei Update Extractor and extract the system.img and boot.img of the update.app
After that flash system.img and boot.img from fastboot.
Warning. This may soft brick your device.
Good luck.
If i helped press the Thanks button
Click to expand...
Click to collapse
i was able to flash the boot and recovery image, but i couldnt flash the system image
lbxda said:
i was able to flash the boot and recovery image, but i couldnt flash the system image
Click to expand...
Click to collapse
Does it show an error or anything?
Fastboot flash system system.img
ok, so i found what i thought was a stock rom for my device on some spanish forum and used sp flash tool to install it
problem is, sp flash tool formatted my phone, but encountered an error trying to install the firmware and now my phone wont boot and windows says its not recognised
is there any fix to this? or is my phone bricked?
hey again! i know this post has been a wild ride of me doing stupid stuff and bricking my phone, but i got the firmware back!
only catch is that i'm receiving some nvram error (which i got on my previous phone too. i swear this is the last time im going mediatek), so if anybody has a method that can fix this it'd be highly appreciated
thanks
Hi, Ibxda.
Can you please share with us where you found the stock rom, what went wrong with flashing, and how you managed to get the firmware back?
I have a running system, but I rooted it and cannot apply official upgrades. I'd like to go back, upgrade and root again. I would appreciate the info on your progress.
ifrag_svk said:
Hi, Ibxda.
Can you please share with us where you found the stock rom, what went wrong with flashing, and how you managed to get the firmware back?
I have a running system, but I rooted it and cannot apply official upgrades. I'd like to go back, upgrade and root again. I would appreciate the info on your progress.
Click to expand...
Click to collapse
You should root with Magisk, it's systemless and it should not affect updates. If you want to update you should flash stock recovery. After you updated you are free to flash Twrp again if you want. If you are rooted with SuperSU you should uninstall SuperSU and install Magisk