Good evening!
Just wanted to update my girlfriends mi4i from an Kitkat Ferrari rom to a newer one. I had an older twrp on the phone, the one that came with the toolkit for mi4i. For the newer rom i should have at least twrp 2.8.7.. . I found a ferrari twrp 2.8.7 and flashed it per flashify. All went fine. Rebootet all worked. So i wanted to install new rom. In recovery i did n factory reset, which didnt finish. I had to abort it after 15min.
Since then, device wont boot beyond bootscreen. When i try to boot into reovery, i just enter fastbootscreen.
I thought, ok t least fastboot. But when i try to flash any recover through the toolkit, it seems lime all is going well (no errors) but it does not upload the file.. It says in 1,4seconds.. File was sent.. Which is definately wrong 30 mb in 1,4seconds.
Is there anything left i can do?
No working recovery and no working fastboot does sound fuctup?
Thanks for reading
Flash MIUI via Fastboot, it should be fine.
BTW You can never install MIUI via Custom Recovery.
Just to finish. Was able to do a fastboot rom flash.
Worked. Solved
Related
Hey guys
so after ive rooted my MI4i, i installed a custom ROM called Infinitive OS, which is quite good then i stupidly flashed Sensei Kernel to My MI4i, and now, my phone is bricked. I tried to turn it on, after the Mi logo, it shuts off. I am still able to get to my TWRP Recovery, tried to delete cache/dalvik/factory reset, but no use. Still can't boot to system. PLEASE HELP GUYS
Thanks..
jonathanfilbert said:
Hey guys
so after ive rooted my MI4i, i installed a custom ROM called Infinitive OS, which is quite good then i stupidly flashed Sensei Kernel to My MI4i, and now, my phone is bricked. I tried to turn it on, after the Mi logo, it shuts off. I am still able to get to my TWRP Recovery, tried to delete cache/dalvik/factory reset, but no use. Still can't boot to system. PLEASE HELP GUYS
Thanks..
Click to expand...
Click to collapse
Tried flashing back the rom? and did you get to boot into the rom before flashing the kernel?
Yes, b4 I flashed the kernel everything works fine.
jonathanfilbert said:
Yes, b4 I flashed the kernel everything works fine.
Click to expand...
Click to collapse
If i understand well, if you can get to twrp there is no reason to worry...
You just download an official / developer rom or any custom rom, reflash and you are done.
Yeah I know, thing is, mi4i doesn't have an external memory slot..
jonathanfilbert said:
Yeah I know, thing is, mi4i doesn't have an external memory slot..
Click to expand...
Click to collapse
go to recovery and connect your phone in mtp mode from recovery , take backup from internal memory and flash official stable rom
You may flash the device recovery/kernel/firmware via FastBoot
Flash TWRP Recovery via Fastboot, then adb sideload a ROM on the Device. Or Download Official Fastboot firmware for the device and flash it.
Don't forget to say thanks
flash the device with fastboot rom via FastBoot using mi flash
I have the same problem. Just Go into TWRP and wipe Dalvik/Cache/Data/System, after that just flash ROM again and everything works fine
The problem is with firmware and kernel. The firmware isn't compatible with kernel. If u flash the whole rom with firmware it will be fine, if U know witch FW have u used flash it flash it back or flash back original kernel.
check http://forum.xda-developers.com/mi-4i/development/miui-firmware-flash-t3367968
Regards
Whatever You Do, first take a backup of your EFS Partition with TWRP or MI Toolkit. My device crashed and corrupted all partitions suddenly and my IMEI is lost now and I didn't have any backup of EFS to restore my IMEI.
And for restoring your device back to normal you will have to follow this..
1. Take backup of EFS and store it somewhere safe in you pc.
2. Download and extract the Fastboot ROM for Mi4i from here : http://update.miui.com/updates/v1/fullromdownload.php?d=ferrari_global&b=X&r=global&n=
3. As you have already rooted, I suppose that you already have adb drivers installed. If not then install
4. Open Recovery and press and hole POWER and VOLUME DOWN button after recovery boots up completely and do not release the keys until fastboot opens.
5. open Terminal(Linux)/CMD(Windows) and navigate into the directory you just downloaded and extracted.
5. Run "flash_all.bat"(Windows)/"flash_all.sh"(Linux).
6. Give it some time and you will get a brand new MIUI 7. After flashing miui 7 you can install any rom you wish.
Let me know if your device gets fixed or if you need any help..
Thanks.
not able boot to twrp recovery and even not in system
not able start twrp in my mi4i as system get crashed and now my phone is not booting up just suck in mi logo. plz help not able to start my device and not able flash my device. I think I lose my imei no. because i was trying to change my imei. I have a backup of miui8 by twrp will it help me to start my device. plz help !!!
My mi4i couldn't complete booting,when i try to switch on it will show mi logo and goes to black and again mi logo(mi logo is blinking in a regular interval) the red notification light is also blinking,i tried the mi flash tool ,but the problem is still alive....i was using cm 13 ....somebody please help me
Hello everyone, i have a problem installing twrp officiall from twrp.me and could not find any thread on my problem. None of the img. files will work when i boot from fatstboot, they boot up allright but i can´t do anything, twrp can´t read partitions. View attachment 3638514
From what i can understand my phone is a r7plusf and not r7plusm. And i got the unoficiall twrp from link in post 2 to work so that i was able to backup but it can´t mount cache so i can´t wipe or flash anyway.
So i decided to try to flash cm13 latest nightly with cm recovery 13, but it failed. I made backups of stock recovery via flashfy. Then i made nandroid bakup via twrp unofficial. I then rebooted and Flashed cm recovery With flashify and that worked. I then booted to cm recovery and wiped data/factory reset and it failed and got stuck. I waited for ca 10 min then was able to reboot system and phone was reset and wiped. I rebooted to cm recovery and tried to flash, failing again and bootloop.
Luckily fastboot still worked. I then booted unofficial twrp via fastboot and flashed latest cm nightly, and it failed, it could not find cache, bootloop still. As nothing else worked i thought it was best to restore nandroid, and gues what? Twrp unofficiall got stuck. By now i got a bit nervous. I was able to reboot twrp again via fastboot and this time restore worked, though it took quite some time before restoring actually began. All worked out well and i was able to restore stock recovery agin with flashify. I wonder if i have some odd batch phone???
Thankful for any input...
tommie.r said:
Hello everyone, i have a problem installing twrp officiall from twrp.me and could not find any thread on my problem. None of the img. files will work when i boot from fatstboot, they boot up allright but i can´t do anything, twrp can´t read partitions. View attachment 3638514
From what i can understand my phone is a r7plusf and not r7plusm. And i got the unoficiall twrp from link in post 2 to work so that i was able to backup but it can´t mount cache so i can´t wipe or flash anyway.
So i decided to try to flash cm13 latest nightly with cm recovery 13, but it failed. I made backups of stock recovery via flashfy. Then i made nandroid bakup via twrp unofficial. I then rebooted and Flashed cm recovery With flashify and that worked. I then booted to cm recovery and wiped data/factory reset and it failed and got stuck. I waited for ca 10 min then was able to reboot system and phone was reset and wiped. I rebooted to cm recovery and tried to flash, failing again and bootloop.
Luckily fastboot still worked. I then booted unofficial twrp via fastboot and flashed latest cm nightly, and it failed, it could not find cache, bootloop still. As nothing else worked i thought it was best to restore nandroid, and gues what? Twrp unofficiall got stuck. By now i got a bit nervous. I was able to reboot twrp again via fastboot and this time restore worked, though it took quite some time before restoring actually began. All worked out well and i was able to restore stock recovery agin with flashify. I wonder if i have some odd batch phone???
Thankful for any input...
Click to expand...
Click to collapse
Got this info from app, it says oppo r7 plusm and oppo r7 plusf. confusing...
no sure if you already figured it out but I think u have an R7PlusF with the bootloader of an R7PlusM. go into the development thread of R7Plus and flash the recovery I posted there. Flash my English translation one via Fastboot. I'm 100% sure TWRP will work flawless for you with that version.
oh and edit that screenshot to hide your IMEI! you don't want to give out that information to the Internet ever!
celoxocis said:
no sure if you already figured it out but I think u have an R7PlusF with the bootloader of an R7PlusM. go into the development thread of R7Plus and flash the recovery I posted there. Flash my English translation one via Fastboot. I'm 100% sure TWRP will work flawless for you with that version.
oh and edit that screenshot to hide your IMEI! you don't want to give out that information to the Internet ever!
Click to expand...
Click to collapse
Yes i have thanks to you, and all my problems with twrp has been resolved, and yes it was very clumsy of me to miss emei...
Thanks for the reminder.
Hi,
Just for you to know:
Model: r7plusf
Recovery: TWRP 3.0.2-0
----------------------------------------
So earlier today I did an OTA update (cm-14.1-20161205-NIGHTLY-r7plus.zip), but couldn't get my phone to boot.
So naturally, I tried wiping Cache and ART cache, but was still bootlooping.
Thought there might be someting wrong with my ROM and data, so I formated data and Installed ROM and GAPPS again after ADB pushing them onto my phone.
Now, and although CM14.1 and GAPPS are successfully installed on my Oppo R7 Plus, I can't boot into the OS. Every time I try reboot system, whether through POWER_BUTTON, RECOVERY or ADB, I just boot into Recovery.
Worst of all, for some unknown reason, I can't get into BOOTLOADER, neither through button combination, nor through Recovery nor ADB.
I found this article (http://forum.xda-developers.com/tmobile-lg-g3/general/fix-recovery-loop-twrp-computer-t2873386) in the LG G3 thread about executing some shell commands, but I haven't tested testing it with my phone's variables because it might hard brick it...
Please Help!
[EDIT] I now have access to fastboot but still recovery looping like crazy.
I installed the same update via CyanDelta , worked like a charm ! hopefully you get back up and running.
[UPDATE] strangely I tried to flash stock recovery and boot CM13 and it worked!
Will try to flash twrp again and insall CM14
keep you up to date
Same thing happened to me! Where did you get a copy of the stock recovery? Link?
resverse said:
[UPDATE] strangely I tried to flash stock recovery and boot CM13 and it worked!
Will try to flash twrp again and insall CM14
keep you up to date
Click to expand...
Click to collapse
I had the same problem. Can't remember exactly how I resolved it. But I think, I use CM recovery to flash nightly. Then flash TWRP to flash gapps. For some strange reason, using CM recovery also show no enough disk space whenever I try to flash opengapps. But TWRP recovery can flash opengapps successfully.
Don't use the OTA, use adb sideload to flash the nightly next time. So far, adb sideload has not given me any issue to flash nightly.
Same problem...
I tried a lot of things nothing works and now I've installed the cm recovery but I have the "unauthorized phone" in terminal when I try to flash the ROM... I can do nothing because I can't enable the usb debugging. I don't know what to do.
If somebody can help I appreciate.
corbalan12 said:
Same problem...
I tried a lot of things nothing works and now I've installed the cm recovery but I have the "unauthorized phone" in terminal when I try to flash the ROM... I can do nothing because I can't enable the usb debugging. I don't know what to do.
If somebody can help I appreciate.
Click to expand...
Click to collapse
Since then I found how to fix it :
first of all I flashed cm13 through TWRP,
Then I flashed the stock recovery (Google it, I found it in OPPO forums) with fastboot,
After that I did a factory reset in the stock recovery,
Booted cm13 with stock recovery,
Then re-flashed TWRP,
From TWRP, I wiped both data and system partitions,
Then fresh installed cm14 and Gapps
And it worked!
Not sure if those are the exact steps I followed because all I did was a hole lot of messing around and trying absurd things out, but think this is how I fixed it.
Let me know if it worked for you or if you still can't fix your problem
Best of luck
Resverse
resverse said:
Since then I found how to fix it :
first of all I flashed cm13 through TWRP,
Then I flashed the stock recovery (Google it, I found it in OPPO forums) with fastboot,
After that I did a factory reset in the stock recovery,
Booted cm13 with stock recovery,
Then re-flashed TWRP,
From TWRP, I wiped both data and system partitions,
Then fresh installed cm14 and Gapps
And it worked!
Not sure if those are the exact steps I followed because all I did was a hole lot of messing around and trying absurd things out, but think this is how I fixed it.
Let me know if it worked for you or if you still can't fix your problem
Best of luck
Resverse
Click to expand...
Click to collapse
Thank you very much!!!! I'll try tomorrow and tell you.
I appreciate a lot!
First of all now works but to be honest, I don't know if the way I fix makes sense or if is correct but not for the same reason I do but I'll try to explain...
I had cm-14.1-20161218-NIGHTLY and I tried to update via OTA to 20161220 the phone reboot and I get the bootloop. The first I thought, install again the ROM making wipe data and blabla... nothing work.
I tried to "reflash" the recovery, nothing. Flashed cm recovery, it always gave me error trying to flash the rom. I tried to install with stock recovery, errors too.
I was reading hundred of post looking for my issues, device unauthorized, "error 7" in twrp... I was crazy.
At last I thought, I've been trying to install from SDcard, if I try to install from internal memory? and I install again the twrp to transfer the ROM and Gapps to the internal memory and... it worked!!!!
Long story but with happy ending.
Thank you for your help I appreciate and sorry for my english.First of all now works but to be honest, I don't know if the way I fix makes sense or if is correct but not for the same reason I do but I'll try to explain...
I had cm-14.1-20161218-NIGHTLY and I tried to update via OTA to 20161220 the phone reboot and I get the bootloop. The first I thought, install again the ROM making wipe data and blabla... nothing work.
I tried to "reflash" the recovery, nothing. Flashed cm recovery, it always gave me error trying to flash the rom. I tried to install with stock recovery, errors too.
I was reading hundred of post looking for my issues, device unauthorized, "error 7" in twrp... I was crazy.
At last I thought, I've been trying to install from SDcard, if I try to install from internal memory? and I install again the twrp to transfer the ROM and Gapps to the internal memory and... it worked!!!!
Long story but with happy ending.
Thank you for your help I appreciate and sorry for my english.
hey folks, yesterday i flashed a new rom, during flash i got an error (dont rember which one). i flashed a few other roms didnt work also, so i flashed a new recovery. i rebooted to recovery but i dont get anything except the oneplus logo. i dont have a recovery or os. i can get into fastboot. i already flashed a few recoverys with fastboot. my recovery flashed succesful with fastboot. the problem is i cant boot into recovery. not with commands with fastboot, not with the volume buttons. so please help me because my phone is unsuable now.
i used this guide (i cant post links) so youve just bricked your oneplus one, reddit
i did all the steps of soft brick cant acces recovery. everything goes succesfully except booting to recovery.
nathan_b87 said:
hey folks, yesterday i flashed a new rom, during flash i got an error (dont rember which one). i flashed a few other roms didnt work also, so i flashed a new recovery. i rebooted to recovery but i dont get anything except the oneplus logo. i dont have a recovery or os. i can get into fastboot. i already flashed a few recoverys with fastboot. my recovery flashed succesful with fastboot. the problem is i cant boot into recovery. not with commands with fastboot, not with the volume buttons. so please help me because my phone is unsuable now.
i used this guide (i cant post links) so youve just bricked your oneplus one, reddit
i did all the steps of soft brick cant acces recovery. everything goes succesfully except booting to recovery.
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B-ikULjZZlloNHpOdVBrTzQxZzQ/view
Download This file, install it somewhere and run Revert-2-CM.exe. Make sure you have fastboot drivers installed or it wont work.Disable any antivirus otherwise you'll get false alarms.The program should automatically boot your device to recovery.
im amazing
wow im so glad. i unzipped a rom and flashed each file one by one and it works its fixed!!
Hey Guys,
so i got a wierd bootloop problem and for now i didn't find any solution here on xda or somewhere else,
not even a thread where someone has the same problem.
I'll try to give you as much information as possible in a chronological order.
First of all I got the international model (G920F).
So like 2-3 months ago everything was fine, my phone was rooted, got TWRP working and was flashing Roms with no problem what so ever. TW-Roms like Noble Rom and also AOSP/Lineage OS.
One day I wanted to flash UltImAtE NoUgAt A8 Port and that is where the trouble began, dont think it has something to do with the rom but maybe it helps.
So i flashed the Rom(wiped everything except int. storage), flashing was no problem but it didnt boot.
I know first boot always takes some time but after about 20-30 min I forced a reboot (Power+Vol. Down for 7sec).
After that the phone got into a Bootloop(always rebooted into the "first bootingscreen")
I let this process happen for about 15 min. and then tried to enter TWRP via hitting the buttons between the boots which didn't work. I then did "force" a reboot(Power + Vol. Down) which strangely resulted in one final reboot and turning the phone off after the first bootscreen.
So with the phone finally turned off I was able to boot into TWRP and reflashed the rom but the result was the same.
I did the same procedure again to get into TWRP and flashed the Stock Deodexed TW Rom, flashing worked but then the Phone directly rebooted into TWRP. Rebooting out of TWRP or booting the phone from beeing shut down both resulting into booting to TWRP.
So to get my Phone working again I had to flash stock ROM which in my case is G920FXXU5EQDF_G920FDBT5EQD1_G920FXXU5EQCD via Odin.
That worked but of course root and TWRP were gone so I then flashed TWRP via Odin(both newest Versions at that point)
aaaaaand phone straightly booted into TWRP again all the time. I tried different combinations of older versions of both twrp and odin but the result always was the same.
So at the moment I am on Stock, the phone works which is nice but i really wanna get TWRP working again and i have no idea what to do.
I hope someone can help me with that.
Cheers Guys
MuTec said:
Hey Guys,
so i got a wierd bootloop problem and for now i didn't find any solution here on xda or somewhere else,
not even a thread where someone has the same problem.
I'll try to give you as much information as possible in a chronological order.
First of all I got the international model (G920F).
So like 2-3 months ago everything was fine, my phone was rooted, got TWRP working and was flashing Roms with no problem what so ever. TW-Roms like Noble Rom and also AOSP/Lineage OS.
One day I wanted to flash UltImAtE NoUgAt A8 Port and that is where the trouble began, dont think it has something to do with the rom but maybe it helps.
So i flashed the Rom(wiped everything except int. storage), flashing was no problem but it didnt boot.
I know first boot always takes some time but after about 20-30 min I forced a reboot (Power+Vol. Down for 7sec).
After that the phone got into a Bootloop(always rebooted into the "first bootingscreen")
I let this process happen for about 15 min. and then tried to enter TWRP via hitting the buttons between the boots which didn't work. I then did "force" a reboot(Power + Vol. Down) which strangely resulted in one final reboot and turning the phone off after the first bootscreen.
So with the phone finally turned off I was able to boot into TWRP and reflashed the rom but the result was the same.
I did the same procedure again to get into TWRP and flashed the Stock Deodexed TW Rom, flashing worked but then the Phone directly rebooted into TWRP. Rebooting out of TWRP or booting the phone from beeing shut down both resulting into booting to TWRP.
So to get my Phone working again I had to flash stock ROM which in my case is G920FXXU5EQDF_G920FDBT5EQD1_G920FXXU5EQCD via Odin.
That worked but of course root and TWRP were gone so I then flashed TWRP via Odin(both newest Versions at that point)
aaaaaand phone straightly booted into TWRP again all the time. I tried different combinations of older versions of both twrp and odin but the result always was the same.
So at the moment I am on Stock, the phone works which is nice but i really wanna get TWRP working again and i have no idea what to do.
I hope someone can help me with that.
Cheers Guys
Click to expand...
Click to collapse
You do know that if you flash TWRP, you need to use a kernel that has dm-verity disabled or you need to be rooted. Flash TWRP then Flash Magisk through TWRP
U99Dev said:
You do know that if you flash TWRP, you need to use a kernel that has dm-verity disabled or you need to be rooted. Flash TWRP then Flash Magisk through TWRP
Click to expand...
Click to collapse
As it seems I did not, good thing that its written right at the TWRP download page...
Can't remember doing this when I installed TWRP first but as it seems I did.
Everything is working fine, just flashed Nexus OS and it booted.
Thank you so much dude