Related
I unlocked bootloader and rooted last night fine, this morning i was trying to flash cmod 10.2 through twrp and it said could not find md5 when flashing then it said it was flashed successfully. I did wipe the cache and dalvik and did a factory reset prior to attempting to flash. Yet when i hit reboot it only shows the google logo then the screen goes black and flickers between dark black and black. I know it takes time to boot the first time so i let it sit for 10 mins and nothing. Everything was working fine before this, the device still boots into fastboot mode and and i can get to twrp anything i can try through that ? Or is efants guide the only way to fix this. No Nandroid backup so ya i hate myself :crying:
BrownPride said:
I unlocked bootloader and rooted last night fine, this morning i was trying to flash cmod 10.2 through twrp and it said could not find md5 when flashing then it said it was flashed successfully. I did wipe the cache and dalvik and did a factory reset prior to attempting to flash. Yet when i hit reboot it only shows the google logo then the screen goes black and flickers between dark black and black. I know it takes time to boot the first time so i let it sit for 10 mins and nothing. Everything was working fine before this, the device still boots into fastboot mode and and i can get to twrp anything i can try through that ? Or is efants guide the only way to fix this. No Nandroid backup so ya i hate myself :crying:
Click to expand...
Click to collapse
Couple of things I would try first, re download CM 10.2 just to make sure you don't have a bad download and make sure you downloaded the correct file. Due your normal wipes then reflash. btw I never check the md5 box when flashing with TWRP. As long as you can get into recovery you should able to fix and always make a back up.
Ok i will give your suggestions a try and post back in a bit. Thanks for your help
If it's the CM10.2 nightly from 20130906, it's a known issue with it not booting. Flash an older nightly or another ROM.
I was unaware of the issues with this versioni thanks for that info. I can not push the zip file through adb i says device is offline, is there anyway to push the older cmod version through fastboot and install it with twrp on device ?
I miss having a device with a removable sdcard
BrownPride said:
I was unaware of the issues with this versioni thanks for that info. I can not push the zip file through adb i says device is offline, is there anyway to push the older cmod version through fastboot and install it with twrp on device ?
I miss having a device with a removable sdcard
Click to expand...
Click to collapse
Yup use adb sideload in TWRP : adb sideload path to rom/namerom.zip. Link http://teamw.in/ADBSideload.
Thank you for your response, going to follow the steps in the link hopefully i can solve this problem
Thank you all for your kind help and patience i was able to get cmod20130905 to flash through adb sideload and everything is working fine. First thing i did after it booted successfully was go back into twrp and make a backup Thanks again
Hi Guys,
I'm Kinda new about making a new thread, so if anything's wrong let me know.
Just last evening my nexus 6p (on Android 7.0 official) got into a boot loop from a normal state. It just boots & right after when the white google logo transforms into 4 round object, it just reboots (it takes about 3-5 secs). I can access the boot loader but was unable to access to recovery from there as that takes it to bootloop again. I've tried flashing it, but since i had already updated to Nougat official version & the official image for 6p is yet to come, i tried with some earlier version of Marshmallow. but that failed as well. can it be that i need to select the right version of factory image as i really do not remember my old marshmallow versions anymore.
It seems i'm out of options right now. :crying:
Any advice guys??
TIA
Found this on Nexus 6p help forum. Haven't tried it though so I'm unable to confirm if it works or not.
https://productforums.google.com/forum/#!topic/nexus/hdrNONCCoNE
@sirluigi, this EXACT thing just happened to me ..
stock nougat, only bootloader unlocked ((( and since I've got no access to recovery and no Nougat image, I don't know what to do next
minicoop7, unfortunately, for that guide I need to go into recovery mode
ciocu said:
@sirluigi, this EXACT thing just happened to me ..
stock nougat, only bootloader unlocked ((( and since I've got no access to recovery and no Nougat image, I don't know what to do next
minicoop7, unfortunately, for that guide I need to go into recovery mode
Click to expand...
Click to collapse
Have you tried using fastboot to temp boot to recovery?
fastboot boot twrp-3.0.2-1-angler.img
downloading 'boot.img'...
OKAY [ 0.409s]
booting...
OKAY [ 0.680s]
finished. total time: 1.097s
Click to expand...
Click to collapse
same behavior, nothing but a bootloop
I'm dowloading an official MM image, just to get the stock recovery and see if I can temp boot in it
edit: not possible, I even tried to flash twrp, I tried flashing stock recovery from MTC20F.. tried to temp boot in both, all with no luck and with phone constantly alternating between the "Your device cannot be checked for corruption" screen and the white Google screen with the open lock.
sirluigi said:
Hi Guys,
I'm Kinda new about making a new thread, so if anything's wrong let me know.
Just last evening my nexus 6p (on Android 7.0 official) got into a boot loop from a normal state. It just boots & right after when the white google logo transforms into 4 round object, it just reboots (it takes about 3-5 secs). I can access the boot loader but was unable to access to recovery from there as that takes it to bootloop again. I've tried flashing it, but since i had already updated to Nougat official version & the official image for 6p is yet to come, i tried with some earlier version of Marshmallow. but that failed as well. can it be that i need to select the right version of factory image as i really do not remember my old marshmallow versions anymore.
It seems i'm out of options right now. :crying:
Any advice guys??
TIA
Click to expand...
Click to collapse
Guys its very simple, flash the stock mtc20f image first. After that boot it, it wont work but don't worry. Onece it bootloops go into bootloader and fastboot flash twrp 3.0.2-0. once thats done boot into twrp recovery. Onece in twrp make a backup of the image you just flashed that don't work. Once thats done mount system in recovery. Once mounted plug phone into computer and open the twrp folder you will see on your internal wich will have the backup that you just made. Transfer an old working backup into that folder that way twrp will recognize that backup. Once the backup is in the folder you shoukd see 2 backups in there, your new one that doesn't boot and your old one that does work wich you just put into the twrp folder. Once done go to restore and restore the backup of the working rom you just put in there, make sure to check off all on restore. Once done reboot system and it should boot. This will only work if you have a backup of an old working rom.
---------- Post added at 01:13 AM ---------- Previous post was at 01:00 AM ----------
sirluigi said:
Hi Guys,
I'm Kinda new about making a new thread, so if anything's wrong let me know.
Just last evening my nexus 6p (on Android 7.0 official) got into a boot loop from a normal state. It just boots & right after when the white google logo transforms into 4 round object, it just reboots (it takes about 3-5 secs). I can access the boot loader but was unable to access to recovery from there as that takes it to bootloop again. I've tried flashing it, but since i had already updated to Nougat official version & the official image for 6p is yet to come, i tried with some earlier version of Marshmallow. but that failed as well. can it be that i need to select the right version of factory image as i really do not remember my old marshmallow versions anymore.
It seems i'm out of options right now. :crying:
Any advice guys??
TIA
Click to expand...
Click to collapse
OMG I finally got mine to work
I'll note down the exact steps , most of which may or may not be relevant
1) Flashed MTC20F using TWRP 3.0.2-1
2) Booted into recovery and wiped everything and the partitions
- Add - Booted back into twrp 3.0.2-1 and then swiped to allow modifications
3) Then fastboot flashed TWRP 3.0.2-0
4) Restored my backup ( except recovery)
5) Still got stuck in the google screen.
Now the next parts are a bit weird
6) Booted into TWRP, flashed vendor.img from pure nexus rom
7) wiped everything except internal storage
8) Flashed vendor.img, pure nexus rom and gapps and then flashed vendor.img again
9) Rebooted and it worked
Let me know if it worked for you guys or if you need any more help
disbeyad999989 said:
Guys its very simple, flash the stock mtc20f image first. After that boot it, it wont work but don't worry. Onece it bootloops go into bootloader and fastboot flash twrp 3.0.2-0. once thats done boot into twrp recovery. Onece in twrp make a backup of the image you just flashed that don't work. Once thats done mount system in recovery. Once mounted plug phone into computer and open the twrp folder you will see on your internal wich will have the backup that you just made. Transfer an old working backup into that folder that way twrp will recognize that backup. Once the backup is in the folder you shoukd see 2 backups in there, your new one that doesn't boot and your old one that does work wich you just put into the twrp folder. Once done go to restore and restore the backup of the working rom you just put in there, make sure to check off all on restore. Once done reboot system and it should boot. This will only work if you have a backup of an old working rom.
---------- Post added at 01:13 AM ---------- Previous post was at 01:00 AM ----------
OMG I finally got mine to work
I'll note down the exact steps , most of which may or may not be relevant
1) Flashed MTC20F using TWRP 3.0.2-1
2) Booted into recovery and wiped everything and the partitions
- Add - Booted back into twrp 3.0.2-1 and then swiped to allow modifications
3) Then fastboot flashed TWRP 3.0.2-0
4) Restored my backup ( except recovery)
5) Still got stuck in the google screen.
Now the next parts are a bit weird
6) Booted into TWRP, flashed vendor.img from pure nexus rom
7) wiped everything except internal storage
8) Flashed vendor.img, pure nexus rom and gapps and then flashed vendor.img again
9) Rebooted and it worked
Let me know if it worked for you guys or if you need any more help
Click to expand...
Click to collapse
Unfortunately, this didn't work for me.
I believe you should be fine with just trying to flash an earlier recovery version using fastboot... if you're trying to save your data and then factory flash MM and then restore your data to the phone, you should be able to use fastboot pull and then copy them back once you've got a working device by simple copy from windows.
disbeyad999989 said:
Guys its very simple, flash the stock mtc20f image first. After that boot it, it wont work but don't worry. Onece it bootloops go into bootloader and fastboot flash twrp 3.0.2-0. once thats done boot into twrp recovery. Onece in twrp make a backup of the image you just flashed that don't work. Once thats done mount system in recovery. Once mounted plug phone into computer and open the twrp folder you will see on your internal wich will have the backup that you just made. Transfer an old working backup into that folder that way twrp will recognize that backup. Once the backup is in the folder you shoukd see 2 backups in there, your new one that doesn't boot and your old one that does work wich you just put into the twrp folder. Once done go to restore and restore the backup of the working rom you just put in there, make sure to check off all on restore. Once done reboot system and it should boot. This will only work if you have a backup of an old working rom.
---------- Post added at 01:13 AM ---------- Previous post was at 01:00 AM ----------
OMG I finally got mine to work
I'll note down the exact steps , most of which may or may not be relevant
1) Flashed MTC20F using TWRP 3.0.2-1
2) Booted into recovery and wiped everything and the partitions
- Add - Booted back into twrp 3.0.2-1 and then swiped to allow modifications
3) Then fastboot flashed TWRP 3.0.2-0
4) Restored my backup ( except recovery)
5) Still got stuck in the google screen.
Now the next parts are a bit weird
6) Booted into TWRP, flashed vendor.img from pure nexus rom
7) wiped everything except internal storage
8) Flashed vendor.img, pure nexus rom and gapps and then flashed vendor.img again
9) Rebooted and it worked
Let me know if it worked for you guys or if you need any more help
Click to expand...
Click to collapse
Can you elaborate the steps pls? also have you had an earlier back up of your phone which i don't have?
Has anyone been able to get this to work without being able to get into TWRP? I can't get into recovery whether it is a temp boot to it, or fastboot flash either version..
I have compiled a list of the 20+ methods from various users in THIS thread. It's the second post.
Stuck in a bootloop still @tr4nqui1i7y but will try your methods as well... Fingers crossed..
So I do not if this may help anyone who as run into this issue but still may want to retrieve their data before formating their data or factory resetting. While running TWRP 3.0.3 and flashing the latest 7.1.1 files for angler. I would sometimes be able to boot into the recovery like 3/10 tries ( from the bootloader menu). My data was encrypted and it woul freeze constantly when trying to decrypt soo i decided once I finally got it to boot again in the recovery menu(TWRP after hours mind you) I let the phone stay idle for a few mins should the cpu would cool down that my battery percentage would drop around 41% and the tried to decrypt data which went tru successfully. I retrieve what I Could and it froze during a process of a nandroid backup and started bootlooping again. I believe the battery percentage may be linked to the early shutdown issues that many user were reported having and the bootloop of death we are experiencing. Hopefully this info may help someone else.
Hi,
So I have created this thread just because I can see many people creating new threads as after flashing CM 14.1, their phone doesn't boot up. So for all those who are going to flash CM 14.1 or have already flashed it and can't get it working, this thread is for you.
What you will need:
1. Rooted OnePlus X (Obviously)
2. Custom Recovery (TWRP recommended)
3. Latest CM 14.1 build
4. Arsenic Kernel or BlackReactor Kernel
So this is how you get CM 14.1 working on your OPX (make sure your battery is above 80% just to be sure that nothing will go wrong considering battery's point of view)
Make sure you have backed up everything before performing the following steps as the process will wipe your data completely. (I would recommend to take a Titanium backup of all user apps and then taking a nandroid backup of system and data)
1. Download the required files and place them in your SD Card or internal storage
2. Reboot your device into recovery
3. Go to wipe, and swipe to factory reset (Note! This will completely wipe all the data from your device including app data and SMS! This won't wipe the contacts but just to be safe, have a backup of all your contacts)
4. Go to Wipe again, and go to Advanced wipe, select the following partitions - System, Cache, Dalvik cache. Swipe to wipe (Note! Make sure you have a backup of the System as this will wipe the Operating System from your phone!) Although this step isn't necessary, I like to do it.
5. Go to install, and direct to the location where you have saved the CM 14.1 zip file and the kernel. Select the files, and swipe to flash.
6. If you want anything else in your system, direct to that location, select the zip file, and swipe to flash. (Note! You need not flash the SuperSU zip file as CM offers Root access in developer options)
7. Reboot your system and wait for it to boot.
Viola! Your device is now running official CM 14.1 nightly.
Hope this helps! ?
Downloads:
1. Latest CyanogenMod nightly - found here https://download.cyanogenmod.org/?device=onyx
You can have any version of the nightly as long as it is CM 14.1
2. Arsenic Kernel R32 (or R31) - http://forum.xda-developers.com/oneplus-x/development/kernel-arsenic-kernel-r2-t3422020
Open the above thread and follow the guide
OR
Black Reactor kernel v1.0 - http://forum.xda-developers.com/oneplus-x/development/kernel-blackreactor-kernel-oneplus-x-t3460989
-Reserved-
Good Evening, @aamodjoshi23 THX a Lot. You are my Hero. Finally it works.
greetings
If you're facing some Error 7 while trying to flash cm 14.1, you can try updating the bootloader following this
http://forum.xda-developers.com/showpost.php?p=69267239&postcount=2560
I used the Oxygen OS 3.13 full ROM as recommended, edited updater-script (following those instructions)
Immediately after flashing the OOS 3.13 rom, you don't have to reboot.
I immediately flashed twrp 3.0.3 original from https://dl.twrp.me/onyx/
I then rebooted into twrp 3.0.3 (using the reboot button in twrp, then bootloader)
Then I installed (in this order):
cm 14.1 (https://download.cyanogenmod.org/?device=onyx)
arsenic kernel (as recommended above)
opengapps
Not sure if this step is necessary, but I wanted to let twrp patch the rom to not overwrite twrp so I rebooted into twrp again (using reboot --> bootloader in twrp)
Then I used reboot --> system
First boot took a while, but now I have nougat!!
kenel zip every time
Do i need to flash the kenel zip every time I update the the cm 14.1 zip file?
allons-y said:
Do i need to flash the kenel zip every time I update the the cm 14.1 zip file?
Click to expand...
Click to collapse
Yes, as when you flash the CM 14.1 build, the kernel that is provided with the build is also flashed, and that is not supported. So you need to flash it every time you flash a CM 14.1 build, but if you want to flash any other build, something like CM 13.0, then you need not as the kernels provided in those are supported.
aamodjoshi23 said:
Yes, as when you flash the CM 14.1 build, the kernel that is provided with the build is also flashed, and that is not supported. So you need to flash it every time you flash a CM 14.1 build, but if you want to flash any other build, something like CM 13.0, then you need not as the kernels provided in those are supported.
Click to expand...
Click to collapse
Hi,
I have a very specific problem. I rooted my Oneplus x few months back and everything was fine. I use to get update notifications and after downloading it use to update automatically. But since last 2 months i download the update files but it takes me to recovery and then i cant find the zip file to flash/install. (i also started using external sd card two months back, but not sure if it has to do anything with this). I tried searching a solution on web - tried checking 'system' under Mount tab, installed an app for auto update and some more but no use. I even connected my phone in recovery mode to laptop and copied the zip file to internal memory but while flashing it gave error.
Now i am not sure what the problem is. Do i need to update my recovery or something else. Pls help.
shashanksachdeva said:
Hi,
I have a very specific problem. I rooted my Oneplus x few months back and everything was fine. I use to get update notifications and after downloading it use to update automatically. But since last 2 months i download the update files but it takes me to recovery and then i cant find the zip file to flash/install. (i also started using external sd card two months back, but not sure if it has to do anything with this). I tried searching a solution on web - tried checking 'system' under Mount tab, installed an app for auto update and some more but no use. I even connected my phone in recovery mode to laptop and copied the zip file to internal memory but while flashing it gave error.
Now i am not sure what the problem is. Do i need to update my recovery or something else. Pls help.
Click to expand...
Click to collapse
First of all we need more info about your current ROM recovery etc.
Fap4k said:
First of all we need more info about your current ROM recovery etc.
Click to expand...
Click to collapse
I installed CM 13.0-20160928-NIGHTLY-onyx and the recovery is: TWRP v2.8.7.0 | blu_spark r8
I'll be grateful for a solution.
shashanksachdeva said:
I installed CM 13.0-20160928-NIGHTLY-onyx and the recovery is: TWRP v2.8.7.0 | blu_spark r8
I'll be grateful for a solution.
Click to expand...
Click to collapse
In October oneplus updated to 6.0.1 officially i.e OOS 3 it brings new bootloader to the device as you are using old recovery you can't flash new update..so you need to upgrade to latest bootloader by following thread available in general section or you can flash stock recovery and upgrade to latest OOS and flash whatever you want to flash..I recommend you to see how to upgrade bootloader in general section if you are planning to flash custom ROMs or if want to flash latest OOS then simply flash stock recovery and upgrade. onece you updated to OOS 3 after that you can flash new official twrp 3.0.3.0 from its official page.
Edit: for old bootloader you need stock 5.1.1 recovery..which is not available in official oneplus download page..so just follow below link
https://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Fap4k said:
In October oneplus updated to 6.0.1 officially i.e OOS 3 it brings new bootloader to the device as you are using old recovery you can't flash new update..so you need to upgrade to latest bootloader by following thread available in general section or you can flash stock recovery and upgrade to latest OOS and flash whatever you want to flash..I recommend you to see how to upgrade bootloader in general section if you are planning to flash custom ROMs or if want to flash latest OOS then simply flash stock recovery and upgrade. onece you updated to OOS 3 after that you can flash new official twrp 3.0.3.0 from its official page.
Edit: for old bootloader you need stock 5.1.1 recovery..which is not available in official oneplus download page..so just follow below link
https://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Click to expand...
Click to collapse
I made a blunder. I read somewhere to upgrade TWRP to 3.0.3 and after doing that now i just can't access the recovery mode. When i try to boot in recovery mode the screen gets stuck with One+ logo. Then I even tried to Factory reset and the phone rebooted to the same screen stuck with logo. I longed pressed the power button and it got switched off and then again turned it on. It started and is working fine but I cant factory set it, nor cant I access recovery to flash anything.
shashanksachdeva said:
I made a blunder. I read somewhere to upgrade TWRP to 3.0.3 and after doing that now i just can't access the recovery mode. When i try to boot in recovery mode the screen gets stuck with One+ logo. Then I even tried to Factory reset and the phone rebooted to the same screen stuck with logo. I longed pressed the power button and it got switched off and then again turned it on. It started and is working fine but I cant factory set it, nor cant I access recovery to flash anything.
Click to expand...
Click to collapse
This is because you flashed wrong recovery twrp 3.0.3 is for new bootloader and you are on old bootloader..that's why it all happened..so you just need to flash old recovery..then follow given link to upgrade bootloader and recovery.
shashanksachdeva said:
I made a blunder. I read somewhere to upgrade TWRP to 3.0.3 and after doing that now i just can't access the recovery mode. When i try to boot in recovery mode the screen gets stuck with One+ logo. Then I even tried to Factory reset and the phone rebooted to the same screen stuck with logo. I longed pressed the power button and it got switched off and then again turned it on. It started and is working fine but I cant factory set it, nor cant I access recovery to flash anything.
Click to expand...
Click to collapse
I've got a good news and bad news for you.
The bad news is, no one has the older 2.8.x TWRP image files and there are no threads that have the download links for the older version of TWRP. So you're stuck and you have lost your recovery. You have lost everything... Having no recovery means you can't do a lot of things like factory reset, any wipe of a partition, you won't be able to update your system, you won't be able to flash zip files to enhance your experience and many more... I'm sorry my friend...
The good news is, I've got you covered. I had saved the older TWRP so that if anyone one day would need that recovery image, I would be able to help them.
Download the older TWRP from here : https://drive.google.com/file/d/0B2Ms-zaNd3SiTmpxX0UtYUV2R1k/view?usp=drivesdk
Flash it. You should get back your recovery.
e: unknown command (log)
e: unknown command (log)
am not able to make my device android 7.0 running...
i tryed and install kernal after that but no luck, stuck on boot only 1 plus logo will appear, please recommend any solution.
Plush suthar said:
e: unknown command (log)
e: unknown command (log)
am not able to make my device android 7.0 running...
i tryed and install kernal after that but no luck, stuck on boot only 1 plus logo will appear, please recommend any solution.
Click to expand...
Click to collapse
Which ROM you are on currently?
If possible post screenshot of about device in setting.
Fap4k said:
Which ROM you are on currently?
If possible post screenshot of about device in setting.
Click to expand...
Click to collapse
using resurrection remix marshmallow 6.0...
Plush suthar said:
using resurrection remix marshmallow 6.0...
Click to expand...
Click to collapse
Did you ever updated bootloader?
If not than update your bootloader and install latest recovery!!
Plush suthar said:
e: unknown command (log)
e: unknown command (log)
am not able to make my device android 7.0 running...
i tryed and install kernal after that but no luck, stuck on boot only 1 plus logo will appear, please recommend any solution.
Click to expand...
Click to collapse
By stuck on boot, I didn't know you meant that it showed only the OnePlus logo and not even powered by Android.
In that case, follow this guide to update your bootloader :
https://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
I had rooted my phone by unlocking the bootloader using adb fastboot method, then flashing the TWRP revocery V2.8.7.0, and then flashing superSU v2.46.
After rebooting my yureka plus, and going to recovery it started cynogen recovery only, even though update cynogen recovery option was disabled.
So I flashed TWRP again and without rebooting again, just flashed crDroidAndroid-6.0.1-20160827-tomato.zip and GApps zip file from internal memory. The phone rebooted and worked fine after that..
but while playing a game the phone automatically rebooted and ever since have been stuck on Preparing to start.. Starting apps..
I had disabled the developer options because I thought it was working fine.
The phone is working behind the preparing to start screen.. I can hear the message notification and caller ringtone when someone messages or calls.
Any suggestions what I should do now? I have tried doing a factory reset from recovery but the problem persists.
khushboop said:
I had rooted my phone by unlocking the bootloader using adb fastboot method, then flashing the TWRP revocery V2.8.7.0, and then flashing superSU v2.46.
After rebooting my yureka plus, and going to recovery it started cynogen recovery only, even though update cynogen recovery option was disabled.
So I flashed TWRP again and without rebooting again, just flashed crDroidAndroid-6.0.1-20160827-tomato.zip and GApps zip file from internal memory. The phone rebooted and worked fine after that..
but while playing a game the phone automatically rebooted and ever since have been stuck on Preparing to start.. Starting apps..
I had disabled the developer options because I thought it was working fine.
The phone is working behind the preparing to start screen.. I can hear the message notification and caller ringtone when someone messages or calls.
Any suggestions what I should do now? I have tried doing a factory reset from recovery but the problem persists.
Click to expand...
Click to collapse
Try flashing it with stock rom or simple wipe the whole system and cache from twrp from advance wipe option ( but backup first ) and again flash the custom rom u used previously.
sk.shehbaz said:
Try flashing it with stock rom or simple wipe the whole system and cache from twrp from advance wipe option ( but backup first ) and again flash the custom rom u used previously.
Click to expand...
Click to collapse
It still opens in cyanogen recovery only, and there is no option for wiping dalvik cache or system. Since the usb debugging is of,f I cannot used cmd to flash twrp recovery again. By the way I still don't understand why twrp recovery is not loading.
khushboop said:
It still opens in cyanogen recovery only, and there is no option for wiping dalvik cache or system. Since the usb debugging is of,f I cannot used cmd to flash twrp recovery again. By the way I still don't understand why twrp recovery is not loading.
Click to expand...
Click to collapse
Get into fastboot and flash the stock rom via fastboot method.
I hope this guide can help u out
http://www.thetechnotriad.com/393/how-to-unbrick-yu-yureka/
sk.shehbaz said:
Get into fastboot and flash the stock rom via fastboot method.
I hope this guide can help u out
thetechnotriad.com/393/how-to-unbrick-yu-yureka/
Click to expand...
Click to collapse
Phone's hard bricked now.. even though I downloaded the flashing tools for lollipop from YUPlayGod's github page.
khushboop said:
Phone's hard bricked now.. even though I downloaded the flashing tools for lollipop from YUPlayGod's github page.
Click to expand...
Click to collapse
I still have no idea why it got bricked. So after searching on google and youtube I came across this: https://androidmtk.com/download-yu-stock-rom-for-all-models . I followed the steps and now KitKat is running except launcher is not working, instead play store open's every time I try to go to home screen. So tried the nova launcher but that still doesn't work with home button, have to open through playstore->my apps, every time. But rest is working.
sk.shehbaz said:
Get into fastboot and flash the stock rom via fastboot method.
I hope this guide can help u out
http://www.thetechnotriad.com/393/how-to-unbrick-yu-yureka/
Click to expand...
Click to collapse
dude!! i tried the above method and thankfully my phone is working now the only major problem now is whatsapp is not opening...when clicked opens for 0.01 sec and returns back to previous screen (flashes) ....please somebody help me with this. Anybody can help me, Thanks in Advance.
I seem to have hard bricked my 9T after flashing the MIUI 11 rom from xiaomi.eu. I think culprit is a totally botched/corrupted boot loader and I have no idea how it happened. I've tried reflashing back to stock through stock image .bat files, but no dice. It flashed everything but the device still refuses to boot past the MI screen. If I try to boot into TWRP, my device gets stuck at the TWRP splash screen, no matter which version it is. Does anyone know what I can do or try at this point? Thanks.
So do I, first time I successfully instal first beta v25 miui 11, and than when the v26 comes, stupidly, i flash it from twrp, it tells me that i succeed installing that zip, and than i wipe art and cache and reboot system, but what next i know, my phone brick, i can not instal anyrom, from mi flash tool, or from anywhere. I did everything and still can not fix the problem.
Anyway, you still can enterin TWRP UI, after waiting about 10 to 30 minutes, because after intalling that rom, automatically your data format change from ext4 to f2fs, and twrp will need a lot of time to read your disk.
But, even after doing anything in twrp, still can not make my phone successfully boot into system.
And theres moun I/O error everytime i tried to wipe everything, or fix disk, or change disk format. Everything... and i just dont know what to do anymore.
So may be you can wait patiently until you can entering twrp ui, and please lemme know if you know how to fix this problem
Soapy! said:
I seem to have hard bricked my 9T after flashing the MIUI 11 rom from xiaomi.eu. I think culprit is a totally botched/corrupted boot loader and I have no idea how it happened. I've tried reflashing back to stock through stock image .bat files, but no dice. It flashed everything but the device still refuses to boot past the MI screen. If I try to boot into TWRP, my device gets stuck at the TWRP splash screen, no matter which version it is. Does anyone know what I can do or try at this point? Thanks.
Click to expand...
Click to collapse
i have experience that, then i flash the twrp chinese version and it works.
@flamedrops which one if i may know? I tried 3.3.1-0916-redmi_k20-CN and still not work ?
Soapy! said:
I seem to have hard bricked my 9T after flashing the MIUI 11 rom from xiaomi.eu. I think culprit is a totally botched/corrupted boot loader and I have no idea how it happened. I've tried reflashing back to stock through stock image .bat files, but no dice. It flashed everything but the device still refuses to boot past the MI screen. If I try to boot into TWRP, my device gets stuck at the TWRP splash screen, no matter which version it is. Does anyone know what I can do or try at this point? Thanks.
Click to expand...
Click to collapse
I got exactly the same problem after installing miui 11rom. Installing firmware via fastboot was unsuccessful. God, help us ...
---------- Post added at 07:44 AM ---------- Previous post was at 07:33 AM ----------
Arif Ferdian said:
So do I, first time I successfully instal first beta v25 miui 11, and than when the v26 comes, stupidly, i flash it from twrp, it tells me that i succeed installing that zip, and than i wipe art and cache and reboot system, but what next i know, my phone brick, i can not instal anyrom, from mi flash tool, or from anywhere. I did everything and still can not fix the problem.
Anyway, you still can enterin TWRP UI, after waiting about 10 to 30 minutes, because after intalling that rom, automatically your data format change from ext4 to f2fs, and twrp will need a lot of time to read your disk.
But, even after doing anything in twrp, still can not make my phone successfully boot into system.
And theres moun I/O error everytime i tried to wipe everything, or fix disk, or change disk format. Everything... and i just dont know what to do anymore.
So may be you can wait patiently until you can entering twrp ui, and please lemme know if you know how to fix this problem
Click to expand...
Click to collapse
Just the exact same problem as mine. If you know anything about how to solve this problem, please tell us.
I had the same problem with a miui 10 weekly beta but unfortunately I wasn't able to fix it but lucky me my phone was still in a return period so I returned it back to Amazon and got my money back since then I have always stayed away from beta ROMs . I tried everything but it wasn't booting pass the mi logo as you said
flamedrops said:
i have experience that, then i flash the twrp chinese version and it works.
Click to expand...
Click to collapse
Benfatica said:
I had the same problem with a miui 10 weekly beta but unfortunately I wasn't able to fix it but lucky me my phone was still in a return period so I returned it back to Amazon and got my money back since then I have always stayed away from beta ROMs . I tried everything but it wasn't booting pass the mi logo as you said
Click to expand...
Click to collapse
Ahhhh yes, i was thinking to using my guaranteed card, as i still can relock bootliader with mi flash tools, already trying anything for couples day with zero result, and im giving up hahaha
Arif Ferdian said:
Ahhhh yes, i was thinking to using my guaranteed card, as i still can relock bootliader with mi flash tools, already trying anything for couples day with zero result, and im giving up hahaha
Click to expand...
Click to collapse
did you really reboot it using adb reboot twrp? and reboot system on twrp using twrp cn version?
Yap @flamedrops i already do, and even tried all the TWRP version that exist, and also reflash many Rom, from stock, eu, ct, aosp, miui 11 25, miui 11 26, i flash from adb sideload, from twrp via usb otg, via miflash tool,
I flash boot.img, etc
Still no result.
Already tried everything that i could thinking about
flamedrops said:
did you really reboot it using adb reboot twrp? and reboot system on twrp using twrp cn version?
Click to expand...
Click to collapse
This LR. TEAM is twrp cn version right? And in fact, this version hardly booting to twrp ui version after this problem, easier to entering twrp ui with the ugly themed greek version
Arif Ferdian said:
This LR. TEAM is twrp cn version right? And in fact, this version hardly booting to twrp ui version after this problem, easier to entering twrp ui with the ugly themed greek version
Click to expand...
Click to collapse
ok, yes thats it. have you tried to flash magisk?
@flamedrops not yet, i never tried to flash magisk yet, ill tried next time i could pass twrp splash screen
flamedrops said:
i have experience that, then i flash the twrp chinese version and it works.
Click to expand...
Click to collapse
Can you list your steps to fix this? My data and cache partitions are 0kb and i get i/o errors too.
I have persist problems after installing muiu 11 over the los16.
Thinking about relock it and sens it back to aliexpress seller.
@mvha just go into fastboot mode, and flash persist.img from stock fastboot rom,
With command : fastboot flash persist persist.img
Thats all
Arif Ferdian said:
So do I, first time I successfully instal first beta v25 miui 11, and than when the v26 comes, stupidly, i flash it from twrp, it tells me that i succeed installing that zip, and than i wipe art and cache and reboot system, but what next i know, my phone brick, i can not instal anyrom, from mi flash tool, or from anywhere. I did everything and still can not fix the problem.
Anyway, you still can enterin TWRP UI, after waiting about 10 to 30 minutes, because after intalling that rom, automatically your data format change from ext4 to f2fs, and twrp will need a lot of time to read your disk.
But, even after doing anything in twrp, still can not make my phone successfully boot into system.
And theres moun I/O error everytime i tried to wipe everything, or fix disk, or change disk format. Everything... and i just dont know what to do anymore.
So may be you can wait patiently until you can entering twrp ui, and please lemme know if you know how to fix this problem
Click to expand...
Click to collapse
This makes sense as I remember trying to boot into stock recovery early in the morning. I woke up and it finally booted, but the recovery was in Chinese. I will give 4PDA TWRP about an hour and see what I can do. Thanks.
Soapy! said:
This makes sense as I remember trying to boot into stock recovery early in the morning. I woke up and it finally booted, but the recovery was in Chinese. I will give 4PDA TWRP about an hour and see what I can do. Thanks.
Click to expand...
Click to collapse
If you can not use 4pda, i suggest u to use greek one, thats twrp version the must successfully booting in my experiences
I am thankful that I saw this before updating to newest miui 11
flamedrops said:
ok, yes thats it. have you tried to flash magisk?
Click to expand...
Click to collapse
Can not flash magisk, etc hahahhahaa
Arif Ferdian said:
If you can not use 4pda, i suggest u to use greek one, thats twrp version the must successfully booting in my experiences
Click to expand...
Click to collapse
After you used the Greek twrp did you manage to solve the problem?