Hi,
Ido have redmi 3S 2/16 gb and have the following problem.
Flash in Fastboot "fastboot flash recovery twrp.img" finishes sucessful
Reboot " fastboot boot twrp.img" finishes sucessful
but phone takes about 30 sec. to reboot and boots into normal system operation
I have tried several times, no success.
I can flash the phone with Miflash, everything fine. at the moment there is MIUI Global V8.1.1.0 stable on it.
Updater App also does not work correct, whenever i select a .zip to update it requires internet connection to download, but ROM is on SD card.
Any hints from the community ?
You MUST unlock the bootloader if you want TWRP flash stick and be usable.
lolo9393 said:
You MUST unlock the bootloader if you want TWRP flash stick and be usable.
Click to expand...
Click to collapse
Bootloader is unlocked, otherwise i would not have posted in Forum but forgot to mention in my first post.
But i found a very interesting way to boot into TWRP.
1. i temporarely booted into cyanogen cwm
2. restarted into recovery in cwm
3. to my surprise it booted into my previous installed TWRP
4. i could install MIUI v8 .eu rom without problems
booted into system the phone is running nice, but i cannot boot into recovery by Keys Power+ Vol+ nor via updater app.
In always boots into running system.
unique case, i'm following this...
i wish i can help but i'm not that expert
hopefuly someone with enough experience can help or at least give some information.
thanks for sharing
fmcheetah said:
Hi,
Ido have redmi 3S 2/16 gb and have the following problem.
Flash in Fastboot "fastboot flash recovery twrp.img" finishes sucessful
Reboot " fastboot boot twrp.img" finishes sucessful
but phone takes about 30 sec. to reboot and boots into normal system operation
I have tried several times, no success.
I can flash the phone with Miflash, everything fine. at the moment there is MIUI Global V8.1.1.0 stable on it.
Updater App also does not work correct, whenever i select a .zip to update it requires internet connection to download, but ROM is on SD card.
Any hints from the community ?
Click to expand...
Click to collapse
I have exactly the same problem with my redmi 3S 2/16 gb. I can't start twrp in any way....i will try to do your way.
Try flasher toolkit: http://en.miui.com/thread-328569-1-1.html or material twrp: http://en.miui.com/thread-346365-1-1.html
Sent from my Redmi Note 3 using Tapatalk
I was having similar problems. Flashed twrp from fastboot but always got stock recovery. I used the flasher toolkit. PROFIT!
I tried everything but always stock recovery is back...
Annoying..
Sent from my MI 3W using Tapatalk
Hello ALL
In order to be sure to follow the same track is it possible for you to post your bootloader status as attached.
I have concern about the called "device critical unlock"
Thanks
exactly the same parameters on my redmi3s...i have to try the method from fmcheetah.
timberwolf60 said:
Try flasher toolkit: http://en.miui.com/thread-328569-1-1.html or material twrp: http://en.miui.com/thread-346365-1-1.html
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
Thanks for your info.
Flasher toolkit executes all the commands wich i tried already in batch file format, no luck !
Same situation here...i've tried all this bat before, not even one works. Have somebody tried TWRP by cofface ?
I didn't...No nerves anymore
Sent from my MI 3W using Tapatalk
i believe you...this goes really on the nerves. What is very strange is that only a few of us have this problem. I have no clue why, but it seems to me that only happens to the people with redmi 3s (2 gb/16 gb) bought recently. I am trying to figure out if this has something to do how we do the flash with Miflash (maybe which version ?), but it doesn't look at the first sight any different from what others do.
Sorry but my Redmi3S is only 10 days old 'from buying date' and TWRP-installer.bat did the job at first trial. But I discovered that the data partition came encrypted and I was forced to format all. Then I installed the new rom from OTG because I didn't have SD card available.
fmcheetah said:
Thanks for your info.
Flasher toolkit executes all the commands wich i tried already in batch file format, no luck !
Click to expand...
Click to collapse
Tried material twrp, fist time I used flasher toolkit it flashed successfully but can't booted into twrp, so I tried material twrp with success which on the second link.
Sent from my Redmi Note 3 using Tapatalk
humaxboy said:
i believe you...this goes really on the nerves. What is very strange is that only a few of us have this problem. I have no clue why, but it seems to me that only happens to the people with redmi 3s (2 gb/16 gb) bought recently. I am trying to figure out if this has something to do how we do the flash with Miflash (maybe which version ?), but it doesn't look at the first sight any different from what others do.
Click to expand...
Click to collapse
Just for info:
The same behaviour i had before i flashed with Miflash with the Global Stable ROM.
I cannot try anything further because i prepared the Phone for a friend of mine. FW is MIUI V8 6.11.10 beta xiaomi eu. , he is happy so far.
By the way on a Redmi 3s 2/16 from 2 months ago i had none of this at all !!!
fmcheetah said:
Bootloader is unlocked, otherwise i would not have posted in Forum but forgot to mention in my first post.
But i found a very interesting way to boot into TWRP.
1. i temporarely booted into cyanogen cwm
2. restarted into recovery in cwm
3. to my surprise it booted into my previous installed TWRP
4. i could install MIUI v8 .eu rom without problems
booted into system the phone is running nice, but i cannot boot into recovery by Keys Power+ Vol+ nor via updater app.
In always boots into running system.
Click to expand...
Click to collapse
PLease explain it clearly.how you booted in cwm.???
officialrooter said:
PLease explain it clearly.how you booted in cwm.???
Click to expand...
Click to collapse
Download latest CyanogenMod Recovery for Redmi 3S to your Computer.
The file you downloaded is called recovery.img
Boot your redmi 3s into fastboot mode
in fastboot command: fastboot boot recovery.img
you are in cyanogen mod recovery and can enjoy.
fmcheetah said:
Download latest CyanogenMod Recovery for Redmi 3S to your Computer.
The file you downloaded is called recovery.img
Boot your redmi 3s into fastboot mode
in fastboot command: fastboot boot recovery.img
you are in cyanogen mod recovery and can enjoy.
Click to expand...
Click to collapse
It means this is the only method to boot into recovery ............. Can someone with better knowledge please figure out the solution....
Related
Hi everyone,
I've run out of ideas on this one and other threads couldn't really help me/were closed already.
I tried CM, stock android by Ivan and M1cha as well as some others, but about a month ago, I was curios for MIUI 6 based on Lollipop for my Mi2s and changed from M1cha's CM12 5.0.1.
Now that I've seen that Ivan published his 5.1.1 I wanted to try it out. He also provides us with a modified custom recovery that I wanted to flash.
First, I renamed the file to update.zip and tried to flash it in Mi-Recovery 2.0.1, which didn't work due to the failing signature verification.
Also, choosing update package in the Updater app in MIUI didn't work out, it immediately tells me something went wrong.
Then I thought, why not use fastboot? That worked before.
Not this time. I tried the simple way, meaning just fastboot flash recovery recovery.img: Then, bc it didn't work, I first erased the recovery partition and then flashed the recovery.img, which was still unsuccessful.
Whenever I try to enter recovery mode, my phone just gets stuck showing the MI logo and not doing anything.
I can reenter fastboot mode or simply reboot to the system as usual, except for when no system is installed.
When I gave up on the custom recovery thing, I simply tried to flash the ROM via update.zip methods, as well as via fastboot. None of them worked, either because the signature verification fails (stock recovery) or because the zip file does not contain the android-info.txt and the other txt file.
As mentioned above, upon entering fastboot -w and then flashing the recovery.img, I can suddenly enter recovery mode. This sucks!
TL;DR: No usual method of flashing either custom rom or recovery works (to my knowledge)
Can anyone help me? I know its stupid but I start feeling kind of boxed in on MIUI.
Thanks in advance
fastboot oem unlock
fastboot flash recovery recovery.img
unfortunately, that didn't work either...
leonfromotown said:
unfortunately, that didn't work either...
Click to expand...
Click to collapse
Do fastboot devices and tell us the output
SkiFire13 said:
Do fastboot devices and tell us the output
Click to expand...
Click to collapse
5b799fb fastboot
looks just the way it did before
This vide will guide you how to root REDMI NOTE 4(SNAPDRAGON)
***IMPORTANT***
BACKUPDATA
Make sure you have adb installed and you place the twrp file to adb folder & other files to internal memory
Downloads:
1. TWRP- 3.0.3-0
https://www.androidfilehost.com/?fid=457095661767136323
2. phh's SuperSu
https://superuser.phh.me/superuser.zip
3. no-verity-opt-encrypt
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-5.1.zip
Steps:
1.unlock bootloader
http://en.miui.com/unlock/
or
Google mi unlock
2.download files
3.enable usb debugging
4.boot to fastboot (volume down+power button)
5.connect to pc run cmd in adb folder .
6.use command (fastboot devices) to check fastboot devices
7.use command (fastboot flash recovery {name of recovery}.img)
8.boot device to recovery (Flash Verity file, su ) ***IMPORTANT***
9.wipe caches
10.reboot
This is not my work all credit to:
XDA:
https://forum.xda-developers.com/re...ecovery-twrp-3-0-3-0-redmi-note-4-sd-t3549970
Video:
https://youtu.be/dV4urAIRKZU
Not working in 8.1.15.0
Unfortunately not working in miui 8.1.15.0.. Eagerly waiting for your response
ashokmor007 said:
This vide will guide you how to root REDMI NOTE 4(SNAPDRAGON)
***IMPORTANT***
BACKUPDATA
Make sure you have adb installed and you place the twrp file to adb folder & other files to internal memory
Downloads:
1. TWRP- 3.0.3-0
https://www.androidfilehost.com/?fid=457095661767136323
2. phh's SuperSu
https://superuser.phh.me/superuser.zip
3. no-verity-opt-encrypt
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-5.1.zip
Steps:
1.unlock bootloader
http://en.miui.com/unlock/
or
Google mi unlock
2.download files
3.enable usb debugging
4.boot to fastboot (volume down+power button)
5.connect to pc run cmd in adb folder .
6.use command (fastboot devices) to check fastboot devices
7.use command (fastboot flash recovery {name of recovery}.img)
8.boot device to recovery (Flash Verity file, su ) ***IMPORTANT***
9.wipe caches
10.reboot
This is not my work all credit to:
XDA:
https://forum.xda-developers.com/re...ecovery-twrp-3-0-3-0-redmi-note-4-sd-t3549970
Video:
https://youtu.be/dV4urAIRKZU
Click to expand...
Click to collapse
twrp titale say its for mtk
amnv said:
Unfortunately not working in miui 8.1.15.0.. Eagerly waiting for your response
Click to expand...
Click to collapse
Wil update you by tmro on the latest version
vikasb32 said:
Not working in 8.1.15.0
Click to expand...
Click to collapse
I did root my device flash custom recovery (TWRP) while running MIUI 8.1.15.0
whats the issue u had? bootloop?
TechRapt said:
I did root my device flash custom recovery (TWRP) while running MIUI 8.1.15.0
whats the issue u had? bootloop?
Click to expand...
Click to collapse
Most of member says this twrp does not work in miui 8.1.15.0, They say after flashing it mi logo flashes for some time and they could not boot into twrp mode
Honestly i haven't flashed it into my device coz most of people facing bugs only in miui 8.1.15.0..
Im miui 8.1.15.0 stable user hope u can help me.
Thank you
Sent from my Redmi Note 4 using Tapatalk
amnv said:
Most of member says this twrp does not work in miui 8.1.15.0, They say after flashing it mi logo flashes for some time and they could not boot into twrp mode
Honestly i haven't flashed it into my device coz most of people facing bugs only in miui 8.1.15.0..
Im miui 8.1.15.0 stable user hope u can help me.
Thank you
Sent from my Redmi Note 4 using Tapatalk
Click to expand...
Click to collapse
I am not sure if this is the same TWRP i used
I used the TWRP version from LA 14.1 thread.
I did face few issues though like long boot time but never had issues with loading TWRP or when the OS booted up completely
I am on 7.3.9 build now let me roll back to stable 8.1.15.0 build tonight and re-try the same flash recovery and root method will let u know the results
Not able to boot to recovery
All the installation went as expected till recovery installation. It is done but using Volume Up & Power button not able to go to recovery. Just MI logo post that nothing.
Everything OK but sim slot 2 does not work after root
chandrash3khar said:
All the installation went as expected till recovery installation. It is done but using Volume Up & Power button not able to go to recovery. Just MI logo post that nothing.
Click to expand...
Click to collapse
Rename your recovery as "recover.img".
After flashing recovery don't disconnect the phone
In fastboot type
"fastboot boot recovery.img"
Your phone will boot into recovery
I have redmi note 4 4g 64gb rom 2017 is not unblock.. plz help
:fingers-crossed:
hadiyalkishan said:
twrp titale say its for mtk
Click to expand...
Click to collapse
I have redmi note 4 4g 64gb rom 2017 is not unblock.. plz help
rajendraDMD said:
:fingers-crossed:
I have redmi note 4 4g 64gb rom 2017 is not unblock.. plz help
Click to expand...
Click to collapse
What do you mean?
Not working on my redmi note 4 sd (stable 8.2.10.0). When i try to flash the img file terminal shows lots of help tips. I installed all drivers carefully, still its happening. Please help..
I had rooted my Oneplus 2 and installed TWRP two years back, and was on default Oxygen OS [Android 5.1] and did not install update since then. My TWRP version number was 2.8.7.0. Now as of yesterday, the phone exhibited an unusual behaviour, apps closing, dialer and message app closing etc. So I decided to update it to Android 7.1 ROM. I took a backup of required data.
The rom I was planning to flash was RR 5.85 along with TWRP 3.1.1.0-oneplus2.img as updated on TWRP website. So I began with flashing TWRP version. I rebooted in my recovery [TWRP 2.8.7.0]. Selected the file from .img menu, and selected Recovery partition when asked to. It gave me a success prompt. And I selected an option for TWRP to reboot to recovery. It was stuck at OnePlus screen [the one which pops up when we restart] with the capacitive lights [Button Lights] on the entire time. I waited for 10 minutes, but without recourse. So I loaded it into fastboot and flashed an earlier version of TWRP recovery twrp-3.0.2-2-oneplus2.img using [fastboot flash recovery twrp-3.0.2-2-oneplus2.img] command. I again tried to reboot into recovery mode, yet the same problem was displaying.
Please help guys. Did I miss something here such as bootloader upgrade or something like that, since I had not performed any updates for 2 Years.
Edit: Never mind fixed it. Please feel free to delete this thread
x0nar said:
I had rooted my Oneplus 2 and installed TWRP two years back, and was on default Oxygen OS [Android 5.1] and did not install update since then. My TWRP version number was 2.8.7.0. Now as of yesterday, the phone exhibited an unusual behaviour, apps closing, dialer and message app closing etc. So I decided to update it to Android 7.1 ROM. I took a backup of required data.
The rom I was planning to flash was RR 5.85 along with TWRP 3.1.1.0-oneplus2.img as updated on TWRP website. So I began with flashing TWRP version. I rebooted in my recovery [TWRP 2.8.7.0]. Selected the file from .img menu, and selected Recovery partition when asked to. It gave me a success prompt. And I selected an option for TWRP to reboot to recovery. It was stuck at OnePlus screen [the one which pops up when we restart] with the capacitive lights [Button Lights] on the entire time. I waited for 10 minutes, but without recourse. So I loaded it into fastboot and flashed an earlier version of TWRP recovery twrp-3.0.2-2-oneplus2.img using [fastboot flash recovery twrp-3.0.2-2-oneplus2.img] command. I again tried to reboot into recovery mode, yet the same problem was displaying.
Please help guys. Did I miss something here such as bootloader upgrade or something like that, since I had not performed any updates for 2 Years.
Edit: Never mind fixed it. Please feel free to delete this thread
Click to expand...
Click to collapse
How did you fix it? My brother's phone has the same problem.
Sent from my Nexus 6 using Tapatalk
merikgvr401 said:
How did you fix it? My brother's phone has the same problem.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
You have to install marshmallow firmware first.
Best option would be to go back to the working TWRP version, flash oxygenos, reboot to Oxygen once, flash new recovery in fastboot, reboot recovery, flash rom
merikgvr401 said:
How did you fix it? My brother's phone has the same problem.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I don't know if this does anything different, but here's what worked for me
1. Ensure that device enters into fastboot mode
2. "fastboot flash recovery recovery.img"
3. **IMP** After your flashing is successful, directly enter the device into recovery mode by pressimg Power (+) Vol Down button.
4. Now a TWRP prompt shall appear asking your permit for modifications, swipe yes.
Note that: I'm not sure if this makes a difference, but earlier I rebooted after Fastboot and then entered into recovery, but the key was to directly enter into recovery after fastboot.
Let me know if that works for you.
Hi, since i got several updates for my device i thought i'd upload them in case you didn't got it by now.
Pulled them out of logcat.
Security Patches : september 2017
These are for TRT-LX1 C432 B100
INSTALL : rename to update.zip and put in intSD and update through settings ( adb sideload ....)
UPDATES :
TRT-LX1C432B140 : https://androidfilehost.com/?fid=817906626617946360
TRT-LX1C432B150 : https://androidfilehost.com/?fid=817906626617946370
TRT-LX1C432B160 : https://androidfilehost.com/?fid=673791459329061119
TRT-LX1C432B171 : https://androidfilehost.com/?fid=673956719939820453
don't just HIT&RUN....there's a :good: button for some reason
Do you have a full stock ROM for this device (or full nandroid backup)? Do you have a working port of TWRP?
We are trying to get TWRP going on an almost identical device, the Ascend XT2.
aslezak said:
Do you have a full stock ROM for this device (or full nandroid backup)? Do you have a working port of TWRP?
We are trying to get TWRP going on an almost identical device, the Ascend XT2.
Click to expand...
Click to collapse
Not yet - going to try to fastboot boot on twrp i found somewhere and pull firmware - keeping you updated
raystef66, want to try these TWRPs that enigma2446 created using your update.zips ?
Please let us know if they work!
steps:
adb reboot bootloader
fastboot flash recovery <imagename>.img
fastboot reboot
adb reboot recovery
enigma2446 said:
Sorry guys I'm an idiot, the recovery files are in update.app that has to be extracted as well.
Here's a couple more
https://drive.google.com/file/d/1fTc2nyKKO0ELjh2-FGxk03HX7Aw4k2qf/view?usp=drivesdk
https://drive.google.com/file/d/1eAwEAqrVnhxPKD4U-TcqfI2ILr37arLz/view?usp=drivesdk
Click to expand...
Click to collapse
raystef66 said:
Not yet - going to try to fastboot boot on twrp i found somewhere and pull firmware - keeping you updated
Click to expand...
Click to collapse
aslezak said:
raystef66, want to try these TWRPs that enigma2446 created using your update.zips ?
Please let us know if they work!
steps:
adb reboot bootloader
fastboot flash recovery <imagename>.img
fastboot reboot
adb reboot recovery
Click to expand...
Click to collapse
Yeah, haven't got the time to create one out of the zips.
But i'll look into it and let you know.
Btw, i'll not flash but BOOT and see if it's booting. Much safer
EDIT : NOT WORKING
I'll try to make one soon
Could you try booting the stock recovery from the update (update.app / RECOVERY.img)? I extracted using the Huawei update extract tool.
I'm not sure if this phone has some type of lock on booting a recovery (without flashing) ...
If it's easier for you, I've uploaded the extracted RECOVERY.img here:
http://www.filedropper.com/recovery-img
raystef66 said:
Yeah, haven't got the time to create one out of the zips.
But i'll look into it and elt you know.
Btw, i'll not flash but BOOT and see if it's booting. Much safer
EDIT : NOT WORKING
I'll try to make one soon
Click to expand...
Click to collapse
aslezak said:
Could you try booting the stock recovery from the update (update.app / RECOVERY.img)? I extracted using the Huawei update extract tool.
I'm not sure if this phone has some type of lock on booting a recovery (without flashing) ...
If it's easier for you, I've uploaded the extracted RECOVERY.img here:
http://www.filedropper.com/recovery-img
Click to expand...
Click to collapse
I've had that file for a while but haven't the time to make a new twrp for it as i'm always working on my axon 7
Anyway thnx for the effort :good:
I'll test it today and update you.
EDIT : cant fastboot boot stockrecovery.img too - hangs on booting...
Seems to be a problem there. Let's look into that.
Hello friends this update serves the Huawei y7 trt lx3. Thank you
Sheesh .. does "adb reboot recovery" work either?
I flashed mine so I have no idea if that works. If it doesn't work for you, and you never flashed it, we should also try to adb reboot recovery2 & see if that also fails.
Thanks again for your help.
raystef66 said:
I've had that file for a while but haven't the time to make a new twrp for it as i'm always working on my axon 7
Anyway thnx for the effort :good:
I'll test it today and update you.
EDIT : cant fastboot boot stockrecovery.img too - hangs on booting...
Seems to be a problem there. Let's look into that.
Click to expand...
Click to collapse
aslezak said:
Sheesh .. does "fastboot reboot recovery" work either?
I flashed mine so I have no idea if that works. If it doesn't work for you, and you never flashed it, we should also try to fastboot reboot recovery2 & see if that also fails.
Thanks again for your help.
Click to expand...
Click to collapse
You're welcome.
As a matter of fact, as i look into my updates i logcatted from my phone (see OP), the recovery.img of 140 and 150 are the same size : 59032 (as yours).
But the latest 160, has a size of 62592. Check for yourself. Strange...
Anyway, i cannot fastboot boot stockrecovery like said, neither size 140 neither 160 . What works is adb reboot recovery as it is standard.
Btw, there is no such command as fastboot reboot recovery imo. Only fastboot reboot or fastboot boot recovery (either for twrp or your stockrecovery)
Also, what do you mean with : you flashed yours....what did you flash ? and why would you flash your stock recovery as you're on stock
Explain what you have done so far because it's unclear what you're doing.
I flashed various TWRPs of similar models as my recovery, including the two links I had posted in this discussion. I flashed them because "fastboot boot recovery.img" doesn't seem to work on our devices.
I still have the stock recovery in partition "erecovery" so I can adb reboot erecovery, but if I adb reboot recovery, I get the blue power light and black screen.
It's good to know that "adb reboot recovery" works for you. In the update packages, the erecovery.img and recovery.img are exactly the same file, so that's expected. It must be that the erecovery for the Y7 2017 is different than the erecovery for the Ascend XT2 H1711 :crying:
raystef66 said:
You're welcome.
As a matter of fact, as i look into my updates i logcatted from my phone (see OP), the recovery.img of 140 and 150 are the same size : 59032 (as yours).
But the latest 160, has a size of 62592. Check for yourself. Strange...
Anyway, i cannot fastboot boot stockrecovery like said, neither size 140 neither 160 . What works is adb reboot recovery as it is standard.
Btw, there is no such command as fastboot reboot recovery imo. Only fastboot reboot or fastboot boot recovery (either for twrp or your stockrecovery)
Also, what do you mean with : you flashed yours....what did you flash ? and why would you flash your stock recovery as you're on stock
Explain what you have done so far because it's unclear what you're doing.
Click to expand...
Click to collapse
aslezak said:
I flashed various TWRPs of similar models as my recovery, including the two links I had posted in this discussion. I flashed them because "fastboot boot recovery.img" doesn't seem to work on our devices.
I still have the stock recovery in partition "erecovery" so I can adb reboot erecovery, but if I adb reboot recovery, I get the blue power light and black screen.
It's good to know that "adb reboot recovery" works for you. In the update packages, the erecovery.img and recovery.img are exactly the same file, so that's expected. It must be that the erecovery for the Y7 2017 is different than the erecovery for the Ascend XT2 H1711 :crying:
Click to expand...
Click to collapse
ok i understand.
True, most likely they are different as you could expect.
Nevertheless we need a twrp
aslezak said:
I flashed various TWRPs of similar models as my recovery, including the two links I had posted in this discussion. I flashed them because "fastboot boot recovery.img" doesn't seem to work on our devices.
I still have the stock recovery in partition "erecovery" so I can adb reboot erecovery, but if I adb reboot recovery, I get the blue power light and black screen.
It's good to know that "adb reboot recovery" works for you. In the update packages, the erecovery.img and recovery.img are exactly the same file, so that's expected. It must be that the erecovery for the Y7 2017 is different than the erecovery for the Ascend XT2 H1711 :crying:
Click to expand...
Click to collapse
I'm in the same situation, I had a bootloader loop going for a minute there. Managed to get out. If anyone figures out the twrp situation it would be greatly appreciated.
I'm not going to wait time with all the one click root apps, considering the only computer available is an app and it seems everything is meant for PC at the moment.
Nice work guys... I'm still waiting for this device but learning in advance... Thanks
Enviado desde mi X5max_PRO mediante Tapatalk
I'm waiting for twrp can't gain super user. I thought the phone would be an easy root.
Slygot said:
I'm waiting for twrp can't gain super user. I thought the phone would be an easy root.
Click to expand...
Click to collapse
Here!
https://forum.xda-developers.com/general/general/twrp-recovery-root-t3734325
astusal said:
Here!
https://forum.xda-developers.com/general/general/twrp-recovery-root-t3734325
Click to expand...
Click to collapse
I managed to get there and the files are no longer available in the tread. Link brings me to a 410 Gone error.
---------- Post added at 12:17 PM ---------- Previous post was at 12:15 PM ----------
Slygot said:
I managed to get there and the files are no longer available in the tread. Link brings me to a 410 Gone error.
Click to expand...
Click to collapse
Nevermind I am an idiot. Found it.
Do you have the full rom?
ashd999 said:
Do you have the full rom?
Click to expand...
Click to collapse
https://forum.xda-developers.com/general/general/twrp-huawei-y7-trt-lx1-trt-lx3-t3738002
I would really love a TRT_LX2 u seemed to get most of them but not my build ive rooted the phone but would love a trwrp for my build..
Moonlighter
A few days ago I bought a Xiaomi Redmi Note 7, I unlocked its bootloader successfully and installed OrangeFox Recovery Project. After that, I installed xiaomi.eu ROM EMUI 12 - Android 10, the latest version of the weekly ROMs for this phone. Since it was a beta ROM, I found some bugs, so I downloaded the stable rom with EMUI 11, but I didn't notice that the zip was corrupted so OrangeFox return an error and I made the mistake of restarting the phone. It was stuck in boot logo and when I enter into fastboot mode, the PC doesn't recognize it. Also, the phone can not enter into recovery mode, it stucks in boot logo.
I have the drivers installed because I tested with another xiaomi en fastboot mode and this one is recognized.
I don't know what to do
Sorry for my english, but I am desperate to fix it. I would really appreciate if someone could help me, please.
it's ok , try format data from orangefox and flash a different zip/rom
EgyBob said:
it's ok , try format data from orangefox and flash a different zip/rom
Click to expand...
Click to collapse
The phone can not enter into recovery mode. :/
Can you enter into fastboot with poder off bottom + volume down ?
If you can then flash a fastboot ROM with mi flash
Check out not relock bootloader
Check "flash all" option https://update.miui.com/updates/v1/fullromdownload.php?d=lavender_global&b=F&r=global&n=
its easy
just unlock bootloader again with miflash unlock then flash any rom you like
uriel cruzitho said:
Can you enter into fastboot with poder off bottom + volume down ?
If you can then flash a fastboot ROM with mi flash
Check out not relock bootloader
Check "flash all" option https://update.miui.com/updates/v1/fullromdownload.php?d=lavender_global&b=F&r=global&n=
Click to expand...
Click to collapse
The problem is that since that happened my cell phone is no longer recognized by the computer.
Phone is not recognized by the PC
My phone is connected now and it is not recognized in fastboot mode.
Dont worry, just put in the commands into fastboot. My device dont get recognized too and i can flash everything.
hi my friend.
sry for my bad english.
i had a redmi 4 prime , and had same problem.
thats get unbricked with a shoke on the phone board.
on the main board of the phone , you have 2 little steel circle and named test points and must connect their to each other .
its easy if you can open the phone. if you cant , you must going to a phone repairer.
like this video
youtu.be/7KyYp_lTR0k
i hope can help you
If your phone can still boot up. Just try to fastboot mode power+vol down. Install latest usb driver for PC. Then try one by one usb port you have on your PC. Because I experienced some usb port doesn't work. And if connected try to reinstall TWRP again.
Uses the previous version of twrp, try connecting the phone to another computer. Use xiaomi usb cable.
228as091215t said:
Dont worry, just put in the commands into fastboot. My device dont get recognized too and i can flash everything.
Click to expand...
Click to collapse
Could you explain to me how you did the Flashing using commands? please
Always you can to made test point and flash with miflash . search in google
:good:
01MaxMarvin said:
A few days ago I bought a Xiaomi Redmi Note 7, I unlocked its bootloader successfully and installed OrangeFox Recovery Project. After that, I installed xiaomi.eu ROM EMUI 12 - Android 10, the latest version of the weekly ROMs for this phone. Since it was a beta ROM, I found some bugs, so I downloaded the stable rom with EMUI 11, but I didn't notice that the zip was corrupted so OrangeFox return an error and I made the mistake of restarting the phone. It was stuck in boot logo and when I enter into fastboot mode, the PC doesn't recognize it. Also, the phone can not enter into recovery mode, it stucks in boot logo.
I have the drivers installed because I tested with another xiaomi en fastboot mode and this one is recognized.
I don't know what to do
Sorry for my english, but I am desperate to fix it. I would really appreciate if someone could help me, please.
Click to expand...
Click to collapse
01MaxMarvin said:
A few days ago I bought a Xiaomi Redmi Note 7, I unlocked its bootloader successfully and installed OrangeFox Recovery Project. After that, I installed xiaomi.eu ROM EMUI 12 - Android 10, the latest version of the weekly ROMs for this phone. Since it was a beta ROM, I found some bugs, so I downloaded the stable rom with EMUI 11, but I didn't notice that the zip was corrupted so OrangeFox return an error and I made the mistake of restarting the phone. It was stuck in boot logo and when I enter into fastboot mode, the PC doesn't recognize it. Also, the phone can not enter into recovery mode, it stucks in boot logo.
I have the drivers installed because I tested with another xiaomi en fastboot mode and this one is recognized.
I don't know what to do
Sorry for my english, but I am desperate to fix it. I would really appreciate if someone could help me, please.
Click to expand...
Click to collapse
If you can put your phone in fastboot mode it's easy, 1) download stock rom. 2 ) unzip the file 3) open it ,and copy all files 3) open the file with ( xiaomi drivers ADB ) than : paste. From the files of the ROM you'll see
" flash all " connect your phone in fastboot mode double click "flash all " and flashing process will start immediately, don't remove your phone until it stops, done.
01MaxMarvin said:
A few days ago I bought a Xiaomi Redmi Note 7, I unlocked its bootloader successfully and installed OrangeFox Recovery Project. After that, I installed xiaomi.eu ROM EMUI 12 - Android 10, the latest version of the weekly ROMs for this phone. Since it was a beta ROM, I found some bugs, so I downloaded the stable rom with EMUI 11, but I didn't notice that the zip was corrupted so OrangeFox return an error and I made the mistake of restarting the phone. It was stuck in boot logo and when I enter into fastboot mode, the PC doesn't recognize it. Also, the phone can not enter into recovery mode, it stucks in boot logo.
I have the drivers installed because I tested with another xiaomi en fastboot mode and this one is recognized.
I don't know what to do
Sorry for my english, but I am desperate to fix it. I would really appreciate if someone could help me, please.
Click to expand...
Click to collapse
01MaxMarvin said:
The problem is that since that happened my cell phone is no longer recognized by the computer.
Click to expand...
Click to collapse
Dude , Try Chinese Version on MI PC Suit. That will recognise your phone for Sure. My phone was also in same situation.
Here is the link of Chinese MI PC Suit with English Translation
miui.blog/ any-devices/china-mi-pc-suite-english-translation/ (Remove Space before 'any')
Chinese MI PC Suit has much more features then Global Version. Like Wiping Your Device , Directly Installing Stock ROM, Etc
Contact Me at +918824712945 (WhatsApp Only - If Any Help Needed)
(Try it Once)