Database Info

Feiteng H7100 Bricked

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

Can i install ROM using PC only??

I am unable to boot my phone but my pc detects as a device.
Also, i cant boot into Recovery menu.
Any process which will allow me to install Android again on my phone.
Phone Model: Xolo 10000
Regards.

Does your pc detects the device in adb mode? If yes, try to flash custom kernel with recovery, or just recovery and try to boot it again, maybe that helps. Or if You can connect your phone in flashtool mode and flash the whole firmaware throu flashtool, that should resolve the problem. Good luck anyway.

in command prompt, adb says <waiting for device>
ps: I m such a newbie,,,please help me

I think you have bricked your phone . Try to install the stock ROM using the flash tool . If it didnt work then take your phone to service center and have a repair done

actually i'm in army and about 300Km away from nearest service center

I dont think its bricked, as long its response. "waiting for the device" means that you dont have correct drivers, you need adb driver, phone driver, and to be sure, serch in forum about your device what else do you need, then it should work.

i searched everywhere but no drivers for xolo a1000.
please note, i installed Jiayu 3g rom, after that everything messed totally.
And, i wiped /system before installation.

Seems like You've been searching not enough hard, http://forum.xda-developers.com/showthread.php?p=39393136#post39393136 read carefuly, coz its for xolo q800, but the drivers seems to be the same. Once You get connected device, try flashing stock firmware.

Actually i have already installed them but it still shows waiting for decive in ADB bro..

I'm affraid I can't help You any futher.

[Q] HELP!!!!OPO bricked

I got my opo a week back.I rooted it and installed twrp custom recovery.I was trying to install a new boot logo via adb which bricked my phone.I used chillstep1998 software to flash the boot logo.Now there is no display,no fastboot,no recovery and no adb.i tries searching and found this http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 ,but my opo is not recognized as QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008.I tried connecting to several pcs but nothing changed.i connect the phone to my laptop but nothing happens either in computer or in device manager.
PLEASE HELP and thanks for helping

Try holding POWER + VOLUME UP for about 30 Secs (it will vibrate). Mine was recognized after that (had the same problem)

radopi said:
Try holding POWER + VOLUME UP for about 30 Secs (it will vibrate). Mine was recognized after that (had the same problem)
Click to expand...
Click to collapse
Thanks bro. Windows detected the phone but color.zip file link is not working. Please post any mirrors or alternative link for the file. Thanks again

There is a tool which flashes CM11s instead of Color OS here.

radopi said:
There is a tool which flashes CM11s instead of Color OS here.
Click to expand...
Click to collapse
Thanks bro. Everything done. My phone is alive again as good as new. Thanks again

BRICKED 6045Y -QDLoader 9008 - any sugestion welcome

Hello,
since 5 years i am playing with google android OS and about 15 devices it looks like i have first fully bricked device.
What happened?
I made a custom marsmallow firmware from the update.zip.
The bad thing was (i think) that i deleted the aboot and also sbl1 partition from the update and also the script for flashing recovery. The second bad thing was (maybe) that i included busybox and root to the update.zip right from the begining without testing the firmware without it.
Then i made complete wipe of cache, dalvik cache, data and system (anothe rmistek i think). Flashed the firmware with no problem, no errors. Then i made wipe cache and dalvik cache again (as i used to, when going to higher OS version).
Afte rthat i hit reboot and my device is dead since then.
It cant be powered on normaly, neither recovery, neither bootloader, neither qualcomm loader.
Only thing that happens is when i connect the device to PC, the LED turns on. I have to tweak the ALCATEL USB drivers to be compatible with my WIN10PRO (yes i hate the win 10 because of the drivers,but had no other option than upgrade to win10).
Now i managed to see the device as "Android HS-USB QDLoader 9008 (yes 9008 not 9006 also bad thing).
When i try to connect to the device with panasonic eluga SUGAR_QCT_SP tool or with mobile upgrade Q or with SUGAR_QCT_SP tool i always get error when the tool downloads the MPRG. It cant download it from the device so it gives me error and thats it.
Since I dont have the proper rawprogram0.xml, patch.xml and other mbn files to pus them trough QPST i think i am in the dead end.
So if anybody has any suggestion i wil appreciate it.
If not, i will send it to warranty repair on friday and get finger crossed that they will repair it (while the service in chzech republic who is Alcatel aproved is a bunch of loosers, who do anything to do not have make it as warranty repair).

DallasCZ said:
Hello,
since 5 years i am playing with google android OS and about 15 devices it looks like i have first fully bricked device.
What happened?
I made a custom marsmallow firmware from the update.zip.
The bad thing was (i think) that i deleted the aboot and also sbl1 partition from the update and also the script for flashing recovery. The second bad thing was (maybe) that i included busybox and root to the update.zip right from the begining without testing the firmware without it.
Then i made complete wipe of cache, dalvik cache, data and system (anothe rmistek i think). Flashed the firmware with no problem, no errors. Then i made wipe cache and dalvik cache again (as i used to, when going to higher OS version).
Afte rthat i hit reboot and my device is dead since then.
It cant be powered on normaly, neither recovery, neither bootloader, neither qualcomm loader.
Only thing that happens is when i connect the device to PC, the LED turns on. I have to tweak the ALCATEL USB drivers to be compatible with my WIN10PRO (yes i hate the win 10 because of the drivers,but had no other option than upgrade to win10).
Now i managed to see the device as "Android HS-USB QDLoader 9008 (yes 9008 not 9006 also bad thing).
When i try to connect to the device with panasonic eluga SUGAR_QCT_SP tool or with mobile upgrade Q or with SUGAR_QCT_SP tool i always get error when the tool downloads the MPRG. It cant download it from the device so it gives me error and thats it.
Since I dont have the proper rawprogram0.xml, patch.xml and other mbn files to pus them trough QPST i think i am in the dead end.
So if anybody has any suggestion i wil appreciate it.
If not, i will send it to warranty repair on friday and get finger crossed that they will repair it (while the service in chzech republic who is Alcatel aproved is a bunch of loosers, who do anything to do not have make it as warranty repair).
Click to expand...
Click to collapse
Try with other Pc with WIndows 7 or 10 ..today i get my phone back 3 times with panasonic software and shows me "Android HS-USB QDLoader 9008"..sometimes fails with download mprg but try again ...first press + and - and then connect usb and try with panasonic in my situation power and volume buttons are don't work so i must open the phone

Alek Dev said:
Try with other Pc with WIndows 7 or 10 ..today i get my phone back 3 times with panasonic software and shows me "Android HS-USB QDLoader 9008"..sometimes fails with download mprg but try again ...first press + and - and then connect usb and try with panasonic in my situation power and volume buttons are don't work so i must open the phone
Click to expand...
Click to collapse
have tried with 3 PCs with win7 and with 3 usb cables. Still error when downloading MPRG.
I cannot understand where it went wrong. The aboot and sbl1 parition shouldnt affect the device to boot to recovery or to bootloader, because when the sbl1 chechk for aboot it should be fine whle they are the same version.

DallasCZ said:
have tried with 3 PCs with win7 and with 3 usb cables. Still error when downloading MPRG.
I cannot understand where it went wrong. The aboot and sbl1 parition shouldnt affect the device to boot to recovery or to bootloader, because when the sbl1 chechk for aboot it should be fine whle they are the same version.
Click to expand...
Click to collapse
i hardbricked many times and panasonic helped in every time...one time i made test zip of Miui and i hardbricked only led worked,screen not worked but panasonic helped me........i can't understand what's the problem with downloading MPRG

Alek Dev said:
i hardbricked many times and panasonic helped in every time...one time i made test zip of Miui and i hardbricked only led worked,screen not worked but panasonic helped me........i can't understand what's the problem with downloading MPRG
Click to expand...
Click to collapse
thats the probelm. I also dont know why is there a probelm to download the MPRG to comunicate with the device.
The removable battery was a good thing, because you can power off the device. Now i can just guess if the device is powered off or not when i connect to the PC.
And of course this f**ing windows 10.

maybe when the 6.0.1 will be released i can connect with propper mbn. but i cant wait. I will send it to repair on friday or buy another device (zenfone 3 or moto g4plus).
Now i am still trying to bring it to life.

DallasCZ said:
thats the probelm. I also dont know why is there a probelm to download the MPRG to comunicate with the device.
The removable battery was a good thing, because you can power off the device. Now i can just guess if the device is powered off or not when i connect to the PC.
And of course this f**ing windows 10.
Click to expand...
Click to collapse
Try to disconnect the Battery and reconnect and then try with Pc AND Panasonic

here is the screen.

Alek Dev said:
Try to disconnect the Battery and reconnect and then try with Pc AND Panasonic
Click to expand...
Click to collapse
but it means to open the device, and i am a little bit affraid not to loose the warranty by opening it and reconnect the battery.

DallasCZ said:
but it means to open the device, and i am a little bit affraid not to loose the warranty by opening it and reconnect the battery.
Click to expand...
Click to collapse
Try to go to TAB Infromation and Get information from Device and then press Reboot Device....I think if you dissconect battery and reconnect it will work....also
whether to open or not Тhe service will want money for repair

Alek Dev said:
Try to go to TAB Infromation and Get information from Device and then press Reboot Device....I think if you dissconect battery and reconnect it will work....also
whether to open or not Тhe service will want money for repair
Click to expand...
Click to collapse
if they cant boot the device they will probably replace the mainboard so they will not get known if the device was unlocked or rooted.
If i will open it and replace the battery i will break the stamps on the battery so they will know i was inside the device and they will refuse to make it as warranty repair.
SO if there is no software option i will send it to warranty repair. If they will refuse to repair it as warranty repair. then i will consider to open it and do whatever it takes to get it to life

DallasCZ said:
if they cant boot the device they will probably replace the mainboard so they will not get known if the device was unlocked or rooted.
If i will open it and replace the battery i will break the stamps on the battery so they will know i was inside the device and they will refuse to make it as warranty repair.
SO if there is no software option i will send it to warranty repair. If they will refuse to repair it as warranty repair. then i will consider to open it and do whatever it takes to get it to life
Click to expand...
Click to collapse
Did you have TeamViewer..i think that i can help you to get your device to life ( if you have Teamviewer send me ID AND pass to PM)

@Alek Dev: i congratulate you ! respect .... Sometime, you're like a morpion. But in this case , i salute your dedication
I hope you manage to save DallaCZ :angel:

murigny64 said:
@Alek Dev: i congratulate you ! respect .... Sometime, you're like a morpion. But in this case , i salute your dedication
I hope you manage to save DallaCZ :angel:
Click to expand...
Click to collapse
We are tried but Nothing same error . .i will google it ..)

murigny64 said:
@Alek Dev: i congratulate you ! respect .... Sometime, you're like a morpion. But in this case , i salute your dedication
I hope you manage to save DallaCZ :angel:
Click to expand...
Click to collapse
As i said to him...sometimes he is a pain in the ass, but he meneged to sped his time to try to solve my problem...rispect!

DallasCZ said:
As i said to him...sometimes he is a pain in the ass, but he meneged to sped his time to try to solve my problem...rispect!
Click to expand...
Click to collapse
i think the problem is drivers...because my device in device manager is showed like "Qualcomm HS-USB QDLoader 9008 " yours is showed like "Android HS-USB QDLoader 9008"-i think that you can again try this + and - and connect usb or + and - and pwr button and then usb

DallasCZ said:
As i said to him...sometimes he is a pain in the ass, but he meneged to sped his time to try to solve my problem...rispect!
Click to expand...
Click to collapse
Sent from my SM-N920V using XDA Free mobile app
---------- Post added at 02:30 AM ---------- Previous post was at 02:26 AM ----------
frankie paul said:
Sent from my SM-N920V using XDA Free mobile app
Click to expand...
Click to collapse
Alek Dev said:
i think the problem is drivers...because my device in device manager is showed like "Qualcomm HS-USB QDLoader 9008 " yours is showed like "Android HS-USB QDLoader 9008"-i think that you can again try this + and - and connect usb or + and - and pwr button and then usb
Click to expand...
Click to collapse
Sent from my SM-N920V using XDA Free mobile app
---------- Post added at 02:35 AM ---------- Previous post was at 02:30 AM ----------
DallasCZ said:
if they cant boot the device they will probably replace the mainboard so they will not get known if the device was unlocked or rooted.
If i will open it and replace the battery i will break the stamps on the battery so they will know i was inside the device and they will refuse to make it as warranty repair.
SO if there is no software option i will send it to warranty repair. If they will refuse to repair it as warranty repair. then i will consider to open it and do whatever it takes to get it to life
Click to expand...
Click to collapse
Sent a my SM-N920V using XDA Free mobile app

Alek Dev said:
i think the problem is drivers...because my device in device manager is showed like "Qualcomm HS-USB QDLoader 9008 " yours is showed like "Android HS-USB QDLoader 9008"-i think that you can again try this + and - and connect usb or + and - and pwr button and then usb
Click to expand...
Click to collapse
I tried with "Android HS-USB QDLoader 9008" and also with "Qualcomm HS-USB QDLoader 9008" and even with "Alcatel HS-USB QDLoader 9008" always error when reading MPRG from the device.

http://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040
This should help you I think

yash_rathore25 said:
http://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040
This should help you I think
Click to expand...
Click to collapse
maybe,but you have to rewrite all the .xml files with data for your device, which we dont have.

Xperia L black screen

Hey! When i install CM 12 / CM13 and Ressurection im getting blackscreen [phone didnt work, only power button, cmw too didnt work.] Please help me, i need new system because my is old.

xawierstudio said:
Hey! When i install CM 12 / CM13 and Ressurection im getting blackscreen [phone didnt work, only power button, cmw too didnt work.] Please help me, i need new system because my is old.
Click to expand...
Click to collapse
You can try to flash back the stock firmware (MUST be the 4.2.2 version) via flashtool, root and install TWRP recovery with this app (http://forum.xda-developers.com/xperia-l/development/app-recoveries-recovery-installer-t3187915).
I dont have any other ideas, make sure you do all that ROM flash stuff properly.

I faced the same issue just now... any update? @xawierstudio

satyapol07 said:
I faced the same issue just now... any update? @xawierstudio
Click to expand...
Click to collapse
It's maybe because of an improperly unlocked bootloader. just reflash latest stock rom (Latest one Here) and check the state of bootloader (it should be " Bootloader unlock Done"). else, if you have Xperia L, use This Link to unlock the bootloader and install TWRP recovery, then install your desired Custom ROM
Well, I think we are the last Survivors of this tough Taoshan at 2019!

Hey Thanks alot for the reference.. But I'm not sure how can I start my phone in bootloader or recovery mode as I cant see any display

satyapol07 said:
Hey Thanks alot for the reference.. But I'm not sure how can I start my phone in bootloader or recovery mode as I cant see any display
Click to expand...
Click to collapse
First, make sure your battery has enough charge to start. if not, then try charging it and then continue your testing. if it doesn't charge, then you should use external battery charger to directly charge your battery (or you may need to change your battery!?). after passing this step, use flashtool version 0.9.18.6 to flash stock rom.
For going into Flash mode, while your phone is off, press and hold volume down and connect it with cable to PC. now LED light should turn into green, and it should be in flash mode ! (nothing displays in screen)

Just got this phone from my friend - he erased too much in twrp recovery (whole partitions) and now can't turn it on. No bootloader mode, no flash mode. Only one com port is visible in device manager: Qualcomm HS-USB QDLoader 9008. Anybody with knowledge what to do on this model?

Franek_Dolas said:
Just got this phone from my friend - he erased too much in twrp recovery (whole partitions) and now can't turn it on. No bootloader mode, no flash mode. Only one com port is visible in device manager: Qualcomm HS-USB QDLoader 9008. Anybody with knowledge what to do on this model?
Click to expand...
Click to collapse
I think these are the signs of hard bricking (or the memory has ended his life). more info and discussions can be found HERE. till now, NO absolute working method has been found for Xperia L. sorry, but I don't have much info about this issue (Although I have this phone too)