I got problem by my Xiaomi Redmi Note 6 Pro (4/64GB). Problem with wifi and TWRP.
I saw on other pages, that On Android Pie, there can be problem with TWRP, but I am unsure if this is the same... Cause I am experiencing two problems, both of them are seriou from my point of view and using this phone.
Wifi doesn't want to start. Actually it was working for some time, about 1 or 2 hours. But after all updates has been done and it doesn't want to start. (it disconnect me automatically). When I want to turn it on it is impossible. I tried to install different version of MIUI, but it didn't help. Before I had installed MIUI Polska 10 and now I got Xiaomi.eu official ROM. Still the same problem. Now I have installed version MIUI global 10.3.3 stable version (PEKMIXM)
Besides I am unable to to anything in TWRP. It was working during instalation, but now I cannot SWIPE I tried different version of it, but none of it works
Don't know, how to solve this problem.
I got installed TWRP in version of TWRP 3.2.3.0, but I have installed almost of version, which I found at different pages, and at all there was the same problem... At bottom TWRP screen I got below some kind of hashes of something. I can see whole screen, but at the bottom I got 1,5cm stripe with different lines.
I don't know, if those 2 problems are connected somehow, but as I wrote above, I tried different versions of TWRP and MIUI and I am still experiencing the smae problems...
Any advice? Or maybe do you want some more output from my phone?
Related
Bare with me, I'm a total noob and I hold my hands up, I got a galaxy note 8.0, rooted it fine then I went to install CM 13 for it following partially instructions partially my own knowledge and now it's muffed. No matter how many times I tried it wouldn't work and I was messing around with it all night last night and all day today and in my infinat wisdom I removed all OS from it full stop. I have been sat here for 6 hours trying to put cm on it (tried 11, 12 and 13) tried installing stock marshmallow I downloaded from some site, and even some other ROM I can't remember off the top of my head (the logo is a horse's head or something) and yep nothing what so ever i have tried several different boot thingies like twrp and it always fails when I try to install the ROM, I know I should have backed up and I thought I had using titaniumbackup but that went with the OS. It's currently got twrp on it and I can get into that and connect it Odin (I think that's what it's called) but that's all I can do. Is it fixable or is it scrap? >.<
Update, after putting it down and thinking about it from another perspective I worked out a fix, it's back running 4.4.2 and works fine (on my note I will say the latest update of the Google app causes a problem with the system UI if you have Google now as your launcher) I'll update with full details in the morning in hopes that if anyone else has a similar problem this will help.
QuesteU said:
Bare with me, I'm a total noob and I hold my hands up, I got a galaxy note 8.0, rooted it fine then I went to install CM 13 for it following partially instructions partially my own knowledge and now it's muffed. No matter how many times I tried it wouldn't work and I was messing around with it all night last night and all day today and in my infinat wisdom I removed all OS from it full stop. I have been sat here for 6 hours trying to put cm on it (tried 11, 12 and 13) tried installing stock marshmallow I downloaded from some site, and even some other ROM I can't remember off the top of my head (the logo is a horse's head or something) and yep nothing what so ever i have tried several different boot thingies like twrp and it always fails when I try to install the ROM, I know I should have backed up and I thought I had using titaniumbackup but that went with the OS. It's currently got twrp on it and I can get into that and connect it Odin (I think that's what it's called) but that's all I can do. Is it fixable or is it scrap? >.<
Update, after putting it down and thinking about it from another perspective I worked out a fix, it's back running 4.4.2 and works fine (on my note I will say the latest update of the Google app causes a problem with the system UI if you have Google now as your launcher) I'll update with full details in the morning in hopes that if anyone else has a similar problem this will help.
Click to expand...
Click to collapse
Greetings and welcome to assist. Have you tried any of the CM based roms from xda ? You may only need to update your recovery. Both of these should work on your device
https://forum.xda-developers.com/ga...0-1r61-rom-resurrection-remix-v5-7-3-t3449444
https://forum.xda-developers.com/ga...m-unofficial-lineageos-14-1-gt-n51xx-t3533329
Latest twrp
https://forum.xda-developers.com/galaxy-note-8-0/development/recovery-twrp-2-8-5-0-t3035004
Good Luck
Sawdoctor
Hello everybody, about 6 hours ago I attempted to flash my first ROM and I believe I am experiencing a bootloop or something similar.
The device (alcatel idol 3 5.5) starts to boot up but never finished booting
the ROM I installed is BlissPop (not exactly sure which version but I believe it is the latest one) but If i remember correctly the build is "unofficial" so I am not exactly surprised I am experiencing this.
Is there a way to fix this, and if so, how? At the moment I only have access to a quite outdated mac machine and I already tried sideloading a different ROM but I get a strange error that my adb's version is too old (it requires something above 1.0 while mine is something above 3.0). I've tried using a few different download locations for it but they all seem to do the same.
I have also done a TWRP backup before flashing but I have no idea how to recover it since I cannot "boot"/flash the TWRP recovery program without adb
Any help or idea how to solve this would be greatly appreciated
Does anyone know what changed regarding wifi in Android 8 or MIUI 10?
I was happily using LOS 14 for a while (after having officially unlocked my bootloader at some point in the past, but became curios and wanted to try out the new MIUI 10. While I could not find anything official, I did find this chinese dev ROM (I DO NOT RECOMMEND YOU FLASH THIS). I flashed it, wasn't that impressed and then decided to try LOS 15 based on Android 8.
That was a bit too unstable for me, so I tried reverting back to LOS 14.
I did so using a backup I made to my pc (I did `adb backup` while in TWRP and selected every partition I think). After booting into LOS14, things seemed to crash an awful lot.
At this point I realized wifi wasn't working. It showed a MAC Address of 02:00:00 I think, but no networks were found. I tried restoring my phone using MiFlash normally. I then tried restoring it using Qualcomm's download mode. Older MIUI versions would not boot anymore (although I did manage to boot an old version of TWRP made for the pre-Nougat bootloader). I tried LOS14 again, and attempted using fastboot to erase various partitions (such as the bluetooth and modem partition, and then manually flashed the image again. Still no wifi.
Does anyone know what could have happened? My bootloader is still unlocked, and even downgrading the device to an old version of MIUI using Qualcomm mode did not make it work again? How come LOS15 and MIUI 10 are able to use wifi without problems?
tl;dr WiFi stopped working on any rom other then Lineage OS 15 or MIUI 10.
Hello,
since today I flashed definitly more than 100 times a custom rom to several Smartphones. So I know the procedure und what to note.
But now the Redmi Note 6 Pro makes me crazy since two days.
Waited 15 days to unlock bootloader, then flashed the first TWRP, Error 7, tried another TWRP for the phone from here - passwort error encryption etc. etc. I think I have seen all the possible error-messages.
I tried everything incl. back to stock rom via Xiaomi Mi flash several time an than the same from the beginning, always errors, some new like "zip-file corrupt" "can't map file". Thought about a hardware error already.
Has anybody been in the same situation? What should I try? Is there a workaround where I can check the reason for these problems?
Regards
Robert
robert_b said:
Hello,
since today I flashed definitly more than 100 times a custom rom to several Smartphones. So I know the procedure und what to note.
But now the Redmi Note 6 Pro makes me crazy since two days.
Waited 15 days to unlock bootloader, then flashed the first TWRP, Error 7, tried another TWRP for the phone from here - passwort error encryption etc. etc. I think I have seen all the possible error-messages.
I tried everything incl. back to stock rom via Xiaomi Mi flash several time an than the same from the beginning, always errors, some new like "zip-file corrupt" "can't map file". Thought about a hardware error already.
Has anybody been in the same situation? What should I try? Is there a workaround where I can check the reason for these problems?
Regards
Robert
Click to expand...
Click to collapse
Same problem here ? I can't solve ? plz help
Never fear, Google is here!
I had this exact same problem, but this post fixed it:
https://forum.xda-developers.com/showthread.php?t=2522762
I still haven't figured out what caused it in the first place though...
I don't think this programming-issue is the only reason for error 7. I have been trying 5 different roms, always error 7. Is it possible that there comes a wrong model-information from the phone?
Another problem is the passwort for decrypting in TWRP. In some threads is said, this password is the screen protecting password. I tried this - nothing - I changed it - nothing, allways wrong password.
This phone makes me crazy.... All the things working allways and xtimes without any problems - here not.
Same Problem
Had the same problem turned out that you need to flash pie firmware first befor flashing any pie-roms.
See the post here: https://forum.xda-developers.com/showpost.php?p=79136824&postcount=2
This was the solution
matthewultraboy said:
Had the same problem turned out that you need to flash pie firmware first befor flashing any pie-roms.
See the post here: https://forum.xda-developers.com/showpost.php?p=79136824&postcount=2
Click to expand...
Click to collapse
Thank you very much. Sorry for the delay....
*SOLVED: see reply*
The ROM I used before was LineageOS [10.0] and used a custom ROM with Android 9 before that. Needed to unlock my phone, and couldn't do that on Lineage, and had troubles flashing firmware with Odin, so I ended up using FrankensteinS6. The Stock kernel seems to let me input the NCK, and unlock the phone. So that's luckily finally over.
For about 4 days now I've been formatting phone and trying again and again. FrankensteinS6 works, some other 6.0/7.0 ROMs work. But LineageOS now enters a bootloop, and Pixel Experience (9.0 and 10.0) and Evolution X 10.0 don't detect the SIM. The ones that don't detect SIM also show no IMEI, which was worrying at first because I though I lost a partition.
Possibly related, the ROM of Pixel Experience Android 10.0 for G920W8 will not install because (paraphrasing) "This device is zeroflte, this file is for zerofltecan, zeroflte***, zeroflte***" claiming that my phone isn't one of those models. I got this S6 from Bell Canada, and I still have even the sticker that says it is a G920W8, not G920F. However, the Pixel Experience ROM for G920F flashes fine (sans the main problem).
I don't know the exact LineageOS ROM I used before, but I've tried all of their 10.0 releases, tried redownloading, and I get the bootloop every time. I see some info online of flashing modem firmware, but... I don't even know where to start with that. As I mentioned at the start, Odin is crapping out. I couldn't flash firmware with it, because it would reject the phone right after I started flashing. Anything I could do within TWRP would be great. I moved it back to FrankensteinS6 for my sanity, I started doing this Sunday and I'm starting to repeat steps over and over hoping that it just solves itself.
I tried to keep this straightforward, and I'm sure I did a bad job. I can extrapolate on what I have attempted. Please tell me what I have to do to get an android 10 ROM working on this old beauty again.
I do not have all the solutions. As per my tests with my SM-G920W8. I have managed to find ROMS and try them out. I have only seen Nougat 7.0 ROMS to work almost flawlessly. NOT 7.1.2, important, 7.0 only.
I have also tested some Pie and v10 ROMS like Pixel Experience. The ROMS boot nicely but since I do not use a SIM card to call as I use SIP phone numbers and require WiFi. But that left asside, I came upon serious camera issues no matter what I try. Up to now, SamStock ROM is pretty much the best Stock ROM I found but I always need to run the Magisk UNINSTALLER before re-installing the latest Magisk version..
As for Kernels, well, Anything that is oriented with Lineage OS, I've had camera issues even with Nougat v7.0. So basically, the only ROMS I found good, as of today, for now, are stock ROMS v7.0. But, to do your tests, Even if you have a 920F ROM, you can download a 920W8 kernel as long as you download a kernel which supports your installed Android version. Also make sure to download the proper Stock or AOSP kernel (AOSP for LineageOS). There's not many but there's a few ones that work properly.
Another option is to download an AOSP ROM that works for W8 phones, unzip the file and grab the boot file inside corresponding to the W8 or T-Mobile version. You simply unzip your real ROM you want top install, replace the boot file for the one you got and rezip it. This made my phone boot properly for some F version ROMS but again, not without issues. That's why, I really suggest v7.0 Srock ROMS. I hope this helps you a bit. Again, you can have your own tests and other users may have other answers, but this is based off over 30 bootloops in my case of trying to mod a ROM for the W8 model. It's not easy to find a good one for Canada, I admit!!!
I flashed TWRP years ago, and I found out that I had a G920F version flashed. I don't know why Lineage allowed me to use SIM before, but rectifying this issue seems to made the SIM work in newer versions.
I don't know what the S6's predisposition to having crashing cameras is, but I have avoided this in the past by using custom camera apps, like Open Camera. This has saved me every time.
As for the boot loops... I think another thing that helped is that "format data" doesn't wipe the OS. When you are in recovery, having issues with bootloops in various ROMs, try advanced wipe, and wipe the system. It didn't fix right away, but the time I got Pixel Experience 10 up and running that was the trick.