Hello i'm new in here and i think this is an awesome forum
Anyway, i'm willing to root my phone but i just don't want to reach the point where my phone got Hard Brick or useless. So how long does rooted phone live? Would it only take a months? because i can read some topics in other forums that their phone got bricked. Why is that happening? Is that normal? And how to avoid soft brick or hard brick? I will not be downloading some Rooted Apps if i root my phone. I just want to use this Wifikill app, dsploit and etc. but i will not be flashing customized ROM or themes. So would it still "soft brick or hard brick" my phone?
Thanks !!!!
Rooting isn't dangerous if you're careful
Hi there, I'm not sure what you mean by "how long does a rooted phone live", but I'll try to answer as best as I can.
Rooted phones 'live' as long as a non-rooted phone, the only risk of rooting a phone is the flashing part. For todays rooting methodes it's actually hard to hardbrick a phone, espescially when you just follow the steps provided by the rooting process.
Hardbricking a phone means that you messed up the flashing soo badly that there is no way to recover the phone. I actually tried on purpose to hardbrick an old SGS3 and even when I removed the USB cable while flashing the recovery, I was still able to revive the phone.
Softbricking however is much more common, but actually quite easy to revive from. All you need to un-brick the device includes having ADB/FastBoot on your PC or access to the recovery.
This way you can allways reflash the recovery or ROM if this gets corrupted.
You'll need a custom recovery to root your phone. You can brick your device if you pick the wrong recovery, but this is easy to check. Always match up the modelnumer of your phone with the one for the recovery.
After the rom has been installed, you'll need to flash the SuperSU zip to succesfully root your device and after that, you're all set.
So, bottomline is: as long as you make sure your phone is fully charged, and your PC won't randomly shutdown (that's why I always flash from a laptop). There is no way you can mess up.
For the lifetime of your phone: If you aren't planning on overclocking, you don't have to worry about shortening the lifetime of the device.
If you're going to root, always make a backup of your data, just in case something does go wrong!
For the apps you're mentioning: Just make sure you use those apps on your own network!
Flashing
So you mean flashing is the most common reason that bricks your phone? What if i want to play games, listens to music, texting or calling, does it brick your phone(soft or hard?)? And is it possible for the unrooted phone to be brick bit by bit if you keep on flashing wrong recovery file? I hope you can answer all my questions
No it's not possible to brick your phone by playing games, music ect. Flashing (Writing another recovery or updating your ROM) is the one and only way to brick your device.
If you flash the wrong recovery image to your device, it will be bricked. It 'should' be fixable in most cases.
The question about unrooted phones... Well, you can flash an custom recovery on your phone and get it bricked that way, but there is no need to flash another recovery if you're not going to root the device afterwards.
So just to clarify, you're not going to brick your device by normal use, rooted or not. The bricking part is when you're installing the recovery and root. When you succesfully rooted your device, there is no way you can brick it, until you're going to install another ROM on your device.
The worst thing that could happen with installing another ROM is getting stuck in a bootloop, but that can be fixed by going into the recovery and reflash(or install, if you prefer that term) the ROM. Unless it's the first time you're installing a custom ROM, in that case you will be stuck in a bootloop because you'll need to wipe the data, system and cache partition before installing a ROM. This prevents getting in a bootloop after installing a new ROM
Thanks !
Ok so i think i will root my phone tomorrow Im not in a purpose of installing custom ROM or kernel. I just want to use apps like dsploit or wifikill and it needs a proper root access. So its all clear and now i understand how bricky part happen. THANKS !
Related
Hi guys,
I've been playing around with my Nexus S for about 3 weeks and I've decided to root it, but I have some question, I've been searching the answers in older posts but it's not quite clear yet, hope you can help me.
When I unlocked the bootloader, what kind of data will be wiped? It's just the SD card or also all the apps I've already downloaded? what about SMS, pictures and videos?
Is there anyway I can backup that data considering I haven't root it yet???
Thanks in advance.
dont do it man. i just got my phone yesterday at 1 pm and its now 12am and its bricked by lack of support from the cummunity. i studyied and studied 4 around 10 hours. then bricked my device. and i have a good idea i wont be getting a replacement this time
LINKSLOVESANDROID said:
dont do it man. i just got my phone yesterday at 1 pm and its now 12am and its bricked by lack of support from the cummunity. i studyied and studied 4 around 10 hours. then bricked my device. and i have a good idea i wont be getting a replacement this time
Click to expand...
Click to collapse
lol what? its nobodys fault but your own. all the resources are available, just because somebody isnt responding to your threads and holding your hand to restore a nandriod backup doesnt make it a "lack of a community".. and your phone isn't bricked, it can be recovered but you are too close-minded and cant install Clockwork Recovery / get drivers working
The data that will be wiped are most likely your SMS/settings/etc. This is standard procedure. And its something you'll go through a lot when you are using custom ROMs.
There are complete instructions for rooting, unrooting and unbricking your phone. It's all here in the forums, and many other places, you just have to look and learn. I read for two weeks before I unlocked and loaded a ROM into my NS.
If you don't have a need to root your phone I wouldn't do it just because you can. I wanted to run the Voodoo app so I had to root and load a ROM. It took a little while but it was painless and I liked learning about the Android system.
You do have to backup your app and your SD, but that was the easy part.
It's close to impossible to brick a nexus device. They purposely come with totally open boot loaders specifically for that purpose!
RogerPodacter said:
It's close to impossible to brick a nexus device. They purposely come with totally open boot loaders specifically for that purpose!
Click to expand...
Click to collapse
its not only Nexus devices but like I said people are using the term brick wrong. with these new phones coming out, a lot of them are hard to brick.
if you're phone is able to get into recovery/start/download mode (odin not popular but still an option)/bootloader then its not bricked.
if its unable to start in any form or way.. its considered a brick. please stop using the term in its wrong definition.
"brick" describes a device that cannot function in any capacity (such as a device with damaged firmware)
In the strictest sense of the term, bricking must imply that software error has rendered the device completely unrecoverable without some hardware replacement.
http://en.wikipedia.org/wiki/Brick_(electronics)
Click to expand...
Click to collapse
I think guys you have lost focus about my question, it's not about how to root (there is a lot of info about), it's about what kind of data will be wiped and how to back it up
Netconn said:
You do have to backup your app and your SD, but that was the easy part.
Click to expand...
Click to collapse
What's the best way to do it? It's there an app or I have to day it by myself?
Make a nandroid backup first and foremost! Use Titanium Backup to make a backup of all your apps. If you want a backup of your sms, go sms pro really does a great job of that. Dont forget your contacts as well! Then copy your sd card and place it on the hard drive of your computer. When you unlock the bootloader, it does wipe your sd card. Once your unlocked and rooted, you should be able to restore everything once you replace the copy of your sd card back on the phone. Coming over from a Vibrant, I was nervous about rooting the phone but its an easy process. Just take your time and do lots of reading! Hope this helps!
Thenx, but I still have one doubt, if I haven't root my phone yet, will nandroid or titanium work?
Sent from my Nexus S using XDA App
Woops..yeah, your right there. Too quick to reply. I followed this method here..
http://forum.xda-developers.com/showthread.php?t=895545
and had no problems. Once you get unlocked/rooted and clockwork recovery, then you can make the fore mentioned backups. Export your contacts to the sd card then copy the sd card to the hard drive of your computer before unlocking the boot loader. I do not think apps get affected during the sd wipe unless you have them stored there.
zephiK said:
its not only Nexus devices but like I said people are using the term brick wrong. with these new phones coming out, a lot of them are hard to brick.
if you're phone is able to get into recovery/start/download mode (odin not popular but still an option)/bootloader then its not bricked.
if its unable to start in any form or way.. its considered a brick. please stop using the term in its wrong definition.
Click to expand...
Click to collapse
i followed the instructions to flash gri74 back to stock and my phone wont turn on, wont goto any mode, wont read that its hookedup to my pc
isnt that what we call a brick? ive had issues on a galaxy s with this game issue. htc devices i can fly through the root procedure but i got this 1 rooted, tried reflashing to stock and the phone wont turn on at all.
may i suggest a noob proof guide|? i postted 1 in the htc desire forum and people love it. yesterday i returned a moto xoom because ti was overheating , got a nexus s and 2day il b returning that because it wont turn on. can any1 help me think of a good idea i can tell the future shop return people?
kmhil said:
I think guys you have lost focus about my question, it's not about how to root (there is a lot of info about), it's about what kind of data will be wiped and how to back it up
What's the best way to do it? It's there an app or I have to day it by myself?
Click to expand...
Click to collapse
you are forced to lose your data to initially root your device. then after that point, you can always create backups and never lose data again while you switch between ROMs and flashing etc. but i think to initially root, you have to lose everything. not the sd card though.
LINKSLOVESANDROID said:
i followed the instructions to flash gri74 back to stock and my phone wont turn on, wont goto any mode, wont read that its hookedup to my pc
isnt that what we call a brick? ive had issues on a galaxy s with this game issue. htc devices i can fly through the root procedure but i got this 1 rooted, tried reflashing to stock and the phone wont turn on at all.
Click to expand...
Click to collapse
Do keep in mind, we don't have an i9020 or an i9023, we have an i9020A So the instruction out there all need to take that into considerations. I rooted mine fine with no "Bricking" I had to follow the instruction for the i9023, but it worked. I figure it took me all of 1 minute to root my phone. Admitedly, the "One click root" for the Galaxy series was easier.
I try to make it a point to never be the "First" person to do something on their phone. Much safer that way.
I also find it very unusual that you've managed to brick two phones, I've also had the pleasure of owning the telus fascinate, and not once did i get it bricked, I tried Bionics, CM7, Darky's and a bunch of other ones. Just never mess with the boot loader. When you went back to stock, did you make sure it was a stock ROM for the I9020A?
Have you tried connecting the USB to a computer, holding the volume up (or in the case of the galaxy, both up and down) While powering on the device? I've had to use that a few times to recover my galaxy (Thank you odin!!).
Now in regards to the OP, I would recommend using a program like Ti to back everything up, unlock the bootloader then restore from Ti, it's a little more hassel, but you can pretty much keep your settings and data. Personally, i rooted my phone before configuring a single thing on it.
kmhil said:
Thenx, but I still have one doubt, if I haven't root my phone yet, will nandroid or titanium work?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
there is no way to make a good backup without rooting.
basically yes, you will lose all your settings
there are a few apps you can use to backup your apk before unlocing/rooting the phone.
look for App admin on market https://market.android.com/details?id=az.mecid.appadmin&feature=search_result
the stuff backed to SD does not get wiped
only the internal storage stuff
LINKSLOVESANDROID said:
dont do it man. i just got my phone yesterday at 1 pm and its now 12am and its bricked by lack of support from the cummunity. i studyied and studied 4 around 10 hours. then bricked my device. and i have a good idea i wont be getting a replacement this time
Click to expand...
Click to collapse
i took about 12 minutes total to unlock my bootloader, flash clockwork, and flash a custom rom. its not difficult if you pay attention to what you read. youre phone is not bricked. btw, i read your threads. if you werent so demanding, i would have helped. use the pdanet website the next time you need to install the proper driver, and follow the directions that they give you.
When I unlocked I used Astro to back up my apps, I turned on the Google data sync to back up my contacts and I did a back up of my SD on my computer.
When the unlock and recovery was done NS asked for my Google account then it restored all my contacts, Astro restored all my apps and I restored my files from my computer. A few steps but not difficult at all.
You will have to redo your accounts and data, and maybe an app or two won't load but the market will show them installed, just reinstall any that didn't.
Make sure you follow the directions properly in the forum. I had to use two computers to get it to work, but it did work and nothing was damaged.
With all that said.... This was the first time I have ever owned or altered an Android phone. Sure I was nervous... Now I'm hooked.. haha
I wound up using NSCollab .17 so far so good..
First thing I did when I got my phone was fastboot oem unlock.
Even if you don't want to root, use another ROM. Fastboot unlock it so your data doesn't get wiped.
If your hardware and everything seems okay, then flash Clockwork Recovery and do a nandroid backup so you can restore to pre-flashing point if you need it for OEM purposes.
Afterwards, go crazy and flash like theres no tomorrow and find something that you'll like.
And agreed with simms. You've made so made so many threads about this. I would help you step by step but I've been busy so I can't do that anymore. But if you search, you'll find about two or three threads where I did help somebody get their phone to a working state.
The basic idea is... if your phone doesn't boot but you can get to recovery.
- Download a ROM or Nandroid backup
- Install USB drivers
- Fastboot oem unlock (if you haven't)
- fastboot flash recovery recovery.img (or whatever the recovery.img is named) should be in /sdk/tools
- reboot into recovery (adb reboot recovery)
- mount and storage: mount USB, put the nandroid backup or ROM onto phone
- nandroid restore or flash a ROM (wipe factory,dalvik,cache --> flash ROM (if its CM7.. flash gapps afterwards)
- reboot
your phone boots. alternatively, you can use Odin but thats not a popular method but the choice is available if you wish to go towards that approach
in the worse worse possible case scenario there is always ODIN to the rescue
Why did you guys wait at all?
Once i got the phone i immediately plugged it into my computer and rooted it.
Hey people, I am slightly new to xda developers but I am an experienced rooted user. So I saw many people who are inexperienced at rooting their phones brick their phones very easily. Yes I did notice a few "how to avoid bricking your phone" threads but they are quite old. Since the new versions of updates and apps are rolling out, I thought it might be a good time to post a newer thread.
Ways to avoid bricking your device.
* When flashing a custom rom or kernel, ALWAYS use the kernel or rom that is for your device and your device only.
I realized that online it does not say anything about always flashing the custom rom or device that is for your device only. Many users are out there who brick their phones by flashing the wrong rom or kernel. ( I myself have once bricked my phone like this).
*Avoid apps that can brick your device.
Many people brick their phones like this because once you have a rooted device, you want to try out all the cool root apps. Also please people name some apps that will brick your device as well.
*** APPS THAT CAN BRICK YOUR DEVICE***
Fonts installer(root), Chain fire 3D when installed on AOS 4.0 and above, switchme when installed on a custom rom, and so on. (I have more apps I could list but I am sure people out there will post it). The basic idea is read the comments about the app and see if the app is safe. Many people just get the apps online without researching and end up bricking their phones. EDIT: Any type of font installer app that is for rooted phones only have a high chance of bricking your device. One tap root apps can give a virus to your device without knowing and have chances that it will brick. After all, it is an application that roots your device, there is always a catch. z4 root for example will give you a virus and brick your device. Rom manager *can* brick your device if you try to flash a custom recovery. For Rom manager, there are users who have successfully flashed a custom recovery and users who have bricked their phones. There is definitely a risk, so I recommend flashing a custom recovery on a safer application like goo manager. Goo manager will be safe if you READ the instruction, if you do not, you will be carrying a brick in your pocket.
*When flashing/installing or in a rooting progress be patient
When flashing or rooting be patient. Do not unplug or turn off the device when in a rooting or flashing progress because that will brick the device, and I am not talking about boot loop/soft brick. Im talking about hard brick, a black screen no sign of life brick. (Once bricked my phone like that lol).
*Research and follow instructions.
Many people tend to skip the reading and researching and do it by their feeling. Then what happens? They carry around a brick in their pocket.
Research about your phone and learn it. All I got to say for this one is, READ READ AND READ.
Anyways everyone that is all I got to say, I have more things but they are minor and someone will definitely post it. Please everyone take the time to comment your thoughts and ideas on how to avoid bricking your device. I hope many users found this helpful.
Good informative article, but .... when your phone have to brick, it will brick hehe
aamirrajpoot said:
Good informative article, but .... when your phone have to brick, it will brick hehe
Click to expand...
Click to collapse
lol
Tell us , what other apps to avoid/be careful with? Pls.
Btw this thread is good idea..
raze_da_noize said:
lol
Click to expand...
Click to collapse
Can i recover my phone from brick without any backup of old stock rom?
raze_da_noize said:
Hey people, I am slightly new to xda developers but I am an experienced rooted user. So I saw many people who are inexperienced at rooting their phones brick their phones very easily. Yes I did notice a few "how to avoid bricking your phone" threads but they are quite old. Since the new versions of updates and apps are rolling out, I thought it might be a good time to post a newer thread.
Ways to avoid bricking your device.
* When flashing a custom rom or kernel, ALWAYS use the kernel or rom that is for your device and your device only.
I realized that online it does not say anything about always flashing the custom rom or device that is for your device only. Many users are out there who brick their phones by flashing the wrong rom or kernel. ( I myself have once bricked my phone like this).
*Avoid apps that can brick your device.
Many people brick their phones like this because once you have a rooted device, you want to try out all the cool root apps. Also please people name some apps that will brick your device as well.
*** APPS THAT CAN BRICK YOUR DEVICE***
Fonts installer(root), Chain fire 3D when installed on AOS 4.0 and above, switchme when installed on a custom rom, and so on. (I have more apps I could list but I am sure people out there will post it). The basic idea is read the comments about the app and see if the app is safe. Many people just get the apps online without researching and end up bricking their phones. EDIT: Any type of font installer app that is for rooted phones only have a high chance of bricking your device. One tap root apps can give a virus to your device without knowing and have chances that it will brick. After all, it is an application that roots your device, there is always a catch. z4 root for example will give you a virus and brick your device. Rom manager *can* brick your device if you try to flash a custom recovery. For Rom manager, there are users who have successfully flashed a custom recovery and users who have bricked their phones. There is definitely a risk, so I recommend flashing a custom recovery on a safer application like goo manager. Goo manager will be safe if you READ the instruction, if you do not, you will be carrying a brick in your pocket.
*When flashing/installing or in a rooting progress be patient
When flashing or rooting be patient. Do not unplug or turn off the device when in a rooting or flashing progress because that will brick the device, and I am not talking about boot loop/soft brick. Im talking about hard brick, a black screen no sign of life brick. (Once bricked my phone like that lol).
*Research and follow instructions.
Many people tend to skip the reading and researching and do it by their feeling. Then what happens? They carry around a brick in their pocket.
Research about your phone and learn it. All I got to say for this one is, READ READ AND READ.
Anyways everyone that is all I got to say, I have more things but they are minor and someone will definitely post it. Please everyone take the time to comment your thoughts and ideas on how to avoid bricking your device. I hope many users found this helpful.
Click to expand...
Click to collapse
I bricked my poco X3 NFC by installing a recovery image by *flashify* app
p.s: i had root access and i already have TWRP, but the reason i wanted to switch to orange fox it's because i haven't access to the whole storage on TWRP recovery so i wanted to install Orange Fox to try it out, and i was too lazy to install it by PC, and i said to myself , why not installing it by the phone it self! After installing it on *Flashify* it asks to reboot, after that i got a bootloop and i don't even know if it's installed . Now the phone it's returned to the shop so it can be fixed...
But altough it's happened, i'm planning to flash more custom rom, ad try the cool Kernel s cause it's fun.
simonbigwave said:
Tell us , what other apps to avoid/be careful with? Pls.
Btw this thread is good idea..
Click to expand...
Click to collapse
Bro i bricked my poco x3 by *Flashify* app it's on google play and it bricked my phone.
Those members posted in 2016! So don't expect a reply... Flashify app hasn't been updated since 2015...be ware.
galaxys said:
Those members posted in 2016! So don't expect a reply... Flashify app hasn't been updated since 2015...be ware.
Click to expand...
Click to collapse
Didn't know that but thx for tye info
Bricking is a condition when a device is usually interrupted in an attempt to update the device. There can be 6 steps to avoid bricking
(1) custom recovery,
(2) know ADB and Fastboot commands;
(3) keep a factory image on your phone;
(4) keep a Nandroid backup on your phone;
(5) keep copies of both backups on a computer;
(6) if you can't replace your battery, know how to hard reset your phone.
Adameur said:
I bricked my poco X3 NFC by installing a recovery image by *flashify* app
p.s: i had root access and i already have TWRP, but the reason i wanted to switch to orange fox it's because i haven't access to the whole storage on TWRP recovery so i wanted to install Orange Fox to try it out, and i was too lazy to install it by PC, and i said to myself , why not installing it by the phone it self! After installing it on *Flashify* it asks to reboot, after that i got a bootloop and i don't even know if it's installed . Now the phone it's returned to the shop so it can be fixed...
But altough it's happened, i'm planning to flash more custom rom, ad try the cool Kernel s cause it's fun.
Click to expand...
Click to collapse
U gave ur phone in shop what did they said?
Honestly one of the most laughable things imo is to return your phone to the shop or any technical expert shop.
Guys what you want the shop to do for you? Factory Reset? Don't think them as a real experienced ones, they just know the basics. Any any one who have an experience of installing custom ROMs or TWRP & Rooting, is better than most of the shop repairs.
They are just experiencers for the AVERAGE people. I maybe even when I sometimes go to the shop to fix my devices, I tell the employee what to do, because they hardly know about their tools.
IF YOU DON'T WANT TO SPEND A LOT OF TIME, DON'T ROOT. Basic Logic, Root isn't for normal users and wont give you a huge advantages. Root is ONLY for fun and amusing, there are no real need of Root. So if you're too lazy to search for solution and trying many methods of solving your problem, and you just hurry to fix your device. DON'T ROOT IT.
Hello, i just rooted my phone (a few minutes ago) and i enjoy root, but i want to ask, is it dangerous to install a custom rom? I want to instal FlexOS but i am kinda scared to do it. I was very very nervous about rooting my phone, but in the end i did it. I have it from 3 weeks and if it breaks, i don't think i will use a smartphone for a while. It gave an error about partition wipe, i got stuck in a bootloop but i rebooted the phone and the bootloader was unlocked and the phone boots normally.
Well there is no danger unless you make a mistake. If you want to flash any custom rom, read all the instructions carefully provided by the ROM administrator. You can also check users feedback in the corresponding thread. Make sure there are no doubts left in you mind before flashing process.
Guru.Eclairs said:
Well there is no danger unless you make a mistake. If you want to flash any custom rom, read all the instructions carefully provided by the ROM administrator. You can also check users feedback in the corresponding thread. Make sure there are no doubts left in you mind before flashing process.
Click to expand...
Click to collapse
Yeah, I will install a custom ROM after a month or two, gotta enjoy a bit of xposed and root first and have no doubts.
Thanks!
Don't want to make a second thread for this, is it possible when using the phone with a custom rom the phone to randomly hard brick itself? If it's a soft brick (i need to reflash or wipe) i don't really have a problem.
Deep explaining how you get your device brick and how can your prevent it !!
Brick is caused by flashing file in system. Like flashing new rom or flashing cwm recovery image which is not supported to your device. And if you try to flash it your device will brick. I will really act like a brick. Pc identifies it like a unown device. There is two kinds of brick hard brick and soft brick. So lets us understand soft brick
Soft brick : In soft brick your device freezes on boot logo or something keep rebooting that is called bootloop . The Bootloop can be easily covered by performing factory reset and wip cache. And soft brick can be covered by re-flashing stock rom. Softbrick is caused when you flash incorrect rom or image also it happens when you are updating OS without clearing cache or data. That deleted system partition. Though it is not that danger than hard brick. Device still boots so dont get panic on softbrick.
Hard brick : It is the most dangerous thing happens on android all the system partition constains data of boot get delted and its extremely hard to cover. Now days it can be covered but in some cases there is no way to cover it except changing the motherboard and they cost you alot for technical help also you waranty voilds since you have rooted no way only one way to pay for service. It is much hard to cover then soft brick your device keep disconnecting from pc then again connecting alsk there is no sign of life in if beacuse there is no recovery no boot nothing just blank. It is actually a brick. In other words yoy can say nothing than a paper weight. Though dont worry about hard brick its rare just sometimes hard ware got damage so now how can you be safe from it !!
So the main reason of brick is root! So main thing let us study about root what is it and why you need it and why it bricks the device.
Root: Root is a acess to user to acess system data. He can delete system apps also system recovery. So unown threats can easily enter in system and damage the system files. Though most of the latest root management apps have high security from these threats they first ask you wheater you need ti give it root acess or not also it blocks silent install which is alsot of risky. After getting root acess some threats can even get to the android core the linux kernel and which is the most important part of android os. Every root apps arent secure. Super SU is the best root security management tool also kingroot king user is good i am not saying other tools are bad but these are the popular tools. Brick also occurs when you try to install Xposed Installer Framework. So sometimes the Xposed Framework damage the android so before selecting framework see if it is 100% stable and supported to the device the beta version has much bug and high chance of getting brick. But dont worry if you choose the architect and the framework supported to your device. There is no problem. And also one most thing that most of user didn't notice that thier warranty is voild but some companies give warranty back if you remove root and reset the system. But some companies won't give warranty back. So if you never root you will never install or flash another rom that is unofficial rom. Made by some other person not the developer of your device or google so it may contains many bugs !!! They are also harmfuk to android. I am not saying never to install custom rom but while installing your device can get brick so its harmful for normal android user. Also it is not necessary for getting brick tou must have root or flash the file to the system. It also occurs while some system errors like also while reset the system and also by android update. And keep in mind never update your system when you have ever rooted the device beacuse there are chances of brick by that also
Thank you for reading if you like please hit thanks.
I thought everything was fixable with flashtool as long as the bootloader is unlocked.. never been so wrong in my life.
Bought a used xperia z3 6166 t mobile version without knowing its support for custom roms (smh).. steps i did:
1)installed recovery.
2) rooted the device
3) unlocked the bootloader (successfully)
4) i thought i was ready to install custom roms like niaboc79's existenz which consequently I did, the phone did boot after that but was connecting in fastboot and flashboot so
5)using flashtool flash stock latest d6616 firmware and was back to step 1.
read somewhere that I could flash d6603 firmware because both phones have same specs so
6)flash d6603 firmware in order to get existenz working
7)flashtool gave some errors and failed
8)used fastboot to flash kernel
the device stops responding all of a sudden..
9) kept on charge for hours, still got nothing , no vibration, no lights , no hard rest via combination of buttons , nothing by pressing the yellow button inside the flap..
10) pc shows usb not recongnized after a couple of seconds of connecting ..
its been beyond frustrating going through the internet, scrolling through threads after thread but no avail.. people say at least the phone should be recognized by pc in any form other than usb not recongnized .. so I went to a local smartphone repair shop and gave it to him but he isnt too hopeful either.. I already have xperia z1c which i messed with so many times but it always responds to the flashtool.. but buying xperia z3 is literally the worst smartphone experience of my life!
is there any way to make this dead brick work again.. any unorthodox means to rewrite boot to make it jump start? any help is appreciated!
hash054 said:
I thought everything was fixable with flashtool as long as the bootloader is unlocked.. never been so wrong in my life.
Bought a used xperia z3 6166 t mobile version without knowing its support for custom roms (smh).. steps i did:
1)installed recovery.
2) rooted the device
3) unlocked the bootloader (successfully)
4) i thought i was ready to install custom roms like niaboc79's existenz which consequently I did, the phone did boot after that but was connecting in fastboot and flashboot so
5)using flashtool flash stock latest d6616 firmware and was back to step 1.
read somewhere that I could flash d6603 firmware because both phones have same specs so
6)flash d6603 firmware in order to get existenz working
7)flashtool gave some errors and failed
8)used fastboot to flash kernel
the device stops responding all of a sudden..
9) kept on charge for hours, still got nothing , no vibration, no lights , no hard rest via combination of buttons , nothing by pressing the yellow button inside the flap..
10) pc shows usb not recongnized after a couple of seconds of connecting ..
its been beyond frustrating going through the internet, scrolling through threads after thread but no avail.. people say at least the phone should be recognized by pc in any form other than usb not recongnized .. so I went to a local smartphone repair shop and gave it to him but he isnt too hopeful either.. I already have xperia z1c which i messed with so many times but it always responds to the flashtool.. but buying xperia z3 is literally the worst smartphone experience of my life!
is there any way to make this dead brick work again.. any unorthodox means to rewrite boot to make it jump start? any help is appreciated!
Click to expand...
Click to collapse
My sincerest apologize for your misfortune. I have not yet encountered this degree of issues. I am going to keep my bootloader locked I do believe. Just got this phone myself and I really wish I could help you. The TMO version of this phone is definitely the worst one I think given the lack of software support.
However I was wondering what method you followed to install recovery and if you attempted to install exposed.
arikdahn said:
My sincerest apologize for your misfortune. I have not yet encountered this degree of issues. I am going to keep my bootloader locked I do believe. Just got this phone myself and I really wish I could help you. The TMO version of this phone is definitely the worst one I think given the lack of software support.
However I was wondering what method you followed to install recovery and if you attempted to install exposed.
Click to expand...
Click to collapse
used the XZdualrecovery zip for locked bootloader.. it was fairly simple , did it twice without any problems! then used recovery to install superuser and update it binaries and the phone was rooted.. I didnt installed xposed because i want to upgrade from lollipop.. that I couldnt do! :crying:
May this thread be a warning to people who themselves arent developers but have a little knowledge about custom roms to do their homework before diving into things they cant get out of..
hash054 said:
used the XZdualrecovery zip for locked bootloader.. it was fairly simple , did it twice without any problems! then used recovery to install superuser and update it binaries and the phone was rooted.. I didnt installed xposed because i want to upgrade from lollipop.. that I couldnt do! :crying:
May this thread be a warning to people who themselves arent developers but have a little knowledge about custom roms to do their homework before diving into things they cant get out of..
Click to expand...
Click to collapse
I will second the f*** out of this, but I will also add that recovery TYPICALLY protects you from a ton of heartache. Not this time huh? Well, I cannot get Kingroot off my frickin' phone. I think it may have been commandeered by China. The uninstall always fails. So I may be in the same boat as you. Not sure if I can install recovery with it on there or not, but I do know it and SuperSU do not play nicely. I am debating which would be more risky, factory resetting a rooted phone to get rid of kingroot, or attempting to install recovery with this scary AF root manager. What a pain in the ass.
So this is the procedure you followed?
https://forum.xda-developers.com/showpost.php?p=60507399&postcount=171
arikdahn said:
I will second the f*** out of this, but I will also add that recovery TYPICALLY protects you from a ton of heartache. Not this time huh? Well, I cannot get Kingroot off my frickin' phone. I think it may have been commandeered by China. The uninstall always fails. So I may be in the same boat as you. Not sure if I can install recovery with it on there or not, but I do know it and SuperSU do not play nicely. I am debating which would be more risky, factory resetting a rooted phone to get rid of kingroot, or attempting to install recovery with this scary AF root manager. What a pain in the ass.
So this is the procedure you followed?
https://forum.xda-developers.com/showpost.php?p=60507399&postcount=171
Click to expand...
Click to collapse
No thats the rooting method.. I just simply flashed the recovery from http://nut.xperia-files.com/path/XZDualRecovery/XZDualRecovery_2.8.26 and just installed superuser and updated the binaries..
I did also have a problem with kingroot.. you can download the official ftf firmware for d6616 and just flash it in flashboot through flashtool.. its the only way to get rid of kingroot in my experience .. but I would give you caution to flash nothing else except official firmware through flashtool.. and do it only if you know how to handle it.. as far my experience is concerned, I did get rid of the kingroot this way not once but twice without problem .. its the stuff that followed bricked the phone.. also my bootloader was unlockable so it might have made a difference..maybe
hash054 said:
No thats the rooting method.. I just simply flashed the recovery from http://nut.xperia-files.com/path/XZDualRecovery/XZDualRecovery_2.8.26 and just installed superuser and updated the binaries..
I did also have a problem with kingroot.. you can download the official ftf firmware for d6616 and just flash it in flashboot through flashtool.. its the only way to get rid of kingroot in my experience .. but I would give you caution to flash nothing else except official firmware through flashtool.. and do it only if you know how to handle it.. as far my experience is concerned, I did get rid of the kingroot this way not once but twice without problem .. its the stuff that followed bricked the phone.. also my bootloader was unlockable so it might have made a difference..maybe
Click to expand...
Click to collapse
Well I guess I'll be doing that then. Thanks. So how do you flash that file without a recovery?
I do not know how to handle flash tool since I have only heard of it and never used it. It appears I'll be using it to get rid of kingroot. How does one learn how to handle it so's one doesn't go and mess anything up?
My bootloader is also unlockable but I don't wanna screw with all the things that unlocking it does to the phone so I'm leaving it alone. I like those features
Also did you ever try to remove bloat on the stock ROM? Everything I remove via titanium backup just reinstalls immediately after removal.
Sorry for all the questions instead of answers for you. You are one of the few still messing with this device and I appreciate all your help very much. All of the info on this forum is mostly applicable to when the phone came out. This means almost all of it only applies to android 4.4 or it doesn't apply to the T-Mobile variant b/c T-Mobile was less popular when this phone was a flagship and uses Wifi text/calling which requires special planning. That and the fact that the threads are several hundred pages long makes following along impossible and makes this site all but useless for these phones now.