Bro was trying to flash a Custom Rom without enabling developer options and oem unlock and usb debugging by using twrp.
The files was somehow corrupted and now i am stuck at boot logo that too switching on and off simultaneously.
Unable to go in Recovery Mode aswell & neither i am unable to flash any recovery due to device unlock(oem unlock).
Please Help.
similar problem
abhi461 said:
Bro was trying to flash a Custom Rom without enabling developer options and oem unlock and usb debugging by using twrp.
The files was somehow corrupted and now i am stuck at boot logo that too switching on and off simultaneously.
Unable to go in Recovery Mode aswell & neither i am unable to flash any recovery due to device unlock(oem unlock).
Please Help.
Click to expand...
Click to collapse
I have a similar problem to yours,did you figure out what to do?
Related
my phone boot but stuck in that part after I format my phone, I can't access recovery and can't go through download mode/ bootloader (right? i'm not sure if this two are the same.) I have a root access, I have unlock my bootloader and my phone is u8150 Huawei, please help i can't solve this problem, thanks in advance for any help!!!!
jc_bonsol said:
my phone boot but stuck in that part after I format my phone, I can't access recovery and can't go through download mode/ bootloader (right? i'm not sure if this two are the same.) I have a root access, I have unlock my bootloader and my phone is u8150 Huawei, please help i can't solve this problem, thanks in advance for any help!!!!
Click to expand...
Click to collapse
You have to got fastboot files and boot into the safemode and startover. Sorrey
try USB JIG
PINGXIANG840 said:
You have to got fastboot files and boot into the safemode and startover. Sorrey
Click to expand...
Click to collapse
how to make it I don't have much knowledge about that, but its ok for me to lose all of my file inside my phone instead to lose my whole phone
Hi,
I upgraded a patch of custom rom and phone restarted and stopped at boot image.
Now, I want to reboot it into recovery and replace other custom rom but due to unusable volume key I'm not able to reboot it to recovery mode.
Tried this by using adb but its not recognizing the phone (might be USB debugging is in disable mode). Pls Help me on this.
Thanks,
Dharmender
dharmuls said:
Hi,
I upgraded a patch of custom rom and phone restarted and stopped at boot image.
Now, I want to reboot it into recovery and replace other custom rom but due to unusable volume key I'm not able to reboot it to recovery mode.
Tried this by using adb but its not recognizing the phone (might be USB debugging is in disable mode). Pls Help me on this.
Thanks,
Dharmender
Click to expand...
Click to collapse
Try this method to install recovery.... http://forum.xda-developers.com/showthread.php?t=2167621
Tried this but getting error msg at sp flash tool and not moving further, might be due to usb debugging not enabled
got the below error msg
zeu55 said:
Try this method to install recovery.... http://forum.xda-developers.com/showthread.php?t=2167621
Click to expand...
Click to collapse
Pls help me, my phone is unusable state now :crying:
dharmuls said:
Pls help me, my phone is unusable state now :crying:
Click to expand...
Click to collapse
Installing recovery does not require adb. Check you have correct drivers installed.
I am currently in a situation where USB debugging was not enabled, CROM service status is set to "Locked". This is causing an issue on my International Galaxy S6 Edge (g9250) -- It is stuck in a boot loop and the android OS that was previously installed was wiped on accident through the stock android recovery mode.
I am unable to flash TWRP recovery to the phone, I am unable to use Odin to flash a stock ROM image to the phone, or perform any data transfer between my Windows machine to the phone. Smart Switch also does not work. Also Now I am sure this is because I never enabled developer mode and turned on USB debugging, and also because this CROM service is set to lock. When I attempt to sideload using ADB I get error:closed. When using the Skipsoft Unified Android Toolkit any task performed stops at: "Waiting for USB debugging".
Is there any solution for this? I've looked all over the internet and haven't been able to solve my issue -- I'm stuck at a perpetual boot loop because there is no Android OS on the device's partition, and also am unable to flash the stock ROM using ODIN or sideload using ADB.
Is there is a way to turn on USB debugging when stuck in a bootloop? Or a way to disable CROM service on the phone to be able to flash or transfer files?
As of right now the device is completely useless and I have been researching for the past 5 days
Any help is very appreciated, please let know if there is more information needed.
Hi there. I am presently stuck in the exactly same situation. Can you please tell me what you did after that. thanks
Hi XDA Community,
I have been a silent reader and user of many custom roms but now I can't solve my problem alone, I have to admit. My current device is a redmi note 3 and I am using it for about a year now. Today the phone went into a bootloop itself and I can't bring it back.
It runs the CM 14.1 kenzo and got xposed and xprivacy installed.
The problem is caused by xposed (very sure) but unfortunately every solution I tried failed.
-My plan was to flash the xposed disabler.zip using TWRP 3.0.2-2 but that won't let me get to main menu. Its stuck at the twrp boot screen. (Any ideas why? Maybe weak battery)
-The next I tried was entering fastboot and flash it this way, but it seems like usb debugging is disabled. (Is there a chance to enabled USB debugging without beeing able to boot?)
-Next I tried was to enter edl mode and flash twrp again using miflash but that gave me the error "unable to communicate on port COM10"
So now I really don't know what to do to disable the xposed moduls and boot again.
I guess possible was would be to enable usb debugging or find out why twrp won't boot or flash that disabler zip in odin. But let me know what ideas you have.
Thanks for your help guys
ligger_sunnyboy said:
Hi XDA Community,
I have been a silent reader and user of many custom roms but now I can't solve my problem alone, I have to admit. My current device is a redmi note 3 and I am using it for about a year now. Today the phone went into a bootloop itself and I can't bring it back.
It runs the CM 14.1 kenzo and got xposed and xprivacy installed.
The problem is caused by xposed (very sure) but unfortunately every solution I tried failed.
-My plan was to flash the xposed disabler.zip using TWRP 3.0.2-2 but that won't let me get to main menu. Its stuck at the twrp boot screen. (Any ideas why? Maybe weak battery)
-The next I tried was entering fastboot and flash it this way, but it seems like usb debugging is disabled. (Is there a chance to enabled USB debugging without beeing able to boot?)
-Next I tried was to enter edl mode and flash twrp again using miflash but that gave me the error "unable to communicate on port COM10"
So now I really don't know what to do to disable the xposed moduls and boot again.
I guess possible was would be to enable usb debugging or find out why twrp won't boot or flash that disabler zip in odin. But let me know what ideas you have.
Thanks for your help guys
Click to expand...
Click to collapse
xposed is not supported on android 7 roms, please dont try that again.
i would suggest that if fastboot is accessible you should use miflash to starover with miui.
if you can access fastboot mode and your device is officially unlocked then try to boot into twrp using fastboot boot <name of the recovery>.img
or you can try flash with mitools (USB debugging is not needed for flashing ). you can use the deep flash cable to flash your device in edl mode
Follow this guide http://en.miui.com/thread-235865-1-1.html
Hi,
my Note 5 (which is standard with latest software updates) hangs on the Mi screen when starts up. I can get it into FASTBOOT mode.
And when I connect to PC/Windows 10 and go through adb and enter this:
fastboot devices
gives this result:
fcef713c0904
But I'm not sure what to do now? I guess I need to flash some sort of recovery but not being super tech savvy I'm a bit nervous.
thanks Phillip
@phil170258
Edit: fastboot is recognicing your device, as far I understood what you mean you tried to unroot it and gave you bootloop, flash the boot image that you are using lastly through fastboot and see what happens
SubwayChamp said:
@phil170258
Edit: fastboot is recognicing your device, as far I understood what you mean you tried to unroot it and gave you bootloop, flash the boot image that you are using lastly through fastboot and see what happens
Click to expand...
Click to collapse
Hi,
thanks for your reply.
I wasn't trying to do anything with my phone (root or unroot) when it started this behaviour so I don't have a boot image to flash? And my phone doesn't have 'usb debugging enabled' but because it won't turn on I can't enable it.
So i need to do 'fastboot flash recovery twrp.img' but when I do this it says cannot load twrp.img no such file or directory.
Aaaaaah!
thanks, Phil
phil170258 said:
Hi,
thanks for your reply.
I wasn't trying to do anything with my phone (root or unroot) when it started this behaviour so I don't have a boot image to flash? And my phone doesn't have 'usb debugging enabled' but because it won't turn on I can't enable it.
So i need to do 'fastboot flash recovery twrp.img' but when I do this it says cannot load twrp.img no such file or directory.
Aaaaaah!
thanks, Phil
Click to expand...
Click to collapse
Then try first going to recovery stock manually and wipe data and try to boot.
There are many users reporting this kind of issues along the time (updating firmware, charging all the night, etc) so the best is enabling USB debugging if something goes wrong you´ll have more options to save your device.
I guess you have your bootloader locked and also for this reason you can no longer use fastboot mode to flash some file.
If the first doesn´t result then your last resource would be to flash a rom through test point method (if you have Redmi 5 Plus-Vince)
SubwayChamp said:
Then try first going to recovery stock manually and wipe data and try to boot.
There are many users reporting this kind of issues along the time (updating firmware, charging all the night, etc) so the best is enabling USB debugging if something goes wrong you´ll have more options to save your device.
I guess you have your bootloader locked and also for this reason you can no longer use fastboot mode to flash some file.
If the first doesn´t result then your last resource would be to flash a rom through test point method (if you have Redmi 5 Plus-Vince)
Click to expand...
Click to collapse
Wipe data worked!
Thanks, and yes, i will enable USB debugging
thanks, Phil