Develop Bugs

Tips on fixing bricked ZTE Warp

It took me forever to find out how to do this simple process. I was being stupid one day with my rooted ZTE Warp, and tried to change the system font. Something went wrong, and it wiped the OS on it. This may also work on other devices. If you go to the ZTE website, go to devices, then the ZTE Warp. Click on support, and download the update utility. Open the update utility, it will ask to upgrade the utility, do it, it won't work without the update. Then follow the instruction, enter FTM mode and it should work, it will wipe all of the data on your device, but it fixed mine. If you have any problems, post a comment and I'll answer as soon as possible, Good Luck!!
Note: I am not responsible if your device breaks.

another method would be to flash easy root or n00b ROM from stock recovery or cwm. EasyRoot would allow you to then install a custom or stock rom back on the phone. n00b ROM would install that rom and it works from either stock or cusom recovery, both these would get out out of a soft brick.
for a hard brick if you can still get to ftm mode the method posted is the best way to go if you can't get into recovery.

[Q] GT-I8160L Peculiar Boot Issue

After attempting to update to the recent Jellybean release for my gt-i8160L I've been left with something between a soft brick and a hard brick. When I attempt to boot the phone normally it can only reach the Samsung model number screen, no animated boot screen. Recovery mode is not accessible, fortunately Download mode is accessible. I've attempted flashing an original "single file" firmware with Odin and the JB to GB method with Russian CSC available here. So far, nothing has fixed the problem and I am left with nothing but Download mode.
Also, when flashing original firmware with Odin, after the auto reboot, I'm given a big green "PASS" even though my device is still dysfunctional. Thanks in advance, all help is much appreciated!
Sorry for the repost. I've been receiving replies asking me questions with answers I've already addressed.

We just can't flash PDA & CSC files from GT-I8160 (russian) on GT-I8160L variant{different WCDMA frequency bands}

noexpo said:
After attempting to update to the recent Jellybean release for my gt-i8160L I've been left with something between a soft brick and a hard brick. When I attempt to boot the phone normally it can only reach the Samsung model number screen, no animated boot screen. Recovery mode is not accessible, fortunately Download mode is accessible. I've attempted flashing an original "single file" firmware with Odin and the JB to GB method with Russian CSC available here. So far, nothing has fixed the problem and I am left with nothing but Download mode.
Also, when flashing original firmware with Odin, after the auto reboot, I'm given a big green "PASS" even though my device is still dysfunctional. Thanks in advance, all help is much appreciated!
Sorry for the repost. I've been receiving replies asking me questions with answers I've already addressed.
Click to expand...
Click to collapse
Forum member @fluffi444 posted a howto for i8160P here: http://forum.xda-developers.com/showthread.php?t=2352064 but i am not sure for L version.
I expirienced similar problem while i was playing around with i8160P. I suggest you to flash kernel with CWM, it is lot easier if you have cwm and with cwm you can root your phone and after that we will see what to do next. Ideal would be if you have a full (or some kind) of backup.
Look here for kernel and root: http://forum.xda-developers.com/showthread.php?t=2059948
Also good thread from @loof13 : http://forum.xda-developers.com/showthread.php?t=2159250

Hi
i have same problem please help

[GUIDE]How not to brick your device

Everyday I see posts about people Bricking( Soft bricking/Hard Bricking) their Xperia S, Ion,AcroS or any other Xperia.Most of the times it is because people know that they have to flash or root or to unlock bootloader but do not have a clear information about what it actually means
I am creating this thread in order to tell you what the terminologies actually mean and how to avoid these bricks
First things you should know:
What is Android??
Android is basically a linux based kernel Operating System for your phones(We probably have heard it a gazillion times)
What it actually means?
Android is an operating system for phones built on a linux kernel. Linux is nothing but a clone of Unix Operating System which is another operating system like Windows. One main feature of Linux is that it is open source unlike windows.
Example of Linux kernel based OS for computer includes Ubuntu
What is kernel?
Kernel is nothing but a bridge between your hardware and Software
What it actually means?
Kernel controls your software according to your systems hardware.So on a computer if you press a key(eg:a) on keyboard. Kernel tells the OS that the key a has been pressed and to interpret it accordingly.So on a phone if you touch the home button,The kernel tells your OS that home button has been pressed and to take action accordingly.
So now comes the question.What if you flash an incompatible kernel?
Simple. Think of your computer having nothing but the monitor and without any working hardware.(I have a keyboard with a defective 'm' key,irritates the hell out of me)...Same happens to your phone. Even the booting process needs the kernel and hence you get the dreaded Soft-Brick...
What is bootloader?
Bootloader is a partition on your device that tells the phone with OS to load
What it actually means?
In Windows you see C:,D: etc..one of them contain your windows folder. In linux,it is different in name,not the concept. In linux based OS like Ubuntu, the partitions are /boot,/home,/root,/system,/recovery.....just like c:,d:,e: etc....
in android stock, you will have /boot,/system,/root.../boot is nothing but the bootloader...and in our sony phones this /boot aka bootloader is locked
What does bootloader contain?
bootloader as the name suggests tells your phone which os to boot..in our case it is the stock rom or custom or whatever os u have on the phone. Pretty self explanatory.
What is Flashmode and fastboot?
Flashmode as the name suggests is a mode which allows you to flash stuff(ROM's,kernel etc) on your phone
Fastboot mode: fastboot mode is another mode on your phone that allows you to flash stuff as well as debug it
What it actually means?
Flashmode: Pretty self explanatory
fastboot: It is used by both flashtool as well as ADB. fastboot allows you to test your kernel or whatever you are flashing..
command: fastboot boot boot.img
This command will boot boot.img(containing kernel/recovery or both and ramdisk) on your phone but wont flash it i.e. a test run. If boot.img doesnt boot,you can just disconnect and restart
command: fastboot flash boot boot.img
This command will flash the boot.img on your phone and then start it with the new boot.img.
Now fastboot wont work with a locked bootloader.So you cannot flash anything on your phone that requires a fastboot flash if your bootloader or /boot partition on your phone is locked
What is flashtool?
Flashtool is a tool developed and maintained by Androxyde, Bin4ry ,Doomlord. This tool lets you do a lot of things to your phone but its main usage is to flash stock Roms, kernels or anything that comes in an ftf package on your phone
What it means to you?
If anything goes wrong. The first thing you would need is this tool to revert back to Stock ROM. So keep this tool ready in case you are entering into the world of flashing custom firmware
What all can go wrong?
Frankly a lot of things(including power cuts,battery going dead)..
What you can avoid?
First thing,read read and read...A custom ROM would have a list of compatible devices..Go through the post and see if your device is listed. If your device
is listed and compatible then you can proceed. Flashing an incompatible ROM will result in a soft brick or hard,depending upon what you are flashing
>Next check if ROM requires a locked bootloader or unlocked(Important)
>Next if you are planning on unlocking bootloader, its better to flash CWM first on your phone and then flash ROM through CWM
What is CWM?
CWM aka Clockworkmod is a custom recovery that allows you to do a host of stuff including flashing of ROMs or zip packages
What it means to you?
Every phone has a recovery partition just like i told in the partition section. However, Latest Sony phones including Xperia S,ION,Acro S do not have one. Now most phones have a stock recovery system which allows users to reset their phones if something goes wrong. But, just like Custom ROMs, We have Custom Recoveries like CWM aka ClockworkMod developed by Koush that has many more options like flashing packages,taking a backup.
So basically CWM would be used by you to take a backup of your current system first and then flash the ROM. Now if anything goes wrong and you get a softbrick, you can just go to CWM and restore your backup and voila!!your phone will be back to normal again
Key Points:
1. CWM needs root
2. Recovery partition is not included in Sony.So, CWM is incorporated into the kernel itself by the kernel developer. What this means to us is that we would need an unlocked bootloader for installing CWM as we would have to flash the CWM included kernel to the boot partition
>Next, Always double check the requirements of the ROM you are going to install(Important)
Ohh before i forget...What is this ROOT everyone talks about?
ROOT is nothing but administrative access to sensitive parts of your OS
What it means to you?
It is nothing but getting admin rights to your system,in our case its our phones. you wont have root access on your phones by default. one major reason for this is safety. So that people don't delete a system file by mistake and what not
With root you can do everything with your phone. Thanks to our devs, we have loads of methods available to root your phone. Good place to search would be the search button
Why are we talking about root??
Because it might be a prerequisite for your custom ROM or a part of another prerequisite for installing your ROM.
>Now double check requirements again. And don't skip any step
>Once you have met all the requirements. Lets start flashing.
Ok now what can go wrong. First low battery..phone went dead while flashing..solution: Please charge it atleast while you finish the other requirements
Laptop crashes(Very Bad luck)..Solution: Always prefer to have the ROM installed through CWM and a backup ready. If you are lucky enough, you will be able to boot into CWM to restore backup and start again.
If you are flashing through any other method, then dont worry, have flashtool ready and your stock firmware..(Check firmware before installing if its for your phone:Very Important)
Check Exclude TA partition in flashtool unless absolutely necessary
Note: If your phone is bricked, it is always better to flash your kernel first(personal opinion), Once that is done, you can easily flash the full firmware
And please wipe cache and dalvik cache after flashing a ROM through CWM: Half the people wont perform this step and then try to find solutions for the bootloop. You can do this either through the CWM or ADB. For ADB method, just search the forum
One last thing and very very important. For Phones running stock firmware with unlocked bootloader or custom FW based on stock kernel with unlocked bootloader. Don't do an OTA update as this will hardbrick your device. Better download an stock FTF of that firmware version and flash it via flashtools
If still your phone bricks then there is a very nice thread here http://forum.xda-developers.com/showthread.php?t=1849170 by Toledo_JAB on bricked phone recovery
In the next post i will add some more information like TA partition backup, some more info about Android..etc.....
In case i have forgotten anything or have given the wrong info, please let me know so that i can add/edit the OP

Reserved

Last one

may i recomend mesaging a mod or admin to pin this thread or are you already on that
Sent From The ACP HQ

Envious_Data said:
may i recomend mesaging a mod or admin to pin this thread or are you already on that
Sent From The ACP HQ
Click to expand...
Click to collapse
No bro.this is my first thread so don't know how to get it stocked

Dark Wraith said:
No bro.this is my first thread so don't know how to get it stocked
Click to expand...
Click to collapse
just PM a mod with a kind message (mod names can be found above the threads in a section)
( i dont realy know how but thats what people talk of so i assume asking a mod is the only way to pin a thread
not to hard to miss ;D
Sent From The ACP HQ

Envious_Data said:
just PM a mod with a kind message (mod names can be found above the threads in a section)
( i dont realy know how but thats what people talk of so i assume asking a mod is the only way to pin a thread
not to hard to miss ;D
Sent From The ACP HQ
Click to expand...
Click to collapse
Haha.. I'll ask if people read the thread mate and benefit from it..till now no such enthusiasm so we'll see

nice
nice

Add: -Don't clear emmc under clockworkmod. ;D
-SnowKatana ^_^~

Good
very easy to understand, Nicely explained...
I just want to know what is hard brick?

Softbrick need help!

Hey guys I'am very frustrated right now staying up overnight to fix this phone -_- I want to flash CWM to my sister's Galaxy Gio when the electricity corrupts and make the phone brick I guess.. Can't even go to recovery mode I can just access download mode but the thing is I've tried reflashing stock rom many many times using Odin but I'am always stuck up at either mibib download or assm
look for the screenshot how much time I wait hoping for a chance that it can go further :3
Things that I've tried:
Install Drivers
Kies
Get my region stock rom and download latest firmware at samfirmware
then flash again and again.
I also read that theres a chance if I change to some fresh computer I do that too and reinstall everything and my effort is still futile
Need help if someone experience this too.

[solved]
After continously experimenting I fixed the problem. I dunno why and its a new learning to me the battery causes flashing failure since Its a replacement battery :3 Y_Y

[Q] Help! Fix Stuck on Boot Logo

Hello there, all xda members.
I got Ace 2 to fix from my friend. He doesnt know exactly why did the phone becoming stuck on bootlogo. Maybe messing up with flashing GB or JB. or maybe wrong terminal command.
Ace 2 Condition :
- Its unable to pass boot logo samsung galaxy ace 2
- Its unable to enter recovery mode
- Its able to enter download mode, and its custom binary download : No, Current binary : Samsung official
Here all the thing that i have tried to fix the phone :
1. Flashing the phone with Russian Gingerbread with 3 files, Pit, CSC, and PDA. But it still stuck on bootlogo and unable to enter stock recovery. it shows succeed though on Odin, but it can't boot.
2. Flashing the phone with Latest Jelly bean, with Jelly bean pit file. Odin displaying succeed, but it doesnt boot either.
Can someone help me how to solve this problem?
Is there a condition where phone completely unable to recover from hardbrick such as stuck on bootlogo, but still able to enter download mode?
I'm going to download jelly bean mb2 or mb4 which include pit and csc from jelly bean and try to reflash it. Hope it gonna work.
Thanks for any help.

Anyone here to help me?
@ChronoMonochrome , maybe you've experienced something like this and able to resolve the problem.
The phone can't boot at all. and im a little frustrated here. I've already tried a 3 parted firmware MB4, and it doesnt work either. Tried to flash chrono 4.3 cwm through odin and it doesnt work either.
And if it really doesnt have a solution, maybe i'll just give it up. And doesnt continue researching to fix this phone. Thanks
maybe another devs that able to fix this. @ace2nutzer @fluffi444 or anyone??
It got the same case. Successfull flashing, but still doesnt boot, it just like flashing is fail. or it just like it reverted the way it was before flashing. Your help is very appreciated.

riyosakura said:
maybe another devs that able to fix this. @ace2nutzer @fluffi444 or anyone??
Click to expand...
Click to collapse
Very strange. And more strange is that several people have this "only boot to logo / only downloadmode issue"
Up to now I have no Idea - I asume that ADB is not working, because of missing recovery mode? With ADB there are plenty of possibilities.
An complete Factory reset could be helpfull - But how to do it out of downloadmode ?! Don't know.
Up to now I didn't had a Phone with this behaviour for repair at home. If it would be reproducible how this all happens, I would bring my phone to this state to find out how to repair it (riff box here - so dead ACE 2 is not a problem) - But even this is unclear - Every report regarding this said only "suddenly" "without any reason" "flashed this or that" - But no exact infomation what happend acctually.
I'm out of Ideas. Sorry!

Thanks for answering.
I dont know if i have to give up already or not. But i'll try to flash it with another pc and data cable. Maybe it gonna work.

riyosakura said:
Thanks for answering.
I dont know if i have to give up already or not. But i'll try to flash it with another pc and data cable. Maybe it gonna work.
Click to expand...
Click to collapse
Another try:
Flash with ODIN Ace2Nutzers Stock Kernel (search on FTP)
Do not let the Phone boot
After Flashing pull usb und press drictly the 3 keys to get into Rec. Mode

riyosakura said:
Anyone here to help me?
@ChronoMonochrome , maybe you've experienced something like this and able to resolve the problem.
The phone can't boot at all. and im a little frustrated here. I've already tried a 3 parted firmware MB4, and it doesnt work either. Tried to flash chrono 4.3 cwm through odin and it doesnt work either.
Click to expand...
Click to collapse
No, I haven't had the phone in such condition as described above. But I have heard that any odin-flashable file that's wrongly flashed via "Phone" entry can lead brick which is similar to this. I remember only one case - one user from 4pda has flashed some file via odin, wrongly putting file to the "phone", and wasn't able to restore it anyhow - but he also had some brick on GPIO side - vol.up worked like vol.down, and the real vol.down didn't work at all. I don't know however, what memory partitions / any devices capable of storing data would be messed after this operation, and whether it's reparable at all. I mentioned devices, that can also store data, I know only that touchscreen has small memory for its firmware(that what I had broke one day in the past after accidental firmware change in the kernel) - but maybe some other devices also has it?!
There are also some chances that it's dead flash memory - chances are pretty small, but should also be taken into account.