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
Related
I already opened an RMA for the phone but they have no stock so I figured I'll take another shot at it.
The short version is that my gf messed up and updated the system while transferring her data from her old phone with the tapNgo thing.
I've done multiple facory resets, downloaded the rom from ZTE support, put it on SD, flashed it from recovery and deleted cache and nothing helps.
I don't have the exact error log anymore since I don't have the phone with me now but it reads something along the lines of
loading /proc/devices/audio/sound------ cannot find file/directory.
I looked it up and after a lot of Googling it seems like the symlink to the actual driver folder is missing and I have no idea why.
Does anyone know if i can fix this with an ADB shell?
Alternatively, I tried to follow some of the many guides out there to put the phone in EDL mode and relfash it with XiamiFlash utility but after trying 3-4 downloads and 900 versions of misflash all I ever get is "reading hello packet... unable to communicate to com4"
Haaaalp please?
*edit* this is pretty much exactly the same as what I'm getting: https://forum.xda-developers.com/android/help/sound-card-detected-t3379736
The problem with the phone is it makes no sounds?
gpz1100 said:
The problem with the phone is it makes no sounds?
Click to expand...
Click to collapse
the sound drivers for the OS is missing completely, no sound no microphone.
The syslog looks like this(this is from another phone its its the exact same problem):
AudioDaemon: Opening sound card state : /proc/asound/card---/state
AudioDaemon: Open /proc/asound/card---/state failed : No such file or directory
AudioDaemon: Sleeping for 100 ms
Strange issue indeed. Which model do you have? Which specific firmware file are you flashing to it?
I would think flashing the full unmodified factory firmware using the stock recovery will wipe the phone completely, including the /data partition.
Everything worked before? Help me understand the order of events. What is tapngo?
While in the midst of transferring information to or from the phone, a software update appeared and she accepted/installed it?
Its the A2017U model.
I had tried the 1.1.0 B15 firmware from SD card as well as the 1.0.0 B29 older firmware.
Right now its on B17 Nougat 7.1.1, the phone runs and works perfectly just has no audio hardware.
I wasn't there for the exact procedure but basically she powered it on, it asked for sim, she inserted that, tapped the "transfer my data" and then held the two phones together to get the NFC process started. That starts the bluetooth transfer process and it takes a really long time where it transfers all data and apps from the old phone.
At this point the phone still made sounds when adjusting the volume etc.
Somewhere in that process the "update available" notification came up and she pressed the option to install it.
After I got home I tried to figure out what is wrong, first i thought the phone wasn't registered on the cellphone network but then after a bit i figured out the audio is the issue, then i did a factory reset both from the phone UI and tried again from recovery mode, both times chose the "erase all data" option but neither time did it help at all.
I don't really know enough about phones but i think its the bootloader/something very early on thats messed up. Either that or the audio chip really just did fry.
My hope was to get the full factory image for everything that you need to install with the EDL mode thing but I can't find any good reliable guides for that.
It's the first thread in the development section.. Stickied even.
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
Get this package - B15-NEW_FULL (Nougat)
I really don't understand zte's numbering scheme. Newer versions get lower numbers. Makes no sense. That's the full firmware except for the fastboot which passes commands. At this point it's a non issue given the issue you're having.
So I don't need to load TWRP on it, I can still keep it just stock with unlocked bootloader?
I tried that miflash thing before, i had it connected un usb download mode but nothing worked for me, I'll try doing this guide when i get home step by step again.
Their firmware numbers is based on numbers and letters 1.0a-z and then 1.1a-z so 1.0z1 is less that 1.1a1
Ok I have an update
Did miflash, nothing changed.
Ulocked bootloader and miflashed the bootloader from the sticky thread.
The phone made the startup sound and audio worked for a few seconds after android started up and then stopped again
*edit*
ok so after it showed signs of life i re-locked the bootloader, and did the OTA updates to 7.1.1 and the audio seems to be working for good now!!
Conclusion seems to be the bootloader was the key to get it working again. Hope this helps others if it comes to it.
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.
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!
I was going to update my P10+ (VKY-L29C626B124) to Oreo. It's unlocked and rooted, but the updater wasn't working normally.
Started with FirmwareFinder and found an early Oreo for my phone. I was going to set up the proxy download in eRecovery. In the meantime, I backed everything up and decided to pony up the 4 euros to get the unlock code again because I figure this was going to put me back in stock. After I got the code, I was going to copy my backup over to my sdcard, but there was a crash in DC Unlocker and my phone rebooted.
Now I am stuck with eRecovery trying to do something and failing all the time. I can get to fastboot, but not TWRP. I am 99.9% sure nothing was flashed (because nothing was downloaded to begin with) but it seems that eRecovery is engaged in a way that it can't be overridden.
Is there a way to get back to either TWRP or the OS so I can move my backups off the phone and try this again? I was going to flash a stock rom via the Huawei Updater on my PC and a proxy, but I am open to other suggestions. So uh... h---e---l---p ? ? ? ?
Okay I managed to push the updates through so now I am on B172. Just need to find the right build to start onto Oreo...
Hello, everyone,
I tried to install LineageOS on my S10 Plus yesterday. That worked so far, but I found that it didn't have a decent camera app and the Samsung Watch wasn't that easy to connect either. So I thought I'd just go back to the Stock ROM again. I then downloaded the latest stock firmware according to this guide and installed it with Odin. The installation also runs through, after the installation the mobile phone starts and after the start screen there is an Android man with the signature "Erasing". After a few seconds, the device turns off and stays black. Even if I put it on the charger or try to restart it, nothing happens. I keep getting into download mode and recovery, but that's about it. Multiple reinstallations and resets via the recovery didn't help - the phone just won't start.
I used the CSC_... and not the HOME_CSC_... at the firmware is the right one for my phone.
Is there any way I can salvage the device? I'm afraid that something in the memory is defective now, which has nothing to do with the flashing itself. Do you have any ideas?
Many thanks!
tefracky said:
Hello, everyone,
I tried to install LineageOS on my S10 Plus yesterday. That worked so far, but I found that it didn't have a decent camera app and the Samsung Watch wasn't that easy to connect either. So I thought I'd just go back to the Stock ROM again. I then downloaded the latest stock firmware according to this guide and installed it with Odin. The installation also runs through, after the installation the mobile phone starts and after the start screen there is an Android man with the signature "Erasing". After a few seconds, the device turns off and stays black. Even if I put it on the charger or try to restart it, nothing happens. I keep getting into download mode and recovery, but that's about it. Multiple reinstallations and resets via the recovery didn't help - the phone just won't start.
I used the CSC_... and not the HOME_CSC_... at the firmware is the right one for my phone.
Is there any way I can salvage the device? I'm afraid that something in the memory is defective now, which has nothing to do with the flashing itself. Do you have any ideas?
Many thanks!
Click to expand...
Click to collapse
same thing happened to me today. but I flashed my s10e the bootloader and modem file of android 9 from twrp, the phone did not boot up and I loaded the stock rom again, then when I open it, it's the same as yours, I really need urgent help.
Releases · corsicanu/9820-bootloaders_and_modems
Contribute to corsicanu/9820-bootloaders_and_modems development by creating an account on GitHub.
github.com
EDİT: Anyway, I solved the problem, I flashed the bootloader and modem file that is suitable for my current version from the same site with twrp and the phone turned on. maybe you can solve it by flashing the bootloader and modem file suitable for the current version. try if you want
Thanks a lot, this worked!
tefracky said:
Thanks a lot, this worked!
Click to expand...
Click to collapse
I'm glad it worked.
I was very afraid that the phone died, what did you do for 5 days in this state?
Now I have a question in my mind: When Samsung releases an update in the future, will the bootloader and modem files be updated when we update it with odin? won't it be updated? After that, do we will always update manually as twrp? do you have any idea?
Well, I simply didn't use a mobile phone in these days. It was a very "interesting" experience, but not a huge problem. I sometimes opened WhatsApp as Windows App (interestingly, which works without phone).
I don't know, what happens at a Samsung Update, but until Android 13, I will not update (so probatly never). In our German forum (www.android-hilfe.de), a pre rooted and debloated "Stock"-Firmware is provided, but I can't install it, since my Bootloader is too new (V15 instead V14 for the ROM). When it is possible, I will install this firmware. If you are interested, here is the link: https://www.android-hilfe.de/forum/...3-2022-stock-rom-v2-0-pre-rooted.1000713.html
tefracky said:
Well, I simply didn't use a mobile phone in these days. It was a very "interesting" experience, but not a huge problem. I sometimes opened WhatsApp as Windows App (interestingly, which works without phone).
I don't know, what happens at a Samsung Update, but until Android 13, I will not update (so probatly never). In our German forum (www.android-hilfe.de), a pre rooted and debloated "Stock"-Firmware is provided, but I can't install it, since my Bootloader is too new (V15 instead V14 for the ROM). When it is possible, I will install this firmware. If you are interested, here is the link: https://www.android-hilfe.de/forum/...3-2022-stock-rom-v2-0-pre-rooted.1000713.html
Click to expand...
Click to collapse
thanks, if i'm going to use stock rom i prefer to root it myself