My phone might be bricked. After many failed attempts to flash a custom rom (I really believe there is a hardware problem since I am a flashaholic since 2009), I managed to flash stock recovery (using cwm 6) so that I could go back to bootloader and flash original ZTE rom.
Now, I can boot to stock recovery, but not to the bootloader.
When pressing Vol+ with Power, instead of going to FTM mode, it shows a white screen with ZTE logo and then reboots back to recovery.
Unfortunately, /system is corrupt with no working rom.
Any ideas?
jastonas said:
My phone might be bricked. After many failed attempts to flash a custom rom (I really believe there is a hardware problem since I am a flashaholic since 2009), I managed to flash stock recovery (using cwm 6) so that I could go back to bootloader and flash original ZTE rom.
Now, I can boot to stock recovery, but not to the bootloader.
When pressing Vol+ with Power, instead of going to FTM mode, it shows a white screen with ZTE logo and then reboots back to recovery.
Unfortunately, /system is corrupt with no working rom.
Any ideas?
Click to expand...
Click to collapse
Seriously... I FIXED IT.
But seriously... I was "Fighting" to solve this for 24 hours. The moment I make this post, I do some magic and phone works....
I really did some magic here I think
: o
jastonas said:
Seriously... I FIXED IT.
But seriously... I was "Fighting" to solve this for 24 hours. The moment I make this post, I do some magic and phone works....
I really did some magic here I think
Click to expand...
Click to collapse
What did you do ?
Blazed2 said:
What did you do ?
Click to expand...
Click to collapse
It's a while back to remember exactly but I think my Blade had a hardware problem with it's internal storage. It just worked after doing the steps correctly after a while and then it went back to be replaced....!
What problems are you having?
jastonas said:
It's a while back to remember exactly but I think my Blade had a hardware problem with it's internal storage. It just worked after doing the steps correctly after a while and then it went back to be replaced....!
What problems are you having?
Click to expand...
Click to collapse
Same as you, can't launch into FTM mode, just to stock CMW mode and can't install any ROM.
Blazed2 said:
Same as you, can't launch into FTM mode, just to stock CMW mode and can't install any ROM.
Click to expand...
Click to collapse
What happens when you try to install a ROM?
jastonas said:
What happens when you try to install a ROM?
Click to expand...
Click to collapse
Just can't! It starts unpacking and then aborts with normally error 0 or 7.
Edit: Check thread [Q] ZTE Blade 2 - Bricked ? Or something You are subscribed to this thread if you can, I state there everything.
Thanks for your time
Related
As said, after flashing AEONFLEX rom from PA KitKat, my phone is now stuck at the black screen with text: Fast boot mode started - udc_start(). I tried to hold the power button to turn off but it keep turning on with that same screen, cannot get into any other stage? Can anyone help me? I already searched through the web but no solution for my case.
kennytung said:
As said, after flashing AEONFLEX rom from PA KitKat, my phone is now stuck at the black screen with text: Fast boot mode started - udc_start(). I tried to hold the power button to turn off but it keep turning on with that same screen, cannot get into any other stage? Can anyone help me? I already searched through the web but no solution for my case.
Click to expand...
Click to collapse
go to recovery. try harder. there is lots of guides or videos how to go to recovery.
darkobas said:
go to recovery. try harder. there is lots of guides or videos how to go to recovery.
Click to expand...
Click to collapse
Thanks, I can get into recovery and flash another rom, can boot up normally now. Any reason why a specific rom can cause this?
EDIT: turn out it was my fault to forgot flash the patch of the rom also.
kennytung said:
Thanks, I can get into recovery and flash another rom, can boot up normally now. Any reason why a specific rom can cause this?
EDIT: turn out it was my fault to forgot flash the patch of the rom also.
Click to expand...
Click to collapse
yes, probably wrong kernel
So I'm rooted with TWRP loki and had CM 11 on and running for a while. I just downloaded the latest nightly through CM OS and it asked to be rebooted.
Upon rebooting to TWRP and installing the update it then just kept on trying to reboot with the CM logo. I cannot get the power and volume keys to boot it to recovery and my computer won't recognize it in this state to boot into recovery.
Any ideas??!! Please! I don't know of any way to restore it.
wave28 said:
So I'm rooted with TWRP loki and had CM 11 on and running for a while. I just downloaded the latest nightly through CM OS and it asked to be rebooted.
Upon rebooting to TWRP and installing the update it then just kept on trying to reboot with the CM logo. I cannot get the power and volume keys to boot it to recovery and my computer won't recognize it in this state to boot into recovery.
Any ideas??!! Please! I don't know of any way to restore it.
Click to expand...
Click to collapse
have you tried turning it off entirely then booting into recovery and flashing a)an older cm11 or b)nandroid backup
XxZombiePikachu said:
have you tried turning it off entirely then booting into recovery and flashing a)an older cm11 or b)nandroid backup
Click to expand...
Click to collapse
I had to take the back off and manually unplug the battery to turn it off. Then I tried the button combinations posted *power and V down* when LG logo comes on repeat to get to wipe screen. However, the phone did not go to the wipe screen, it just rebooted again.
If I could get it to boot to recovery I'd be golden.
wave28 said:
I had to take the back off and manually unplug the battery to turn it off. Then I tried the button combinations posted *power and V down* when LG logo comes on repeat to get to wipe screen. However, the phone did not go to the wipe screen, it just rebooted again.
If I could get it to boot to recovery I'd be golden.
Click to expand...
Click to collapse
have you tried getting into download mode while powered off volume up and plug into pc
XxZombiePikachu said:
have you tried getting into download mode while powered off volume up and plug into pc
Click to expand...
Click to collapse
Success!! I'm in Download Mode... What next? ADB still doesn't look to be recognizing the phone.
wave28 said:
Success!! I'm in Download Mode... What next? ADB still doesn't look to be recognizing the phone.
Click to expand...
Click to collapse
well you should be able to use this guide http://forum.xda-developers.com/showthread.php?t=2432476 to get back to stock make sure you download correct files for your device
XxZombiePikachu said:
well you should be able to use this guide http://forum.xda-developers.com/showthread.php?t=2432476 to get back to stock make sure you download correct files for your device
Click to expand...
Click to collapse
Fingers crossed. Appreciate the help. I don't think I can go back to my Nexus!
XxZombiePikachu said:
well you should be able to use this guide http://forum.xda-developers.com/showthread.php?t=2432476 to get back to stock make sure you download correct files for your device
Click to expand...
Click to collapse
Error due to low batter. I'll have to see if I can charge it without it wanting to turn on. However, it looks promising -- after three times trying I got the utility to recognize the device at least!
Either way, I appreciate the assistance.
wave28 said:
Error due to low batter. I'll have to see if I can charge it without it wanting to turn on. However, it looks promising -- after three times trying I got the utility to recognize the device at least!
Either way, I appreciate the assistance.
Click to expand...
Click to collapse
SWEET!! Took a LOT of doing but it finally got restored to stock! Let's pray that never happens ever again!!!
wave28 said:
SWEET!! Took a LOT of doing but it finally got restored to stock! Let's pray that never happens ever again!!!
Click to expand...
Click to collapse
great to see everythings up and running
My Nexus 10 has been acting up recently...the battery seemed to be draining A LOT quicker then it normally would.....the tablet would just shutdown in the middle of doing something. Fast forward a week or two, now when I turn it on it vibrates for a second, shows the "GOOGLE" logo and starts the boot animation for 4.4, vibrates and repeats the same. I manually formatted and flashed 4.4 (fastboot flash boot ...etc...) and still am getting the same issues...Any suggestions on what to try next?
Flash the newest factory image automatically via fastboot.
Sent from my Galaxy Nexus using XDA Free mobile app
Just did that to no avail....same issue as before...Anything else to try?
It almost seems like it is not charging but I would assume I could still get it to boot up while connected to the charger....correct?
Update....I flashed CWM and sideloaded gapps and a ROM...and tried that...still the result..."GOOGLE" logo comes up and then a vibration...then it goes back to "charging" (the white battery with the lightning bolt through it)
Nobody has anything? Damn...lol
cirenj said:
Nobody has anything? Damn...lol
Click to expand...
Click to collapse
Sounds like it may be a hardware issue, since flashing the factory image didn't even help. I would say trying flashing the factory image using the flash-all method, and wiping data/factory reset right after. Couldn't hurt.
cirenj said:
Nobody has anything? Damn...lol
Click to expand...
Click to collapse
You said you installed cwm -- I assume you mean the recovery rom... If I'm wrong ignore the rest.
I too have had this issue and it was not hardware. To fix this I booted into cwm (the recovery rom I use on my N10) and reinstalled a stock factory boot rom. Just for those that don't know to boot into the recovery rom, power off the tablet, then press and hold the power, volume up AND volume down simultaneously --- finally, use the volume button to scroll to the recovery menu.
uDude
texascwby1836 said:
You said you installed cwm -- I assume you mean the recovery rom... If I'm wrong ignore the rest.
I too have had this issue and it was not hardware. To fix this I booted into cwm (the recovery rom I use on my N10) and reinstalled a stock factory boot rom. Just for those that don't know to boot into the recovery rom, power off the tablet, then press and hold the power, volume up AND volume down simultaneously --- finally, use the volume button to scroll to the recovery menu.
uDude
Click to expand...
Click to collapse
I have tried that as well...I am thinking it is a hardware issue as previously stated....amazing...spend $500 for a piece of hardware only to have it die a little over 12 months later....talk about pissed off....
cirenj said:
I have tried that as well...I am thinking it is a hardware issue as previously stated....amazing...spend $500 for a piece of hardware only to have it die a little over 12 months later....talk about pissed off....
Click to expand...
Click to collapse
No shoot me a PM ..
Lets see if we can get you up and running again ..
If we do we can post what we did back here from all XDA users ..
Thx Josh
I am having the same exact issues. I too force flashed stock 4.4.4 and it still does not boot up. Any ideas on how to remedy this would be greatly appreciated.
Thank you!
Hoping to hear something as well...but doesn't look good...
Can you access adb? To check logcat while it's booting (and possibly find out why it's bootlooping)?
What did you use to format the partitions?
Sent from my Nexus 10 using Tapatalk
I can access adb on my laptop...and I used the "fastboot format" and "fastboot flash"
How would I check the logcat file?
http://forum.xda-developers.com/showthread.php?t=2274119
beekay201 said:
Can you access adb? To check logcat while it's booting (and possibly find out why it's bootlooping)?
What did you use to format the partitions?
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
I am unable to get my Nexus to show up in command prompt when I run "adb devices". Not sure what to do.
Any ideas? I've tried reflashing stock images and still have the same problems..
michaelearth said:
Any ideas? I've tried reflashing stock images and still have the same problems..
Click to expand...
Click to collapse
Can you give more details about your issue? If its still about not connecting PC and tablet see this guide for help
http://forum.xda-developers.com/showthread.php?t=2277112
demkantor said:
Can you give more details about your issue? If its still about not connecting PC and tablet see this guide for help
http://forum.xda-developers.com/showthread.php?t=2277112
Click to expand...
Click to collapse
The problem is that my tablet will reboot constantly and it shows my battery being fully drained even after charging it overnight. I'm able to force flash stock images to my tablet and this has not fixed the issue. So at the moment my nexus 10 is an expensive paperweight.
What happens when booted to bootloader or recovery? Does it act normal or loop?
demkantor said:
What happens when booted to bootloader or recovery? Does it act normal or loop?
Click to expand...
Click to collapse
When I boot into the bootloader it acts normal.
Well this is my first post here.I flashed cm 14.1 on my devices with gapps through twrp.I managed to get to recovery with the adb drivers (as I mentioned I have a broken button so pressing Volume Down+Power+Home won't work).Everything was ok but due to the critical bugs of this rom (was still in development) I decided to downgrade to cm 13 which had less bugs.So I tried getting into recovery but everytime I gave the command in it would reboot to the system (not even in stock recovery).So I decided to flash the stock rom with odin and then try entering recovery mode.After flashing I actually realised that I f*cked up cuz I couldn't wipe the system data/davik cache,due to the fact that my home button is broken and so i cant access my stock recovery.Now my device is in bootloop...I already have a usb jig and it will just make it boot into download mode where i cant really do much.Any help would be appreciated.
RemainCalm said:
Well this is my first post here.I flashed cm 14.1 on my devices with gapps through twrp.I managed to get to recovery with the adb drivers (as I mentioned I have a broken button so pressing Volume Down+Power+Home won't work).Everything was ok but due to the critical bugs of this rom (was still in development) I decided to downgrade to cm 13 which had less bugs.So I tried getting into recovery but everytime I gave the command in it would reboot to the system (not even in stock recovery).So I decided to flash the stock rom with odin and then try entering recovery mode.After flashing I actually realised that I f*cked up cuz I couldn't wipe the system data/davik cache,due to the fact that my home button is broken and so i cant access my stock recovery.Now my device is in bootloop...I already have a usb jig and it will just make it boot into download mode where i cant really do much.Any help would be appreciated.
Click to expand...
Click to collapse
And the stock rom doesn't boot ?
McFy said:
And the stock rom doesn't boot ?
Click to expand...
Click to collapse
No my phone is in bootloop.Random vibrations occur now and then.
RemainCalm said:
No my phone is in bootloop.Random vibrations occur now and then.
Click to expand...
Click to collapse
So flash twrp and then reboot on twrp using adb I thought it work on dl mode
Say if that have work and hit tank please
McFy said:
And the stock rom doesn't boot ?
Click to expand...
Click to collapse
McFy said:
So flash twrp and then reboot on twrp using adb I thought it work on dl mode
Say if that have work and hit tank please
Click to expand...
Click to collapse
Well I don't think adb recognizes a device in download mode.
Will try though
RemainCalm said:
Well I don't think adb recognizes a device in download mode.
Have you try ? O hope is still a way to unbrick may be try to repair your botom if you can
Click to expand...
Click to collapse
McFy said:
RemainCalm said:
Well I don't think adb recognizes a device in download mode.
Have you try ? O hope is still a way to unbrick may be try to repair your botom if you can
Click to expand...
Click to collapse
Not yet.Phone is dead i need to charge it first.There is no way of turning off the devices while it boots up.You can either restart it or let the battery die.I cant really fix my home button cuz in order to do so i would need to remove the screen,thus damaging the Amoled panel.I could send the phone back to samsung idk
Click to expand...
Click to collapse
RemainCalm said:
McFy said:
Not yet.Phone is dead i need to charge it first.There is no way of turning off the devices while it boots up.You can either restart it or let the battery die.I cant really fix my home button cuz in order to do so i would need to remove the screen,thus damaging the Amoled panel.I could send the phone back to samsung idk
Click to expand...
Click to collapse
Yes maybe samsung can repair it depend of your country ...
Click to expand...
Click to collapse
RemainCalm said:
McFy said:
Not yet.Phone is dead i need to charge it first.There is no way of turning off the devices while it boots up.You can either restart it or let the battery die.I cant really fix my home button cuz in order to do so i would need to remove the screen,thus damaging the Amoled panel.I could send the phone back to samsung idk
Click to expand...
Click to collapse
Boot back to download mode and reflash twrp and set "auto-reboot, should boot back to recovery then + you will need to factory reset on recovery before flashing stock as the data actually stays
Click to expand...
Click to collapse
jimbomodder said:
RemainCalm said:
Boot back to download mode and reflash twrp and set "auto-reboot, should boot back to recovery then + you will need to factory reset on recovery before flashing stock as the data actually stays
Click to expand...
Click to collapse
Thanks for replying .I gave my a500fu who is a better geek than me to try and fix it.I will either get back my phone and try this or just tell him to do this.Thanks again I hope you are the one that saves my potato :fingers-crossed:
Click to expand...
Click to collapse
jimbomodder said:
Boot back to download mode and reflash twrp and set "auto-reboot, should boot back to recovery then + you will need to factory reset on recovery before flashing stock as the data actually stays
Click to expand...
Click to collapse
Didnt work phone boots back to system.
RemainCalm said:
Didnt work phone boots back to system.
Click to expand...
Click to collapse
Then you'll need to fix home button, it's not part of screen. It's got its own circuit underneath
My phone stuck on samsung logo and can only boot on download mode unable to boot into recovery ...tried to flash stock firmware also repair firmware that comes with AP BL CB CSC AND PIT FILE ..and flashed CWM and TWRP with no use...
Flash stock firmware through Odin and post fail message .
JJEgan said:
Flash stock firmware through Odin and post fail message .
Click to expand...
Click to collapse
I already did that ..it gives pass but the phone boots and stuck on the logo (SAMSUNG GALAXY NOTE 3)..only restart on download mode no recovery
Suggests wrong firmware flashed .
Maybe you will get more info in the multiple identical questions you have posted .
JJEgan said:
Suggests wrong firmware flashed .
Maybe you will get more info in the multiple identical questions you have posted .
Click to expand...
Click to collapse
Of course i need help that's why i posted (multiple identical question)???
After successfully flashing the latest stock ROM with Odin, are you performing a factory wipe before booting the phone for the first time?
audit13 said:
After successfully flashing the latest stock ROM with Odin, are you performing a factory wipe before booting the phone for the first time?
Click to expand...
Click to collapse
I could not enter the recovery mode at all...even i flash the firmware successfuly
alitaleb said:
I could not enter the recovery mode at all...even i flash the firmware successfuly
Click to expand...
Click to collapse
Flash TWRP after you flash stock and immediately try to boot into recovery before the first ever boot, then wipe everything.
ShaDisNX255 said:
Flash TWRP after you flash stock and immediately try to boot into recovery before the first ever boot, then wipe everything.
Click to expand...
Click to collapse
Will give it a try again....
alitaleb said:
I could not enter the recovery mode at all...even i flash the firmware successfuly
Click to expand...
Click to collapse
You are unchecking auto reboot in Odin? You are using the correct button combination to enter recovery?
audit13 said:
You are unchecking auto reboot in Odin? You are using the correct button combination to enter recovery?
Click to expand...
Click to collapse
Yes i did that several times...power button volume up and main button below the screen...i flashed twrp recovery right now after flashing stock firmware...wit no use....only download mode whic i can enter....foes that mean the phone is brick?but it can flash firmware successfuly every time i flash stock firmware it gives PASS....
Is there any custom rom can be flashed via odin?
Looks like you are doing every right and it could be a bad memory chip in the phone.
I think the last hope would be to take the phone to a shop with a riff or octopus box and have them force flash the phone. If that doesn't solve the problem, memory chip is probably defective.
Thanx for everyone who provided his help, knwoledge and experience to solve my issue.
Appreciate it from my heart????
Have you solved the problem ? If yes can tell us what did the trick ?
Thanks,
Droiid848 said:
Have you solved the problem ? If yes can tell us what did the trick ?
No...i did everything related to software with no use, i gave up...???
Click to expand...
Click to collapse
alitaleb said:
Droiid848 said:
Have you solved the problem ? If yes can tell us what did the trick ?
No...i did everything related to software with no use, i gave up...
Click to expand...
Click to collapse
Hi Alitaleb,
I read back the posts, and it seems you have a problem close to mine (not exactelly the same but similar..) see here :
https://forum.xda-developers.com/galaxy-note-3/help/help-understanding-to-wipe-device-t3679424
I was thinking of something about your problem, are you sure that the volume button is not defective ? I explain myself:
when you want to go to the recovery mode, the volume up has to be pushed, if the up button does not respond correctly then you may think you push up but in fact it is the down position that is detected by your phone...
I would suggest you to dismantle the back of your phone and check if there is no some dirt or simply broken part in the volume button..
Cheers,
Click to expand...
Click to collapse
Droiid848 said:
alitaleb said:
Hi Alitaleb,
I read back the posts, and it seems you have a problem close to mine (not exactelly the same but similar..) see here :
https://forum.xda-developers.com/galaxy-note-3/help/help-understanding-to-wipe-device-t3679424
I was thinking of something about your problem, are you sure that the volume button is not defective ? I explain myself:
when you want to go to the recovery mode, the volume up has to be pushed, if the up button does not respond correctly then you may think you push up but in fact it is the down position that is detected by your phone...
I would suggest you to dismantle the back of your phone and check if there is no some dirt or simply broken part in the volume button..
Cheers,
Click to expand...
Click to collapse
Thank you for your relpy..but the volume buttons up and down are working fine..that's appear when i want to flash via odin..i checked both of them and working fine
Click to expand...
Click to collapse
alitaleb said:
My phone stuck on samsung logo and can only boot on download mode unable to boot into recovery ...tried to flash stock firmware also repair firmware that comes with AP BL CB CSC AND PIT FILE ..and flashed CWM and TWRP with no use...
Click to expand...
Click to collapse
Hello
brother i read your thread and i know its an hardware problem because same thing happened in my galaxy s4 and i did everything to solved it but failed and in the end i had purchased logic board for my s4
sufian.ahmed2007 said:
Hello
brother i read your thread and i know its an hardware problem because same thing happened in my galaxy s4 and i did everything to solved it but failed and in the end i had purchased logic board for my s4
Click to expand...
Click to collapse
Thanx a lot..that's what i realized later on...???