Related
Hello everyone!
I tried to look for a solution to my problem but unfortunately could not find one.
When I was in China in a moment of madness I went to OPPO store and purchased N1 Mini - smashed screen on my old S3 so thought this was a great idea at the time. I read the reviews, I knew it was very easy to install CM so I thought - great, I'm gonna get one of these...
So got home, downloaded the ROM... and got installation failed every time. Tried different builds, same again. I started reading and realized this phone is a bit different...
Is there antyhing I can do? I'm even happy to stay on ColorOS, but I need to install Gapps (flashing them in recovery gives ... instalation failed )
xy
xywojtek said:
Hello everyone!
I tried to look for a solution to my problem but unfortunately could not find one.
When I was in China in a moment of madness I went to OPPO store and purchased N1 Mini - smashed screen on my old S3 so thought this was a great idea at the time. I read the reviews, I knew it was very easy to install CM so I thought - great, I'm gonna get one of these...
So got home, downloaded the ROM... and got installation failed every time. Tried different builds, same again. I started reading and realized this phone is a bit different...
Is there antyhing I can do? I'm even happy to stay on ColorOS, but I need to install Gapps (flashing them in recovery gives ... instalation failed )
xy
Click to expand...
Click to collapse
U need to root the phone.
Step 1
Download aptoide apk
Step 2
install mi market app from aptoide
Step 3
Open mi market and search root
Step 4
Scroll thru the list and click on the search other market tab.
Step 5
Install kingroot, open app and click root.
If u root successful, Pls proceed to herehttp://forum.xda-developers.com/showthread.php?t=1874285 and download the file
Install root explorer
Unzip the downloaded file
Move to system/apps
Reboot ur phone.
U will see playstore installed.
Let us know whether it works.
adix82 said:
Step 5
Install kingroot, open app and click root.
.
Click to expand...
Click to collapse
Thank you for your time, answer much aprreciated. Unfortunately kingroot did not work, and yesterday I sold this phone.
Best regards,
xy
Hello everyone!
i have oppo n5117 but its stop on oppo logo
i need a custom recovery to do side load
side load kernel
or any one have solution for me
washwshny_13 said:
Hello everyone!
i have oppo n5117 but its stop on oppo logo
i need a custom recovery to do side load
side load kernel
or any one have solution for me
Click to expand...
Click to collapse
Don't know whether it's too late... (?)
Anyway, I've found this which can help you flash using your PC to unbrick.
http://pan.baidu.com/s/1hsjQUES
This will help you flash back to official 4.4
Hello,
First of all, Thanks for this great community. It has been helping me with my S4 for a long time.
Almost a year ago, I bought a fire phone for my younger brother. Today I tried to install the Custom Rom CM11 (which I successfully did), but, among the files in the proper thread, are 2 more files, the Google apps and also, a "flash wipe out". I did this in the end, expecting that just cleaned everything without touching the OS. Huge and novice mistake from miself. After almost 5 hours of looking for a solution, I realized that I don't have an OS and can only enter to "Fire phone recovery mode". I have downloaded almost 5 or 6 stock firmwares that are available to donwload here in XDA. Tried to download the OTA for an unlocked phone from amazon and tried to upload it to the phone via ABD tools. In the end, I always get the same errors: Not-signed and can't install it in the phone.
I'm going to be honest: I'm desperate.
In conlcusion:
1) No OS in a fire phone.
2) No custom TWRP.
3) I just have recovery mode
4) Been trying to install through ADB tools without any success the stock OTA update (the last one, since I had the 4.6.6 version)
Anything that can help will be well received.
Thanks in advance
Hello,
Have you tried ADB sideload when you go into your phone's recovery? And if you did, what did it say when you tried installing it? Try using this to sideload your phone.
Thanks for your answer @mechasnyper but I have tried that out as well
Hey, thanks for the answer. I really appreciate the time for doing it.
Yes, I have tried the ADB Sideload. The phone it's identified through the CMD (I get to see the serial) and then try the ADB Sideload. It doesn't work with bin files. It says unable to load. I tried also with the zip files that are posted here in the forums, being able to load then at 100% but the cell phone says "invalid signature", and for this couldn't install it over the fire phone.
lordofra said:
Hey, thanks for the answer. I really appreciate the time for doing it.
Yes, I have tried the ADB Sideload. The phone it's identified through the CMD (I get to see the serial) and then try the ADB Sideload. It doesn't work with bin files. It says unable to load. I tried also with the zip files that are posted here in the forums, being able to load then at 100% but the cell phone says "invalid signature", and for this couldn't install it over the fire phone.
Click to expand...
Click to collapse
Try sideloading using this file. https://www.androidfilehost.com/?fid=24052804347783512 I found this somewhere else and this is the file I used when I screwed up my ROM installation.
When I get home I'll try using that file that you have posted.
I'll update the results.
lordofra said:
When I get home I'll try using that file that you have posted.
I'll update the results.
Click to expand...
Click to collapse
Success?
Sorry for the delay. Been talking with centurylink because since yesterday I have no Internet service (Answering from the phone). No, no success at all.
lordofra said:
It says unable to load.
Click to expand...
Click to collapse
Your need free RAM on computer bigger than .bin size.
Hey, thanks for the answer.
I'm doing it on my laptop that has 8 Gb of ram. Just in case, I'm going to try it on my brother's laptop that has 16 gb of ram to test this out. But I doubt this will make a difference, since I've tried already many .bin files (all of them are unable to load an their size its 1.2 GB max. Many zip files as well where I have obtained 100% load but the firephone aborts the installation due to signature verification failure.
This is really strange. I have screwed up installing Cyanogenmod onto my phone, yet I was able to revert back to the stock ROM with just the stock recovery. I will have to look more into this. I will post again soon for updates. Have you wiped the data and cache?
EDIT: I am not sure if this will work, but try using this bin file. http://androidhost.org/o120v
@lordofra
Try (with quotes)
adb sideload "full_path_and_name_of_the_bin.bin"
Official updates for our M2 tablet,
although having installed another
recovery and root access, already.
- Disclaimer
Well, whatever you do with this guide is all up to you and in your own responsibility. You
should have basic knowledge about ADB and flashing, which is explained in many other
threads here on our beloved XDA.
- Issue
When you used this guide (https://goo.gl/r04XjJ) or any other one to give your M2 tablet
another recovery and therefore root rights, you have now the problem, that EMUI will show
you new updates, but you are not able to install them, because of the missing stock recovery,
of course.
- Solution
So, you have to flash back the original stock recovery, getting the official update and then you
can flash back your TWRP recovery.
- Guide
1. You should start your EMUI update programme/app and start the download of your update.
When it is finished, it will ask you to reboot into recovery and install automatically. As you have
no stock recovery I strongly advise not to do so. Usually nothing happens, but there is one case
reported, where it somehow ****ed up the guy's tablet. I am not sure, if that story is true, but
well, I have warned you.
2. Just turn your tablet off after you have finished downloading the update (it will wait now in
the directory "HwOUC" on your tablet and it is called "update.zip" - just let it sleep there).
3. Start the tablet in the fastboot recovery mode, meaning plugging in the USB cable (connected
to the computer) and hold the buttons "power" and "volume down", immediately, until a white
screen appears, which is the fastboot recovery screen. It should tell you, it has the bootloader
unlocked, which is normal, because you did that earlier on with any of the other guides (see above).
4. Copy the downloaded stock recovery of your choice to your ADB directory. In my case this is
"c:\ADB", but this depends on your way of installation.
5. Now open up a command line in Windows (with Windows key + R) and type "cmd") and go to
your ADB directory, using commands like "cd .." and "cd adb".
6. When having arrived in the ADB directory, you have to enter these commands one after the other:
fastboot flash recovery stock-recovery.img
fastboot reboot
If you renamed the recovery file, then you have to consider that in the command, of course.
7. The device will reboot directly into the recovery, because it "sees" the update in the update
directory et voila ... you are getting your awaited update. Sometimes it will boot not into the EMUI
recovery directly, but then you hast have to start the tablet normally, open up the EMUI app and
download the update again and do the OTA update properly with the reboot it tells you to do,
when it is finished.
8. Okay, now you have received your update, but if you want to have back your TWRP, you just
have to turn off your tablet and boot into the fastboot recovery again (see 3.).
9. You have to copy your TWRP recovery to your ADB directory (in my case "twrp.img" in "c:\ADB").
10. Now open up a command line in Windows (with Windows key + R and type "cmd") and go to
your ADB directory, using commands like "cd .." and "cd adb".
11. When having arrived in the ADB directory, you have to enter these commands one after the other:
fastboot flash recovery twrp.img
fastboot reboot
12. The tablet will reboot and you are back to a working lovely updated M2 tablet.
- Root:
If you want to have root rights, I strongly recommend flashing Magisk within TWRP, because it is
just a nice and more modern approach to having root. It works very fine on my M2 10 tablet. The
link for the files and guide is here:
https://goo.gl/UXYk4d
It is very easy. You just flash Magisk 12 in TWRP and then install the Magisk Manager app from the
Play store.
- Files for M2-802L and M2-A01L:
https://ufile.io/0df492 (all four recoveries here)
https://files.fm/u/aajdmadr (all four recoveries here)
https://www.file-upload.net/download-12438839/HuaweiM2recoveries.rar.html (all four recoveries here)
Have fun with your updated tablet. ... and I am happy, if I could help you - any coffee appreciated.
...
..
.
+++ saved +++
Additionally, I can offer you the updates B007 and B010 (most current one) for the
M2 10 LTE (M2-A01L), because I managed to save them/back them up. These are the
European versions of B007 and B010 with all language files, I believe.
So, who is having a M2-A01L and is still sitting on B006 or B007, might try a manual
update, which is as easy as pie. It is just one simple step.
Also, an update from B009 to B010 might be possible.
Of course, I cannot give any guarantee for Huawei's update files, which you will
understand, I guess.
what android version ?? M2-801L, thanks
Eagle-no1 said:
what android version ?? M2-801L, thanks
Click to expand...
Click to collapse
M2-A01L, not M2-801L. For all 8 models you find your ROMs here:
https://forum.xda-developers.com/me...om-8-0-models-stock-marshmallow-roms-t3535466
or
https://forum.xda-developers.com/me...-b207-android-6-0-marshmallow-emui-4-t3533572
or
https://forum.xda-developers.com/mediapad-m2/development/rom-stock-rooted-xposed-t3519031
xsycox said:
Additionally, I can offer you the updates B007 and B010 (most current one) for the
M2 10 LTE (M2-A01L), because I managed to save them/back them up. These are the
European versions of B007 and B010 with all language files, I believe.
So, who is having a M2-A01L and is still sitting on B006 or B007, might try a manual
update, which is as easy as pie. It is just one simple step.
Also, an update from B009 to B010 might be possible.
Of course, I cannot give any guarantee for Huawei's update files, which you will
understand, I guess.
Click to expand...
Click to collapse
I'd greatly appreciate it, if you could share. Got the problem that my A-01L got corrupted. The only official ROM I've been able to find has been B005 what is somewhat old. As it seems to be a pre-release version the tablet doesn't find any updates. Thus I'd like to try to upgrade to B007, or even B010 manually when I'm back home. Currently I'm on a weekend trip as friends of mine are going to marry tomorrow. Thus I'd be able to download them on Sunday evening if you'd provide them.
Regards
Sent from my htc_pmeuhl using XDA Labs
Tried Magisk but can't pass Safetinet test even with Magisk hide enable...
is it working for you?
5m4r7ph0n36uru said:
I'd greatly appreciate it, if you could share. Got the problem that my A-01L got corrupted. The only official ROM I've been able to find has been B005 what is somewhat old. As it seems to be a pre-release version the tablet doesn't find any updates. Thus I'd like to try to upgrade to B007, or even B010 manually when I'm back home. Currently I'm on a weekend trip as friends of mine are going to marry tomorrow. Thus I'd be able to download them on Sunday evening if you'd provide them.
Regards
Click to expand...
Click to collapse
https://forum.xda-developers.com/me...om-official-manual-updates-m2-tablet-t3595211
zedoc said:
Tried Magisk but can't pass Safetinet test even with Magisk hide enable...
is it working for you?
Click to expand...
Click to collapse
I have Magisk running on several devices, including the M2-A01L, but I must admit,
I never got the Safetynet passed, even with Magisk hide enabled.
I just use it as systemless root and with systemless Xposed, which is great.
zedoc said:
Tried Magisk but can't pass Safetinet test even with Magisk hide enable...
is it working for you?
Click to expand...
Click to collapse
xsycox said:
I have Magisk running on several devices, including the M2-A01L, but I must admit,
I never got the Safetynet passed, even with Magisk hide enabled.
I just use it as systemless root and with systemless Xposed, which is great.
Click to expand...
Click to collapse
After enabling magisk hide, you have to reboot your device. Got the 801L working with that and safetynet passes.
Noob Question on recovery files
Hi, and thanks for a incredible well detailed guide for updating. Came here because I haven't found any good recovery files for the wifi model. I've been trying (unsuccessfully may I add...) to install TWRP and magisk. So, my question is: can the recovery files for the LTE model be used on the wifi model? (M2-A01w). Thanks for your help!
myst771 said:
Hi, and thanks for a incredible well detailed guide for updating. Came here because I haven't found any good recovery files for the wifi model. I've been trying (unsuccessfully may I add...) to install TWRP and magisk. So, my question is: can the recovery files for the LTE model be used on the wifi model? (M2-A01w). Thanks for your help!
Click to expand...
Click to collapse
Sorry, I have been on vacation.
To be honest, I am not sure, if the recovery for M2-A01L works on M2-A01w, too, but you can just try it.
I think, there should not be that big a problem, because the recovery has nothing to do with Wi-Fi or LTE, at all. It is just important, that partition tables and drives are accessible the same way and well, I really think, there is not much difference in between the M2 10 models.
From M2 8 to 10 there is a difference, of course. That is why I uploaded both recoveries (for 802L and A01L).
Just use that guide (https://forum.xda-developers.com/mediapad-m2/how-to/guide-unlock-bootlader-twrp-root-huawei-t3322340) without the SuperSU flashing and my recoveries in this guide.
Hi guys,
I need help, I have a M2 10 LTE previously modded with TWRP for root and I've just followed this guide to update from 007 to 010 version.
So I've flashed the stock-recovery, rebooted the tablet, requested the firmware update (I don't know if I got any error during the process) and the tablet has rebooted. Now it's stuck on HUAWEI logo..
I use this tablet for work so I really need to recover it asap.
Please help.
Shocker580 said:
Hi guys,
I need help, I have a M2 10 LTE previously modded with TWRP for root and I've just followed this guide to update from 007 to 010 version.
So I've flashed the stock-recovery, rebooted the tablet, requested the firmware update (I don't know if I got any error during the process) and the tablet has rebooted. Now it's stuck on HUAWEI logo..
I use this tablet for work so I really need to recover it asap.
Please help.
Click to expand...
Click to collapse
Could upload the B010 fullstock ROM/firmware. Thus you could reset the device to the latest stock ROM using the /dload method and gain a factory rested Huawei, as if out of the box. Just quote me if you'd want me to upload and I'll share the link asap. Took that way myself as soon as I found the full stock ROM.
Sent from my htc_ocnuhl using XDA Labs
thanx
Dear xsycox
I have an issue where I updated my W version tablet to L version accidentally and I am having issue getting it back..
I am currently trying to get some help in this thread: https://forum.xda-developers.com/me...-m2-installed-wrong-update-zip-t3563105/page2
Can you please help me out? do you have any idea what ican do to get back to W version?
Thanks!
Hi guys,
Could you please advise?
Here is what happened:
New phone from China with Spyware/Ad infested ROM
Decided to flash to LineageOS. I've flashed my other phones many times before (Oneplus).
Followed instructions but skipped backup due to some kind of an error (Yes I know, stupid, but never had problems with other phones, of course this is a stupid excuse as well but hey ho, I'm stupid):
1. Unlocked officially.
2. Installed TWRP.
3. pushed LineageOS/gaaps.
4. Tried to do a backup but skipped it due to an error :///////.
5. Wiped Syste/cache/data/dalv.
6. During installation got an error 7 (xiaomi.verify_modem("2017-07-05) =="1".
7. Read on the forum that I need to flash to the latest official rom.
8. Pushed it to the device (stable version, not dev)
9. Got a little bit scared and decided to push smaller older rom in order to try to install it first.
10. Can't push anything anymore. It starts copying but after 5s it changes to read-only and stops copying.
11. My best move??
Guys, please help, any help would be appreciated.
Not sure if you tried this first: http://en.miui.com/a-232.html
** Choose Fastboot from the left side!
I would suggest first trying to install the official recovery and fastboot ROM, then after that is successful, then go ahead and install TWRP and lineage.
dgrasley, I love you! You saved me. I don't know why I haven't checked fastboot update before! Worked like a dream. Thanks a lot .
tomkkkk said:
dgrasley, I love you! You saved me. I don't know why I haven't checked fastboot update before! Worked like a dream. Thanks a lot .
Click to expand...
Click to collapse
That's great! Glad you got it working! Happy flashing!
Hello to all of you!
I'm a newbie in flashing ROMs... ahaha
I'm trying to install LineageOS 14.1 into my Samsung A5 17 but I'm running into some problems... I hope that someone around here can help me out
So right now I’m on Android 8.0 with the stock Samsung experience, bootloader ecc… I’ve tried to install TWRP and lineageOS 14.1, and it runs fine but it can’t recognize the SIM card! I did some research and turns out that I’ve to install first the stock Samsung ROM with 7.0 nougat and then install lineage in order to make the SIM show up. So I’ve tried to do so but when I try to flash the original stock ROM with Odin it returns this problem:
The flash fails after it tries to insert the param.bin file
The device in download mode return this error:
sw rev. check fail(bootloader) device: 7, binary: 4
Can you give me some advice?
Thanks :angel:
Why would you want to downgrade?
Make sure you have the proper ROM, as well as CS file.
Download said files again.
For some reason my brothers windows 10 partition hates downloading the files properly, on my Linux partition I never had said issues.
Because the I've read in other topics that if downgrade my phone to 7.0 it would be able to read the SIM card after install LineageOS 14.1, but I'm not sure about that. Am I right?
Don't worry I've tried to download the stock ROM multiple times but in every case it returns me this error.
I think that the ROM files aren't the problem.
Other advice? Thx you btw
Same here , my phone doesnt recognize sim aswell , but i didnt installed any custom rom i just had stock rom. It started with android 8 i tried a lot , but i cant make it work , if someone knows how to fix tell me.
And about the Binary on the device , you have to download a rom with a higher binary that you already have , since you have 7 you can only update to a 7 binary or higher , to know which is the binary on the rom ill Tell you how to realize the binary
The rom's file name is like this FXX5UIR7XVBR that seven in the last characters is the binary number of this rom. It was just an example.
Sorry about my english.
So if someone knows how to fix sim card problem it will help me so much , i tried to flash another stock rom , like 3 or 4 and nothing happened , imei is right its not corrupted or something.
Thx
Aliwu said:
Same here , my phone doesnt recognize sim aswell , but i didnt installed any custom rom i just had stock rom. It started with android 8 i tried a lot , but i cant make it work , if someone knows how to fix tell me.
And about the Binary on the device , you have to download a rom with a higher binary that you already have , since you have 7 you can only update to a 7 binary or higher , to know which is the binary on the rom ill Tell you how to realize the binary
The rom's file name is like this FXX5UIR7XVBR that seven in the last characters is the binary number of this rom. It was just an example.
Sorry about my english.
So if someone knows how to fix sim card problem it will help me so much , i tried to flash another stock rom , like 3 or 4 and nothing happened , imei is right its not corrupted or something.
Thx
Click to expand...
Click to collapse
Don't worry for the English I'm learning it too ahaha
Can you give me a more detailed explanation of that binary stuff that you were writing about? I didn't get how it fit with our problem, maybe I've just missed something ^^'
Also if you can find anything about our problem, please post it on this thread!
Thank you