When she got this Xiaomi 3S I rooted it and put Lollypop xiaomi.eu_multi_HM3_6.9.22_v8-5.1 ROM together with TWRP recovery (don't know what version it was, but it was the latest at that time).
Yesterday we learned that she cannot connect to Gear S2 watch via Samsung Gear Companion app, so I thought that changing the ROM might improve things.
From http://en.miui.com/download-303.html I downloaded miui_HM3SGlobal_V8.2.5.0.MALMIDL_5271576d3b_6.0.zip and after copying it to the local storage I pointed the installer to the zip file. The logs showed that the installer could not mount /firmware and after a half an hour the progress bar reached the end but nothing happened. I left it for at least 10 more minutes, nothing changed. I took a screenshot, which the TWRP log acknowledged, so it wasn't really stuck.
I held the power button and the phone shut down, but now I cannot turn it on. No signs of life whatsoever, no matter what key combination I press now.
What might've happened?
Did I get the wrong ROM? I don't think so.
Was that ROM supposed to be installed over the old one? Xiaomi didn't say no.
Any advice is welcome.
I've created the nandroid backup with TWRP, and backed it off the phone before I started the upgrade, but it's of no use to me now, as I cannot get it back to life.
Guys at Xiaomi boards pointed out to a mistake I've done, apparently one does not flash stock ROM over Xiaomi.eu ROM.
I should've used MiFlash to do it.
You can try to use Xiaomi Deep Flash Cable.
Try to enter EDL mode and use miflash.
Thanks, I've already tried with making my own deep flash cable, but the phone did not react to it as expected. These days I plan to bring it to a repair shop and let them have a go, rather than ordering one of those cables and then wait for a month before I have a chance to play again with it
Related
Tried to unroot, now I have this. Been trying to flash through Odin (PDA md5 file only), gets to 'system', goes about 10 minutes then fails. Nothing on sd card. Im hoping I can save this. Any help would be greatly appreciated.
This is a retail Wifi.
I have the correct USB drivers and can see it in device manager but not in explorer. I do not have the correct ADB SDK, cant seem to find it.
Been reading several threads and watching vids on youtube, nothing seems to do the trick. Im stuck but hopefully not bumming.
This may or may not work for most but this worked heavily for my 2 units that had the same issue. One with a broken nvflash, the other that faced a bootloop and never booted up again. Took almost a week and I felt almost all hope was gone because the bloody service centre's refused to accept the unit's as they were not purchased from the region, rather online. Scumbag Samsung .
[!] This is usually a 90% fix for both broken nvflashes/deep sleep of death, considering you haven't drowned your Tab by now with no hope . I ask that you kindly attempt this once if you haven't before you QQ to the nearest Samsung center like I did.
- Drain your tablet
And by all mean's do so, The quickest way to get this done in less than 2 days or so (Depending on the battery percent charged) is to get a clear tape and tape around the power button pressed.
- Testing if you have drained it completely/Taped it right.
Connect the tablet via USB to your PC, make sure you have the NV Driver files [http://forum.xda-developers.com/show...php?t=1130574]
Just install the driver and proceed to the step where it asks about holding down the [Power button] +[ Volume+] and wait for the constant USB connect/disconnect sounds. It also helps to look at Device Manager to see if it still pops up.
When the battery is completely drained it will stop popping up in the device manager, and your ready to go.
MOST IMPORTANT STEP
You have only 1 and only 1 chance per drain to get this done right. Plug it into the socket charger and see if the charging icon should come up, after being fully drained you should see the charge icon should pop up [100% tested and works, this step is annoying but it's the tablet version of taking out the battery and popping it back in] and what ever you do, DON'T BOOT IT UP NORMALLY, instead press [Power Button] + [Volume -] keys and let go when you see the logo to get into fastboot mode.
Select the android buddy with the [Volume +] key and it will boot into Download Mode.
From here on out everything is easy sailing. Get the right firmware and Odin and flash the firmware you require. It doesn't matter what region you are from, the tablet is made to accept any regional firmware BUT the model number should be the same. Which mean's 7500 for 7500 ONLY.
Edit: Since you have only one chance per drain, I suggest you flash a stock firmware rather than flashing CWM to save it, Because CWM would only fix the recovery, It wouldn't fix the damaged bln. The fastest way to get a stock firmware is grabbing the stock firmware from the Overcome thread
Click to expand...
Click to collapse
Source:
http://forum.xda-developers.com/showthread.php?t=1478361
Ok, killed it that long....actually, just havent had time to get into this or deal with the frustration.
Anyway, it did what it was supposed to, meaning the battery icon came on. then I booted to download mode, plugged it in to the PC and it hooked up to Odin. It ported and I started to load the md5 file. I get stuck at the bootloader.bin. Been sitting there for 40 minutes. Has not failed yet. What now??
Never mind, I am an idiot who needs to read more. Please ignore me.
Sent from my GT-P7510 using XDA Premium HD app
Any and all help is appreciated, nobody is an idiot, except me for bricking this thing.
By the way, about 20 minutes after I posted the screenshot, it failed.
Hello
I need some advice and help if someone can.
My LG V10 was rooted and on latest Eliminators room. It was working perfectly and few days ago while ending the phone call it just switched off.
Since then i have been trying to bring it back to life but without any success .
I can boot it to fastboot but no commands are accepted in fastboot mode, no download mode . It only goes to logo and the information that software can not be checked , further from there it goes nowhere . Since i am mac user , i installed VM of Win 7 and only thing it detects is Qualcom 9008......
Please some advice and help what is possible to do.
In fastboot mode i can not do anything.......
Sent from my iPhone using Tapatalk
This is the exact thing that happened to me last night too. I was wondering if my phone pushed the latest update on accident or something to cause it.
Another thread in the Q & A Section has reports of this happening and maybe being a hardware issue.
I plan on trying to do a full restore back to stock tonight when I get home from work to see if I can bring it back to life. I also read somewhere that you need to have the latest binary for fastboot to work.
The few minutes I messed around with it last night, my fastboot was sending but not writing. I'll keep you posted it I have any success tonight after work.
Side note the thread I mentioned above the S/N for the phones having issues started with 510...
Also, I can get mine to boot into recovery but once I try to erase or install it freezes and boot loops again.
I will play with it from tomorrow again. From yesterday i have gave it to one service center but they have not succeeded to do anything. I have succeeded in one moment to get to download mode which laster only about 2 seconds, not enough even to connect it to lg up, suspecting tht it is maybe something because of VM that doesn't' discover phone complerely. Tomorrow morning i shall pick it up and during next few days i shall try again, if i succeed to find a solution it would be good. I was also planing to do complete factory back up to stock last version. But...
Sent from my iPhone using Tapatalk
bildo said:
This is the exact thing that happened to me last night too. I was wondering if my phone pushed the latest update on accident or something to cause it.
Another thread in the Q & A Section has reports of this happening and maybe being a hardware issue.
I plan on trying to do a full restore back to stock tonight when I get home from work to see if I can bring it back to life. I also read somewhere that you need to have the latest binary for fastboot to work.
The few minutes I messed around with it last night, my fastboot was sending but not writing. I'll keep you posted it I have any success tonight after work.
Side note the thread I mentioned above the S/N for the phones having issues started with 510...
Also, I can get mine to boot into recovery but once I try to erase or install it freezes and boot loops again.
Click to expand...
Click to collapse
I have the same problem with my v10 do you found a solution ?
No. I bought a new phone and my v10 is now a paperweight. I have not really tried too fix either. Jumped on project fi and got a got a 5x on the cheap. Couldn't be happier.
I've had luck flashing my LG from within a virtual machine, running on top of Linux Mint. I tried both VMware Workstation and VirtualBox. Just make sure to install the guest additions within VMware, or the extension pack within VirtualBox. Also download the LG driver and install that inside the VM too. Each VM software may have settings relating to sharing a real USB port with the VM, make sure you look into that and enable the relevant options. Otherwise the VM may not detect the device.
On the other hand, my v10 isn't hardbricked, I'm just going to hold onto it as long as possible until it goes belly-up. Which it will probably do sooner rather than later, if the issues I've had are any indication. If you're only seeing Qualcomm 9008, fastboot not responding to any commands, and no download mode, this def sounds like a hardbrick. If you're still under warranty I would recommend getting it replaced by LG. If you have insurance then cash it in.
This is the 3rd v10 I've had, so far I've done 2 exchanges if I remember correctly. These phones are definitely susceptible to big issues. Like the now famous LG bootloop scenario.
Hope you get this figured out!
Hi guys, sorry if I posted this at the wrong place.
I have a Lenovo s860 and it went into a bootloop. It was stock and all so I thought that I can have my files recovered if I just bring it to a service center so they can get the files first before wiping it or maybe even fixing the bootloop without wiping the device. Well, the thing is, the guy at the service center screwed up and now, when I try to turn it on, I still see the boot screen (Lenovo, powered by Android) but the next screen is like an television with bad signal.
I'm familiar with rooting and flashing ROMs, I've tried it on my Galaxy S2 (yeah I know, it was way back), but I think things are still more or less the same: I need to be able to boot into recovery mode in order to root the device. However, when I tried the Power Button + Volume Up, or any combinations of the Power Button and the Volume Buttons, it just goes straight to the dead screen, I get no response whatsoever.
I also tried to check if adb can detect it, however, it didn't seem to be able to do so. I'm using a MacBook Pro so I know I don't have to install any drivers, I also code Android Apps so I have a background on this.
I think my only option would be to flash the ROM on this dead device but I don't know how to do that. I've also seen some posts that suggest doing some things (I forgot the specifics) while the battery is drained, so what I'm doing for the mean time is to leave the phone open and let it drain which might take ~2 days.
Does anyone know how to flash a ROM on a bricked device? Thanks for any leads.
I only want my Wogiz WX40 to work properly again. It somehow got into a booting loop and I spent many hours figuring out how to flash it due to drivers acting unexpectedly, incorrect instructions for my device and so on.
I finally got it to flash with stock software I got from needrom using SP Flash Tool. However 1) none of the bottom keys work now and 2) it looks as if the resolution is set too high for the device and I think there is also some slowness when using the phone. I have tried clicking upgrade firmware and formatting the entire flash and using different versions of the software and the result is always the same - the bottom keys not working in particular makes it unusable. I tried downloading the stock rom from another location but after downloading it said I needed a password.
So what is the next thing I can try? I'm at my wit's end here and just want it to work again. Thanks for all help.
Anyone know what I should try? For example what custom RAM + firmware might I want to try? At this point I don't care what it is as long as it works. It's a MT6580 device if that helps.
God, I FINALLY got it working.
In case there's anyone else that runs into this: My mistake was getting the stockrom from needrom, every one of those roms for this phone is bad. Get the rom from shareas.us and use SP Flash Tool to flash it, and even then you have to try to get the one that isn't password protected with no password. Leave the battery in, turn the phone off, use option "format + download" in the software and click download BEFORE you connect the phone, NOW connect the phone and after a little while it will start downloading. Disconnect the phone when it's done and switch it on, it will take a REALLY long time to boot up the first time but it should then work.
That's what came from hours of trying to get it to work. The tutorials etc. online are so confusing, even some incorrect instructions like saying I should take out the battery that are completely false and I would never have gotten it to work if I paid more attention to them. I don't ever want to go through something like that again. I finally have my phone back.
I need help with unbricking my Ulefone Power 2.
First, a few words about how the issue came to be: I bought the phone two days ago and after bringing it back home, and powering it on, I noticed that the icons were not the same as the ones that were on the displayed phone's screen (although I found the new ones to be an improvement, I thought that maybe I have to install "the official ROM" no matter how unattractive it was, as the phone would probably work better with it).
So I went to the official ulefone site, saw the instructions for installing the drivers for windows 10 as being fairly easy to do myself, and downloaded the sp flash tool provided on the site and then, of course, downloaded the official stock rom from the ulefone site.
After installing the drivers, I tried to flash the phone and then the first error happened. Naturally, I sought the answers on Google, as any proper boy scout should, and learned in the process that I should hold volume up while connecting the phone.
And it worked!
Alas, my happiness wouldn't last long as another error decided to stand in my way. BROM Error: sec imghdr type mismatch. Of course, I took another trip to Google's search bar.
Then I tried many different solutions, those being:
Downloading Sp flash tool v3 instead of v5 and trying to flash with that one - this one asks something like if I'm sure that my scatter file is legal (how it cannot be, I don't know as it was downloaded from theanufacturer's site). Regardless, i clicked download but it couldn't recognize my phone I guess as nothing was happening when I plugged it in)
Afterwards I tried to format the phone using the sp flash tool v5 and then flash the ROM onto my phone but that also did not work (with the exact same error as last time - imghdr type mismatch).
Now I have a phone that cannot power up and when plugged in it constantly connects/disconnects regardless of me holding down the volume up button (could be that I'm holding down the wrong button).
Please, is there anyone who can help me unbrick my phone? I just want to flash the stock ROM onto it, that's all