Hi,
Recently after i dirty flashed Evolution X rom update, i started facing this issue, where i have to reboot my phone each time i want to charge my phone. To fix this i tried clean flashing the ROM and even tried formatting my device but the issue did not resolve.
EDIT:
Even flashing stock rom via ADB did not solve the issue.
Also, not able to transfer files via USB. After attaching the USB, is keeps connecting and disconnecting repeatedly.
Also i see this error repeatedly in TWRP
Code:
E:recv error on uevent
Googling this found some post saying that this error can be ignored. But not sure if the two issues are related or not.
Please help.
Thanks
Same problem. TWRP has that error too, charging is faulty, and connecting to PC is just connect-disconnect cycle. Hope someone can help us
I think this usually happens when partition is resized. Hopefully the following steps would resolve your issue.
1 Install stock ROM using Mi Flash tool cleaning everything and lock the bootloader. After install allow the phone to boot/get encrypted.
2 When phone reboots, unlock the bootloader using Mi tool.
3 Flash TWRP and then flash whatever you want.
wiley.devil said:
I think this usually happens when partition is resized. Hopefully the following steps would resolve your issue.
1 Install stock ROM using Mi Flash tool cleaning everything and lock the bootloader. After install allow the phone to boot/get encrypted.
2 When phone reboots, unlock the bootloader using Mi tool.
3 Flash TWRP and then flash whatever you want.
Click to expand...
Click to collapse
I'll try this. Hopefully it works
Try performing following steps:
1. Go to recovery and wipe cache, system, & data.
2. Then go to repair and repair system.
3. Now try to flashing rom.
wiley.devil said:
I think this usually happens when partition is resized. Hopefully the following steps would resolve your issue.
1 Install stock ROM using Mi Flash tool cleaning everything and lock the bootloader. After install allow the phone to boot/get encrypted.
2 When phone reboots, unlock the bootloader using Mi tool.
3 Flash TWRP and then flash whatever you want.
Click to expand...
Click to collapse
I tried this method first time, it failed. The flashing and locking of bootloader via Mi Flash Tool went well, locked then unlocked the bootloader, flashing TWRP went well (new version btw, 3.4.0.0), flashing of custom rom went well, but the error is still in TWRP. The only difference it made was my data was encrypted when booting up to TWRP.
Tried it the second time but this time, I logged out my Mi Account before flashing TWRP and I flashed of DFE before flashing a Custom ROM. Now it doesn't have the error. Not sure if this fixed the problem but I'm gonna see if it doesn't return. Thanks!
---------- Post added at 04:34 PM ---------- Previous post was at 04:34 PM ----------
gr8guzzler said:
Try performing following steps:
1. Go to recovery and wipe cache, system, & data.
2. Then go to repair and repair system.
3. Now try to flashing rom.
Click to expand...
Click to collapse
Saw this in another thread, did it, sadly the error still persist.
my phone does not load with this same problem any solution ??? I ask for help from the dev masters.
Related
My Moto E Hangs when I try to boot a TWRP image
Attempted procedure:
(After booting into stock fastboot)
Code:
fastboot boot twrp-2.7.1.0-condor.img
A reboot to that TWRP was expected instead. But it freezes on bootloader.
TWRP used on the attempt:
dl.twrp.me/condor/twrp-2.7.1.0-condor.img.html
I don't want to flash a different recovery or anything else, just a clean root.
Moto E XT1025 DTV Dual BR
4.4.4
21.12.40.condor_retbr_tv_ds.retvr.en.BR.retbr
LucasBS1 said:
My Moto E Hangs when I try to boot a TWRP image
Attempted procedure:
(After booting into stock fastboot)
Code:
fastboot boot twrp-2.7.1.0-condor.img
A reboot to that TWRP was expected instead. But it freezes on bootloader.
TWRP used on the attempt:
dl.twrp.me/condor/twrp-2.7.1.0-condor.img.html
I don't want to flash a different recovery or anything else, just a clean root.
Moto E XT1025 DTV Dual BR
4.4.4
21.12.40.condor_retbr_tv_ds.retvr.en.BR.retbr
Click to expand...
Click to collapse
Sometimes booting recovery doesn't work...You will have to flash it. Perhaps you can flash the stock recovery after successful root? though i am not sure that will work
Also try booting into CWM
Tried the same method with CWM.img
Same result: fastboot frozen (volume buttons not responsive, and PC no longer sends commands)
To flash the stock recovery I would need to back it up first
But guess what's needed to backup ?
Yes, a temporary flashed bootloader with ZIP support
Would you know someone, who knows someone, who knows an master from MTI or Hogwarts or Narnia that knows an alternative ?
I would flash a mod right away if I could backup the original first...
(Unless, as I don't know exactly how this works, the ROM might come with the bootloader (?) Because the stock ROM I can download easily anywhere (already did))
LucasBS1 said:
Tried the same method with CWM.img
Same result: fastboot frozen (volume buttons not responsive, and PC no longer sends commands)
To flash the stock recovery I would need to back it up first
But guess what's needed to backup ?
Yes, a temporary flashed bootloader with ZIP support
Would you know someone, who knows someone, who knows an master from MTI or Hogwarts or Narnia that knows an alternative ?
I would flash a mod right away if I could backup the original first...
(Unless, as I don't know exactly how this works, the ROM might come with the bootloader (?) Because the stock ROM I can download easily anywhere (already did))
Click to expand...
Click to collapse
Hi,
Did you managed it to work? I have exactly the same problem. If I even flash twrp or cwm I still can't boot into it, there is only "no command" message.
I can't get any help anywhere, it makes me crazy. Do you have any custom recovery that worked for you after flashing?? I'm even starting to think that my device is broken somehow.
giaur said:
Hi,
Did you managed it to work? I have exactly the same problem. If I even flash twrp or cwm I still can't boot into it, there is only "no command" message.
I can't get any help anywhere, it makes me crazy. Do you have any custom recovery that worked for you after flashing?? I'm even starting to think that my device is broken somehow.
Click to expand...
Click to collapse
I did NOT flash the recovery yet
I'm trying to run the recovery without flashing it, to avoid problems like yours
You said you flashed both CWM and TWRP ?
And Neither one of them worked ?
I'm screwed too, then...
:crying:
See if you can find the stock recovery somewhere
And NOT here
This forum is not good for it
It's too much phone specific... too narrow... and we get no attention; specially with our "not-mainstream" phone
Generic instruction could work
If you take any action, or find any forum you find helpful, let me know
@giaur @LucasBS1
I too have tried booting the recovery ,but it doesn't work. You will have to flash it
if you are seeing 'no command' message it means that you still have stock recovery and the custom recovery wasn't flashed successfully.
try this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-2-0-touch-recovery-t2971601
or this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-6-0-touch-recovery-t3100879
LucasBS1 said:
I did NOT flash the recovery yet
I'm trying to run the recovery without flashing it, to avoid problems like yours
You said you flashed both CWM and TWRP ?
And Neither one of them worked ?
I'm screwed too, then...
:crying:
See if you can find the stock recovery somewhere
And NOT here
This forum is not good for it
It's too much phone specific... too narrow... and we get no attention; specially with our "not-mainstream" phone
Generic instruction could work
If you take any action, or find any forum you find helpful, let me know
Click to expand...
Click to collapse
None of them worked. I'm going to resign, because there is nothing I can do. Seems you have exactly the same problem as me. What I tried:
- fastboot boot recovery.img. Phone hangs on bootlogo
- flash recovery, then use go to recovery option in fastboot menu. In this case, 2 possibilities: with usb cable connected, it boots normally to system, not to recovery. With usb cable disconnected, screen goes black and phone looks like powered off. You will need to power it on and it will boot to system.
- On running system with usb debugging enabled. If you type "adb reboot recovery", you will end with dead robot and "no command" error. You can however press VolUP +Power on this screen and you will see Android 3e recovery.
If you have the same problem as me, you are completly lost and it's impossible to intall recovery on your device. I'm close to resign and say "**** this ****ty phone" because (as you already mentioned), there is no any attention on my questions, twrp support was dropped long time ago etc.
Flashing recovery should not wipe your data, so once you try to flash twrp or cwm, please let me know about your results. I'm sure I will never able to solve this problem, but I will feel better knowing that I'm not alone whit it
---------- Post added at 06:05 PM ---------- Previous post was at 06:00 PM ----------
mepsilon2 said:
@giaur @LucasBS1
I too have tried booting the recovery ,but it doesn't work. You will have to flash it
if you are seeing 'no command' message it means that you still have stock recovery and the custom recovery wasn't flashed successfully.
try this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-2-0-touch-recovery-t2971601
or this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-6-0-touch-recovery-t3100879
Click to expand...
Click to collapse
Still the same, I'm on stock recovery. In console, no errors:
Code:
[email protected]:~/android/DO_MOTOROLI/twrp/2.8.5$ fastboot flash recovery twrp2.8.5.0-recovery.img
target reported max download size of 299892736 bytes
sending 'recovery' (9046 KB)...
OKAY [ 0.312s]
writing 'recovery'...
OKAY [ 0.860s]
finished. total time: 1.172s
But "adb reboot recovery" - "No command". Damn it...
---------- Post added at 06:26 PM ---------- Previous post was at 06:05 PM ----------
Ok, I'm finished. It's not possible. F U C K Motorola and good night. My advice: don't waste your time if you have the same problem. You will get nothing, except wasted time. It's good that it's not my phone (I own OnePlus One). But I was asked to install CM12.1 on my friend's phone. It's impossible, so I will need to tell him I was failed with that.
mepsilon2 said:
@giaur @LucasBS1
I too have tried booting the recovery ,but it doesn't work. You will have to flash it
if you are seeing 'no command' message it means that you still have stock recovery and the custom recovery wasn't flashed successfully.
try this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-2-0-touch-recovery-t2971601
or this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-6-0-touch-recovery-t3100879
Click to expand...
Click to collapse
I see people complaining about bugs or not-working features on the first link
Are you sure it's safe ?
It's not the official TWRP (apparently)
When I google for this bootloader the official page shows version 2.7.1.0
Whereas on your second link they are on the 2.8.2.0
Which one should I trust ?
And to anyone who might answer:
Trough PC is the only/safest way to flash these recoveries ?
Seeing giaur on that situation puts me stepping back...
LucasBS1 said:
I see people complaining about bugs or not-working features on the first link
Are you sure it's safe ?
It's not the official TWRP (apparently)
When I google for this bootloader the official page shows version 2.7.1.0
Whereas on your second link they are on the 2.8.2.0
Which one should I trust ?
And to anyone who might answer:
Trough PC is the only/safest way to flash these recoveries ?
Click to expand...
Click to collapse
I tested both: latest official 2.7 and linked 2.8. So they are safe. Official support for Moto E was dropped long time ago.
giaur said:
I tested both: latest official 2.7 and linked 2.8. So they are safe. Official support for Moto E was dropped long time ago.
Click to expand...
Click to collapse
Cool
Regarding to safety
Should I flash CWM or TWRP ? Why ?
Regarding the method
Flash through usb->Fastboot or through Apk (like CWM)
Or a third method ?
And why
Between TWRP 2.7 and 2.8, which one is safer ?
And of course...why ?
And a last question, before I leave you guys alone:
Did you manage to root the phone, despite the poblems occurring to you, giaur ?
Once you succesfuly flash twrp, you need to flash supersu then and you are rooted. If you don't have your current system rooted, the only way to flash custom recovery is to flash via fastboot. TWRP is recommended, because it's way better
I can't say anything more, because my moto e is not flashable, so I can't replace stock recovery.
Yo !
Flashed TWRP
But wiped things I shouldnt
How to put the ROM back via USB ?
EDIT:
NEVERMIND
Found how to use SD to do that
giaur said:
Once you succesfuly flash twrp, you need to flash supersu then and you are rooted. If you don't have your current system rooted, the only way to flash custom recovery is to flash via fastboot. TWRP is recommended, because it's way better
I can't say anything more, because my moto e is not flashable, so I can't replace stock recovery.
Click to expand...
Click to collapse
I was also struggling a lot many days into getting twrp and cw loaded on to a Moto E. The problem was that I was pressing the Power button to activate the recovery menu and that will not activate the recovery option. You got to press the UP button instead of power after executing
Code:
fastboot.exe flash recovery twrp-2.8.1.0-condor.img
. This is quite counter intuitive but described well in most posts, but as experts we assume up button is to go up the menu.
Sunish Issac
Hi my friends.
this is my story :
my phone is Redmi note 3 pro (qualqomm)
I got permissions for unlocking a week ago.
then i tried xiaomi website unlock method but it stopped at 50% and gave me couldn't verify device (different account) error.
my rom is global (MIUI 8) . then i tried to flash dev rom with updater app but it gave me couldn't verify update package error. i cleared updater data and tried again but same error.
in next step i tried mi pc suite to flash but no success.
then i used fastboot mode and mi flash and i got locked bootloader error.
then i used EDL mode to flash but in mi flash i got hello package error. (object reference not set to an instance of an object)
i completely confused . i tried all methods and read many fix like login in i.mi.com and other method that people fixed their problem but all of them not fix mine.
i read some threads about flashing twrp and root without unlocking bootloader but all of them need flashing dev rom and i can't flash.
can anyone help me?
x23are said:
Hi my friends.
this is my story :
my phone is Redmi note 3 pro (qualqomm)
I got permissions for unlocking a week ago.
then i tried xiaomi website unlock method but it stopped at 50% and gave me couldn't verify device (different account) error.
my rom is global (MIUI 8) . then i tried to flash dev rom with updater app but it gave me couldn't verify update package error. i cleared updater data and tried again but same error.
in next step i tried mi pc suite to flash but no success.
then i used fastboot mode and mi flash and i got locked bootloader error.
then i used EDL mode to flash but in mi flash i got hello package error. (object reference not set to an instance of an object)
i completely confused . i tried all methods and read many fix like login in i.mi.com and other method that people fixed their problem but all of them not fix mine.
i read some threads about flashing twrp and root without unlocking bootloader but all of them need flashing dev rom and i can't flash.
can anyone help me?
Click to expand...
Click to collapse
I just recently went through most of what you have gone through... Be patient though... It seems that the unlocking of bootloader even after you getting permission, takes atleast 2-3 weeks more.
- You can flash the miui global dev rom, you may download it from the miui forums... Here is the link for the fastboot rom http://en.miui.com/a-234.html.
- To flash the dev rom, you need to ensure you put your phone into fastboot, ensure all the fastboot drivers are installed on your computer
- Also, you need to ensure that you download the GLOBAL/DEV FASTBOOT ROM(this is different than the regular zip package) that you download.
- Then you can follow the instructions to install the ROM using miflash tool
- If the ROM installation is a success, then you just need to wait patiently atleast for 15-20 days from the time you got unlock permission sms from MI
- Then try running the flash unlock tool, it should get unlocked.
- Now flashing TWRP might be tricky, I was able to flash the official TWRP, but had issues where the internal memory wasn't getting mounted, because you keep getting asked for decryption password in TWRP to mount the data, no matter what you enter, it might not work
- After trying many TWRP types, the one that worked was "zcx twrp"
- Once you flash that, you should be able to flash any custom or miui roms you need :good:
GENiU5 said:
I just recently went through most of what you have gone through... Be patient though... It seems that the unlocking of bootloader even after you getting permission, takes atleast 2-3 weeks more.
- You can flash the miui global dev rom, you may download it from the miui forums... Here is the link for the fastboot rom http://en.miui.com/a-234.html.
- To flash the dev rom, you need to ensure you put your phone into fastboot, ensure all the fastboot drivers are installed on your computer
- Also, you need to ensure that you download the GLOBAL/DEV FASTBOOT ROM(this is different than the regular zip package) that you download.
- Then you can follow the instructions to install the ROM using miflash tool
- If the ROM installation is a success, then you just need to wait patiently atleast for 15-20 days from the time you got unlock permission sms from MI
- Then try running the flash unlock tool, it should get unlocked.
- Now flashing TWRP might be tricky, I was able to flash the official TWRP, but had issues where the internal memory wasn't getting mounted, because you keep getting asked for decryption password in TWRP to mount the data, no matter what you enter, it might not work
- After trying many TWRP types, the one that worked was "zcx twrp"
- Once you flash that, you should be able to flash any custom or miui roms you need :good:
Click to expand...
Click to collapse
tnx for reply but my problem is i cant flash.
my bootloader is locked and i cant flash fastboot rom.
therefor i must use edl mode or updater app but both of them don't work as a said in first post.
You don't need an unlocked BL to flash official fast boot miui ROMs
GENiU5 said:
You don't need an unlocked BL to flash official fast boot miui ROMs
Click to expand...
Click to collapse
mi flash show me : bootloader unlock in flashing process
x23are said:
mi flash show me : bootloader unlock in flashing process
Click to expand...
Click to collapse
You may try the steps on this link http://en.miui.com/thread-235865-1-1.html
Skip the EDL thing and go directly to the part where they explain how to use the miflash tool to flash a fastboot ROM
I should have asked this first... what's the state of your phone right now? Does it boot, stuck on boot loop, or are you able to boot into some ROM.
maybe u have a vendors rom, flash the fastboot rom using edl
finally a downloaded adb 1.4.3 and installed it and i flashed dev rom in EDL mode.
but now i have some questions:
can i change kernel with locked bootloader?
if i change kernel does fingerprint work?
You just dont have proper drivers installed im 100% sure, else it would go via edl
Hehe was right������
And why dont you ask for official unlock approval? Its approved in less than a day, anyone saying otherwise have old news
Or you can always use a method in this forum...
I know there are several threads about unbricking RN3 but I didn't find any article that could solve this problem, not even in other forums.
This started when apps were continuously force closing for no reason and I decided to flash a new official ROM (going on MIUI settings) but the problem persisted. So I did that via MI Flash and I had the same result.
As this force closing situation were being more and more frequent I flashed several times different official MIUI ROMS from EDL mode (developer and stable) and then, after one of this times, it just don't start the system anymore, its just keep bootlooping again and again.
I also tried another methods, like flashing updated fastboot ROMS but didn't work out.
Another thing, I've flashed TWRP once but it asked for a password so I couldn't access the files and flash a custom rom and my phone is locked (that xiaomi lock situation). But after that I've restored the original recovery (that appears an image of a unplugged/plugged phone to use with pc suite but it doen't recognize my device).
So, I don't really know what to do anymore.
I didn't even use this phone for a complete year and xiaomi lacks of support in my country and they wont help me, like they replied my by email.
Anyone could help me with this issue?
Thank you, by the way!
Try unlocking bootloader unofficially if can't do officially . Try edl mod
tom jp said:
Try unlocking bootloader unofficially if can't do officially . Try edl mod
Click to expand...
Click to collapse
Actually, I tried to flash a file to do that, but didn't work out. Maybe it's the method that I've used.
Could you recommend anyone?
the simple reason is your phone is soft bricked...
all yoi have to do is flash fastboot rom via edl using mi flash tool... you will find thered relating to it in guide section of this forum.
~peace
adithyan25 said:
the simple reason is your phone is soft bricked...
all yoi have to do is flash fastboot rom via edl using mi flash tool... you will find thered relating to it in guide section of this forum.
~peace
Click to expand...
Click to collapse
Actually, I did that several times... so, that's not the solution
lucasmp.paiva said:
Actually, I did that several times... so, that's not the solution
Click to expand...
Click to collapse
didu done a full wipe via miflashtool?..
adithyan25 said:
didu done a full wipe via miflashtool?..
Click to expand...
Click to collapse
Yes, I did.
Cleaned all and with multiple roms.
lucasmp.paiva said:
I know there are several threads about unbricking RN3 but I didn't find any article that could solve this problem, not even in other forums.
This started when apps were continuously force closing for no reason and I decided to flash a new official ROM (going on MIUI settings) but the problem persisted. So I did that via MI Flash and I had the same result.
As this force closing situation were being more and more frequent I flashed several times different official MIUI ROMS from EDL mode (developer and stable) and then, after one of this times, it just don't start the system anymore, its just keep bootlooping again and again.
I also tried another methods, like flashing updated fastboot ROMS but didn't work out.
Another thing, I've flashed TWRP once but it asked for a password so I couldn't access the files and flash a custom rom and my phone is locked (that xiaomi lock situation). But after that I've restored the original recovery (that appears an image of a unplugged/plugged phone to use with pc suite but it doen't recognize my device).
So, I don't really know what to do anymore.
I didn't even use this phone for a complete year and xiaomi lacks of support in my country and they wont help me, like they replied my by email.
Anyone could help me with this issue?
Thank you, by the way!
Click to expand...
Click to collapse
Hi my friend if you cant mount data in twrp. your internal storage is encrypted by custom rom
to solve your problem
1-format data (not wipe)
2-wipe
system
cache
dalvik cache
internal storage
3-flash(clean all and lock) latest miui rom in edl mod
and if your problem solved tell us
(my english...)
farshad9500gy said:
Hi my friend if you cant mount data in twrp. your internal storage is encrypted by custom rom
to solve your problem
1-format data (not wipe)
2-wipe
system
cache
dalvik cache
internal storage
3-flash(clean all and lock) latest miui rom in edl mod
and if your problem solved tell us
(my english...)
Click to expand...
Click to collapse
I've tried to install TWRP but it needs a password to decript data. So it appears 0mb on everything and shows an error to format, wipe or do anything.
Remember, my device is still locked by miui.
lucasmp.paiva said:
I've tried to install TWRP but it needs a password to decript data. So it appears 0mb on everything and shows an error to format, wipe or do anything.
Remember, my device is still locked by miui.
Click to expand...
Click to collapse
take a picture of data format error and put here
Make sure you have try this:
wipe->format data->type "yes" and ok
also try this command in fastboot mod:
fastboot erase userdata
and remember use latest twrp
So I accidentally flashed a wrong boot.img while on my current ROM (AOSiP 8.1) The wrong flash caused my system to be somewhat destroyed (Can't mount and others). The only hope I had was to do the FastBoot method which somehow worked but returned me to MIUI 9.
I did all the rooting and recovery process again and decided to flash the AOSiP ROM again with the proper procedures but as soon as I install after wiping I get the error something like "twfunc failed to flash repacked image". I thought it was just a corrupt download but after downloading twice and using another ROM it was still the same. Can somebody please help me? It's a hassle going through the FastBoot flash method again and it might get worse if not yet fixed ASAP.
ClockUpEx said:
So I accidentally flashed a wrong boot.img while on my current ROM (AOSiP 8.1) The wrong flash caused my system to be somewhat destroyed (Can't mount and others). The only hope I had was to do the FastBoot method which somehow worked but returned me to MIUI 9.
I did all the rooting and recovery process again and decided to flash the AOSiP ROM again with the proper procedures but as soon as I install after wiping I get the error something like "twfunc failed to flash repacked image". I thought it was just a corrupt download but after downloading twice and using another ROM it was still the same. Can somebody please help me? It's a hassle going through the FastBoot flash method again and it might get worse if not yet fixed ASAP.
Click to expand...
Click to collapse
Did you try using redwolf recovery? Also do this. Go to en.miui.com and dl the latest miui zip. Using redwolf try to flash it. If you are able to do it then possibly it's something with stock twrp. If not then you might need to fastboot flash miui again. The last option would be to use edl mode.
I tried FastBoot method flashing the latest MIUI 9 build. Worked out fine but after Rooting again and adding Recovery, flashing ROMs give me Error7 most of the time. What I did is I accidentally clicked the Clear All on the MiFlash and resulted to my problem being fixed while losing all files in my internal. Noooooo!
ClockUpEx said:
I tried FastBoot method flashing the latest MIUI 9 build. Worked out fine but after Rooting again and adding Recovery, flashing ROMs give me Error7 most of the time. What I did is I accidentally clicked the Clear All on the MiFlash and resulted to my problem being fixed while losing all files in my internal. Noooooo!
Click to expand...
Click to collapse
Soo? Is it fixed now? Is that what you mean?
I was read https://topjohnwu.github.io/Magisk/install.html. That link describe how to install Magisk in our device in few ways. I was interested "Boot Image Patching" section that tell us about rooting device without TWRP.
Before this, I have 5 redmi devices and 3 of it were rooted-well via TWRP. 1 bricked (totally bricked) :laugh: and 1 still un-rooted (Redmi 6A-cactus).
My spec of Redmi 6A are:
Security Level Patch: 2019-03-01
MIUI Version: Global Stable 10.2.8.0 (oCBMIXM)
Unlocked: False (i know that i should unlocked it later, i still waiting my 360 hours )
RAM: 2GB
Storage: 16GB
Since i found that link, i still wondering and keep searching about: "is anybody succesfull root their device (especially Redmi 6A with same spec above) with "Boot Image Patching" way?
if any, please let me know. i just want to hear their review and (of course) their experience.
thanks
Yes, i got it working but i still recommend the TWRP method, but if you're still interested, be careful, don't disable the forceencrypt while patching, you can disable dm-verity but DO NOT disable the forceencrypt or you'll lose IMEI/Baseband.
Anyway, this is the patched_boot.img i've used (extracted from the latest V10.2.8.0.OCBMIXM rom).
https://www80.zippyshare.com/v/2zWEXIcM/file.html
Repeating, i still prefer the TWRP method, be careful.
jonaaa said:
Yes, i got it working but i still recommend the TWRP method, but if you're still interested, be careful, don't disable the forceencrypt while patching, you can disable dm-verity but DO NOT disable the forceencrypt or you'll lose IMEI/Baseband.
Anyway, this is the patched_boot.img i've used (extracted from the latest V10.2.8.0.OCBMIXM rom).
https://www80.zippyshare.com/v/2zWEXIcM/file.html
Repeating, i still prefer the TWRP method, be careful.
Click to expand...
Click to collapse
Nice... i'll try that soon when my 360 hours run out..
thanks.
Hi @jonaaa, its me again..
i was success root my 6a with patched_boot.img. but i've got problem when i installing systemless xposed. Xposed Zip successfully installed, but when i tried to install Xposed Manager then reboot, i got stuck in mi logo. i've been trying for 3 times and getting frustrated
now i decided to install twrp and (again) i got stuck in encryption problem. most of google result said that data partition should be formatted and that dont make any sense for me. how could i formatting data partition while that partition is untouchable.
so i wanna ask you: how you get rid from twrp encrypt-decrypt problem?
adista said:
Hi @jonaaa, its me again..
i was success root my 6a with patched_boot.img. but i've got problem when i installing systemless xposed. Xposed Zip successfully installed, but when i tried to install Xposed Manager then reboot, i got stuck in mi logo. i've been trying for 3 times and getting frustrated
now i decided to install twrp and (again) i got stuck in encryption problem. most of google result said that data partition should be formatted and that dont make any sense for me. how could i formatting data partition while that partition is untouchable.
so i wanna ask you: how you get rid from twrp encrypt-decrypt problem?
Click to expand...
Click to collapse
Forget it..
My step was wrong. i was ignoring "fastboot format userdata" command in first and install twrp directly...
thanks for your suggestion :good:
adista said:
Forget it..
My step was wrong. i was ignoring "fastboot format userdata" command in first and install twrp directly...
thanks for your suggestion :good:
Click to expand...
Click to collapse
hi
can share your steps in detail, from beginning to end
Sent from my Redmi 6A using Tapatalk
ahhl said:
hi
can share your steps in detail, from beginning to end
Sent from my Redmi 6A using Tapatalk
Click to expand...
Click to collapse
i dont recommend to use my step, because right now i even dont have twrp in my redmi 6a. In other word, im failed.
UBL
Enabling Developer Option
Entry Fastboot mode
fastboot devices (to check it's connected well with pc)
fastboot format userdata
fastboot flash recovery twrp-3.3.0.0.img
fastboot boot twrp-3.3.0.0.img
For a while, i was able to entry twrp without any password asked and installing magisk (magisk-19.0.zip) smoothly.
But, when i rebooting, i've got stuck at mi logo (i've been wait more than 40 minutes and still at mi logo). When i tried to Volume Up + Power, just nothing happened but back to mi logo and stuck again (and more 40 minutes :silly:).
and finally i did install fastboot-rom from scratch... :laugh::laugh: and since that, twrp wont installed on my redmi even i flash fastboot-rom again and again. Till now i still wondering why and not found the answer yet.
adista said:
i dont recommend to use my step, because right now i even dont have twrp in my redmi 6a. In other word, im failed.
UBL
Enabling Developer Option
Entry Fastboot mode
fastboot devices (to check it's connected well with pc)
fastboot format userdata
fastboot flash recovery twrp-3.3.0.0.img
fastboot boot twrp-3.3.0.0.img
For a while, i was able to entry twrp without any password asked and installing magisk (magisk-19.0.zip) smoothly.
But, when i rebooting, i've got stuck at mi logo (i've been wait more than 40 minutes and still at mi logo). When i tried to Volume Up + Power, just nothing happened but back to mi logo and stuck again (and more 40 minutes :silly:).
and finally i did install fastboot-rom from scratch... :laugh::laugh: and since that, twrp wont installed on my redmi even i flash fastboot-rom again and again. Till now i still wondering why and not found the answer yet.
Click to expand...
Click to collapse
Use the TWRP-1020 instead, it works much better.
hi, i followed this video and i succes for install twrp https://www.youtube.com/watch?v=522RzZ7_uRM&t=254s
jonaaa said:
Yes, i got it working but i still recommend the TWRP method, but if you're still interested, be careful, don't disable the forceencrypt while patching, you can disable dm-verity but DO NOT disable the forceencrypt or you'll lose IMEI/Baseband.
Anyway, this is the patched_boot.img i've used (extracted from the latest V10.2.8.0.OCBMIXM rom).
https://www80.zippyshare.com/v/2zWEXIcM/file.html
Repeating, i still prefer the TWRP method, be careful.
Click to expand...
Click to collapse
My IMEI/Baseband are gone, when I install xposed framework and reboot it's stuck in MI logo, and I tried factory reset from my original MI recovery, it's fix the bootloop but my IMEI/Baseband are gone.... Do you know how to fix it? I spend my time searching to fix it and no result. And I tried flash stock ROM too and no result. Hope you know how fix my issue, thanks!!
whothehellami said:
My IMEI/Baseband are gone, when I install xposed framework and reboot it's stuck in MI logo, and I tried factory reset from my original MI recovery, it's fix the bootloop but my IMEI/Baseband are gone.... Do you know how to fix it? I spend my time searching to fix it and no result. And I tried flash stock ROM too and no result. Hope you know how fix my issue, thanks!!
Click to expand...
Click to collapse
Someone said to encrypt the data on settings, i don't know how though, if you fix it, next time, don't disable the forceencrypt.
Can you post questions in the questions and answers section next time?
i was looking around on how to flash twrp but theres no clear guide on how to do it. i keep noticing people said dont disable verity, they didn't mentioned where and when not to disable it.
because after we flash twrp, we boot to twrp. then what?
Sent from my vivo 1723 using Tapatalk
ahhl said:
i was looking around on how to flash twrp but theres no clear guide on how to do it. i keep noticing people said dont disable verity, they didn't mentioned where and when not to disable it.
because after we flash twrp, we boot to twrp. then what?
Sent from my vivo 1723 using Tapatalk
Click to expand...
Click to collapse
Uhh... just flash the TWRP and you're done.
The dm-verity removal is necessary if you want to install any GSI.
jonaaa said:
Uhh... just flash the TWRP and you're done.
The dm-verity removal is necessary if you want to install any GSI.
Click to expand...
Click to collapse
well i got this issue after flash twrp. after boot and reboot
i got this annyoing android system error, contact manufacturer for detail.
I have a similar problem
I was rooting my redmi 6a and now its bricked
First i intall the twrp, then i flash the Magisk with DisableEncryption, the first boot work fine, i update the magisk app and the new version isnt compatible with the magisk installed
Well i repeat the steps and then i lost the signal, in that moment i didnt know it is the IMEI lost, then i try to install Lineage OS 15.1 GSI for Redmi6a cause i think that is the solution
but the system dont boot, only boot the Xiaomi Tittle with "unlocked" (I unlock the phone before) and then get me to TWRP
Im only one with this problem?
I try use the MiFlashTool for flash the stock rom but not work, now im trying with MiFlashTool flash the MIUI9 and MIUI10.2 and other versions
I think, the problem maybe is the Boot.img
(Sorry for my bad English)
Edit-
I dont have any backup lol
---------- Post added at 02:23 AM ---------- Previous post was at 02:01 AM ----------
jonaaa said:
Uhh... just flash the TWRP and you're done.
The dm-verity removal is necessary if you want to install any GSI.
Click to expand...
Click to collapse
¿Can you share your correct steps to have the Lineage OS 15.1 in Redmi6A Please?
ahhl said:
well i got this issue after flash twrp. after boot and reboot
i got this annyoing android system error, contact manufacturer for detail.
Click to expand...
Click to collapse
This "contact manufacturer" error happens when you disable dm-verity, you can install Magisk without disabling it.
whothehellami said:
My IMEI/Baseband are gone, when I install xposed framework and reboot it's stuck in MI logo, and I tried factory reset from my original MI recovery, it's fix the bootloop but my IMEI/Baseband are gone.... Do you know how to fix it? I spend my time searching to fix it and no result. And I tried flash stock ROM too and no result. Hope you know how fix my issue, thanks!!
Click to expand...
Click to collapse
Sorry for late post
Just make sure that you flash Fastboot ROM, not just STOCK ROM. I did that last time when my IMEI/Baseband are gone. Of course it will wipe all of your data. Just be prepare for it.. :laugh:
davidhozic said:
Can you post questions in the questions and answers section next time?
Click to expand...
Click to collapse
Ups sorry.. i didnt notice that is exists :silly:
No, it wasnt like that :laugh:,, actually i did confused where should i put this question, because in Question & Answers (for me) the topic just too general and i was thinking that my question (maybe) still in development because i didnt found that in Question & Answer...
All my fault, Sorry again,
jonaaa said:
Use the TWRP-1020 instead, it works much better.
Click to expand...
Click to collapse
that just un-official TWRP, right??
i will try that in this weekend. Last time i remember that i can not boot into twrp. Till now, my devices still unrooted. I flash it back to stock ROM. But, when OTA update notification comes and reboot for installing, it give me bootloop into twrp (not to system), and that's mean my TWRP still inside i just cannot boot into.
so, i'll try that TWRP-1020 this weekend. Thanks.