Hello there.
I am trying to root my SM-M205FN with android 10.
However Magisk is telling me the boot image is unkown or unsupported.
I got stuck in a bootloop before but managed to get my device in download mode and fixed it with odin.
Maybe this is causing errors. Until now i only had 2 problems after i got stuck in the loop, which are not being able to use Netflix or Instagram.
I found the boot image via google and im pretty sure its not from a shady website so i dont really know what the problem could be.
Ihope someone can help.
Ps: im a newbie so please try to explain easy
Get ROM from https://www.sammobile.com.
I don't know if it is official Samsung site, but I used some from there and didn't have any problems.
You will have to register but it doesn't require further steps.
You may compare your ROM to the one from site above, it costs nothing.
Related
Hi,
I just received my phone today and somehow I managed to brick it. I don't know how this happened as I was only trying to fix a common issue I was having with my google play store ("download pending"). I didn't uninstall anything as I didn't even root my phone. I just disabled some apps like the browser and now im stuck at the zuk logo boot page. I got into the bootloader page and it's asking me for an update.zip file. can anyone please help with this?
thanks
well, at least you can still enter the bootloader page, which means the phone is still alive. Which zuk do you have? Did you try reboot? How many times?
hi thanks for the reply. i tried rebooting more than ten times for sure and i am sure i didn't disable any important apps. My model is the Z2. The model number is Z2131 on the box.
I also tried flashing the phone with a new rom as per instructions on another thread but its only showing no port available and when it sometimes shows something its not qualcomm snapdragon as it said in the thread.
Hi guys,
I've bought an P9 and wanted to get rid of the booting screen with the resellers logo.
So I thought I'd be smart, unlocked the device, flashed TWRP 3.1.1-1-eva.img onto it. Got an SuperSu-file and tried to install it...
I never got to experience the rooted version. Got stuck in a bootloop, somehow got out of it. Logged in, saw an green SuperSu-app, opend it and it saidthe device has to be rooted to use the device, ergo i failed to root it. [Forgot some steps here] and I found myself in another bootloop. A friendly guy suggested to flash these 2 files
[Link-Removed]update.zip
[Link-Removed]update_data_full_hw_eu.zip
which I did with dload. After that, I was still in a bootloop, but with WipeCache I was able to get myself back into my phone [hooraay].
The happyness-phase was a short, because i soon found out, that it doesn't have an keyboard (only googleVoice, should be fun to type in a wifi-password). Huawei-ID tab is also missing (usually located below Accounts), Update Phone, which was between Advanced Settings and About Phone is also missing, and bluetooth doesn't seem to work. That's when I noticed that I'm on NRD90M test-keys build.
After reading some threads here i downloaded rollback from huawei (for west-europe). Now I'm on C900B300 but all settings still missing.
Now I'm here crying for help.
Any suggestions? Please?
Ryan
You got to rebrand your phone.
movizdb said:
You got to rebrand your phone.
Click to expand...
Click to collapse
do you mean, that i have to put the bootlogo back into it?
could be a meanie to do, because it's a swiss brand and I don't think that there's a version here for me to use.
//or do an OEM-Flash, which worked
So, i tried flashing meticulus ROM by This guide, but it said that other version of recovery is needed which is meant for P9 lite and it should work on 5C. Then i did read that it does not work on EMUI 5.0+ and i did restore my old rom back. But the weird thing is that, my sound, microphone, video playback and nothing of those features work currently. Everything else works fine. I tried restoring OEMinfo, trying the dload method and such but nothing is making me able to downgrade. Has anyone has any similar problems before, because i checked that my OEMinfo is right but dload says "incompability with current version" so im unsure whether the problem is with the UPDATE.APP or my phone. TWRP works and i can flash things with it, but i'd rather rollback to the original ROM so i can install Lineage OS. The funny thing is that i tried flashing this multiple times but it will not boot but hangs on "Your device is booting": https://forum.xda-developers.com/ho...covery-stock-recovery-download-honor-t3521504
Camera isn't working either. Tried flashing Elite ROM to see if that works, but ended up in a bootloop. eRecovery does not update via wifi because it says that "cannot get package info" or something similar.
I flashed the oeminfo zip and tried to restore old nandroid backup. Now it only boots to eRecovery and says "getting package info failed". It's not booting into fastboot either nor recovery.
Managed to get into fastboot, but can only gain access to the product ID via software i guess and cannot get key without that. So now im stuck with locked bootloader, without rom and a stock recovery that is completely useless. Does anyone know if huawei support can help me?
They can help.
But you cam try dload method. There is a quick guide in my signature for the same. let me know in case you need any further information or help
shashank1320 said:
They can help.
But you cam try dload method. There is a quick guide in my signature for the same. let me know in case you need any further information or help
Click to expand...
Click to collapse
Actually there was some problems with the internal memory. Im not sure if i did damage it or did it have something to do with faulty hardware.
Anyhow it passed warranty so i did not get charged anything. Maybe i'll keep the phone as stock for a while at least
onnz423 said:
Actually there was some problems with the internal memory. Im not sure if i did damage it or did it have something to do with faulty hardware.
Anyhow it passed warranty so i did not get charged anything. Maybe i'll keep the phone as stock for a while at least
Click to expand...
Click to collapse
just dont blindly flash stuff thats made p9, it can work but not fully. NEVER flash anything thats made for other device.
Hello, I've spent at least 10 hours now trying to fix this and searching for solutions. I'm going to try to describe it as best I can.
The device is in bootloader mode and does not go beyond the moto logo with parity mode disabled. I've tried using the lenovo moto assistant to rescue it and it's only using the latest update, but it still doesn't boot up beyond the bootloader mode.
I've tried sideloading from adb inside recovery mode but I always get a driver issue
I don't know what else to do besides that.
Please help? Ask as many questions as you need.
nalsur10 said:
Hello, I've spent at least 10 hours now trying to fix this and searching for solutions. I'm going to try to describe it as best I can.
The device is in bootloader mode and does not go beyond the moto logo with parity mode disabled. I've tried using the lenovo moto assistant to rescue it and it's only using the latest update, but it still doesn't boot up beyond the bootloader mode.
I've tried sideloading from adb inside recovery mode but I always get a driver issue
I don't know what else to do besides that.
Please help? Ask as many questions as you need.
Click to expand...
Click to collapse
Just an update everyone, I was able to partially fix the issue by using part of what this person posted here: https://forum.xda-developers.com/moto-z-play/how-to/guide-relock-bootloader-to-lasted-stock-t3718190
The device however now says it's loaded a different operating system, though it works
nalsur10 said:
Just an update everyone, I was able to partially fix the issue by using part of what this person posted here: https://forum.xda-developers.com/moto-z-play/how-to/guide-relock-bootloader-to-lasted-stock-t3718190
The device however now says it's loaded a different operating system, though it works
Click to expand...
Click to collapse
The only real problem now is how do I fix this so that I can use google pay. Can anyone share any quality guides for how to bypass google's check?
Most of the time I am the guy helping people out. This time I think I did something pretty dumb.
I have an old "beater" P9 plus that I was using as a casual gaming device. Most of the apps I was using were beginning to no longer be supported because for some reason the device NEVER updated. Any time I check for a possible update the phone stated it was up to date. After much searching I discovered that this device SHOULD have updated quite a few times.
I used firmware finder to find a supported update and the first one went somewhat unexpected. The firmware was downloaded and put in the correct folders but kept failing after 5%. I decided that the next thing to do was to find a cool rom and go through the process of unlocking and installing TWRP. I usually try to install the latest TWRP. This turned out not working at all so I went for an older version and it booted into TWRP, however it found the update and installed it!
I kind of wanted to keep it stock, but updated stock so I went for a bigger upgrade to Android 7 firmware. This only worked partially and (stupid and I know better) forgot to do a backup. I did not know that TWRP was gone and root was gone. The battery died and I rebooted like normal and there was a much improved interface. However, a good bit of stuff stopped working like bluetooth and the boot screen was in red stating the device can't be verified and ended up in something like a NOR905 test keys build. I did a backup, selected a downgrade package that was checked and "updated" to the downgraded firmware through Project Menu. It successfully stated it was 100% complete.
Now it is stuck on the boot screen for an unlocked device.
What works (or is possibly a good thing):
The hardware keys can get me to the bootloader (fastboot)
ADB recognizes the device is in fastboot
Phone is Unlocked
FRP is unlock
What doesn't work:
Everything else. All I have is fastboot and an unlocked bootloader. I can try to flash recovery but that never boots, it just stays suck on the recovery boot screen. The system will not boot at all.
UPDATE:
I broke down and spent the money to use the DC-Phoenix software to unbrick the phone. Several of the options for firmware did NOT work. The one file set that did work was to use this firmware:
VIE-L29_C900B101_Firmware_countryValue_Nonspecific_Android_6.0_EMUI4.1
Then use this as the customization:
update_data_C900B101_hw_default
The phone originally started out as VIE-L29C636B130. This changed it to VIE-L29C900B101 and is on EMUI 4.1 android version 6.
Now the fun part is going to see if I can find a version of TWRP that will work and see if I can root it. Maybe even try a custom ROM. We'll see though. The device is just an old beater for fun. But at least, she's not broken anymore. Guess I'll grab a beer and celebrate my "unbricked" device.