Related
Hi guys Zeph here.
I've just rooted my Redmi Note 4 without any problems. I've tried to install several custom ROMs like HAVOC, Pixel, etc using TWRP but it showed some error I don't know. My backup ROM did not install so I've tried to install Global Stable ROMS from Internet but those were shown as corrupt. I've also tried using fastboot, ADB sideloader but same problems are happening. So basically my phone is just a hollow without any OS. Any solutions please because that is my only phone.
Here are some screenshots..
Can you boot up normally?
If not what happens, when you try?
gabtit7 said:
Can you boot up normally?
If not what happens, when you try?
Click to expand...
Click to collapse
Sorry when the backup ROM didn't get installed I had completely wiped all data for sake of installing Global custom ROMs. But it still didn't get installed. So my phone is like DOS without any OS.
Oh. Well thats a problem.
First of all:
Go to https://c.mi.com/oc/miuidownload/detail?device=1700309
dowload the rom (its a zip) and transfer it to your phone
go to twrp
flash it with twrp
reboot to system
Now if (while booting up) it says "The system has been destroyed":
Just keep booting in twrp, back to system, back to fastboot and repeat for some time and multiple times a day. For some reason thats how you call the autorepair to wake up, it will remove the ROM you just installed and probably install a backup one on its own
If this doesnt work too:
I will suppose you have a pc with fastboot & adb drivers available
Since the phone is alr in deep s***, lets try something quite risky
1)
go to twrp > wipe > format data
2)
connect your phone to pc while in fastboot
and execute these commands
fastboot erase system
fastboot erase cust
fastboot erase boot
fastboot erase vendor
CAREFUL: NOW YOUR PHONE IS BRICKED, BUT FIXABLE (probably)
3)
repeat the steps on the top of this message
All this should fix the problem, if not i am sorry but the phone will be unrepairable without any professional technician
Hi! My old phone is booting into fastboot mode, when I try to boot normally I get a black screen, the "Power off" button appears when I hold the power button. The bootloader is not unlocked and the phone was never rooted. Wiping the user partition does not help. It is visible in fastboot mode and I can enter stock recovery, though trying to adb sideload a stock rom returns an error (footer is wrong; signature verification failed). Trying to fastboot boot twrp or recovery.img doesn't work either. I've ran out of ideas, what should I do to get this phone to work?
Try flashing the stock ROM with fastboot. I'm pretty sure ADB doesn't let you flash onto your phone because using your phone with ADB means that it's still powered on - which can cause some issues. You can also try and unlock your bootloader through fastboot, and then flash a recovery and custom ROM.
Both failed. I attached the errors I recieved.
crepper4454 said:
Both failed. I attached the errors I recieved.
Click to expand...
Click to collapse
Try "fastboot bootloader unlock", maybe. Also: Is there a flashall.bat in the stock ROM folder? If there is: Connect your device while in fastboot, and double-click it.
crepper4454 said:
Both failed. I attached the errors I recieved.
Click to expand...
Click to collapse
Try this maybe. I know you can't wipe through the stock ROM, so, try the command: "fastboot -w". That'll wipe everything off the device.
[INDEX][Osprey][Merlin] Moto G Factory Firmware Images
Disclaimer: I am not responsible for anything that happens as a result of flashing these files. Your destiny is your own. Moto G (3rd Gen) Factory Firmware Images - Provided by Firmware TEAM - Please report broken links. New Mirrors welcome...
forum.xda-developers.com
I can wipe through stock recovery. I did fastboot -w and it cleared the cache and userdata partitions, they were already clean afaik. Typing fastboot bootloader unlock returns unknown command. There are no .bat files in my firmware. I can try downloading one from the site you linked, but I don't know what to do with it if fastboot flash does not work.
crepper4454 said:
I can wipe through stock recovery. I did fastboot -w and it cleared the cache and userdata partitions, they were already clean afaik. Typing fastboot bootloader unlock returns unknown command. There are no .bat files in my firmware. I can try downloading one from the site you linked, but I don't know what to do with it if fastboot flash does not work.
Click to expand...
Click to collapse
Try this: https://forum.xda-developers.com/t/guide-osprey-fastboot-flashing-factory-firmware-images.3187750/
It says there that the "preflash validation failed" error occurs when the firmware being flashed is older than the one already installed. I will try downloading a newer version and flashing it. Will update here.
Update: I have dowloaded a newer rom and tried to flash it. This time got different errors (picture attached, this went for every sparsechunk). I think I know the reason but I do not know how to solve it. This might not be the exact stock rom of this phone so I cannot flash it with a locked bootloader. Could someone help me finding the correct rom or suggest a different solution?
Yooooo. I have the Moto e5 Cruise and so does my wife. We bought them in 2018 from Cricket and last night hers went to emmc failure, also known scientifically as 'no worky' mode.
The phone would only load in fastboot and had tried to use my Moto RSD tool to reflash but the phone would not detect in anything but fastboot mode.. Here's where it gets interesting....
There is a piece of software called the Lenovo (which now owns Moto) Rescue and Smart Assistant that can reflash your phone back to factory, no matter your sub-variant (cricket, metro, etc). Without having a fresh backup on hand, you're going to be beholden to the last cloud sync or manual backup you have because all data will be wiped in the below process.
BTW: Just run the assistant as it seems to be the easiest 'back-to-stock/working' tool I can find. Going to fastboot alone yielded weird errors since i didn't have the unlock code for the 'fastboot oem unlock [code goes here]' command.
**RESTORATION PROCESS**
This will apply to multiple Lenovo/Moto Mobility devices. Unknown at this time how many have been impacted by this seemingly pre-planned failure on Lenovo's part.
If your phone is stuck in fastboot mode where MTK download mode does not load, nor does adb, follow these simple steps:
(NOTE: BACKUP YOUR FILES IF POSSIBLE)
1. Click the link above to be directed to the Lenovo software download page and run the installer on your PC (Sorry Mac users :'().
2. The software, once installed, will require you to sign up for OR link a google, fb, g+, etc account to it for purposes of creating a Lenovo ID. Once signed in, click on 'Rescue Now'.
3. With your phone in fastboot mode, allow the software to download the firmware for your phone.
4. Once the firmware has finished downloading and validating, click on 'Rescue Now' once again. Your phone will begin the reflashing process.
That... actually worked. The program found the required ROM and flashing went without problems. Thank you very much @kmt5150 .
crepper4454 said:
That... actually worked. The program found the required ROM and flashing went without problems. Thank you very much @kmt5150 .
Click to expand...
Click to collapse
No problemo! Glad it worked!
Okay so yesterday I decided to finally try to install TWRP to flash a custom rom on the system, but never thought it would give so much headache. My drivers were bad, the system locked and android 11 updating making the phone all sorts of bugs, I was anxious to get rid of it, and I did somehow. I was unable to flash TWRP into the recovery as the system partition type is different than usual for it seems, but the recovery partition was all weird, "no command" was stuck in the screen even after a hard reset through there. So I got Magisk and got Root and used Smart Flash to install TWRP through the running system and it landed successful. But when going to the recovery the TWRP screen was flickering, but I could send ADB commands yet and boot normally, I just couldn't access the recovery functions yet. So I flashed a different version of the TWRP with the IMG and the zip folder and nothing worked then I realized that maybe I should erase the partition before flashing it and then the murder. I found a tutorial on erasing stuff, but the whole process cost me more than twelve hours as I messed with so many things and was kinda learning the hows and dos.
But then I saw the command "fastboot erase system -w" that was a shortcut for all cleanup processes and I was wanting to wipe it again even to recover my google backup and be able to use my messenger apps. But it did erase, of course, the whole system and everything, simply destroying everything, but yet stuck in the fastboot screen. What I did? Well, I downloaded the TGRZ of an older version of xiaomi mi a3 firmware, the android 10, as I was tired and thought that maybe if I downgraded it I would get my phone to get rid of android 11 bugs and sleep for good till tomorrow, that is today. I ran the script to wipe anything and install the system over it and it did successfully, then the message "successfully installed, press any key to finish" but then the prompt closed and the phone tried to reboot but fell into a hard brick. The computer recognizes the device as the name "QUSB_BULK_CID:0411_SN:EFCF04FD" and the hardware ID "USB\VID_05C6&PID_9008" matches the original.
So is there anything I could do yet? Phone warranty ended in january and that's why I tried that process, it is any worth?
BillyWroth said:
Okay so yesterday I decided to finally try to install TWRP to flash a custom rom on the system, but never thought it would give so much headache. My drivers were bad, the system locked and android 11 updating making the phone all sorts of bugs, I was anxious to get rid of it, and I did somehow. I was unable to flash TWRP into the recovery as the system partition type is different than usual for it seems, but the recovery partition was all weird, "no command" was stuck in the screen even after a hard reset through there. So I got Magisk and got Root and used Smart Flash to install TWRP through the running system and it landed successful. But when going to the recovery the TWRP screen was flickering, but I could send ADB commands yet and boot normally, I just couldn't access the recovery functions yet. So I flashed a different version of the TWRP with the IMG and the zip folder and nothing worked then I realized that maybe I should erase the partition before flashing it and then the murder. I found a tutorial on erasing stuff, but the whole process cost me more than twelve hours as I messed with so many things and was kinda learning the hows and dos.
But then I saw the command "fastboot erase system -w" that was a shortcut for all cleanup processes and I was wanting to wipe it again even to recover my google backup and be able to use my messenger apps. But it did erase, of course, the whole system and everything, simply destroying everything, but yet stuck in the fastboot screen. What I did? Well, I downloaded the TGRZ of an older version of xiaomi mi a3 firmware, the android 10, as I was tired and thought that maybe if I downgraded it I would get my phone to get rid of android 11 bugs and sleep for good till tomorrow, that is today. I ran the script to wipe anything and install the system over it and it did successfully, then the message "successfully installed, press any key to finish" but then the prompt closed and the phone tried to reboot but fell into a hard brick. The computer recognizes the device as the name "QUSB_BULK_CID:0411_SN:EFCF04FD" and the hardware ID "USB\VID_05C6&PID_9008" matches the original.
So is there anything I could do yet? Phone warranty ended in january and that's why I tried that process, it is any worth?
Click to expand...
Click to collapse
You should never try to install software for another board (mi mix 3 global is codenamed "perseus")...
If you are unable to reach fastboot and recovery, you may refer to this, since it sounds like your phone is in EDL mode:
Reboot to EDL mode from FASTBOOT!
Reboot to EDL mode from FASTBOOT! No more Test Point Method needed Technical Details: Redmi Note 3 support rebooting to EDL in Android Bootloader aboot module (the "reboot-edl" command) but fastboot utility doesn't recognize "reboot-edl" in the...
forum.xda-developers.com
I never encountered this issue so only do this if you're absolutely sure you have no other means of flashing anything on it (i.e. through fastboot), and use the appropriate firmware at all times for your specific model
CriGiu said:
You should never try to install software for another board (mi mix 3 global is codenamed "perseus")...
If you are unable to reach fastboot and recovery, you may refer to this, since it sounds like your phone is in EDL mode:
Reboot to EDL mode from FASTBOOT!
Reboot to EDL mode from FASTBOOT! No more Test Point Method needed Technical Details: Redmi Note 3 support rebooting to EDL in Android Bootloader aboot module (the "reboot-edl" command) but fastboot utility doesn't recognize "reboot-edl" in the...
forum.xda-developers.com
I never encountered this issue so only do this if you're absolutely sure you have no other means of flashing anything on it (i.e. through fastboot), and use the appropriate firmware at all times for your specific model
Click to expand...
Click to collapse
well it seems I recovered it back, I bricked it and somehow it just got into EDL mode without cable or opening it up. So I found a tutorial back on reddit showing how use GFIL to install the stock rom back. I used android 10 stock rom before bricking it, but as I just flashed everything on empty partitions it didn't work, it seems that the Qualcomm setup needs some kind of previous work to set everything up. Anyways I managed to boot it, but now I'm aware that I should use Lineage recovery instead of TWRP as Mi A3 support is lacking, that's why after installing it I got it flickering (no compatible version with the latest Android 11 firmware).
BillyWroth said:
well it seems I recovered it back, I bricked it and somehow it just got into EDL mode without cable or opening it up. So I found a tutorial back on reddit showing how use GFIL to install the stock rom back. I used android 10 stock rom before bricking it, but as I just flashed everything on empty partitions it didn't work, it seems that the Qualcomm setup needs some kind of previous work to set everything up. Anyways I managed to boot it, but now I'm aware that I should use Lineage recovery instead of TWRP as Mi A3 support is lacking, that's why after installing it I got it flickering (no compatible version with the latest Android 11 firmware).
Click to expand...
Click to collapse
hello, im having maybe a similiar case with my phone (in this case its a MI A3) i installed "succefully" evolution x 6.3 on my phone and everthing was ok with a few bugs, the only problem was that mi cannot connect to internet, so i decided to restart the phone and now my phone just don't turn on, the power button don't respond and i cannot start up my phone and its just a black screen, if u remeber ¿can u pass the tutorial that u saw on reddit? maybe it can help me
Hi Guys,
I think I f...ed up big time...
My device was rooted and I tried to unroot/factory reset to give it to my wife. Since I'm now sitting here for about 5 hrs I try to summarize what I've been doing:
1. I started with trying to Flash a Factory Image with the ALL-IN-ONE Tool
- My Device was on the Latest Oxygen OS 11 and I just stupidly followed the instructions of the Tool and downloaded a OOS 10 based Stock Rom and flashed it (thats where my nightmare began)
- After I flashed the OOS 10 Stock Rom I was Stuck in at the Open Bootloader warning screen ("the boot loader is unlocked and software integrity cannot be guaranteed ...")
2. Since there is no (at least I couldn't find one for the life of me) OOS 11 fastboot stock ROM I tried to downgrade via an OOS Beta ROM I found in a downgrade guide
- That didn't work either and I ended up stuck at the same Screen
3. After some googling I came across this guide and tried to manually flash a none fastboot OOS 11 ROM by manually extracting all the images of the payload.bin
- After I extracted all the images I flashed them one by one as mentioned in the guide via fastboot and this ended up with
Qualcomm Crash Dump mode dm-verity device corrupted force dump Kernel restart
Click to expand...
Click to collapse
4. After that I panicked a little since I've never seen this error before and tried to Flash the OOS 10 based Stock rom via the ALL-IN-ONE Tool again
- This worked with no errors but now I'm still stuck in the "Open Bootloader warning Screen"
Since then I tried Step 4 with another OOS 11 none fastboot ROM but now I keep getting following error everytime I try to flash one of the extracted images via fastboot (which worked before):
FAILED (remote: Flashing is not allowed for Critical Partitions
Click to expand...
Click to collapse
I did some research, seems like this error indicates a locked bootloader which is wrong, bootloader is still unlocked.
Even if I try to unlock the bootloader again I get the reply that bootloader cannot be unlocked since it already is unlocked.
So now I'm stuck with a completely f...ed up device with absolutely no clue if and how I can fix this.
I really hope anyone of you guys can help ...
Apologies for the bad writing but it's 5 am and I'm tired and frustrated af ...
greetings from Germany.
Timo
EDIT: Oh and yes, I know about the MSM-Tool and tried it but I can't get it to work since my device is not showing. I followed this guide several time but nothing is happening and my device is not even showing in the device manager. Only time it shows in the device manager is when in fastboot mode.
Guys I finally did it.
I deinstalled all stale/inactive drivers and reinstalled the Qualcomm drivers and finally managed to get the MSM Tool up and running and revived the phone.
Solution: I hardbricked my device because of my dumbness. This device is not veux... It s viva. Be cautious my friends...
I unlocked my bootloader and wanted to install TWRP to flash a custom ROM to the device. Unfortunately, right after I tried, device got stuck in a bootloop (Mi logo showing, then closing.)
I tried flashing multiple TWRP files after that. Since there is no official file for this device, I tried the ones given in the forum and a youtube video.
Holding power+up does not open anything. Holding power+down I can go to fastboot. ADB does not see the device (adb devices does not show anything). But fastboot devices does show. (MiFlash tool also sees the device but can't flash the ROM.)
MiFlash first gives the classic crc error, I delete the lines, it passes this error and finally gives another error ("Command failed"). I tried flashing 2 versions (my local version and eu version) of the stock rom in both windows and ubuntu based linux. What am I doing wrong?
Am I doomed? What can be done? Why isn't ADB working? Thank you for replies
turbotales said:
I unlocked my bootloader and wanted to install TWRP to flash a custom ROM to the device. Unfortunately, right after I tried, device got stuck in a bootloop (Mi logo showing, then closing.)
I tried flashing multiple TWRP files after that. Since there is no official file for this device, I tried the ones given in the forum and a youtube video.
Holding power+up does not open anything. Holding power+down I can go to fastboot. ADB does not see the device (adb devices does not show anything). But fastboot devices does show. (MiFlash tool also sees the device but can't flash the ROM.)
MiFlash first gives the classic crc error, I delete the lines, it passes this error and finally gives another error ("Command failed"). I tried flashing 2 versions (my local version and eu version) of the stock rom in both windows and ubuntu based linux. What am I doing wrong?
Am I doomed? What can be done? Why isn't ADB working? Thank you for replies
Click to expand...
Click to collapse
ABD works only if you have enabled USB debugging.
Eventually check here that everything is correct:
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Or try to install a Xiaomi Eu rom (Fastboot).
Extract the zip then run the scrip in the corresponding extracted folder to your O.S.
Fastboot_first install.
xiaomi.eu_multi_VEUX_V13.0.3.0.SKCCNXM_v13-12-fastboot.zip
https://sourceforge.net/projects/xi...files/xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv13/
NOSS8 said:
ABD works only if you have enabled USB debugging.
Eventually check here that everything is correct:
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Or try to install a Xiaomi Eu rom (Fastboot).
Extract the zip then run the scrip in the corresponding extracted folder to your O.S.
Fastboot_first install.
xiaomi.eu_multi_VEUX_V13.0.3.0.SKCCNXM_v13-12-fastboot.zip
https://sourceforge.net/projects/xi...files/xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv13/
Click to expand...
Click to collapse
Hello, I do have my bootloader unlocked and USB debugger is also on.
I tried flashing twrp again, says it worked but does not boot into it. Goes back to boot loop
Then I tried flashing with MiFlash again. Same error
fastboot error remote: command failed
When I google it everyone says my bootloader should be locked. But it is not.
Can I use the hard brick solution with bypass for this problem?
turbotales said:
Hello, I do have my bootloader unlocked and USB debugger is also on.
I tried flashing twrp again, says it worked but does not boot into it. Goes back to boot loop
Then I tried flashing with MiFlash again. Same error
fastboot error remote: command failed
When I google it everyone says my bootloader should be locked. But it is not.
Can I use the hard brick solution with bypass for this problem?
Click to expand...
Click to collapse
All these procedures, Miflash, Twrp, Xiaomi Eu rom are done in Fastboot mode not ADB and obviously the bootloader must be unlocked.
Try the Xiaomi Eu rom.(TWRP included).
NOSS8 said:
All these procedures, Miflash, Twrp, Xiaomi Eu rom are done in Fastboot mode not ADB and obviously the bootloader must be unlocked.
Try the Xiaomi Eu rom.(TWRP included).
Click to expand...
Click to collapse
Tried doing this.. now it s hard bricked.
turbotales said:
Tried doing this.. now it s hard bricked.
Click to expand...
Click to collapse
You have flashed a Xiaomi Eu rom and it does not work?
And with Miflash?
NOSS8 said:
You have flashed a Xiaomi Eu rom and it does not work?
And with Miflash?
Click to expand...
Click to collapse
I tried flashing with Miflash didnt work,
Tried flashing with linux and said it is done, but now device does not open in any way. What should I do?
These are the screenshots of the Xiaomi Eu rom?
What is the version of your phone? (11 pro/Poco).
What rom were you on?
post the Miflash log.
NOSS8 said:
These are the screenshots of the Xiaomi Eu rom?
What is the version of your phone? (11 pro/Poco).
What rom were you on?
post the Miflash log.
Click to expand...
Click to collapse
Downloaded the rom from the link you sent me earlier. My device is veux and had MIUI13 before getting bricked.
Again the device got bricked from the last think i did. Do you know what wen wrong?
turbotales said:
Downloaded the rom from the link you sent me earlier. My device is veux and had MIUI13 before getting bricked.
Again the device got bricked from the last think i did. Do you know what wen wrong?
Click to expand...
Click to collapse
If you tried with Miflash post the log otherwise try and post the log.
Solved, I'm dumber than I thought. This phone is not veux. It's viva. If I were to re-check it I d not be in this position... Let this be a lesson to me. Going to have to take it to the service now.