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
Last week I was given a new, boxed SGS2 model GT-I9100G, running ICS 4.0.4, purchased in China. Much of it I can use, after setting it to UK English. However, all the important high use apps. refer to the Chinese national equivalents, and it appears to be linked to the Chinese app. store. So, no Google, no YouTube, no Twitter, no FaceBook and so and none of the obvious European email providers etc.
My local service provider pointed me to a site, with the name androidauthority, as a way of (hopefully) installing a European version of ICS 4.0.4: However, as a new user I am prevented from giving a link to this location (!), so could I ask somebody here with the necessary knowledge to tell me if there is going to be a safe procedure for replacing the Chinese system in my phone with a European equivalent, with a reasonable chance of success?
The questions that come to mind are such things as:
1. This procedure does not appear to require me to have acquired root privileges. Can it work as 'non-root' user?
2. Is the handset as secure after the change as it was before?
3. How much of ICS is replaced by this procedure?
4. Does ICS imply a kernel too? Or is it just an operating system on top of the kernel. If the latter, won't the kernel need changing too, from a Chinese version to a European version?
5. If there is a black screen of death after this procedure, what should I do, in aditional to wailing, throwing myself on the ground or banging my head forcefully against a wall?
By the way, I have purposely held off putting any useful data on the handset before I have solved the language-version issue, so I don't have any back-up/recovery issues (do I?)
Having read a little on this forum, I notice that there does not seem to be a version of CF-root for my handset. 'About phone' gives me a kernel version of 3.0.8-1067026. This version name doesn't seem to match any of those in the list of downloads elsewhere on this forum - it contains no alpha characters for example. 'About phone' also tells me that I have something called 'Baseband Version' - identified as I9100GZCLPL. What is this?
greatbridge said:
Last week I was given a new, boxed SGS2 model GT-I9100G, running ICS 4.0.4, purchased in China. Much of it I can use, after setting it to UK English. However, all the important high use apps. refer to the Chinese national equivalents, and it appears to be linked to the Chinese app. store. So, no Google, no YouTube, no Twitter, no FaceBook and so and none of the obvious European email providers etc.
My local service provider pointed me to a site, with the name androidauthority, as a way of (hopefully) installing a European version of ICS 4.0.4: However, as a new user I am prevented from giving a link to this location (!), so could I ask somebody here with the necessary knowledge to tell me if there is going to be a safe procedure for replacing the Chinese system in my phone with a European equivalent, with a reasonable chance of success?
The questions that come to mind are such things as:
1. This procedure does not appear to require me to have acquired root privileges. Can it work as 'non-root' user?
2. Is the handset as secure after the change as it was before?
3. How much of ICS is replaced by this procedure?
4. Does ICS imply a kernel too? Or is it just an operating system on top of the kernel. If the latter, won't the kernel need changing too, from a Chinese version to a European version?
5. If there is a black screen of death after this procedure, what should I do, in aditional to wailing, throwing myself on the ground or banging my head forcefully against a wall?
By the way, I have purposely held off putting any useful data on the handset before I have solved the language-version issue, so I don't have any back-up/recovery issues (do I?)
Having read a little on this forum, I notice that there does not seem to be a version of CF-root for my handset. 'About phone' gives me a kernel version of 3.0.8-1067026. This version name doesn't seem to match any of those in the list of downloads elsewhere on this forum - it contains no alpha characters for example. 'About phone' also tells me that I have something called 'Baseband Version' - identified as I9100GZCLPL. What is this?
Click to expand...
Click to collapse
Okay, here we go:
0) You really should check if your device is authentic. You are mentioning apps restrictions (In the about the phone section tag, does it says "Android Version 4.0.4"?) and apps country related (might be chinase carrier bloatware).
1) You can flash a new ROM (Euro Version for example) via Odin (no Root) or via CWM (Root required).
2) Flashing is all about changing operating systems, If you choose the right ROM for YOUR device, and you FOLLOW instructions given, it's safe.
3) ICS versions comes in 2 ways, Branded (Carrier Bloatware) & Unbranded (No carrier bloatware).
4) ICS package comes with ROM, Modem and Kernel. You can look it up each of them so you'll get familiar with these terms.
5) Don't think about that, should be fine.
6) No worrys about data, this is a system flash, not a SD Card flash.
7) You can follow many guides here on XDA to root your device.
8) Baseband is related to Modem. Network for your country / region.
And most importantly, make sure anything u flash is for the I9100G and not the I9100.
Sent from my GT-I9100 using Tapatalk 2
Hayth said:
And most importantly, make sure anything u flash is for the I9100G and not the I9100.
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
True + Read about Brick Bug (4.0.4) kernel.
gastonw said:
Okay, here we go:
0) You really should check if your device is authentic. You are mentioning apps restrictions (In the about the phone section tag, does it says "Android Version 4.0.4"?) and apps country related (might be chinase carrier bloatware).
1) You can flash a new ROM (Euro Version for example) via Odin (no Root) or via CWM (Root required).
2) Flashing is all about changing operating systems, If you choose the right ROM for YOUR device, and you FOLLOW instructions given, it's safe.
3) ICS versions comes in 2 ways, Branded (Carrier Bloatware) & Unbranded (No carrier bloatware).
4) ICS package comes with ROM, Modem and Kernel. You can look it up each of them so you'll get familiar with these terms.
5) Don't think about that, should be fine.
6) No worrys about data, this is a system flash, not a SD Card flash.
7) You can follow many guides here on XDA to root your device.
8) Baseband is related to Modem. Network for your country / region.
Click to expand...
Click to collapse
Great, thanks for this detailed reply.
From what I write here you will conclude that I am totally uninformed and (naturally) would be a little impatient. I would ask your indulgence. The fact is that I am totally uninformed - about things mobile - but I have been messing around with technology since 1959, (yes, that's 1959), especially with Linux installs and updates since about 2003. Being exceptionally outdated, I am exceptionally diligent at following instructions, so I have read your guidance in detail. Ignorance-driven questions arise:
As far as I can reasonably tell the device is not a fake - packaging style and contents, reputation of supplier, functionality of the phone all appear to be authentic (but what do I know?), This begs the question: what is a water-tight test of authenticity? The (non Samsung) apps. on the device appear to be only the Chinese national equivalents of those US/European ones which I expected: Weibo, QQ, YouKou, Baidu, RenRen - with, perhaps the stuff from TenCent which is admittedly bloatware, It does indeed say (in 'About phone') Android 4.0.4.
From elsewhere (sorry, cannot identify from browser history where) I found a list of all the ROMs(?) currently 'current' for the GT-I9100G. which seemed to link my system to ChinaUnicom, However it doesn't seem to be locked to that service provider because I was able to make phone calls with SIMs from both O2 and Giff-Gaff (which is really O2) installed in the handset. There was no SIM in the handset when I received it.
a). How do I identify the 'correct' ROM - seeing as the one I have is 'incorrect' in the sense that it is not what I want and therefore isn't much of a guide to me in identifying the correct one! I assume here correctness is synonymous with handset model number being fully and unambiguously identified. Yes?
b). Where do I download an unbranded, unbloated, version of ICS 4.0.4? I have downloaded a 380MB file (following instructions on the Androidauthority website that I am not permitted to mention <sigh>) named I9100GXXLPY_I9100GDBTLP3_DBT.zip - does this look like an unbranded ROM of approximately the correct size and naming convention?
c). Is it necessary to root the device (I was planning to use Odin, which I have downloaded)? In my naive state I associate a system in which the user has root privileges as being about as secure as Windows 2000 - i.e. a welcome destination for every hacker and psycho in the world. Is this correct? If so, why would I ever want to run with a 'rooted' handset, give the remarkable growth in the number of malware and the number of ways of 'acquiring' them? Thus, I was hoping to be able to make this change without having to 'root' the device. (btw did anybody from Oz ever point out what the commonly understood meaning of that word is? It surprised me to see it in common use!)
I look forward to your continued advice. Thanks again.
Hayth said:
And most importantly, make sure anything u flash is for the I9100G and not the I9100.
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Yes, I think I have realised that. The G version has quite different hardware (main processor and graphics processor) than the non-G version. I would expect a 'black screen of death' if using the wring ROM. But is there some naming convention in the ROM which will, without doubt, identify its intended hardware target?
greatbridge said:
Great, thanks for this detailed reply.
From what I write here you will conclude that I am totally uninformed and (naturally) would be a little impatient. I would ask your indulgence. The fact is that I am totally uninformed - about things mobile - but I have been messing around with technology since 1959, (yes, that's 1959), especially with Linux installs and updates since about 2003. Being exceptionally outdated, I am exceptionally diligent at following instructions, so I have read your guidance in detail. Ignorance-driven questions arise:
As far as I can reasonably tell the device is not a fake - packaging style and contents, reputation of supplier, functionality of the phone all appear to be authentic (but what do I know?), This begs the question: what is a water-tight test of authenticity? The (non Samsung) apps. on the device appear to be only the Chinese national equivalents of those US/European ones which I expected: Weibo, QQ, YouKou, Baidu, RenRen - with, perhaps the stuff from TenCent which is admittedly bloatware, It does indeed say (in 'About phone') Android 4.0.4.
From elsewhere (sorry, cannot identify from browser history where) I found a list of all the ROMs(?) currently 'current' for the GT-I9100G. which seemed to link my system to ChinaUnicom, However it doesn't seem to be locked to that service provider because I was able to make phone calls with SIMs from both O2 and Giff-Gaff (which is really O2) installed in the handset. There was no SIM in the handset when I received it.
a). How do I identify the 'correct' ROM - seeing as the one I have is 'incorrect' in the sense that it is not what I want and therefore isn't much of a guide to me in identifying the correct one! I assume here correctness is synonymous with handset model number being fully and unambiguously identified. Yes?
b). Where do I download an unbranded, unbloated, version of ICS 4.0.4? I have downloaded a 380MB file (following instructions on the Androidauthority website that I am not permitted to mention <sigh>) named I9100GXXLPY_I9100GDBTLP3_DBT.zip - does this look like an unbranded ROM of approximately the correct size and naming convention?
c). Is it necessary to root the device (I was planning to use Odin, which I have downloaded)? In my naive state I associate a system in which the user has root privileges as being about as secure as Windows 2000 - i.e. a welcome destination for every hacker and psycho in the world. Is this correct? If so, why would I ever want to run with a 'rooted' handset, give the remarkable growth in the number of malware and the number of ways of 'acquiring' them? Thus, I was hoping to be able to make this change without having to 'root' the device. (btw did anybody from Oz ever point out what the commonly understood meaning of that word is? It surprised me to see it in common use!)
I look forward to your continued advice. Thanks again.
Click to expand...
Click to collapse
Looks like you are already getting the hang of it.
First off, here's some reading material:
Index Guide.
Here you will learn about the infamus brick bug (Everyone on 4.0.4 should be aware of this).
Here you will see what NOT to do, because these guys already did and went bad. It's about how to get it back, so you'll get to know some interesting process.
About Root, you got this guy.
Worried about possible exploits, see what the Android Main Man did.
About some Root Humour, you got this.
If you are root sold, here's how you do it (I9100G Version).
Sammobile.com has got plenty of branded and unbranded ROMs for you to choose from (remember that crazy G at the end!).
About that fake remark, here's an example.
I guess I'm not forgetting anything....if I did, well, I'll notice it
gastonw said:
True + Read about Brick Bug (4.0.4) kernel.
Click to expand...
Click to collapse
I tried searching on this term in Google. It referred me to
http://forum.xda-developers.com/showthread.php?t=1897295
in which I learn that if I flash my handset with kernel 4.0.4, when that kernel is already installed (as it is on my handset), then I will be certain to have a bricked kernel. So, is this another way of saying that a solution to my original problem is not available?
Here's some additional info on your device:
Custom Roms & Kernels for I9100G.
Switch Between Chinease & International.
Here is something abour porting, whatever that is
gastonw said:
Looks like you are already getting the hang of it.
First off, here's some reading material:
Index Guide.
Here you will learn about the infamus brick bug (Everyone on 4.0.4 should be aware of this).
Here you will see what NOT to do, because these guys already did and went bad. It's about how to get it back, so you'll get to know some interesting process.
About Root, you got this guy.
Worried about possible exploits, see what the Android Main Man did.
About some Root Humour, you got this.
If you are root sold, here's how you do it (I9100G Version).
Sammobile.com has got plenty of branded and unbranded ROMs for you to choose from (remember that crazy G at the end!).
About that fake remark, here's an example.
I guess I'm not forgetting anything....if I did, well, I'll notice it
Click to expand...
Click to collapse
Wow, I find myself overwhelmed by all this information.
You know, all I really want to do is change the operating system language version, so that it makes my handset look like one that was purchased in UK/Europe, and that avoid a costly embarrassment. (The person who gave me the phone is waiting for me to use it...)
To refer to a Linux desk-top analogy, I want to replace Ubuntu 12.04 , simplified Chinese version, with Ubuntu 12.04 UK English version. I don't want to change my Linux kernel version, there's no need to when I'm not changing the version of Ubuntu and anyway too new = too risky; too old = inadequate hardware support. I don't want to change my ROM: I've got no hardware errors or bugs in my ROM which are directly responsible for functional limitations which affect my use of the phone - the 3 'dead' motherboards in my cupboard here are proof that ROM flashing is not without its risks.
So, conceptually, I want to try to do something straight forward. In the desktop scenario I would just download the correct level & version of Ubuntu from a Canonical server and install it. End of task. But in this mobile scenario I'm told about flashing ROMs, secure and insecure kernels, asked to choose whether or not to root the phone, asking to locate and choose 'firmware' (what ever that is, in this contex)t and also told that that the update is bound to fail, rendering my phone unusable.
That's all a very daunting story, which at the least requires me to embark on a serious and in-depth re-education program. That's a bit of challenge for somebody into their 7th decade, when all they want to do is use a phone.
Isn't there a simpler, more straightforward way of doing this?
Trust me, this isn't as hard as its sounds. And I'm also sure that in one week you will be sticking your teeth into the flashing & rooting world.
As you already are a Linux user, you'll find this OS very similar, because it's based on it.
Once you realize everything you can do with that little guy sittin right next to you, yoo'll be up for a thrill, regardless of your age or whatever.
You can start by Internationalization here.
gastonw said:
Trust me, this isn't as hard as its sounds. And I'm also sure that in one week you will be sticking your teeth into the flashing & rooting world.
As you already are a Linux user, you'll find this OS very similar, because it's based on it.
Once you realize everything you can do with that little guy sittin right next to you, yoo'll be up for a thrill, regardless of your age or whatever.
You can start by Internationalization here.
Click to expand...
Click to collapse
Yes, that is indeed where I want to start, so I really appreciate this link.
My first step in education is to be able to correctly interpret the English that is being used - I'm from a different age & universe, so some of the expressions in the linked article are confusing to me. The guide appears to be written from the assumption that the target audience is the uninformed user (like myself) but then invites the reader to 'use any stock ROM you choose' which implies a level of knowledge (about what a 'stock ROM' is, which ones are appropriate and where to find them) that is wholly inconsistent with the assumption. If I new all that stuff already, I wouldn't need the guide!. As it is the guide is great - but leaves me hanging in the air while I research the missing - and key - chapter.
Ah, well, never a dull moment; pity I have so few of them left (moments, that is)
gastonw said:
Trust me, this isn't as hard as its sounds. And I'm also sure that in one week you will be sticking your teeth into the flashing & rooting world.
As you already are a Linux user, you'll find this OS very similar, because it's based on it.
Once you realize everything you can do with that little guy sittin right next to you, yoo'll be up for a thrill, regardless of your age or whatever.
You can start by Internationalization here.
Click to expand...
Click to collapse
Damn it, this is so frustrating: none of the links available directly or indirectly in the article you have directed me to identify a suitable ICS firmware for United Kingdom. However, the threads that are referenced obviously are started by people with inappropriate knowledge, but - frustratingly - lacking the necessary credibility I am not allowed to post to those threads to ask.
The primary article has the same issue:I would like to post a reply to this method of internationalization by asking for an interpretation of the expression '- Manual Load Driver for OMAP4430 From usb_drv_windows folder (included in download content )' - 'manual load'? Load what from where into what? What is this download content? I don't have any 'download content'
Next frustration is my attempts to get Samsung USB drivers. EVERY site I have tried says words to the effect that this file has been deleted because too many people have requested it - or it points me back to XDA in an area I am not allowed access to - or it points me to the singularly ineffective (in my experience) SAMWARE site, which does not list anything, irrespective of language, for the I9100G.
Yep - it's truly like the Linux world: frustrating in the extreme, full of dead ends and self-referential logic, notable for its disciple (in the sense of the total lack thereof), wondrously chaotic and - by simple observation - very effective. But not for me.
Lol, think of it as a marriage.
D.L. mode (you probably screwed up and you gotta turn the balance to your side)
Recovery Mode (now YOU did screw up)
Flash (show off)
wipe (start from scratch, now on your feet)
Stock (this is who I married, now I just gotta hang in here)
Custom (An affair)
Brick ("Honey, we need to talk")
gastonw said:
Trust me, this isn't as hard as its sounds. And I'm also sure that in one week you will be sticking your teeth into the flashing & rooting world.
As you already are a Linux user, you'll find this OS very similar, because it's based on it.
Once you realize everything you can do with that little guy sittin right next to you, yoo'll be up for a thrill, regardless of your age or whatever.
You can start by Internationalization here.
Click to expand...
Click to collapse
Well, it's more than a week - and I still have not been able to locate the right firmware to download, or a process for using it that can be followed.
I did invoke Samsung UK Technical support. They directed me to a service agent - a 6 hour round trip plus waiting time. This 'service agent' announced that it would take 'more than 2 hours' to download the firmware, then advised me that the attempt to flash my phone failed at the point of loading the PIT. He refused to tell me what firmware load he had tried and refused to return the phone unless I paid a service charge. At this time Samsung haven't responded to my complaint about this con-trick.
Got any advice on where else I might go to get this fixed?
gastonw said:
Lol, think of it as a marriage.
D.L. mode (you probably screwed up and you gotta turn the balance to your side)
Recovery Mode (now YOU did screw up)
Flash (show off)
wipe (start from scratch, now on your feet)
Stock (this is who I married, now I just gotta hang in here)
Custom (An affair)
Brick ("Honey, we need to talk")
Click to expand...
Click to collapse
Huh?
greatbridge said:
Huh?
Click to expand...
Click to collapse
analogys
gastonw said:
analogys
Click to expand...
Click to collapse
This dialogue has not made one word of sense to me; I'm clearly in the wrong time or place, or both.
Can somebody point me to the exit so I can come in again, and ask for some guidance on how to get my phone updated?
alt + f4?
Sent from the little guy
The g model doesnt have a Uk rom because the phone isnt meant for here.
You can see what custom firmware is available.
"noob ok...lazy noob not ok"
Hi there!
I have been searching and reading tons of post in xda-developers and I feel I'm ready to ask since I haven't found what I need.
In short: I want to root my I9100 WITHOUT FLASHING ANYTHING and later return to my official legally supported vanilla non-rooted immaculate guaranteed configuration.
My mobile is Samsung Galaxy S II (model GT-I9100), with:
Android version: 4.1.2
Baseband version: I9100UHMS1
Kernel version: 3.0.31-914166 [email protected] #3
Build number: JZO54K.I9100UHMS8
Product code: GT-I9100LKLCHE
External microSD card: 32GB
I guess the important things are the JellyBean 4.1.2 and the "MS1/MS8" version.
I already tried SuperOneClick v2.3.3. Sadly it turns not-responding at step #7. I did read that "psneuter exploit" could make it work instead; however, it didn't (it turn not-responding at step #5).
All other threads in xda-developers mention the word "flash" in the process and it terrifies me.
Hence, could you please lead me to a proper guide, or draft a recipe for me? (I don't care if the process is tedious and hard)
Thanks in advance,
Turritopsis Nutricula (the immortal Jelly...Fish)
As far as I know using methods like superoneclick or CF-Root causes the yellow triangle at the bootscreen. This can be deleted by a simply programme, but you take a risk that something might go wrong. The only thing I've seen that shouldn't make flash counter go up is flashing Philz kernel. I know you wanted the way without flashing but there's nothing scary.I was worried too when I was rooting my phone this way(even if my chip was sane) but all went good. Then I've made the same thing on my friend's s2 and this time his chip was insane.Everything went fine. I would suggest this way of rooting phone because it's the easiest and the safest method out there in my opinion.
Turritopsis said:
In short: I want to root my I9100 WITHOUT FLASHING ANYTHING and later return to my official legally supported vanilla non-rooted immaculate guaranteed configuration.
Click to expand...
Click to collapse
Here's a quote that comes to my mind:
“You Can't Cross a River Without Getting Wet”
To be frank, I feel flashing is more safer than using a toolkit, because you know exactly what and how you're flashing. :good:
And it doesn't make a difference which method you choose as long as you can unroot it and return to stock (which is probably the reason you are afraid to flash).
So, I suggest you check this thread out, or flash Philz kernel.
My device. Only had it a week. Been reading more on here that I've actually tried to use the fone, cause the first thing I discover is it's "broken" (which means it works the way "THEY" want it to, not how *I* like it to) ... Am on Verizon based pageplus carrier, don't need any verizon anything I don't think it'll get OTA updates (but need to be sure about that)
Code:
Product Manufacturer: samsung
Product Model: SCH-I605
Model ID:
Device Type: t0ltevzw
Device Characteristics: verizon
Product Serial Number: 42f76dxxxxxxxxxx
Build Description: t0ltevzw-user 4.4.2 KOT49H I605VRUFND7 release-keys
Build Date: Thu May 8 01:25:12 KST 2014
Hardware: smdk4x12
Board Platform: exynos4
Build Version Release: 4.4.2
Build ID: KOT49H
Bootloader: I605VRUFND7
Build PDA: I605VRUFND7
CSC Sales Code: VZW
Region Code: US
Ro.secure Level: 1
Ro.adb.secure Level: 1
Selinux.enforce Level: 1
Selinux Level: 1
Question 1: Got a 32 gig class 10 Sdcard for it, do I format that ext4 (like the rest of my linux?) Or ??? I have heard people unsing fat32 but .... Just tell me what works & by what means (program CLI whatever, w32 or Linux, just whatever THIS phone likes best)
Question 2: Need to totally back the whole thing up before I try to tame this poor beast. Have both odin (all the flavors I could find) and heimdall. would be wise if I could extract not just the whole "blob" but also radio, system, etc so forth (I have found a Pic file)
how to . Yes I've looked.
Question 3: Odin or Heimdall? Or Jodin? I've tried turning the innernetz upside down to find some kinda .chm or .pdf for this Odin thing, nuthin.... I've seen a few good general guides but nothing explaining it's function. Ditto for Heimdall, but atleast I can look at the comments in the code on the Github .... Of these tools, which is best documented / most reliably EFFECTIVE / best supported?
Question 4: Obviously my phone is broken because it was boot-raped when previous owner took 4.4.2 It appears (?) there are very limitted options to getting it 1/2ways usable (but not really RESTORED) with Ghetto-root and Safestrap, I have some access to the phone and can use only some ROMS? No Cyanogen-mod? Losts of warnings in colored boxes, but they say use Heimdal.... Other things I've read says this wont work.... nothing clear on their side.
I need to know how to back the poor thing up first, and get the memory card working before I even try Ghettoroot and safestrap (I already tried GR and failed, and thought, dumbass better make a backup before going any further)
THANK YOU IN ADVANCE
Qestion 1: I usually use the phone to format the SD card. That's the surefire way to make sure that your phone and computer will read the card.
Question 2: I use Odin to flash stock ROM, but haven't tried Heimdall yet, but heard good things. If the devs in this forum say there's no way to unlock the bootloader on a 4.4.2 SCH-I605 yet, I believe them. Don't try anything else unless you know how to unbrick it yet.
Question 3: Just format your memory card and try the ghettoroot like I did. I have Safestrap running as well, and am going to try to flash some modified 4.4.2 ROMs today. I'll post something later indicating my result.
Question 4: Your phone isn't broken, just stock.
It's hard for me to justify asking for too much help with this hardware, considering it's age. I'm late to the root game, but have some good tech knowhow, so I would recommend just trying things. Ghettoroot the phone and get that to work, then flash the stock rom back just for practice with Odin. Then ghettoroot again and install Safestrap, and make a backup onto your external SD Card, so if you run into any problems you can re-flash that using safestrap and get back to normal.
Soft bricks can be fixed with Odin. But hard bricks are tougher to fix (Opening the device and shorting a resistor sounds like it would be fun to try, but I don't really want to risk that with my daily driver phone unless I absolutely have to). I learn by practice, and if it wasn't for this site I wouldn't know crap. Much thanks to the devs and all people with their questions and answers that have taken me this far! And, we'll see if when the SDK comes out for 5.0 lolipop if anyone wants to crack it for the Verizon Note 2. Hopefully they do, cause I'm learning programming, but I'm nowhere near that far yet!
Thank you thank you
Hellstorm32 said:
Question 4: Your phone isn't broken, just stock.
Click to expand...
Click to collapse
:cyclops::cyclops: I know..... "they" broke it to keep me from breaking it myself... but I bought it, I paid for it, I will suffer the consequenses and how will I ever learn anything if I don't break it a few times? "they" do not encourage learning... THEY ENCOURAGE BUYING... my phone is full of Amazon and Verizon and NFL for God's sake and I can't use an addblocker without root!
Hellstorm32 said:
It's hard for me to justify asking for too much help with this hardware, considering it's age. I'm late to the root game, but have some good tech knowhow, so I would recommend just trying things. ....
Click to expand...
Click to collapse
It's (to me the annoying noob) utterly justifiable to ask for help. The phone is old enough it's no longer under contract and is now available to purchase for cash (I only draw $700 month in disability, I could not afford these new jewelry phones)
Furthermore the phone is old enough that plenty of people smarter than me have had LOTS MORE TIME to really get to understand whats going on with it, how to make it better etc....
Good Luck, I'm gonna format the card tonite
DEPRECATED
This firmware is old and deprecated.
See the below link for new firmware and a better root method.
https://forum.xda-developers.com/galaxy-s8/development/root-partcyborgrom-aqi6-deodexed-t3702988
You can just flash the BL_ tarball if you don't want to install a new system
but want the better screen and modem drivers.
PART 2: FIRMWARE RELOADED
I have done extensive research into the issues reported by those of you who are still experiencing screen issues.
I was unable to reproduce the screen issue on my then-current firmware with this update.
Not being content to leave people with buggy screens, I learned as much as I could about the s8 firmware.
This is what I did with that information.
Flashable Custom Firmware Package For ALL SM-G950U/U1 ON US CARRIERS
If you have a non-us G950U and want to install this pm me or ask in the thread and ill make one. Its very simple but I wanted to get this out to everyone else ASAP
NOTICE!
This an UPDATE (and More) to the Green/Garbled Screen Issue firmware.
There is NEW firmware to download below, and everyone who is rooted should read on, even if you installed the previous version.
Background
At the core of the issue with the garbled screen, modem panics, and sd card issues are two central themes: Bugs, and Incompatibilities. The S8 family of phones was fraught with issues early in its release, including the infamous "Red Tint', Fingerprint scanner malfunctions, mysteriously poor battery life, and surely a bunch of smaller others. Many of these bugs were caused by issues in the device's underlying firmware. Like most devices, Samsung has worked to fix these bugs and improve device performance throughout the phones lifetime for sale in public.
Root Bugs
The problem was unfortunately worse for users of one of the rooting methods for the S8. The biggest reason for this is that in order to relax security constraints enough to make rooting possible, a "non-user oriented", "factory" combination firmware was used. This firmware, being designed apparently for configuration/repair processes inside a factory, was not tuned to the normal level as the public firmware, likely did not go through the same testing, and ultimately any bugs unique to this "Combination" firmware that did not directly affect basic functionality or also stock were probably largely initially ignored.
This is where most of the issues that you all have had come from.
Finding a Solution
As I was unable to reproduce the issue on my device without resorting to the original firmware shipped out with the root method I used, I decided to think about what made my device different than the other devices reporting these issues. While sure we may have slightly varying hardware and that may contribute to these issues as well. What I am absolutely certain of is that most of us have different releases of software from each other. Not only have people essentially ad-hoc upgraded from the original firmware they rooted with until now, many have not upgraded at all or, only partially upgraded (such as with the pervious version of this).
While I could have simply packaged up my firmware/bootloader flashfire backup, I decided to take it a step further.
THE GOODS
Without further ado, I present to you:
S8Root Improved: A SM-G950U1 Custom Firmware Package for Root Users
This package contains a custom mix of the latest AQH3 STOCK (not combination) firmware used wherever possible with the Necessary boot/kernel images from the combination firmware necessary to keep root working with permissive SELinux. It contains all of the improvements from the previous version, and many more.
RESULTS
I can only speak for myself, but the results I experienced were amazing:
- Better UI Responsiveness.
Things surprise me how they move
- Sharper/brighter screen colors
I thought it couldn't get better than the last version but it has! Everything just looks crisper and are super bright without being oversaturated like with the Adaptie Mode.
- POSSIBLY Improved LTE network connectivity.
Note I said POSSIBLY. I personally regularly experienced 8-10Mb/s download bumps and 2-3Mb/s upload bumps in LTE while moving back and forth from this new firmware. I have my LTE radio locked to a specific channel (there are two i pick up at my place and one is terrible) and I carefully measured -107 to -112 dBm RSRP and -13 to -14 dB RSRQ prior to each measurement. I almost left this out but I figured it would be better to give you the information with no conclusion either way. It ABSOLUTELY could be Atmospheric changes, Traffic level changes, or any other of a million thins. YMMV
- Could POTENTIALLY still any remaining fix long-standing SDCard issues
I did not experience this, but had a few reports from users that did. The same pieces used in that version that would touch SDcard usage are used here, so that fix/improvement will carry over.
DISCLAIMER
Unfortunately proving beyond any shadow of a doubt that this package fixes the issue was impossible . I have TRIED AND TRIED AND TRIED to trigger the screen issues, including tweaking on and off every setting (auto brightness, multiple DPIs, different graphs modes, etc) I could get my hands on and it just was not happening. I used every software/systems trick I could think of to break this again, and I was completely unable to tickle the bug on this firmware, despite being able to reliably trigger it almost on command using my previous firmware.
The only thing left to do is either:
- Get the source from samsung, fix the bug myself, and get them to sign my new kernel image with their key so our locked bootloaders would allow it (HAHA I DOUBT IT)
- Acquire a large fleet of S8s (and S8+s) to run distributed integration testing (like the kind Android use at Google). Well if someone wants to buy me a few dozen s8s and s8+s (each) sure I'll take a month off work and squash this, but otherwise not gonna happen either.
If it STILL happens for you, I'm sorry.
I have done everything I can think of, and if it happens to you and you have suggestions, I'm all ears.
BUT HEY, but this is XDA right? Land of mods like Xposed which will brick one persons device and work flawlessly on the identical one next to it. And we love Xposed don't we?
Despite absolutely hilarious comments to the contrary, this package absolutely meets the (aka "BugFix") as well as just about any android update ever does, given the wide variety of environments, usecases and software configurations out there. I surely hope that this works for you.
Instructions
1) Download the package from the link above.
- Here it is Again for good measure.
2) Reboot into download mode and flash using Comsy Odin
Thats it! I packaged this in a way to make the process as smooth as possible.
There is NO reinstall, NO wipe of any kind, nor ANY further work on your part needed to install and use this.
The file size is small so the download is fast, and again, there is NO WIPE or config change needed.
if (for some inexplicable reason) you want to roll back, or go to 100% stock sans root, that process should not be made any more difficult as well.
Legacy Information
If you were here before and either looked at or downloaded the previous version, AND YOU HAVE NO QUESTIONS you can skip this part.
If you have questions, please read through to the end of the post before asking them, as I tried to answer as many as I could before hand and all of this information still applies.
WHAT IT IS NOT:
I wanted to outline a few things it is NOT about, to make a valliant effort to stem off the flow of questions before they begin (ha!):
NOT: A new Stock ROM for Your Phone
THIS IS NOT A FULL OS BUILD! DO NOT DOWNLOAD THE WHOLE THING AND FLASH IT EXPECTING AN ENTIRELY UPGRADED OS.
There is no full stock AQI1 image I have found. Believe me I looked a bunch of places after I found it
NOT: Oreo Early Preview
Given the predictions that the next release from Samsung would likely be Oreo, there was some initial over excitement. This wound up being NOT the case and if you read at least current Samsung Oreo projections they are predicting AQB now.
NOT: A Fix for the 80% Battery Issue
I know this is completely futile to hope for but:
THIS DOES NOT FIX THE 80% BATTERY ISSUE!!!!
NO WE DO NOT HAVE A FIX FOR THAT OR ONE COMING ANY TIME SOON!
YES SOME PEOPLE ARE STILL TRYING!
PLEASE DO NOT ASK! OFF TOPIC FOR THS THREAD
NOT: Currently Tested by ANYONE but ME
Since the moment I installed this I have not had ONE SINGLE screen issue, where previously I would have them several times throughout the day (at least 3 sometimes upwards of 6). For the case of ME and MY device, I am confident in declaring that this boot ROM does not have the same kernel bug that was causing the issue on the boot.img provided as part of your traditional root method.
NOTE: This is for the s8 G950 US Snapdragon models ONLY! Do NOT Flash this on your exynos, your Chinese/HK S8, your N8, your MOTO RAZR flip phone, whatever else you have. Kernels/boot.img files are very device specific and you will surely break it if not completely brick it.
DISCLAIMER:
YOUR WARRANTY IS ALREADY VOID if you are paying attention and are doing this to fix bugs with the existing sampwnd root.
HOWEVER IT IS EVEN VOIDER NOW. FLASH THUS TO YOUR DEVICE AT YOUR OWN RISK!
and if you break it I AM NOT RESPONSIBLE! FLASH AT YOUR OWN RISK!
As I said I have not tested this anywhere but my phone as I dont have any other s8s nor do I have access to any locally. I hope it works for you as well as it has for me.
STEPS
Download Boot Image
Use the URL here to Download the AQI1 boot.img file: Go Download the New Hotness
Prepare Phone for Flashing in FlashFire
If you did not download it on your phone, copy it somewhere FlashFire can see it.
Flash it
Open up FlashFire
Hit the "+" button
Select the "Flash Firmware Package" option, NOT the "Flash Zip or OTA" option!
You should see a popup window thing that has a checkbox next to the word BOOT, with "boot.img, 22MiB" underneath.
Make sure the checkbox is checked.
Make sure that it says BOOT above boot.img.
I have no idea if its possible for this to get messed up, but BOOT implies flashing the BOOT partition so if it says something else you are headed towards brick town, abort immediately.
Press the Check mark at the top right corner once you have confirmed the two things above.
MAKE SURE EVER ROOT IS DISABLED!!!
Click on the "Reboot" box, and choose "Recovery". MAKE SURE PRESERVE RECOVERY IS NOT CHECKED!
Back at the main menu, click the lightening bolt next to the word FLASH. Confirm.
Wait for FlashFire to do its thing. Sometimes it takes a minute for FF to wake up and start flashing. Occasionally for me it never happens, if this happens DO NOT PANIC ITS FINE. Hold down power+volDown until you eventually wind up in upload mode, then just reboot normally and everything will come back fine.
When FlashFire finishes (it will go really fast, the image is only 22MB we arent flashing a 5GB system here), it will auto-reboot your device into the recovery men
Select Wipe Cache and Confirm
This will wipe cache which is fine and safe. Again maybe not needed, feel free to skip if you know what you are doing. If you mess up and accidentally click factory reset instead, please tell me so I can laugh at you.
Reboot into a Clear New World
Select reboot and boot the system normally. If you formatted the cache partition above, it will take a little longer to start your phone. This is just the first time per normal.
Thats it! Welcome to the world of clear screens and bright colors. It could be a total placebo effect but I actually think this kernel drives the display better sometimes.
Please let me know what you think, and if this works for you. I wi;; be here for a while to answer questions or fix anything i typoed above or whatever.
FYI: A s8+ thread is coming too, as I sprung for purchasing both downloads to be an equal opportunity XDAer (at least with US flagship Samsung devices lol) but since I have an s8 and thus had the files locally already I made this one first
@jhofseth for nerding out with me the last few nights on trying crazy **** to get a bootloader unlock which prompted me to dig at this in the first place
Most of all, all of the tons of you who have made so many aewesome mods, themes, apps, what have you that I use every day and that make me enjoy my device all the more. I could not be happier to have the opportunity to give back a little.
Here is the restof the s8 combo firm if you are interested, but don't just flash this as its not a full OS:
EDIT: DOWNLOAD THE NEW ONE ABOVE
Can I Get The Link To The S8+ Boot im willing to try it
Mark805 said:
Can I Get The Link To The S8+ Boot im willing to try it
Click to expand...
Click to collapse
Coming very soon I promise! 10m max
Ok thanks
Mark805 said:
Can I Get The Link To The S8+ Boot im willing to try it
Click to expand...
Click to collapse
Its up now! https://forum.xda-developers.com/ga...sampwnd-root-green-screen-corruption-t3673815
whats the bootloader verison? it can be found by booting into download mode manually.
Cameron581 said:
whats the bootloader verison? it can be found by booting into download mode manually.
Click to expand...
Click to collapse
This isn't a bootloader change, it's boot.img which is the kernel and root filesystem essentially
Hey, btw this does not void warranty. I understand it's a standard disclaimer but it doesn't void it. It doesn't trip knox, so warranty is still very intact.
mweinbach said:
Hey, btw this does not void warranty. I understand it's a standard disclaimer but it doesn't void it. It doesn't trip knox, so warranty is still very intact.
Click to expand...
Click to collapse
Uh just because their service does not catch you does not mean that technically you are not violating your warranty contract thus making using technically illegal
That would be like saying "it's not murder if you leave no forensics!" Lol
wildermjs8 said:
Uh just because their service does not catch you does not mean that technically you are not violating your warranty contract thus making using technically illegal
That would be like saying "it's not murder if you leave no forensics!" Lol
Click to expand...
Click to collapse
i mean legally a warranty can not be void through software modifications unless it causes physical damage to the device. Since the efuse was not tripped no physical damage has been caused and no warranties have legally been void.
I had the green screen/graphics corruption after flashing this still...
goliath714 said:
I had the green screen/graphics corruption after flashing this still...
Click to expand...
Click to collapse
Apparently this happens to some people. I am fairly certain it is a firmware combination issue but I haven't been able to track it down. One thing you can do to eliminate it if you have the issue still (please let me know if this does not work) is to disable auto brightness.
wildermjs8 said:
Apparently this happens to some people. I am fairly certain it is a firmware combination issue but I haven't been able to track it down. One thing you can do to eliminate it if you have the issue still (please let me know if this does not work) is to disable auto brightness.
Click to expand...
Click to collapse
I have auto brightness off and still get it here and there.
goliath714 said:
I had the green screen/graphics corruption after flashing this still...
Click to expand...
Click to collapse
Please check out the OP again and download/flash the new version. Rather than just a few files, its a whole new entire bootloader/kernel package that I assembled piece by piece to have as much latest stock firmware as possible while maintaining what we need for root.
My primary suspect for why some people experience this regression is having older parts of their system. Rather than push everyone to upgrade, I made a painless upgrade process for all of their firmware instead
This includes the Radio drivers and bootloaders, kernels and flash layer libraries. Its all either latest stock or its AQI1 Combination because it was absolutely necessary.
wildermjs8 said:
Please check out the OP again and download/flash the new version. Rather than just a few files, its a whole new entire bootloader/kernel package that I assembled piece by piece to have as much latest stock firmware as possible while maintaining what we need for root.
My primary suspect for why some people experience this regression is having older parts of their system. Rather than push everyone to upgrade, I made a painless upgrade process for all of their firmware instead
This includes the Radio drivers and bootloaders, kernels and flash layer libraries. Its all either latest stock or its AQI1 Combination because it was absolutely necessary.
Click to expand...
Click to collapse
We flash the tar in the AP slot correct?
CloudyxVision13 said:
We flash the tar in the AP slot correct?
Click to expand...
Click to collapse
Yep
---------- Post added at 08:29 PM ---------- Previous post was at 08:28 PM ----------
Seems to be running better to me. Thanks bro
CloudyxVision13 said:
We flash the tar in the AP slot correct?
Click to expand...
Click to collapse
It actually does not matter, as Odin will do the right thing no matter what.
Sorry I should have made that clear. I will update the op to make that clear
Just wanna make sure of something. First, I flash the first download files through modded doin, then afterwards, flash the second file in ff?
AngelIsL33T said:
Just wanna make sure of something. First, I flash the first download files through modded doin, then afterwards, flash the second file in ff?
Click to expand...
Click to collapse
Nope, only need the tar file bud. The old boot.img file is just basically the previous version of this.
AngelIsL33T said:
Just wanna make sure of something. First, I flash the first download files through modded doin, then afterwards, flash the second file in ff?
Click to expand...
Click to collapse
The old image is actually part of the new tar, do you will have it anyway . I packaged it in Odin this time because there are some pieces of firmware FF either can't or warns against using it for. Plus one clean simple tar seemed easier, no?
Do you see the boot.img in the op? I thought I nixed all the instances of the link but I may have missed one.
I almost rewrote all the old text to reflect now but it felt like editing history so I tried to preserve what made the most sense still. It sounds like it's still a little confusing sobrskr another crack at it shortly.
Please let me know if you have any trouble! I'll be here to help all evening