Hello anyone reading this, the other day i was at a birthday party and was just randomly browsing facebook on my phone when the phone ran out of battery. When i got home and put it on charge, it booted to the home screen, i put my lock code in and then it would start loading everything but then it just suddenly freezes so i had to keep restarting it manually and after a few goes, it got to the point where it would not go past the boot screen and now it seems as if it has like no idea what its doing.. i went into fastboot and factory resetting it but nothing happened, and when i go into recovery and try to wipe anything, it just freezes and does nothing. It wont even recgonize a usb cable and i have installed it on my computer before, and i have got to the point where i dont know what to do can anyone PLEASE help? :crying: :crying: :crying:
Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
Good luck
Pastyslayer said:
Hello anyone reading this, the other day i was at a birthday party and was just randomly browsing facebook on my phone when the phone ran out of battery. When i got home and put it on charge, it booted to the home screen, i put my lock code in and then it would start loading everything but then it just suddenly freezes so i had to keep restarting it manually and after a few goes, it got to the point where it would not go past the boot screen and now it seems as if it has like no idea what its doing.. i went into fastboot and factory resetting it but nothing happened, and when i go into recovery and try to wipe anything, it just freezes and does nothing. It wont even recgonize a usb cable and i have installed it on my computer before, and i have got to the point where i dont know what to do can anyone PLEASE help? :crying: :crying: :crying:
Click to expand...
Click to collapse
I need some more information to help, what do you mean lockcode. Do you mean the lock screen or encryption key at bootup. Also what version are you running and can you access fastboot mode? What recovery are you running? Stock?
Please answer these and I will try my best to assist.
Yes i ment lockscreen, and im running 4.4.4 and i can access fastboot mode but when i connect a usb cable, nothing happens.
Pastyslayer said:
Yes i ment lockscreen, and im running 4.4.4 and i can access fastboot mode but when i connect a usb cable, nothing happens.
Click to expand...
Click to collapse
Wipe /cache through stock recovery.
help sparsechunks
i have got past the gpt.bin bit but when i get to the sparse chunks, it wont let me flash them, i have checked and the sparsechunk files are in there so why cant i flash them? help?
Pastyslayer said:
i have got past the gpt.bin bit but when i get to the sparse chunks, it wont let me flash them, i have checked and the sparsechunk files are in there so why cant i flash them? help?
Click to expand...
Click to collapse
What is the error message.
Related
Hi everyone. I have been looking everywhere i can and i cannot find any existing threads explaining how to fix this.
First off I am a little bit of a noob when it comes to rooting. I rooted my phone using a one-click method yesterday and was flashing roms fine. I couldnt find anything i liked last night so i restored the backup i made. This morning i was going to flash CM9. My phone was fine this morning. I turned off my phone and went into fastboot mode. When i went to recovery it came right back into fastboot mode saying "no boot or recovery image". No matter how i turn the phone on it goes to fastboot mode. Also, i can't seem to get my computer to recognize my phone no matter what i try. I have pulled the battery and left it out for 30 minutes and still nothing.
What am i missing.
Thank you in advance for any help.
I had a similar situation, don't get stressed, basically u'll have to force the phone into recovery, delete all the files in regards to android on ur pc, restart it, same for the phone, I don't exactly remember where it is but I think is around here on the forums at XDA that explain how to force the Nexus to be recognized by Windows again, or ;look it up on Google, lessons learned!!!
Also check the posts about Nexus being stuck on Boot and similar.
cmill600rr said:
Hi everyone. I have been looking everywhere i can and i cannot find any existing threads explaining how to fix this.
First off I am a little bit of a noob when it comes to rooting. I rooted my phone using a one-click method yesterday and was flashing roms fine. I couldnt find anything i liked last night so i restored the backup i made. This morning i was going to flash CM9. My phone was fine this morning. I turned off my phone and went into fastboot mode. When i went to recovery it came right back into fastboot mode saying "no boot or recovery image". No matter how i turn the phone on it goes to fastboot mode. Also, i can't seem to get my computer to recognize my phone no matter what i try. I have pulled the battery and left it out for 30 minutes and still nothing.
What am i missing.
Thank you in advance for any help.
Click to expand...
Click to collapse
Since your in fast boot try to go to recovery. From recovery try to delete data and cache. Then try to reflash your rom. Chances are if it will not work. Maybe the file you downloaded is corrupted and u need to download it again.
PS don't forget to do a nand backup before flashing any rom or update.
Sent from my Nexus S using XDA
stuck in fastboot mode, optimus G E970 (AT&T)
bought the phone unlocked and rooted, w. Root Box. everything was working good, had too many files so format the sdcard, data, cache, system... so now Im stuck in fastboot mode... the phone doesnt recognize the ext.sdcard and neither usb when pluged in the PC......please somebody, PLEASE! help me..
Okay from the top, have OPO that had paranoid 4.6 Beta 2 working just fine. Was playing with settings(dumb idea) and changed the runtime to ART like i have on multiple other phones just to try it out. Phone rebooted and upgraded all the apps like it should, but about 5 seconds after it booted, screen froze for a second and then it rebooted. Once it rebooted it was up for 5 seconds again and then rebooted again. thus started a continues reboot loop.
Using the five seconds i had i was able to race through settings and switch the runtime back to dalvik. this caused the normal reboot and fixing of apps however once it finished the boot process it began the reboot loop again and there was nothing i could do to stop it.
I booted to recovery and attempted to reflash the last update, that failed.
attempted to wipe cache and dalvik cache and that failed.
attempted factory data reset, that failed
NOW is when i made a mistake, on TWRP i checked system wipe as well as data and cache. Wiped everything.
So, phone was then entirely devoid of OS which is a slight problem. I was able to get into fastboot however and flash cm11s which i figured would fix it, false. Now when it boots the system ui crashes over and over continuously and it wont become stable. Went back to recovery but my twrp was gone and i just had cyanogenmod simple recovery. attempted to get to fastboot mode but its apparently nonexistent, i tried every combination of commands possible to get there but cant. so now im stuck with an unusable OS and a useless recovery and no way to get to fastboot mode that im at least aware of... if there are any other details that could help feel free to help, ill post pictures once i figure out a way to do that.
please, for the love of God, help me.
If you gold the power button for about 15 seconds then it should turn off. Then hold volume up and then press and hold power while still holding volume up for a few seconds and it should boot fastboot mode. Try erasing userdata from there to see if you can recover from the crashing.
tiny4579 said:
If you gold the power button for about 15 seconds then it should turn off. Then hold volume up and then press and hold power while still holding volume up for a few seconds and it should boot fastboot mode. Try erasing userdata from there to see if you can recover from the crashing.
Click to expand...
Click to collapse
I tried that a hundred times, the problem is once the screen turns off, if you keep holding vol up it never comes back on, its something i have never seen before and its exxtremely frustrating. Its like fastboot doesnt exist.
I wiped out everything on my Oneplus two months ago by mistake. Then my phone wont boot up because it had nothing in it except the TWRP. I tried EVERYTHING, to load a Rom into the phone, but it didn't work. It goes through the motion of loading a Rom into your phone and when you are about to hit the 100% level, it says FAILED. It wants you to check the debugging which you can't because your phone wont boot up. Anyways, I purchased a micro usb flash drive and loaded up the Rom into flash drive from my comp's usb. Then I connected it to my phone from TWRP via the micro usb port. After it loaded up the Rom from the flash drive, it booted up. Hope that works.
grenademasta said:
I wiped out everything on my Oneplus two months ago by mistake. Then my phone wont boot up because it had nothing in it except the TWRP. I tried EVERYTHING, to load a Rom into the phone, but it didn't work. It goes through the motion of loading a Rom into your phone and when you are about to hit the 100% level, it says FAILED. It wants you to check the debugging which you can't because your phone wont boot up. Anyways, I purchased a micro usb flash drive and loaded up the Rom into flash drive from my comp's usb. Then I connected it to my phone from TWRP via the micro usb port. After it loaded up the Rom from the flash drive, it booted up. Hope that works.
Click to expand...
Click to collapse
hey i hadnt thought of that, thanks ill try that as soon as i can get my hands on a micro usb flash drive, will the device find it using cyanogenmod simple recovery? twrp is gone for some reason.
Don't know if it will work without TWRP. I only see "Apply Update" then "Apply from ADB" and "Choose from internal storage". Hopefully the phone might recognize additional storage from the micro usb flash drive. Good luck.
grenademasta said:
Don't know if it will work without TWRP. I only see "Apply Update" then "Apply from ADB" and "Choose from internal storage". Hopefully the phone might recognize additional storage from the micro usb flash drive. Good luck.
Click to expand...
Click to collapse
thanks for your help! ill update as soon as i get one
The latest twrp supports mtp and you can use adb push to push the file to sdcard. Its really worth learning.
ugly_duckling said:
I tried that a hundred times, the problem is once the screen turns off, if you keep holding vol up it never comes back on, its something i have never seen before and its exxtremely frustrating. Its like fastboot doesnt exist.
Click to expand...
Click to collapse
You should let go of the power button after the device turns off. Then vol up+power when the phone is off. This is different than what I read for the device but it works for getting me in fastboot.
Try flashing it by adb?
Overdose1986 said:
Try flashing it by adb?
Click to expand...
Click to collapse
tried using adb to push files but got error: closed, tried adb kill-server etc to try and get it to work but it wouldnt go, trust me i have tried a lot of things
as for the holding of the volume up button, ive tried every combination of holding and releasing i could think of, it just wont work :/
ugly_duckling said:
tried using adb to push files but got error: closed, tried adb kill-server etc to try and get it to work but it wouldnt go, trust me i have tried a lot of things
Click to expand...
Click to collapse
He meant using adb sideload
Sent from my Oneplus One
have you had a look at my thread here? sure sounds like one of the issues listed. Take a peak and decide if it's something you'd like to try
Makrilli said:
He meant using adb sideload
Click to expand...
Click to collapse
ya i tried, it wouldnt connect to the phone, tried multiple tweaks from pc side and device side and couldnt get it to work, im probably messing it up somewhere but i tried to follow various "tutorials" to the letter
markbencze said:
have you had a look at my thread here? sure sounds like one of the issues listed. Take a peak and decide if it's something you'd like to try
Click to expand...
Click to collapse
Hey thats exactly how it started when i first reflashed cm11, but i managed to get through and force disable audiofx, from there though it just kept crashing system ui, i will definitely try this when i get outta class.
is there something different ill need to do based on having already disabled audiofx?
ugly_duckling said:
Hey thats exactly how it started when i first reflashed cm11, but i managed to get through and force disable audiofx, from there though it just kept crashing system ui, i will definitely try this when i get outta class.
is there something different ill need to do based on having already disabled audiofx?
Click to expand...
Click to collapse
Disabling it will not fix your issue. My thread tells you what needs to happen. Generally when people decide to try new ideas without proper knowledge is when they get into trouble
ugly_duckling said:
I tried that a hundred times, the problem is once the screen turns off, if you keep holding vol up it never comes back on, its something i have never seen before and its exxtremely frustrating. Its like fastboot doesnt exist.
Click to expand...
Click to collapse
Just a tip, if u can go in fastboot mode, try to disconnect usb from phone first , and then try
markbencze said:
Disabling it will not fix your issue. My thread tells you what needs to happen. Generally when people decide to try new ideas without proper knowledge is when they get into trouble
Click to expand...
Click to collapse
ya i gotcha, i was just wondering if i needed to re-enable audiofx for stuff to work, my other problem with this method is, and correct me if im wrong, but i believe i need to be in fastboot mode? which for some reason is unattainable at the moment..
ugly_duckling said:
ya i gotcha, i was just wondering if i needed to re-enable audiofx for stuff to work, my other problem with this method is, and correct me if im wrong, but i believe i need to be in fastboot mode? which for some reason is unattainable at the moment..
Click to expand...
Click to collapse
Yes and then follow the directions in my thread
luka1002 said:
Just a tip, if u can go in fastboot mode, try to disconnect usb from phone first , and then try
Click to expand...
Click to collapse
idk why, but i read this post and said "what the hell, ill try it again" out loud to myself. unplugged my phone, held down the volume up key and turned it on, IT WENT STRAIGHT TO FASTBOOT. fml thanks guys, i think i can fix everything from here...i dont know how i managed to never do it correctly even though before this happened i booted into fastboot regularly to flash different ROMS...thank you guys very much for the help
Hey folks...I'm running into a problem I was hoping someone might be able to help with.
Earlier today I pulled my phone out of my pocket at work and saw that it was off...I thought that the battery must have died sooner than I thought. I started charging it in the car on the way home and it wouldn't boot up like normal. It would get to the google or "dots" screen and then reboot. I again thought that the battery might just be really low. After getting home and charging the phone all the way I still can't get it to boot up. As of now, one of 3 things will happen...
1-The phone will turn on, get to the google screen and bootloop (usually when plugged in).
2-The phone will turn on, get to the google screen and freeze.
3-Get to the "dots" screen and either swirl forever or eventually reboot and do one of the above again.
I've read some threads where people suggest this is a faulty power button, that doesn't seem to be the case for me though because I can get into fastboot and it won't select anything or turn off without me doing it.
I've used WugFresh NRT and wiped/reflashed android. I'm running out of ideas. Do you have any others?
I was running the stock 5.0.1, unlocked, not currently rooted.
Thanks!
kyle313 said:
Hey folks...I'm running into a problem I was hoping someone might be able to help with.
Earlier today I pulled my phone out of my pocket at work and saw that it was off...I thought that the battery must have died sooner than I thought. I started charging it in the car on the way home and it wouldn't boot up like normal. It would get to the google or "dots" screen and then reboot. I again thought that the battery might just be really low. After getting home and charging the phone all the way I still can't get it to boot up. As of now, one of 3 things will happen...
1-The phone will turn on, get to the google screen and bootloop (usually when plugged in).
2-The phone will turn on, get to the google screen and freeze.
3-Get to the "dots" screen and either swirl forever or eventually reboot and do one of the above again.
I've read some threads where people suggest this is a faulty power button, that doesn't seem to be the case for me though because I can get into fastboot and it won't select anything or turn off without me doing it.
I've used WugFresh NRT and wiped/reflashed android. I'm running out of ideas. Do you have any others?
I was running the stock 5.0.1, unlocked, not currently rooted.
Thanks!
Click to expand...
Click to collapse
Did you try flashing factory images?
ryukiri said:
Did you try flashing factory images?
Click to expand...
Click to collapse
Yeah, that was what I flashed :/
If you can get into fastboot you "should" be able to flash stock images... Obviously this will revert any root and you will need to flash TWRP/CWM recovery after.
I assume you have a Windows PC with fastboot/adb setup and all drivers etc..
- Download latest "stock" hammerhead images (I cannot post links due to XDA rules... so: "developers.google.com/android/nexus/images#hammerhead"
- Extract the .tgz archive contents on your PC into a folder
- Boot the N5 into fastboot and plug USB cable from phone into your PC
- Go to the folder with the extracted files and run the "flash-all.bat" script on Windows
**Hopefully at this point your device will start to respond.. I.e, on fastboot screen, at the bottom you will see "writing" or something, as the script runs on the command window on your PC.**
If this works, you should be able to reboot once complete and then wait to see if you can get back into your phone.. then you can fastboot again and flash custom recovery, and then whatever rom.
If however you have a hardware issue (i.e, even after the above process it fails) then I am not sure what you could do... I guess ensure it has a complete charge. If you can get into fastboot and the buttons are responsive then it should not be a faulty power button.
Hope this helps :good:
Have you tried a simple factory reset? Reason I ask is it was working fine so sounds like something needs "flushing out" clear cache etc.
kyle313 said:
Hey folks...I'm running into a problem I was hoping someone might be able to help with.
Earlier today I pulled my phone out of my pocket at work and saw that it was off...I thought that the battery must have died sooner than I thought. I started charging it in the car on the way home and it wouldn't boot up like normal. It would get to the google or "dots" screen and then reboot. I again thought that the battery might just be really low. After getting home and charging the phone all the way I still can't get it to boot up. As of now, one of 3 things will happen...
1-The phone will turn on, get to the google screen and bootloop (usually when plugged in).
2-The phone will turn on, get to the google screen and freeze.
3-Get to the "dots" screen and either swirl forever or eventually reboot and do one of the above again.
I've read some threads where people suggest this is a faulty power button, that doesn't seem to be the case for me though because I can get into fastboot and it won't select anything or turn off without me doing it.
I've used WugFresh NRT and wiped/reflashed android. I'm running out of ideas. Do you have any others?
I was running the stock 5.0.1, unlocked, not currently rooted.
Thanks!
Click to expand...
Click to collapse
Did you choose the right model and firmware before you flash in WugFresh NRT?
The above could be right, however when I've used it, it's pointed out if I made that mistake. Having used his software dozens of times I've found it will bring any Nexus 5 back to life.
howard bamber said:
The above could be right, however when I've used it, it's pointed out if I made that mistake. Having used his software dozens of times I've found it will bring any Nexus 5 back to life.
Click to expand...
Click to collapse
Hello! I am apologize for that I didn't read the OP carefully. This happened to me once in that particulary way, but it was immediately after flashing. OP says that it happened suddenly, without reason. So now I am the one, who doesn't read, right? Sorry for that.
Regards, Zagor
Thanks for the responses, but I'm still having trouble.
I have been able to successfully write the newest stock android 3 times (1 without full wipe, 2 with) and the phone still can't boot up and goes through one of the three issues above.
I've also been able to get to the system recovery from the bootloader and I've tried wiping the cache and doing a factory reset from there and the problem remains.
I'd contact google, but I bought it at launch so I don't think they'll do anything for me since it's been 1+ years.
kyle313 said:
Thanks for the responses, but I'm still having trouble.
I have been able to successfully write the newest stock android 3 times (1 without full wipe, 2 with) and the phone still can't boot up and goes through one of the three issues above.
I've also been able to get to the system recovery from the bootloader and I've tried wiping the cache and doing a factory reset from there and the problem remains.
I'd contact google, but I bought it at launch so I don't think they'll do anything for me since it's been 1+ years.
Click to expand...
Click to collapse
Sounds like you have a bad nand sector. From fastboot try:
Code:
fastboot oem lock
Then reboot into fastboot and check if it's locked or not. If the device isn't locked your emmc is corrupt and there is nothing you can do. If that is the case call Google and they will most likely help you out with a RMA.
theesotericone said:
Sounds like you have a bad nand sector. From fastboot try:
Code:
fastboot oem lock
Then reboot into fastboot and check if it's locked or not. If the device isn't locked your emmc is corrupt and there is nothing you can do. If that is the case call Google and they will most likely help you out with a RMA.
Click to expand...
Click to collapse
I was actually able to relock the phone.
Luckily I called google and they're going to send me a replacement.
If anyone else has any other ideas, I'll still take them...I'd rather not be without a phone for the next week!
You won't be without a phone - they are sending a refurbish unit to you , putting a block on your credit card and waiting for you phone to arive at them. Once that happens they will release the funds.
He there, just recently my phone had an update and i said yes to it. After the update completed It rebooted but never started back up.
When turned on, it just get up to the OnePlus One logo screen and stays there. I have tried a factory reset as I can access the recovery menu but the factory reset doesn't seem to do anything. I let the battery drain until the phone died and then charged it but it still will not start. Plugging it into my PC lets it charge but it does not let you access the storage. Its not a driver problem as it was working fine before the update.
I have tried fast boot but it just gets stuck on the fast boot screen.
I tried using OnePlus One Toolkit but it cant find the phone
I have read that I need to flash it but it would seem I need to transfer a file onto the phone but nothing recognizes the phone to transfer it to.
Can anyone help?
Thanks in advance,
Zastarx said:
He there, just recently my phone had an update and i said yes to it. After the update completed It rebooted but never started back up.
When turned on, it just get up to the OnePlus One logo screen and stays there. I have tried a factory reset as I can access the recovery menu but the factory reset doesn't seem to do anything. I let the battery drain until the phone died and then charged it but it still will not start. Plugging it into my PC lets it charge but it does not let you access the storage. Its not a driver problem as it was working fine before the update.
I have tried fast boot but it just gets stuck on the fast boot screen.
I tried using OnePlus One Toolkit but it cant find the phone
I have read that I need to flash it but it would seem I need to transfer a file onto the phone but nothing recognizes the phone to transfer it to.
Can anyone help?
Thanks in advance,
Click to expand...
Click to collapse
Your persist partition might be corrupt. Grab this:
https://drive.google.com/file/d/0B98G0KTJwnBFUnJCNldodGs2dE0/view?usp=docslist_api
Then do this with fastboot:
Code:
fastboot erase persist
fastboot flash persist persist.img
Didn't work sadly. Maybe I should just flash everything?
Zastarx said:
Didn't work sadly. Maybe I should just flash everything?
Click to expand...
Click to collapse
Yeah, it's worth a shot. You can find full instructions in section 8 of my guide here:
http://forum.xda-developers.com/showthread.php?t=2839471
Yay!
It worked, thanks a lot!
Hey community, today i was sent here by a friend that though maybe this forum can help, a few days ago i was on my Infocus m808 watching videos on youtube, videos were of the new COD WWI, however my phone randomly shut off and then kept vibrating when i turned it on, nothing appeared so i left it a few hours (5 roughly) then i though i would try it again and i tried it again, and now it actually shows me a screen saying "Infocus Powered by android" then below in little white writing it says "Could not load the correct dtb file!!!!!!" any clue how i can fix this?
Jakeyiii said:
Hey community, today i was sent here by a friend that though maybe this forum can help, a few days ago i was on my Infocus m808 watching videos on youtube, videos were of the new COD WWI, however my phone randomly shut off and then kept vibrating when i turned it on, nothing appeared so i left it a few hours (5 roughly) then i though i would try it again and i tried it again, and now it actually shows me a screen saying "Infocus Powered by android" then below in little white writing it says "Could not load the correct dtb file!!!!!!" any clue how i can fix this?
Click to expand...
Click to collapse
Sounds like you modified your boot.img or your boot.img got corrupted.
It seems you'll have to flash your stock firmware to fix this.
Sent from my SM-S903VL using Tapatalk
Response
Hello, I'm experiencing logging problems with the jakeyiii account. However umm your saying its the wrong boot.IMG I haven't touched the boot atall. I was watching YouTube videos while being connected to the laptop for charge. Even if I was to try putting a stock boot image onto the phone its impossible because soon as I see the logo "InFocus" it comes up saying something "cannot load the correct dtb file!!!!" Can't boot into fast boot either as when I try to boot into fastboot that's the message it says "cannot load the correct dtb file!!!!!" When trying to turn on normally it just vibrates and does nothing.
Any clue how to get stock back on?
Jplay444 said:
Hello, I'm experiencing logging problems with the jakeyiii account. However umm your saying its the wrong boot.IMG I haven't touched the boot atall. I was watching YouTube videos while being connected to the laptop for charge. Even if I was to try putting a stock boot image onto the phone its impossible because soon as I see the logo "InFocus" it comes up saying something "cannot load the correct dtb file!!!!" Can't boot into fast boot either as when I try to boot into fastboot that's the message it says "cannot load the correct dtb file!!!!!" When trying to turn on normally it just vibrates and does nothing.
Any clue how to get stock back on?
Click to expand...
Click to collapse
I said it sounded as if "you" modified boot.img OR your boot.img got corrupted "on its own". You said that you didn't modify anything so of the two possibilities I listed, which possibility does that leave?
Sent from my SM-S903VL using Tapatalk
Response
The remaining possibility is it just got corrupt on its own this is the second time this has happened to me. The first one happened like 4 months after getting it and the n again 9 months after that. So currently stuck using a family's phone to message here haha.
If I can't boot the phone in faceboot or even recovery any clue how I can solve this?
Jplay444 said:
The remaining possibility is it just got corrupt on its own this is the second time this has happened to me. The first one happened like 4 months after getting it and the n again 9 months after that. So currently stuck using a family's phone to message here haha.
If I can't boot the phone in faceboot or even recovery any clue how I can solve this?
Click to expand...
Click to collapse
You might can try the script from the thread linked below in the "using adb" section, it might allow you get connected to adb while in bootloop at the InFocus screen.
From there you can try a dd command to push a copy of your device's boot.img if you can find a copy of your firmware and extract the .img from it or you can try getting someone with your device to pull a copy of boot.img from their device for you to use.
Have you tried booting to safe mode?
Sent from my SM-S903VL using Tapatalk
Hello
Yes I've tried to boot into safe mode can't boot what so ever. It just vibrates if I try fast boot I get the DTB file error. And no one near me has a in focus.
I can't enable USB debugging because it won't boot and can't use ADB because it won't find the device as when USB is connected the phone trys to boot and restarts constantly .
have you found solution to it bcos me have same problem
Jplay444 said:
Hello
Yes I've tried to boot into safe mode can't boot what so ever. It just vibrates if I try fast boot I get the DTB file error. And no one near me has a in focus.
I can't enable USB debugging because it won't boot and can't use ADB because it won't find the device as when USB is connected the phone trys to boot and restarts constantly .
Click to expand...
Click to collapse
i need help too