Hi guys! this is my first post, or thread, whatever you wanna call it.
So here i am facing problems with my 2013 nexus 7 device, im currently on JB 4.3, the update for 4.4.2 is downloaded and verified, but when i try to install it the countdown of 10 seconds starts, when it reach to "rebooting" it stucks in there and nothing, i waited like 10 minutes once,( the tablet wont stuck).
Any help of suggerstions? i hope anyone can help me since i dont want to do a manually update for now. :silly:
thanks.
It isn't seldom thing that OTA updates fail, or even soft-brick the device for they have not been completely flashed. Updsting manually is much safer option IMHO.
.....of course, it is only then safe, if the fastboot commands get executed flawlessly well... read: if stupid Windows has installed the USB driver properly. Read around how guys fall into troubles if it isn't the case.
tetakpatalked from P5110
Hi guys,
hope you can help me with a nasty little problem ..
I got a Chinese Note 2 (GT-N7100_CHN_CHN) from my father in law - he bought a Note 4 just recently. The phone is virtually not usable in Europe, as no Google support is implemented (mail, G+, Maps) and there is no access to the regular Playstore. Also, the only Android available is 4.1.
So I tried to flash a new Firmware (and yes, I'm a noob), and that's were the problems began. I've downloaded this ROM: N7100XXUFNE1_N7100DBTFNE1_N7100XXUFND3_HOME.tar.md5 which is - as far as I could figure out - a more or less "factory" version of a German Android 4.4 ROM. For whatever reason, I was unable to flash it using Odin (I tried several drivers, cables, computers (all Win7/64), disabled virus scan .. no way to get Odin 3.09 to work. It recognizes the phone, but aborts the flash process immediately with just a "1 processes failed" error.
After reading a bit here, I tried to root the phone using Saferoot (worked perfectly), loaded MobileOdin and this ROM to the phone and did the flashing there. This works fine, the phone starts, it has a German interface, is running KitKat .. great. Only issue: The WiFi does not work. As I figured out from this forum, I need to install either a WiFi patch or a new Bootloader (I've downloaded BL_N7100XXUEMJ5_1903221_REV04_user_low_ship.tar.md5 - hope that's the right one).
The problem now is:
Saferoot fails to root the Android 4.4 version - so no root access
MobileOdin does not work without root (and I don't know whether it would be able to flash a bootloader)
Odin 3.09 still does not work with the device
I tried Heimdall, but it does not accept the .md5 files for Odin and I could not find any ROMs in the right format
So I'm running out of ideas what else to try. Could you give me a hint what to to do?
Many thanks,
Scooby
You are saying the phone is chinese and doesn't have support from Google so there is clearly not original phone.
Samsung has not produced that phone so it means the hardware parts are not from samsung and the ROM you are flashing can't be installed.
I read you want to root but I think it is already rooted(try with the app "root checker")
You can't do much with that phone.
Sorry
manuel1992 said:
You are saying the phone is chinese and doesn't have support from Google so there is clearly not original phone.
Samsung has not produced that phone so it means the hardware parts are not from samsung and the ROM you are flashing can't be installed.
I read you want to root but I think it is already rooted(try with the app "root checker")
You can't do much with that phone.
Sorry
Click to expand...
Click to collapse
Hi Manuel,
it's definitely a original Samsung device. Google is simply (virtually) not available in China, so they install a slightly modified Android that points to a local Samsung store instead of playstore, G+ and Maps is not pre-installed ..
As written above, I was able to root it as long as the original Android 4.1.x was installed and I have successfully flashed the new german Kitkat ROM. "Only" Problem right now is that I can't get Odin to work and due to that I can not install the Wifi fix or new Bootloader. And ideas on that?
Thanks
Scooby
hello
i have rooted the device using the "1 CLICK ROOT TOOL" and now i have the dead android bot with error when i enter recovery.
i have tried the "fastboot erase cache" command at fastboot mode but it did not help
is their a way to fix it?
Try pressing Volume + key and Power. Don't hold just press. It might take a few goes to get it right. I had the same problem. That means that the update you have downloaded (saved on your system) fails to install.
hello and thanks
i can enter recovery by pressing the keys. this is not the issue
its just that i want to completely solve the problem
koby058 said:
hello and thanks
i can enter recovery by pressing the keys. this is not the issue
its just that i want to completely solve the problem
Click to expand...
Click to collapse
Awh sorry, I thought you can't get into recovery.
Try sideloading the stock Firmware. Go to official ASUS website and download it from there. It's about 1 GB. On this website you can find instructions on how to do it. http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596 Section 3.2)
After that you can download OTA updates and install them using method described here http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835, "Steps to Apply OTA manually".
OTA can be downloaded from there (look at the later posts for newer OTA) http://forum.xda-developers.com/zenfone2/general/ota-links-stock-rom-t3093999
I had a very similar problem few days ago. That solved it. Had a similar problem a few days ago coz I messed up my build.prop
hello
i have already did a "adb siedeload" for the stock rom downloaded from the asus web site but the issue remain.
also i downloaded the latest ota, and "adb sideloaded" them as well. it worked flawlessly .
but the small thing with the recovery is annoying.
i thinking about looking inside tmp directory and delete something called "last update"
what do you say?
koby058 said:
hello
i have already did a "adb siedeload" for the stock rom downloaded from the asus web site but the issue remain.
also i downloaded the latest ota, and "adb sideloaded" them as well. it worked flawlessly .
but the small thing with the recovery is annoying.
i thinking about looking inside tmp directory and delete something called "last update"
what do you say?
Click to expand...
Click to collapse
You're not understanding because the information he gave you is slightly wrong. When you try to enter stock recovery it will ALWAYS say installing update and pop up an error Android bot. It's not about having some update data somewhere that fails to install properly. It will ALWAYS do that. That's normal.
rlaw said:
You're not understanding because the information he gave you is slightly wrong. When you try to enter stock recovery it will ALWAYS say installing update and pop up an error Android bot. It's not about having some update data somewhere that fails to install properly. It will ALWAYS do that. That's normal.
Click to expand...
Click to collapse
Owh, this is embarrassing. I was playing with it a lot and I was kind of sure that if you have a working installed update, which is the same as a zip of an OTA update you have on an SD card it will skip installing the update and go to recovery without an error, but I was very very wrong. I'm very sorry for missleading you, and I've learned something new. Thank you.
NiKiToS-04 said:
Owh, this is embarrassing. I was playing with it a lot and I was kind of sure that if you have a working installed update, which is the same as a zip of an OTA update you have on an SD card it will skip installing the update and go to recovery without an error, but I was very very wrong. I'm very sorry for missleading you, and I've learned something new. Thank you.
Click to expand...
Click to collapse
No worries, I've made the same mistake before. We've all been there, still learning new things about this phone after months of using it!
ok let me tell why i begin asking about it.
when i just got the phone i update all of the ota updates and after that i rooted it with "1 CLICK ROOT TOOL" .
two days ago i receive tha 2.20.40.58 ota . i downloaded and install but the instalation failed .
so i unroot it with "1 CLICK ROOT TOOL" and then i checked for update . but there was no update.
so i assumed the problem is because of the recovery issue.
the qustion is why i cannot install ota automatically ?
koby058 said:
ok let me tell why i begin asking about it.
when i just got the phone i update all of the ota updates and after that i rooted it with "1 CLICK ROOT TOOL" .
two days ago i receive tha 2.20.40.58 ota . i downloaded and install but the instalation failed .
so i unroot it with "1 CLICK ROOT TOOL" and then i checked for update . but there was no update.
so i assumed the problem is because of the recovery issue.
the qustion is why i cannot install ota automatically ?
Click to expand...
Click to collapse
The 2.20.40.58 OTA was bugged and pulled from release. Just flash the full stock 2.20.40.59 firmware available from ASUS site and stop modifying your phone if you want to remain trouble-free with OTA updates. Or if you choose to continue to root and tinker with your phone accept that some things might get broken.
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
I have a Samsung Galaxy S9 (SM-G960F) Exynos, branded under Australian Optus and have been trying to load the latest Lineage Rom onto it but have ran into a multitude of issues. I'm going to list all of the things I've done and the Errors I've recieved
Developer Tools Enabled -> OEM Unlock Enabled (Forced Wipe) -> Developer Tools Enabled -> OEM Already Enabled -> USB Debugging Enabled -> ADB Tools installed and enabled (Computer trusted)
From Heimdall I tried flashing Lineages own bootloader from their website. I ended up getting the error "Failed to Receive Session End Confirmation"
My phone would also display the message "Only Official Released Binaries Are Allowed To Be Flashed"
I was also told RMM State played a part in this and if it was Prenormal, it wouldn't work. I went to check and sure enough, my phones RMM State was Prenormal
Despite this, I tried sideloading the packages anyway because I was told that just because it said that message, didn't mean it failed. Those ended up also failing, telling me the installation was aborted because of a validity error
From there, I was told to use Odin. That failed. I ended up switching to TWRPs bootloader instead and that also failed
After that I tried Flashing the Stock Android 10 Rom but that didn't solve any of the issues
I also tried downgrading to Android 8 Oreo to see if I could load everything from there but got the error SW REV CK FAIL
Dr Ketons Guide did not work as I was unable to Flash TWRP so I couldn't follow that route
I have the no Verity File downloaded but no way to apply it. Same with Magisk and Magisk Manager
Does anyone know what I can possibly do to try and get these things loaded onto my phone. I really would like to get them working as my main sim card is Vodafone so I'm unable to use it with this phone. Flashing the Stock unbranded XSA rom didn't seem to fix this issue either. The phone isn't under any contract or warranty, however I have no idea if its locked or unlocked.
Thanks
if you are in the prenormal state that means you can't modify your phone for like a week, just wait for the time. then it should work
by reading what you did, I didn't see anything wrong. it's just the prenormal thing that you have to wait for 7 days
edit: also forgot to mention if you failed to modify the phone after the prenormal state ends, you might need another 7 days to be able to modify your phone again
B1nz said:
if you are in the prenormal state that means you can't modify your phone for like a week, just wait for the time. then it should work
by reading what you did, I didn't see anything wrong. it's just the prenormal thing that you have to wait for 7 days
edit: also forgot to mention if you failed to modify the phone after the prenormal state ends, you might need another 7 days to be able to modify your phone again
Click to expand...
Click to collapse
So I waited 7 Days and its still prenormal. What should I do now. I tried flashing anyway to see if it was just a visual thing but it still failed. The phone was on for the whole 7 days.
CrashSpyro said:
So I waited 7 Days and its still prenormal. What should I do now. I tried flashing anyway to see if it was just a visual thing but it still failed. The phone was on for the whole 7 days.
Click to expand...
Click to collapse
I don't know it will work or not, have you try to flash the lastest stock firmware, do the initial first android setup (just skip everything), once you finish the setup go to download mode then try to flash the twrp through odin.
I used that method everytime I failed at flashing new rom. Hope it's also works for you, since my phone is also came from Australia
B1nz said:
I don't know it will work or not, have you try to flash the lastest stock firmware, do the initial first android setup (just skip everything), once you finish the setup go to download mode then try to flash the twrp through odin.
I used that method everytime I failed at flashing new rom. Hope it's also works for you, since my phone is also came from Australia
Click to expand...
Click to collapse
Unfortunately I have already tried that and it ended up not working