Hi, so a friend give me this phone with this problem and I'm trying to solve it. The fastboot menu works, bootloader is locked, and the options there are start, factory mode, meta mode and recovery mode. The only one that works is recovery mode, the other 3 get stuck in the m logo and at the bottom says powered by android (no animation or anything). Recovery mode says no command, but by pressing power+vol. up you can acces it. However, when i do that, it only shows at the bottom "supported api: 3". No options or menu, so i don't know what to do. It has usb debugging off and oem locked, and when connected to the pc, fastboot devices and adb devices commands don't recognised the phone.
Any suggestions?
v5tge said:
Hi, .
Any suggestions?
Click to expand...
Click to collapse
Option A=Try installing dm disabling dm verity via fast book it that doesn't work restore boot.img and then try again.
Option B: (Data is lost but success is assured)
You can try downloading with
https://mega.nz/folder/LKgzUYwI#BGxxvjc5K3UaLOsCUqjwRg
Instructions here:https://forum.xda-developers.com/moto-e4/development/stock-stock-rom-moto-e4-mediatek-sku-t3804870
Related
Hey guys I was trying to flash MIUI 8 on my a6000 lenovo. Bear with me because I'm new to this so I might have screwed up.
Rooted and installed TWRP perfectly. Phone was running kitkat.
I then, through TWRP tried to flash MIUI 8 from http://forum.xda-developers.com/lenovo-a6000/development/rom-miui-7-lenovo-a6000-a6000-t3355692
After first swiping right to install the zip, i got an "error executing binary in zip" error. Wiped dalvik,etc. again and tried again and then I got a MD5 file not found "warning". It was not in red letters and after that message there was no progress bar or anything and the phone just stopped responding. I assumed it wasn't working and few minutes later took the battery out. After trying to boot again it would give me the "mi.com" boot screen (not the default lenovo I used to get) and won't boot into neither recovery nor normal mode. (for recovery boot I'm trying holding both volume buttons and the power button at the same time. perhaps that is different now?)
I'm guessing the flashing was going on and i interrupted it. How can I fix this?
Update: It boots into MIUI now however pretty much nothing works as expected. It wont even go into settings. Recovery still seems botched and i cant boot into it.
TLDR: Recovery broken cant boot into it. Can boot into MIUI with very limited capabilities. Cannot select USB debugging and "adb devices" won't find the phone. What can I do?
Alright nevermind guys I managed to fix it. for anyone wondering or having the same issue, i tried many things but what I think worked is this:
Turnt on my phone in fastboot mode (hold volume - and power button) , connected it to the computer and used command "fastboot flash recovery recovery.img" to flash the old TWRP i had on my computer. After that I managed to boot my phone in recovery mode and reflash the rom properly. The weird thing is, my phone could not be recognized by the computer and "adb devices" gave me nothing back so I thought using any fastboot command wouldn't work. Oddly, it did and it flashed TWRP back into my phone.
was on CM13/TWRP, suddenly my phone rebooted while i was talking, i looked at it and it had a linux logo on it....waited a bit, didn't go away, so i held power until it turned off.....then it wouldn't turn on.....so i tried recovery, nope. tried fast boot, that worked.. tried to reflash TWRP from fastboot command, failed because device is not unlocked.
can't run oem unlock because i can't get in the OS to developer mode to enable it.....
so i've been trying to do the qualcom recovery, windows 10 laptop, tried all the versions of the qualcom recovery/drivers i can find...... the recovery tool keeps giving me a red error on line 4. either that or it flat out crashes the whole program.
whats my next step? i'm attempting to run it on a windows 7 computer now thinking that may make a difference.
anyone have any thoughts?
Hello,
My issue is really weird. I was using No Limits rom with oos 4.5.1
Later, i've reverted back to stock rom and my actual version is Pie with OOS 9.0.7 . Also my recovery is stock at the moment.
The issue is, i can not enter to fastboot mode. İ am selecting that and pressing power button to start fb mode but my device reboots back to desktop without entering to mode. Device is up and running, no stuck at bootloop or etc.
Now i can not load any recovery, root etc. Tried all combinations to enter but doesnt work at all.
İs there any solution to solve this ?
Kaanb93 said:
Hello,
My issue is really weird. I was using No Limits rom with oos 4.5.1
Later, i've reverted back to stock rom and my actual version is Pie with OOS 9.0.7 . Also my recovery is stock at the moment.
The issue is, i can not enter to fastboot mode. İ am selecting that and pressing power button to start fb mode but my device reboots back to desktop without entering to mode. Device is up and running, no stuck at bootloop or etc.
Now i can not load any recovery, root etc. Tried all combinations to enter but doesnt work at all.
İs there any solution to solve this ?
Click to expand...
Click to collapse
Instead of trying to enter fastboot mode from android did you tried to enter bootloader by holding power + volume up while powering the device on.
Also if you have enabled USB debugging you should be able to enter fastboot mode by connecting to a pc and using platform tools: adb reboot bootloader
strongst said:
Instead of trying to enter fastboot mode from android did you tried to enter bootloader by holding power + volume up while powering the device on.
Also if you have enabled USB debugging you should be able to enter fastboot mode by connecting to a pc and using platform tools: adb reboot bootloader
Click to expand...
Click to collapse
Hello, tried that ways too, and it reboots to the desktop anyway. On pc, when i wrote that command, it reboots again.
İ guess something happened to the bootloader firmware if it exists..
Kaanb93 said:
Hello, tried that ways too, and it reboots to the desktop anyway. On pc, when i wrote that command, it reboots again.
İ guess something happened to the bootloader firmware if it exists..
Click to expand...
Click to collapse
Then I recommend to flashing everything from scratch with https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
Hey their. So i jsut bought a one plus 6t and started playing around iwth it. I tried to get twrp and i got it but when i rebooted to os i had no wifi. So i download magisk zip and flashed it. After this i got stuck in bootloop and so i wne to twrp and wiped everything except system. Then i rebooted and got this message Qualcomm CrashDump Mode Attempted to kill init! exit code=0x0000000b do_exit. Then i freaked out and accidently wipes system too. Now i think i have a complete brick as adb still works but i cant transfer any file from pc to phone because theirs no system. Please help!!!
Never wipe system and vendor on A/B devices, literally, never.
Boot twrp and flash OOS or use msmdownloadtool.
What do you mean flash OOS. Like flash a fastboot file? And what version of msmdownloadtool should I get as their is no system. Should I get 10 cause that was my last system or it doesn't matter.
Update. I left twrp after flashing a stock image and now adb doesn't recognize my phone. When booting into recovery I go into the one plus recovery. Now I'm really screwed.
Okay now im really screwed. Whenever I boot with power up or power down I get sent to the bootlaoder page that says fastboot mode products name. I cant leave this page however. On the options above the information I click reboot recovery I get sent back to this page.
UPDATE. My phone is a literal brick now. It won't even turn on. I tried to force reboot it before and after it powered off it wont turn on. Its fully charged and when connecting to charger of holding buttons nothing happens. I have no warranty so Im hoping that someone can help me.
The "bootloader page" is fastboot and that's normal because there's no system to boot, you wiped that partition... and ADB only recognizes the phone when the boot process ends and ADB is enabled in the phone.
If you press vol up + down when you connect the usb cable the phone boots in EDL (Emergency Download Mode) mode, long press power + vol up to leave that state.
Now, download msmdownloadtool from here, extract the file, power off you phone, conect the usb cable to your pc, press vol up + down and connect the usb cable to the phone, open msmdownloadtool and flash the OS.
Edit: Read this thread for more detailed instructions.
What do you mean by flash the OS. The OS in the system or do I have to download one?
whenever I plug in my device it vibrates and then goes into the fastboot page. Also adb can detect it if I type in fastboot devices.
So i go the device to work and MsM worked until 4 seconds and then It said param preload for status of connection and status of last communication says device not match image
Try with the fastboot ROM.
When i downloaded another version of MsM it did not say no image match instead it stays at 4sec and says recording download time
Can you give me instructions on how to use the fastboot room? Like after i download it what should i do with it?
Download the rom, unpack it, boot your phone in fastboot (Power + vol up + vol down), connect the phone to your pc and execute the "flash-all.bat" file, and just wait.
um what is flash-all... How does it work what am i supposed to do.
what does unpack it mean?
Hey their im going to assume you meant to unzip the file and then open the file called falsh-all.bash. In that case when i do that i get this message "error: failed to load 'images.zip': No such file or directory
Press any key to exit..." In a CMD window
I've been attempting to re-load factory firmware on this device, but when I hold volume-up and plug in a USB cable, it would flash the "download" screen for a part of a second then jump to the "Cannot verify the firmware" screen, then go straight to twrp rather than download mode.
So, I rebooted to fastboot mode, and did a "fastboot flashing lock" hoping that it would stop trying to verify the firmware and just get straight into download mode for LGUP. This seems to be where my biggest mistake was.
So, now, I get a quick flash of download mode, then straight into "Your device is corrupt." How can I prevent the "Your device is corrupt" and get back to the "Download" mode where LGUP will actually see it and work with it?
Thanks!
Got into fastboot. Unfortunately, I haven't checked "Enable OEM Unlock" in Developer options, and it won't boot to anything anymore.