Related
Hi everyone I'm pretty new to the whole Android world, I've read a lot of stuff through this forum and in general through the internet but I haven't got to the point of really understanding this clear.
I performed the rooting and sim unlocking following the guide on this forum, so basically I had to install the ClockworkMod Recovery.
I read that having installed a custom kernel (or rom, not clear the difference) or a custom recovery (or bootloader, like CWM in this case) voids the warranty.
I also read that is pretty simple to restore the stock kernel/firmware by simply flashing it on with Odin, but what about the Recovery?
I found this post http://forum.xda-developers.com/showthread.php?t=1286432&highlight=stock+bootloader my questions are:
1. Is having the phone flashed with stock kernel (but a different than the original recovery, e.g. CWM) enough to bring the phone back in warranty conditions?
2. flashing the stock unrooted kernel following the above thread will restore also the original android recovery console?
3 if not is there a way of getting rid of CWM and restoring the original android recovery? (I read "just flash it with odin like you did with CWM, but where do I find the package (image) to flash?)
4 the stock kernel in the post seems to me "not official" in the sense that has been ripped from a user, is there any chance that we (SGHI777) will get something more official like the international kernels (GTI9001) that you can find on samfirmware?
5 this is extra, if I have a rooted GS2 (following the forum procedure so CWM+original kernel) will I be able to install official update through Kies? (I'm asking cause the unlock security flaw bugs me a lot...)
Thank you very much to everyone that will answer.
frabass said:
Hi everyone I'm pretty new to the whole Android world, I've read a lot of stuff through this forum and in general through the internet but I haven't got to the point of really understanding this clear.
I performed the rooting and sim unlocking following the guide on this forum, so basically I had to install the ClockworkMod Recovery.
I read that having installed a custom kernel (or rom, not clear the difference) or a custom recovery (or bootloader, like CWM in this case) voids the warranty.
I also read that is pretty simple to restore the stock kernel/firmware by simply flashing it on with Odin, but what about the Recovery?
I found this post http://forum.xda-developers.com/showthread.php?t=1286432&highlight=stock+bootloader my questions are:
1. Is having the phone flashed with stock kernel (but a different than the original recovery, e.g. CWM) enough to bring the phone back in warranty conditions?
2. flashing the stock unrooted kernel following the above thread will restore also the original android recovery console?
3 if not is there a way of getting rid of CWM and restoring the original android recovery? (I read "just flash it with odin like you did with CWM, but where do I find the package (image) to flash?)
4 the stock kernel in the post seems to me "not official" in the sense that has been ripped from a user, is there any chance that we (SGHI777) will get something more official like the international kernels (GTI9001) that you can find on samfirmware?
5 this is extra, if I have a rooted GS2 (following the forum procedure so CWM+original kernel) will I be able to install official update through Kies? (I'm asking cause the unlock security flaw bugs me a lot...)
Thank you very much to everyone that will answer.
Click to expand...
Click to collapse
On nearly all Samsung phones, recovery is a part of the kernel. Flash a new kernel, you've flashed a new recovery.
The stock kernel zImage is as official as it gets - nothing is more official than what was actually flashed into the device by the manufacturer and sold on launch day. The additional evidence that it's official is that it passes the bootloader signing checks, eliminating the "custom kernel" warning screen.
We won't see a samfirmware release until AT&T releases an update.
Stock rooted shouldn't affect OTA updates, however sometimes things you do WITH root (such as debloating) will interfere with OTAs.
Once an OTA update becomes available, expect its fixes to be integrated into ROM releases fairly soon.
FYI there are three components you should know about. Kernel>ROM>Modem
The kernel It's the core/kernel of an operating system. It's main functions are to interact with the hardware a.k.a. Device Drivers, to manage resources (things like memory management and processor time sharing a.k.a. multi-tasking), service interrupt requests, network services and the like. It also provides a System Call Interface (API) to the user space (apps running on the machine) so the apps can use system resources.
Now the why so many part... First of all in general there are MANY options available when compiling (building) the kernel. Things like CPU schedulers, file system support, system type support, etc. etc. etc. So there are many different ways to configure the kernel and that gives many options to "test" and see which might work better or not. Some of them are dead giveaways like compiling the kernel for MIPS and trying to run it on the SGS2 won't work but some are "tweaks" that may help a little or a lot, like CPU management options.
Second part of the why so many is the code. Again as mentioned above things like changing code to make the colors of the display more or less sharp (display device driver), make the file system faster (voodoo lag fix) or overclocking the processor, and different "modem" tweaks are all "enhancements" that people have made to the original Linux kernel source. So those things "creep" into existence over time, since there are many people working on them, and you see different versions of the Kernel from that as well.
Anyone that plays music can relate to the options available in that there are only 12 notes on a guitar fret board but millions (or more) ways to put them together to play music. There are certain things that have to be present in the Kernel (notes) but writing code to enhance them and/or combining options at compile time is much broader (music).
The ROM. ROM is actually Random Access Memory and we flash an image to the "ROM" (which it really isn't but I'll leave that one alone). The "ROM" in this case is the operating system (a version of embedded Linux), which is the basic software needed to run and admin the phone, things like the Kernel, bootloader, device drivers, and file system plus any user apps like the phone dialer, launcher, etc. that are included in the ROM. As you can imagine the possibilities of customization are almost endless when it comes to the ROM. Different kernels, different drivers, different apps and many combinations of those.
The modem is actually part of the kernel. It's the device driver for the phone hardware. Being that it's part of the kernel it "works with" other code that's elsewhere in the kernel and ROM that is "tweaked" for a particular phone in this case. So when you see "use an i777 modem with an i777 kernel" it's because the code in the modem is written to work with the other code in the kernel. It doesn't necessarily mean it will brick the phone and/or not work but it quite often means it won't work the best if it's not "matched".
Actually the modem is NOT part of the kernel. The modem firmware runs on an entirely separate processor (not one of the main application cores.) - the RIL (Radio Interface Layer - part of the ROM) bootloads that processor by sending the modem firmware to it via a serial port when the system boots.
The baseband processor is almost never listed in a phone's specs because it's a "hidden" part of the system. Very often a device like ours will have more CPU cores than just the advertised application processor cores. For example, early Qualcomm MSM7000-series chips had two processors, one for applications and one for radio. Some people labeled these chips as "dual core" even when they really weren't - the two CPUs were completely different.
Similarly, we have two ARM Cortex-A9 cores acting as applications processors, an unknown ARM core doing radio work (much simpler, slower, and power-efficient than the two A9s), and possibly another application-specific ARM core hidden in the GPS chipset. Maybe more.
I obviously don't know what I'm doing but hopefully on of you can help. Below is my current SGH-1777 in the "about phone" stats after I tried to root my phone. I didn't understand the root instructions very well (Ya stupid me) and temporarily bricked my phone because after the reboot I got the evil yellow triangle. I could see the options to chose from but none of them would respond.
So I reconnected my bricked phone to my PC and put the phone in download mode and reinstalled the stock kernel which I had saved earlier and the phone works normal again, but it looks like I still have the installs from the root first root attempt:
"about phone" Info
Android Vs 2.3.4
Base band Vs 1777UCKH7
Kernel Vs 2.6.35.7
Build number UCKH7
I was rooting my phone because I'm pis... off at Samsung and AT&T because part of the reason I bought this phone was for the NFC feature and wanted to use Google Wallet. I also read where rooting the phone improves battery life and get rid of all the bloatware AT&T stuck me with. In my software list I see where I have Superuser and the ROM manager still installed.
Do I need to start all over and how do I do that, or am I just missing a piece of the puzzle? I think one mistake I accidentally made was using the ODIN 1.82 instead of the 1.85 but when I try to PDA the 1.85 now the PDA screen flashes for a second and disappears.
Newbie needs help!
sounds like you rooted it correctly the first time. That yellow triangle doesnt mean you screwed it up. It just means you flashed a non-stock kernel and you tripped the counter. Thats all. Nothing to worry about there.
I dont think you can Google Wallet just yet from the i777. You can, however, remove bloat or better yet, just load a custom rom from one of the great devs.
If you see the superuser app, you're currently rooted. All this info is documented already in stickies.
The info in your About Phone screen is the same as stock out of the box. It would also look the same for stock rooted, and the same with custom roms based on stock. You can make these modifications without changing that info.
The I9100 boot screen with the yellow warning triangle is caused by flashing a non-stock kernel using Odin or Heimdall from a computer. That in itself does not mean the phone is soft bricked.
You can install a custom kernel with nfc support (Entropy512's latest daily driver), but it does not include support for Google Wallet. Support for Google Wallet is a fairly complex programming task that will be a long while appearing if ever.
Please read the guides linked in my signature. There is a lot of good information in there. If you still want to install custom software, a good way for a beginner is to follow the step by step guide.
creepyncrawly said:
The info in your About Phone screen is the same as stock out of the box. It would also look the same for stock rooted, and the same with custom roms based on stock. You can make these modifications without changing that info.
The I9100 boot screen with the yellow warning triangle is caused by flashing a non-stock kernel using Odin or Heimdall from a computer. That in itself does not mean the phone is soft bricked.
You can install a custom kernel with nfc support (Entropy512's latest daily driver), but it does not include support for Google Wallet. Support for Google Wallet is a fairly complex programming task that will be a long while appearing if ever.
Please read the guides linked in my signature. There is a lot of good information in there. If you still want to install custom software, a good way for a beginner is to follow the step by step guide.
Click to expand...
Click to collapse
NFC isn't the kernel - it's just a permissions XML and modified Settings.apk (on I777-based ROMs. Hellraised I9100 ROMs only need the permissions XML, which is included in Hellraiser)
I am pretty much with everyone else and think you are probably rooted. I would just download TB or Root Explorer from the market and see if Superuser allows you root to access either of these apps. Having Superuser on the phone would normally mean you are rooted but to make sure you can run one of the above programs to make sure you are allowed access.
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"
Don't forget to hit the thanks button.
http://superstarmobility.weebly.com/
New thread: http://forum.xda-developers.com/android/development/twrp-m1-lg-k7-t3462130.
(Above TWRP can be flashed with Flashify from Playstore)
Instructions from video:
With phone powered off, hold POWER and VOLUME DOWN buttons until LG logo shows. Release POWER then quickly press and hold again until factory reset menu comes up. Select YES and you will be booted into recovery instead of a factory reset ; )
Thanks @czarsuperstar!
V2 with the proper cmd line from m1 aka LG K7
Reserved.
This the real deal?
goitalone said:
This the real deal?
Click to expand...
Click to collapse
Of course. You looked at the video?
goitalone said:
This the real deal?
Click to expand...
Click to collapse
I've used it and can confirm, first tested it with fastboot without flashing of course(use adb to get to the bootloader: adb reboot bootloader , then fastboot:fastboot boot "twrp.img file, tested then rebooted into bootloader, then flashed via fastboot:fastboot flash "twrp.img file") instructions are for any random person that come by i know you know how to do all this
concerned xda citizen
what are the boardconfig.mk file contents that you used to compile this recovery?
the fact youre using a ghetto hacked twrp that works is fine, but id prefer an actual device specific twrp version that will reliably work - theres no telling what this twrp can do to your device, and the fact youre using another devices ramdisk scares the hell out of me.
ramdisks arent something you play around with - you can seriously ruin someones device like that.
also requesting the twrp fstab file youve used.
youre literally just throwing files at users that have perviously bricked their devices and not explaining in detail what they consist of.
if you seriously damage any of these user's device partitions by overwriting the wrong partition, are you going to pay for the devices when theyre hardbricked and no longer responsive to the oem flashing?
not once have a even seen a warning on these files yet youre just posting forum to forum; not to mention youre inexperienced at rom/kernel/recovery compiling for the fact you think its okay to just throw a different devices ramdisk in there " because it just works." when we have readily available source for our device.
legally- youre held responsible for these files youre distributing.
and to those just flashing this twrp file to their device, yes its reversible - but would you want to find out it doesnt work when its too late? IE backing up partitions in the wrong order, and restoring them into the wrong partitions? the video shows it backs up and restores, but is it doing so in the right order? in the right places. i may be ranting but id rather be careful/safe then sorry.
not one detail of this compile/build has been released, just a link that is claimed to work.
"left sock fits on right, doesnt feel right - but my feet aren't cold!" is how this feels to me.
i was sketched to even test this twrp version considering you need to tell the factory reset "yes, i want to wipe" twice, in order to boot to twrp.
idk about you but ive never seen any recovery warrant those options. normally twrp would just boot upon button combo - which is why im sharing this post. recoveries arent supposed to be functioning that way.
NASSTYROME said:
what are the boardconfig.mk file contents that you used to compile this recovery?
the fact youre using a ghetto hacked twrp that works is fine, but id prefer an actual device specific twrp version that will reliably work - theres no telling what this twrp can do to your device, and the fact youre using another devices ramdisk scares the hell out of me.
ramdisks arent something you play around with - you can seriously ruin someones device like that.
also requesting the twrp fstab file youve used.
youre literally just throwing files at users that have perviously bricked their devices and not explaining in detail what they consist of.
if you seriously damage any of these user's device partitions by overwriting the wrong partition, are you going to pay for the devices when theyre hardbricked and no longer responsive to the oem flashing?
not once have a even seen a warning on these files yet youre just posting forum to forum; not to mention youre inexperienced at rom/kernel/recovery compiling for the fact you think its okay to just throw a different devices ramdisk in there " because it just works." when we have readily available source for our device.
legally- youre held responsible for these files youre distributing.
and to those just flashing this twrp file to their device, yes its reversible - but would you want to find out it doesnt work when its too late? IE backing up partitions in the wrong order, and restoring them into the wrong partitions? the video shows it backs up and restores, but is it doing so in the right order? in the right places. i may be ranting but id rather be careful/safe then sorry.
not one detail of this compile/build has been released, just a link that is claimed to work.
"left sock fits on right, doesnt feel right - but my feet aren't cold!" is how this feels to me.
i was sketched to even test this twrp version considering you need to tell the factory reset "yes, i want to wipe" twice, in order to boot to twrp.
idk about you but ive never seen any recovery warrant those options. normally twrp would just boot upon button combo - which is why im sharing this post. recoveries arent supposed to be functioning that way.
Click to expand...
Click to collapse
The first twrp was from a htc phone. This is from lg leon lte. Same manufacturer. I used my boot.img dumped on my sdcard and used the ramdisk from Twrp Leon aka c50 the leon twrp is missing the options seen on this one. Don't use it. But I'm working on cm_m1 so continue to use the old one and when your phone can't come on have fun getting in recovery. Make it better.
Recovery log
Make a log.
NASSTYROME said:
what are the boardconfig.mk file contents that you used to compile this recovery?
the fact youre using a ghetto hacked twrp that works is fine, but id prefer an actual device specific twrp version that will reliably work - theres no telling what this twrp can do to your device, and the fact youre using another devices ramdisk scares the hell out of me.
ramdisks arent something you play around with - you can seriously ruin someones device like that.
also requesting the twrp fstab file youve used.
youre literally just throwing files at users that have perviously bricked their devices and not explaining in detail what they consist of.
if you seriously damage any of these user's device partitions by overwriting the wrong partition, are you going to pay for the devices when theyre hardbricked and no longer responsive to the oem flashing?
not once have a even seen a warning on these files yet youre just posting forum to forum; not to mention youre inexperienced at rom/kernel/recovery compiling for the fact you think its okay to just throw a different devices ramdisk in there " because it just works." when we have readily available source for our device.
legally- youre held responsible for these files youre distributing.
and to those just flashing this twrp file to their device, yes its reversible - but would you want to find out it doesnt work when its too late? IE backing up partitions in the wrong order, and restoring them into the wrong partitions? the video shows it backs up and restores, but is it doing so in the right order? in the right places. i may be ranting but id rather be careful/safe then sorry.
not one detail of this compile/build has been released, just a link that is claimed to work.
"left sock fits on right, doesnt feel right - but my feet aren't cold!" is how this feels to me.
i was sketched to even test this twrp version considering you need to tell the factory reset "yes, i want to wipe" twice, in order to boot to twrp.
idk about you but ive never seen any recovery warrant those options. normally twrp would just boot upon button combo - which is why im sharing this post. recoveries arent supposed to be functioning that way.
Click to expand...
Click to collapse
Check out the LG L70 it's the same way to get in recovery. This must be your first LG phone.
i dont care whether its the same way to enter recovery, my care is youre using another phone's ramdisk in this device.
"I used my boot.img dumped on my sdcard and used the ramdisk from Twrp Leon aka c50 the leon"
post twrp.fstab and boardconfig.mk youve used for this "twrp" build.
this must be your first posting for development on an unsupported device.
as for anyone using another device's files when we have access to source of our own device - i wouldnt trust them to build anything, let alone CM. thats just pure shortcutting and laziness .. and at what expense?
as for twrp making this official, they wont - as you cannot provide SOURCE.
So, now, hopefully you've compiled TWRP for your device and gotten it working. Now, you'd like to know how to get TWRP officially supported for your device so that it can be installed automatically with GooManager. In order for us to add "official support" for your device we'll need the following:
1) Device configuration files to compile TWRP from source for your device. This means that you cannot have repacked a recovery.img by hand to get it working. We need to be able to compile it from source so that we can easily release future updates.
2) A copy of a build prop for your device (it's in /system/build.prop) so that we can add the correct device information to GooManager
3) We'll build a copy of TWRP and send it to you for validation. Once you've validated that we can build a working image for your device, we'll add it to GooManager.
Go spam the other thread. Over 200 downloads and no problems but there was problems right away with the first version. For your info download Twrp c50 from the Twrp site examine it and ask why it's incomplete. That's why I linked the video of the Twrp from the site and same problems. Bye and leave me be. Hd2 check it out. Czarsuperstar's HTC HD2 android custom roms. Check it out and leave me alone. Thanks for your concern. Oh and for your info we have the same keyboard configuration as the LG Leon. There's a device tree. Google it. Google is your friend bro.
NASSTYROME said:
i dont care whether its the same way to enter recovery, my care is youre using another phone's ramdisk in this device.
"I used my boot.img dumped on my sdcard and used the ramdisk from Twrp Leon aka c50 the leon"
post twrp.fstab and boardconfig.mk youve used for this "twrp" build.
this must be your first posting for development on an unsupported device.
as for anyone using another device's files when we have access to source of our own device - i wouldnt trust them to build anything, let alone CM. thats just pure shortcutting and laziness .. and at what expense?
as for twrp making this official, they wont - as you cannot provide SOURCE.
So, now, hopefully you've compiled TWRP for your device and gotten it working. Now, you'd like to know how to get TWRP officially supported for your device so that it can be installed automatically with GooManager. In order for us to add "official support" for your device we'll need the following:
1) Device configuration files to compile TWRP from source for your device. This means that you cannot have repacked a recovery.img by hand to get it working. We need to be able to compile it from source so that we can easily release future updates.
2) A copy of a build prop for your device (it's in /system/build.prop) so that we can add the correct device information to GooManager
3) We'll build a copy of TWRP and send it to you for validation. Once you've validated that we can build a working image for your device, we'll add it to GooManager.
Click to expand...
Click to collapse
not saying a official twrp isn't preferable, but man you got to learn how to talk to people, you were just short of cursing the dude out, and as far as the recovery the thing is solid(tested backup, flash and restore/ anyhow we got LGUP if you **** up so its not a huge deal), but anyone on this site shouldn't take someones word for things like recovery's and you should always test boot before you flash, also you don't seem to understand the first rule of xda-whatever happens to your device is on you, been that way since the og day's- talking politely to others is the way to go about things, people wont listen if you combative.
Kernel
Im building the kernel from source right now check out the video on Twitter. Anyone that wants to join the development I am down with it.
Didn't work, after selecting yes twice, my phone just starts like normal, doesn't go to TWRP or factory restore, it is there though because I can boot to it from the flashify app, ah well.
wait...my bad, I was highlighting the wrong one, lol, works great, thanks
Assuming it ever worked right it should work better now because you can always get to it.
As for concerns about the ramdisk I don't see any issues with that, it's just being used to boot and run recovery on if I'm not mistaken and apparently where the buttons get enabled so a necessity.
Considering many phones have such hacked together recoverys and many more have no custom recovery I'm thankful to have it particularly since most of my work is done away from my pc.
callihn said:
Assuming it ever worked right it should work better now because you can always get to it.
As for concerns about the ramdisk I don't see any issues with that, it's just being used to boot and run recovery on if I'm not mistaken and apparently where the buttons get enabled so a necessity.
Considering many phones have such hacked together recoverys and many more have no custom recovery I'm thankful to have it particularly since most of my work is done away from my pc.
Click to expand...
Click to collapse
Thanks for report. The other Twrp w/o the button combo was from a HTC phone lol and I am getting blasted. HTC or LG? LG K7. ... LG.
[email protected] said:
Thanks for report. The other Twrp w/o the button combo was from a HTC phone lol and I am getting blasted. HTC or LG? LG K7. ... LG.
Click to expand...
Click to collapse
Right and that's why the buttons didn't work. Great job! Best discovery yet for this phone, so happy that we can restore now withoit adb and withoit having to worry about debugging getting turn off, very essential find. Don't let those that don't understand get you down.
callihn said:
Right and that's why the buttons didn't work. Great job! Best discovery yet for this phone, so happy that we can restore now withoit adb and withoit having to worry about debugging getting turn off, very essential find. Don't let those that don't understand get you down.
Click to expand...
Click to collapse
I'm working on building it from source but keep getting errors and I'm trying it with another device that has Twrp (Moto E 2015) and followed the directions to the T and no luck. So I am trying......... Will let everyone know how it's going.
[email protected] said:
Im building the kernel from source right now check out the video on Twitter. Anyone that wants to join the development I am down with it.
Click to expand...
Click to collapse
kernel??????????????????????????
im down!
Maybe the problem is that I don't know how to properly ask for what I want/need. First off, I am new, so let's pretend I know nothing about modding phones. Second, what I am trying to achieve is the following:
Marshmallow OS or newer (I have lollipop and I highly dislike it)
Complete removal of all AT&T software/bloatware from my M8
Ability to try out different ROMs (are those the same thing as operating systems?) like cyanogenmod.
Those are the highlights to my endgame.
I have found there are several steps to this, and it seems like each step has at least one prerequisite or sub-step and I get overwhelmed when reading up on how to achieve the above goals. Feels like I'm doing taxes for a poorly run business. Apparently I need TWRP on my phone. No clue why or what it does. In order to install it, I need to have root access or a previous version of TWRP already installed, or I need to install the SDK tools package, and from that, only install fastboot and adb. Then after that I need to already have some type of drivers on my PC for that to be useful. Like I said, it is overwhelming to someone who does not know all of the lingo. Especially when I know that if I mess up at certain intervals, I could very well turn my phone into a shiny paperweight or small cocaine tray. Anywhere I have read up on this, when it says download/install _______, I cannot determine whether that means download/install on my PC, or on my phone, bc it doesn't specifically say what goes where in every instance. To make matters more difficult, I do not have an internet connection other than on my phone. Anything that needs to go on my PC, I have to download it to my phone first, then transfer it over, then install it. I asked once for a step by step tutorial or a link to one, and I was given something that was just as confusing as what I have already found. These tutorials seem to be written for ppl who know a lot by ppl who know a lot. I am not one of those ppl. I am a green noob, still wet behind the ears. I apologize in advance for not knowing, but I am just not at the level where I can guess which things go where and If I temporarily render my phone unusable, I won't be able to easily go online to find the fix, nor will I be able to download anything else, if needed. Would greatly help me if I had a list of ingredients needed before I begin, and a sequence, much like a recipe for a cake. Again, I apologize for not knowing, and I'm sure all of you reading this were, at one point, uneducated on the matter. Thank you for any advice and/or reading my TL/DR post.
See my responses below, in red font:
Damagj said:
Apparently I need TWRP on my phone. No clue why or what it does. In order to install it,
TWRP is a custom recovery, and what that is, is explained in "that" thread I linked you to: https://forum.xda-developers.com/showthread.php?t=2744194
Think of TWRP as a kind of small installer program and backup/recovery tool. You need it to flash custom ROMs, and you can also use it to backup the current ROM. It's not used within the Android OS, but rather you can boot into it separately. Which is obviously handy, if for whatever reason you can't boot to Android OS, and need to "recover" (restore the OS).
I need to have root access or a previous version of TWRP already installed, or I need to install the SDK tools package, and from that, only install fastboot and adb. Then after that I need to already have some type of drivers on my PC for that to be useful.
Don't go by the install instructions on the TWRP website, they are not device specific (to the M8) and may misguide you (every Android device has it's own nuances).
To install TWRP, you need to unlock the bootloader. The bootloader is "locked" by default, which by definition means you cannot install a custom recovery. The following is a good step-by-step guide to unlock the bootloader and install custom recovery. Note, that you do not need to root, in order to install TWRP, or flash a custom ROM. So stop before you get to the step of root (flash SuperSU). Also, the version of TWRP you install should be current (3.1) or alternately 2.8.7 (which is a known "old reliable) version).
https://forum.xda-developers.com/showthread.php?t=2799796
Like I said, it is overwhelming to someone who does not know all of the lingo. Especially when I know that if I mess up at certain intervals, I could very well turn my phone into a shiny paperweight or small cocaine tray.
No, you actually can't. Your fear of bricking the phone (permanent damage) is unfounded. As with s-on, this phone is nearly impossible to brick. The phone is fully recoverable even if you screw up; since for what you describe, you are only touching a limited number of partitions (system which is the OS, and recovery). As long as you don't mess with "critical" partitions like hboot and radio, you can't actually brick this phone. And those partitions are actually protected, and you can't modify them even if you wanted, unless you s-off. So all the more reason to stay s-on, as I described in the other thread you posted in here: https://forum.xda-developers.com/showpost.php?p=74107487&postcount=100
To make matters more difficult, I do not have an internet connection other than on my phone. Anything that needs to go on my PC, I have to download it to my phone first, then transfer it over, then install it.
but I am just not at the level where I can guess which things go where and If I temporarily render my phone unusable, I won't be able to easily go online to find the fix, nor will I be able to download anything else, if needed.
That part is difficult. While possible, doing what you describe is somewhat risky with no other device for internet. At some point, it's almost inevitable for anyone tinkering these phones, that something will go wrong. Either you forget a step, or you can't boot for no mistake of your own, at all. Even having done this stuff for years, it still happens to be, once in a while. It just happens. So without a way to ask for help, or download files, you can get stuck in a bad jam. You'll need to have some backup plan, even if it's a friend or family, letting you use their computer as a last resort.
Click to expand...
Click to collapse
Stick with it. Keep reading up, and trying to learn the basic terms, concepts, tools, and methods. I know it seems overwhelming, but it will all start to make sense. You really can't (and shouldn't) try doing these things, until you have some basic understanding. You wouldn't ask someone to tell you how to tear the engine out of a car, without knowing how any tools work, or what any of the parts of the car are called.
I would also suggest you refer to my (AT&T M8) index thread. It has a lot of links and basic info, you may find useful: https://forum.xda-developers.com/showthread.php?t=2751432