Hi, I downloaded the Evolution X 5.9 surya unofficial zip file in my internal storage and then went to TWRP.
I watched a tutorial on Youtube so I wiped Dalvik/Art Cache, Data, and Cache before flashing the custom rom (wiped the dalvik/art cache again before pressing boot to system)
I thought it was going well but then my phone is now stuck in a bootloop where it's just stuck in Fastboot mode. Currently trying to fix it..
I just want to know what could have caused this? And if I did the whole process wrong? I want to try out the Evo X custom rom, I'm willing to try and flash the rom again once I've gotten out of the bootloop, but I'm anxious I'll mess up again. I've never unlocked my bootloader and flashed a custom rom before, so forgive me.
EDIT: any possible fixes for getting out of the bootloop would be really appreciated too!
EDIT2: I may have really messed up. I decided to press the power button while in Fastboot, and then now it's just a black screen. Windows won't recognize it anymore...
Which firmware you used before flashing the evolution x
Related
i am new to this root thing.i have search forum.i have tried lots of thing but it didnt work.i have wipe cache,dalvik cache,wipe data and factory reset,format boot,sytem,data.all the step that were given in thread to get out of this problem.even tried switching to ext3.and even tried fastboot flash boot.img and recovery.installing cyanogen mod 10, pandora kernel,gapps and using recovery twrp.pls help stuck at cyanogenmod boot screen. what i am suppose to do please help.
Hello,
I successfully installed cyanogenmod 7.2 on my Motorola Defy MB525 using the instructions from the cyanogenmod wiki "Install CM for jordan" (can't post link yet).
After a while, I wanted to install gapps, so I installed it from Bootmenu. After this, the phone was always booting to boot menu and I didn't know how to make it boot into the system, so I changed the "Boot" option default to something like "Normal", I think.
Now when starting the phone, all I see is the Google logo which stays there indefinitely.
I can still boot to BootMenu and tried a number of times to wipe data/factory reset, wipe cache, wipe dalvik cache, and re-install the cyanogenmod7.2 zip, but it still can't get out of the infinite loop.
I found out that a posible solution would be to flash an image with RSD Lite, but it seems kind of tricky and I would rather leave it as a last resort.
Any ideas?
Thanks
I managed to unbrick my phone eventually.
Tried to use RSD Lite with several images, but it would give an error and then the application would crash and leave my bootloader corrupt. I tried all the schemes I could find including: loading the image from root of C:, disabling UAC, etc., but nothing worked.
Then I tried sbf_flash on Linux with the same image, and it worked like a charm, no errors, and my phone was up and running again.
So for anyone else who may encounter this problem, I warmly recommend using sbf_flash, it is incredibly simple to use.
sltrv said:
Hello,
I successfully installed cyanogenmod 7.2 on my Motorola Defy MB525 using the instructions from the cyanogenmod wiki "Install CM for jordan" (can't post link yet).
After a while, I wanted to install gapps, so I installed it from Bootmenu. After this, the phone was always booting to boot menu and I didn't know how to make it boot into the system, so I changed the "Boot" option default to something like "Normal", I think.
Now when starting the phone, all I see is the Google logo which stays there indefinitely.
I can still boot to BootMenu and tried a number of times to wipe data/factory reset, wipe cache, wipe dalvik cache, and re-install the cyanogenmod7.2 zip, but it still can't get out of the infinite loop.
I found out that a posible solution would be to flash an image with RSD Lite, but it seems kind of tricky and I would rather leave it as a last resort.
Any ideas?
Thanks
Click to expand...
Click to collapse
Details first:
Oneplus One 64GB
Have never changed the kernel (so, stock? I think?)
TWRP 3.0.2.0
LineageOS 14.1 - "nightly" (weekly?) 2017-05-01
Phone is (was) encrypted
I'm not quite sure what to make of this:
Yesterday my phone wouldn't turn the screen on. I had received a notification, the notification light was flashing, and I had just used it, but double-tapping the screen or pressing the power button wouldn't turn the screen on. I wasn't overly worried, I've encountered bugs like this before, so I held the power button to restart the phone.
The OS wouldn't move past the boot animation.
The phone very happily booted into the recovery though.
Here's what I've attempted so far, in this order:
Wipe cache & dalvik cache.
Wipe cache, dalvik cache, and data.
Wipe cache, dalvik cache, data, and internal storage.
Restore nandroid backup
Fresh install of OS and Gapps
Fresh install of recovery in fastboot and then #5
Fresh install of a different OS (SlimRom 7.1.2 Beta 2017-04-21) and Gapps
Nothing is getting me back into Android, but as you can read, fastboot and recovery load up with no worries.
Does anyone have any idea as to what might be wrong? I'm about to load a new kernel on and see if that does anything, but I'm not holding my breath.
Any help would be greatly appreciated, thank you.
NoSyt15 said:
Details first:
Oneplus One 64GB
Have never changed the kernel (so, stock? I think?)
TWRP 3.0.2.0
LineageOS 14.1 - "nightly" (weekly?) 2017-05-01
Phone is (was) encrypted
I'm not quite sure what to make of this:
Yesterday my phone wouldn't turn the screen on. I had received a notification, the notification light was flashing, and I had just used it, but double-tapping the screen or pressing the power button wouldn't turn the screen on. I wasn't overly worried, I've encountered bugs like this before, so I held the power button to restart the phone.
The OS wouldn't move past the boot animation.
The phone very happily booted into the recovery though.
Here's what I've attempted so far, in this order:
Wipe cache & dalvik cache.
Wipe cache, dalvik cache, and data.
Wipe cache, dalvik cache, data, and internal storage.
Restore nandroid backup
Fresh install of OS and Gapps
Fresh install of recovery in fastboot and then #5
Fresh install of a different OS (SlimRom 7.1.2 Beta 2017-04-21) and Gapps
Nothing is getting me back into Android, but as you can read, fastboot and recovery load up with no worries.
Does anyone have any idea as to what might be wrong? I'm about to load a new kernel on and see if that does anything, but I'm not holding my breath.
Any help would be greatly appreciated, thank you.
Click to expand...
Click to collapse
Did you tried flashing stock Cyanogen Os through fastboot?
Mr.Ak said:
Did you tried flashing stock Cyanogen Os through fastboot?
Click to expand...
Click to collapse
No, but I tried flashing a different OS, so I wouldn't think that would work? Especially considering Cyanogen is gone and not supporting anymore.
Either way, I worked it out in the end!
I thought I'd tried everything, but turns out I hadn't: I didn't try formatting the phone. Doing so "removed" the previous encryption, which meant that with a fresh flash I could boot again. After that I restored my backup, re-encrypted, and I'm good to go!
So it must've been something wrong with the decryption/boot process(?)
Anyway, thanks for your help!
Hi, so short story is.
1. I had a backup of my stock rom that i did using twrp.
2. I flashed Franco Kernel for COS 13 downloaded from his website (https://kernels.franco-lnx.net/OnePlusOne/6.0.1/anyKernel/)
3. When i flashed i performed a Wipe dalvik cache from recovery
4. Reboted phone, and started optimizing apps but suddenly it rebooted.
5. Started optimizing apps but when it showed optimizing app 1 of 103 the phone keept restarting.
6. I decided to restore my backup made from TWRP, but then phone got stuck and restated everytime from the CYANOGENOS logo.
7. Since it was not booting, i decided to install from fastboot a clean CM13.
8. Flashed, finished and then the phone restarted, but heeey, again stuck in the CYANOGENOS Logo and restarting when the logo shows up.
9. I freak out and I don't know what to do.
So far:
fastboot is working
Cyanogen Recovery is Working ( tried the wipe from that, but still no luck)
When I plug the device directly to my PC, it shows "QHSUSB_BULK", but as i say: fastboot and COS recovery are working.
Can you guys help me, please
First of all, I let the phone charge till 100% on screen (yes, the charger indicator was working aswell)
Well, since my device was able to boot into both Recovery and Fastboot modes, I decided to flash a custom recovery one more time to replace the COS recovery. I flashed CWM 6 (because before TWRP was not helping) and performed a "backup" of the whole rom, just to see if it worked, and it did. After that, i wiped /factory reset from CWM.
Rebooted the device, and voilá I guess. The phone was able to boot into CM 13, now I'm happy to see that I was able to recover from this issue.
Still have no clue about why the FrancoKernel ended in a bootloop. Was the cache wiping a bad idea ?
leokook said:
First of all, I let the phone charge till 100% on screen (yes, the charger indicator was working aswell)
Well, since my device was able to boot into both Recovery and Fastboot modes, I decided to flash a custom recovery one more time to replace the COS recovery. I flashed CWM 6 (because before TWRP was not helping) and performed a "backup" of the whole rom, just to see if it worked, and it did. After that, i wiped /factory reset from CWM.
Rebooted the device, and voilá I guess. The phone was able to boot into CM 13, now I'm happy to see that I was able to recover from this issue.
Still have no clue about why the FrancoKernel ended in a bootloop. Was the cache wiping a bad idea ?
Click to expand...
Click to collapse
Yes,that's where it all went wrong.You should never wipe anything while flashing a custom kernel.
Mr.Ak said:
Yes,that's where it all went wrong.You should never wipe anything while flashing a custom kernel.
Click to expand...
Click to collapse
Lesson learned.
Hello. My new phone got stolen. I currently have a phone named symphony W17 ( MT6572 ). I had flashed stock rom using sp flash tool, but its stuck in bootloop. I tried clearing data and dalvik cache from recovery but no luck, Its stuck in the bootloop. Please help me!
Most often we face a bootloop just after flashing a stock or custom ROM over an old one not having immediately cleared cache / data before a reboot. This might be a major factor behind the bootloop issue on your device.
xXx yYy said:
Most often we face a bootloop just after flashing a stock or custom ROM over an old one not having immediately cleared cache / data before a reboot. This might be a major factor behind the bootloop issue on your device.
Click to expand...
Click to collapse
But i cleared both cache and data and still its stuck in bootloop! Not just that I also did format whole flash using sp flash tool but the issue never goes. Please help me