Database Info

[Q] Doesn't load into bootloader , or into system.Stuck

Hello everyone , i have an issue , i had custom room on my phone. I wanted to install another custom ROM so i cleared cache i think i deleted something that i didnt need to delete when i was using TWRP recovery , after i cleared cached i restarted the phone and now its not booting anywhere not boot loader not recovery nowhere it just stuck on HTC quite brilliant screen (with htc warning message about that it is for developers only version)
please help
I tried pluging in to computer cmd commands fastboot just saying waiting for device , some tool kits also can't get in touch with device
when i power it on computer does have usb sound but i dont see any device in the list , i have feeling that it eject its as soon as it connect to it.
Phone is unlocked rooted ,but its s-on
Please help!!!

lins_nt said:
Hello everyone , i have an issue , i had custom room on my phone. I wanted to install another custom ROM so i cleared cache i think i deleted something that i didnt need to delete when i was using TWRP recovery , after i cleared cached i restarted the phone and now its not booting anywhere not boot loader not recovery nowhere it just stuck on HTC quite brilliant screen (with htc warning message about that it is for developers only version)
please help
I tried pluging in to computer cmd commands fastboot just saying waiting for device , some tool kits also can't get in touch with device
when i power it on computer does have usb sound but i dont see any device in the list , i have feeling that it eject its as soon as it connect to it.
Phone is unlocked rooted ,but its s-on
Please help!!!
Click to expand...
Click to collapse
UPDATE!!!!!!!!!!! when i power phone off computer does see the device via usb port

lins_nt said:
UPDATE!!!!!!!!!!! when i power phone off computer does see the device via usb port
Click to expand...
Click to collapse
You Can delete this post i got it fixed

lins_nt said:
You Can delete this post i got it fixed
Click to expand...
Click to collapse
Please tell my how you fixed ??

Help Please Please with my bricked Alcatel Ot 5020 (Evolve)

This is my first time asking for help directly here, I always find the answers in the other threads solved, but this time I can not find an answer.
I have a alcatel one touch 5020t evolve its a MTK6575 (t-mobile but is used in el salvador), I used to MTKDroidTools to install CWM Revocovery, I did back up with the same program but apparently did not because i look and i cant find anything in the back up folder, only left some files called:
ALCATEL-ONE-TOUCH-5020T_130818__boot_patched_140129-175612.img
ALCATEL-ONE-TOUCH-5020T_130818__recovery_140129-175612.img
in the folder called recovery.
Now the phone on, the startup screen and then turns off, I can enter a menu by pressing on + vol +, where it says enter recovery mode or normal mode, before they tried to install cwm I could go in and delete everything from there, now I get the menu of recovery mode and normal mode but since does not enter recovery mode, got it turns off, like when entering the normal mode.
I tried to flash with sp flash tool but I get an authentication error that is on the img
The pc recognizes my phone, makes the sound when you connect something, now if we go to Device Manager, a device called first appears:
MTK USB Port
After that is disconnected and then a new one appears called :
Media Tek Preloader USB VCOM Port
But there ir a problem, then this becomes a repetitive one disconnects and connects the other, but only when I connect the phone without battery only stays in:
MTK USB Port.
Help what can i do to revive my phone ???????????????

you found any solution i have the same problem ?

:/
harold99 said:
you found any solution i have the same problem ?
Click to expand...
Click to collapse
Sorry, but i could not solve yet, nobody helps me

So were you able to flash cwm to the device? there are several threads requesting a custom recovery for this device and either way could you upload those first two .img files I may be able to use them to try to recover my device
*** Okay so the problem is that the boot loader on this device is locked and for the time being a custom recovery is not possible. I still have access to the recovery on my device so if I could find a way to build an update file from the source code or an official firmware update I could fix mine. Yours may be too far gone. sorry.

any luck with a solution? How close to one have you got to...

ipeedalil said:
*** Okay so the problem is that the boot loader on this device is locked and for the time being a custom recovery is not possible.
Click to expand...
Click to collapse
A friendly warning: Don't just mess around with the Bootloader, that's one delicate piece of software, try to find how to unlock it first, then we can talk of changing the recovery. For rooting purposes I can attest that you can safely root it using the OneClickRoot solutions around the net. I used some chinese root and it worked like a charm.

Soft Bricked 5020T
carlitox2301 said:
This is my first time asking for help directly here, I always find the answers in the other threads solved, but this time I can not find an answer.
I have a alcatel one touch 5020t evolve its a MTK6575 (t-mobile but is used in el salvador), I used to MTKDroidTools to install CWM Revocovery, I did back up with the same program but apparently did not because i look and i cant find anything in the back up folder, only left some files called:
ALCATEL-ONE-TOUCH-5020T_130818__boot_patched_140129-175612.img
ALCATEL-ONE-TOUCH-5020T_130818__recovery_140129-175612.img
in the folder called recovery.
Now the phone on, the startup screen and then turns off, I can enter a menu by pressing on + vol +, where it says enter recovery mode or normal mode, before they tried to install cwm I could go in and delete everything from there, now I get the menu of recovery mode and normal mode but since does not enter recovery mode, got it turns off, like when entering the normal mode.
I tried to flash with sp flash tool but I get an authentication error that is on the img
The pc recognizes my phone, makes the sound when you connect something, now if we go to Device Manager, a device called first appears:
MTK USB Port
After that is disconnected and then a new one appears called :
Media Tek Preloader USB VCOM Port
But there ir a problem, then this becomes a repetitive one disconnects and connects the other, but only when I connect the phone without battery only stays in:
MTK USB Port.
Help what can i do to revive my phone ???????????????
Click to expand...
Click to collapse
I have had a OT-5020T with all the same symptoms as you describe. After much research and diagnosis here is what I have learned and know to be true.
You have soft bricked your phone. For this phone it results in the boot loop you described. At present a Custom Recovery that works is not available for this phone and any attempt to flash an existing one results in a soft brick. There are apps that will flash a Custom Recovery while the phone is one but once you reboot ... !!! Bricked!! This is because ...
a) the memory mapping for this phone is different that other OT-5020 models, so the Custom Recovery placement and indexing is wrong when flashed, causing the boot-loop, and inability for Custom Recovery to load,
and ,
b) the bootloader is locked for the 5020T (different story for other OT 5020 models), and no one has found a way around it yet. Trying to flash back stock firmware for the OT-5020T requires it to be unlocked.
One Touch Update 2.8.0 doesn't seem to want to work one the phone has been altered in this way. SPtools won't work because you need an accurate OT-5020T scatter file (memory map) ,and certification file (bootloader unlocker) to flash any image. In addition to all this the phone doesn't maintain a steady usb connection long enough to allow use of android tools adb and fastboot commands although it does can stay connected in a different mode.
What I have used to restore my phones firmware is a package from Furious Gold that allows the phone to be flashed to factory firmware. I have used it successfully, so I can confirm that the phone wasn't a permanent brick.

Alcatel 5020t T-Mobile plis help flshe file

please am in need of alcatel 5020w firmware, please if someone is having it or having that same phone and want to read the firmware for me my email is [email protected]
thanks

HTC One Mini (M4_U4) Softbricked, OEM not unlocked, USB debug not enabled, bootloop

Hi all,
My HTC One Mini crashed one month after warranty (Boo!). I can get to the FASTBOOT and BOOTLOADER screen and select options. However, the Factory reset and recovery just cause a vibration and get be back to FASTBOOT menu. The phone is *** LOCKED ***.
After a few false starts on linux and mac machines, I've installed WinDroid Toolkit v3.1 on Windows 7. I have gotten the Token ID and used it to get an Unlock_code.bin via email from the HTC developers website (Cannot link as newb). However, when I follow the instructions in WinDroid it recommends that newer devices require "Enable OEM Unlock" to be set:
I cannot do this now. I continue but when it says a menu will appear on the phone, the menu does not and the phone remains in *** LOCKED *** state. I tried continuing with step 2 "Flashing a TWRP" but it does nothing.
TL;DR Am I screwed with having previously unlocked OEM on my HTC One Mini, now that it is soft-bricked?

I'm not that good at this stuff, but managed to get mine unlocked and a recovery on it via this link
sadly mine still has a problem in that it's now stuck in a boot loop, so don't use Oneclickroot as I did in my post here
hopefully you will get yours to work ok, but when you get to instruction 17 you may find that HTC website is quite fussy with the code you copy/paste
when you copy the Identifier block into Notepad or whatever, ensure you don't get any leading blank spaces before you submit it to HTC.
this excerpt from mine had blank spaces where I have inserted red X's, but it worked with them removed and HTC then emailed me the Unlock_code.bin file
XX<<<< Identifier Token Start >>>>
XX36ADF279412BE14D5002935236B24913
XXetc
XXetc
XX<<<<< Identifier Token End >>>>>
I hope this is of some use mate
---------- Post added at 02:39 PM ---------- Previous post was at 02:26 PM ----------
sorry,
lost the plot on my first reply and forget about the OEM unlock bit ...
to get that OEM unlock bit you would normally
first Enable Developer Modeon your phone by Launching the Settings Application -
Scroll Down and Tap on About Phone(or About Device) - Locate the Build Number Section - Tap on the Build Number Option 7 Times -
Go Back to the Main Settings Page - Scroll Down and Tap on Developer Options and it's found there
but given that you are in is bad a place as me in that we cannot get a bootup, I'm afraid I can't offer any more info,
but it's worth knowing anyway in case you do get booted up

Hi, i have the same issue, but a little different.
My phone was in a box for like 2 months, and then i decide to turn it on again, and i faced the same problem as the OP, but my One Mini is UNLOCKED, and i can't lock it again because i get an error in ADB. I try to enter on recovery (and flashed three differents recoveries without sucess), and reboot in bootloader, then try to factory reset, and reboot bootloader again. It don't do anything, only turn on when i plug the usb and enter in bootloader but no more than that. i've try to flash a RUU too, but it give me the error 171. i tried too the method with the rubber band pressing the power button to cause a reboot loop and get enough charge to launch the system but nothing, i don't see any results. I'm one step closer to give up, please help, i tried everything and nothing has worked for me. If need more information don't doubt on asking me. I really appreciate any help you can provide.

I'll try mate ... but perhaps you are asking for help from the wrong guy! - firstly I have to say mine is still in a very bad place! -
I managed to get a permanent TWRP on it, installed a lovely rom named InsertCoin on it, rebooted, and all seemed fine, but then the battery drained rapidly and it would not charge - that issue is ongoing and I'm spending ages on it just now..
Firstly can you confirm that you can enter Bootloader and select Fastboot, and that your phone is then recognised by your PC?
ie: let me know what happens when you press power and vol down together, select fasboot, goto PC, run ADB, cable phone to PC,
then issue the command ADB devices
can you also upload a photo of your bootloader screen

carkev said:
I'll try mate ... but perhaps you are asking for help from the wrong guy! - firstly I have to say mine is still in a very bad place! -
I managed to get a permanent TWRP on it, installed a lovely rom named InsertCoin on it, rebooted, and all seemed fine, but then the battery drained rapidly and it would not charge - that issue is ongoing and I'm spending ages on it just now..
Firstly can you confirm that you can enter Bootloader and select Fastboot, and that your phone is then recognised by your PC?
ie: let me know what happens when you press power and vol down together, select fasboot, goto PC, run ADB, cable phone to PC,
then issue the command ADB devices
can you also upload a photo of your bootloader screen
Click to expand...
Click to collapse
i don't need to press vol down and power together, the phone enter in bootloader once you plug the usb cable. it do that alone.
This is what i get
C:\adb>adb devices
List of devices attached
C:\adb>
the phone is recognized by HTC Sync manager but i can't see it in ADB.

a few things things jump out at me ...
1. from your photo the screen is shattered! - even though I don't like being beaten by phones I would scrap it
the repair would cost more than you can get one from ebay for - about £40.00
2. "abd devices" should return you something like ... "List of devices attached sh3d7h3dj631f6a7" - when it doesn't it show a device number it's usually your drivers
3. you may think that's not it since you say that it is recognised by HTC Sync when on your PC, but I had read that HTC sync is unreliable and that the drivers are not the best
the one's I used were HTC-Mobile-USB Driver-v4.17.0.001.exe but I can't remember where I got them and will upload them later today and send you a link.
(also, it pays to plug your usb cable into a rear port on your PC when doing this kind of work as front are not as reliable)
4. your Hboot is shown as 2.22 -this also can be a problem for TWRP see this link
5. the download link he has is broken, so get any TWRP above 2.7 from their website here

carkev said:
a few things things jump out at me ...
1. from your photo the screen is shattered! - even though I don't like being beaten by phones I would scrap it
the repair would cost more than you can get one from ebay for - about £40.00
Click to expand...
Click to collapse
Hahaha, i know, i have the replacement here, i'll change it once i solve this problem.
carkev said:
2. "abd devices" should return you something like ... "List of devices attached sh3d7h3dj631f6a7" - when it doesn't it show a device number it's usually your drivers
3. you may think that's not it since you say that it is recognised by HTC Sync when on your PC, but I had read that HTC sync is unreliable and that the drivers are not the best
the one's I used were HTC-Mobile-USB Driver-v4.17.0.001.exe but I can't remember where I got them and will upload them later today and send you a link.
(also, it pays to plug your usb cable into a rear port on your PC when doing this kind of work as front are not as reliable)
4. your Hboot is shown as 2.22 -this also can be a problem for TWRP see this link
5. the download link he has is broken, so get any TWRP above 2.7 from their website here
Click to expand...
Click to collapse
2. I will leave you down here exactly what i get when i type "adb devices" (with an attached image)
3. i have installed the latest HTC drivers, and i tried connecting my phone to front an rear usb ports, both of them. No results.
4. Down here i'll leave you an attached image of what i get when i try to install a recovery by typing "fastboot flash recovery recovery.img" (i changed the name to recovery.img of course) and the phone seems installing the recovery in fastboot but it gave me that error in adb and when i try to enter in recovery it reboots on bootloader.

your first image does not 'see' your device mate, so there is no point in trying a flash of anything
until you get a response from "adb devices" that shows a device number you have no chance of getting anywhere!
I am quite certain that the problem MUST be with your drivers
my advice would be to uninstall the HTC Sync and clean out any drivers on your PC and to install the drivers and flash the TWRP I mentioned earlier
sorry I didn't upload earlier as I've been very busy indeed - they are now on my Google Drive ... links here .... and here

carkev said:
your first image does not 'see' your device mate, so there is no point in trying a flash of anything
until you get a response from "adb devices" that shows a device number you have no chance of getting anywhere!
I am quite certain that the problem MUST be with your drivers
my advice would be to uninstall the HTC Sync and clean out any drivers on your PC and to install the drivers and flash the TWRP I mentioned earlier
sorry I didn't upload earlier as I've been very busy indeed - they are now on my Google Drive ... links here .... and here
Click to expand...
Click to collapse
Ok, don't worry mate, i'll try that and then i'll tell you.
Thanks for taking your time helping me.
EDIT: adb still seeing nothing with that drivers

Little Snevil said:
Ok, don't worry mate, i'll try that and then i'll tell you.
Thanks for taking your time helping me.
EDIT: adb still seeing nothing with that drivers
Click to expand...
Click to collapse
Hello guys, I've been following this thread and I'm having same issue. Adb does not sees my phone.
Fastboot does, but when I run ruu , it disconnects and give error 171
Tried usb 2 instead of 3.nothing.
I also think it's the drivers, but I can't seem to find the correct one for this phone. Any help is appreciated

my phone only starts in bootloader it have s-on and i cant use the toolkit cause usb debugging isnt active
adb writes waiting for device
can anyone help me?

[Completed] Enable USB debugging on phone stuck in bootloop

Hello,
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. 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.

mellobc said:
Hello,
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. 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.
Click to expand...
Click to collapse
Greetings and welcome to assist. Can you get into download mode ? If you can does smartswitch emergency firmware recovery work
Regards
Sawdoctor

impossible to restore Nexus 5 to stock

Hello everyone, I found again my old Nexus 5, I changed few years ago because after changing the OS many time maybe I did something wrong and my phone was stuck.
loop on the ANDROID logo, I can still access fastboot mode.
Today I want to try to restore it to stock, I installed again adb, downloaded the factory img.
Though when I want to use fastboot command, I have a <waiting device> line.
Because I can use my phone, I can't go to developer mod to install drivers. so I try to do it manually by adding legacy drivers, but it didn't seemed to work because I still have the waiting device line ...
If someone can help me to resurrect my good ol' Nexus 5

No one to help me ?

Enterenn said:
No one to help me ?
Click to expand...
Click to collapse
try this https://forum.xda-developers.com/go...ol-tool-one-driversunlocktwrpfactory-t3358707
or restore nexus 5 nougat
https://mega.nz/#F!mxhBAKrL!pcsihiNof05gLrv-nY7dJQ
or restore to kitkat
https://mega.nz/#!Ow5DjQCT!vmES1dGhWSc0mxjdl7KyNCzAlHVgUterB6d6gJhh1pE
for these two tools put your phone in fastboot mode and click on recovery nexus 5 bat and see the instruction .
https://forum.xda-developers.com/go...l-06-03-14-one-click-factory-restore-t2513937

The thing is even the tool all in one ask for usb debugging, I don't know if this option on my phone is good, but I can't go on it because it can't boot (bootloop)
And when in fastboot mode, my device doesn't appear in the device list of the all in one

You may try and this ...http://www.wugfresh.com/

No, nothing is working. because my phone is not detected by anything.

You don't need developer mod to install drivers.
1- Boot into fastboot.
2- https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
Download and unzip this.
3- Go to your Windows Device Manager, find your phone and manual install the driver.