[Completed] Bricked ZTE Blade C2 V809 - XDA Assist

ZTE Blade C2 V809
Well I simply changed recovery-from-boot.p name to recovery-from-boot.p-bak and install-recovery.sh to install-recovery.sh-bak
Now the phone doesn't boot properly, in fact it's stuck in a boot loop:
-Starts
-Shows white ZTE logo on screen
-Restarts
Tried connecting the phone via USB cable and used fastboot devices & adb devices commands, no devices found.
Also tried pressing "power + vol down" and "power + vol up", nothing. I can't enter recovery mode or bootloader.
I need another way to get in and change the name of those specific files, or re-install the OS.
I need help finding the desired solution for this specific phone or similar brand one, or some kind of expertise who knows more about this.
There's always a way.

Mr Doodly fox said:
ZTE Blade C2 V809
Well I simply changed recovery-from-boot.p name to recovery-from-boot.p-bak and install-recovery.sh to install-recovery.sh-bak
Now the phone doesn't boot properly, in fact it's stuck in a boot loop:
-Starts
-Shows white ZTE logo on screen
-Restarts
Tried connecting the phone via USB cable and used fastboot devices & adb devices commands, no devices found.
Also tried pressing "power + vol down" and "power + vol up", nothing. I can't enter recovery mode or bootloader.
I need another way to get in and change the name of those specific files, or re-install the OS.
I need help finding the desired solution for this specific phone or similar brand one, or some kind of expertise who knows more about this.
There's always a way.
Click to expand...
Click to collapse
Hi, thank you for using XDA assist.
There is a general forum for android here http://forum.xda-developers.com/android/help where you can get better help and support if you try to ask over there.
Good luck.

Related

[Completed] [Q] Huawei Ascend P1 LTE U9202L-1 Build120

Hello
I have 2 exactly same model of Huawei Ascend P1 LTE U9202L-1 Build120. One of them is working fine all this while. However, lately, the other device stucked at the booting logo screen and unable to boot to the main screen.
I have tried ADB and Fastboot command, and it somehow managed to get the problem set to main screen, but the "Power" and "Vol Down" buttons not working when in the recovery mode and as well the main screen. However, when I tried to boot to the fastboot mode by pressing the "Power" and "Vol Down" buttons, my pc recognized it and I could enter fastboot commands, but not in the recovery mode and main screen mode....not so sure what are the exact problems and errors....to put in simple, the "Power" and "Vol Down" buttons are not spoilt, but I do not know why they are not working when in the recovery mode and main screen mode?? Whether the problem set is semi-bricked or just software corruption??
I have read the forums about using command "fastboot flash boot boot.img", "fastboot flash recovery recovery.img" and "fastboot flash system system.img", but confusing me....and I do not want to take the risk....
I would like to know is there any faster ways to clone the rom images of the good working set, and flash it on the problem set? Any experts out there kindly assist.
Many Thanks.
Hi,
It sounds like the buttons are failing to me. Maybe it's a software issue, but unlikely. I can't find anything relevant on XDA about your issue, so you will need to ask for help here,
> Android Development and Hacking > Android Q&A, Help & Troubleshooting
Good luck!
Thank you. Thread closed.

[Completed] Android boot loop - is my device dead?

Hello All,
This is my first post at this forum.
I've come to a point where I'm on the verge of giving up.
A few days ago my Nexus 5 entered a boot loop without me doing anything special with it - it was just in my pocket.
All see is the google logo for a few seconds , then the screen goes down for a few more, and back to the google logo.
I'm able to go into fastboot by hold down the volume down (only) button when this happens, but the boot loop happens when I choose to boot into recovery mode.
My device has an unlocked bootloader.
I have fast boot access and no ADB (ADB wait-for-device doesn't work).
Went over a tutorial from androidforums.com and flashed a completely new image using fastboot.
The entire process worked, but the phone is still at the same state.
I've read that there is and issue with the power button on these devices - so I tried all methods of knocking it against stuff without success.
I've taken it to a lab nearby and the guy there was sure it was the power button. He said he fixed about 50 of these already - after a few hours he called me up and said he had replaced the power button 3 times and he's giving up.
in short , this is the current situation :
1. Device stuck in bootloop - only google logo is seen
2. can boot into fastboot (and have fastboot access from PC) but can't boot into recovery
3. flushing a stock succeeds but won't help
4. power button seems o.k.
I am about to call this a bricked phone and look for a new one but something inside me tells me that this might still be a software issue and can be fixed.
I would be happy to know if there is a way to know what is failing in the boot sequence. or maybe load a debug application on to the device to check the HW. I've yet to find any help in that direction.
I'm a software eng. working in the cellular comm. field, so I'm up for anything that anyone has in mind.
Thanks,
Ran.
XDA Visitor said:
Hello All,
This is my first post at this forum.
I've come to a point where I'm on the verge of giving up.
A few days ago my Nexus 5 entered a boot loop without me doing anything special with it - it was just in my pocket.
All see is the google logo for a few seconds , then the screen goes down for a few more, and back to the google logo.
I'm able to go into fastboot by hold down the volume down (only) button when this happens, but the boot loop happens when I choose to boot into recovery mode.
My device has an unlocked bootloader.
I have fast boot access and no ADB (ADB wait-for-device doesn't work).
Went over a tutorial from androidforums.com and flashed a completely new image using fastboot.
The entire process worked, but the phone is still at the same state.
I've read that there is and issue with the power button on these devices - so I tried all methods of knocking it against stuff without success.
I've taken it to a lab nearby and the guy there was sure it was the power button. He said he fixed about 50 of these already - after a few hours he called me up and said he had replaced the power button 3 times and he's giving up.
in short , this is the current situation :
1. Device stuck in bootloop - only google logo is seen
2. can boot into fastboot (and have fastboot access from PC) but can't boot into recovery
3. flushing a stock succeeds but won't help
4. power button seems o.k.
I am about to call this a bricked phone and look for a new one but something inside me tells me that this might still be a software issue and can be fixed.
I would be happy to know if there is a way to know what is failing in the boot sequence. or maybe load a debug application on to the device to check the HW. I've yet to find any help in that direction.
I'm a software eng. working in the cellular comm. field, so I'm up for anything that anyone has in mind.
Thanks,
Ran.
Click to expand...
Click to collapse
Hello, and welcome to XDA!
It does sound like a hardware issue and it could be the power button, except for one thing: wouldn't a held down power button in fastboot cause a shutdown as well? Maybe not, but I thought I'd ask that.
At any rate, better to get an opinion from someone who actually has the deivce. Please create an account (so you post in other forums) and then post in this thread (can copy and paste from here):
> Google Nexus 5 > Nexus 5 Q&A, Help & Troubleshooting > [HELP THREAD] Nexus 5
Hope this helps, and good luck!

[Completed] [HELP] Can't root ZTE KIS 3

I've been trying to use a tutorial on modaco which I can't link because I'm a new user to root my ZTE KIS 3, but I can't get past the fastboot command, it says "wating for device" and nothing happens, I've tried turning it on myself, I've held down the power button and power + vol up for 20 seconds maximum and nothing happens, I've waited withou touching it and it just stays black. I feel like the rest is a piece of cake, I just can't get past fastboot for making a rom dump. Any help?
Hi,
Thanks for using XDA Assist.
Please check the below thread to setup Fastboot:
[Guide] How To Setup And Use Fastboot

[Completed] Recovery only shows no command.

Hello.I have a Gigaset qv1030 with Nvidia Tegra 4 cpu.
The main idea is that i cannot enter the android due to not knowing the password.So i ''tried'' to went to recovery for a fresh wipe/factory reset.Problem is no key combination does start up recovery.
Power+volume up does only power up the tablet / Power volume down does nothing and freezes the tablet (need to hold power for it to resests).
Only thing that does work however is if i press Volume up and power , after first vibration pressing volume down (with all 3 button now pressed) goes me into bootloader (says Unlocked) , and have the following options continue , reboot , fastboot protocol , recovery kernel , power off.
Fastboot protocol only restarts the tablet at the same point back into the bootloader (useless i guess)
Recovery kernel brings up an green android sitting on it's back with a red triangle saying no command. (tried every combination found , nothing seems to work)
Adb debugging is not set up in the settings i guess , and fastboot does appear in device manager if connected to a PC but it just does not accept any drivers (neither the modified google_usb drivers with tegra enabled , neither some found on the internet trough drivescape).So no device is found by the PC .
Connecting it while on the password screen, PC does recognize the tablet but that's it . No adb recognition.
This is as far as i got , idk what to do . Please help?
# PS yes i did not own the tablet , i got scammed by someone , and hoped to do the best out of the situation.
i think it is android 4.2
Hello, and welcome to Assist,
I'm afraid we can't really help if you've lost/forgot your password. The password is there to protect the information that is contained in the file.
You'll have to create an account to post in the main forums if you have any other questions.
Good luck
Razvan

Phone died after installing ROM

I wanted to install Global Developer ROM for my Redmi 3s Prime which I downloaded from their website. So I started with installing TWRP custom recovery and completed successfully. After this I installed my developer ROM and after success TWRP tool asked me whether to root the phone or not, to which I said YES.
After this blank screen appeared for very long time and nothing happened. So, I long pressed the power button and now my phone is not booting up at all.
I tried the following things but none of them are working.
Fastboot mode by pressing VOLUME DOWN + POWER buttons.
Recovery mode by pressing VOLUME UP + POWER Buttons
Also tried by pressing all three buttons.
I also ran these commands adb devices and fastboot devices, cannot see my device.
And even the battery charging indicator is also not showing up.
Is there any tool or something which can help me to fix this problem?
Any help is appreciated.
chat_faraz said:
I wanted to install Global Developer ROM for my Redmi 3s Prime which I downloaded from their website. So I started with installing TWRP custom recovery and completed successfully. After this I installed my developer ROM and after success TWRP tool asked me whether to root the phone or not, to which I said YES.
After this blank screen appeared for very long time and nothing happened. So, I long pressed the power button and now my phone is not booting up at all.
I tried the following things but none of them are working.
Fastboot mode by pressing VOLUME DOWN + POWER buttons.
Recovery mode by pressing VOLUME UP + POWER Buttons
Also tried by pressing all three buttons.
I also ran these commands adb devices and fastboot devices, cannot see my device.
And even the battery charging indicator is also not showing up.
Is there any tool or something which can help me to fix this problem?
Any help is appreciated.
Click to expand...
Click to collapse
Was the ROM built for your specific model number of Redmi 3s Prime? If it was for a different model number then that's what bricked your device, it probably didn't have anything to do with the message asking you if you wanted to root the device.
If the device does not charge and shows no LED while connected, does not boot to any of its modes, does not connect to PC and makes no tone when connecting it and does not show anything in device manager on PC then your device is hard bricked. You need to replace the motherboard or send the device to a repair shop that offers a JTAG service.
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Categories

Resources