Related
hey guys,
i think i made something really stupid.
-unlocked bootloader
-installed TWRP
-rooted
everthing was fine B161.
installed apps2sd and did something there so my phone was stuck in bootloop.
now the stupid part:
i wiped everything in TWRP... system, internal storage everything... i am such a douchebag!
I tried to recover with eRecovery and install stock firmware B161. Update process was successful and i can start my phone again.
but everytime i start the setup wizard i am stuck after wi-fi+ service (enhanced internet expierence) the screen shows "checking data.." for 1 second and switched back to wi-fi+ service.
is there anything i can do? guys help me please i am starting to freak out.
is my guarantee voided after i unlocked my phone?
fastboot shows
-phone locked
-frp locked
THANKS FOR ANY HELP!
khajiit said:
hey guys,
i think i made something really stupid.
-unlocked bootloader
-installed TWRP
-rooted
everthing was fine B161.
installed apps2sd and did something there so my phone was stuck in bootloop.
now the stupid part:
i wiped everything in TWRP... system, internal storage everything... i am such a douchebag!
I tried to recover with eRecovery and install stock firmware B161. Update process was successful and i can start my phone again.
but everytime i start the setup wizard i am stuck after wi-fi+ service (enhanced internet expierence) the screen shows "checking data.." for 1 second and switched back to wi-fi+ service.
is there anything i can do? guys help me please i am starting to freak out.
is my guarantee voided after i unlocked my phone?
fastboot shows
-phone locked
-frp locked
THANKS FOR ANY HELP!
Click to expand...
Click to collapse
did you do factory reset? I had some weird stuff going on after recovery, so I booted back to factory reset (vol + and power), after that it worked OK.
Once you requested the bootloader unlock key, your warranty might be void from that point (depends on country). The bootloader gets locked after flashing official firmware via eRecovery though.
yes i did a factory reset, still can't proceed after wi-fi+ configuration.
is there anything else i can do?
I have one question: is it possible with
-frp locked
and
-phone locked
to downgrade via eRecovery? (to b130 or something..)
I have the exact same problem.
I bought it 3 days ago, and suddenly yesterday downloaded Apps (from the Play Store) stopped working. So someone told me to hard reset it. I got into EMUI and did it. Then I rebooted it and now it stuck there. Can't complete the setup wizard.
I found no solution to my problem after reading google & xda-forum for 3 days. Tried everything... nothing worked. Sent it back and (luckily) got a new one. Now i'm more careful for sure.
The store I bought it from claimed that they had numerous similar complaints about the 3gb version. Which is the one I have. They told me I should take it back and that they will give me a new 2gb version along with any difference in money. We will see.
Exact same thing with me stuck at setup wizard so had to send it off for warranty and got a brand new phone yesterday
Sent from my HUAWEI VNS-L31 using XDA-Developers mobile app
Help please my Huawei P9 cannot proceed afta WiFi setting it is stuck on "Checking info "and Reply saying "Couldn't sign in"
The problem is Android System Webview, it's not a system app in this rom and when you reset your phone it deletes it, happened the same to me, I had to go to a huawei center, they menaged to skip the initial setup and I've installed the apk from apk mirror. Without this app the phone can't login in your google account, so if you don't install it your gapps won't work
Maxai94 said:
The problem is Android System Webview, it's not a system app in this rom and when you reset your phone it deletes it, happened the same to me, I had to go to a huawei center, they menaged to skip the initial setup and I've installed the apk from apk mirror. Without this app the phone can't login in your google account, so if you don't install it your gapps won't work
Click to expand...
Click to collapse
Hello,
does ist really work? Is it just installing the androidsystemview.apk and the phone works fine again?
huawei p9 lite bricked ...please i need a help
my phone stoped in fastboot...
phone locked
frp lock
i can´t enter on recovery mode and he not pass the huawei icon ...
please i need help
i do not connect phone to pc ....
contact me to solve the problem
I'm having exact problem with my mate 8 NXT-L09, after i had to factory reset when update from firmware finder failed. Anyway to bypass this problem? Do you have a way of add Android System View into the mate 8 during the bootup process. I love this mate 8 phone and 5 days now i has been torture.
logjam said:
I'm having exact problem with my mate 8 NXT-L09, after i had to factory reset when update from firmware finder failed. Anyway to bypass this problem? Do you have a way of add Android System View into the mate 8 during the bootup process. I love this mate 8 phone and 5 days now i has been torture.
Click to expand...
Click to collapse
Reflash the rom you were on using the "dload" method
dariomrk said:
Reflash the rom you were on using the "dload" method
Click to expand...
Click to collapse
Sorry, dont have the previous ROM, I boiught it off someone and they probably did the first update. The factory reset should reset to huawei original but i think this is where my problem sits.
HARDWARE VERSION=NEXT_L09_VN2
BOOTLOADER VERSION=NXT-C900B120_FASTBOOT
KERNEL VERSION=NXT-C900BB140_BOOT
AP VERSION=NXT-C900B140_SYSTEM
CP VERSION=21.750.08.00.010(balong)
Parameter Version:
P-00.00.000 G-17.V271.371 E-40.01.000
does anyone have an international rom for this or any version that can work.
The way i was able to factory reset was
1. going to huawei site. "consumerDOThuaweiDOTcomSLASHjmSLASHsupportSLASHdownloadsSLASHindexDOThtm"
change slash to / and dots to .
2. Select options for your phone, mine was NXT-L09. Will show "HUAWEI Mate 8 Firmware(NXT-L09, Android 6.0, EMUI 4.0, C605B100, Latin America, Channel-Others)"
3. Download, extract onto sdcard in dload folder, restart phone using vol up & vol down & power.
4. phone will complete boot restart but will then loop the boot process.
5. Do factory reset again
6. After huawei logo, different options show and you are then ok to proceed to login to your google account and setup refreshed phone.
Now on NXT-L09C900B100 build, if anyone has nougat rom for this, please share.
For future reference, if anyone gets stuck with this on P9 lite, indeed the instructions provided by Huawei point to VNS-L11C432B161, which doesn't include Android webview and therefore initial setup cannot proceed. The solution is to flash B210 on top of B161:
update.hicloud.com:8180/TDS/data/files/p3/s15/G1164/g104/v80562/f1/full/update.zip
which allows you to pass setup as the bug has been fixed. No root/unlock/twrp required.
First excuse me for opening an other thread like this, i think i have read all other threats regarding my problem, but none have the same situation
My Huawei M3 Wifi (BTV-W09) seems semi bricked after installation of Nougat Update.
The Installation (Force Install with dload) gave me an error and also while boot i got the error message: "Your device has failed verification and may not work properly."
I have the option to press "Powerbutton" and the device will boot up. I checked the Version and it showed android 7 + EMUI 5. The only problem was that almost every system app was missing, like keyboard, calendar etc. (playstore was there)
So i tried to do the rollback with:
HUAWEI MediaPad M3 8 Rollback Package%28BTV-W09 %2CC900B300%2C EMUI5.0%2BAndroid7.0 rollback to EMUI4.1%2BAndroid 6.0%29
The Installtion (force update) gets stuck at 5% and after like 3-5 minutes the tablet will boot up showing the same boot error that can be skipped with pressing powerbutton. I checked sytem and it still showed "android 7 + EMUI 5" but built : BTV-W09C900B300
I think this is the one i "need" to be able to install the "HUAWEI MediaPad M3 8 Firmware %28BTV-W09 %2CC100B006%2C EMUI4.1%2BAndroid 6.0%29"
Problem is regardless which "update.app" i try to force install will get stuck at 5% and give me same error. I have ADB/Fastboot installed and tried some different things like flashing/unbricking it with "Huawei Multitool" where you can extract like boot.img or recovery.img and try to flash it.
Also getting an error. I can access eRecovery witout problems, the option to fix it by itself by wifi doesn`t work. I can´t access "normal" recovery and i think there is the problem (may got bricked while flashing Nougat?) I think its recovery problem, cause when i boot it up to the "half-installed" Android and go into setting "hard-reset" option i know it would boot up intoi recovery and would erease everything, while bootup it shows error "reset failed".
In fastbootmode i see bootloader: unlocked FRM: unlocked
I tried to install TWRP recovery with adb but get error: adb remote command not allowed
I downloaded like 15 different Android Versions 6+7 Emui 4.1+5 to try with force update but none worked, may i have to flash special version of recovery first?
I just want a normal version of android 6 or 7 i dont mind but at the moment with half working 7 "without" systemapps its a hardtime.
I hope someone can help me.
This isnt my first android device and im not a total noob i unlocked bootloader and flashed kernels on many other phones but with the W-09 where i did nothing special i dont get why "recovery got broken"
Thanks in advance
You haven't read other threads too well: more times people reported that the bootloader got locked after an update still declaring itself unlocked!
Second thing you have not found: the Nougat update consist of 2 packages and the second must be installed from TWRP.
nicolap8 said:
You haven't read other threads too well: more times people reported that the bootloader got locked after an update still declaring itself unlocked!
Second thing you have not found: the Nougat update consist of 2 packages and the second must be installed from TWRP.
Click to expand...
Click to collapse
thanks for your anwser, i read that so i also tried unlocking it "again" and it quotet it is also unlocked in adb. I also know that there are 2 packages. That you need TWRP i didnt know thanks so i am a bit smater now. I think i ll try "relock" and unlock it again might be the right way, thanks for the tip.
kivi90 said:
I think i ll try "relock" and unlock it again might be the right way, thanks for the tip.
Click to expand...
Click to collapse
This is nonsense. Unlock, install the right TWRP then install the second zip package.
nicolap8 said:
This is nonsense. Unlock, install the right TWRP then install the second zip package.
Click to expand...
Click to collapse
i cant unlock cause i dont have the code, on the huawei page i try do make an account and get the code by providing the necessary information.
I just uploaded a picture, i choose "before EMUI5" cause this is the only option i can choose "tablets". --> i choose "tablet wifi" , enter product model "BTV-W09" then the serialnumber i can see in setting: 28D6R17316XXXXXX but then i have the problem to input product id, it say i can get it through "Dialer" app (which i dont have in wifi model ) or the calculator. Problem is in my damaged installation there is no huawei calc, other calcs from store dont work (read that problem in other threats) I tried many apps from appstore to get a product ID but huawei site keeps saying wrong product ID =/
With the program DC Unlocker i am able to see a MEID i dont know if its the right one, i tried my luck with the Product ID Generator from Huawei but it doenst work. (device not supported)
It's very strange that it says bootloader unlocked if you have never unlocked...
And was very stupid to try to installl a beta release without before unlocking and taking a backup.
Exhange your device for a Nokia 3110!
nicolap8 said:
It's very strange that it says bootloader unlocked if you have never unlocked...
And was very stupid to try to installl a beta release without before unlocking and taking a backup.
Exhange your device for a Nokia 3110!
Click to expand...
Click to collapse
yeah at this device i never touched bootloader, i didnt think it would become such a big deal , i didnt want unlocked bootloader or other recovery just newest android. Never had any problems with the "force update function" to come back to stock. I tried DC Unlocker but cant get further cause device need to get into manufature mode (thorugh dialer or calculator which i both dont have) i hope maybe i find one more way.
Did you ever find a fix
Did you ever find a way to fix this. I'm in the same situation. I even did a VPN on my router to give me a Hong Kong address for erecovery and that still didn't work. I have the exact same product. Like you I tried to various attempts to download a new recovery, but nothing works. Nice hardware, but some of the worst software/firmware I have ever dealt with since starting with the first release of Android on the HTC Hero.
kivi90 said:
yeah at this device i never touched bootloader, i didnt think it would become such a big deal , i didnt want unlocked bootloader or other recovery just newest android. Never had any problems with the "force update function" to come back to stock. I tried DC Unlocker but cant get further cause device need to get into manufature mode (thorugh dialer or calculator which i both dont have) i hope maybe i find one more way.
Click to expand...
Click to collapse
I had mostly the same problem. I rolled back to 4.1 using the rollback and the actual 4.1 update.app. I think that puts you on C100 if I remember right. Tablet I have is C128 (USA) but no problem for this step. Get the Product ID from the calculator. Allow OEM unlock in the settings, then unlock it using the unlock code. Email yourself the unlock code because who knows if their website will even be functional next time. Alternatively you can extract the stock calculator from the update_data_usa.zip or whatever and try to use DC with 5.0. That second update zip does not install properly via the dload method, so a bunch of stock apps don't get installed. You can kind of hack it and flash it via TWRP but I didn't do it that way.
Or...you can use firmware finder to force an OTA from 4.1 right up to 5.0 (350), then take that last partial OTA to 351 after as well. The way to do that is via DNS in firmware finder. Find the Full OTA in firmware finder you want, send it to the updater by changing your DNS the way it tells you to, and when it does the OTA, everything will be properly installed basically the official way. Good as new. Flash TWRP to recovery2 and replace the erecovery. Keep the stock recovery as is. Install magisk. Golden.
---------- Post added at 03:36 AM ---------- Previous post was at 03:26 AM ----------
kivi90 said:
So i tried to do the rollback with:
HUAWEI MediaPad M3 8 Rollback Package%28BTV-W09 %2CC900B300%2C EMUI5.0%2BAndroid7.0 rollback to EMUI4.1%2BAndroid 6.0%29
The Installtion (force update) gets stuck at 5% and after like 3-5 minutes the tablet will boot up showing the same boot error that can be skipped with pressing powerbutton. I checked sytem and it still showed "android 7 + EMUI 5" but built : BTV-W09C900B300
I think this is the one i "need" to be able to install the "HUAWEI MediaPad M3 8 Firmware %28BTV-W09 %2CC100B006%2C EMUI4.1%2BAndroid 6.0%29"
Problem is regardless which "update.app" i try to force install will get stuck at 5% and give me same error.
Click to expand...
Click to collapse
Also, as far as the rollback, you need to do the first one (the C900 which is just a compatibility fix to allow rollback, previously used by beta testers I believe). Then you need to do the second one, the C100. If it is getting stuck, try downloading it again and be sure you don't have anything else in the /dload directory on either internal or the sd card. I had one on both at one point so maybe that happened to you. The C900 should be very quick but the C100 will slowly progress after 5% all the way around in several minutes.
When you get to updating back to 5.0, you can choose whichever region you want as long as it is a full OTA. C128 is USA and that's what I bought so that's what I picked. That gets you back in the right OTA update channel after that.
Hi guys,
I started as a novice and have learnt the hard way.
Has anyone tried rollback to EMUI 4.1 EU version on a US device (W09) and are there any problems I should be aware of?
I have had the exact same problem shared in this thread and have gone through the pain of finding a solution. My last resort is to rollback to 4.1 and restart the whole process.
@deV14nt: you suggested that when updating back to EMUI 5.0, I can choose the region even if my EMUI4.1 is EU version. How does this work?
Thanks in advance for your help.
Ok so to start i got my bootloader code, did the Oem line in adb all went well, used the greatslon us M3 Twrp, said it went through ok, tried to boot using the volume up an down as well as power just boots to blackscreen then does nothing. if i let it just boot into factory android it runs for a min and then forces a reboot, oh and my model is the CPN-W09 which i think is the issue upon reading, the Greatslon twrp is for a dif version of M3 then mine, so i tried the erecovery it says im not supported, i tried restore through hisuite says not supported, i try and do a factory reset but unit powers off before it can complete. Any ideas what i can do?
I had that issue with my first M3, even though it's a BAH-W09. Since it was US version and I didn't catch there being a difference between it and the international/European BTV-W09, I screwed it up. I was never able to get back to full operation, but that was mostly out of irritation and the ease at which I could return it for a replacement.
That being said, there are full-update firmwares out there, you'll need to spend some time on Google/search engine of choice to find them. Once you have one, you'll need the firmware extractor to pull the update apart into the individual .img files, which can then be flashed using fastboot.
I'd start with https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146 - this is a firmware finder that should be able to find and download firmware updates for you (Windows only, I believe)
Then https://forum.xda-developers.com/showthread.php?t=2433454 - this should be able to pull the firmware apart for you. This was the part I got stuck on and initiated my return after, but I'm sure it works, I just wanted the easy way out
Hello, I really messed this up... I haven't rooted a phone in over 5 years, but just ordered a moto g7 from google fi because I wanted to play around with rooting and rooted apps again.
Setup:
-got moto drivers, adb, set developer mode, unlocked bootloader
I had tried to just root using the "simple?" method of using Magisk with the lolinet firmware files. I used the PPO files in the Official/FI dir. I thought that I had seen an error when flashing the magisk modified boot.img that there was an issue or that it wasn't valid, I (stupidly) assumed that this was like the notification you get after unlocking bootloader about invalid key or whatever. When trying to boot up it would just keep boot looping, and I went into hard panic mode... I saw other people had mentioned using retail or retus firmware on the google fi variant, so I proceeded to try to just flash those stock boot.img files after the fi one hadn't worked. I then finally got it to boot up fully, I don't even remember which firmware it was (retail maybe) and felt a little bit better about it, but had also seen that some people had said it wouldn't have the full functionality of network switching if I wasn't using the fi firmware. So... back to the fi firmware...
I was able to get it booting up on stock fi firmware, and to be honest I should have stopped there and given up on root, because I'm guessing I would have been perfectly fine up to that point... I again tried magisk modified fi firmware to no avail, and was having trouble getting back on stock fi for some reason... I followed a post to reset to stock and relock bootloader ***I'm guessing this was my major fault***, I must not have been paying enough attention to the command prompts doing this, but I think this is where I messed something up royally. It was able to boot, but then it said it had updated software to the 'PPOS' variant which I thought was strange... After attempting to reflash stock fi and then magisk fi boot.img it is failing and won't even get to boot loop.... when trying the slew of commands to flash full stock firmware I keep getting issues with the "_a" partition being not found.
At this point I can't get to recovery, or boot after attempting to flash a number of times. Any help would be appreciated, even if it is just a confirmation that I f'd this device and to stop wasting my time and give up on ever having a rooted device again lol.
Thanks for your time, and let me know if there is additional info to provide that may help.
Edit: Current status:
"Start Up Failed: Your device didn't start up successfully. Use the Software Repair Assistant on computer to repair your device. Connect your device to your computer to get the software Repair Assistant."
in Bootloader logs, but I don't know what software repair assistant it is referring to, i have tried connecting to pc.
Edit 2: Or I'm just a complete idiot and needed to re-unlock bootloader with the code like previous... which I totally should have known, but again, I'm an idiot...
So, now that I've got it booting up, do I attempt reflashing a magisk img or just admit I'm too stupid to do this? Or should I go with twrp which seemed like more steps and potentially more issues to run into?
Sorry for the scare and immense stupidity!
Hi, I get a notification to update magisk. then I update it and use the recommended action to update it. After that it asks me to reboot the device. After rebooting the device it goes to fastboot only. And I see the device now changes to US996 while what I have is H990DS.
Can someone explain to me what's wrong and how to fix it without losing all my data?
thanks...
Hi there,
all I can say is that is happened exactly the same to me just some minutes ago, I installed latest magisk update like I've been doing with no problems, just that today, after reset, its always booting stuck into fastboot mode.
I have a H910 and I also see the message about US996, maybe this is related to the method used to root the phone, If I recall correctly it had something to do with installing a US996 modified bootloader.
I still haven't found a way to get my phone back to life. All I can say is that I do manage to boot into recovery (TWRP, via the appropriate key combination at power on), so I guess I'll manage to flash something to fix this and return it back to life I hope
aliks00 said:
Hi there,
all I can say is that is happened exactly the same to me just some minutes ago, I installed latest magisk update like I've been doing with no problems, just that today, after reset, its always booting stuck into fastboot mode.
I have a H910 and I also see the message about US996, maybe this is related to the method used to root the phone, If I recall correctly it had something to do with installing a US996 modified bootloader.
I still haven't found a way to get my phone back to life. All I can say is that I do manage to boot into recovery (TWRP, via the appropriate key combination at power on), so I guess I'll manage to flash something to fix this and return it back to life I hope
Click to expand...
Click to collapse
It's common knowledge that if you root your phone you never apply an OTA
Sent from my LG-H910 using XDA Labs
cnjax said:
It's common knowledge that if you root your phone you never apply an OTA
Click to expand...
Click to collapse
Thanks, but who said I ever applied an OTA? It was magisk that wanted to update itself, I've been performing magisk updates regularly for quite some time and never had a problem, in fact I can't even perform an OTA phone update as I have AT&T variant but with a different sim...
Other times, when updating magisk, I lost root but never lost the ability to boot...
I was running alpha-omega oreo with mk2000 kernel and updating rom, kernel and magisk regularly through TWRP (or direct install in case of magisk though magisk app) and never had this problem before... at least I can manage to boot from recovery/TWRP so hopefully I will soon manage to get things working again... that is, if I can copy some images to my SD card that windows insists that is corrupted but that's another story...
I ended up flashing whole rom again and everything is back to normal