like title ... half day to configure all and then after a recharge the display is black .. not black like phone off but with a little retro light of display ... the phone is always on and after 10 seconds of start button it restart but always the display is gray/black and is not possible to tap anything ... some suggestion please ... thanks a lot ...
Affichage des articles dont le libellé est dead. Afficher tous les articles
Affichage des articles dont le libellé est dead. Afficher tous les articles
mardi 25 août 2015
htc one m8 dead after "fastboot oem reset" command
I used "fastboot oem reset" command. then my device restarted. but screen became totally black. bootloader screen is not loading. no htc logo.but computer detects the device.after this command in device tree product name has disapeared. also serialno, imei, modelid has corrupted. is there a method to rewrite product name, serialno, imei, modelid?
D:\htc one m8\fastboot m8>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: UUUUUUUUUUUUUUU
(bootloader) version-misc: UNKNOWN
(bootloader) serialno: UUUUUUUUUUUUUUU
(bootloader) imei: 355195000000010
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product:
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU
(bootloader) cidnum: UUUUUUUU
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: UNKNOWN
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.094s
I am really really thankfull if you can help me here.
D:\htc one m8\fastboot m8>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: UUUUUUUUUUUUUUU
(bootloader) version-misc: UNKNOWN
(bootloader) serialno: UUUUUUUUUUUUUUU
(bootloader) imei: 355195000000010
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product:
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU
(bootloader) cidnum: UUUUUUUU
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: UNKNOWN
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.094s
I am really really thankfull if you can help me here.
how to backup with dead touchscreen
rooted my phone few months ago, using this method.
apparently the phone is not so waterproof as advertised. just a few drops of water in the swimming pool (didn't even put it under water) and wet hands made the touchscreen unresponsive an hour after. I am going to return it to Sony as it is only 4 months old.
but I really like to backup all my stuff before I return it.
the phone works fully, even the display works, but the touchscreen doesn't respond to any swiping. is there still a way to do so? I can put the phone into recovery via ADB, but TWRP is/seems useless when touchscreen isn't working. is there another way, eg. via ADB commands or any other way, to do a full (nandroid) backup?
many thanks!
regards Eddict
apparently the phone is not so waterproof as advertised. just a few drops of water in the swimming pool (didn't even put it under water) and wet hands made the touchscreen unresponsive an hour after. I am going to return it to Sony as it is only 4 months old.
but I really like to backup all my stuff before I return it.
the phone works fully, even the display works, but the touchscreen doesn't respond to any swiping. is there still a way to do so? I can put the phone into recovery via ADB, but TWRP is/seems useless when touchscreen isn't working. is there another way, eg. via ADB commands or any other way, to do a full (nandroid) backup?
many thanks!
regards Eddict
lundi 24 août 2015
my ir dead can any one help
I'm using note 4 n910c and my infraad stop working can any one help me that happened after update to 5.0.1 plz help
samedi 22 août 2015
Dead Gear S: suggestions?
My Gear S died on me today.
Went running for first time with Gear S. Turned on GPS and tracking worked fine. About 50% battery at start of run.
About 1 hour later hit button on watch and no response. Thought it was strange, but thought battery died. Put on charger for several hours, but charge indicator didn't light up.
Held button for 30 seconds and 1 minute to see if it would reset. No response at all. Attached to several other cables and charge plugs plus PC USB port. Nothing worked.
Got this through eBay Buy.com deal two months ago. Not sure about warranty.
Any suggestions appreciated. Hate to see 0 go down the drain. Plus I like this watch!
jb
Went running for first time with Gear S. Turned on GPS and tracking worked fine. About 50% battery at start of run.
About 1 hour later hit button on watch and no response. Thought it was strange, but thought battery died. Put on charger for several hours, but charge indicator didn't light up.
Held button for 30 seconds and 1 minute to see if it would reset. No response at all. Attached to several other cables and charge plugs plus PC USB port. Nothing worked.
Got this through eBay Buy.com deal two months ago. Not sure about warranty.
Any suggestions appreciated. Hate to see 0 go down the drain. Plus I like this watch!
jb
Dead Turbo?
So I was running CF 1.3 base for quite a while with no issues. Two days ago my phone shut down on me and would not boot. I wipe everything multiple times. I wiped cache. I did a factory reset, nothing... I wiped again. Nothing.
It gets past the Motorola logo and then just sits at the boot screen. A couple of times it would say updating android, it would finish, but then it would go right back to the boot screen. After about 8 hours it finally booted and I used it all day yesterday. This morning my issue is back. I've flashed different images to see if it has something to do with 1.3. It's all the same. I think I might try to go back to kit kat. It seems to be a software problem, but I am starting to think that something most be wrong with my hardware.
I found this thread: https://forums.motorola.com/posts/b0021413e7
I think my phone is shot... Any ideas?
It gets past the Motorola logo and then just sits at the boot screen. A couple of times it would say updating android, it would finish, but then it would go right back to the boot screen. After about 8 hours it finally booted and I used it all day yesterday. This morning my issue is back. I've flashed different images to see if it has something to do with 1.3. It's all the same. I think I might try to go back to kit kat. It seems to be a software problem, but I am starting to think that something most be wrong with my hardware.
I found this thread: https://forums.motorola.com/posts/b0021413e7
I think my phone is shot... Any ideas?
No network signal - how to know is gsm Radio dead in hardware or it is software issue
I have OnePlus One with OxygenOS now, but gsm wasn't working under CM12 either, so I clean installed Oxygen and it didn't resolve issue.
In log I have :
D/RILJ ( 1523): [3904]> QUERY_AVAILABLE_NETWORKS [SUB0]
D/RILC ( 250): SOCKET RIL_SOCKET_1 REQUEST: QUERY_AVAILABLE_NETWORKS length
:8
D/RILC ( 250): RequestComplete, RIL_SOCKET_1
E/RILC ( 250): Send Response to RIL_SOCKET_1
D/RilRequest( 1523): [3904]< QUERY_AVAILABLE_NETWORKS error: com.android.intern
al.telephony.CommandException: GENERIC_FAILURE ret=
*********************
D/NetworkSetting( 1523): EVENT_NETWORK_DATA_MANAGER_DONE: 1
V/QC_RIL_OEM_HOOK( 1523): sendRilOemHookMsg: Outgoing Data is 514f454d484f4f4b1200080000000000
D/QcrilMsgTunnelIfaceManager( 2776): handleMessage what = 1
D/QcrilMsgTunnelSocket( 2776): [1000] > OEM_HOOK_RAW[514f454d484f4f4b1200080000000000]
D/PowerManagerService( 833): acquireWakeLockInternal: lock=562127469, flags=0x1, tag="QcrilMsgTunnelSocket", ws=null, uid=1001, pid=2776
D/QcrilMsgTunnelSocket( 2776): readRilMessage: Buffer = [B@a57e87c HexData = [00000000e803000002000000ffffffff]
D/QcrilMsgTunnelSocket( 2776): Rcvd SOLICITED response with 12 bytes data for SUB0
D/QcRilRequest( 2776): [1000] < OEM_HOOK_RAW error: com.android.internal.telephony.CommandException: GENERIC_FAILURE
I also have this when trying to click "TURN RADIO ON" in service menu (*#*#4636#*#*) :
D/GsmSST ( 1523): [GsmSST] mDeviceShuttingDown = false
D/GsmSST ( 1523): [GsmSST] mDesiredPowerState = true
D/GsmSST ( 1523): [GsmSST] getRadioState = RADIO_OFF
D/GsmSST ( 1523): [GsmSST] mPowerOffDelayNeed = true
D/GsmSST ( 1523): [GsmSST] mAlarmSwitch = false
D/RILJ ( 1523): [4127]> RADIO_POWER on [SUB0]
D/RILC ( 250): SOCKET RIL_SOCKET_1 REQUEST: RADIO_POWER length:16
D/RILC ( 250): RequestComplete, RIL_SOCKET_1
E/RILC ( 250): Send Response to RIL_SOCKET_1
D/RilRequest( 1523): [4127]< RADIO_POWER error: com.android.internal.telephony.C
ommandException: GENERIC_FAILURE ret=
In log I have :
D/RILJ ( 1523): [3904]> QUERY_AVAILABLE_NETWORKS [SUB0]
D/RILC ( 250): SOCKET RIL_SOCKET_1 REQUEST: QUERY_AVAILABLE_NETWORKS length
:8
D/RILC ( 250): RequestComplete, RIL_SOCKET_1
E/RILC ( 250): Send Response to RIL_SOCKET_1
D/RilRequest( 1523): [3904]< QUERY_AVAILABLE_NETWORKS error: com.android.intern
al.telephony.CommandException: GENERIC_FAILURE ret=
*********************
D/NetworkSetting( 1523): EVENT_NETWORK_DATA_MANAGER_DONE: 1
V/QC_RIL_OEM_HOOK( 1523): sendRilOemHookMsg: Outgoing Data is 514f454d484f4f4b1200080000000000
D/QcrilMsgTunnelIfaceManager( 2776): handleMessage what = 1
D/QcrilMsgTunnelSocket( 2776): [1000] > OEM_HOOK_RAW[514f454d484f4f4b1200080000000000]
D/PowerManagerService( 833): acquireWakeLockInternal: lock=562127469, flags=0x1, tag="QcrilMsgTunnelSocket", ws=null, uid=1001, pid=2776
D/QcrilMsgTunnelSocket( 2776): readRilMessage: Buffer = [B@a57e87c HexData = [00000000e803000002000000ffffffff]
D/QcrilMsgTunnelSocket( 2776): Rcvd SOLICITED response with 12 bytes data for SUB0
D/QcRilRequest( 2776): [1000] < OEM_HOOK_RAW error: com.android.internal.telephony.CommandException: GENERIC_FAILURE
I also have this when trying to click "TURN RADIO ON" in service menu (*#*#4636#*#*) :
D/GsmSST ( 1523): [GsmSST] mDeviceShuttingDown = false
D/GsmSST ( 1523): [GsmSST] mDesiredPowerState = true
D/GsmSST ( 1523): [GsmSST] getRadioState = RADIO_OFF
D/GsmSST ( 1523): [GsmSST] mPowerOffDelayNeed = true
D/GsmSST ( 1523): [GsmSST] mAlarmSwitch = false
D/RILJ ( 1523): [4127]> RADIO_POWER on [SUB0]
D/RILC ( 250): SOCKET RIL_SOCKET_1 REQUEST: RADIO_POWER length:16
D/RILC ( 250): RequestComplete, RIL_SOCKET_1
E/RILC ( 250): Send Response to RIL_SOCKET_1
D/RilRequest( 1523): [4127]< RADIO_POWER error: com.android.internal.telephony.C
ommandException: GENERIC_FAILURE ret=
vendredi 21 août 2015
Nexus 5 rebooting loop with dead Recovery mode ! any help ?
Welcome Dears
Before 1 week ago, my nexus 5 went into rebooting loop, it was a hardware issue, and after I replace the power button
still the phone rebooting on Google logo every second, when I connect it to the charger, its charging without problem until get a full charged battery, so I think it is not a battery issue, and I can enter the fastboot mode without rebooting, so I think its not a hardware issue now, it was and its goes out !
the problem also when I enter the recovery mode , "No Command" with android logo appears, then I press the Volume Up button then I get the recovery mode command, but unfortunately my PC can't see the phone, so I can't use the "adb sideload" command to flash my MIUI ROM (Version: 5.8.6) again
but in the fastboot my PC can connect with Nexus, so I try to flash the CWM/TWRP recovery , I got these replay from the command,
but unfortunately when I repeat my nexus to recovery mode I didn't get the new flashed recovery ! still stuck on the dead old one !
when I use from recovery mode the "wipe data/factory reset" I got these three line then flashing on "no command" dead recovery logo
then go into "no command" dead recovery logo flashing until I force it shutdown by power button !
same result by "wipe cache partition" command
my Next step to flash the factory image by fastbood command but this solution will remove all files & pictures & Videos & my notes isn't it ?! :(
so if that is right ? do you have any other solution to run up my nexus and avoiding these rebooting loop or flash new recovery / custom ROM without loosing my data ?! " I am not afraid of loos any Apps and data of them" I need my sound files, videos, pictures and notes.
Pictures below for more clarify the issue !
I get "No Command" when I enter the Recovery mode
http://store2.up-00.com/2015-08/1440196110631.jpg
The pictures of Dead Recovery Mode commands
http://store2.up-00.com/2015-08/1440196110722.jpg
Thank you.
Before 1 week ago, my nexus 5 went into rebooting loop, it was a hardware issue, and after I replace the power button
still the phone rebooting on Google logo every second, when I connect it to the charger, its charging without problem until get a full charged battery, so I think it is not a battery issue, and I can enter the fastboot mode without rebooting, so I think its not a hardware issue now, it was and its goes out !
the problem also when I enter the recovery mode , "No Command" with android logo appears, then I press the Volume Up button then I get the recovery mode command, but unfortunately my PC can't see the phone, so I can't use the "adb sideload" command to flash my MIUI ROM (Version: 5.8.6) again
Code:
adb sideload MIUI.zip
error: device not found
Code:
C:\adb>fastboot flash recovery hammerhead-cwm-6.0.4.4-unofficial.img
< waiting for device >
sending 'recovery' (10498 KB)...
OKAY [ 0.453s]
writing 'recovery'...
OKAY [ 0.847s]
finished. total time: 1.302s
C:\adb>
when I use from recovery mode the "wipe data/factory reset" I got these three line then flashing on "no command" dead recovery logo
Code:
--wiping data. . .
Formatting/data. . .
Formatting/cache . . .
same result by "wipe cache partition" command
my Next step to flash the factory image by fastbood command but this solution will remove all files & pictures & Videos & my notes isn't it ?! :(
so if that is right ? do you have any other solution to run up my nexus and avoiding these rebooting loop or flash new recovery / custom ROM without loosing my data ?! " I am not afraid of loos any Apps and data of them" I need my sound files, videos, pictures and notes.
Pictures below for more clarify the issue !
I get "No Command" when I enter the Recovery mode
http://store2.up-00.com/2015-08/1440196110631.jpg
The pictures of Dead Recovery Mode commands
http://store2.up-00.com/2015-08/1440196110722.jpg
Thank you.
P6 dead after change sd card with phone on
Hi there:
The phone is totally black screen. I let the battery go empty and connect to the supply: now connect to the pc and something happen. for a few seconds try to install, but don't complete. and start again.
before go down a message similar to "ascend.core don't work anymore" appears.
The phone works well before the issue, i think is something with the software.
Thanks in advance.
The phone is totally black screen. I let the battery go empty and connect to the supply: now connect to the pc and something happen. for a few seconds try to install, but don't complete. and start again.
before go down a message similar to "ascend.core don't work anymore" appears.
The phone works well before the issue, i think is something with the software.
Thanks in advance.
How to Unbrick Totally Dead Alcatel 918
I mean totally dead as in, only the charging light is showing, no android logo, no recovery mode
Files you need
1.ALCATEL OT 918 )ROM BACKUP FROM A WORKING PHONE( MOST IMPORTANT)
https://docs.google.com/uc?id=0B_XoE...xport=download
2.MTK USB DRIVER FOR YOUR PHONE
3.SP_Flash Tool v3.1224.00
https://disk.yandex.com/public/?hash=%2BFgTiMPQgqQjcFeH30tIoZnLBEVANGQz3%2BeBBWub 5m0%3D
PROCEDURE
2. Install usb drivers and make sure your it works well (by using another identical phone)
3. Run Sp falsh tool and select the alcatel scatter file.
4. Copy all the downloaded files in one folder for easy access.
5.Select and check every item from the ROM BACKUP starting from the preloader,ds pl.....etc.
6. Connect your phone to the computer using the usb cable .PRESS VOLUME + continuously then click download in the sp fash tool.
NOW YOU WILL BE ABLE TO FLASH YOUR ALCATEL.
NB.
After flashing your dead alcatel will boot up .
IF IT HANGS IN THE BOOTLOOP.
1.Flash the CWM BY MARK by running sp flashtool and check recovery only (this allows you to flash clock work mode that will allow you to flash a working OS to your phone.)
2.After a complete flash. Copy ORIGINAL ROM.RAR to sd and Start your phone in recovery (power + volume up)
3.Go to install rom from sd and select ORIGINAL ROM or flash new working rom.
Thank me later
Files you need
1.ALCATEL OT 918 )ROM BACKUP FROM A WORKING PHONE( MOST IMPORTANT)
https://docs.google.com/uc?id=0B_XoE...xport=download
2.MTK USB DRIVER FOR YOUR PHONE
3.SP_Flash Tool v3.1224.00
https://disk.yandex.com/public/?hash=%2BFgTiMPQgqQjcFeH30tIoZnLBEVANGQz3%2BeBBWub 5m0%3D
PROCEDURE
2. Install usb drivers and make sure your it works well (by using another identical phone)
3. Run Sp falsh tool and select the alcatel scatter file.
4. Copy all the downloaded files in one folder for easy access.
5.Select and check every item from the ROM BACKUP starting from the preloader,ds pl.....etc.
6. Connect your phone to the computer using the usb cable .PRESS VOLUME + continuously then click download in the sp fash tool.
NOW YOU WILL BE ABLE TO FLASH YOUR ALCATEL.
NB.
After flashing your dead alcatel will boot up .
IF IT HANGS IN THE BOOTLOOP.
1.Flash the CWM BY MARK by running sp flashtool and check recovery only (this allows you to flash clock work mode that will allow you to flash a working OS to your phone.)
2.After a complete flash. Copy ORIGINAL ROM.RAR to sd and Start your phone in recovery (power + volume up)
3.Go to install rom from sd and select ORIGINAL ROM or flash new working rom.
Thank me later
LCD dead after replacement
Hello.
I have bought a faulty Xperia Z off the market,the screen was broken so it didn't work,but everything else did,as I could connect it
to the PC and take screenshots via hardware buttons,so I ordered a new screen for the phone.
I replaced the screen,but I tore the battery a little bit,on the outer metal "paper",now the phone turns on,
you can hear everything,but the screen is dead,although it's new.
I tried to hard reset it,update the software,repair it,but no help.
Also,could it be the battery,so I can order a new one?
How is the LCD powered on Xperia Z?
I have bought a faulty Xperia Z off the market,the screen was broken so it didn't work,but everything else did,as I could connect it
to the PC and take screenshots via hardware buttons,so I ordered a new screen for the phone.
I replaced the screen,but I tore the battery a little bit,on the outer metal "paper",now the phone turns on,
you can hear everything,but the screen is dead,although it's new.
I tried to hard reset it,update the software,repair it,but no help.
Also,could it be the battery,so I can order a new one?
How is the LCD powered on Xperia Z?
mercredi 19 août 2015
Bootloop, dead stock recovery.
OK, So I went to flash the latest M preview today coming from the latest CM nightly. Tried flash-all but, as always, got the system.img error. So I flashed everything again manually. Checked recovery and it only went to the dead android with the red triangle. Tried booting like normal, but its stuck on the new boot animation for 30mins or so.
After that I figured I would wipe and try to flash back to stock latest Google image. After flashing all parts manually for LMY48I, I'm still getting the dead android at recovery and stuck at boot animation, still the NEW animation, not the previous one from LMY48I.
Is there anything I'm missing here? I'll keep plugging away at it.
Thanks!
After that I figured I would wipe and try to flash back to stock latest Google image. After flashing all parts manually for LMY48I, I'm still getting the dead android at recovery and stuck at boot animation, still the NEW animation, not the previous one from LMY48I.
Is there anything I'm missing here? I'll keep plugging away at it.
Thanks!
mardi 18 août 2015
Phone dead and bootlooping. How to recover data?
My moto X 2013 met an unfortunate demise by being dropped onto concrete. The phone will not boot, and cycles through the power on vibrate, wait about 10 seconds, and then power on vibrate again ad infinitum. I accept its fate, but there are quite a few photos/videos that I would really want to get recovered if possible. Is there any way to do so?
Power button dead. Any way i can still unlock bootloader and root nexus 5
My power button is completely dead. I can neither switch off or switch on phone nor can i out it to sleep widout third party app.
I need to unlock bootloader and root phone but all methods need a working power button.. Any way i can do this widout power button jus by using pc and command window ?
Please help.. Em a noob..
I need to unlock bootloader and root phone but all methods need a working power button.. Any way i can do this widout power button jus by using pc and command window ?
Please help.. Em a noob..
lundi 17 août 2015
Is my Note 2 N7100 dead?
After flashing PIT with using ODIN, my samsung Note 2 cant even enter download mode. The phone show nothing at all when press power button + home + volume down.
This is the pit file I download from here
http://forum.xda-developers.com/show...1927983&page=3
Is my phone totally dead? Cannot be revived anymore?
This is the pit file I download from here
http://forum.xda-developers.com/show...1927983&page=3
Is my phone totally dead? Cannot be revived anymore?
dimanche 16 août 2015
Dead Android
I bought a Xoom WiFi shortly after they were available to the US market.
It has always been totally reliable and trouble free.
It is (was??) currently completely stock and running 4.1.2.
With the exception of one application (Olive Tree Bible Reader 6.0) it runs everything I want to with no problems.
I have a Nexus 5 and bought a Nexus 9 open box at Best Buy as I wanted something more powerful than the Xoom. However, after a week I returned the Nexus 9 as I didnt care for the smaller screen size.
I considered rooting thee Xoom and trying to overclock it to get some more power.
I tried the instructions found on the Xoom forum called "how-rookie-rooting-flashing-unrooting-under-one-roof" using the section: Rooting Jellybean 4.1.1 and 4.1.2 OTA
It seemed to be going along fine until I got to the part:
Once you have verification on your device that this has been flashed:
- Reboot your device by holding Volume Up + Power.
- Then 3 seconds after you see the "Motorola logo", hit Volume Down.
You should now see "Android Recovery" at the top left corner.
- Hit Volume Up to boot/enter into recovery.
When I try to go into the Android Recovery mode it starts and says
Entering Android Recovery Mode
Reading ODM Fuse 1
Then I get this dead android laying on his back with his belly open and a red triangle with an exclamation mark on it coming out.
All I wanted to do was a simple root so that I could do an overclock as described at unlocker.com - "how-to-overclock-the-motorola-xoom"
And help in getting me unstuck would be greatly appreciated.
Thanks
HK
It has always been totally reliable and trouble free.
It is (was??) currently completely stock and running 4.1.2.
With the exception of one application (Olive Tree Bible Reader 6.0) it runs everything I want to with no problems.
I have a Nexus 5 and bought a Nexus 9 open box at Best Buy as I wanted something more powerful than the Xoom. However, after a week I returned the Nexus 9 as I didnt care for the smaller screen size.
I considered rooting thee Xoom and trying to overclock it to get some more power.
I tried the instructions found on the Xoom forum called "how-rookie-rooting-flashing-unrooting-under-one-roof" using the section: Rooting Jellybean 4.1.1 and 4.1.2 OTA
It seemed to be going along fine until I got to the part:
Once you have verification on your device that this has been flashed:
- Reboot your device by holding Volume Up + Power.
- Then 3 seconds after you see the "Motorola logo", hit Volume Down.
You should now see "Android Recovery" at the top left corner.
- Hit Volume Up to boot/enter into recovery.
When I try to go into the Android Recovery mode it starts and says
Entering Android Recovery Mode
Reading ODM Fuse 1
Then I get this dead android laying on his back with his belly open and a red triangle with an exclamation mark on it coming out.
All I wanted to do was a simple root so that I could do an overclock as described at unlocker.com - "how-to-overclock-the-motorola-xoom"
And help in getting me unstuck would be greatly appreciated.
Thanks
HK
samedi 15 août 2015
Touchscreen is dead
So lately i got a problem..i was borwsing chrome and boom...touchscreen stopped working...i thought reboot would solve the problem but nope :/ it works for 2-3 minutes after boot but then it stops... Any ideas? I am ready to go into hardware just i dont know what to do there :/
Thanks in advance :)
Sent from my A0001 using XDA Free mobile app
Thanks in advance :)
Sent from my A0001 using XDA Free mobile app
Android is dead... back to Windows
I was tempted to get the Note 5 maybe only for Gear VR...
My Note 4 is beyond its limits...
I don't see any other important reason not to switch to the Lumia 950XL
Am already using Onenote with my colleagues.
So much better... well it's Office...
Same with my Note 10.1 2014... Surface (pro) 4 it will be.
Android apps are already and maybe iOS ones will be running on Windows which is the other major seller for Windows 10
Android was once very open... now it's becoming more restrictive to satisfy even the dumbest user... for those there is already i'doit'OS.
Impossible / hard to root... SD practically unusable...
Huge Software problems with 5.0 and 5.1 across all Manufacturers.
The Base is too old... not designed for 8 core 4GB Ram devices
Windows 10 is a completely new OS
Android is dying... fragmenting within itself now - in the near future more manufacturers will make their own Android... am telling you... it's the rise of Windows
Back to the smartphone roots
My Note 4 is beyond its limits...
I don't see any other important reason not to switch to the Lumia 950XL
Am already using Onenote with my colleagues.
So much better... well it's Office...
Same with my Note 10.1 2014... Surface (pro) 4 it will be.
Android apps are already and maybe iOS ones will be running on Windows which is the other major seller for Windows 10
Android was once very open... now it's becoming more restrictive to satisfy even the dumbest user... for those there is already i'doit'OS.
Impossible / hard to root... SD practically unusable...
Huge Software problems with 5.0 and 5.1 across all Manufacturers.
The Base is too old... not designed for 8 core 4GB Ram devices
Windows 10 is a completely new OS
Android is dying... fragmenting within itself now - in the near future more manufacturers will make their own Android... am telling you... it's the rise of Windows
Back to the smartphone roots
vendredi 14 août 2015
S3 Mini VE Hard bricked (DEAD)
So i have a S3 mini VE, and i was flashing a stock firmware on my phone suddenly the USB cable disconnected during the process (ODIN) now when i try to turn on the phone, it doesn't come on at all. the only way to get the phone on is to charge it (AC). but it goes into loop every 5 seconds. So when i take the battery outta the phone and then plug the charger in. It shows this message (See below) but won't go into loop. It's seriously weird. The button combo are fully dead.
So basically i can't get into the phone i tried every method, even tried USB JIG from eBay. i seriously don't know what's going on with the phone, i need help fixing this issue.
has this happened to anyone else?
Button combo (DEAD)
Flashing with ODIN (DEAD)
Download Mode (DEAD)
Recovery Mode (DEAD)
Connecting to PC (DEAD)
So i've done all this, so please don't tell me to do these again i've done em :P
Thanks!
So basically i can't get into the phone i tried every method, even tried USB JIG from eBay. i seriously don't know what's going on with the phone, i need help fixing this issue.
has this happened to anyone else?
Button combo (DEAD)
Flashing with ODIN (DEAD)
Download Mode (DEAD)
Recovery Mode (DEAD)
Connecting to PC (DEAD)
So i've done all this, so please don't tell me to do these again i've done em :P
Thanks!
coolpad dazen 1 dead... plz help..
hello..
i was trying to root and install cwm.. and i unfortunately installe the wrong recovery now my phone does not start.. not even recovery mode..
it shows a messege "Download and install package...........etc. press volume up to proceed down to cancel" pressing the keys don't do any thing phone gets off after a while.. i have a backup of stock recovery and boot but i think both files are same its 20mb both.. i had used Flashify to backup. and i can't even enter fastboot my pc does not detect my phone perhaps because i don't have the drivers... is it possible to fix my phone or its dead for ever..:crying::crying::crying::crying::crying::cry ing::silly::silly::crying:
i was following this method here.. www[dot]gizdev[dot]com/easy-way-to-root-coolpad-dazen-1/
i was trying to root and install cwm.. and i unfortunately installe the wrong recovery now my phone does not start.. not even recovery mode..
it shows a messege "Download and install package...........etc. press volume up to proceed down to cancel" pressing the keys don't do any thing phone gets off after a while.. i have a backup of stock recovery and boot but i think both files are same its 20mb both.. i had used Flashify to backup. and i can't even enter fastboot my pc does not detect my phone perhaps because i don't have the drivers... is it possible to fix my phone or its dead for ever..:crying::crying::crying::crying::crying::cry ing::silly::silly::crying:
i was following this method here.. www[dot]gizdev[dot]com/easy-way-to-root-coolpad-dazen-1/
Inscription à :
Articles (Atom)