Hi to all!
I have a Cherry Mobile One G1, pure stock (Android N, not rooted, no recovery and USB Debugging DISABLED), been with me for almost 2 years bought brand new. What happened was I was going to download a movie then suddenly the phone restarted and its stuck on bootloop. The only thing I can do with it is boot it to fastboot. It can be detected by my pc's device manager as Android Bootloader Interface but ADB terminal cant seem to detect it. Is there anything I can do to revive it? If there is, can any genius mind help me out?
My dilemma now is trying to turn USB debugging via fastboot which is not possible since adb could not even detect my device. If only I can have it enabled, I would know how to fix the rest.
Any help would be very much appreciated. Thank you and God Bless!
This happened to me before. factory reset via stock recovery fixed it. If you can't boot to recovery try removing the sd card first. It will take a while to reset, don't take the battery off while it does and make sure it's charged.
Related
Hello to everyone. I have in my possession an Asus Memopad 7 Me173x as the title suggest. It was given to me from a friend to recover it but it seems harder than I figured. Usb debugging mode is not enabled, it cannot go to recovery - when I boot it into recovery it shows me a dead android with a red triangle. I have tried flashing it with numerous different roms using SP Flash Tool, getting all sorts of errors, get past one stumble upon another one. I Installed Linux on my desktop pc to try and flash recovery using fastboot, I added the proper text for the android rules file, but I'm getting the "waiting a device" error. The tablet isnt hardly bricked, like it doesnt turn on. Actually the thing is it boots to android, an error pops, the tablet restarts over and over. When I power it on once, I have to take it apart and remove the battery, because it cant turn off, just keeps rebooting. I thought if I could flash custom recovery and use an sd card to install stock rom using the recovery it should fix. The bootloader is locked, usb debugging isnt checked and the tablet doesnt boot properly. Any guidance towards fixing it will be greatly appreciated. Thank you in advance.
I'm also new to linux, but kind of getting along.
I did a google research if there is a way to enable usb debugging if the tablet is bricked, but sadly I did not find anything.
Hey guys,
recently i found myself in a sticky situaiton, my USB connection to PC stopped working. Stometimes charging doesn't work until I reboot the phone, random car mode etc...
I tried everything, from reseting my ports on PC, reinstaling drivers, wiping phone cashe, factory reset and so on. PC just says "USB device is not recognized" .
So I wonder how to make the phone varanty possible without USB connection. Maybe trough terminal emulator?. I had TWRP recovery installed and I flashed stock recovery image directly from it, but it's still tampered and I have to get rid of it before taking it to store for varanty.
Any seggestions? I'm pretty desperate, pretty sure it's usb port on the phone or motherboard.
InFam0 said:
Hey guys,
recently i found myself in a sticky situaiton, my USB connection to PC stopped working. Stometimes charging doesn't work until I reboot the phone, random car mode etc...
I tried everything, from reseting my ports on PC, reinstaling drivers, wiping phone cashe, factory reset and so on. PC just says "USB device is not recognized" .
So I wonder how to make the phone varanty possible without USB connection. Maybe trough terminal emulator?. I had TWRP recovery installed and I flashed stock recovery image directly from it, but it's still tampered and I have to get rid of it before taking it to store for varanty.
Any seggestions? I'm pretty desperate, pretty sure it's usb port on the phone or motherboard.
Click to expand...
Click to collapse
you cannot remove tempered from bootloader and it will show relocked. Its there for a reason, so HTC can see if you been tampering with the phone.
Yes it does void the #warranty.
That said, I send my phone to HTC to replace charging port and they did not charge me .. Have the phone for over 3 years and its rooted.
Tak to HTC but bear in mind Depending the country there's a 50% chance they will charge you.
so i rooted my note 5 sm-n920p phone using odin to flash everything i even had twrp flashed to it. the phone worked properly for months then one day i ended up switching off oem unlock forgetting it would trigger my frp lock if my phone had died well my phone died and when i went to turn it back on i got stuck in the frp boot loop i can get it into odin mode but it will not go into twrp recovery mode at all. i know how to flash the stock firmware to my phone but my problem is i cannot get any computer to recognize my phone it says one of the useb devices attatched to this computer has malfunctioned and windows does not recognize it. ive tried everything from uninstalling my usb drivers and reinstalling them and manually installing samsung android adb interface directly to the unkown device. odin will not pick up my phone and add it for me to flash it back to stock and factory reset it im willing to lose all my data i just want my phone to be able to work. if there is anyone with any advice or is willing to assist me to get my phone back to a proper working state id really appreciate it. also i am not sure if i even need the computer to recognize my phone not sure if i just need to keep trying different versions of odin but i know that my cable isnt the problem because ive tried it with my other note 5 and it works ive tried multiple cables with the frp boot looped phone that i have and i cant seem to figure it out why odin wont pick it up. as far as i know usb debugging is on and oem unlock is disabled on my frp locked note 5 please someone help me.
Right...
I'm going through the exact same thing right now. In all of the guides right now, it seems like theres always something that doesn't work out with our specific phone... lame sauce tbh.
xjackgimleyx said:
so i rooted my note 5 sm-n920p phone using odin to flash everything i even had twrp flashed to it. the phone worked properly for months then one day i ended up switching off oem unlock forgetting it would trigger my frp lock if my phone had died well my phone died and when i went to turn it back on i got stuck in the frp boot loop i can get it into odin mode but it will not go into twrp recovery mode at all. i know how to flash the stock firmware to my phone but my problem is i cannot get any computer to recognize my phone it says one of the useb devices attatched to this computer has malfunctioned and windows does not recognize it. ive tried everything from uninstalling my usb drivers and reinstalling them and manually installing samsung android adb interface directly to the unkown device. odin will not pick up my phone and add it for me to flash it back to stock and factory reset it im willing to lose all my data i just want my phone to be able to work. if there is anyone with any advice or is willing to assist me to get my phone back to a proper working state id really appreciate it. also i am not sure if i even need the computer to recognize my phone not sure if i just need to keep trying different versions of odin but i know that my cable isnt the problem because ive tried it with my other note 5 and it works ive tried multiple cables with the frp boot looped phone that i have and i cant seem to figure it out why odin wont pick it up. as far as i know usb debugging is on and oem unlock is disabled on my frp locked note 5 please someone help me.
Click to expand...
Click to collapse
NEVER let your phone die. Charge immediately if battery goes to 15%. You need a charged battery to do any flashing so yeah, you may need to replace or charge the battery to flash a 4 file firmware.
Hi all!
Made a really stupid mistake this morning: I was getting frustrated with Linneage 15.1 battery performance, so I tried flashing latest franco kernel (without reading that 15.1 doesn't like custom kernels; mistake #1).
No big deal right? I mean sure, I didn't make a back up first (Mistake #2) but it shouldn't matter because I can just go into twrp and factory reset and reflash everything.
So off I went to copy over the zips to my phone -- went ahead and wiped everything (mistake #3) and then opened up windows explorer to copy over the zips. Turned out my computer couldn't see my phone.
I tried mounting and unmounting and installing and uninstalling drivers. Moving over to my other computer (linux mint) messing around with adb sideloads, and lastly tried using OTG. Turned out my computer just couldn't register my phone at all with adb.
So then I switched to fastboot -- at the very least I should be able to reflash stock and then root and then install custom stuf, right? But I couldn't get my phone to even register on windows or linux with driver changes using fastboot!
I was pretty upset at this point (still am, admittedly).
In fastboot mode whenever I plug in my phone my computer doesn't even bat an eye, and my phone just says it's waiting for a data cable connection. Windows will register it after a while as a "code 43: Windows has stopped this device because it has reported problems" after a while but I still wasn't able to get the right drivers to register the device. Doesn't even show up in lsusb in linux.
Wondering now if maybe when the device was alive I forgot to enable adb debugging first or maybe it doesn't register because it was set to charge only in the usb mode setting. Is there a way to change those settings in recovery like through the terminal? I would love to hear any possible solutions, I've been googling and search xda all over the place so any insight would be really appreciated.
Fortunately I had an extra shamu (with a very cracked screen) left over that I switched to in the mean time, but I'd like to get my old phone back in working order if possible! Any help or insight is appreciated!
gunha said:
Hi all!
Made a really stupid mistake this morning: I was getting frustrated with Linneage 15.1 battery performance, so I tried flashing latest franco kernel (without reading that 15.1 doesn't like custom kernels; mistake #1).
Click to expand...
Click to collapse
You even made more errors. You don't seem to read properly. Franco does only support shamu up to nougat.
- Did you install the latest USB drivers and latest platform tools (adb, fastboot ...)
- Did you boot you phone into bootloader when you tried to connect?
Yup! I installed drivers from Google when I downloaded the platform-tools. I put my phone in bootloader mode when using fastboot, and my phone never indicated 'USB transfer cable connected' it just said 'connect usb.' also fastboot just said waiting for devices when I tried doing a getvar all....
try it on another laptop, try a new usb cable...you seem to have done everything right
I've tried a bunch of different computers and cables... the weirdest thing is that it'll use the cable to charge just fine, but won't let me transfer anything by mtp (in recovery) or fastboot when in its bootloader :/ still get "connect usb data cable" even if the battery is charging
gunha said:
I've tried a bunch of different computers and cables... the weirdest thing is that it'll use the cable to charge just fine, but won't let me transfer anything by mtp (in recovery) or fastboot when in its bootloader :/ still get "connect usb data cable" even if the battery is charging
Click to expand...
Click to collapse
Could be the cable. But the USB port could also be the cause. The simplest solution could be that the port is just full of dust. In that case, cleaning will help.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
IF you still have access to TWRP, you can move your zips on an usb drive and connect it via otg and mount in TWRP and flash from the USB drive. Might help.
hi, guys
my samsung note 5 has been rooted for a long time, i disabled USB debugging a couple of days ago for some reason i dont remember and i forgot to enable it. i reboot my phone the day before yesterday, and it went reboot loop, theres a note that says custom binary blocked by FRP lock. i was trying to flash a stock ROM in download mode, but the windows10 dosent recognize the USB device.
so im coming here for help, guys, is there any chance that i can get my phone back? what should i do? i can be sure that my phone cable is good, cus i tested it on another phone, i tried some samsung usb drivers by installing/uninstalling then restarting windows, but it dosent help, i think its just because i disabled the USB debugging, so windows cant recognize it.
guys, is there anything i can do to get my phone back?plz, help me! ill appreciate it! thank you very much!
nope, unrelated to usb-debugging. you need to boot into download mode for flashing with Odin. regarding FRP read instructions on samfw.com