Hi guys,
I got unlock permissions from Xiaomi today, and I wanted to install Cyanogenmod 13 beta 2 as I hate MIUI with passion. Yet I couldn't unlock my device ("Couldn't verify device" on 50% of verifying). Went through some googling, found out I have to update my 7.3.2.0.0 Global to Developer version. (Yes, I have that infamous 7.3.2.0.0 rom everyone hates and I am trying hard to get rid of it.)
So I tried it. Went to Updater, chose "Choose update package" and chose the package I've downloaded from official miui site, which was located in "downloaded_rom" folder in root right as official manual said.
And the phone turned off and started again.
Yet nothing happened. It just restarted without actually doing anything. My all data are as they were, my version is still 7.3.2.0.0 Global.
Recovery mode update doesn't work, as I don't get that usual recovery mode menu, but just a picture showing me I should plug my Redmi into PC (does nothing when I do).
Fastboot update has this notice underneath it: "If your device is locked. please click here to unlock it first." ... hell, I'm trying to do that whole time, that's why I need to change that ROM first.
I've ran out of options. And so I'm turning to you guys - help me, please.
I'm not an experienced user, haven't owned Android for like 3 years, although I've flashed some roms earlier. But I need to get rid of this vendor rom. Google play services are terribly unstable on it, for example.
Ask me any additional questions you need to know. I'm not married and I own a dog, for example.
Any help is appreciated. Thank you very much.
EDIT: That title doesn't really reflect my thread at all. I just wanted to talk about the first updating option, but then I started ranting about it all and couldn't stop. Please, forgive me the title isn't really pinpoint right.
EDIT2: My recovery looks like this: choimobile *dot* vn/attachments/vao-che-do-download-redmi-3-jpg.21534/ ... as a newbie user I can't post links, so please, exchange that *dot* for an actual dot and you'll see. I don't speak chinese.
I had that too, you need to flash it via fastboot
http://en.miui.com/a-234.html
Edit: or you could flash SpaceX via fastboot without unlocking bootloader, and then flash via the TWRP installed with that. People say that works.
Thing is, I can't see my device in MiFlash. No idea why - on "adb devices" it shows up without any problems, but in fastboot mode it just doesn't cooperate.
Could that be because I'm not using the original cable? Heard it can cause some issues. Can't try it atm sadly.
Sent from my Redmi 3 using Tapatalk
Barty19 said:
Thing is, I can't see my device in MiFlash. No idea why - on "adb devices" it shows up without any problems, but in fastboot mode it just doesn't cooperate.
Could that be because I'm not using the original cable? Heard it can cause some issues. Can't try it atm sadly.
Sent from my Redmi 3 using Tapatalk
Click to expand...
Click to collapse
In normal Google fastboot.exe, I couldn't see my device, but in MiFlash's fastboot.exe, I could.
Open the folder with the fastboot.exe you want to check if it's working, shift+right click and "open command window here", then run "fastboot devices".
Also, to open fastboot mode you need to use power + vol up and it opens to that image, no menu. Or was it vol down? Try the one that opens to that image directly, no menu.
Vol down it was. Anyway meanwhile you were writing your advice I've deleted some drivers that were apparently messing with my device and now I see it in MiFlash! Yay!!!
Well, let's hope I won't screw it now. I'm in a middle of SpaceX download. Should I try to MiFlash a normal MIUI with a locked bootloader, or should I do it through SpaceX?
Barty19 said:
Vol down it was. Anyway meanwhile you were writing your advice I've deleted some drivers that were apparently messing with my device and now I see it in MiFlash! Yay!!!
Well, let's hope I won't screw it now. I'm in a middle of SpaceX download. Should I try to MiFlash a normal MIUI with a locked bootloader, or should I do it through SpaceX?
Click to expand...
Click to collapse
What I did is I installed SpaceX MIUI 8 by ManhIT and it came pre-loaded with TWRP recovery and then I booted into the recovery by MIUI 8's updater app and bam....there you go. Now you can flash any ROM you'd like. Btw, I did this while my bootloader is still locked; never went to Xiaomi to unlock it for me. I've flashed several locked bootloader roms such as CM 13, CM12.1 , and locked versions of MIUI roms and I've never encountered any bricks....yet lol
I DID IT!
Not quite your way, to be honest - the fault was in my already installed (and faulty) PC drivers. Yet I did it with your support and I really appreciate the fact you were willing to help me with the problem. Thank you very much, mate.
Anyway, good night.
*a very happy Barty*
Barty19 said:
I DID IT!
Not quite your way, to be honest - the fault was in my already installed (and faulty) PC drivers. Yet I did it with your support and I really appreciate the fact you were willing to help me with the problem. Thank you very much, mate.
Anyway, good night.
*a very happy Barty*
Click to expand...
Click to collapse
Cheers to you my friend!!
Related
Hello,
I just jumped on a good deal for Xperia Z5 (E5823) with software issue. Device boots up to the Xperia logo screen and hags there. I am preparing myself for flashing but hoping a simple hard reset might solve the problem. What should my steps be? I already downloaded Flashtool and did some reading on the forum to get myself familiar with the process. Looks like I will need to download FTF file (I am in US, prefer to have unbranded with minimal carrier bloat) and can use your advice on which version/file to start with. Ideally I would want to root as well, but for now more concerned about restoring back to stock. I did read that Lollipop has a better performance, but open to suggestions for whatever is easier/stable. Any guidance/advice is appreciated (with links to tools or downloads if avail). Is there a way to tell what version # along with region/customization I have installed now?! Should I try the Sony Companion software?
For the record, I have successfully flashed custom ROMS on various Samsung/LG devices, as well as Nexus 4/5. Therefore, feel pretty confident this should not be impossible or any harder. Thanks A LOT.
An update after spending few hours yesterday. PC Companion doesn't recognize the phone when attempting to repair (Vol down + insert USB). It did install few drivers when connected to PC, and it looks like the phone does go into flashmode (as indicated by LED staying green). Then tried the Flashtool, created FTF file (based on tutorial at XperiaBlog) and again the same thing, can't get the phone to be recognized in flashmode. It does respond in fastboot mode and able to get some identifying information. I couldn't find any information on how to flash system, kernel, etc through fastboot (was hoping to use the Flashtool FastBoot mode option, but picking corresponding SIN files resulted is fail errors). I am afraid that flashmode might not work for me as the phone might not have USB debugging enabled (not sure what was done to it and who had it prior).
Are the other alternatives/methods I should try? I wish there was a way to send flash commands from ADB command prompt (like with Nexus phones) and from fastboot mode. Any ideas? Really love the phone, though and want to get it repaired to replace my huge LG! Thanks everyone.
coolmen777 said:
An update after spending few hours yesterday. PC Companion doesn't recognize the phone when attempting to repair (Vol down + insert USB). It did install few drivers when connected to PC, and it looks like the phone does go into flashmode (as indicated by LED staying green). Then tried the Flashtool, created FTF file (based on tutorial at XperiaBlog) and again the same thing, can't get the phone to be recognized in flashmode. It does respond in fastboot mode and able to get some identifying information. I couldn't find any information on how to flash system, kernel, etc through fastboot (was hoping to use the Flashtool FastBoot mode option, but picking corresponding SIN files resulted is fail errors). I am afraid that flashmode might not work for me as the phone might not have USB debugging enabled (not sure what was done to it and who had it prior).
Are the other alternatives/methods I should try? I wish there was a way to send flash commands from ADB command prompt (like with Nexus phones) and from fastboot mode. Any ideas? Really love the phone, though and want to get it repaired to replace my huge LG! Thanks everyone.
Click to expand...
Click to collapse
Why couldn't you use adb? I use it to flash the recovery every once in a while, I hate flash tool. It took me a good 4 different PCs before I found one it would work on
civicsr2cool said:
Why couldn't you use adb? I use it to flash the recovery every once in a while, I hate flash tool. It took me a good 4 different PCs before I found one it would work on
Click to expand...
Click to collapse
I gladly would, except that I am not very comfortable using it due to lack of experience and available zips for my Z5 compact. Can you point me to that info and how to make zips to flash and what to start with? I am willing to try it.
Also, how can I check if my boot loader is unlocked? Can't seemed to find a command to use. Thanks again.
Any pointers for zips or how to flash a rom through fastboot? Thanks.
coolmen777 said:
Any pointers for zips or how to flash a rom through fastboot? Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2277112
We have a couple aosp Roms available to flash, I'd try cm13. I don't know if you've tried to unlock your bootloader yet or not but you should try that. You could also try flashing zombie kernal and see if that'd boot up.
civicsr2cool said:
Why couldn't you use adb? I use it to flash the recovery every once in a while, I hate flash tool. It took me a good 4 different PCs before I found one it would work on
Click to expand...
Click to collapse
civicsr2cool said:
http://forum.xda-developers.com/showthread.php?t=2277112
We have a couple aosp Roms available to flash, I'd try cm13. I don't know if you've tried to unlock your bootloader yet or not but you should try that. You could also try flashing zombie kernal and see if that'd boot up.
Click to expand...
Click to collapse
Thanks for the reply and guidance. I would prefer to stick with Stock Xperia software and launcher. From my experience, CM tends to be buggy and I need full stable functionality with max battery (hoping to give Stamina a test). I am not sure if the bootloader is unlocked and don't want to mess with it unless I absolutely have to (does unlocking BL still messes with DRM keys for camera processing?) Wish I could see if it is unlocked somehow, maybe someone tried to flash/root it and messed up the bootloader somehow.
I will look at zombie kernel (does it need unlocked bootloader or recovery to flash, will it work with stock ROM?) Thanks again for your help.
coolmen777 said:
Thanks for the reply and guidance. I would prefer to stick with Stock Xperia software and launcher. From my experience, CM tends to be buggy and I need full stable functionality with max battery (hoping to give Stamina a test). I am not sure if the bootloader is unlocked and don't want to mess with it unless I absolutely have to (does unlocking BL still messes with DRM keys for camera processing?) Wish I could see if it is unlocked somehow, maybe someone tried to flash/root it and messed up the bootloader somehow.
I will look at zombie kernel (does it need unlocked bootloader or recovery to flash, will it work with stock ROM?) Thanks again for your help.
Click to expand...
Click to collapse
I'm only trying to suggest things that could get the phone working again not permanent solutions lol I don't run cm13 yet as it's definitely not refined. Flashing a stock ftf should be able to bring you to complete original specs without unlocking bootloader or anything.
civicsr2cool said:
I'm only trying to suggest things that could get the phone working again not permanent solutions lol I don't run cm13 yet as it's definitely not refined. Flashing a stock ftf should be able to bring you to complete original specs without unlocking bootloader or anything.
Click to expand...
Click to collapse
Lol, I understand now. It looks like the bootloader might still be locked as I am unable to flash zombie kernel (command: "fastboot flash boot boot.img" results in sending OK, but Failed: remote command not allowed). Looks like I am stuck to trying to unlock a bootloader to keep trying to revive the phone. Just bothers me that I can't get into Flashmode (even after installing drivers that come with Flashtool). Could this be because the phone might not have USB debugging enabled? Is there a way to try to flash the stock through fastboot (as zip) instead of ftf?
My big concern is loosing TA partition and associated DRM keys (any way to back it up from fastboot or toolkit?). Or is that not a factor with the hack available now? Sorry for all these questions, just getting more and more frustrated with this.
coolmen777 said:
Lol, I understand now. It looks like the bootloader might still be locked as I am unable to flash zombie kernel (command: "fastboot flash boot boot.img" results in sending OK, but Failed: remote command not allowed). Looks like I am stuck to trying to unlock a bootloader to keep trying to revive the phone. Just bothers me that I can't get into Flashmode (even after installing drivers that come with Flashtool). Could this be because the phone might not have USB debugging enabled? Is there a way to try to flash the stock through fastboot (as zip) instead of ftf?
My big concern is loosing TA partition and associated DRM keys (any way to back it up from fastboot or toolkit?). Or is that not a factor with the hack available now? Sorry for all these questions, just getting more and more frustrated with this.
Click to expand...
Click to collapse
Come to think of it without getting into the phone to enable unlocking the bootloader I don't think you would even be able to do that. Even if the drivers weren't installed the phone should go into flash mode. I had a hard time with my first attempt with flash tool at getting into flash mode. If you hold power and volume up you should be able to power down the phone completely then hold volume up while plugging in. The problem I had was my PC has a few different USB ports and I was using one that was meant for charging and it wouldn't go into flash mode, tried a different port and it went well after that.
Failed: remote command not allowed ???
This error is because you have not enabled OEM Unlocking from the Developer Option.
If you have enabled it but still receiving the error then you have not unlocked bootloader properly.
There is no need to unlock bootloader for flashing official sony firmwares. It is pretty simple. If you are facing any problems then please feel free to message me.
my email : [email protected]
#coolmen777
Looks like this phone got the dreaded sleep of death bug (won't turn on at all, no matter which combination of buttons I press). Had it on the charger for last 3 days (no led indicators at all and no vibrations), so I got a brick now. Any ideas? This phone should still be under warranty (manufactored week 9 of 2016), but Sony USA refuses to service International phones in their facility. Learned that based on IMEI, this is a Hong Kong version and they want an invoice from authorized dealer for warranty work. Are there are other countries that honor warranty without checking invoice (go by date of manufactoring?) I had Moto and LG repaired before just based on age of phone, no invoice needed. This is my last resort option (to attempt sending in for service).
coolmen777 said:
Looks like this phone got the dreaded sleep of death bug (won't turn on at all, no matter which combination of buttons I press). Had it on the charger for last 3 days (no led indicators at all and no vibrations), so I got a brick now. Any ideas? This phone should still be under warranty (manufactored week 9 of 2016), but Sony USA refuses to service International phones in their facility. Learned that based on IMEI, this is a Hong Kong version and they want an invoice from authorized dealer for warranty work. Are there are other countries that honor warranty without checking invoice (go by date of manufactoring?) I had Moto and LG repaired before just based on age of phone, no invoice needed. This is my last resort option (to attempt sending in for service).
Click to expand...
Click to collapse
search on here for a thread about flashing the wrong ftf onto the phone, I think op used a tablet ftf and had teh same results and had to send to sony
edit:
http://forum.xda-developers.com/z5-compact/help/flashed-wrong-mm-rom-phone-dead-help-t3330929
civicsr2cool said:
search on here for a thread about flashing the wrong ftf onto the phone, I think op used a tablet ftf and had teh same results and had to send to sony
edit:
http://forum.xda-developers.com/z5-compact/help/flashed-wrong-mm-rom-phone-dead-help-t3330929
Click to expand...
Click to collapse
Thanks, not very encouraging given the fact that Sony USA supposedly doesn't currently have a service center to repair international phones (closed their TX center). Are there other countries (Canada or UK) which have less stringent policies of needing invoice (for proof of purchase) and can simply go off of manufacture date from the IMEI or device info? Thanks again.
Hi Folks
I just bought my girlfriend a Redmi Note 3 SE (Kate) quick back story, she received it turned it on added a pin to it got called away, when she got back to it she couldn't remember the pin, bad news is she hadn't yet turned on Developer Mode or USB Debugging.
Original SW - MIUI 7.5 android 6.0.1, at least that's what the Ali product page says (Sorry it seems I can't post a link to the actual product)
This began last Friday, since then she has tried the following:-
Installed MI Suite and registered a gmail account - so far "device not recognised"
Applied for an Unlock code.
Unlocked the boot loader which seems to have been successful.
Flashed two different (stock) ROM's which completed successfully but both stuck while booting the phone.
One was:-
"kate_global_images_6.12.29_20161228.0000.00_6.0_global" not sure what the other was.
On trying a different ROM today she's now getting the following error:-
"Can't Flash in miflash. Not enough storage is available to process this command"
Tried different versions of the Flash tool including the Beta version but still getting the same error on each of them.
Ticked the "Clear Data" box in the Mi Flash tool but that doesn't help.
A bit stuck on what to try from here and any help would be greatly appreciated if you need any more info please let me know.
I had the same bootloop problem with the stock firmware and miflash and driver was a pain to get sorted out.
What versions of miflash have you tried and which firmware did you download from xiaomi?
theoneofgod said:
I had the same bootloop problem with the stock firmware and miflash and driver was a pain to get sorted out.
What versions of miflash have you tried and which firmware did you download from xiaomi?
Click to expand...
Click to collapse
Hi thanks for the reply, unfortunately I need to wait for an answer on that as she's not around at the moment, but from what I can gather she has tried miuiflash 1, 2 and beta and i know she tried this which I'm assuming is a firmware - kate_global_images_6.12.29_20161228.0000.00_6.0_global (if it's not please let me know what we should be using) *edit, mind you that's one of the files that got stuck showing the out of space error.
I also forgot to mention the PC is a win 10 64bit..
Soon as I can get you a better answer on the above I'll post it.
I would have them try this version http://bigota.d.miui.com/V8.1.1.0.M...DI_20161202.0000.00_6.0_global_ac46ea44bd.tgz it's the latest fastboot ROM.
Make sure when you install miflash you are running in test mode so the drivers install properly and accept any prompts about driver signatures. That is important. I believe MiFLash_v20160401 worked for me. Also you know when you're in EDL when the front LED flashes red now and then.
theoneofgod said:
I would have them try this version http://bigota.d.miui.com/V8.1.1.0.M...DI_20161202.0000.00_6.0_global_ac46ea44bd.tgz it's the latest fastboot ROM.
Make sure when you install miflash you are running in test mode so the drivers install properly and accept any prompts about driver signatures. That is important. I believe MiFLash_v20160401 worked for me. Also you know when you're in EDL when the front LED flashes red now and then.
Click to expand...
Click to collapse
Ah so it wasn't a firmware, alright I've passed this on as soon as I hear back I'll post here, many thanks.
I just checked the link for the 8.1.1.0 Firmware but it gives a 404 error on the page, I'll look on their site for an alternative, but if you do know of an alternative please let me know.
**edit Never mind a right click and copy link location got it.
So the issue looks to be solved, so firstly many thanks "theoneofgod" for your input.
Unfortunately due to a rather dodgy internet connection I haven't managed to get further into it, but here is what I received:-
"I used the same Kate and used miflash beta version.. i did the same as i did on first attempt.. after succesfully flashing it, i turned it on (result:same stuck on booting)
i switch it back to fastboot mode.
flash it.
result error.
i then press power on for about 5 seconds or till the mi logo appeared.
unplugged the USB cable and plugged it in again.
then phone booted.
and
When miflash beta version recognized my phone as just a device not com port. i flashed it. (it was just flashing endlessly)
So i tried to refresh the page, it then showed my device with an id as com10 (I have a feeling this might be the important part)
i flashed that too, and then it worked didn't get that error " no storage" anymore.
I'm not sure though if that helped
Basically I'm saying that i was flashing 1 device with two different id.
So I'm thinking simply the device refresh actually did the trick, anyway it looks to be solved, that was 3 days of no fun, and that whole thing about hey submit an application for a bootloader unlock and then wait 2 or 3 weeks and we might even refuse it lol.
Thanks again for your help "theoneofgod" thanks meter pressed.
Steps:
1. Turn Off Any Virus Protection Software
2. Download MP26010j_00_0316.kdz To Flash Your Phone Back To Stock
3. Install LGMobileDriver_WHQL_Ver_4.2.0.exe
4. Next Install LGUP_Store_Frame_Ver_1_14_3.msi
5. Make Sure That You Have Your Phone Connected (Take Battery Out Then Put It Back In Hold Volume Up And Connect With Micro USB) So LGUP Can Be Able To Recognize It
6. Then Double Click UPPERCUT.exe to open up LGUP Now But Only Thing Is That Uppercut will try to verify just ignore and if it doesn't open up just open lgup from desktop and its going to view phone as unknown
7. Unplug Phone But Keep LG Download Mode On And Exit LGUP
8. Open LGUP First And Then Connect Phone Which Should Recognize Phone As MP260
9. Click Upgrade, Make Sure That Bin Is Checked And Select File MP26010j_00_0316.kdz To Flash And Click Start
10. Your Done! Video Coming Soon
Links: https://mega.nz/#!EZcURRSD!NF_5MU4dJUpTknRcPMQWFVoYo4ePsGkoA0ndkkzVsmI https://mega.nz/#!dFNWFZZa!Rl3P7tJs7J51TtjcnaLwR3RHgGdRSco8NcJ9yog86J0 https://mega.nz/#!oVNSnYTB!3y9-P4t_8P-lj5sCXhFjO0R8J3j4Z_US-XCjVGysgEI https://mega.nz/#!pAUgGAwC!j5d3C8pUdQR5XMpqWBgLDu2O3tE99yWNa2nwXud3OSo
The Only Thing Im Disappointed Is That Every Time You Reboot Phone or Turn It On It Keeps Saying Lock Bootloader But Just Press The Power Button To Continue Repeating The Process Does Not Remove That Message
I Made This Tutorial For Some People That Have Trouble With Apps That Detect Root
Phone dont turn on at all
yesterday i rooted my k20 mp260 then this morning i wanted to revert back to stock and no root, i tried to unroot it but i didnt follow this cause i didnt find it til now,but i got rid of root and then i tried to update via ota and it went into twrp and then it was installing until it just went black, like it shut off now it doesnt power on. when i plug it in to pc it finds it but it cant install the driver. any help to try to Resurrect from the grave would be great
Just a Heads up there is a new version out, as of 9/01/17
MP26010r_00_0817.kdz
download link
https://lg-firmwares.com/lg-mp260-firmwares/
fyi u can get rid of the bootloader bootup annoyance by following the unlock bootloader instructions but instead of typing fastboot oem unlock type fastboot oem lock
shaneg79 said:
fyi u can get rid of the bootloader bootup annoyance by following the unlock bootloader instructions but instead of typing fastboot oem unlock type fastboot oem lock
Click to expand...
Click to collapse
If you lock the bootloader if you have custom recovery (twrp) and superuser you will not be able to boot
New Optimus said:
If you lock the bootloader if you have custom recovery (twrp) and superuser you will not be able to boot
Click to expand...
Click to collapse
Correct but this thread was about removing root
shaneg79 said:
Correct but this thread was about removing root
Click to expand...
Click to collapse
ah, I thought that was in the original post or implied if completely unrooting.
New Optimus said:
Just a Heads up there is a new version out, as of 9/01/17
MP26010r_00_0817.kdz
download link
https://lg-firmwares.com/lg-mp260-firmwares/
Click to expand...
Click to collapse
Any link for the T-mobile variant?
I looked all over and reached the end of internet but couldn't find , lol!
meazz1 said:
Any link for the T-mobile variant?
I looked all over and reached the end of internet but couldn't find , lol!
Click to expand...
Click to collapse
Here
kc6wke said:
Here
Click to expand...
Click to collapse
Thanks
meazz1 said:
Thanks
Click to expand...
Click to collapse
Looked and saw two links for the newest kdz. I'm in the USA so TMO =north america.
But I 'm curios what TMI stands for, no info on that page of region listings.
meazz1 said:
Looked and saw two links for the newest kdz. I'm in the USA so TMO =north america.
But I 'm curios what TMI stands for, no info on that page of region listings.
Click to expand...
Click to collapse
Not sure about TMI, use TMO North America
I figured I'd post this here to, because I am thinking about getting this phone. It's $99 at metro pcs right now, that's really hard to pass up.
In a twrp+root thread there are some that cannot get root, with the last LG firmware update, so I'm guessing this is a soft brick as apposed to a hard brick.
So, had a question.
If in the case of the like 10% of the people that do this root, the phone won't root or bricks, if I get this phone and and that happens, is it possible to flash the phone via the LG program, with a KDZ file and go back to stock like in this thread? If so I will probably buy this phone tomorrow (crosses fingers the kdz trick will work)
From looking at the videos, it looks as if the LG program is similar to the Samsung Odin program as far as flashing goes, am I correct in this?
...
Sent from my [device_name] using XDA-Developers Legacy app
I know this thread has not been active for a while. However I have a Metro LG K20 Plus phone and want to change the firmware to T-Mobile. I have not been successful doing this as I always get invalid firmware, because LG UP recognizes the phone as a metro phone. Is there a way to succeed in getting the T-Mobile firmware on the phone?
thanks in advance.
Stoner101 said:
yesterday i rooted my k20 mp260 then this morning i wanted to revert back to stock and no root, i tried to unroot it but i didnt follow this cause i didnt find it til now,but i got rid of root and then i tried to update via ota and it went into twrp and then it was installing until it just went black, like it shut off now it doesnt power on. when i plug it in to pc it finds it but it cant install the driver. any help to try to Resurrect from the grave would be great
Click to expand...
Click to collapse
Did you find any answers to this? I have one that is bricked. It will not show up when connected to a computer at all
Virus warning from Avira in Uppercut
lg k20 plus soft bricked?
So I've searched high and low and have tried suggestion after suggestion with no avail. To start things off, I have a soft bricked LG k20 plus. Everything was working fine until the other day when I went to flash a kernel, and when the phone restarted, the screen was a dark grey/black color. I rooted the devices using massis method, removed SU and then rooted using Magisk. Like I said everything was working fine and for whatever reason I decided to try a different kernel. That's when it all went downhill. So now when I turn the phone on, the screen is still blank but it vibrates. When I've connected it to a computer, on my Mac it doesn't show up with ADB or FASTBOOT but in my device tree it comes up as LGE Android device. I borrowed my friends laptop since it runs windows, and my Mac is a dinosaur. ADB doesn't pick it up either, but in a USB hub it says the same thing, LGE Android device and lower down it comes up as TP-LINK. Now tryin to use LG Flash tools doesn't work, LGUP doesn't see my device, and when I tried to extract the KZD file, when I go to select it from the list there is no file to choose. Since I can't see anything on my screen, I can't tell if I'm in download mode, bootloader, etc, but in my device tree sometimes my phone will pop up an bootloader interface and I can use fastboot commands. When I was last able to see my screen, yes, USB debugging was on, I had a recovery, but since I can't see anything on my screen I can't seem to boot into recovery. If I could I would wipe cache and all. I think I may have read too many article and suggestions as to what to do because nothing seems to be working, and don't seem to find anything else related closely enough to my issue. Anyone have a clue as to where I should start? I'll have to give my friend back her laptop soon, and since my mac is so old, and the whole PC vs Mac feud, my computer won't be of much help. Any advice my hair strands would greatly appreciate before they rest are pulled out lol
Hello Awesome People!
I've read and I've tried a lot to unbrick my Xiaomi Redmi Note 4 on Snapdragon 625.
What happened?
After software actualization my phone stuck on Mi logo for 36+hours.
What has been tried?
I manually unblocked bootloader and I tried several ROMs. Every time I had this error in MiFlash critical partition flashing is not allowed or partition flashing is not allowed. I tried to edit in TextEditor some files but with no success after all.
1. One thing I didn't do was disabling driver signature enforcements in windows. What is this needed for?
2. Is this kind of malfunction can be reported during warranty period? Who is responsible for making my phone unusable?
3. Which ROM would you recommend to stick with during my following flashing tryouts?
4. I am going to check all the USB cables. Might it help when I've got the "critical partition flashing is not allowed" error?
5. What causes this "critical partition flashing is not allowed" error?
6. I've got no deep flash cable and I'm at the end of the world, so it's very difficult to get one of these here. Should I start trying to get one anyway? Someone had the same issue and could resolve it this way?
7. What to do now guys? Any ideas? -> For now I'll be checking all the usb cables I can get my hands on.
I know that some of the answers can overlap, but I chose the questions intentionally. I've been researching and checking solutions for over a week now. I would like to have deeper understanding of what the heck is going on with my phone and its software. There are no service centers here which can help me (their workers have less knowledge than I have, a sad lol), so I am dependent on your knowledge and your good will.
Best Regards
PatchMe said:
Hello Awesome People!
I've read and I've tried a lot to unbrick my Xiaomi Redmi Note 4 on Snapdragon 625.
What happened?
After software actualization my phone stuck on Mi logo for 36+hours.
What has been tried?
I manually unblocked bootloader and I tried several ROMs. Every time I had this error in MiFlash critical partition flashing is not allowed or partition flashing is not allowed. I tried to edit in TextEditor some files but with no success after all.
1. One thing I didn't do was disabling driver signature enforcements in windows. What is this needed for?
2. Is this kind of malfunction can be reported during warranty period? Who is responsible for making my phone unusable?
3. Which ROM would you recommend to stick with during my following flashing tryouts?
4. I am going to check all the USB cables. Might it help when I've got the "critical partition flashing is not allowed" error?
5. What causes this "critical partition flashing is not allowed" error?
6. I've got no deep flash cable and I'm at the end of the world, so it's very difficult to get one of these here. Should I start trying to get one anyway? Someone had the same issue and could resolve it this way?
7. What to do now guys? Any ideas? -> For now I'll be checking all the usb cables I can get my hands on.
I know that some of the answers can overlap, but I chose the questions intentionally. I've been researching and checking solutions for over a week now. I would like to have deeper understanding of what the heck is going on with my phone and its software. There are no service centers here which can help me (their workers have less knowledge than I have, a sad lol), so I am dependent on your knowledge and your good will.
Best Regards
Click to expand...
Click to collapse
What do you mean my manually unlocked the bootloader? Did you perform steps other than those in official guide?
1. Driver verification has to be disabled because mi flash has to install some drivers for mido.
2. Warranty isn't going to be valid here somehow.
3. Miui. Latest miui 9.5 fastboot rom.
4. Up and until your device is being recognised you don't need to change usb cable.
5. Probably driver verification?
6. No. It isn't required as of now.
7. For now perform disabling driver verification and try again.
MyNameIsRage said:
What do you mean my manually unlocked the bootloader? Did you perform steps other than those in official guide?
1. Driver verification has to be disabled because mi flash has to install some drivers for mido.
2. Warranty isn't going to be valid here somehow.
3. Miui. Latest miui 9.5 fastboot rom.
4. Up and until your device is being recognised you don't need to change usb cable.
5. Probably driver verification?
6. No. It isn't required as of now.
7. For now perform disabling driver verification and try again.
Click to expand...
Click to collapse
Thanks for advice!
Sorry for late reply. Lack of laptop, time and internet connection is a harsh hybrid
I've disabled driver verification and went on to minimal adb and fastboot. Command "adb devices" doesn't show any devices. And "adb reboot boatloader" gives error: no devices/emulaters found.
I've tried it on 3 different laptops including one with iOS. When I plug in my Redmi Note 4 SD every laptop beeps and only MiFlash detects a device. Tried out 4 different USB cables and 3 of 4 detected my Note 4.
Check the screenshots:
dropbox.com/s/u7xoewalgho9kh5/adb%20reboot%20boatloader.png?dl=0
dropbox.com/s/a782soi5aub2puf/ios%20device%20oem%20locked.png?dl=0
Sorry for cutting the link but couldn't post whole.
What do you mean my manually unlocked the bootloader? Did you perform steps other than those in official guide?
Click to expand...
Click to collapse
I tried the TEST POINT approach.
en.miui.com/thread-729246-1-1.html
What do you think MyNameIsRage?
Cheers
Hello all,
Anyone having the same problem was able to overcome it?
I'm still wishing to unblock my phone. Will the deep flash cable be of any help in this case?
Cheers!
PatchMe said:
Thanks for advice!
Sorry for late reply. Lack of laptop, time and internet connection is a harsh hybrid
I've disabled driver verification and went on to minimal adb and fastboot. Command "adb devices" doesn't show any devices. And "adb reboot boatloader" gives error: no devices/emulaters found.
I've tried it on 3 different laptops including one with iOS. When I plug in my Redmi Note 4 SD every laptop beeps and only MiFlash detects a device. Tried out 4 different USB cables and 3 of 4 detected my Note 4.
Check the screenshots:
dropbox.com/s/u7xoewalgho9kh5/adb%20reboot%20boatloader.png?dl=0
dropbox.com/s/a782soi5aub2puf/ios%20device%20oem%20locked.png?dl=0
Sorry for cutting the link but couldn't post whole.
I tried the TEST POINT approach.
en.miui.com/thread-729246-1-1.html
What do you think MyNameIsRage?
Cheers
Click to expand...
Click to collapse
Sorry for replying late. I see what you did there, and to be honest that wasn't really the correct steps.
First of all, in order to flash the rom, you should try to make sure that fastboot works. Boot into fastboot and check if device shows up. To do that execute
"fastboot devices" and if it returns some data then you are good to go for flashing fastboot rom. We'll go step wise. Try performing fastboot check and report if it works. Also if you have telegram you can contact me at @MyNameIsRage
MyNameIsRage said:
First of all, in order to flash the rom, you should try to make sure that fastboot works. Boot into fastboot and check if device shows up. To do that execute
"fastboot devices" and if it returns some data then you are good to go for flashing fastboot rom. We'll go step wise. Try performing fastboot check and report if it works. Also if you have telegram you can contact me at @MyNameIsRage
Click to expand...
Click to collapse
Ok, thanks!
I did "fast boot devices" and it shows the device.
dropbox.com/s/9qqpjdev31ssuw3/Zrzut%20ekranu%202018-09-29%20o%2014.40.00.png?dl=0
but still adb devices doesn't give any numbers back and flashing is impossible.
What now?
PatchMe said:
Ok, thanks!
I did "fast boot devices" and it shows the device.
dropbox.com/s/9qqpjdev31ssuw3/Zrzut%20ekranu%202018-09-29%20o%2014.40.00.png?dl=0
but still adb devices doesn't give any numbers back and flashing is impossible.
What now?
Click to expand...
Click to collapse
Now you should try mi flash. And possibly on a windows machine.
http://en.miui.com/thread-565784-1-1.html
MyNameIsRage said:
Now you should try mi flash. And possibly on a windows machine.
http://en.miui.com/thread-565784-1-1.html
Click to expand...
Click to collapse
My phone is in a bootloop. Can't do this.
2. Enable Developer options:- Go to About phone > tap MIUI version at least 7 times to activate the Developer options.
and neither installing VPN.
PatchMe said:
My phone is in a bootloop. Can't do this.
2. Enable Developer options:- Go to About phone > tap MIUI version at least 7 times to activate the Developer options.
and neither installing VPN.
Click to expand...
Click to collapse
Skip that part. Try as it is. Mi flash should detect your device. Jump straight to the part of flashing.
MyNameIsRage said:
Skip that part. Try as it is. Mi flash should detect your device. Jump straight to the part of flashing.
Click to expand...
Click to collapse
I did it on Mac (lack of windows laptop atm) and it said again "device oem locked". As in the screenshot I uploaded before.
PatchMe said:
I did it on Mac (lack of windows laptop atm) and it said again "device oem locked". As in the screenshot I uploaded before.
Click to expand...
Click to collapse
afaik mac won't work. You'll need a windows machine and mi flash tool.
MyNameIsRage said:
afaik mac won't work. You'll need a windows machine and mi flash tool.
Click to expand...
Click to collapse
Ok
Will do that in the next 24h and will report back.
Tried it all!
I tried to unlock boot loader via MiUnlock. Failed to "couldn't verify device" - unknown error (-1)
Same problem with trying to install ROM on windows as on MacBook.
I positively performed PIN TEST but couldn't install ROM. I am struggling with putting the device into fast boot mode after positively connecting it to windows pc with PIN TEST.
Any suggestions?
PS. I've sent info to xiaomi support as well.
Finally done it!
Hey guys!
I'm glad to tell you that after million tries with different ROMs and different approaches to PIN forcing i was able to reinstall my ROM. The working ROM for me was mido_global_images_V9.6.2.0.NCFMIFD_20180716.0000.00_7.0_global_228dc638d1
THANK YOU so much for help. You kept me going and finally i was able to overcome the obstacle
I hope I can be of help when you need it.
Take care,
Cheers
Edit: PS. I've done it on Mac
I'm stuck on waiting for all devices in adb.. My phone screen has a menu with three choices, one of them is flash unlock.bin. Should I keep waiting for all devices for how long in adb?
What procedure are you using to unlock? The WTF process is the one that I believe has worked the best for most people... and that doesn't have anything special on the phone screen, so I'm thinking you're using some app or script?
dsk1000 said:
I'm stuck on waiting for all devices in adb.. My phone screen has a menu with three choices, one of them is flash unlock.bin. Should I keep waiting for all devices for how long in adb?
Click to expand...
Click to collapse
Yea, I'm following that one. I read somewhere about AMD PCs causing problems. My phone shows when I use adb devices. So should I be a little more patient or what?
No, the processes are quick. AMD Ryzens typically have issues, but it's only because of the USB driver they use. I've heard a few Intels have issues sometimes as well.
The key is, you just need to try other computers... this is the "hardest" thing to do, but it's really the only solution to that issue. The process takes under a second, so it's not a patience issue.
For the record, my older laptop with an AMD A9 CPU did the process fine... so, again, it's not a CPU issue, but a driver issue for the USB, apparently...
schwinn8 said:
No, the processes are quick. AMD Ryzens typically have issues, but it's only because of the USB driver they use. I've heard a few Intels have issues sometimes as well.
The key is, you just need to try other computers... this is the "hardest" thing to do, but it's really the only solution to that issue. The process takes under a second, so it's not a patience issue.
For the record, my older laptop with an AMD A9 CPU did the process fine... so, again, it's not a CPU issue, but a driver issue for the USB, apparently...
Click to expand...
Click to collapse
Thanks for the reply..I'm super new to adb..but I am following wtf instructions. I will keep researching..and asking questions. Thanks. PS I haven't rooted anything since my lg g3..
dsk1000 said:
Thanks for the reply..I'm super new to adb..but I am following wtf instructions. I will keep researching..and asking questions. Thanks. PS I haven't rooted anything since my lg g3..
Click to expand...
Click to collapse
Some people had to use 2 or 3 computers. An older one with Intel CPU works best (especially if it has USB 2.0), but yes an AMD can work. As noted by @schwinn8 Ryzens are no go. One guy was upset because he had superfast gaming computer and we kept telling him to try another computer. He borrowed his brother's mediocre laptop and BOOM, worked. Another guy dug some old laptop out of his closet and it worked.
Thanks for the reply...i was just reading about adb making sure it wasn't something i was doing wrong. Even tried on an old iMac that i had installed linux on. "Waiting for device..." So..still reading and learning to be patient. Thank you
dsk1000 said:
Thanks for the reply...i was just reading about adb making sure it wasn't something i was doing wrong. Even tried on an old iMac that i had installed linux on. "Waiting for device..." So..still reading and learning to be patient. Thank you
Click to expand...
Click to collapse
Also, try the steps mentioned in Wtf troubleshooting section.
Other than that you may have to mess around in the device manager section to see if the phone is detected properly or not.
(if there's a problem with the driver the device will show up as unknown android device or something)
dsk1000 said:
Thanks for the reply...i was just reading about adb making sure it wasn't something i was doing wrong. Even tried on an old iMac that i had installed linux on. "Waiting for device..." So..still reading and learning to be patient. Thank you
Click to expand...
Click to collapse
You said "patient"... just to reiterate, this process doesn't take longer on a computer that says "waiting for device". It's a fast process, so if it's not happening within a few seconds, it won't work on that setup, period. Don't waste your time waiting - get another machine/cable/etc (check the troubleshooting steps to find other possible issues... the computer is usually the biggest problem to overcome, but the most successful).
Good news, i unlocked my phone and installed twrp, then i had to stop the process (wtf)
i still need to make a backup in TWRP and flash two more files from wtf notes. I cannot seem to be able to reboot into TWRP from ADB. thanks in advance
The oem is greyed out in developer mode and says its unlocked. Idk?
Glad to hear you got it unlocked.
In the WTF post it says that the developer mode may remain grayed out after being flipped... this is normal. It comes back after some time. Of course, you don't want to toggle it again anyway, since you're unlocked...
When i go to use an app to boot into twrp..it tells me its not rooted.
dsk1000 said:
When i go to use an app to boot into twrp..it tells me its not rooted.
Click to expand...
Click to collapse
Used getvar..unlocked.
Well its done..used an old hp A6 with linuxmint. I found linux to be straightforward and easy when trying to root my phone. No jumping thru hoops and juggling stuff.
Any recommendations for remodeling the phone? Boot to twrp..roms..ect?
dsk1000 said:
When i go to use an app to boot into twrp..it tells me its not rooted.
Click to expand...
Click to collapse
Bootloader unlocked is not rooted. It's just the prerequisite to being rooted. Then you install TWRP custom recovery and then use that to flash Magisk. It's all in the WTF Instructions. Also be sure to use the version of Magisk in the WTF Instructions, at least initially.
Thanks..ive got magisk from the instructions. It wants to update..should?
Once you are booted into Android, you can update Magisk to some degree. I forget the last version I had but I recall I could go to 20.x or something without issue. But there is always a risk of having issues if you update to the latest version... so be prepared to go back to the one on the WTF thread if the phone has issues. In other words, don't do this last minute or without a PC to work from... because it could fail.
The only time you have to use the old Magisk is during that first boot with it... once you're booted through, you have been able to update to newer versions. But unless you need some specific feature of the newest version, I might suggest leaving it alone...
I read somewhere..when i upgrade on US 998 20b, i need to move up to 20c?
Also, do i use the "twrp version. 20c"?