Related
Hey guys,
I want to know potential ways to brick my phone so I will be more careful.
Which ones will brick my phone?
1. Flashing recovery for another phone
2. Flashing ROM for another phone
3. Flashing just the kernel for another phone
4. Flashing wrong ROM without the kernel
5. Flashing a mod for another phone
6. Pulling the battery when doing a NAND restore/backup
7. Pulling the battery when installing a mod or a ROM
Or any others you know about. Thanks!
And no, I don't want to brick my phone, this is for prevention
To be honest its seriously not recommended to do any of the things you listed, some of them you may be able to restore your NAND to fix others will kill your phone. Just make sure you follow the guides on here and you'll be fine. But seriously don't install mods or roms that are for another phone.
Sent From My Omega'd Galaxy S3 ...
Don't do any of those....its still a £500 phone and doing any of those things you mentioned will reduce your phone to a rather uncomfortable form of loo roll! If you catch my drift....
Sent from my GT-I9300 using xda premium
That depends on the definition of "bricking". For me, a bricked phone is one that can no longer be fixed no matter what you do: it has no use other than an expensive paperweight.
Flashing kernels (even if wrong ones) won't brick your phone. They will render your phone unuseable until a proper kernel is flashed, but it isn't a brick.
Also, wrong ROMs won't brick your phone UNLESS they also contain a bootloader and/or a Partition Information Table (PIT) file, which is quite rare.
So, bricking (by my definition), only happens when you mess with the bootloader and/or the PIT, because those are either impossible or extremely hard to fix.
No matter what you do, DO NOT mess with the bootloader: as long as the bootloader is ok, everything else (including the PIT) can be fixed with some effort.
Simonetti2011 said:
That depends on the definition of "bricking". For me, a bricked phone is one that can no longer be fixed no matter what you do: it has no use other than an expensive paperweight.
Flashing kernels (even if wrong ones) won't brick your phone. They will render your phone unuseable until a proper kernel is flashed, but it isn't a brick.
Also, wrong ROMs won't brick your phone UNLESS they also contain a bootloader and/or a Partition Information Table (PIT) file, which is quite rare.
So, bricking (by my definition), only happens when you mess with the bootloader and/or the PIT, because those are either impossible or extremely hard to fix.
No matter what you do, DO NOT mess with the bootloader: as long as the bootloader is ok, everything else (including the PIT) can be fixed with some effort.
Click to expand...
Click to collapse
Thank you, that's exactly the answer I was looking for. So it's impossible to hardbrick my SGS3 unless I flash the bootloader?
Glebun said:
Thank you, that's exactly the answer I was looking for. So it's impossible to hardbrick my SGS3 unless I flash the bootloader?
Click to expand...
Click to collapse
Yes, or the PIT (Partition Information table).
Never, EVER, flash any of these, unless you know EXACTLY what and why you are doing it: PIT, Bootloader, Recovery.
Flashing kernels and simple ROMs (such as the stock ones) don't brick your phone.
Simonetti2011 said:
Flashing kernels and simple ROMs (such as the stock ones) don't brick your phone.
Click to expand...
Click to collapse
What bout custom ROMs, like CM10?
Glebun said:
What bout custom ROMs, like CM10?
Click to expand...
Click to collapse
You have to know if they include a recovery and/or bootloader before flashing.
Usually they DON'T, but you have to check.
Besides, you don't need CMW ( = recovery) to use CM10 ( = ROM), although some badly informed people will tell you that you do.
Glebun said:
Hey guys,
I want to know potential ways to brick my phone so I will be more careful.
Which ones will brick my phone?
1. Flashing recovery for another phone
2. Flashing ROM for another phone
3. Flashing just the kernel for another phone
4. Flashing wrong ROM without the kernel
5. Flashing a mod for another phone
6. Pulling the battery when doing a NAND restore/backup
7. Pulling the battery when installing a mod or a ROM
Or any others you know about. Thanks!
And no, I don't want to brick my phone, this is for prevention
Click to expand...
Click to collapse
Well, even though it's only for prevention;
this is the ultimate way of bricking a device:
Take a picture or download a picture of the desired device, make sure it fits onto a brick, then glue the picture onto a brick, voilà, you now have a bricked device.
Now to serious things:
All the things you wrote are correct.
Hope I could help!
LG familyguy59/Beatsleigher
familyguy59 said:
Now to serious things:
All the things you wrote are correct.
Hope I could help!
LG familyguy59/Beatsleigher
Click to expand...
Click to collapse
What do you mean? I just asked a question. Are you saying that all of the actions I listed will hardbrick my device? So who should I believe then?
Glebun said:
What do you mean? I just asked a question. Are you saying that all of the actions I listed will hardbrick my device? So who should I believe then?
Click to expand...
Click to collapse
They can potentially brick your device, because they use different drivers, files, etc. ... and the partitions are stored in different parts of the memory, changing these partitions can confuse the device and therefore brick it.
I said "serious things" because the first thing I wrote, was a n00b joke, I saw on the forums a while back...
Believe what you wish, all I'm saying is this:
if you flash something to your device, that was intentioned for a different device, then it's your responsibility, because most devs/modders warn you, and I did here, now. Everything you do to your device voids your warranty, and potentially harms your device, what you do to your phone is your thing, all we can do is advise you not to do things, it's your responsibility..
Hope I could help!
LG familyguy59/Beatsleigher
---------- Post added at 11:13 PM ---------- Previous post was at 11:11 PM ----------
Simonetti2011 said:
That depends on the definition of "bricking". For me, a bricked phone is one that can no longer be fixed no matter what you do: it has no use other than an expensive paperweight.
Click to expand...
Click to collapse
You can always repair a bricked device with a JTAG, it's just the cost and the time consumption, that scares people off
LG familyguy59/Beatsleigher
I'd just pull the battery while flashing a bootloader. Guaranteed brick with little chances of recovery. You need to be fast though, that bootloader is really small and flashes fast
familyguy59 said:
They can potentially brick your device, because they use different drivers, files, etc. ... and the partitions are stored in different parts of the memory, changing these partitions can confuse the device and therefore brick it.
Click to expand...
Click to collapse
So Simonetti2011 is wrong?
familyguy59 said:
They can potentially brick your device, because they use different drivers, files, etc. ... and the partitions are stored in different parts of the memory, changing these partitions can confuse the device and therefore brick it.
Click to expand...
Click to collapse
You are incorrect.
Only a PIT file can change partitions.
Besides, the location of files are standardized across firmwares.
that is why I wrote (page 1 of this thread) that the ROM being flashed must inform if they contain PIT's or recoveries. Stock ROMs (and all ROMs based on Samsung stock ROMs) do not change the PIT, recovery or bootloader.
If the user is going to flash a ROM that is not stock-based AND the developer of the ROM won't tell what it does, then simply avoid that ROM.
I stand correct: as long as the PIT and bootloader are untouched, the phone can be revived with very little effort (matter of minutes).
A JTAG can certainly be used in most cases, but not only it will take a few days (to get the thing delivered), but it will also be quite expensive and demand a lot of technical knowledge. So, I usually consider a device that requires a JTAG to be revived as bricked since I'd rather send it to an authorized service center than try to do it myself and make things worse.
My (most of ours, I guess) S III has a 1 year warranty. I figure that I can mess with it pretty bad and if it gets FUBAR I'll simply send it a service center.
So far, I'm yet to brick my SII, my SIII or even a HTC Kaiser which came with Windows Mobile 6.0 and got an upgrade to Android 2.3.7! I've flashed more ROMs than I can remember, I've wiped, I've lost data, but I have never bricked a single phone.
the thing is that whatever I do I read a lot beforehand and if I think - no matter how little - a ROM can be insecure, I simply don't do it.
My experience has taught me that something others consider a "must-have", I consider a waste of time and unnecessary headache and trouble: one such example is CWM.
There are dozens of people here with USB and MHL problems and 99% of them have CWM. That is NOT a coincidence.
I loved overclocking my S II, using SiyahKernel for that, but the device driver support in it (specially for wifi) was so bad that it was a waste of time.
What most people don't get is the definition of BRICKING. Will an improper stock ROM render your phone unusable? YES. Can it be fixed in 5 minutes? YES. Is that bricking? NO.
UNUSABLE <> USELESS
I am on jellybean can I directly flash any ics custom rom from cwm and then wipe and this wont brick my s3 I am asking this question because I had a galaxy note which was on ics and I flashed cm10 on it I had made a backup of the stock rom I found it to be little unstable so I restored the nand backup of stock rom this hard bricked my device
Simonetti2011 said:
That depends on the definition of "bricking". For me, a bricked phone is one that can no longer be fixed no matter what you do: it has no use other than an expensive paperweight.
Flashing kernels (even if wrong ones) won't brick your phone. They will render your phone unuseable until a proper kernel is flashed, but it isn't a brick.
Also, wrong ROMs won't brick your phone UNLESS they also contain a bootloader and/or a Partition Information Table (PIT) file, which is quite rare.
So, bricking (by my definition), only happens when you mess with the bootloader and/or the PIT, because those are either impossible or extremely hard to fix.
No matter what you do, DO NOT mess with the bootloader: as long as the bootloader is ok, everything else (including the PIT) can be fixed with some effort.
Click to expand...
Click to collapse
Did You Mean If I Flashed Custom ROM Made Specially For My Phone (Codec For i9300) My Phone Will Not Hard Brick?
THE.W!ZARD said:
Did You Mean If I Flashed Custom ROM Made Specially For My Phone (Codec For i9300) My Phone Will Not Hard Brick?
Click to expand...
Click to collapse
that means if you flash ANY custom ROM, you won't hard brick, because they don't touch the bootloader
Glebun said:
What bout custom ROMs, like CM10?
Click to expand...
Click to collapse
CM10 is safe. It does not include any of these information that can brick your phone.
---------- Post added at 09:33 AM ---------- Previous post was at 09:27 AM ----------
Glebun said:
that means if you flash ANY custom ROM, you won't hard brick, because they don't touch the bootloader
Click to expand...
Click to collapse
Yes, typically but keep in mind that if you flash rom from different phone model then it might soft brick your phone or some core services might not work.
I kinda did it to myself a couple of weeks ago. I have international i9300 and I flashed a rom for att. everything went smooth but my phone reception was not working. I was like WTF. then I checked rom correctly and I find it was for ATT. I was terrified that I might have broke my phone's reception forever. But then I again flashed CM10 for i9300 international and I am back into game again.
So when you flash any rom, try to double check phone model and reviews in discussion thread.
Yeah, but a soft brick is not a problem at all. I'm sure all of us have had a couple of them
Glebun said:
Yeah, but a soft brick is not a problem at all. I'm sure all of us have had a couple of them
Click to expand...
Click to collapse
yes
Hi,
I have a Pantech Flex P8010. I never thought it would be updated to jb. So I rooted it. Removed all bloated applications from it. Changed the recovery to CWM. I haven't taken any back up before the bloat removal. All I have is the cwm backup of the debloated version.
Now Pantech have released the jb ota. Oh well I never knew that this was going to happen ever.
I have a couple of questions.
Is there any way to update the phone to jb with the root privilege?
Is there any way to return to complete stock?
Will the recovery and bootloader image available in the forums be useful?
Any help would be really great help.
Thanks a lot.
hi
can someone pls upload or send me a stock rom for the flex i lose my backup when my sister mess with my computer
I think we should wait. You can make back up even now if your device is bootable..
What recovery u use? Clockworkmod?
Sent from my PantechP8010 using xda premium
anoopch said:
Hi,
I have a Pantech Flex P8010. I never thought it would be updated to jb. So I rooted it. Removed all bloated applications from it. Changed the recovery to CWM. I haven't taken any back up before the bloat removal. All I have is the cwm backup of the debloated version.
Now Pantech have released the jb ota. Oh well I never knew that this was going to happen ever.
I have a couple of questions.
Is there any way to update the phone to jb with the root privilege? No
Is there any way to return to complete stock?No
Will the recovery and bootloader image available in the forums be useful? Not Yet
Any help would be really great help.
Thanks a lot.
Click to expand...
Click to collapse
As it sits right now unfortunately we have no complete stock image to put back on the phone in order to restore it to a pure factory state. The factory restore on the phone does not affect the recovery only the data. In as much OTA updates are not available at this time and probably never since this phone is getting older. If you attempt to install the OTA update and get caught in the CWM bootloop simply start the phone in fastboot mode (I believe it is power + the volume down key on this phone) and choose the reboot option it will then skip the recovery and start the phone normally. Sorry I don't have any better answers for you. I'm hoping to land an HTC One in the near future...
I have the same problem :\ i removed all the at&t apps and the at&t software updater and when i go to update setting force close :,(
Backup Pantech Flex AT&T Apps
lopez_angel3 said:
I have the same problem :\ i removed all the at&t apps and the at&t software updater and when i go to update setting force close :,(
Click to expand...
Click to collapse
I also accidentally removed 1 too many of the at&t apps from my Pantech Flex using Titanium Backup. I am already running the 4.1.2 Jelly Bean update.
Would anyone out there be willing to use Titanium Backup to create 'backups' of the stock Pantech AT&T apps for us to recover with?
I'd be willing to pay for the Titanium Backup app as well as a bit for the time and effort.
Thanks!
Update to JB
Hi guys, maybe this was asked before, I want to know, now is possible to update to JB if I have a stock ICS? I know it was possible before but many peoples were facing a WiFi problem. I am on stock ICS, but would like to try JB.
CondriX said:
Hi guys, maybe this was asked before, I want to know, now is possible to update to JB if I have a stock ICS? I know it was possible before but many peoples were facing a WiFi problem. I am on stock ICS, but would like to try JB.
Click to expand...
Click to collapse
Yes. Go here. http://forum.xda-developers.com/showpost.php?p=46177375&postcount=462
attn1 said:
Yes. Go here. http://forum.xda-developers.com/showpost.php?p=46177375&postcount=462
Click to expand...
Click to collapse
Ok, thank you very much. Still, I have some questions if you don't mind. First I have to install CWM on my Flex, or is it already in my phone? If there is a tutorial that wil be nice, if not i will find somehow how to do it. I am just new to Android, my last phone was a Symbian one (Nokia C7) and it was pretty easy to install a new firmware on that one.
help needed Pantech flex wont boot or turn on
Soo i just picked up a like new pantech flex on the att carrier today.I've been searching online for hours about a problem im having. Will not charge,power on nor boot. Im kinda a noob I guess idk.ive done a little hands on with androids repairing and fixed a few galaxy s2s that needed stock roms put back on thats as far as I got. Now I bought the phone as is not working for $20 figured id give it a try..the condition is flawless and no signs of dropping or water damage at all.lady seller said she may have over charged the battery..idk please help if u know of any similiar problems with fixs.ive tried to connect it to my laptop running win7 it recognizes something upon plug in but states unrecognized usb device etc..I cannot find pantech flex drivers or any related help if anyone can please any advice appretiated
skillitmade said:
Soo i just picked up a like new pantech flex on the att carrier today.I've been searching online for hours about a problem im having. Will not charge,power on nor boot. Im kinda a noob I guess idk.ive done a little hands on with androids repairing and fixed a few galaxy s2s that needed stock roms put back on thats as far as I got. Now I bought the phone as is not working for $20 figured id give it a try..the condition is flawless and no signs of dropping or water damage at all.lady seller said she may have over charged the battery..idk please help if u know of any similiar problems with fixs.ive tried to connect it to my laptop running win7 it recognizes something upon plug in but states unrecognized usb device etc..I cannot find pantech flex drivers or any related help if anyone can please any advice appretiated
Click to expand...
Click to collapse
Have you tried the pantech PC suite for the drivers?
So I've heard that some people have permanently bricked their phones by rooting them and making mistakes and I just don't understand this. I have rooted mine and it isn't bricked or anything but how is this possible?
Coming from Windows/PC Windows programming and maintenance I've fixed computer that had absolute corrupted hardware from malware or user error. No matter how bad the SOFTWARE is corrupted the computer itself is left undamaged in terms of hardware.
I'm not saying that certain forms of malware can't affect hardware under bizarre circumstances but generally this seems to be an old wives tail. If you rewrite the Master Boot Record on Windows Re flash Firmware and completely format and reinstall Windows it WILL fix even the most complex malware ROOTKITS like tdl4 which installs itself to the MBR (Master Boot Record.)
Why can't you do the same thing on an Android phone? Lets pretend the system gets extremely corrupted from being root what keeps me from removing everything and completely re-installing android? I don't get how you can permanently brick your phone from a software issue alone no matter how corrupted the phone is?
ableright said:
So I've heard that some people have permanently bricked their phones by rooting them and making mistakes and I just don't understand this. I have rooted mine and it isn't bricked or anything but how is this possible?
Coming from Windows/PC Windows programming and maintenance I've fixed computer that had absolute corrupted hardware from malware or user error. No matter how bad the SOFTWARE is corrupted the computer itself is left undamaged in terms of hardware.
I'm not saying that certain forms of malware can't affect hardware under bizarre circumstances but generally this seems to be an old wives tail. If you rewrite the Master Boot Record on Windows Re flash Firmware and completely format and reinstall Windows it WILL fix even the most complex malware ROOTKITS like tdl4 which installs itself to the MBR (Master Boot Record.)
Why can't you do the same thing on an Android phone? Lets pretend the system gets extremely corrupted from being root what keeps me from removing everything and completely re-installing android? I don't get how you can permanently brick your phone from a software issue alone no matter how corrupted the phone is?
Click to expand...
Click to collapse
Nobody has anything to say about this? I'm amazed. I've been reading online that it's hard to permanently brick your phone from rooting alone but some say it's impossible I get different theories everywhere lol?
ableright said:
Nobody has anything to say about this? I'm amazed. I've been reading online that it's hard to permanently brick your phone from rooting alone but some say it's impossible I get different theories everywhere lol?
Click to expand...
Click to collapse
Thread moved to Android Q&A, Help & Troubleshooting.
Perhaps if you post in the correct forum, you would get more responses.
ableright said:
So I've heard that some people have permanently bricked their phones by rooting them and making mistakes and I just don't understand this. I have rooted mine and it isn't bricked or anything but how is this possible?
Coming from Windows/PC Windows programming and maintenance I've fixed computer that had absolute corrupted hardware from malware or user error. No matter how bad the SOFTWARE is corrupted the computer itself is left undamaged in terms of hardware.
I'm not saying that certain forms of malware can't affect hardware under bizarre circumstances but generally this seems to be an old wives tail. If you rewrite the Master Boot Record on Windows Re flash Firmware and completely format and reinstall Windows it WILL fix even the most complex malware ROOTKITS like tdl4 which installs itself to the MBR (Master Boot Record.)
Why can't you do the same thing on an Android phone? Lets pretend the system gets extremely corrupted from being root what keeps me from removing everything and completely re-installing android? I don't get how you can permanently brick your phone from a software issue alone no matter how corrupted the phone is?
Click to expand...
Click to collapse
bricked phone can unbrick using reinstall the firmware just like you say in windows
Vaibhav Chauhan said:
bricked phone can unbrick using reinstall the firmware just like you say in windows
Click to expand...
Click to collapse
That's what I was figuring. So basically the entire concept of permanently bricking your phone from rooting alone or messing things up as root is essentially a spooky incorrect nonsense tale spread around the internet?
ableright said:
That's what I was figuring. So basically the entire concept of permanently bricking your phone from rooting alone or messing things up as root is essentially a spooky incorrect nonsense tale spread around the internet?
Click to expand...
Click to collapse
rooting is not process of brick your device .it gives access the phone as super user.it just install su bin in system/bin folder
Vaibhav Chauhan said:
rooting is not process of brick your device .it gives access the phone as super user.it just install su bin in system/bin folder
Click to expand...
Click to collapse
No I know that friend (My phone is rooted right now) but what I don't understand is all these people saying things like they accidentally deleted xyz files or programs in root and now their phone is PERMANENTLY BRICKED.
I didn't think it was possible to permanently brick something like a phone from a software issue alone? What keeps them from re-flashing the device?
ableright said:
No I know that friend (My phone is rooted right now) but what I don't understand is all these people saying things like they accidentally deleted xyz files or programs in root and now their phone is PERMANENTLY BRICKED.
I didn't think it was possible to permanently brick something like a phone from a software issue alone? What keeps them from re-flashing the device?
Click to expand...
Click to collapse
Half the time people don't know what rooting is, they just know that they want it to install and show off 'cool' root apps. Attribute it to lack of knowledge, not reading the instructions first or following the instructions religiously or, in case they mess up their phone, not wanting to search for a solution which most likely would already have been posted by someone somewhere.
I've messed up my old Motorola Defy more times than I'd like to admit - so often that I uploded a copy of all the required files on my SD card and on the cloud so that I could access it anywhere - but following the instructions posted online helped me revert to stock with no hassles.
PhaseBeta said:
Half the time people don't know what rooting is, they just know that they want it to install and show off 'cool' root apps. Attribute it to lack of knowledge, not reading the instructions first or following the instructions religiously or, in case they mess up their phone, not wanting to search for a solution which most likely would already have been posted by someone somewhere.
I've messed up my old Motorola Defy more times than I'd like to admit - so often that I uploded a copy of all the required files on my SD card and on the cloud so that I could access it anywhere - but following the instructions posted online helped me revert to stock with no hassles.
Click to expand...
Click to collapse
if you delete basic system app you will go to the boot loops but if you got hardbrick during flashing rom then it ia difficult to unbrick your device.it occurs when you remove battery while flashing is running
Vaibhav Chauhan said:
if you delete basic system app you will go to the boot loops but if you got hardbrick during flashing rom then it ia difficult to unbrick your device.it occurs when you remove battery while flashing is running
Click to expand...
Click to collapse
But that's still a software issue correct? Therefore in theory it should be fixable am I right?
ableright said:
But that's still a software issue correct? Therefore in theory it should be fixable am I right?
Click to expand...
Click to collapse
It depends. Software needs hardware to work and hardware needs software. It matters what part of software you mess. You get a permanent brick when you are ****ing the bootloader. Then you get your hard brick. Think of the bootloader like the bios of your computer. The bootloader is the boss. If you mess the bootloader you can't enter recovery and so on. So game over. But yeah when rooting you can delete some system files that are checked by the bootloader and get a secure boot fail or a bootloop. If you have the Stock Rom you can flash that if not then you are soft bricked but still can't fix the soft brick.
HIT THANKS if i helped you.
ableright said:
But that's still a software issue correct? Therefore in theory it should be fixable am I right?
Click to expand...
Click to collapse
yes it is fixable
it on bricked permanently when device hardware will damage
Vaibhav Chauhan said:
yes it is fixable
it on bricked permanently when device hardware will damage
Click to expand...
Click to collapse
That's what I figured. It seems to a large degree then that these anti rooting people are mostly silly
ableright said:
That's what I figured. It seems to a large degree then that these anti rooting people are mostly silly
Click to expand...
Click to collapse
but really you want to brick your phone?
there are also one click brick tool for bricking your phone
Vaibhav Chauhan said:
but really you want to brick your phone?
there are also one click brick tool for bricking your phone
Click to expand...
Click to collapse
No I don't want to brick my phone I was just curious if there was something I didn't know in terms of software somehow causing your phone to permanently brick in a way that couldn't be fixed and it appears from what I've heard from you guys on here that that is not possible and that's a good thing.
ableright said:
No I don't want to brick my phone I was just curious if there was something I didn't know in terms of software somehow causing your phone to permanently brick in a way that couldn't be fixed and it appears from what I've heard from you guys on here that that is not possible and that's a good thing.
Click to expand...
Click to collapse
there is one click brick tool available
after using it your device will be just a garbage
Vaibhav Chauhan said:
there is one click brick tool available
after using it your device will be just a garbage
Click to expand...
Click to collapse
So I guess that's my ultimate questions lets even say you use one of these 1 click brick tools there is still no possible way to fix your phone at that point? The hardware of the phone would remain unchanged so essentially it should be impossible to re-install the OS etc. and your phone would work again am I right?
ableright said:
So I guess that's my ultimate questions lets even say you use one of these 1 click brick tools there is still no possible way to fix your phone at that point? The hardware of the phone would remain unchanged so essentially it should be impossible to re-install the OS etc. and your phone would work again am I right?
Click to expand...
Click to collapse
i have't try it just read about it on xda
i don't want to brick my phone so i don't know it cause permanent brick or not
but this is the link
http://forum.xda-developers.com/showthread.php?t=2701969
Vaibhav Chauhan said:
i have't try it just read about it on xda
i don't want to brick my phone so i don't know it cause permanent brick or not
but this is the link
http://forum.xda-developers.com/showthread.php?t=2701969
Click to expand...
Click to collapse
I get your point on that lol I just wish I had a definitive answer on whether or not a software issue alone on android can permanently brick your phone in suck a way that you can't fix it and how scientifically that's possible as I find this interesting!
ableright said:
I get your point on that lol I just wish I had a definitive answer on whether or not a software issue alone on android can permanently brick your phone in suck a way that you can't fix it and how scientifically that's possible as I find this interesting!
Click to expand...
Click to collapse
:good:
[update 2] I just summarized a way to backup and restore (all based on other great DEV's work, just put in one place) your TS before your play with your TS here: http://forum.xda-developers.com/showthread.php?p=52820278#post52820278
Go check it if you plan to root your TS!
[update] With the help of cheahcl, I got the latest F/W for 4th List 1/8/2100. With the MTK SP_Flash_Tool, I was able to upload a corrected F/W for my TS and everything goes back to normal!
Thanks for cheahcl for his dump and Lokifish Marz for his All in one tools! You guys really saved my day! (and my TS).
A Quick summary: Do NOT use any method on XDA yet to root or change TWRP recovery! It seems the TS of 4th list is different in some way than the ones before which render most of stuffs here invalid. However, fear not to play around since now we have a way to go back to stock!
In my experience, I found that it's really difficult to truly brick a MTK based system. The system will just reject flashing at slightest sign that a F/W is not compatible. The only cache is you need to have the "correct" F/W specifically for your TS!
In my observation, OMate made changes between each delivery. For Example, the 4th list of 1/8/2100 is different in (At least F/W configuration) of the 3rd or earlier 1/8/2100.
------------------------below is my original story of what I tried and failed--------------------------
Just got mine (1/8/2100) 5 hrs ago! I am on the 4th list. The delivery in FAST!
The watch starts normally. I played with it for a while, than decided to root it, install TWRP and apply the security hack made by +Lokifish Marz
Now I have a brick! Just after 30 min I receive the watch!
<<Can anyone help me here?>>
First of all, in respecting to all great DEVs, I have NO intention to blame anyone else but myself. (I did this to my own watch!)
Second, I have been rooting Android since Cupcake day, so I am not a Noob... (or so I think...) I am very familiar with ADB/fastboot... and use almost daily.
So here is the guide to brick. If Anyone have any idea please help me out!
--------------------------------------------------------------------------------------------------
1st, I tried to use this tool to root+TWRP+scurity patch http://forum.xda-developers.com/showthread.php?t=2713183&page=2 knowing it's NOT tested against 1/8/2100. I just tried anyway... The script went with a lot of errors, it seems the script cannot locate correct files but still push the security patched files into the /system/app (and other places).
I turn on the watch, but it just stuck at boot logo (the orange "Truesmart" logo without animation)
Also, the Recovery is still stock, TWRP is no where to be seen.
Since ADB still works, I adb reboot couple times, pull the battery, let the watch run for 2hrs, etc... Nothing works. The watch just stuck at the boot logo.
Than I follow this thread http://forum.xda-developers.com/showthread.php?t=2641261 and http://forum.xda-developers.com/showthread.php?t=2641261 with Stock firmware downloaded from http://d-h.st/users/Lokifish Marz/?fld_id=30814#files (Omate_1-8_2100_TrueSmart_20140328.zip)
I installed all drivers, restarts my Win 7 (x86) pc (several times), and after several attempts the Flashtool just flash in the Firmware.
The Tools flash with a green Check mark, indicating everything is ok!
However the watch just become a brick after this....
Than this completed the brick process! Now the watch won't even turn on, when I try to use Flash tool again, it always say S_FT_ENABLE_DRAM_FAIL. Google this and you find it's due to flashing wrong F/W, but I don't know where went wrong!
Anyone else have same problem or it's just me? Anyone have solution?
You said everything...
You made mistake but that shouldn't be problem.
You soft brick it using wrong recovery image and root tool but as you said, you had adb and fastboot on - so if you know what are you doing and I see you know (except of that pary of flashing something that's not for your device .) you should be able to flash stock firmware back.
If you can flash another firmware, try with other firmware...
Don't know what else to say....
Omate build piece of sh*t and we'll all have problems with it...
It's very hard to differentiate devices.
All of them has same nr on mother boards and, as I said, we will all have problems with Omate and their TrueSh*t...
Sent from my C6903 using Tapatalk
funky0308 said:
You said everything...
You made mistake but that shouldn't be problem.
You soft brick it using wrong recovery image and root tool but as you said, you had adb and fastboot on - so if you know what are you doing and I see you know (except of that pary of flashing something that's not for your device .) you should be able to flash stock firmware back.
If you can flash another firmware, try with other firmware...
Don't know what else to say....
Omate build piece of sh*t and we'll all have problems with it...
It's very hard to differentiate devices.
All of them has same nr on mother boards and, as I said, we will all have problems with Omate and their TrueSh*t...
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
Ha! Very true! I think you are right! I believe Omate have many segmentation on their HW/SW, even with same model number.... A lot of things changes between versions which makes the "factory image" not compatible....
Anyone has the latest (4th list) 1/8/2100 TS who could dump their whole image for me would be helpful...
I would like to help you but mine is 2nd list and it's still on customs office...
Omate shipment experts, you just gotta love them....
Sent from my C6903 using Tapatalk
Not sure what to tell you on this. A board revision change is possible as the Omate_1-8_2100_TrueSmart_20140328.zip was from a 1/8 2100. I can't even test stuff anymore as I gave one to a tech student that's studying network and system security and the other four were stripped down, reworked into data gathering modules and then donated to near space projects.
Lokifish Marz said:
Not sure what to tell you on this. A board revision change is possible as the Omate_1-8_2100_TrueSmart_20140328.zip was from a 1/8 2100. I can't even test stuff anymore as I gave one to a tech student that's studying network and system security and the other four were stripped down, reworked into data gathering modules and then donated to near space projects.
Click to expand...
Click to collapse
Thanks Lokifish for your comment... Is there anyway to get a latest F/W? If you know anyone I could contact, please PM me... Thanks!
Anyone have yet received a 1/8/2100 on 4th list could PM me a Factory F/W dump?
I tried another XP PC with all steps checked and rechecked but still... No luck...
Teach me how to do a dump and I'll dump it for you. I was also looking how to backup my stock firmware before playing around, seeing as no one has our version of firmware uploaded for restore yet.
Also received mine yesterday and firmware version is 20140513, pretty damn recent.
You guys are going to have to help each other out on this one. I've already deleted 90% of any and all Android dev stuff from my personal file server and computer. This includes tools, guides and work going as far back as the original HTC Evo.
cheahcl said:
Teach me how to do a dump and I'll dump it for you. I was also looking how to backup my stock firmware before playing around, seeing as no one has our version of firmware uploaded for restore yet.
Also received mine yesterday and firmware version is 20140513, pretty damn recent.
Click to expand...
Click to collapse
Thanks a lot! First of all, Currently don't do anything posted on XDA yet since most of them will not work with this version of TS... (This is where I am now...)
First of all, please get all necessary tools directly from this post "All Tools" http://forum.xda-developers.com/showthread.php?t=2734687 (Do NOT download or install any other things there!)
Follow those steps: (modified from link above)
1. Download "All Tools"
2. Install Universal ADB Drivers (included in All Tools) <--If you already have ADB up and running, it's not necessarily, then.
3. Enable USB Debugging on watch
4. Launch MTKDroid Tools
5. Connect watch to PC
6. Please follow the instruction from here: http://www.chinaphonearena.com/foru...up-MTK6592-MTK6589-MTK6577-and-all-MTK-Phones
a. Skip everything above and just starts from "B) Open ADB prompt to begin communication with the phone" .
b. Don't worry about the recovery thing... TS comes with a recovery which is not locked and you can do everything this article said with only stock recovery. (also no busy box is needed, nor su since TS run everything in root!)
c. You could also refer to the video guide below for details
7. it's okay to just provide the file you got after finishing the step "C) Read back the ROM with MTK Droid Tools" I should be able to do the Step D) and after myself.
Thanks a lot for your help!
Lokifish Marz said:
You guys are going to have to help each other out on this one. I've already deleted 90% of any and all Android dev stuff from my personal file server and computer. This includes tools, guides and work going as far back as the original HTC Evo.
Click to expand...
Click to collapse
Dear Lokifish,
Could you please still keep those tools on the host servers so people can still access them? (Like "All tools", etc.) Please...... (I need a emoticon of a small kitten with big eyes here...)
Thanks!
ok will get it to tonight. about 6 hours time. cheers
lssong99 said:
Dear Lokifish,
Could you please still keep those tools on the host servers so people can still access them? (Like "All tools", etc.) Please...... (I need a emoticon of a small kitten with big eyes here...)
Thanks!
Click to expand...
Click to collapse
The space was given to me for free as a recognized developer and contributor. Seeing that I have left development completely, it is not right that I continue to use the services. So at the end of the week the files will be purged and I will ask the xda remove my developer and contributor status.
Lokifish Marz said:
The space was given to me for free as a recognized developer and contributor. Seeing that I have left development completely, it is not right that I continue to use the services. So at the end of the week the files will be purged and I will ask the xda remove my developer and contributor status.
Click to expand...
Click to collapse
Oh! I see the situation... In this case, may I have your permission to host those files somewhere (maybe by XDA moderator, or ...me?) so they could still be accessible?
I could feel your feeling on this fiasco. Must be quite frustrate experiences for you...
lssong99 said:
Oh! I see the situation... In this case, may I have your permission to host those files somewhere (maybe by XDA moderator, or ...me?) so they could still be accessible?
I could feel your feeling on this fiasco. Must be quite frustrate experiences for you...
Click to expand...
Click to collapse
https://dl.dropboxusercontent.com/u/25414599/!Files_to_FlashTool.rar
I've done step D as well, good to just flash it I guess.
Let me know if it worked, before I start messing about. I'm not good in all these stuff. Been flashing since HD2 days but still, just a tutorial follower, can probably count Linux commands I know with 1 hand.
cheahcl said:
https://dl.dropboxusercontent.com/u/25414599/!Files_to_FlashTool.rar
I've done step D as well, good to just flash it I guess.
Let me know if it worked, before I start messing about. I'm not good in all these stuff. Been flashing since HD2 days but still, just a tutorial follower, can probably count Linux commands I know with 1 hand.
Click to expand...
Click to collapse
Dear cheahcl,
Thank you soooo much for the image! I successfully restored my TS and now EVERYTHING GOES BACK TO NORMAL!
If you want to play around, please don't forge to back up your IMEI! since the MTK SP_Flash_Tool will wipe your IMEI!
Please follow this guide here: http://forum.xda-developers.com/showthread.php?t=2631953 under "IMEI Backup Procedure" before proceed anything dangerous!
After this, you are good to go! MTK is non-brickable (from what I learned for the past day... All you need is a corrected factory F/W!)
Thank you! Thank you! Thank you! Thank you! Thank you! Thank you!!
lssong99 said:
Dear cheahcl,
Thank you soooo much for the image! I successfully restored my TS and now EVERYTHING GOES BACK TO NORMAL!
If you want to play around, please don't forge to back up your IMEI! since the MTK SP_Flash_Tool will wipe your IMEI!
Please follow this guide here: http://forum.xda-developers.com/showthread.php?t=2631953 under "IMEI Backup Procedure" before proceed anything dangerous!
After this, you are good to go! MTK is non-brickable (from what I learned for the past day... All you need is a corrected factory F/W!)
Thank you! Thank you! Thank you! Thank you! Thank you! Thank you!!
Click to expand...
Click to collapse
don't sweat it, haha i needed to backup my original firmware as well anyways, seeing how scarce it is around here and all the weird discrepancies in HW/SW versions. good to know i can always fall back on this file. haha yeah i've also backed up my imei. time to play around and see.
cheers
Ive managed to get my brand new watch stuck in a bootloop after using framaRoot to root it. (I know, I know)
Now, I am able to boot into recovery mode or factory, and tried a factory reset. No luck, so i'm pretty sure the issue is in the /system partition.
Does anyone know if there are zip files somewhere that i can flash from recovery, to restore the system partition?
Device:
- 1GB / 8GB / 2100MHz Version
- Originally unrooted
- OUI 2.1
- Modem Ver: MOLY.WR8.W1315.MD.WG.MP.V4, 2013/08/14 18:16
- No other modifications besides the rooting (which did work already before I rebooted)
Spoetnicus said:
Ive managed to get my brand new watch stuck in a bootloop after using framaRoot to root it. (I know, I know)
Now, I am able to boot into recovery mode or factory, and tried a factory reset. No luck, so i'm pretty sure the issue is in the /system partition.
Does anyone know if there are zip files somewhere that i can flash from recovery, to restore the system partition?
Device:
- 1GB / 8GB / 2100MHz Version
- Originally unrooted
- OUI 2.1
- Modem Ver: MOLY.WR8.W1315.MD.WG.MP.V4, 2013/08/14 18:16
- No other modifications besides the rooting (which did work already before I rebooted)
Click to expand...
Click to collapse
The TS (or any MTK based system) does not use the usually "recovery backup/restore" way we familiar of, instead it goes the "special tool on PC backup/restore" method. You need ask people who receive their watch in around the same time as yours with same configuration to backup their watch FW with MTK tools than restore with said FW.
Basically what I had done in this thread!
Please follow my another guild to see how to do this...
http://forum.xda-developers.com/showthread.php?t=2758733
Sent from my HTC_One_max using XDA Premium HD app
lssong99 said:
The TS (or any MTK based system) does not use the usually "recovery backup/restore" way we familiar of, instead it goes the "special tool on PC backup/restore" method. You need ask people who receive their watch in around the same time as yours with same configuration to backup their watch FW with MTK tools than restore with said FW.
Basically what I had done in this thread!
Please follow my another guild to see how to do this...
http://forum.xda-developers.com/showthread.php?t=2758733
Sent from my HTC_One_max using XDA Premium HD app
Click to expand...
Click to collapse
Thanks!
Im pretty sure that I was on 'Omate_TrueSmart_20140513.103530_V2.0' before I bricked it, so that gives hope
I dont have it with me right now, but Ill try it as soon as I get back home on monday
Thanks again for the tutorials and reply
lssong99 said:
Please follow my another guild to see how to do this...
http://forum.xda-developers.com/showthread.php?t=2758733
Click to expand...
Click to collapse
HEY! It worked
I'm back at a functional Truesmart
Thank you soo much
And in case three smiley's aren't enough:
Also, quick note for other people bricking their phone, my issue (after I bricked it again), was that I used an app to change the density property, which broke the boot of the watch.
The app that broke my watch was: https://play.google.com/store/apps/details?id=com.birdapi.android.dpi
First off, I am sorry if this is the wrong section, but I figure anything can go in 'general'.
My phone is an LG g4 running h81110n and I am wondering if the exploits in this software version can be patched by LG without releasing an entirely new software update (whatever is the successor to 10n), or any manufacturer for instance, like Samsung or Sony? Will a root method made for a certain software version always work on a phone running that software version? I suppose this question is more about Android software versions in general than LG. It goes without saying I do not fully understand what exactly a software version is.
Also I have one other question about bricking. I tried installing a rooted 10h image using the "low effort" method provided by thecubed in july and it soft bricked my phone. I followed the instructions exactly so I assume it happened because I used a 10h image on my 10n phone (I fixed it by flashing a stock image back onto it). What I am wondering is if it is possible to hard brick my phone or brick it irreversibly using a method like this, even if I do everything correctly?
I am planning on trying again tonight with a rooted 10n image. I will give updates if you guys want them.