Related
Hello folks. Today I did a cache, system, data wipe in TWRP on my G920F. After that I tried to restore a nandroid backup, but it failed and when I tried to restart it said there was no OS installed. So the phone wouldn't boot. I figured I did something wrong so I downloaded a 5.1.1 stock rom (UK) and flashed it with odin. But after the flash the phone would just bootloop. How can I revive the phone? Tried flashing the firmware again using another version of odin and also, I did a factory reset from the stock recovery, but no dice. Any ideas? Thanks in advance
Hey there,
check this thread here, should help (use TWRP to flash a ROM instead of Odin, links in thread).
Good luck!
Managed to make it work flashing another official rom, then factory reset. Lost all my files though...
Can be closed. Thanks!
Sent from my SM-G925F using Tapatalk
kendall1004 said:
Hey there,
check this thread here, should help (use TWRP to flash a ROM instead of Odin, links in thread).
Good luck!
Click to expand...
Click to collapse
How can i make TWRP flash a rom when Galaxy S6 doesn't have SD card to put the rom in the phone?
Immoblize said:
How can i make TWRP flash a rom when Galaxy S6 doesn't have SD card to put the rom in the phone?
Click to expand...
Click to collapse
Connect the phone to your PC and copy the ROM file to its root folder (just open "phone" and drop it there).
Using TWRP's "install" menu, you can browse your files and point it to this one; usually you're already in the right directory.
kendall1004 said:
Connect the phone to your PC and copy the ROM file to its root folder (just open "phone" and drop it there).
Using TWRP's "install" menu, you can browse your files and point it to this one; usually you're already in the right directory.
Click to expand...
Click to collapse
I wish that was so easy. I am on bootloop on my second day and i can fix it. I am getting crazy here. Nothing work - Kies, Smart Switch or Odin.
Immoblize said:
I wish that was so easy. I am on bootloop on my second day and i can fix it. I am getting crazy here. Nothing work - Kies, Smart Switch or Odin.
Click to expand...
Click to collapse
None of these three will help, i'm afraid.
The bootloop issue is a result of system write protection with 5.1.1 version, the phone tries to override a flashed recovery-
if it succeeds in automatically rebooting after you flashed, you're stuck on bootloop.
You have to flash a new kernel and root user via Odin, then flash TWRP and use it to install a new ROM.
A short description in this thread here, have a look.
As long as you can get into download mode, don't worry, nothings bricked :good:
kendall1004 said:
None of these three will help, i'm afraid.
The bootloop issue is a result of system write protection with 5.1.1 version, the phone tries to override a flashed recovery-
if it succeeds in automatically rebooting after you flashed, you're stuck on bootloop.
You have to flash a new kernel and root user via Odin, then flash TWRP and use it to install a new ROM.
A short description in this thread here, have a look.
As long as you can get into download mode, don't worry, nothings bricked :good:
Click to expand...
Click to collapse
THANKS A LOT for the info. I have today worked for about 8-9 hours to fix it. I will try read tomorrow on the site you put there and also read about how to put files to TWRP - since i don't have a SD card on my S6.
Immoblize said:
THANKS A LOT for the info. I have today worked for about 8-9 hours to fix it. I will try read tomorrow on the site you put there and also read about how to put files to TWRP - since i don't have a SD card on my S6.
Click to expand...
Click to collapse
Sleep over it, tomorrow is another day
Also, browse my recent postings here; most of them revolving around your issue, this will surely help.
kendall1004 said:
None of these three will help, i'm afraid.
The bootloop issue is a result of system write protection with 5.1.1 version, the phone tries to override a flashed recovery-
if it succeeds in automatically rebooting after you flashed, you're stuck on bootloop.
You have to flash a new kernel and root user via Odin, then flash TWRP and use it to install a new ROM.
A short description in this thread here, have a look.
As long as you can get into download mode, don't worry, nothings bricked :good:
Click to expand...
Click to collapse
Okay, i have done almost all of what you said.
But what im thinking about is the thread your refering to is to a S6 Edge and not for SM-G920F model.
But so far so good.
What kernel to you want me to flash? How can i root via Odin when i don't have USB-debugging on - But i can according to the thread, install SuperSU via TWRP.
I didn't know what kernel i had on, but i managed to install TWRP, install SuperSU via TWRP, pushing my stock rom to TWRP. But when installing the stock rom, it says "no md5 file found" or something like that. What am i doing wrong?
Immoblize said:
Okay, i have done almost all of what you said.
But what im thinking about is the thread your refering to is to a S6 Edge and not for SM-G920F model.
But so far so good.
What kernel to you want me to flash? How can i root via Odin when i don't have USB-debugging on - But i can according to the thread, install SuperSU via TWRP.
I didn't know what kernel i had on, but i managed to install TWRP, install SuperSU via TWRP, pushing my stock rom to TWRP. But when installing the stock rom, it says "no md5 file found" or something like that. What am i doing wrong?
Click to expand...
Click to collapse
Should work on both Edge and normal.
I have the G920F and did it this way, i also had problems, by the way:
http://forum.xda-developers.com/showpost.php?p=62550973&postcount=29
I recommend chosing an XtreStoLite ROM, the odexed version is an "improved stock" one, comes with a modified UniKernel and runs much smoother than stock.
Anyway, in TWRP, there is an option to skip md5 checking for backup files and for skipping the zipfile-check; not sure if you can also disable md5sum-checks.
Maybe you should try downloading the ROM from here or sammobile.de, verify the md5-sum yourself to make sure it is fine, and flash that one.
If TWRP doesn't think the ROM file is ok, it probably isn't ...
here's the odexed version of XtreStoLite:
http://forum.xda-developers.com/galaxy-s6/development/rom-xtrestolite-pure-edition-1-0-beta-1-t3082467
kendall1004 said:
Should work on both Edge and normal.
I have the G920F and did it this way, i also had problems, by the way:
http://forum.xda-developers.com/showpost.php?p=62550973&postcount=29
I recommend chosing an XtreStoLite ROM, the odexed version is an "improved stock" one, comes with a modified UniKernel and runs much smoother than stock.
Anyway, in TWRP, there is an option to skip md5 checking for backup files and for skipping the zipfile-check; not sure if you can also disable md5sum-checks.
Maybe you should try downloading the ROM from here or sammobile.de, verify the md5-sum yourself to make sure it is fine, and flash that one.
If TWRP doesn't think the ROM file is ok, it probably isn't ...
here's the odexed version of XtreStoLite:
http://forum.xda-developers.com/galaxy-s6/development/rom-xtrestolite-pure-edition-1-0-beta-1-t3082467
Click to expand...
Click to collapse
Okay, i have flashed TWRP, installed the kernel and Super SU (http://forum.xda-developers.com/gal...p-recovery-2-8-7-1-g925f-android-5-1-t3144866). But i can't flash the modem and bootloader for the XtreStoLite because it gives me Nand write error. I tried then to install XtreStoLite from TWRP which installed correctly but still doesn't fix the bootloop. I can read that i WILL get the bootloop if not using the correct modem and bootloader, but for some reason i am not able to flash them. Any help here? Or am i doing everything wrong here?
Immoblize said:
Okay, i have flashed TWRP, installed the kernel and Super SU (http://forum.xda-developers.com/gal...p-recovery-2-8-7-1-g925f-android-5-1-t3144866). But i can't flash the modem and bootloader for the XtreStoLite because it gives me Nand write error. I tried then to install XtreStoLite from TWRP which installed correctly but still doesn't fix the bootloop. I can read that i WILL get the bootloop if not using the correct modem and bootloader, but for some reason i am not able to flash them. Any help here? Or am i doing everything wrong here?
Click to expand...
Click to collapse
Alright, you have root access and TWRP is running.
All you have to do is install the ROM file (unextracted, as a .zip) from your phone`s root folder; if your model is a G920F, the bootloader should be 5.1.1 and work, no need to change.
When exactly does Odin give you the error message, right after you click start or after a few secs of flashing?
I suspect the issue to be related to first reboot after flashing the recovery,.
When finished flashing TWRP, did you successfully boot into recovery menu be pressing vol up+home+power?
If you saw the bootloop screen then, you`ll have to do it again, i'm afraid:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. (...) Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
I know, it`s annoying; but give it another try:
use Odin 3.1.0.7 (run with admin rights), do a full wipe and install TWRP 2.8.7.
When doing so and Odin gives you the "finished/successfully flashed" message, immediately press & hold the key combo to get into recovery; don`t wait for the scrteen to change or unplug the phone, you need to be damn quick here.
If you have done it right, you are in TWRPs recovery menu.
From there, install the XtreStoLite ROM after doing a factory reset; reboot and you should be fine.
Aaaarrgh we will get this thing running, goddammit
kendall1004 said:
Alright, you have root access and TWRP is running.
All you have to do is install the ROM file (unextracted, as a .zip) from your phone`s root folder; if your model is a G920F, the bootloader should be 5.1.1 and work, no need to change.
When exactly does Odin give you the error message, right after you click start or after a few secs of flashing?
I suspect the issue to be related to first reboot after flashing the recovery,.
When finished flashing TWRP, did you successfully boot into recovery menu be pressing vol up+home+power?
If you saw the bootloop screen then, you`ll have to do it again, i'm afraid:
I know, it`s annoying; but give it another try:
use Odin 3.1.0.7 (run with admin rights), do a full wipe and install TWRP 2.8.7.
When doing so and Odin gives you the "finished/successfully flashed" message, immediately press & hold the key combo to get into recovery; don`t wait for the scrteen to change or unplug the phone, you need to be damn quick here.
If you have done it right, you are in TWRPs recovery menu.
From there, install the XtreStoLite ROM after doing a factory reset; reboot and you should be fine.
Aaaarrgh we will get this thing running, goddammit
Click to expand...
Click to collapse
What i did was install stock android via Odin.
Flashed TWRP
Flashed Alex V kernel first, then SUPER SU.
Flashed XtreStoLite and it still gives me bootloop.
What i can't manage to do is after flashing TWRP, then i am not fast enough to press Shutdown button, home button, and volume up button before the Samsung logo appears. I think that is the problem.
:silly:
Immoblize said:
What i did was install stock android via Odin.
Flashed TWRP
Flashed Alex V kernel first, then SUPER SU.
Flashed XtreStoLite and it still gives me bootloop.
What i can't manage to do is after flashing TWRP, then i am not fast enough to press Shutdown button, home button, and volume up button before the Samsung logo appears. I think that is the problem.
Click to expand...
Click to collapse
That IS the problem, i think :fingers-crossed:
Solved the same problem at reddit, take a look: reddit thread
Unfortunately, you must flash TWRP again to try once more, as soon as the samsung logo apperars, your custom recovery is overridden and thats it.
So now, take a deep breath, lean back and try again.
As soon as you have clicked to start the flashing procedure, press the 3 butons firmly, simultaneously and quick as lightning-
hold them down till it boots into TWRP.
Come on, even i have managed it after a few tries
kendall1004 said:
:silly:
That IS the problem, i think :fingers-crossed:
Solved the same problem at reddit, take a look: reddit thread
Unfortunately, you must flash TWRP again to try once more, as soon as the samsung logo apperars, your custom recovery is overridden and thats it.
So now, take a deep breath, lean back and try again.
As soon as you have clicked to start the flashing procedure, press the 3 butons firmly, simultaneously and quick as lightning-
hold them down till it boots into TWRP.
Come on, even i have managed it after a few tries
Click to expand...
Click to collapse
HMMM. I see.
It's not possible for me to boot into TWRP without the Samsung logo appears. I press the start, the same time i press the start, i press Power, Home and Volume Up button but still the logo appears. It takes 4 sec and it have flashed the TWRP. It's not possible...
Immoblize said:
HMMM. I see.
It's not possible for me to boot into TWRP without the Samsung logo appears. I press the start, the same time i press the start, i press Power, Home and Volume Up button but still the logo appears. It takes 4 sec and it have flashed the TWRP. It's not possible...
Click to expand...
Click to collapse
So, for some reason you can't enter recovery mode.
This could be
a) TWRP is not installed correctly (did you use the .img ot the .tar-file? Odin needs the .tar-format: link )
or
b) the kernel you flashed doesn't work with this-
here is the one i have used to root my S6.
I would try to reflash above Unikernel first, if you used the .img-file of TWRP rather than the .tar to flash TWRP,
do it again with the .tar file instead.
If this fails, the last thing would be to flash a unmodified stock ROM to restore the original setup including the bootloader...
i will look into this now a little bit deeper, there has to be a workaround.
Best of luck for now, we stay in touch
EDIT: the developer of XtreStoLite recommends another way with Chainfire's root:
Flash CF-Root for your model with Odin - Make sure you have an custom recovery installed (I advise you to use TWRP) (2.8.7.1 or newer REQUIRED for v.2.1 > of this ROM!!)
Click to expand...
Click to collapse
If the bootloader is your problem, you can update to the newest versions of bootloader and modem for your model following these instructions:
edgarf28`s instructions
I will do this right now, for a new version of XtreStoLite was just released today and i will upgrade.
Keep me informed
kendall1004 said:
So, for some reason you can't enter recovery mode.
This could be
a) TWRP is not installed correctly (did you use the .img ot the .tar-file? Odin needs the .tar-format: link )
or
b) the kernel you flashed doesn't work with this-
here is the one i have used to root my S6.
I would try to reflash above Unikernel first, if you used the .img-file of TWRP rather than the .tar to flash TWRP,
do it again with the .tar file instead.
If this fails, the last thing would be to flash a unmodified stock ROM to restore the original setup including the bootloader...
i will look into this now a little bit deeper, there has to be a workaround.
Best of luck for now, we stay in touch
EDIT: the developer of XtreStoLite recommends another way with Chainfire's root:
If the bootloader is your problem, you can update to the newest versions of bootloader and modem for your model following these instructions:
edgarf28`s instructions
I will do this right now, for a new version of XtreStoLite was just released today and i will upgrade.
Keep me informed
Click to expand...
Click to collapse
I can enter the recovery mode (TWRP) but not before the Samsung logo appears when i install TWRP. I have tried many times and i still can't enter TWRP before the samsung logo appears for 1-2 secs.
I am not able to flash Edgar28s bootloader and modem because it always gives me nand write error fail. I think it's because i'm not rooted with CFautoroot - and to get rooted with that way, i have to have USB debuggin on which i don't have.
What i think is, that i was very close but i still can't manage to enter TWRP (after installing) without the samsung logo appears for 1-2 secs. Because what you said before "Unfortunately, you must flash TWRP again to try once more, as soon as the samsung logo apperars, your custom recovery is overridden and thats it."
So what do you think now?
And btw thanks for all the help so far. I'm trying my best and following your steps but i always think i'm very close. I'm also so close to destroy my phone but i've read so many places that "it's only a softbrick, that can be fixed very easy".
Immoblize said:
I can enter the recovery mode (TWRP) but not before the Samsung logo appears when i install TWRP. I have tried many times and i still can't enter TWRP before the samsung logo appears for 1-2 secs.
I am not able to flash Edgar28s bootloader and modem because it always gives me nand write error fail. I think it's because i'm not rooted with CFautoroot - and to get rooted with that way, i have to have USB debuggin on which i don't have.
What i think is, that i was very close but i still can't manage to enter TWRP (after installing) without the samsung logo appears for 1-2 secs. Because what you said before "Unfortunately, you must flash TWRP again to try once more, as soon as the samsung logo apperars, your custom recovery is overridden and thats it."
So what do you think now?
And btw thanks for all the help so far. I'm trying my best and following your steps but i always think i'm very close. I'm also so close to destroy my phone but i've read so many places that "it's only a softbrick, that can be fixed very easy".
Click to expand...
Click to collapse
OK, so you can enter the TWRP menu and install a ROM, right?
Any stock ROM from sammobile.com includes firmware, kernel and bootloader, so flashing the right one of these should reset all this.
Give it a try, for i think TWRP is actually working- otherwise you wouldn't get to the screen.
If the phone runs again with stock firmware, you can then flash a custom ROM.
And yeah, we're close, this can be only a minor flaw...it's near impossible to brick your android phone, so they say.
Don't worry mate, and be assured you're not the only one:
i just got stuck on bootloop also for a few minutes after upgrading to the newest version of XtreStoLite, which came out today.
Using TWRP, i could just flash back the previous version and all's good again.
Cya tomorrow...
EDIT:
I read through your previous comments again; the "md5sum"- issue seems to be a problem with the ROM file itself (corrupted or wrong version).
I'd bet that flashing the correct stock firmware for your carrier and model will solve the problem.
So enter the exact model number (like G920FXXU3COI9 or such) you have, get the right ROM and flash it with Odin 3.10.7
I couldn't find a denmark carrier on sammobile, eventually you have to look here at XDA, there's a list of stock imges as well.
Read lots of threads around this issue, almost all solved the problem flashing a stock ROM again.
Fingers crossed :fingers-crossed:
OK, so you can enter the TWRP menu and install a ROM, right?
Any stock ROM from sammobile.com includes firmware, kernel and bootloader, so flashing the right one of these should reset all this.
Give it a try, for i think TWRP is actually working- otherwise you wouldn't get to the screen.
If the phone runs again with stock firmware, you can then flash a custom ROM.
And yeah, we're close, this can be only a minor flaw...it's near impossible to brick your android phone, so they say.
Don't worry mate, and be assured you're not the only one:
i just got stuck on bootloop also for a few minutes after upgrading to the newest version of XtreStoLite, which came out today.
Using TWRP, i could just flash back the previous version and all's good again.
Cya tomorrow...
EDIT:
I read through your previous comments again; the "md5sum"- issue seems to be a problem with the ROM file itself (corrupted or wrong version).
I'd bet that flashing the correct stock firmware for your carrier and model will solve the problem.
So enter the exact model number (like G920FXXU3COI9 or such) you have, get the right ROM and flash it with Odin 3.10.7
I couldn't find a denmark carrier on sammobile, eventually you have to look here at XDA, there's a list of stock imges as well.
Read lots of threads around this issue, almost all solved the problem flashing a stock ROM again.
Fingers crossed
Click to expand...
Click to collapse
Yeah, i've never had problems entering TWRP menu. I can flash stock firmware via Odin but i can never do it via TWRP because it's says no md5 file found error - tho i can flash XtreStoLite (i think it's because it says aroma installer).
I've read many places about the md5 file error, but for some reason, i can't figure out how to fix it.
No, there is no Denmark model, but we have NEE (Nordic). The only stock firmware i can install is XEF (i don't remember where i got that from actually).
I will try agian and flash stock android via TWRP AND read about the md5 file error now/later. Tomorrow i will call the store i got the phone from and tell them i have a hardware issue or something like that. The guy owns a store for sellings covers, cases and stuff like that. He got the phone from Samsung free and sold it brand new in the package with 1 year warranty, so i will contact him tomorrow if i can't figure out how to flash stock android via TWRP or if it gives me error about the md5 file.
Talk to you tomorrow.
Update: I can not flash NEE model via Odin. Only XEF model - i also found out it was French firmware.
Unbrick tool by One-Team - EypCnn
First: This tool seems to be from EypCnn, One-Team. All credits to them!
EDIT2: I no longer own this device, so i will leave this thread here for people to use. But don't expect any direct support from me .
What can this tool do?:
Restore phone to Stock(International) Firmware (S048) Marshmallow (Locked & Unlocked bootloader)
Fix Lost or bad Signal / IMEI any software Problem
For who does this work?
Pretty much any Lenovo P2 Variant (Chinese and International)
Phones which can access bootloader(you have to boot into it)
Works on Locked & Unlocked Bootloader
Installation aka. Flashing-Steps
Put your phone into bootloader (which is also fastboot) mode.
Download the folder and unzip it.
Connect your phone to your pc.
Go into the unzipped folder and open "flashall - stock reco.bat"
Wait, for the process to end, your phone will reboot on its own.! A stock lenovo bootlogo will show up !
You can disconnect your phone cable from pc and plug into a wall charger, just to be safe. Once the lockscreen is showing up, you're done.
If you want to flash Custom Roms:
look below:
WHEN MOVING TO CUSTOM ROMS NOW:
1. Boot to twrp. (Make sure it is pietwrp from telegram or the official 3.2.3 or later version)
2. Select WIPE menu option
3. Select data partition
4. Change file format to f2fs or anyother.
5. Go back to Start Menu of TWRP, choose Reboot Menu Option
6.Reboot to Recovery
7. Repeat Steps 2 and 3
8. This time select EXT4 when changing file format
9. Do Step 5 and 6
10. Wipe System,Cache and Dalvik-Cache partitions
( for older twrp versions: 10.1 If you're on official twrp 3.2.3 or lower, you have to flash pietwrp or latest twrp now !)
11. Flash your Custom Rom, Gapps (optional) and latest Magisk(optional)
12. Wipe Cache and Dalvik-Cache
13. Reboot. First Boot might take a few minutes but never longer than 7minutes.
If it takes longer, you're encounter a so called bootloop.
Comment hear if that happens, containing information on your twrp-version, rom, gapps, magisk and mods(if present) you're using.
When you corrupt your internal Storage or geht TWRP Error 1001, Error 7:
1. Repeat steps 2-6
2. Repeat steps 7-8
Download(Official Link)
2nd Link(reuploaded because some couldn't download it from androidfilehost): https://drive.google.com/open?id=1wUOZiTwW8mo0IheAGONyj9-QnjimnY2M
I will help if questions arise.
Credits to One-Team & EypCnn.
Thanks a lot. You literally saved my life!
Works like Magic
Thanks a lot for saving my ass . simplest way to downgrade to mm too. Thanks again
Wait.... downgrade to MM? Does this mean you can regain your signal or did @krishnakoonala get it wrong?
I have a spare P2 lying around that I never used because the IMEI got corrupted and I couldn't flash the bootloader files since I was unlocked.
I assume this wouldn't solve my issue?
eried1 said:
Wait.... downgrade to MM? Does this mean you can regain your signal or did @krishnakoonala get it wrong?
I have a spare P2 lying around that I never used because the IMEI got corrupted and I couldn't flash the bootloader files since I was unlocked.
I assume this wouldn't solve my issue?
Click to expand...
Click to collapse
My p2 was bricked and , stuck in boot loop. I followed the above instructions, 10 mins into it , it booted with mm version, the same version when i bought and booted for 1st time. It was like a new phone to me.
So i assume if one has upgraded to noughat and want to downgrade but is worried he might brick his device, one can take a back up and try this tool. It works flawless.
No harm in trying this one if ur p2 can boot up mate. Give it a shot. Good luck
Cheers
This tool has saved my device from multiple over a span of two years soft bricks. Can confirm it to do wonders.
eried1 said:
Wait.... downgrade to MM? Does this mean you can regain your signal or did @krishnakoonala get it wrong?
I have a spare P2 lying around that I never used because the IMEI got corrupted and I couldn't flash the bootloader files since I was unlocked.
I assume this wouldn't solve my issue?
Click to expand...
Click to collapse
THis will solve your problem , Cheers.
I tried but cannot download it - do you where to find it?
can i flash this without pc?? if yes please tell how
@sm00th4f3 bro, i wanna know, does this tool flashes full ROM including modem files etc, even on unlocked bootloader?
What is the state of bootloader after using this tool?
amansehdav said:
@sm00th4f3 bro, i wanna know, does this tool flashes full ROM including modem files etc, even on unlocked bootloader?
What is the state of bootloader after using this tool?
Click to expand...
Click to collapse
It flashed everything you have when you buy a new phone. And no, it doesn't lock your bootloader.
So you can either :
- keep using MM Stock Rom S048
- Update via ota in System like you normally would do.
- Update till latest Firmware, then flash twrp- and then Custom Rom of your Choice.
Bootloader is in the same state it was before you used this tool.
sm00th4f3 said:
It flashed everything you have when you buy a new phone. And no, it doesn't lock your bootloader.
So you can either :
- keep using MM Stock Rom S048
- Update via ota in System like you normally would do.
- Update till latest Firmware, then flash twrp- and then Custom Rom of your Choice.
Bootloader is in the same state it was before you used this tool.
Click to expand...
Click to collapse
So how does it fixes corrupted modems? it cannot be flashed on unlocked P2 right?
amansehdav said:
So how does it fixes corrupted modems? it cannot be flashed on unlocked P2 right?
Click to expand...
Click to collapse
I literally just answered it above somewhere.
(Literally in thread description)
You can flash it on unlocked bootloader or locked as well.
So many thanks for bringing up tis tool for us!
This thread should be stick as the "New user" thread is, they definitely belong together.
Download source
Thanks guys, if this works I can now revive my phone. But can someone please upload the tool to another place like google drive. From android filehost it will take an eternity to download!
HkQc said:
So many thanks for bringing up tis tool for us!
This thread should be stick as the "New user" thread is, they definitely belong together.
Click to expand...
Click to collapse
I didn't bring it up, i just linked it . All Credits belong to ONE TEAM and EypCnn.
ryd3r89 said:
Thanks guys, if this works I can now revive my phone. But can someone please upload the tool to another place like google drive. From android filehost it will take an eternity to download!
Click to expand...
Click to collapse
Link updated, Cheers
Lavesh05 said:
can i flash this without pc?? if yes please tell how
Click to expand...
Click to collapse
Nah you need a Computer for this.
no signal after using "flashall - stock reco.bat", it finished successfully, but after rom setup still no signal
GPSSlovakia said:
no signal after using "flashall - stock reco.bat", it finished successfully, but after rom setup still no signal
Click to expand...
Click to collapse
If you used some other tool for imei. You are pretty much done for.
Using this tool i can go to MM version and can upgrade to S251. However after installing twrp and flashing custom rom, it goes to bootloader
Hey guys,
Im quite new to android and all that comes with it regarding flashing roms. Now i've had the mi mix 3 cn version since october and been wanting to flash to the global rom ever since. So far i have unlocked the bootloader only on my Mix 3. Now Ive started doing some experimenting with an old one plus 1 device of mine before i fully try it on my mix 3 (and **** it up) and so far been able to unlock bootloader and install twrp. But it seems i cant get through the rooting part because every time i download supersu.zip (on my mac) it doesnt actually show as a zip file. So when i copy/paste it into the oneplus directory and try to install through twrp, basically nothing happens because its not a zip file. Is the solution as simple as: " i should just download the same file using Windows??"
Magisk:
in order to root my my Mix 3 and Oneplus 1 i need to install and run Magisk. But after installing it and opening it, it always says 'Magisk is not installed" and under that "Magisk Manager installed".
Question 1: How to fix this.....
Question 2: Do i need to root my Mix 3 in order to flash the global rom?
Currently running MIUI 10.2 Stable 10.2.2.0(PEECNXM)
Many thanks!
Safari unzips after downloading. You can disable it in the settings I think.
TheArchangel123 said:
Hey guys,
Im quite new to android and all that comes with it regarding flashing roms. Now i've had the mi mix 3 cn version since october and been wanting to flash to the global rom ever since. So far i have unlocked the bootloader only on my Mix 3. Now Ive started doing some experimenting with an old one plus 1 device of mine before i fully try it on my mix 3 (and **** it up) and so far been able to unlock bootloader and install twrp. But it seems i cant get through the rooting part because every time i download supersu.zip (on my mac) it doesnt actually show as a zip file. So when i copy/paste it into the oneplus directory and try to install through twrp, basically nothing happens because its not a zip file. Is the solution as simple as: " i should just download the same file using Windows??"
Magisk:
in order to root my my Mix 3 and Oneplus 1 i need to install and run Magisk. But after installing it and opening it, it always says 'Magisk is not installed" and under that "Magisk Manager installed".
Question 1: How to fix this.....
Question 2: Do i need to root my Mix 3 in order to flash the global rom?
Currently running MIUI 10.2 Stable 10.2.2.0(PEECNXM)
Many thanks!
Click to expand...
Click to collapse
Flash magisk 19 then install the magisk app
TheArchangel123 said:
Hey guys,
Im quite new to android and all that comes with it regarding flashing roms. Now i've had the mi mix 3 cn version since october and been wanting to flash to the global rom ever since. So far i have unlocked the bootloader only on my Mix 3. Now Ive started doing some experimenting with an old one plus 1 device of mine before i fully try it on my mix 3 (and **** it up) and so far been able to unlock bootloader and install twrp. But it seems i cant get through the rooting part because every time i download supersu.zip (on my mac) it doesnt actually show as a zip file. So when i copy/paste it into the oneplus directory and try to install through twrp, basically nothing happens because its not a zip file. Is the solution as simple as: " i should just download the same file using Windows??"
Magisk:
in order to root my my Mix 3 and Oneplus 1 i need to install and run Magisk. But after installing it and opening it, it always says 'Magisk is not installed" and under that "Magisk Manager installed".
Question 1: How to fix this.....
Question 2: Do i need to root my Mix 3 in order to flash the global rom?
Currently running MIUI 10.2 Stable 10.2.2.0(PEECNXM)
Many thanks!
Click to expand...
Click to collapse
You do not need to root your device to flash it to the Global ROM. Unless you need root for something specific, I would suggest forgetting about TWRP and root and using fastboot to flash to the Global ROM. You can find the fastboot flashing guide, here. Click on fastboot, read the instructions, download the correct fastboot image for the Mi Mix 3, unzip it, boot your device into fastboot, connect it via USB to a Windows based machine, and run the flash_all.bat. The device will reboot when finished.
Thanks!
jcsww said:
You do not need to root your device to flash it to the Global ROM. Unless you need root for something specific, I would suggest forgetting about TWRP and root and using fastboot to flash to the Global ROM. You can find the fastboot flashing guide, "https://en.miui.com/a-232.html"]here. Click on fastboot, read the instructions, download the correct fastboot image for the Mi Mix 3, unzip it, boot your device into fastboot, connect it via USB to a Windows based machine, and run the flash_all.bat. The device will reboot when finished.
Click to expand...
Click to collapse
Ok thanks! Will definitly check it out. However i would like to get twrp working as well even just for the sake of it. But every time after i do the "reboot flash recovery rocovery.img" cmd it keeps booting into either the normal OS or into fastboot mode. Ive read about installing the force disable encryption zip file but how do i install that if i cant boot into twrp?
TheArchangel123 said:
Ok thanks! Will definitly check it out. However i would like to get twrp working as well even just for the sake of it. But every time after i do the "reboot flash recovery rocovery.img" cmd it keeps booting into either the normal OS or into fastboot mode. Ive read about installing the force disable encryption zip file but how do i install that if i cant boot into twrp?
Click to expand...
Click to collapse
Which TWRP are you flashing? When I was attempting to root my Chinese Mi Mix 3 running the GLobal Stable ROM, it was very hit and miss getting TWRP to stick. I couldn't get fastboot reboot-recovery to work for me so I had to power the device off after flashing TWRP and then hold Volume Up and Power until it vibrates again to get it into TWRP.
To root in that particular situation (Chinese device/Global ROM), you need to flash this region hiding thing right after you flash root. My device kept bootlooping so I gave up and used fastboot to debloat the ROM, which took a few minutes compared to the almost hour I spent on trying to get TWRP to stick and try to get the device rooted. This is one of my many gripes with Magisk root and how inferior it is to Chainfire's discontinued implementation.
Final stage!
Ok so my last post can be ignored as i was finally able to boot into twrp and also installed magisk so now my device is rooted.
I have now uploaded MIMIX3GLOBAL_V10.2.2.0 PEEMIXM into my phones directory.
Now before i install it thru twrp.... Do i need to wipe/erase/clean my phone first? Or can i just install it without doing so?
Many thanks in advance!
TheArchangel123 said:
Ok so my last post can be ignored as i was finally able to boot into twrp and also installed magisk so now my device is rooted.
I have now uploaded MIMIX3GLOBAL_V10.2.2.0 PEEMIXM into my phones directory.
Now before i install it thru twrp.... Do i need to wipe/erase/clean my phone first? Or can i just install it without doing so?
Many thanks in advance!
Click to expand...
Click to collapse
You can dirty flash it. It's just a minor update. The current beta will bring some new features though, once it is released in the next stable version.
jcsww said:
You can dirty flash it. It's just a minor update. The current beta will bring some new features though, once it is released in the next stable version.
Click to expand...
Click to collapse
Even though my current rom is the chinese version and i want to flash to a global version?
And how about if I flash to Mi Mix 3’s MIUI 10 Global Stable ROM based on Android 9 Pie (MIUI v10.0.11)??
TheArchangel123 said:
Even though my current rom is the chinese version and i want to flash to a global version?
And how about if I flash to Mi Mix 3’s MIUI 10 Global Stable ROM based on Android 9 Pie (MIUI v10.0.11)??
Click to expand...
Click to collapse
You can't dirty flash it...
Wipe in twrp
Install zip in twrp
format data in twrp
Reboot
If you want to root it you'll need the hardware origin magisk module that's somewhere in the mix 3 forums
Region, china?!
So i just clean flashed my phone and then formatted the data and rebooted. After i chose my language i have to choose my region, and the only option it gives me is China!????
TheArchangel123 said:
So i just clean flashed my phone and then formatted the data and rebooted. After i chose my language i have to choose my region, and the only option it gives me is China!????
Click to expand...
Click to collapse
China has the most content, it's not a bad thing. All themes become available etc
Mackay53 said:
China has the most content, it's not a bad thing. All themes become available etc
Click to expand...
Click to collapse
ok fair enough. However I have a situation now... after installing the process goes into a loop after selection china as region. The last small message it gives is "find device quit unexpectedly" and then it loops for 5 minutes untill it boots into recovery mode. Here i can only choose boot system (which will go into the same loop again), wipe data, or connect to MIUI assistent...
What did i do wrong?? Did i flash the wrong rom?
TheArchangel123 said:
So i just clean flashed my phone and then formatted the data and rebooted. After i chose my language i have to choose my region, and the only option it gives me is China!????
Click to expand...
Click to collapse
When cross-flashing, clean/factory reset is always the way to go. With TWRP though, there seems to be some sort of region options not changing issue. There are a few ways to work around it I personally never bothered with, but I have flashed two Chinese devices via fastboot with the Global Stable ROM and haven't ran into the region issue at all.
TheArchangel123 said:
ok fair enough. However I have a situation now... after installing the process goes into a loop after selection china as region. The last small message it gives is "find device quit unexpectedly" and then it loops for 5 minutes untill it boots into recovery mode. Here i can only choose boot system (which will go into the same loop again), wipe data, or connect to MIUI assistent...
What did i do wrong?? Did i flash the wrong rom?
Click to expand...
Click to collapse
Google miui region fix, download and flash and it should sort it
Mackay53 said:
Google miui region fix, download and flash and it should sort it
Click to expand...
Click to collapse
ok got the miui region fix. But how do i flash it... my phone wont boot into twrp anymore. Im also not sure how to get into fastboot either because it doesnt seem to connect if i type in the commands in cmd
TheArchangel123 said:
ok got the miui region fix. But how do i flash it... my phone wont boot into twrp anymore. Im also not sure how to get into fastboot either because it doesnt seem to connect if i type in the commands in cmd
Click to expand...
Click to collapse
Fastboot is the bootloader. Once you boot your device into the bootloader (Volume Down + Power), you can use ADB through the command prompt to flash TWRP or just flash the Global ROM properly. This thread on it is still very relevant and useful.
Got it!
jcsww said:
Fastboot is the bootloader. Once you boot your device into the bootloader (Volume Down + Power), you can use ADB through the command prompt to flash TWRP or just flash the Global ROM properly. This thread on it is still very relevant and useful.
Click to expand...
Click to collapse
Thanks guys, after a few long days ive finally succeeded to flash a global rom for the first time. Nxt step, try to get all my apps/data etc back. Hopefully i made a correct back up...
So I am not an entire noob when it comes to these things, I've flashed ROMs on phones for 8 years now, but this Moto G7 Power screwed me up good.
I tried installing CrDroid from this post. I didn't even notice the A/B part at first, I went through all the usual steps, I booted TWRP, then flashed it, rebooted into the installed TWRP, flashed CrDroid, GApps and Magisk and rebooted, hoping to start Android up. At that part it all screwed up. The phone didn't boot AT ALL, and after a while I found that blankflash zip file and managed to get into the bootloader again. The only thing I can do now is boot into TWRP, not flash, and when I boot, the touchscreen does not work.
So, where do I go from here? I now only have an unlocked bootloader to play with. What are the exact steps to flash the firmware? Why do I need to flash firmware to slot A anyway? Isn't or wasn't there firmware out of the box on the device? The guides for this phone are vague and people write really short and rambling sentences in the steps and mention certain files out of the blue without explanation or download link.
1 - Which firmware file do I need? I have an XT1955-4 bought in a Dutch shop called Belsimpel with no sim. I assume it's an international variant. Here is a download list of all the firmware variants, but how do I know which one to pick? Will it wipe things like IMEI data? The box says the type is M3C94, and it seems to be this international variant.
2 - In the bootloader, what commands do I need to put into adb when I want to flash the firmware to partition A?
3 - When I boot into TWRP, my touchscreen does not work, so how can I even use it?
4 - The 'guide' in the CrDroid thread suddenly mentions copypartitions.zip. What is that file, and why do I need to flash it? It says I have to flash it in Slot A. Does TWRP give options to switch slots? I wish I could check but since my touch screen doesn't work in TWRP..
5 - During the actual ROM install part, the guide says Flash ROM.zip + TWRP_installer/boot.img ramdisk method Why do I need to install TWRP again? And what is the ramdisk method? How do you do that?
Can someone please explain in detail step by step what I need to do?
kerelberel said:
So I am not an entire noob when it comes to these things, I've flashed ROMs on phones for 8 years now, but this Moto G7 Power screwed me up good.
I tried installing CrDroid from this post. I didn't even notice the A/B part at first, I went through all the usual steps, I booted TWRP, then flashed it, rebooted into the installed TWRP, flashed CrDroid, GApps and Magisk and rebooted, hoping to start Android up. At that part it all screwed up. The phone didn't boot AT ALL, and after a while I found that blankflash zip file and managed to get into the bootloader again. The only thing I can do now is boot into TWRP, not flash, and when I boot, the touchscreen does not work.
So, where do I go from here? I now only have an unlocked bootloader to play with. What are the exact steps to flash the firmware? Why do I need to flash firmware to slot A anyway? Isn't or wasn't there firmware out of the box on the device? The guides for this phone are vague and people write really short and rambling sentences in the steps and mention certain files out of the blue without explanation or download link.
1 - Which firmware file do I need? I have an XT1955-4 bought in a Dutch shop called Belsimpel with no sim. I assume it's an international variant. Here is a download list of all the firmware variants, but how do I know which one to pick? Will it wipe things like IMEI data? The box says the type is M3C94, and it seems to be this international variant.
2 - In the bootloader, what commands do I need to put into adb when I want to flash the firmware to partition A?
3 - When I boot into TWRP, my touchscreen does not work, so how can I even use it?
4 - The 'guide' in the CrDroid thread suddenly mentions copypartitions.zip. What is that file, where do I download it, and why do I need to flash it? It says I have to flash it in Slot A. Does TWRP give options to switch slots?
5 - During the actual ROM install part, the guide says Flash ROM.zip + TWRP_installer/boot.img ramdisk method Why do I need to install TWRP again? And what is the ramdisk method? How do you do that?
Can someone please explain in detail step by step what I need to do?
Click to expand...
Click to collapse
1. go to settings - system - about phone check build number, this is the firmware you'll need
2. there's a thread here regarding that matter check again
3. I'm not aware of this issue
4. you'll only need to flash that file once coming from stock rom - https://androidfilehost.com/?fid=4349826312261636295
5. because it be overwritten by lineage recovery.
ramdisk method is just another way of installing twrp back when we still dont have the installer zip
vinoxflame said:
1. go to settings - system - about phone check build number, this is the firmware you'll need
2. there's a thread here regarding that matter check again
3. I'm not aware of this issue
4. you'll only need to flash that file once coming from stock rom - https://androidfilehost.com/?fid=4349826312261636295
5. because it be overwritten by lineage recovery.
ramdisk method is just another way of installing twrp back when we still dont have the installer zip
Click to expand...
Click to collapse
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
then try another version of twrp or the unofficial orangefox recovery for our device
vinoxflame said:
then try another version of twrp or the unofficial orangefox recovery for our device
Click to expand...
Click to collapse
I tried an older version of TWRP which didn't work either. I am not aware of Orangefox, but I don't see any mention, official or unofficial for the G7 Power. There's no mention in the G7 Power forum either.
kerelberel said:
I tried an older version of TWRP which didn't work either. I am not aware of Orangefox, but I don't see any mention, official or unofficial for the G7 Power. There's no mention in the G7 Power forum either.
Click to expand...
Click to collapse
it's on the telegram group
vinoxflame said:
it's on the telegram group
Click to expand...
Click to collapse
No it is not. There's no mention of G7 Power in the search results. Only E5.
kerelberel said:
No it is not. There's no mention of G7 Power in the search results. Only E5.
Click to expand...
Click to collapse
deleted
vinoxflame said:
https://t.me/mG7Power
tell me if it is not!!!!
Click to expand...
Click to collapse
From the desktop search in this one I couldn't find it: https://t.me/OrangeFoxRecovery I didn't know there was a separate chat for each device. But thanks.
FWIW when this happened to me I did the blankflash thing to get it back to bootloader. Then I used the LMSA tool from Motorola to do a rescue/restore.
I also used LMSA to force the update to the most recent security update. In general, it seems a very useful utility.
https://www.motorola.com/us/lenovo-motorola-smart-assistant
I had this issue after blankflashing this temperamental device out of a brick. While in twrp you can do "adb shell" then "twrp install /path/to/zip" I think this has to do with new twrp versions on older firmwares
kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
When i had this issue go reboot fastboot
then fastboot boot recovery.img or twrp as your boot img do what you need to do just dont flash it to boot only boot from it so you preserve your real boot should fix the touch screen part only time i had prob like this is when i flashed twrp to recovery without disabling dm verity etc. But I cant even get a stock OTA since I flashed twrp as recovery nor can I find a RETUS stock recovery.img so far if i had that I can update and keep magisk etc, then reflash twrp when im done.
---------- Post added at 06:06 PM ---------- Previous post was at 05:58 PM ----------
kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
When i had this issue go reboot fastboot
then fastboot boot recovery.img or twrp as your boot img do what you need to do just dont flash it to boot only boot from it so you preserve your real boot should fix the touch screen part only time i had prob like this is when i flashed twrp to recovery without disabling dm verity etc. But I cant even get a stock OTA since I flashed twrp as recovery nor can I find a RETUS stock recovery.img so far if i had that I can update and keep magisk etc, then reflash twrp when im done. The latest stock RETUS build i can find is here https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip but if i do that i will lose all my apps AGAIN etc I am trying to just get the stock recovery img from previous version so I can install the ota in magisk you just tap uninstall tap restore images to get stock boot as well then ota should work once its done go back into magisk and install to inactive slot but you will or could need TWRP A/B retention script so that you keep it even after ota...which you will first go in magisk tap uninstall restore images, but must have stock recovery not twrp installed at this time either from what i can tell, once ota is successful install the TWRP A/B Retention script but do this before you install magisk to inactive slot from magisk manager after that it should work. But I cannot locate a stock recovery.img thus far.... and I dont wanna redownload my apps right now, so I may just wait til I see a rom i really think ill like and say screw it.
kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
I also installed crDroid and after that twrp-3.3.1-2-ocean.img was not responding to touch, but twrp-3.3.1-0-ocean.img works. (btw I was doing a fastboot -w in between.)
Edit:
Ah nevermind, I have it constantly when installed, with both versions.
s33b said:
I also installed crDroid and after that twrp-3.3.1-2-ocean.img was not responding to touch, but twrp-3.3.1-0-ocean.img works. (btw I was doing a fastboot -w in between.)
Edit:
Ah nevermind, I have it constantly when installed, with both versions.
Click to expand...
Click to collapse
I've flashed another stock rom (https://forum.xda-developers.com/g7-power/how-to/guide-moto-g7-power-supra-flash-to-t3927138) and it worked with twrp-3.3.1-0-ocean.img not with the newest.
kerelberel said:
2 - In the bootloader, what commands do I need to put into adb when I want to flash the firmware to partition A?
Click to expand...
Click to collapse
You use fastboot commands in the bootloader.
The firmware contains a flash file with all fastboot commands you'll need.
kerelberel said:
3 - When I boot into TWRP, my touchscreen does not work, so how can I even use it?
Click to expand...
Click to collapse
TWRP has adb enabled by default. So instead of TWRP you can use
Code:
abd shell twrp --help
So you can use the basic functions like backup, install, and so on.
I had the same issue...
I'm not sure everyone is experiencing the same issue here, but I've been dealing with that exact problem the entire time I've had this phone. While this work around won't work every time, it will eventually work (for me within 3 tries). It doesn't matter if your "fastboot boot twrp.img" or running an installed version, all are the same. Even the latest 3.4.0.0.
As soon as you start recovery, start tapping the area of the screen where the "Advanced button" is in recovery. I mean tap as fast as you can, use two fingers if you need to. If it doesn't work right away, "adb reboot bootloader" and try again. I can get this to work within 3 tries. Its sucks and its stupid, but it works.
TheGuysGuysGuy said:
I'm not sure everyone is experiencing the same issue here, but I've been dealing with that exact problem the entire time I've had this phone. While this work around won't work every time, it will eventually work (for me within 3 tries). It doesn't matter if your "fastboot boot twrp.img" or running an installed version, all are the same. Even the latest 3.4.0.0.
As soon as you start recovery, start tapping the area of the screen where the "Advanced button" is in recovery. I mean tap as fast as you can, use two fingers if you need to. If it doesn't work right away, "adb reboot bootloader" and try again. I can get this to work within 3 tries. Its sucks and its stupid, but it works.
Click to expand...
Click to collapse
I getba link to one that works for u. https://t.me/CustoKernal_JavaShin_Mods/565. Fastboot boot (name of recovery)
roadkill42 said:
I getba link to one that works for u. https://t.me/CustoKernal_JavaShin_Mods/565. Fastboot boot (name of recovery)
Click to expand...
Click to collapse
Again not everyone is experiencing this same issue. A custom kernel isn't going to help when its incompatible with my ROM. My stupid workaround works for "No Touch Screen Response" in TWRP as well as OrangeFox. Its happened to me in both. Happily cruising along on Paranoid Android Quartz.
TheGuysGuysGuy said:
Again not everyone is experiencing this same issue. A custom kernel isn't going to help when its incompatible with my ROM. My stupid workaround works for "No Touch Screen Response" in TWRP as well as OrangeFox. Its happened to me in both. Happily cruising along on Paranoid Android Quartz.
Click to expand...
Click to collapse
The problem with the touch is the right driver needs to b installed that kernel I shared makes it work and stick I'm on it now go to tellagram group Moto g7 power support group both twrp and ofox there that works not the one from twrp it's self and the twrp there has some other features that one from official one has that don't work
This boot image gave me a touchscreen and allowed me to flash a regular twrp: hxxps://f.emvn.me/android-roms-and-stuff/twrp.3.4-kakarot.boot.img
Thanks to whoever made it.
So I was using PixelExperiece ROM and decided to switch back to MIUI. I downloaded latest fastboot ROM from MIUI website, Flashed it using MI FLash Tool.
While flashing my phone displayed "System has been destroyed" in between. And MIFlash tool showed some error.
So, I tried flashing again and MIFlash tool now said Bootloader was locked. (Because lock_all_and_install was selected previously).
Therefore I downloaded MI Bootloader unlock tool. (The phone still shows "System has been destroyed"). Ignoring that warning, I went to fastboot and ran unlocker. To my surprise, after unlocking was complete and phone restarted it booted into MIUI. I thought "System has been destroyed" problem would be solved. But later I realised, my camera was not focusing on close range object. It wasnt focusing at all. Then after playing around to check everything I found out, my camera was not focusing, gyro was not working (No auto rotate and noting in CIT test) neither was my compass working. So there is some kind of problem with my hardware now.
Later I tried flashing same fastboot ROM again hoping it will install fully now and not ending up in "System has been destroyed" error. And I also chose option to not lock bootloader while flashing in MI Flash tool. This time the phone did started on to MIUI but in MI Flash tool it kept showing flashing as status. Even after I disconnected my phone USB cable it said flashing. And those hardware things are still not working.
While using PixelExperience I did changed SELinux mode to make ANXCamera work. Would it (SELinux mode) be a problem for hardware not working? Or is there any other problem?
Thanks in advance for any help.
DragonSlayer7# said:
So I was using PixelExperiece ROM and decided to switch back to MIUI. I downloaded latest recovery ROM from MIUI website, Flashed it using MI FLash Tool.
While flashing my phone displayed "System has been destroyed" in between. And MIFlash tool showed some error.
So, I tried flashing again and MIFlash tool now said Bootloader was locked. (Because lock_all_and_install was selected previously).
Therefore I downloaded MI Bootloader unlock tool. (The phone still shows "System has been destroyed"). Ignoring that warning, I went to fastboot and ran unlocker. To my surprise, after unlocking was complete and phone restarted it booted into MIUI. I thought "System has been destroyed" problem would be solved. But later I realised, my camera was not focusing on close range object. It wasnt focusing at all. Then after playing around to check everything I found out, my camera was not focusing, gyro was not working (No auto rotate and noting in CIT test) neither was my compass working. So there is some kind of problem with my hardware now.
Later I tried flashing same recovery ROM again hoping it will install fully now and not ending up in "System has been destroyed" error. And I also chose option to not lock bootloader while flashing in MI Flash tool. This time the phone did started on to MIUI but in MI Flash tool it kept showing flashing as status. Even after I disconnected my phone USB cable it said flashing. And those hardware things are still not working.
While using PixelExperience I did changed SELinux mode to make ANXCamera work. Would it (SELinux mode) be a problem for hardware not working? Or is there any other problem?
Thanks in advance for any help.
Click to expand...
Click to collapse
Wait what u said u flashed recovery rom via mi flash ? U have to flash persist.img (u will find this in your fastboot rom) from custom recovery in system/persist partition. Thats it.
hackermssharma said:
Wait what u said u flashed recovery rom via mi flash ? U have to flash persist.img (u will find this in your fastboot rom) from custom recovery in system/persist partition. Thats it.
Click to expand...
Click to collapse
Im sorry, my mistake. I flased fastboot ROM only. Not recovery. MIFlash tool won't allow you to flash recovery ROM at all.
DragonSlayer7# said:
Im sorry, my mistake. I flased fastboot ROM only. Not recovery. MIFlash tool won't allow you to flash recovery ROM at all.
Click to expand...
Click to collapse
Mmmm... No need to worry extract persist.img from fastboot rom folder and flash via OF recovery in system/persist partition. Then boot u get all your sensors back.
hackermssharma said:
Mmmm... No need to worry extract persist.img from fastboot rom folder and flash via OF recovery in system/persist partition. Then boot u get all your sensors back.
Click to expand...
Click to collapse
Instead of fixing existing sensors, flashing persist.img screwed up my wifi and hotspot. After flashing whole fastboot ROM againg they are now working. But other sensors are still not working.
DragonSlayer7# said:
Instead of fixing existing sensors, flashing persist.img screwed up my wifi and hotspot. After flashing whole fastboot ROM againg they are now working. But other sensors are still not working.
Click to expand...
Click to collapse
Really? I mean i used same method last time for my sensors to work again and that worked for me. Next workaround is u should clean flash miui 10 fastboot rom then update to miui 11 using updater app. Hope it should work for u.
flashing persist.img worked for me.
hackermssharma said:
Really? I mean i used same method last time for my sensors to work again and that worked for me. Next workaround is u should clean flash miui 10 fastboot rom then update to miui 11 using updater app. Hope it should work for u.
Click to expand...
Click to collapse
I flashed same MIUI fastboot ROM again, and miraculously all sensors started working again.:good::good:
DragonSlayer7# said:
I flashed same MIUI fastboot ROM again, and miraculously all sensors started working again.:good::good:
Click to expand...
Click to collapse
Great ??
Sensors
DragonSlayer7# said:
I flashed same MIUI fastboot ROM again, and miraculously all sensors started working again.:good::good:
Click to expand...
Click to collapse
I am also facing the same problem (sensors are not working) after i switched back from Pixel Experience to MIUI 11. Though i read all replies i did get some ideas but not clearly. Can you please little explain how to do it. Step by step method explanation will be much appriciated !! (only installation part, i have all required software and ROM ready for fastboot) I am just not clear how fix my sensors.
--------------------------------------------------------------
EDIT: No need guide. I understood how to do it. Some the things mentioned in reply were new for me so it was hard time for me to understand?.. I am new to Redmi phone
Widevine L1
hackermssharma said:
Mmmm... No need to worry extract persist.img from fastboot rom folder and flash via OF recovery in system/persist partition. Then boot u get all your sensors back.
Click to expand...
Click to collapse
Well i just got to know that by flashing 'persist.img' from a recovery will void Widevine L1 certification (Netflix with no HD, also other HD content streaming platform that requires Widevine L1 certification). I heard it will be permanent warrenty void and i don't know it can be fixed or not.
Azhar001 said:
I am also facing the same problem (sensors are not working) after i switched back from Pixel Experience to MIUI 11. Though i read all replies i did get some ideas but not clearly. Can you please little explain how to do it. Step by step method explanation will be much appriciated !! (only installation part, i have all required software and ROM ready for fastboot) I am just not clear how fix my sensors.
--------------------------------------------------------------
EDIT: No need guide. I understood how to do it. Some the things mentioned in reply were new for me so it was hard time for me to understand?.. I am new to Redmi phone
Click to expand...
Click to collapse
This persist.img thing might work for you or might not.
The full proof way is to reinstall Pixel Experience (Android 10) so that you get your sensors up and running again, then flash MIUI 10 and upgrade to MIUI 11 using system updater app.
Azhar001 said:
Well i just got to know that by flashing 'persist.img' from a recovery will void Widevine L1 certification (Netflix with no HD, also other HD content streaming platform that requires Widevine L1 certification). I heard it will be permanent warrenty void and i don't know it can be fixed or not.
Click to expand...
Click to collapse
Its fine. Just install Netflix from ApkMirror (not from Google Play) and it should work.
Azhar001 said:
Well i just got to know that by flashing 'persist.img' from a recovery will void Widevine L1 certification (Netflix with no HD, also other HD content streaming platform that requires Widevine L1 certification). I heard it will be permanent warrenty void and i don't know it can be fixed or not.
Click to expand...
Click to collapse
Also if you are coming back to MIUI, use this method...
DragonSlayer7# said:
This persist.img thing might work for you or might not.
The full proof way is to reinstall Pixel Experience (Android 10) so that you get your sensors up and running again, then flash MIUI 10 and upgrade to MIUI 11 using system updater app.
Click to expand...
Click to collapse
DragonSlayer7# said:
This persist.img thing might work for you or might not.
The full proof way is to reinstall Pixel Experience (Android 10) so that you get your sensors up and running again, then flash MIUI 10 and upgrade to MIUI 11 using system updater app.
Click to expand...
Click to collapse
should i flash MIUI 10 using custom recovery or fastboot after reinstalling Pixel Experience ?
Azhar001 said:
should i flash MIUI 10 using custom recovery or fastboot after reinstalling Pixel Experience ?
Click to expand...
Click to collapse
Fastboot ROM using MIFlashTool
DragonSlayer7# said:
Fastboot ROM using MIFlashTool
Click to expand...
Click to collapse
okay, i willl let you know if it works
I think you should try reflashing the stock firmware using the Mi Flash and select wipe data option.
Sent from my Redmi Note 7 Pro using Tapatalk
DragonSlayer7# said:
Fastboot ROM using MIFlashTool
Click to expand...
Click to collapse
I got all the sensors back again, everything working fine.
Here is what is did (using PC):
1) i installed Pixek Experience ROM (Android 10) using ADB Fastboot method.
Pros: Every sensors started to work, back to normal.
Cons: None i noticed.
2) Then i turn off the phone and entered into fastboot mode
3) I flashed MIUI 10 fastboot ROM using MIFlash Tool. Though i didn't get the "Success" message on MIFlash Tool but phone booted itself (did show MIUI 10 during boot up, and Set Up screen was appearing) so i assumed flashing was complete. Then i unplugged phone from USB cable.
After setup,
Pros: Every sensors was working perfectly fine.
Cons: None i noticed.
4) i updated from MIUI 10 to MIUI 11 using System update on phone. Now i am on MIUI 11 and everything works FINE!!
So what i found is there is some problem with MIUI 11 fastboot ROM itself. Directly flashing MIUI 11 fastboot ROM is the reason sensors stops working!!
Azhar001 said:
I got all the sensors back again, everything working fine.
Here is what is did (using PC):
1) i installed Pixek Experience ROM (Android 10) using ADB Fastboot method.
Pros: Every sensors started to work, back to normal.
Cons: None i noticed.
2) Then i turn off the phone and entered into fastboot mode
3) I flashed MIUI 10 fastboot ROM using MIFlash Tool. Though i didn't get the "Success" message on MIFlash Tool but phone booted itself (did show MIUI 10 during boot up, and Set Up screen was appearing) so i assumed flashing was complete. Then i unplugged phone from USB cable.
After setup,
Pros: Every sensors was working perfectly fine.
Cons: None i noticed.
4) i updated from MIUI 10 to MIUI 11 using System update on phone. Now i am on MIUI 11 and everything works FINE!!
So what i found is there is some problem with MIUI 11 fastboot ROM itself. Directly flashing MIUI 11 fastboot ROM is the reason sensors stops working!!
Click to expand...
Click to collapse
Yes, its kernel problem. It happens if you are flashing MIUI 11 based on Android Pie from any AOSP based ROM running Android 10.