Related
Installing now...
having a problem reinstalling TWRP. I followed all the commands and here is a copy of what Happens when I flash
C:\Users\Robert\Desktop\files\TWRP_for_mate2\TWRP_for_mate2>fastboot flash recovery twrp.img
target reported max download size of 804257792 bytes
sending 'recovery' (14382 KB)...
OKAY [ 0.469s]
writing 'recovery'...
OKAY [ 0.328s]
finished. total time: 0.797s
but when I try to boot into it it starts up the stock recovery. Any suggestions on how to install TWRP and make it stick or how to gain root because I mainly use TWRP for root.
I also get this screen sometimes when trying to boot into boot loader. The phone doesn't seem to vibrate like it does when it boots normally or loads recovery and boot loader.
http://imgur.com/IQlBmP1
The usb is connected but I haven't tried to send anything to the phone or told anything other than to reboot system when it boots into stock recovery. If I leave it , it just sits there doing nothing so I rebooted and it boots just fine. Should I try to reflash stock recovery and then flash TWRP?
Found a way to at least let the phone get using TWRP without apparently being able to boot into it for some reason. Don't know if you can backup and restore backups using this method but at least its a temporary workaround. I found it at this site https://aubykhan.wordpress.com/2013...t-into-twrp-or-cwm-recovery-without-flashing/. below is the guide copied from the site.
Prerequisites
•An unlocked bootloader – It is just a command away on Nexus devices. Google will give you very useful links depending on your device type.
•ADB with Fastboot – Check out this link: http://www.jailbreakeye.com/android/install-adb-fastboot
•A custom recovery image – TWRP or CWM (check the Download recovery or Download touch recovery columns)
Guide
1.Copy the downloaded recovery image (.img file) to the folder where you have placed your ADB and Fastboot.
2.Launch terminal (or command prompt on Windows).
3.Navigate to the directory where you have placed the ADB, Fastboot and .img file together.
4.Shut down your phone and reboot into boot loader. For nexus devices, simply hold volume down + power to start up the phone.
5.Connect your phone to your computer.
6.On terminal (or command prompt) window, write fastboot boot <img file name>, e.g. fastboot boot twrp.img.
7.Your phone will restart and will boot into the recovery mode.
That’s it. As simple as it can get!
Hopefully this will help out those who are having trouble getting into TWRP after updating to B321.
what new on the b321 updated
dizwikedcbr said:
what new on the b321 updated
Click to expand...
Click to collapse
It's very stable. Lots of things are now fixed. Getting 3rd party launcher to stick after reboot is now working. Actually, I have been using it as my daily driver for several days. Not even rebooted since install. This may be released to public, at least as the next preview.
Which launcher?
kimtyson said:
It's very stable. Lots of things are now fixed. Getting 3rd party launcher to stick after reboot is now working. Actually, I have been using it as my daily driver for several days. Not even rebooted since install. This may be released to public, at least as the next preview.
Click to expand...
Click to collapse
Which launcher are you using?
I installed B321 ...phone rebooted and is stuck on huawei logo screen. I can't get to fastboot or recovery. Help.
kimtyson said:
It's very stable. Lots of things are now fixed. Getting 3rd party launcher to stick after reboot is now working. Actually, I have been using it as my daily driver for several days. Not even rebooted since install. This may be released to public, at least as the next preview.
Click to expand...
Click to collapse
Nope. Still quite a few issues with notifications, led issues and issues with losing APN settings at random requiring a reboot. Sounds like you've just been lucky.
Have to consider user error. How many of those having issue are stock. Not rooted and LCD density changed etc. Not all issues are the fault of the rom. I am sure Huawei is taking that into consideration.
gale2000 said:
I installed B321 ...phone rebooted and is stuck on huawei logo screen. I can't get to fastboot or recovery. Help.
Click to expand...
Click to collapse
same happened with me. did the b321 ota and got stuck on boot screen. had to go back to b309 and now cant get back to b320.
How long did you let it run. It can take a good while on first boot...
I let it sit there so long i had forgotten about it all together. so at least 10-15 min on huawei splash screen. not the emul loading screen. i dont think a 30-40mb upgrade should take longer that it takes to load a complete image
---------- Post added at 01:17 AM ---------- Previous post was at 01:16 AM ----------
And when i search for updates now I get nothing... stuck on b309 i guess.
Moody66 said:
Have to consider user error. How many of those having issue are stock. Not rooted and LCD density changed etc. Not all issues are the fault of the rom. I am sure Huawei is taking that into consideration.
Click to expand...
Click to collapse
My phone is stock. Nothing added and no root. The issues are apparent and have been reported by other users, so the issues I have posted are NOT user error. A number of them have been confirmed as being fixed in the next release. 321 won't be the next release to the general public.
Confirmed fix in next release? Who is running the "next release"?
The b321 ota might be a good thing, but it's new enough that I am wary. I just upgraded to b320 less than a week ago and still haven't gotten everything situated on the phone. I've had some issues with Nova Prime launcher on power up. I have one question, er maybe two. What improvements if any make this new update a good choice and will I once again have to reload everything back onto my phone?
Moody66 said:
How long did you let it run. It can take a good while on first boot...
Click to expand...
Click to collapse
Overnight. If I power it off it turns itself right back on. Still stuck on splash screen...can't get to fastboot or recovery. Boo.
gale2000 said:
Overnight. If I power it off it turns itself right back on. Still stuck on splash screen...can't get to fastboot or recovery. Boo.
Click to expand...
Click to collapse
You have to put b320 or 309 update on the root of your sd card in folder named dload. do the three finger reset ( vol + vol- and PWR ) it will then install b320.
My guess is that you were still rooted when you updated, you have to be stock.
Davinci50 said:
You have to put b320 or 309 update on the root of your sd card in folder named dload. do the three finger reset ( vol + vol- and PWR ) it will then install b320.
My guess is that you were still rooted when you updated, you have to be stock.
Click to expand...
Click to collapse
Yes, I was rooted. Thanks for your help.
Harris.S.Newman said:
Which launcher are you using?
Click to expand...
Click to collapse
I am using Nova but Apex also stuck after reboot.
gale2000 said:
I installed B321 ...phone rebooted and is stuck on huawei logo screen. I can't get to fastboot or recovery. Help.
Click to expand...
Click to collapse
Sorry for your headaches. I have had no issues but I am using a clean install with no root or other magical add-ons.
TheIgster said:
Nope. Still quite a few issues with notifications, led issues and issues with losing APN settings at random requiring a reboot. Sounds like you've just been lucky.
Click to expand...
Click to collapse
You are correct about the notifications but that is an EMUI thing and they have no intentions (so far) of changing EMUI, so deal with it or get a notification add-on app. (Sorry for my bluntness.)
What LED issues?
My APN has been perfect. I am on ATT. Not sure what your APN issue might be but I'm not seeing others with APN issues.
No reboots for me and no need for reboots.
So, yeah, I'm lucky I guess. Or maybe I have a clean install without root. Or maybe I just know what I'm doing.
Moody66 said:
Confirmed fix in next release? Who is running the "next release"?
Click to expand...
Click to collapse
Confirmed on the Huawei website I've been posting on as well.
kimtyson said:
You are correct about the notifications but that is an EMUI thing and they have no intentions (so far) of changing EMUI, so deal with it or get a notification add-on app. (Sorry for my bluntness.)
What LED issues?
My APN has been perfect. I am on ATT. Not sure what your APN issue might be but I'm not seeing others with APN issues.
No reboots for me and no need for reboots.
So, yeah, I'm lucky I guess. Or maybe I have a clean install without root. Or maybe I just know what I'm doing.
Click to expand...
Click to collapse
Notifications were working fine on JB. There are issues since the update that need to be addressed. EMUI had it working just fine prior to the update to L.
There are no LED notifications for some notifications at times and I have yet to get a notification via the LED for Facebook. With and without a third party app.
The APN issues are documented and reported by other users. It is being fixed in the next release.
My install, yes, was not clean, but only an upgrade from 309. I have never had root. Yes, of course, you and Moody are experts and the rest of us are idiots. You both sure like to insinuate that in your posts. It's a little tiresome, but if it makes you feel better, I guess feel free.
EDIT: The problem is fixed, the problem was my dead SD card, as soon as I took it out and boot into TWRP the recovery has been working well. Thank you all for your help anyways.
What's going on guys, today I'm in need of some aid. Couple days ago I was trying to swap ROMs from PsyRom to FlyMeOS and when I tried to access TWRP recovery, it would get stuck on the TeamWin logo. I softbricked my phone by restoring the stock recovery and kernel (lol) and flashed the latest Fastboot ROM. Now I'm fine with MIUI8, and I flashed TRWP again (with Fastboot flash) but everytime I try to access TRWP it gives me that stuck logo or a black screen. I don't know what to do because I already tried with a rooted Dev ROM and flashify and even the TWRP Manager but I can't get anywhere. Do you know what I can do?
I've seen several TWRP versions for RN2.
Did you try with the official one?
https://dl.twrp.me/hermes/
gnazio said:
I've seen several TWRP versions for RN2.
Did you try with the official one?
https://dl.twrp.me/hermes/
Click to expand...
Click to collapse
Yes I did, and with the 2.8.7, and the other 3.0.x
Always the same result. Did Xiaomi lock the Redmi Note 2 bootloader?
kiko9895 said:
Yes I did, and with the 2.8.7, and the other 3.0.x
Always the same result. Did Xiaomi lock the Redmi Note 2 bootloader?
Click to expand...
Click to collapse
AFAIK the bootloader is not locked.
Otherwise I think that you can't even install TWRP.
I any case, I would try with an older fastboot ROM and with the official TWRP.
Have you tried this one: http://forum.xda-developers.com/redmi-note-2/general/twrp2-8-7-0-light-materialized-theme-t3308492
DarthJabba9 said:
Have you tried this one: http://forum.xda-developers.com/redmi-note-2/general/twrp2-8-7-0-light-materialized-theme-t3308492
Click to expand...
Click to collapse
Yes, it's the last one I tried, I used the one on the first link, with MIUI8 compatibility.
gnazio said:
AFAIK the bootloader is not locked.
Otherwise I think that you can't even install TWRP.
I any case, I would try with an older fastboot ROM and with the official TWRP.
Click to expand...
Click to collapse
I'm sorry but do you know where I can find an older one?
kiko9895 said:
Yes, it's the last one I tried, I used the one on the first link, with MIUI8 compatibility.
Click to expand...
Click to collapse
I am using this one: https://drive.google.com/file/d/0BwdRTuyj12_yVlJoMzJoeUJKLVE/view
I have no problem with it (MIUI8). To be honest, I don't think any of them should cause the problem that you are having. Trying to solve the problem without identifying the cause will probably prove unfruitful. How did you install the first one that you had problems with? Did it ever work at all? If so, when did it start malfunctioning?
DarthJabba9 said:
I am using this one: https://drive.google.com/file/d/0BwdRTuyj12_yVlJoMzJoeUJKLVE/view
I have no problem with it (MIUI8). To be honest, I don't think any of them should cause the problem that you are having. Trying to solve the problem without identifying the cause will probably prove unfruitful. How did you install the first one that you had problems with? Did it ever work at all? If so, when did it start malfunctioning?
Click to expand...
Click to collapse
Yes it used to work, I already tried a lot of ROMs, I had the one compatible with Android 6.0 which I flashed with TWRP itself (It worked since I flashed CM13 with it).
I don't really know when it started malfunctioning because the last time I made a backup was at least one month ago when I swapped to PsyRom (it was functioning well). But two days ago when I tried to access it to change to FlyMe it wouldn't work. Anyways I'm flashing a MIUI7 fastboot ROM to see if it works.
I'm sorry if I can't explain myself very well but I'm doing the best I can lol. Thank you for your help too.
Perhaps something messed up your file system or partitions. If all attempts don't work, then you might want to use the SP Flash Tool to flash a compatible ROM and working TWRP.
DarthJabba9 said:
Perhaps something messed up your file system or partitions. If all attempts don't work, then you might want to use the SP Flash Tool to flash a compatible ROM and working TWRP.
Click to expand...
Click to collapse
I just flashed MIUI 7 with SP Flash Tool. Gonna try and flash TWRP through fastboot and with update.zip method, see if anything works.
kiko9895 said:
I'm sorry but do you know where I can find an older one?
Click to expand...
Click to collapse
I should have a MIUI7 on my mega account, it should be the last 7 stable, saved just in case something was wrong with 8.
I can send you the link if you are still searching.
OK, I just noticed that you have solved yet.
Good, I hope that this time everything will be fine.
gnazio said:
I should have a MIUI7 on my mega account, it should be the last 7 stable, saved just in case something was wrong with 8.
I can send you the link if you are still searching.
OK, I just noticed that you have solved yet.
Good, I hope that this time everything will be fine.
Click to expand...
Click to collapse
Thank you very much for your kindness, I'm still trying tho ahah using WinDroid Toolkit now.
gnazio said:
I should have a MIUI7 on my mega account, it should be the last 7 stable, saved just in case something was wrong with 8.
I can send you the link if you are still searching.
OK, I just noticed that you have solved yet.
Good, I hope that this time everything will be fine.
Click to expand...
Click to collapse
Hello, after one month the issue is still not fixed, the recovery still hangs. Perhaps you could send me that fastboot rom you talked about please? Thank you.
I'm going to send you the link.
In the meanwhile...reading the thread again...what is "update.zip method"?
Are you try to install TWRP from Mi recovery?
This is not going to work anymore.
You should better stay with the last ROM and flash TWRP from fastboot.
This is the recovery image: https://dl.twrp.me/hermes/twrp-3.0.2-0-hermes.img
This is the guide: https://twrp.me/devices/xiaomiredminote2.html
Just start your RN2 into fastboot (vol down+power on), run fastboot flash recovery twrp.img and finally keep pressed vol up and send fastboot reboot and wait with the key pressed until it enter TWRP.
BTW:
in the official forum there should be a thread with link to all officially released ROMs for RN2.
kiko9895 said:
Hello, after one month the issue is still not fixed, the recovery still hangs. Perhaps you could send me that fastboot rom you talked about please? Thank you.
Click to expand...
Click to collapse
Here you should find every MIUI Global ROM released for RN2:
http://en.miui.com/forum.php?mod=viewthread&tid=394496
I just realized that the one I have is China version, used just to clean the phone from reseller ROM.
gnazio said:
I'm going to send you the link.
In the meanwhile...reading the thread again...what is "update.zip method"?
Are you try to install TWRP from Mi recovery?
This is not going to work anymore.
You should better stay with the last ROM and flash TWRP from fastboot.
This is the recovery image: https://dl.twrp.me/hermes/twrp-3.0.2-0-hermes.img
This is the guide: https://twrp.me/devices/xiaomiredminote2.html
Just start your RN2 into fastboot (vol down+power on), run fastboot flash recovery twrp.img and finally keep pressed vol up and send fastboot reboot and wait with the key pressed until it enter TWRP.
BTW:
in the official forum there should be a thread with link to all officially released ROMs for RN2.
Click to expand...
Click to collapse
The problem is I already tried the fastboot method as well, and the problem is always the same, stuck TWRP logo. Even if it was a partition problem, flashing the fastboot ROM should fix it, but it didn't. I tried the SP Flash Tools method too, and the flashing methods are successful, they all Flash TWRP, but when I try to access it it's stuck. I don't know why this is happening, it used to work.
@kiko9895 Sounds like you have screwed your partitions. You will need to load a full ROM using SP Tools to correct it as this is the only way to set the partitions back at their correct memory locations. Fastboot and Recovery rewrite the partitions by name not memory location so any fault in that will never be fixed. If you have flashed an Android 6.0 based ROM or something intended for another model phone, this will definitely be the case. Anyone flashing custom ROMs should first gather the skills and tools to recover from disasters - luckily, MTK based phones are virtually unbrickable!
As far as the "official" TWRP goes, it is not official and not a good version. It is just someone who has used the TWRP build server to knock out a random version. How does that make it "official"?
jajk said:
@kiko9895 Sounds like you have screwed your partitions. You will need to load a full ROM using SP Tools to correct it as this is the only way to set the partitions back at their correct memory locations. Fastboot and Recovery rewrite the partitions by name not memory location so any fault in that will never be fixed. If you have flashed an Android 6.0 based ROM or something intended for another model phone, this will definitely be the case. Anyone flashing custom ROMs should first gather the skills and tools to recover from disasters - luckily, MTK based phones are virtually unbrickable!
As far as the "official" TWRP goes, it is not official and not a good version. It is just someone who has used the TWRP build server to knock out a random version. How does that make it "official"?
Click to expand...
Click to collapse
Ahah I have the skills and the tools, I've been flashing ROMs for more than two years. This never happened before. If you read what I said before on this thread, you'll see that I already flashed a new ROM through SP Flash Tools. And yes I flashed a 6.0 rom before so that must be the problem, but since I already flashed a fastboot rom through SP Flash Tools I can't see where the problem is. The partitions should be fixed by now but that isn't the case.
@kiko9895 Sorry if it sounded like I was coming down hard on you. You should only need to flash a matching preloader, uboot, logo plus TWRP recovery using SP Flash Tools with the correct scatter file to get back into booting to TWRP. Any other problems can be sorted from there.
I will attach a known good scatter file because I know there are several floating around that will reverse one or two partitions on you (such as the RN3 version)
I got the latest CM14.1 nightly(25 Dec) and flashed it. After that, I flashed the BlackReactor Kernel. I booted the phone and it booted up fine. I went ahead and flashed Opengapps after that. Then I went through the setup process and then flashed the GooglePixelExperience zip (v3.5) However when I booted the phone, the boot screen was completely blank and the phone's LED turned white. I waited but then the phone did not boot up.
aryan.arora180 said:
boot screen was completely blank and the phone's LED turned white.
Click to expand...
Click to collapse
Unrepairable hard brick. Sent mine with same prolbem to them, got it back with new mainboard. Now it on a new unreleased rom built and twrp doesn't find any partition. So no more root or custom rom.
See my posts to read more about it.
I had similar issue with a kernel once where screen went black and white LED. Was able to reflash ROM no problem. Your better too install pixel experience piece by piece.
Can't be a hard brick
adefigo said:
Unrepairable hard brick. Sent mine with same prolbem to them, got it back with new mainboard. Now it on a new unreleased rom built and twrp doesn't find any partition. So no more root or custom rom.
See my posts to read more about it.
Click to expand...
Click to collapse
It can't be a hard brick, I was able to get into recovery and wipe and reflash the ROM, this time without flashing GooglePixel Experience and it worked just fine.
Exodusche said:
I had similar issue with a kernel once where screen went black and white LED. Was able to reflash ROM no problem. Your better too install pixel experience piece by piece.
Click to expand...
Click to collapse
What do you mean by installing GooglePixel Experience piece by piece? It's a single zip file.
Did it work on any previous version of the rom or did it work without the custom kernel?
aryan.arora180 said:
What do you mean by installing GooglePixel Experience piece by piece? It's a single zip file.
Click to expand...
Click to collapse
Google experience is made up of mostly installable apps. You could open the zip with file manager and see what it consists of. Might be just one thing in the zip that's not compatible with your device or maybe are version of cm14
Akshat2100 said:
Did it work on any previous version of the rom or did it work without the custom kernel?
Click to expand...
Click to collapse
I never tried using it with the previous version of the ROM, I had found the zip from a different site and it worked just fine. I wasn't able to find the link to my previous one and only found this: https://www.androidfilehost.com/?w=files&flid=122156
adefigo said:
Unrepairable hard brick. Sent mine with same prolbem to them, got it back with new mainboard. Now it on a new unreleased rom built and twrp doesn't find any partition. So no more root or custom rom.
See my posts to read more about it.
Click to expand...
Click to collapse
Definitely not mate. Hell half the time if mine kernel panics, depending on the rom it just goes to a black screen with white LED. You can find that all across this forum as the phone just does that.
Hi, my Redmi note 3 Pro was working just fine on MoKee rom but I wanted to change for LineageOS 14.1, so I did it. So I flashed the firmware to have the latest then flashed everything fine. My phone worked fine on LineageOS til I install adaway, my phone asked for a reboot and I had black screen after typing my Sim Card PIN. I did multiple fresh install, different rom, Stock and Custom, android N, always the same problem. I also tried different version of TWRP, still the black screen of death. I also tried ZCW_TWRP but it was still the same. I formatted partition manually using fastboot and still the same problem.
Then I did nothing different, Wipe of everything necessary using TWRP, installed LineageOS 14.1 and it worked just like this, totally random. Yesterday, I was trying to copy some music on my SD card when my phone froze in the middle of the process. Of course, I had to reboot it and now he is freezing on boot with this beautiful black screen of death just after I enter my Sim Card PIN.
I tried to flash the Radon Kernel to see if something was going to change but it stayed the same. I am thinking it is because of the firmware since I didn't have any problem before I flash it.
Pls guys tell me you have a solution. It seems like it's a random bug occuring for no obvious reason and disappearing like if nothing just happened.
Thanks you all for reading and I hope you'll have some solutions for me
ddescham said:
Hi, my Redmi note 3 Pro was working just fine on MoKee rom but I wanted to change for LineageOS 14.1, so I did it. So I flashed the firmware to have the latest then flashed everything fine. My phone worked fine on LineageOS til I install adaway, my phone asked for a reboot and I had black screen after typing my Sim Card PIN. I did multiple fresh install, different rom, Stock and Custom, MM and N, always the same problem. I also tried different version of TWRP, still the black screen of death. I also tried ZCW_TWRP but it was still the same. I formatted partition manually using fastboot and still the same problem.
Then I did nothing different, Wipe of everything necessary using TWRP, installed LineageOS 14.1 and it worked just like this, totally random. Yesterday, I was trying to copy some music on my SD card when my phone froze in the middle of the process. Of course, I had to reboot it and now he is freezing on boot with this beautiful black screen of death just after I enter my Sim Card PIN.
I tried to flash the Radon Kernel to see if something was going to change but it stayed the same. I am thinking it is because of the firmware since I didn't have any problem before I flash it.
Pls guys tell me you have a solution. It seems like it's a random bug occuring for no obvious reason and disappearing like if nothing just happened.
Thanks you all for reading and I hope you'll have some solutions for me
Click to expand...
Click to collapse
Try reverting to latest global dev rom in fastboot (clean all), unlock and flash los again.
JLius said:
Try reverting to latest global dev rom in fastboot (clean all), unlock and flash los again.
Click to expand...
Click to collapse
I tried it already, didn't work. My phone kept freezing on boot. Exact same problem.
ddescham said:
I tried it already, didn't work. My phone kept freezing on boot. Exact same problem.
Click to expand...
Click to collapse
Then you'll probably need a new phone
JLius said:
Then you'll probably need a new phone
Click to expand...
Click to collapse
My phone work now, but I don't know for how long. SInce it's a random bug.
ddescham said:
My phone work now, but I don't know for how long. SInce it's a random bug.
Click to expand...
Click to collapse
Can't be a bug when you clean flashed miui.
ddescham said:
My phone work now, but I don't know for how long. SInce it's a random bug.
Click to expand...
Click to collapse
It's surely some eMMC issue
bro,try removing sim card lock.
just try it.Can it be your solution!!
Androbots said:
It's surely some eMMC issue
Click to expand...
Click to collapse
How do I fix that then?
dean [email protected]# said:
bro,try removing sim card lock.
just try it.Can it be your solution!!
Click to expand...
Click to collapse
No, it's not. If the solution was that simple, I wouldn't be asking there. I tried booting it without any Sim card and the result was the exact same.
bro,you flashed which firmware after you got all this problem, please describe the full name
dean [email protected]# said:
bro,you flashed which firmware after you got all this problem, please describe the full name
Click to expand...
Click to collapse
I flashed the firmware of the miui_HMNote3ProGlobal_7.6.7. Found the Zip here on XDA. And this version is recommended for custom ROM which is my case. I tried to flash another version of the firmware but I still have the same issue anyway.
bro,the firmware you flashed is I think have some problems,I visited the page from where you downloaded this firmware on xda and a lot of people are having sim card problems. so,try contacting maintainer of that firmware to get solution.
dean [email protected]# said:
bro,the firmware you flashed is I think have some problems,I visited the page from where you downloaded this firmware on xda and a lot of people are having sim card problems. so,try contacting maintainer of that firmware to get solution.
Click to expand...
Click to collapse
I don't have problem with my sim card... I have a black screen of death WITH and WITHOUT sim card in >.> Also, I told you I flashed a different firmware and I still have the same problem.
ddescham said:
I don't have problem with my sim card... I have a black screen of death WITH and WITHOUT sim card in >.> Also, I told you I flashed a different firmware and I still have the same problem.
Click to expand...
Click to collapse
Flash firmware from lineage os thread
ook bro ,so I don't know your problem solution
Androbots said:
Flash firmware from lineage os thread
Click to expand...
Click to collapse
If you are talking about that thread https://goo.gl/t5SVYv , I tried there solution and there firmware gave me the same issue too.
dean [email protected]# said:
ook bro ,so I don't know your problem solution
Click to expand...
Click to collapse
Thanks for trying.
ddescham said:
If you are talking about that thread https://goo.gl/t5SVYv , I tried there solution and there firmware gave me the same issue too.
Thanks for trying.
Click to expand...
Click to collapse
milankumarn said:
Mi logo blinks when i press the power button.
Click to expand...
Click to collapse
Flash stock emmc file that u can obtain from latest official miui ROM via fastboot.
- Boot into fastboot (connect device to pc),
- Open cmd on adb fastboot (on adb folder press and hold shift+right click then click open command windows here),
- Type fastboot flash aboot "drag and drop emmc file to ur command line" then press enter.
Hope it works.
Capt. John Yossarian said:
Flash stock emmc file that u can obtain from latest official miui ROM via fastboot.
- Boot into fastboot (connect device to pc),
- Open cmd on adb fastboot (on adb folder press and hold shift+right click then click open command windows here),
- Type fastboot flash aboot "drag and drop emmc file to ur command line" then press enter.
Hope it works.
Click to expand...
Click to collapse
I already flashed latest MIUI ROM in fastboot mode and the phone was still having the same issue. Black screen after I enter my Pin code or after 5 seconds of running, while starting android and everything.
ddescham said:
I already flashed latest MIUI ROM in fastboot mode and the phone was still having the same issue. Black screen after I enter my Pin code or after 5 seconds of running, while starting android and everything.
Click to expand...
Click to collapse
Emmc file, not rom.
Capt. John Yossarian said:
Emmc file, not rom.
Click to expand...
Click to collapse
When you flash a ROM, you flash the emmc as well.
It's up and here https://developers.google.com/android/ota
gm007 said:
It's up and here https://developers.google.com/android/ota
Click to expand...
Click to collapse
Changelog?
Sent from my Pixel 3 using Tapatalk
nickporwal said:
Changelog?
Click to expand...
Click to collapse
https://source.android.com/security/bulletin/pixel/2018-12-01.html
One of this days the 'Check for Update' button will work damn it! Hahahaha
Hahaha right, I have been flashing the OTA manually, its no biggie for me I am used to manually flashing the ota now
AntLyoN2053 said:
One of this days the 'Check for Update' button will work damn it! Hahahaha
Click to expand...
Click to collapse
Can anybody sucessfully root again?
Just flash-all works fine, but after flashing magisk 17.3 again and reboot, phone instant restarts to recovery and tells me devices is corrupt.
AntLyoN2053 said:
One of this days the 'Check for Update' button will work damn it! Hahahaha
Click to expand...
Click to collapse
I got it through ota 1 hour ago.
gm007 said:
I got it through ota 1 hour ago.
Click to expand...
Click to collapse
You know Im mashing the button, lol. Only google phone that got all the updates pretty much same day was the Nexus 6P, I used to get the update notification even before any site would announce that it was out
Bluffer94 said:
Can anybody sucessfully root again?
Just flash-all works fine, but after flashing magisk 17.3 again and reboot, phone instant restarts to recovery and tells me devices is corrupt.
Click to expand...
Click to collapse
Same, not able to root with beta or canary builds atm.. seems to just boot back to twrp every time.
sulpher said:
Same, not able to root with beta or canary builds atm.. seems to just boot back to twrp every time.
Click to expand...
Click to collapse
I've rooted with 17.3 without a problem. Are you just booting into twrp, not flashing it?
Sent from my [device_name] using XDA-Developers Legacy app
Bluffer94 said:
Can anybody sucessfully root again?
Just flash-all works fine, but after flashing magisk 17.3 again and reboot, phone instant restarts to recovery and tells me devices is corrupt.
Click to expand...
Click to collapse
sulpher said:
Same, not able to root with beta or canary builds atm.. seems to just boot back to twrp every time.
Click to expand...
Click to collapse
Do you have the Magisk uninstaller on your phone? Run it from the temp TWRP .img, and then it should boot OK. Go back to temp TWRP, and install Magisk again. The Edge Sense Plus module is broken again. Don not reinstall it until fixed.
Bluffer94 said:
Can anybody sucessfully root again?
Just flash-all works fine, but after flashing magisk 17.3 again and reboot, phone instant restarts to recovery and tells me devices is corrupt.
Click to expand...
Click to collapse
sulpher said:
Same, not able to root with beta or canary builds atm.. seems to just boot back to twrp every time.
Click to expand...
Click to collapse
Flash all after removing the -w, rebooted and let it finish. Boot to TWRP and installed the latest canary. Did not install TWRP.
All good.
jd1639 said:
I've rooted with 17.3 without a problem. Are you just booting into twrp, not flashing it?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Ah figured it out, edge sense broken.
edit- thanks guys~
sulpher said:
Ah figured it out, edge sense broken.
Click to expand...
Click to collapse
There's no magic. I sideload the ota in the stock recovery. Booted into the system to make sure everything worked. Powered off the device and booted into the bootloader. Then booted twrp and flashed magisk. Then booted into the system. That's it.
Sent from my [device_name] using XDA-Developers Legacy app
No OTA here... It usually comes days later with unlocked Google pixel using TMobile. -.-
Installed the full version to update it, root just after and everything's fine!
There is only the edge sense that is'nt working as already told
TWRP keeps getting error 1 when flashing the OTA, bit odd
The TWRP for this device has never been able to side-load the OTA it always errors out. I just use the full firmware and take out the -w and all good.
laill said:
TWRP keeps getting error 1 when flashing the OTA, bit odd
Click to expand...
Click to collapse
Archangel said:
The TWRP for this device has never been able to side-load the OTA it always errors out. I just use the full firmware and take out the -w and all good.
Click to expand...
Click to collapse
So then how do we flash the OTA and keep root? Pardon my ignorance on the matter but taking out the -w, do you mean through terminal on the device or flashing with adb or something? Just need a little more detail.
I am used to putting the OTA on the device and flashing through TWRP then flashing TWRP&Magisk again before a full restart.
Once again I am new to this style of flashing so sorry for asking a dumb question.
What I do is download the full updated firmware, unzip that in your platform tools folder,,,make sure you also unzip the second zip inside there as well. If you have the Pixel edge module installed uninstall it and I also uninstalled Magisk in TWRP before I updated just in case there were any problems. Then find the flash-all.bat file in your platform tools folder, right click on it, open with notepad+ and find the -w at the bottom and delete it. After this, save the flash-all.bat notepad xml file and do not just close it. You can then flash the full firmware without it deleting your user data. After this you will have to fastboot boot TWRP and flash the TWRP zip over again. I rebooted then used TWRP to flash the Magisk 17.1 zip. I am up and running and did the same thing last month for the Nov update,,,hope this helps.
Rumsfield said:
So then how do we flash the OTA and keep root? Pardon my ignorance on the matter but taking out the -w, do you mean through terminal on the device or flashing with adb or something? Just need a little more detail.
I am used to putting the OTA on the device and flashing through TWRP then flashing TWRP&Magisk again before a full restart.
Once again I am new to this style of flashing so sorry for asking a dumb question.
Click to expand...
Click to collapse