Related
I am looking for info for the Dev section library. Though there are a few comments made regarding flashing back to stock, none seem to offer a (up to date) return to store, stock phone method.
That having been said could sombody offer up a tutorial so I can post it.
Thank you.
Entropy's Thread entitled "[Heimdall][Odin][Stock][Root]UCKH7 Return/Unbrick to Stock (or Root)" is the closest you are going to find to a complete restore to stock.
http://forum.xda-developers.com/showthread.php?t=1286432
I believe this will work for a good majority of folks needing to get back to stock (provided they haven't completely hosed or done something crazy).
Basic steps:
1. Flash the package in the second link of the OP - *NEW* - Kernel + non-rooted system package using either Odin or Heimdall (user's choice - and extract or prepare files accordingly)
2. If the user has accidentally flashed a i9100 International ROM, then they may need to also reflash the stock ATT modem (also in the thread)
3. For good measure, after those items are flashed, probably best to do a factory reset (either via # code or in the UI)
As I mentioned, that should work for 95% of folks that need to go back to stock.
The other 5% are people that flashed a ROM that had new or alternate bootloaders. In this case, I am not aware of any Odin one-click package or bootloader pack available (yet) for the stock ROM, so this may been an issue. But someone may have some more updated information on that.
First settings> privacy> factory data reset.
Then boot into download mode and flash stock plus non root package from here
http://forum.xda-developers.com/showthread.php?t=1286432
With heimdall or Odin
And for anyone who has flashed a different modem you can get the stock modem from the above thread also.
and encase you need to repartition you will need a stock .pit file as well - though as of now as far as I know this is not needed for any reason - non of the roms or kernels in the dev section here in the att xda forums would cause any need for a repartition. Take care with .pit and repartitioning you could end up with a soft brick, a situation that can be recovered from but still not desirable
And if you have flashed anything containing the boot loaders you will need stock boot loaders too, but be very careful with boot loaders as a mistake with boot loaders can result in a hard brick
Sent from my SAMSUNG-SGH-I777 using XDA App
tomween1 said:
I am looking for info for the Dev section library. Though there are a few comments made regarding flashing back to stock, none seem to offer a (up to date) return to store, stock phone method.
That having been said could sombody offer up a tutorial so I can post it.
Thank you.
Click to expand...
Click to collapse
How to Prepare Your Phone to Return to the Store or for Warranty Replacement
There you go. A nice easy to read guide by creepy. Good work.
Sent from my SAMSUNG-SGH-I777 using XDA App
Great guide creepy.
To the OP - why do you believe my packages are not up to date? There is only one firmare revision available for our phone, and that's UCKH7. UCKJ2 is a leak - trying to return a phone with J2 will be a surefire sign to AT&T that you've been diddling around.
It is correct I don't include bootloaders in the package - this is intentional, flashing bootloaders is extremely dangerous. I have a bootloader dump buried within the thread, but I strongly encourage you NOT to try flashing those - again, very dangerous with a good chance of hardbricking.
Entropy512 said:
Great guide creepy.
To the OP - why do you believe my packages are not up to date? There is only one firmare revision available for our phone, and that's UCKH7. UCKJ2 is a leak - trying to return a phone with J2 will be a surefire sign to AT&T that you've been diddling around.
It is correct I don't include bootloaders in the package - this is intentional, flashing bootloaders is extremely dangerous. I have a bootloader dump buried within the thread, but I strongly encourage you NOT to try flashing those - again, very dangerous with a good chance of hardbricking.
Click to expand...
Click to collapse
Well I read through my post again. I thought my question was pretty straight forward, by the responses I received, but I can see where you could have misconstrued my request.
Your packages are all great and (with out a doubt) are the go-to steps. However for noobs, I wanted a more "spelled out" dictation of the steps.... Like the ones supplied by creepyncrawly!
Bro my apologies if I've offended you.... THIS WAS NOT MY INTENT!!!
I still have questions of superuser being in the apps, after all these steps. As I stated to you (PM). I really don't remember if this is installed by AT&T/Samsung out of the box. If not, how is it removed? I would assume, if one were to return a phone, this would be something AT&T wouldn't want to see (again assuming it wasn't stock).
Was the su app still there after flashing entropy's non root package? Are you sure you flashed the non root package and not the stock + root?
Sent from my SAMSUNG-SGH-I777 using XDA App
tomween1 said:
Well I read through my post again. I thought my question was pretty straight forward, by the responses I received, but I can see where you could have misconstrued my request.
Your packages are all great and (with out a doubt) are the go-to steps. However for noobs, I wanted a more "spelled out" dictation of the steps.... Like the ones supplied by creepyncrawly!
Bro my apologies if I've offended you.... THIS WAS NOT MY INTENT!!!
I still have questions of superuser being in the apps, after all these steps. As I stated to you (PM). I really don't remember if this is installed by AT&T/Samsung out of the box. If not, how is it removed? I would assume, if one were to return a phone, this would be something AT&T wouldn't want to see (again assuming it wasn't stock).
Click to expand...
Click to collapse
did you use the UNROOTED version of the package that he provided?
no, superuser is NOT provided by ATT, for obvious reasons.
dayv said:
Was the su app still there after flashing entropy's non root package? Are you sure you flashed the non root package and not the stock + root?
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
Well there's something interesting. I will retry. I had both on my computer and may have used the wrong one.
I understand that this may have been asked, and I've been looking at similar threads, but I'm having a hard time finding a direct answer, so I apologize.
I have some experience rooting with an Atrix, but I just got this phone two days ago, this morning I used the 1-click method from rootwhiz to install the ICS leak. No problems having it run at all. I need to know, directly, did this install change my bootloader and change the binary count? I can't remember if I saw anytime of yellow triangle as people talk about. If it changed the bootloader what is there a safe method to return to the older bootloaders, and or do I even need to do so to root and install other roms?
I know that the Atrix had some problems in terms of returning to prior versions of things, and in my research I haven't found a direct answer to this question too.
Basically, did my bootloader change? Can I root using the heimdall method I keep seeing about safely? What would be the best way to root and install custom roms, neglecting the binary counter if I can get a jig or something?
Forgive me again for asking, I just need to have better answers before I try anything.
Are you asking for info for your Atrix or SGS2 device?
Sorry, I am asking about the SGS2.
ds1904.ds said:
I understand that this may have been asked, and I've been looking at similar threads, but I'm having a hard time finding a direct answer, so I apologize.
I have some experience rooting with an Atrix, but I just got this phone two days ago, this morning I used the 1-click method from rootwhiz to install the ICS leak. No problems having it run at all. I need to know, directly, did this install change my bootloader and change the binary count? I can't remember if I saw anytime of yellow triangle as people talk about. If it changed the bootloader what is there a safe method to return to the older bootloaders, and or do I even need to do so to root and install other roms?
I know that the Atrix had some problems in terms of returning to prior versions of things, and in my research I haven't found a direct answer to this question too.
Basically, did my bootloader change? Can I root using the heimdall method I keep seeing about safely? What would be the best way to root and install custom roms, neglecting the binary counter if I can get a jig or something?
Forgive me again for asking, I just need to have better answers before I try anything.
Click to expand...
Click to collapse
If you used the 1-Click method, yes. Your bootloaders are changed. Wouldve been much better to use the Heimdall method or just root your phone then flash the Leak ROM that task650 and Fenny made. As far as reverting bootloaders to stock, thats out of my range of knowledge. Im sure there is a way to do it though.
EDIT: For rooting, best way is to be on stock 2.3.4 and use the Zergrush exploit.
I've seen you're using the past tense a lot, I thought you already DID.
Anyway, for rooting and installing custom ROM, follow this thread:
http://forum.xda-developers.com/showthread.php?t=1311081
I can't pinpoint exactly what to do since having no info.
Thanks for the answers so far, now that I know my bootloaders have been changed I need to figure out how to either change back / and how to safely root. I may just have to wait it out I think though, no problem with that really, working just fine now. And never use the alarm
For clarification, my rooting experience is limited to the Atrix, the SGS2 is new as of Monday, and I am having trouble sifting through information. What I've learned so far is that maybe it was a little hasty to install the ICS leak the way I did. Prior to the ICS leak there was nothing changed on the phone.
You're going to have to get some experience with ODIN. Here is the bootloader you'll want to flash back to, however, then you'll probably need to flash a kernel with CWM (clock work mod) and then boot into cwm to flash a rom such as Tasks stock ICS leak. http://forum.xda-developers.com/showthread.php?t=1316726
So if I follow correctly the ICS leak I installed added newer bootloaders that prevent jigging in the future if it was needed. My two options are apparently to use the method that bypasses the counter, which was posted, or to use ODIN and flash the older bootloader, but this can be dangerous if done incorrectly.
The danger of bricking scares me a little, but I successfully used RSD Lite to unlock the bootloader on my Atrix, don't know if it's similar. Perhaps I should take the Atrix and attempt to install an older bootloader on it to get a feel for things? I figure that it wouldn't make much of a difference however...
I figured out that even though I have a newer bootloader now I still have a 0 for the binary counter, as the leak is considered a samsung official release, of course I don't know how that would effect any given warranty.
So, I still feel that these following questions are unanswered, I apologize if I am not understanding correctly:
1. Is it safe for me to root with the heimdall method even with the newer bootloaders
2. Is it safe for me to install custom roms without reverting the bootloader, as long as I am using the bypass method to prevent my counter from changing?
3. What is the exact risk to flashing the older bootloader, and what precautions should I take before doing so? If I flash the older bootloader without reverting to stock firmware will that cause a brick? Or is the risk just associated with fudging up the process of the flash itself, and hoping that the connection doesn't get cut (on that note, the phone, usb cord, and computer I'm using are all less than 4 months old, so that risk doesn't concern me a whole lote).
Sorry if these are stupid questions, I hope I am asking good enough questions to help others out in the future
After some more reading, here's another question as well:
Does the SGS2 technically have an unlocked bootloader already? It just counts how many times you install non samsung firmware?
Also just so I know that I'm not wrong, are Kernal, Firmware, and "Roms" all the same thing? How can you tell if a "package" or "rom" comes with bootloaders, as this is something I apparently am supposed to avoid.
ds1904.ds said:
1. Is it safe for me to root with the heimdall method even with the newer bootloaders
Click to expand...
Click to collapse
Dont believe you can root since you already flashed it with ODIN 1-Click
ds1904.ds said:
2. Is it safe for me to install custom roms without reverting the bootloader, as long as I am using the bypass method to prevent my counter from changing?
Click to expand...
Click to collapse
You cannot install custom ROM's because you dont have CWM.
ds1904.ds said:
3. What is the exact risk to flashing the older bootloader, and what precautions should I take before doing so? If I flash the older bootloader without reverting to stock firmware will that cause a brick? Or is the risk just associated with fudging up the process of the flash itself, and hoping that the connection doesn't get cut (on that note, the phone, usb cord, and computer I'm using are all less than 4 months old, so that risk doesn't concern me a whole lot).
Click to expand...
Click to collapse
Really not sure on these questions. Any takers?
ds1904.ds said:
After some more reading, here's another question as well:
Does the SGS2 technically have an unlocked bootloader already? It just counts how many times you install non samsung firmware?
Click to expand...
Click to collapse
No; Only download mode (Odin/Heimdall) flashes trigger changes to the warning screen.
ds1904.ds said:
Also just so I know that I'm not wrong, are Kernal, Firmware, and "Roms" all the same thing? How can you tell if a "package" or "rom" comes with bootloaders, as this is something I apparently am supposed to avoid.
Click to expand...
Click to collapse
Kernel is a set of drivers that tells the hardware what to do. Firmware is like a new base. (XXLPQ, DXLP7 etc.) A ROM is the whole package.
Please if I missed anything or am incorrect about some/all of this, somebody correct me.
Okay I think I'm starting to figure this out. I downgraded to 2.3.4 using an unroot/stock method I found, using odin and it worked. It would not accept the OTA update however, but I believe this is due to the ULCL2 baseband? Someone correct me if I am wrong.
Now I am going to use method 2c found here:
http://forum.xda-developers.com/showthread.php?t=1311081
to root and restore to the other baseband, which also happens to be the one that's best for my area I believe. From there, I can install CWM using one of the 31-c methods, and use CWM to install custom roms as long as they don't have bootloaders, correct? Or does it not matter if the packages have bootloaders.
Someone correct me if I am wrong, I don't want to ruin anything here. I think it's safe to install the files that come from the 2c method but wont be doing anything else until I know it's safe.
ds1904.ds said:
Okay I think I'm starting to figure this out. I downgraded to 2.3.4 using an unroot/stock method I found, using odin and it worked. It would not accept the OTA update however, but I believe this is due to the ULCL2 baseband? Someone correct me if I am wrong.
Now I am going to use method 2c found here:
http://forum.xda-developers.com/showthread.php?t=1311081
to root and restore to the other baseband, which also happens to be the one that's best for my area I believe. From there, I can install CWM using one of the 31-c methods, and use CWM to install custom roms as long as they don't have bootloaders, correct? Or does it not matter if the packages have bootloaders.
Someone correct me if I am wrong, I don't want to ruin anything here. I think it's safe to install the files that come from the 2c method but wont be doing anything else until I know it's safe.
Click to expand...
Click to collapse
Should be fine. NONE of the ROMs you find on the I777 boards in Ported or Original will have bootloaders so no worries. And yes after root use Mobile ODIN to install a zImage which will give you CWM. Highly recommend Siyah 2.6.14. Please stick to just trying some GB ROM's and get the hang of making nandroids etc before moving on the ICS ROM's.
D3M3NT3D_L0RD said:
Should be fine. NONE of the ROMs you find on the I777 boards in Ported or Original will have bootloaders so no worries. And yes after root use Mobile ODIN to install a zImage which will give you CWM. Highly recommend Siyah 2.6.14. Please stick to just trying some GB ROM's and get the hang of making nandroids etc before moving on the ICS ROM's.
Click to expand...
Click to collapse
All I get is an apk file, I've been searching all night for a zimage... The file says i777 flashkernal, and it's just an .apk. Mobile Odin can't see it unless I name it zimage with no file extension. I tried that and it seemed like it was soft-bricked so I used odin on the PC to reflash the stock root think mentioned in the thread.
I was thinking of CM7 if it will work flashing as a zip from CWM, if I can get CWM on there that is.
ds1904.ds said:
All I get is an apk file, I've been searching all night for a zimage... The file says i777 flashkernal, and it's just an .apk. Mobile Odin can't see it unless I name it zimage with no file extension. I tried that and it seemed like it was soft-bricked so I used odin on the PC to reflash the stock root think mentioned in the thread.
I was thinking of CM7 if it will work flashing as a zip from CWM, if I can get CWM on there that is.
Click to expand...
Click to collapse
Where in the hell are you getting an apk from? If you dl Siyah or Entropy kernel, the zImage is in the zip. Pull that and put it on your SD card
I am interested because I was in your position. Did the ICS leak 1 day too early and lost root. So what method did you use to go back to GB? Did you have to flash a new bootloader or was that all done in one package? Was it Entropy's "return" method?
I was seeing if I can keep the ICS leak and root. A dev here advised that all I need to do is re-flash the zip filed ICS leak. However since I have no root, I can't CWM recovery...I don't know another method to flash the rooted ICS leak.
So I'm thinking I have to wait for an exploit, or flash back to an old GB, root, ensure I have CWM, nandroid (I nandroided my rooted GB before upgrading to ICS leak), then flash the zip ICS leak.
Does anyone else have alternatives?
ds1904.ds said:
Okay I think I'm starting to figure this out. I downgraded to 2.3.4 using an unroot/stock method I found, using odin and it worked. It would not accept the OTA update however, but I believe this is due to the ULCL2 baseband? Someone correct me if I am wrong.
Now I am going to use method 2c found here:
http://forum.xda-developers.com/showthread.php?t=1311081
to root and restore to the other baseband, which also happens to be the one that's best for my area I believe. From there, I can install CWM using one of the 31-c methods, and use CWM to install custom roms as long as they don't have bootloaders, correct? Or does it not matter if the packages have bootloaders.
Someone correct me if I am wrong, I don't want to ruin anything here. I think it's safe to install the files that come from the 2c method but wont be doing anything else until I know it's safe.
Click to expand...
Click to collapse
SMH...root is not needed for CWM... a custom kernel is
Pirateghost said:
SMH...root is not needed for CWM... a custom kernel is
Click to expand...
Click to collapse
True but to do it with Mobile ODIN you need root
ds1904.ds said:
After some more reading, here's another question as well:
Does the SGS2 technically have an unlocked bootloader already? It just counts how many times you install non samsung firmware?
Also just so I know that I'm not wrong, are Kernal, Firmware, and "Roms" all the same thing? How can you tell if a "package" or "rom" comes with bootloaders, as this is something I apparently am supposed to avoid.
Click to expand...
Click to collapse
"ROM" is an improper name for the firmware flashed to a phone. (the memory in question isn't read-only by any means. In Windows Mobile devices, you had to flash the firmware image all in one go - but on Android, /system contents can be modified on the fly as they're a normal file system.) garyd9 started a little crusade against the term ROM and I try to continue it (but I slip up sometimes).
Kernel contains the most basic low-level hardware drivers for a device. It's a small portion of the firmware for a phone. The remaining portion is the system partition - /system - kernel and /system together make a complete firmware package.
And you are correct - our bootloaders are fundamentally unlocked, the only code signing enforcement is the custom binary counter. It can be reset either with the jig or with TriangleAway (TriangleAway requires ICS)
Entropy512 said:
"ROM" is an improper name for the firmware flashed to a phone. (the memory in question isn't read-only by any means. In Windows Mobile devices, you had to flash the firmware image all in one go - but on Android, /system contents can be modified on the fly as they're a normal file system.) garyd9 started a little crusade against the term ROM and I try to continue it (but I slip up sometimes).
Kernel contains the most basic low-level hardware drivers for a device. It's a small portion of the firmware for a phone. The remaining portion is the system partition - /system - kernel and /system together make a complete firmware package.
And you are correct - our bootloaders are fundamentally unlocked, the only code signing enforcement is the custom binary counter. It can be reset either with the jig or with TriangleAway (TriangleAway requires ICS)
Click to expand...
Click to collapse
Glad you chimed in. I now feel stupid at my lack of knowledge
I almost think that the issue is that your "unzipping" the zip image files that you are downloading.
Why is it so important that you keep the phone in a reversable mode? Are you planning on returning it or perhaps selling it and do not want it to be known that you have flashed it?
Personally I am not knowledgeable enough to offer much advice, I just read the forums as most and try to put together the peices of information that fit my situation.
The Dev forum is by far the best place to look and get your questions answered and there are a bunch of guides on step by step processes. The only real advice I can give you is to google each term and understand what it is you need and then post your question.
I rooted my son's AT&T SGII, then flashed CyanogenMod 9 daily updated ROM and Google Market. Everything worked great, but by using CWM recovery the flash counter increased by 1 (then 2 on retry) and the splash screen has the GT-I9100 and warning triangle graphics. As this was expected, I didn't see any cause for alarm.
No cause because I have a micro USB Jig and expected to be able to use it to go into download mode in order to reset the counter and remove the warning triangle. BUT... It didn't work.
I know the jig is good because it still works on my personal I777; I even purposefully tripped the flash counter to check. No problem. Since both devices are identical models, both rev. 01, and are configured alike I cannot diagnose why the jig will not work on the second device.
The differences between the devices are time and place of purchase. I bought mine very soon after the original release date, in San Antonio, TX. My son bought his in D.C. earlier this month.
Can anyone tell me how the device purchased at a later date differs in either hardware or firmware from an earlier device? And if so, does that make the jig obsolete?
The flash counter code is contained in the secondary bootloader. It is possible that the secondary bootloader was flashed and updated to a version of the sbl that cripples the flash counter reset code. If that is the case, the only fix is to flash the original secondary bootloader back onto the phone. You can find the files in the Download Repository. See link in my signature. Please be sure that you understand the risks of flashing bootloaders if you choose to take this path.
creepyncrawly said:
The flash counter code is contained in the secondary bootloader. It is possible that the secondary bootloader was flashed and updated to a version of the sbl that cripples the flash counter reset code. If that is the case, the only fix is to flash the original secondary bootloader back onto the phone. You can find the files in the Download Repository. See link in my signature. Please be sure that you understand the risks of flashing bootloaders if you choose to take this path.
Click to expand...
Click to collapse
Creepyncrawly,
Thank you for the prompt reply and the suggested solution. I will do as you recommend and try to correct the secondary boot loader using the files in the download repository.
I have to admit I am puzzled, since I used exactly the same procedure to root and flash ROMs on both devices. The only difference in procedures was which daily update to CM9 I used to originally flash.
Once I complete the procedure I'll let you know how successful the fix proved to be.
I would check the package that you flashed to see what it contains. If it did indeed flash sbl.bin you will find that file in the package. Just open it up to see what it contains. I would do that before I flash the bootloader.
There is an app to reset the flash counter that works with ics based roms called triangle away in case you are interested.
http://forum.xda-developers.com/showthread.php?p=22463153#post22463153
Sent from my SGH-I777 using XDA Premium HD app
creepyncrawly said:
I would check the package that you flashed to see what it contains. If it did indeed flash sbl.bin you will find that file in the package. Just open it up to see what it contains. I would do that before I flash the bootloader.
Click to expand...
Click to collapse
creepyncrawly,
Did check the file to verify the sbl, but couldn't find anything that seemed pertinent. Due to time constraints (My son goes back to D.C. this morning) I went forward with flashing the tar in the download repository as you suggested.
All seems well; phone booted up as expected, and the startup screen displays the correct model number minus the warning triangle. I then rebooted into download and applied the jig to reset the 0din flash counter. Now just like new, with CM9 running strong.
Only troubling aspect is why there would be a difference in the results using the same configuration on two identical devices. I'll leave that for another day.
Thank you for your suggestion.
~ zancro
One if the updates from Samsung for the sgs 2 made jigs stop resetting the flash counter with an update to the secondary boot ladders. Reflashing the old bootloader should fix that. Funny that the fix is so easy isn't it?
Sent from my SGH-I777 using xda premium
A newly purchased GS2 might include updated bootloaders.
The UCKK6 leak included "jig-crippled" bootloaders.
The OTA didn't touch the bootloaders.
Factory-UCKK6 devices may contain the UCKK6 bootloaders.
TriangleAway will do the trick on ICS.
Right so, this is my first post so I'm very new here.
I have a Samsung S2 (I9100) which I rooted using Framaroot. I then flashed CM 10.1.3 on my phone. I also flashed the DorimanX 9.41 kernel. I want to return my phone to stock everything. Basically, as it was when it came out of the box. I want to do this because I might return it to warranty soon. I know the steps to do. However, I need to understand a few things:
Is Triangle Away safe if I use it correctly?
When I flash the stock firmware, will I be able to receive OTA updates or will all of my updates need to be from Odin?
If I want to restore my warranty, does my phone need to have the carrier branded firmware? I am going to get carrier-branded firmware anyway but I am just wondering.
My baseband version is I9100XXLPH. My carrier is T-Mobile UK. When I go to SamMobile, I get this:
GT-I9100 United Kingdom (T-Mobile) 2013 June 4.1.2 I9100XWLSY I9100TMULS8
If my baseband version is I9100XXLPH, does this mean that this firmware is not correct for my phone?
Thanks for the help!
1) Well yes, like any flash there's that 0.0000001% something will go wrong. You can't remove that risk regardless of what anyone might tell you. If that frightens you, best not flash anything at all. Ever.
2) If you go back to stock, you should be able to get OTA updates OK, but sometimes it doesn't always work out this way. It's just as easy to flash your stock updates via Odin if you find OTA updates won't happen for whatever reason (flashing a 3 part firmware with CSC when you go back to stock seems to make it more likely OTA updates happen smoothly after).
3) If I was returning a phone for a warranty claim, yes, I'd put the latest stock firmware on for my carrier.
4) Forget basebands (which is your modem & not really relevant to anything) or anything else, choose the latest firmware they have for your carrier, flash that.
Thanks very much. However, when using Triangle Away, is there ANYTHING I can do to increase the chances of a successful reset? Also, will having used Framaroot change anything?
I've never had any problems using it (have used it a number of times/on different devices) & am not aware of anything you can do to try and 'maximise' your chances of it working (it should work for most people/most of the time), other than reading thread devoted to it on here thoroughly if you're genuinely nervous about it; other people's experiences in the thread might yield some useful info.
The root method shouldn't have a great deal of bearing on anything, but I'm not a developer so I'm not familiar with the 'inner workings' of how Framaroot injects Su & Busybox onto the phone/whether it does anything materially different compared to other root methods that might interfere with Triangle Away. I don't believe it does based on I can't remember anyone posting in the two yrs I've been coming here saying 'Triangle Away wouldn't work because I used X root method'.
Put it this way, if worse came to worse, if Triangle Away refused to work/reset the flash counter, you could always go back to Gingerbread stock, reset the flash counter with a jig, then flash the latest stock firmware & sent it in for warranty service.
Triangle Away is quick/simple/works most of the time, but that's not the only option you have if it won't work & you absolutely must reset the flash counter.
Thanks for all the advice. One more question though , is Triangle Away compatible with all ROMs and kernels? And (hopefully) final question, do I only wipe data on recovery or do I also wipe cache?
It's I9100 compatible, so yes, it is.
Sent from the little guy
Eyensteinium said:
And (hopefully) final question, do I only wipe data on recovery or do I also wipe cache?
Click to expand...
Click to collapse
Could you answer this question?
It doesn't matter, whatever suits you.
Sent from the little guy
gastonw said:
It doesn't matter, whatever suits you.
Sent from the little guy
Click to expand...
Click to collapse
What does the cache do then?
Stores apps' info and other s#!t.
It's not mandatory to wipe per se, but it might help when going stock from custom and viceversa.
I told you, you're safe from the brick bug as long as you stay away from 4.0.4.
Sent from the little guy
OP - You're starting to overthink/ovecomplicate this. There's no need to. Reset the counter, flash stock, done.
Okay. It's just that the warnings on the Triangle Away app are a bit scary and both times I've flashed with Odin, I've been stuck in a bootloop. Anyway, hopefully, I'll have stock JB up and running before Monday.
Sent from my GT-I9100.
Trust me, you'll be fine (never trust someone who says 'trust me' )
When should I wipe data, before or after flash?
After.
Okay, thanks a lot. Just need to make a note of which apps I have installed so I can reinstall them afterwards. Also, is it possible to backup my messages and call logs?
Yes, titanium back up pro & similar.
Sent from the little guy
But Titanium Backup doesn't work without root. After going back to stock, I'm going to stay unrooted for a while. Also, I don't want to backup apps.
Notice that I included "similar" over there.
You really should hit the threads before you jump onto the flashing field.
Sent from the little guy
Thanks for the reply. Just two more questions:
If I do EVERYTHING correctly, is there any chance of a hard brick.
And, I tried following this guide (http://forum.xda-developers.com/showthread.php?t=1068193) but the commands it said to back up my efs folder didn't work. Could you recommend an efs backup tool?
Hi guys so today I got my art unlocked m8
I tried to update but tells me there is no update and to it will check in the next 48hours
I 've been told to get rid of art room and get HTC official room but I have no idea how I've been looking over the forums and I didn't understand a thing with all the techi talking could anyone help me please kinda clueless
ibma said:
Hi guys so today I got my art unlocked m8
I tried to update but tells me there is no update and to it will check in the next 48hours
I 've been told to get rid of art room and get HTC official room but I have no idea how I've been looking over the forums and I didn't understand a thing with all the techi talking could anyone help me please kinda clueless
Click to expand...
Click to collapse
They pulled the AT&T update. Soooo....just gotta wait.....
ibma said:
I 've been told to get rid of art room and get HTC official room but I have no idea how I've been looking over the forums and I didn't understand a thing with all the techi talking could anyone help me please kinda clueless
Click to expand...
Click to collapse
I'm just guessing this is a case of autocorrect, and you mean "custom ROM" and not "art room"?
How did the custom ROM get on your phone, did you buy it that way or did someone do it for you?
The update won't install with a custom ROM, its true (at least if any system files have been altered, which is usually the case). Also, it won't install with a custom recovery. Might even send you into a bootloop and render the phone unusable.
If you want to return to a stock condition and get the update, you can either read up and learn, or run the RUU to return to stock (bootloader must be locked or you need S-off). In either case, we can help you, but need specifics on how you want to approach it.
redpoint73 said:
I'm just guessing this is a case of autocorrect, and you mean "custom ROM" and not "art room"?
How did the custom ROM get on your phone, did you buy it that way or did someone do it for you?
The update won't install with a custom ROM, its true (at least if any system files have been altered, which is usually the case). Also, it won't install with a custom recovery. Might even send you into a bootloop and render the phone unusable.
If you want to return to a stock condition and get the update, you can either read up and learn, or run the RUU to return to stock (bootloader must be locked or you need S-off). In either case, we can help you, but need specifics on how you want to approach it.
Click to expand...
Click to collapse
oh the lousy autocorrect got me.
I have no idea what im doing lol, im following a tut to install revolution hd rom and so far everything is working perfect lets see what happens after system reboot.
Can I unroot and relock bootloader after custom rom install done ?
Update: restoring old content phone seems faster with better signal, but before custom rom it had 4g signal now seems only 3g
Now that sucks boomsound enable/disbale in settings is gone!
So is extreme power saving gone from status bar
also 4g signal
Signal will not show 4g or 4glte like AT&T [email protected] [email protected]
You could relock and unroot,but then no reason to flash a custom rom.
Those two settings are in settings. And on the m8 443 euro builds some are reporting lesser [email protected]
There are AT&T ROM's available that are tailored to us AT&T/GSM networks
ibma said:
oh the lousy autocorrect got me.
I have no idea what im doing lol, im following a tut to install revolution hd rom and so far everything is working perfect lets see what happens after system reboot.
Can I unroot and relock bootloader after custom rom install done ?
Update: restoring old content phone seems faster with better signal, but before custom rom it had 4g signal now seems only 3g
Click to expand...
Click to collapse
ibma said:
Now that sucks boomsound enable/disbale in settings is gone!
So is extreme power saving gone from status bar
also 4g signal
Click to expand...
Click to collapse
ibma said:
Hi guys so today I got my art unlocked m8
I tried to update but tells me there is no update and to it will check in the next 48hours
I 've been told to get rid of art room and get HTC official room but I have no idea how I've been looking over the forums and I didn't understand a thing with all the techi talking could anyone help me please kinda clueless
Click to expand...
Click to collapse
Just use this guide to flash the ruu for 4.4.3. It only works on att m8. MAKE SURE YOU READ THE DIRECTIONS! You just need to relock your boot loader if you are not s-off
http://forum.xda-developers.com/att...-2-23-502-3-bootable-ruu-pc-required-t2860486
ibma said:
I have no idea what im doing lol, im following a tut to install revolution hd rom
Click to expand...
Click to collapse
This is the exact reason I highly discourage following step-by-step tutorials; and/or using toolkits. You are modding the phone with apparently very little understanding of what you are actually doing. Not only is this very risky, as it might result in damage to you phone. But it also leaves you completely unequipped to handle any problems.
My suggestion is to spend a few hours reading the basic information that the folks here have taken the time to compile. This isn't "techie" stuff, this is the basic information and concepts that should be understood before doing any modding of the phone. Quite simply IMO if you don't understand the basics, you have no business rooting/modding the phone.
exad's excellent guide: http://forum.xda-developers.com/showthread.php?p=52484527
FAQs: http://forum.xda-developers.com/showthread.php?t=2711073
Index of AT&T M8 resources: http://forum.xda-developers.com/showthread.php?t=2751432
Index of "international" M8 resources (most apply to AT&T version): http://forum.xda-developers.com/showthread.php?t=2694600
redpoint73 said:
This is the exact reason I highly discourage following step-by-step tutorials; and/or using toolkits. You are modding the phone with apparently very little understanding of what you are actually doing. Not only is this very risky, as it might result in damage to you phone. But it also leaves you completely unequipped to handle any problems.
My suggestion is to spend a few hours reading the basic information that the folks here have taken the time to compile. This isn't "techie" stuff, this is the basic information and concepts that should be understood before doing any modding of the phone. Quite simply IMO if you don't understand the basics, you have no business rooting/modding the phone.
exad's excellent guide: http://forum.xda-developers.com/showthread.php?p=52484527
FAQs: http://forum.xda-developers.com/showthread.php?t=2711073
Index of AT&T M8 resources: http://forum.xda-developers.com/showthread.php?t=2751432
Index of "international" M8 resources (most apply to AT&T version): http://forum.xda-developers.com/showthread.php?t=2694600
Click to expand...
Click to collapse
What i did is i unocked, rooted, then installed twrp, took nanodroid backup and installed custom rom, would it cause any issues if i factory reset the phone ?(will it reset to at&t room that came with the device)
ibma said:
What i did is i unocked, rooted, then installed twrp, took nanodroid backup and installed custom rom, would it cause any issues if i factory reset the phone ?(will it reset to at&t room that came with the device)
Click to expand...
Click to collapse
Again, you need to learn and research more before doing anything. This is another perfect example. Factory reset doesn't do anything to the ROM. All it does is wipe the user data partition, and isn't going to help your case in any way. And trying to make up your own solutions is not a good idea (but at least you thought to ask before trying it).
If the intent is to simply be on the latest 2.23 stock software, just run the RUU. You will need to relock the bootloader before RUU if you are s-on. Also, back up any personal data, as user data will be wiped by RUU.
redpoint73 said:
Again, you need to learn and research more before doing anything. This is another perfect example. Factory reset doesn't do anything to the ROM. All it does is wipe the user data partition, and isn't going to help your case in any way. And trying to make up your own solutions is not a good idea (but at least you thought to ask before trying it).
If the intent is to simply be on the latest 2.23 stock software, just run the RUU. You will need to relock the bootloader before RUU if you are s-on. Also, back up any personal data, as user data will be wiped by RUU.
Click to expand...
Click to collapse
I restored stock recovery and got bavk to att rom RUU is giving me usb error dunno why.
ibma said:
I restored stock recovery and got bavk to att rom RUU is giving me usb error dunno why.
Click to expand...
Click to collapse
Not enough info. What exactly does the error say?
S-on or S-off. Did you relock the bootloader?
Any response if you type (using adb):
adb devices
Improper HTC/ADB drivers or using Microsoft USB 3.0 drivers on USB 3 port on Windows 8.x instead of Intel USB drivers would be my first two guess. The ladder of the two issues would be most likely scenario if RUU communicates with device while booted into Android OS but fails to connect when the device is in fastboot/boot loader mode.
-Sent from a payphone...