Related
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.
Firstly, my phone isn't hard-bricked. I'm able to load different versions of the TWRP recovery and access Fastboot without any problems. I'm also pretty comfortable using adb to push, sideload, access fastboot, recovery , etc. so please feel free to throw out any suggestions that might help me resolve my issue. (Note:I'm unable to find the stock recovery on OnePlus's support page anymore, I recall they always had the option to download the stock recovery just below the download option for the stock ROM, so I haven't been able to try sideloading after formatting with the stock recovery.)
My OnePlus 5 was running stock Oreo and I'd been meaning to upgrade to Lineage 16.0 (Pie) or any other Pie ROM really. I booted into TWRP (3.2.3-0 - Oreo firmware) and wiped everything other than USB storage and formatted data too as my previous Oreo installation was encrypted. Then, I downloaded codeworkxx's 9.0.3 firmware for OnePlus 5 and pushed it to my phone using adb. I flashed the firmware successfully, rebooted into Bootloader/fastboot; and flashed the Android Pie version of TWRP recovery ( https://sourceforge.net/projects/cheeseburgerdumplings/files/16.0/cheeseburger/ ) and was able to successfully boot back into the recovery. Since then, I've tried to flash multiple different Pie ROMs (Pixel Experience, Lineage 16.0, stock OOS official build - 9.0.3 , Beta OOS build OpenBeta26) (clean flashing always) but always ended up with a bootloop with the boot animations in all the ROMs. I've even tried flashing them with Magisk-v18.0 but that doesn't help either. I've waited for 15 min with each boot for the different ROM's (ending up in bootloops) and on rebooting back to TWRP, I've always found that irrespective of ROMs, the only folder that's created in Internal Storage is 'obb' and it is an empty folder. I've even tried sideloading OOS 9.0.3 (official build) via TWRP and that still ends up in a bootloop with the obb folder in Internal Storage being the only thing created. Also, flashing the boot.img recovery in the stock ROM zip files leads to a blank screen with a white LED that tries to install Qualcom drivers, so I just reflashed TWRP and am back to where I started.
That pretty much sums up my problem here. Kindly throw suggestions at me to help fix my problem' I've searched the forums but most of the bootloop issues I've found and read are about unsuccessful firmware flashes (not the case with me as I've explained above) or dirty flashes (again, not the case with me as I always cleanflash).
Thanks!
You should be focusing on getting stock OOS back on before trying custom rom. Have you tried rolling back to 5.1.7 Oreo? Sometime it better to go back to square 1 and try again.
Z-Blade said:
You should be focusing on getting stock OOS back on before trying custom rom. Have you tried rolling back to 5.1.7 Oreo? Sometime it better to go back to square 1 and try again.
Click to expand...
Click to collapse
Thank you for replying!
I successfully flashed the 5.1.7 firmware and Oreo-TWRP-recovery and was able to install Lineage OS 15.1 and boot it up properly. I'm unable to find a link for previous versions of OOS to test whether or not 5.1.7 would work. Do you know where I can find a link?
Thanks again!
BigTurboSkipper said:
Thank you for replying!
I successfully flashed the 5.1.7 firmware and Oreo-TWRP-recovery and was able to install Lineage OS 15.1 and boot it up properly. I'm unable to find a link for previous versions of OOS to test whether or not 5.1.7 would work. Do you know where I can find a link?
Thanks again!
Click to expand...
Click to collapse
It's within the guides section https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190
strongst said:
It's within the guides section https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190
Click to expand...
Click to collapse
Thanks!
So the Lineage 15.1 flash worked fine but OOS 5.1.7 still leaves me with a bootloop and the obb folder as detailed in my first post. I'm unsure as to how to proceed.
BigTurboSkipper said:
Thanks!
So the Lineage 15.1 flash worked fine but OOS 5.1.7 still leaves me with a bootloop and the obb folder as detailed in my first post. I'm unsure as to how to proceed.
Click to expand...
Click to collapse
What was your LAST stock oxygenOS version that was installed your device prior to 5.1.7?
strongst said:
What was your LAST stock oxygenOS version that was installed your device prior to 5.1.7?
Click to expand...
Click to collapse
I can't recall exactly, but it was most probably OB23/24 (Oreo)
BigTurboSkipper said:
I can't recall exactly, but it was most probably OB23/24 (Oreo)
Click to expand...
Click to collapse
Can you please try to flash 5.1.4 stock oxygenOS rom and the 5.1.7 after it, then magisk and reboot to the os?
Make sure you have an old Oreo compatible recovery like this https://drive.google.com/file/d/1DrEMydZfQxC_eWx1W-OlASo8H7okXNTQ/view?usp=drivesdk
strongst said:
Can you please try to flash 5.1.4 stock oxygenOS rom and the 5.1.7 after it, then magisk and reboot to the os?
Make sure you have an old Oreo compatible recovery like this https://drive.google.com/file/d/1DrEMydZfQxC_eWx1W-OlASo8H7okXNTQ/view?usp=drivesdk
Click to expand...
Click to collapse
Successfully flashed but still results in a bootloop
BigTurboSkipper said:
Thanks!
So the Lineage 15.1 flash worked fine but OOS 5.1.7 still leaves me with a bootloop and the obb folder as detailed in my first post. I'm unsure as to how to proceed.
Click to expand...
Click to collapse
Lineage 15.1 (official) boots successfully but without radios working... I tried reflashing Firmware-5.1.7 but that does not help; not sure how to fix this. Could it be a firmware issue with installing Pie ROMs? But then again, OOS Oreo doesn't boot either - still ends up in a bootloop
My only suggestion ...
BigTurboSkipper said:
Lineage 15.1 (official) boots successfully but without radios working... I tried reflashing Firmware-5.1.7 but that does not help; not sure how to fix this. Could it be a firmware issue with installing Pie ROMs? But then again, OOS Oreo doesn't boot either - still ends up in a bootloop
Click to expand...
Click to collapse
Greetings! I got your private message, but I haven't read it yet. Sorry, very busy today. However, I can make the following suggestion to get your device back into original working order.
Have a look at this link on xda. It's for an unbrick tool, which I've used numerous times with great success.
https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169
This tool will put your device back into its original condition, with original OOS.
Let me know if it works for you.
Peter
BigTurboSkipper said:
Lineage 15.1 (official) boots successfully but without radios working... I tried reflashing Firmware-5.1.7 but that does not help; not sure how to fix this. Could it be a firmware issue with installing Pie ROMs? But then again, OOS Oreo doesn't boot either - still ends up in a bootloop
Click to expand...
Click to collapse
OxygenOS also needs a formatted internal storage, otherwise bootloop will pop up
strongst said:
OxygenOS also needs a formatted internal storage, otherwise bootloop will pop up
Click to expand...
Click to collapse
Definitely! I've always been clean flashing ROMs (Wiping Internal Storage, Data, System, Dalvik Cache, Cache + Wiping/Formatting Data to factory reset ) for each trial!
BigTurboSkipper said:
Definitely! I've always been clean flashing ROMs (Wiping Internal Storage, Data, System, Dalvik Cache, Cache + Wiping/Formatting Data to factory reset ) for each trial!
Click to expand...
Click to collapse
Wiping system, data, cache, Installing 5.1.4, then magisk, then format internal storage, then boot os should not cause a bootloop
What's your twrp recovery? Did you tried mine?
strongst said:
Wiping system, data, cache, Installing 5.1.4, then magisk, then format internal storage, then boot os should not cause a bootloop
What's your twrp recovery? Did you tried mine?
Click to expand...
Click to collapse
That's exactly what I'm doing. I've tried using codeworkxx 's versions, blu_spark TWRP versions and yours too!
PeterGuru said:
Greetings! I got your private message, but I haven't read it yet. Sorry, very busy today. However, I can make the following suggestion to get your device back into original working order.
Have a look at this link on xda. It's for an unbrick tool, which I've used numerous times with great success.
https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169
This tool will put your device back into its original condition, with original OOS.
Let me know if it works for you.
Peter
Click to expand...
Click to collapse
Thank you for replying!
The tool doesn't detect my device whatsoever - I have system-wide adb & fastboot set up (to use from any folder or path) yet the device is not detected in fastboot mode or recovery mode.
How do you use it?
Thanks!
BigTurboSkipper said:
Thank you for replying!
The tool doesn't detect my device whatsoever - I have system-wide adb & fastboot set up (to use from any folder or path) yet the device is not detected in fastboot mode or recovery mode.
How do you use it?
Thanks!
Click to expand...
Click to collapse
You need to put your device into MSM Download mode. It's simple. Power off your device. Press and hold the Volume UP key for about 8-10 seconds and, while continuing to hold the Volume UP key, plug in your device to your computer via USB. Open the MSM Tool and press Start.
That's it.
It takes about 3-5 minutes for the tool to complete the unbrick process.
Peter
Thank you! I was able to successfully use the unbrick tool to reset to OOS 4.5.8 Nougat. I'm going to try stepping all the way up to Pie now!
Whenever I try to flash a custom ROM it will stuck on bootloop
I try pixel experience pie ,pixel experience Oreo, crDroid rom
But as always in every rom it stuck on bootloop
Only stock room works after restoring
Pramod saxena said:
Whenever I try to flash a custom ROM it will stuck on bootloop
I try pixel experience pie ,pixel experience Oreo, crDroid rom
But as always in every rom it stuck on bootloop
Only stock room works after restoring
Click to expand...
Click to collapse
What about some more information?
- Is your bootloader unlocked?
- Are you rooted and if yes how (magisk version)?
- TWRP version?
- What's your actual stock firmware and from which you were coming from?
- Is your data partition encrypted?
- When you say "stuck on bootloop" what does that mean? Is it a bootloop like looping all the time without booting the OS or are you stuck on your bootlogo/bootanimation?
- Any error messages from TWRP?
You'll find the log in cache/recovery/last_log.
Nobody will be able to help you if you don't provide informations i.e. logs.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
What about some more information?
- Is your bootloader unlocked?
- Are you rooted and if yes how (magisk version)?
- TWRP version?
- What's your actual stock firmware and from which you were coming from?
- Is your data partition encrypted?
- When you say "stuck on bootloop" what does that mean? Is it a bootloop like looping all the time without booting the OS or are you stuck on your bootlogo/bootanimation?
- Any error messages from TWRP?
You'll find the log in cache/recovery/last_log.
Nobody will be able to help you if you don't provide informations i.e. logs.
Click to expand...
Click to collapse
★yes my bootloader is unlocked
★Root:- No, I didn't root my phone
★twrp version:- twrp-3.2.3-1-potter.img
★I am on Stock Oreo 8.1 by recovery my stock room after stucking and I am also coming from stock Oreo 8.1 (Sorry properly I didn't understand what u ask)
★yes,my device is encrypted
★it is stuck on that's rom logo, like if I install pixel rom it starts by a circular motion of Google and then stuck on Google logo....
Or when I install crDroid rom then it stuck on crDroid logo
And there is a loading line below the logo
★TWRP error:- Sometimes unmount storage/partition error occurred but when I repair data,cache and system in wipe option it will solve
Pramod saxena said:
★yes my bootloader is unlocked
★Root:- No, I didn't root my phone
★twrp version:- twrp-3.2.3-1-potter.img
★I am on Stock Oreo 8.1 by recovery my stock room after stucking and I am also coming from stock Oreo 8.1 (Sorry properly I didn't understand what u ask)
★yes,my device is encrypted
★it is stuck on that's rom logo, like if I install pixel rom it starts by a circular motion of Google and then stuck on Google logo....
Or when I install crDroid rom then it stuck on crDroid logo
And there is a loading line below the logo
★TWRP error:- Sometimes unmount storage/partition error occurred but when I repair data,cache and system in wipe option it will solve
Click to expand...
Click to collapse
Maybe try to format /data in TWRP to decrypt it. A lot of custom ROMs can't handle encrypted devices.
Post the last_log from cache/recovery when you try to flash a custom ROM.
Sent from my Moto G5 Plus using XDA Labs
Yesterday when I flash pixel rom
(Same issue stucking on bootloop)
But then I again go to bootloader and factory reset and do power off
And surprisingly it's on
I did all setup also login to my Google account
Everything gonna properly working but camera error occurred
So I power off my cell phone and when I restart... It again stuck on bootloop
This is the log after installing pixel rom??
Pramod saxena said:
Yesterday when I flash pixel rom
(Same issue stucking on bootloop)
But then I again go to bootloader and factory reset and do power off
And surprisingly it's on
I did all setup also login to my Google account
Everything gonna properly working but camera error occurred
So I power off my cell phone and when I restart... It again stuck on bootloop
This is the log after installing pixel rom??
Click to expand...
Click to collapse
Wolfcity said:
Maybe try to format /data in TWRP to decrypt it. A lot of custom ROMs can't handle encrypted devices.
Post the last_log from cache/recovery when you try to flash a custom ROM.
Click to expand...
Click to collapse
Yesterday when I flash pixel rom
(Same issue stucking on bootloop)
But then I again go to bootloader and factory reset and do power off
And surprisingly it's on
I did all setup also login to my Google account
Everything gonna properly working but camera error occurred
So I power off my cell phone and when I restart... It again stuck on bootloop
This is the log after installing pixel rom??
Hello, did you find the solution? I'm facing the same problem with the rom crDroid for moto g5 plus.
viclib said:
Hello, did you find the solution? I'm facing the same problem with the rom crDroid for moto g5 plus.
Click to expand...
Click to collapse
The Solution for me was to format data. It is NOT JUST WIPE but to FORMAT.
That removed the encryption and I was able to flash any other rooms again
Hey!
I installed LineageOs on my Xiaomi Mi A1, everything went okay but when I installed the Gapps, it got stuck on the LineageOs logo. The volume button wasn't working right, yet somehow, I manage to enter TWRP and wipe that OS and restore the backup with the original Android One. But when I boot it, it got stuck on Android logo, unable to enter fastboot, TWRP or hard reset because of the volume button not working.
I don't know what else to do, to be honest...
p.d.: I'm new here, sorry if this is not the right section to ask.
Are you 100% sure that you have chosen right version of GApps? because i never had any issues with GApps causing boot loop. BTW what lineage os version 16 or 17 ?
I never had any luck restoring stock rom backup via TWRP either i have no idea why whenever i restore it will stuck on androidone logo.
royalasif said:
Are you 100% sure that you have chosen right version of GApps? because i never had any issues with GApps causing boot loop. BTW what lineage os version 16 or 17 ?
I never had any luck restoring stock rom backup via TWRP either i have no idea why whenever i restore it will stuck on androidone logo.
Click to expand...
Click to collapse
I chose Android 10 GApps since I installed LineageOS 17. I thought it was the right version.
So TWRP can't be used for stock rom? I didn't know, maybe that's what got me stuck on Android One logo.
Any idea on how to get out from that loop? ?
Dont worry bootloop is not a problem download pixel experience it include gapps boot ur phone to twrp copy rom into internal or sd card Wipe system , data , cache and install the rom ..
TWRP should backup and restore stock image but i think there is something with this phone which wont let twrp to apply system restore i have done it 10 times and i failed everytime.
Edit: do let me know how it goes:good:
royalasif said:
Dont worry bootloop is not a problem download pixel experience it include gapps boot ur phone to twrp copy rom into internal or sd card Wipe system , data , cache and install the rom ..
TWRP should backup and restore stock image but i think there is something with this phone which wont let twrp to apply system restore i have done it 10 times and i failed everytime.
Edit: do let me know how it goes:good:
Click to expand...
Click to collapse
Definitely I'll try Pixel Experience! Seems like a good choice. I still need to figure out how to enter Fastboot or TWRP without the volume button.
try adb cmd if it works if not then u have to boot your device to EDL mode by test point method and then flash stock rom
ranjodhricky said:
try adb cmd if it works if not then u have to boot your device to EDL mode by test point method and then flash stock rom
Click to expand...
Click to collapse
Adb cmd won't recognize the device, so I'll have to boot it to EDL mode. Is there any guide here? I don't know how to do it.
Hey, I'm trying to flash Lineage OS onto my Galaxy A20e (SM-A202F) and after I flash it from an SD card onto the system image partition, it says [IMAGE FLASH COMPLETED]. When I press reboot system from there, it tells me I have no OS installed. Trying to reboot anyway puts me in a bootloop. To get the phone working I need to flash the stock OS on to the phone.
I've tried a few versions of Lineage for the A20e to no avail. I have rooted the phone with Magisk and wiped the system, data, cache, and Dalvik, with the same result every time. I can't seem to find this problem mentioned anywhere else.
I've been at this for days and would appreciate any suggestions, cheers.
fixed by @hainguyenthao, thanks ^-^
turtpipchim said:
Hey, I'm trying to flash Lineage OS onto my Galaxy A20e (SM-A202F) and after I flash it from an SD card onto the system image partition, it says [IMAGE FLASH COMPLETED]. When I press reboot system from there, it tells me I have no OS installed. Trying to reboot anyway puts me in a bootloop. To get the phone working I need to flash the stock OS on to the phone.
I've tried a few versions of Lineage for the A20e to no avail. I have rooted the phone with Magisk and wiped the system, data, cache, and Dalvik, with the same result every time. I can't seem to find this problem mentioned anywhere else.
I've been at this for days and would appreciate any suggestions, cheers.
Click to expand...
Click to collapse
try my kernel
A20e Root,Kernel, TWRP and custom ROM
Root & TWRP from Xyn XDotnest https://forum.xda-developers.com/galaxy-a20/development/recovery-twrp-3-4-0-0-galaxy-a20e-a202f-t4141767 Orange Fox Recovery from @Royna...
forum.xda-developers.com
turtpipchim said:
fixed by @hainguyenthao, thanks ^-^
Click to expand...
Click to collapse
can I ask how was it fixed? I have the same problem with A6+ Samsung device. thanks
turtpipchim said:
fixed by @hainguyenthao, thanks ^-^
Click to expand...
Click to collapse
How?