I found one of my Huawei G620s phones, I remember in 2019 it was rooted and started haviing problems, for example it was stuck at the bootanimation or did not work at all (red,green,blue LED), then in 2022 I turned it on just to find no reaction at all, nothing. I ran a flashing tool for Huawei and got it to turn on and display a green screen with 2 boxes, one blue and one red, along with the text:
"bootloader lock state: widevine disable mode"
"press and hold poewr key for 10s or more to forcibly reboot."
and surprisingly, i booted twrp 2.8.6.0 using the fastboot command from my PC. However when it loads i keep getting errors, for example:
"E: Primary block device '/dev/block/bootdevice/by-name/userdata' for mount point '/data' is not present!"
"E: Unable to mount '/data'" and it goes on with '/data/media' , '/boot' '/recovery' '/cache' '/system'.
It also says internal storage is 0MB.
I have tried everything, I wiped everything, I tried the file system changing trick, I tried to repair SELinux contexts and permissions, and it all resulted in nothing. Backup shows no partitions too, mount shows the names but clicking on them to mount does nothing, MTP enabled makes the phone show up in This PC but also nothing appears, and if I had a SD card then it would only show it. I tried to install a custom ROM for example, also nothing. Flashing for example TWRP to the recovery or boot partition using the fastboot command on my PC results in: "FAILED (remote: "partition table doesn't exist").
Now before you say the NAND failed, I once found a random paid tool and downloaded a free version of it. It was called something like Miko service tool and I flashed it in the boardsoft section because the other ones didn't work. And guess what? It flashed the stock ROM for me, but I had to use the phone's testpoint. Then the phone started booting but I noticed something was off, the bootanimation was playing kinda too fast, and it took not so long to boot. Then it booted to a lockscreen with a red wallpaper with the qualcomm logo. After swiping up I just saw like 5 hoem screen pages with only test apps, no google apps no huawei services apps, the phone didn't even have a theme applied and looked like old generations of EMUI, just some apps like settings,browser, camera, dialer etc. The test ones were named "MMI Test" or something. I was happy and decided to just ignore this until I put my SIM card into the phone, reboot it, just to see the error that network communication is unavailable because the device ID was altered. then I opened settings, went to the about phone section just to see my IMEI appear as "0", and serial number was "0123456789AB". Then I ran some codes and got into a test menu, and saw that the device mode was "Factory". I tried everything to disable it but I couldn't, then I got the idea to update the phone with the branded rom that was on it when I got it. And it updated, installed the stock applications but the IMEI and S/N were still gone, bootanimation was still the same (I checked in the ROM zip and it was the branded one so I didn't get the wrong ZIP). Then I booted into fastboot to see the thing that made me scared to death, Fastboot said "Phone LOCKED". I was scared thinking that the phone is done forever, because the bootloader relocked itself. Tried to boot TWRP just for the error saying that it's not allowed to appear, I also tried fastboot oem unlock but it asked for the code. Then I started the phone from the test point again and used an program to reflash it, the program failed and the phone rebooted to the green screen again, then I tried to boot TWRP and it worked. Reflashed the phone again with miko's service tool and same result as before.
Is there anyone that had a similiar problem? I really wanna get this phone back to work, I still have the battery with the IMEI written on it along with the S/N. I just don't know why TWRP is refusing to work, I tried the 3.2 build too but same result. Maybe it's because the bootloader is "locked" ? I ran the command to unlock it in the cmd (fastboot oem unlock) and it said "OKAY [ 0.006s]". It's weird because don't huawei phones need a code to be unlocked? And when I had the OS installed it didn't let me run the command and asked for the code.
Sorry if it's the wrong section but I saw the G620s custom ROMs only being posted in the honor 4x section so I thought it's good.
Related
About two months back, I rooted my htc one mini 2.
Unlocked the bootloader, installed a new recovery (This one) and finally rooted the device. I wanted to install different fonts for it, and in the process relocked the bootloader again.
Now, after several weeks of not doing anything regarding the root, my phone has errors after errors.
First, Google Play stopped working, and along with it, Youtube and the Play Store of course.
About two weeks later, even the "internet" app stopped working.
Today i wanted to start my phone only to find it stuck in the starting screen. (Looks like this)
What I want to do now is get my phone factory resetted, not rooted anymore and WORKING.
What I tried to do is get the phone into fastbood mode (this worked) and connecting it with the "Minimal ADB and Fastboot" console. (This did NOT work)
Rebooting the device from the fastboot menu did not work, it either gets stuck in the loading screen again or directly enters fastboot.
What can I do to make my phone work again?
I hope you can help me :/
Montor
Montor said:
About two months back, I rooted my htc one mini 2.
Unlocked the bootloader, installed a new recovery (This one) and finally rooted the device. I wanted to install different fonts for it, and in the process relocked the bootloader again.
Now, after several weeks of not doing anything regarding the root, my phone has errors after errors.
First, Google Play stopped working, and along with it, Youtube and the Play Store of course.
About two weeks later, even the "internet" app stopped working.
Today i wanted to start my phone only to find it stuck in the starting screen. (Looks like this)
What I want to do now is get my phone factory resetted, not rooted anymore and WORKING.
What I tried to do is get the phone into fastbood mode (this worked) and connecting it with the "Minimal ADB and Fastboot" console. (This did NOT work)
Rebooting the device from the fastboot menu did not work, it either gets stuck in the loading screen again or directly enters fastboot.
What can I do to make my phone work again?
I hope you can help me :/
Montor
Click to expand...
Click to collapse
Try unlocking the bootloader again.Flash the custom recovery and then flash the stock rom available in the development section. It looks like your system partition got corrupted
csoulr666 said:
Try unlocking the bootloader again.Flash the custom recovery and then flash the stock rom available in the development section. It looks like your system partition got corrupted
Click to expand...
Click to collapse
How can i unlock the bootloader again?
The only way i know is via the console and "fastboot oem unlock" - i cant get my phone to connect though.
The available devices the console gives me are an emulator and three times my phone, which is/are offline.
Edit:
Stupid me. "Fastboot oem devices" and it shows my phone in fastboot mode.
Next problem: "fastboot oem unlock" does not work, and flashing the recovery with "fastboot flash myrecovery.img" doesn't work either :/
Edit 2: Managed to unlock the bootloader again (mistook the android folder with de adb folder, no unlocktoken there of course)
Directly after unlocking the bootloader again, the device went into recovery mode, showed the recovery starting logo, and went black.
After turning it back on, it got stuck in the starting screen again - will have to wait for it to run out of battery.
Edit 3: Flashed the recovery, but i can't seem to find a stock rom (only one i did find is this here - and the files are down...)
Solved it!
Just did a factory reset in bootloader menu.
(I hope i didn't forget anything, since I don't know s*** about android development)
So this morning i tried this. Kingroot didn't complete the root, some error happened, i didn't mind since i was just testing to see if i could root my phone for the first time [i've never done it before and it seemed simple enough].
I quit the app, a bunch of errors showed up, one after the other [i didn't register what exactly the windows said, i'm pretty sure it was a google application that stopped working]. The phone turned itself off.
i booted it up again, and it showed me the AP Fastboot Flash Mode screen. i know this from previously doing a factory reset, so i tried doing it again. After it wiped all of my data and custom, i tried rebooting it.
it showed me the motorola icon, but a few seconds later, i was back at the fastboot screen. i'm pretty desperate right now since this is my only phone. i tried selecting the "normal powerup" command, it didn't work. this is my screen right now:
"hab check failed for boot
failed to validate boot image
fastboot reason: fall-through from normal boot mode
USB conected
hab check failed for boot
failed to validate boot image
boot up failed"
none of the other commands, aside from Recovery, work. it takes me to the no command screen and all of the known options once i use the power+volume up command: reboot system now, reboot to bootloader, apply update from ABD, etc.
sorry if this thread reads weird, i'm sort of freaking out right now and english isn't my main language. thanks in advance to anyone who might help!
Check here
If you have questions PM me I will try to help. I got the same problem on Monday and solved it yesterday.
Hi
So I've been trying to set my P9 Plus back to stock, unless I experienced an unknown error during the flash and I got stuck outside the OS, with the black screen warning me that " the phone is unlocked and it can't be trusted". I tested some other firmware but no luck, also for some reason now I can't even access the TWRP. I'm stuck even outer at the moment, I can access only the white bootloader. I since tried to flash TWRP again, following this guide https://forum.xda-developers.com/p9/how-to/huawei-p9-brick-easiest-to-unbrick-t3662348 for the update extractor, but from adb/fastboot I get the FAILED (remote: Command not allowed) error. Looked for most of the solutionfor this step but none of them worked.
I gave a chance to the HWOTA7 tool, to HiSuite, to automatic update too, no progress at all
What could be the next move?
Thanks a lot for the support
Same
Exactly same issue here. Phone boots (when it wants to) but unresponsive (apps won´t open).
Somehow either partition became read only or partition completely gone.
Micro sd download gyári Rom
Hey!
So i'm making this post after battling over 4 days with my friends old oneplus 3t.
All started maybe year ago when my friend asked me for help because his oneplus had suddenly gone into a bootloop kind of state (he told me that the phone was in his pocket working fine and when he tried to use it next time it started acting up.) Before i could even help him he had already bought new iphone, so the oneplus stayed in his drawer until last week when i remembered it and started to try to fix it.
So first thing that i noticed was this message "The dm-verity is not started in enforcing mode and may not work properly", the message eventually went away and i got to a recovery mode and thought that this is gonna be easy, hooked the phone to pc and started adb and tried to sideload the official rom from oneplus site, but everytime i tried it went to maybe 47 %or 66% and failed eventually. So i thought that ill try flashing original recovery.img, started fastboot and tried flashing and everytime "remote: Partition flashing is not allowed". Tried many times also oem unlock command and failed miserably, all i got was "remote: oem unlock is not allowed". Eventually trying every command from fastboot and adb i came to a conclusion that the device doesn't allow anything to be written to its storage (Tried of course flashing twrp, but same error).
Downloaded Oneplus 3T unbrick tool v3.0, and qualcomm drivers (turned windows driver signature off) everything went great and the green text came in oneplus unbrick tool and i proceeded to start the phone in excitement and the circling bootlogo started and it just stayed there, nothing, and after while shut down.
Things tried now:
-Sideloading (many times with different roms) no success.
-Fastboot (It recognizes the device everytime, but all other commands than "fastboot devices" end to an error"remote: something not allowed") no success
- Unbricktool v3.0 (Works like a charm everytime, but phone doesent still boot to os) no success
-recovery (wiped cache and all data many times) no success
My friend never flashed anything to this device, he doesn't even now how to do this kind of stuff.
Phone not dropped even once, is in a perfect condition and has all the original stickers even.
I have grown obsessed to fixing this phone, so any help is greatly appreciated :laugh:
onlyoneplusproblems said:
So i thought that ill try flashing original recovery.img, started fastboot and tried flashing and everytime "remote: Partition flashing is not allowed". Tried many times also oem unlock command and failed miserably, all i got was "remote: oem unlock is not allowed". Eventually trying every command from fastboot and adb i came to a conclusion that the device doesn't allow anything to be written to its storage (Tried of course flashing twrp, but same error).
-Fastboot (It recognizes the device everytime, but all other commands than "fastboot devices" end to an error"remote: something not allowed") no success
Click to expand...
Click to collapse
I haven't personally ever had to use the unbrick tool, so I can't help too much with the core problem. But what I can say, is that the steps I've quoted above (trying to flash recovery partition, etc.) are going to fail by design, since the bootloader is locked. This is the very purpose of the locked bootloader. The expected result is "remote: not allowed".
And as far as I am aware, you have to have a working OS and have "OEM unlocking" first toggled on, in the phone Developer settings. Otherwise (again, by design) the "fastboot oem unlock" command is going to fail.
Spontaneous failure of the phone to boot to OS, and dm-verity warning, to me probably indicates the OS has become corrupt/damaged. The damage is showing as a change to the system, therefore the dm-verity warning. Normally, I would tell you to flash the stock recovery image. But of course you have already tried that. Probably difficult to determine for sure. but spontaneous failure, and failure to flash recovery image (multiple times) may indicate a hardware failure such as bad emmc.
Hello everyone, it's my first time writing here, but I’ve tried everything, searched everywhere, and am desperate for help.
I screwed up big time while trying to flash a custom rom on my nem-l21, as I successfully did before with my xiaomi... So what I did:
I managed to unlock bootloader with dc unlocker. Then I got stucked flashing twrp with adb tools. Everything was looking to be fine, no error messages, “flashing successful”… But, I was never able to boot into flashed twrp. Always got stuck on “your phone has been unlocked blah blah. Your device is booting.” It never booted, not in twrp, nor in stock recovery. I tried different versions of twrp from different sources, always same result (flashing successful, booting into recovery not). Booting into the system was fine. And then I made that horrible mistake. Oh, how I wish I didn’t!!
I read on some website, that you are supposed to flash the twrp as boot.img, not as recovery.img. Seemed illogical and stupid to me, but in the end I tried it. Of course, this just bricked my phone, with no possibility to boot. After hours of googling, installing, trying and crying, I managed in the end to flash back stock boot.img. But at that time, I didn’t know my build number (b359), and I flashed boot.img b351. So now I have a phone which boots into the system b359 with boot.img b351, but with lot of errors.
- developer options, security options, display and factory reset option doesn’t work and just crashes. Therefore I am not able to flash the correct boot.img b359 or anything else at all from pc, no way to enable usb debugging and oem unlocking. Adb devices → nothing. I am able to use fastboot (fastboot devices sees the phone), but when try to flash something, I get error “command not allowed”. Also I can’t enable unknown sources installation, which bothers me a lot. And I can’t make factory reset to restore the crashing settings. Also I can’t change display timeout, and original 30 secs is super annoying.
- I am not able to uninstall even apps installed by me, always just restarts system UI and app stays.
What I tried so far:
- flashing correct boot.img from pc, not working because of dev options crashing
- go into recovery, but stock one is overwritten with unfunctioning twrp, always just get stuck on “your phone was unlocked blah blah… your device is booting now”, but it never does, have to hard reboot
- go into huawei erecovery, which is working, but when I try to resolve problem from there, always ends up with errors and crashes
- connect to pc and use HiSuite, system recovery tool here always says “no problem detected”
- updating to b361 through system update settings, always crashes on 5% and sends phone into “your phone was unlocked blah blah… your device is booting now” error
- downloading the proper b359 as and update.app file, put it in dload internal storage → same error during update, put it in dload sdcard → same error, no matter which way I use to start the update
- boot into twrp or stock recovery.img through fastboot without actually flashing it, anyway error “command not allowed”
- do factory reset or update through dial codes (i.e. *#*#123456#*#* …), nothing worked
My pc is windows 10, all drivers up to date. Using powershell as an admin. Am an idiot for not making backup of the phone before I started...
So, now I have more or less functioning phone, but I can’t uninstall any apps at all, can’t install from unknown sources, can’t do nothing from pc, can’t make any update, and lot of important settings keep crashing.
I can use the phone like this, but if somebody could think about some solution for this ****ed up situation I got myself into, I would be grateful to him/her for the rest of my life.
Sorry for a long post.
Thank you in advance and have a nice day
I think using Hisuit will help. Enter Fastboot and connect ur phone to ur computer and use system recovery toll