Related
Hello,
I managed to brick my new Feiteng H7100 phone, i flashed wrong rom to it and got a greenish screen when trying to start the phone.
So i formatted the phone in SPFT tool "Format whole flash" and from then it stopped responding, i cant start the phone anymore, and the charging indicator wont light up when charging.
When connecting the phone to try and reflash it the computer recognizes that i have connected the phone to the computer, but flashing doesnt work.
It is the S7180 with 1GB ram.
I hope there is a solution to it and it can be fixed, iam not sure if this can be called had brick or soft brick.
Was very close to throw it out of the window yesterday, but then thought i can give it a chance
Thanks
Have you found a solution to the problem? I have a similar problem. Dead after flash ROM
please help me
Thanks
Mine is dead also
jemmars said:
Have you found a solution to the problem? I have a similar problem. Dead after flash ROM
please help me
Thanks
Click to expand...
Click to collapse
Same mine is completely dead after I flash it - Its not recognized by the originally drivers in windows 7. Showing up as an Unknown Device.
if it is showing up as an device, it isn`t bricked. you need to get the right firmware and flash it again. force install the drivers for the unknown device or take the drivers for Rom you flashed. (e.g. flashed wrong preloader from ZTE to a Star device, need to install ZTE drivers)
While I don't know the specifics of the Feiteng H7100, I've "bricked" many an android phone and tablet. Fortunately it's usually easy to fix.
1) Reboot the device into CWM Recovery Mode (usually by holding power and volume buttons at the same time)
2) Plug it into your computer & run "adb devices" - if you device comes up as a Recovery device, then you're probably home free
3) Run an "adb push newly_downloaded_cyanogenmod_rom.zip /sdcard/" - the data location (/sdcard/ in this example) might vary depending on your device
4) Wipe Cache
5) Install Zip from sdcard and choose your new_rom.zip
Hello,
Few months ago , the power button of my nexus s had broken. I used volume rocker and I could turn on the screen.
Today I tried to flash a rom . I have done this before many times and I know the process.
After I had wiped all the data ( system , faxtory reset, cache) , I pulled off the battery.
When the phone starts it stucks on google logo , because there is no rom in it.
When I boot it into the fastboot mode , my pc cannot recognize it at all, I plug it in my pc and there is no sign that a new hardware has been installed.
I don't know what else to do. If I could get it recognized by my pc , I would be able to silve the problem.
Any suggestions on how can I fix it? Can I fix the fastboot mode problem????
Thanks for your time
I am looking forward hearing your replies...
If you don't have this installed on your PC already, you should install it and follow the directions for installing the drivers carefully. It worked for me.
P.S. this thread belongs in Q&A
Thanks for the reply but it cannot do anything. I posted here so as I can get help from developers who know more stuff than other users.
unless your thread is about ANDROID DEVELOPMENT ... IE your own ROM / KERNEL / MOD etc... it should be in q and a or general.
OP that is not how it works, posting in the Development Section because you believe the help is great there....WRONG! Sir, you will find the best help is in the proper place in the proper Threads....Please familiarize yourself with the Forum Rules on Posting. Thank You and Moved here.
When you connect your phone to your PC while it's in fastboot mode, if you haven't tried already, go to device manager (assuming your pc is running windows), there should be an unrecognized device in the list, if so you can right click on it and choose update driver, then select driver manually and navigate to the data/drivers folder where ever you have Wug's tool installed (if you don't have it installed then you should), that should properly install the drivers and allow your computer to recognize the phone, then you can use the flash stock+unroot option to repair your phone.
If you don't see any change in device manager when your phone is connected to your computer then I can't help much, maybe try a different usb port if you haven't already.
Good luck
jj_z1 said:
When you connect your phone to your PC while it's in fastboot mode, if you haven't tried already, go to device manager (assuming your pc is running windows), there should be an unrecognized device in the list, if so you can right click on it and choose update driver, then select driver manually and navigate to the data/drivers folder where ever you have Wug's tool installed (if you don't have it installed then you should), that should properly install the drivers and allow your computer to recognize the phone, then you can use the flash stock+unroot option to repair your phone.
If you don't see any change in device manager when your phone is connected to your computer then I can't help much, maybe try a different usb port if you haven't already.
Good luck
Click to expand...
Click to collapse
There are no changes when I plug in the phone, I tried all the usb ports , other pc and other new cable but nothing work.
Thanks for the reply
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
Ok so first off just wanted to say that i succesfullt rooted my Moto g 4.4.2.. Had SuperSu and all was fantastic...a day went by and i decided that i wanted to put run CMrom .. i was having a few issues so i decided that i would clear the dalvik and all that.
But this is where i messed up.. i wasnt paying attention and Deleted EVERYTHING..including the os.
Now im at a loss because my computer wont recognize my device ..even if im in fastboot or recovery.. i cant get it to show up in adb when i type adb devices or anything! So how can i flash an os when my device isnt recognized??.. There is 1 thing, When im in fastboot and i click the Superboot.bat it acts like it did when i first rooted it... but does me no good i still cant do anything... and yes ive read every guide i could find but i just cant get it recognized... Is there something im missing?
I appreciate any help with this as i am now without a phone... Thanks guys
Edit: Oh and just incase i forgot to mention i believe i have all the drivers and adb..all that...Like i said i rooted succesfully
With the phone in fastboot mode and connected to your computer, do you get the device's serial # when you type "fastboot devices" ?
audit13 said:
With the phone in fastboot mode and connected to your computer, do you get the device's serial # when you type "fastboot devices" ?
Click to expand...
Click to collapse
nope, i tried to get it to show up in every mode and way i could come up with.. nothing
Are you trying the fastboot commands on a Win7 or XP machine? I don't think ADB commands will not work when the phone is in fastboot mode,
It's a Windows 8 machine.
Any suggestions I'm still stuck
Try to flash a ROM in fastboot on a Win7 (x86 or x64) or XP (x86) machine.
Just tried it man... Still no luck. . Man what am I doing here? Do you have a link maybe I'm doing it wrong from the one I'm reading... But the machines just will not get the device
Put your phone into fastboot mode, connect the USB cable, do you see the Moto G appear as an android device in Device Manager on your Win7 or XP machine?
Delphi Hacker said:
Ok so first off just wanted to say that i succesfullt rooted my Moto g 4.4.2.. Had SuperSu and all was fantastic...a day went by and i decided that i wanted to put run CMrom .. i was having a few issues so i decided that i would clear the dalvik and all that.
But this is where i messed up.. i wasnt paying attention and Deleted EVERYTHING..including the os.
Now im at a loss because my computer wont recognize my device ..even if im in fastboot or recovery.. i cant get it to show up in adb when i type adb devices or anything! So how can i flash an os when my device isnt recognized??.. There is 1 thing, When im in fastboot and i click the Superboot.bat it acts like it did when i first rooted it... but does me no good i still cant do anything... and yes ive read every guide i could find but i just cant get it recognized... Is there something im missing?
I appreciate any help with this as i am now without a phone... Thanks guys
Edit: Oh and just incase i forgot to mention i believe i have all the drivers and adb..all that...Like i said i rooted succesfully
Click to expand...
Click to collapse
I think you need to restore your stock rom
This thread will help u
http://forum.xda-developers.com/showthread.php?t=2542219
no my device is not recognized no matt r what I do
After booting your phone in fastboot mode and connecting it to a Win7 or XP machine, you see no unknown devices in Device Manager?
Do you have pds partition since you cleared everything.
"fastboot devices" does this command shows any device or your device recognized by pc or not.
This may be useful - http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
but how can i flash the stock firmware when its not recognized?
My SPREADTUM device sc8825 chip is totally dead after trying to flash rom of same type through SPRD write mode in miraclebox 27A . firstly miracle was unable to read flash for backup . therefore i chose option to erase flash ....its done.. without writing new Rom on it. ......
And now i m with no power device., nocharging, unable to recognized usb by win7 device manager.
Already tried vol+pwer, vol-pwr and all combos.
:crying::crying::crying::crying::crying::crying:
ANY HELP WILL BE LIKE DAWN IN DARK
:crying:
mayank.rudolf said:
My SPREADTUM device sc8825 chip is totally dead after trying to flash rom of same type through SPRD write mode in miraclebox 27A . firstly miracle was unable to read flash for backup . therefore i chose option to erase flash ....its done.. without writing new Rom on it. ......
And now i m with no power device., nocharging, unable to recognized usb by win7 device manager.
Already tried vol+pwer, vol-pwr and all combos.
:crying::crying::crying::crying::crying::crying:
ANY HELP WILL BE LIKE DAWN IN DARK
:crying:
Click to expand...
Click to collapse
Does device manager even show anything at all about the device when the device is plugged in?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE