After resetting the flash counter via TriangleAway, If I go into CWM Recovery Mode and than return to Download Mode, counter says 1 and system binary is "Custom".
But for example this guy does the same steps as i did, but in minute 3.47 he sees 0 and official in his device but i see 1 and custom in mine: http://www.youtube.com/watch?v=raY_bwsHZSs
Please inform me why is it and how can i fix this?
Nope it never has so something wrong on your phone or running TA .
and yes i have just tested ..
TA sets 1 to 0 boot recovery boot download mode and still 0
Status will of course say modified until you follow the instructions and flash stock firmware and factory reset .
jje
To be honest, there isn't any other instruction left that I didn't try. Applying every step one by one.. "Reset counter on boot" option in TA is also active. But after booting in CWM Recovery, it add 1 (i'm using stock rom and flashed siyah kernel for TA).
Which instruction are you trying? I'll be glad if you can copy&paste to here. I don't think so but maybe there are something different by any chance..
BTW Here what I did last time:
1) Flashed a 4.0.4 stock rom.
2) Rooted with CWM Recovery included one.
3) In CWM Recovery Menu, wiped factory&cache&dalvik
4) Rooted with Stock Recovery included one.
5) Used TriangleAway and removed the battery when it's done (before booting the device)
6) Booted in 'stock' Recovery Mode wiped factory&cache.
7) Immediately booted into Download Mode (counter was 0, both status were official)
8) Flashed the same 4.0.4 stock rom and downloaded automaticly 4.1.1 JB.
Now I'm using it like an ordinary users, I hope it doesn't change binary/system status & counter in time...
Related
Ok so I just flashed the I9300XXDLIH official firmware (4.1.1) with ODIN, returning to stock firmware and stock recovery. I then rooted (while retaining the stock recovery) and used triangle away. It showed the flash count as 3 before aplying the fix, and now it shows flash count 1 and "custom "status. It stays like that and won't go to 0 no matter what.
How come it removed the 3 count and replaced it with 1 but won't remove it to 0? I don't use a custom kernel or custom recovery.
I read certain kernels are compatible and let it go to 0 but when you use a custom kernel, it will be set to 1 on each reboot anyways, so that doesn't help.
Anyone know how to get i to 0? It worked on a CM Rom but I need it to be zero with the stock firmware
thanks for replying
Triangle Away. Make sure you have absolutely stock FW + Kernel.
If it doesn't work, flash the Siyah Kernel then reset and flash the stock on back on.
Everything is stock.
Well, when I flash siyah, reset the counter and then flash back the stock kernel, the flash will bump the counter back to 1.
I have to install the kernel either via CWM or ODIN, but both will trigger the counter. Kind of a vicious cycle. What to do
- Use Triangle Away to reset the flash counters, and pull the battery immediately after rebooting starts
- Boot into recovery and perform a wipe, and pull the battery immediately after rebooting starts
- Go to SamMobile and get the stock firmware for your region
- Flash that stock firmware on your device
- Let Android boot, go through device setup (without doing any logins) until Android is fully usable again
- Reboot
- Wait at least 10 minutes
- Check Settings->About device->Status and make sure Device status is not "Modified"
- Perform another factory reset
- Boot into download mode and make sure the flash counter and system status are all set to official
Try this...
Vipeout said:
Everything is stock.
Well, when I flash siyah, reset the counter and then flash back the stock kernel, the flash will bump the counter back to 1.
I have to install the kernel either via CWM or ODIN, but both will trigger the counter. Kind of a vicious cycle. What to do
Click to expand...
Click to collapse
It is a vicious cycle. It took me forever to get it right.
Once you have installed triangle away:
1. reset counter ( sometimes it reboots sometimes it doesn't ) regardless after the it resets remove the battery.
2. put the SG3 in download mode and flash the stock firmware
3. right after ODIn reboots the SG3 remove the battery
4. reboot into recovery mode and perform a factory reset
5. done
:highfive:
Usually Flash Counter is reset to 1 because of the custom recovery, or because some Samsung devices (including i9300 of course ^^) send a "System Modified" flag both from the bootloader and from fully booted android. There is an option, however, to run Triangle Away at every boot, and early in the boot cycle, to keep it at 0.
See here for the original Triangle Away thread. In the second post, developer chainfire explains why it's this way and what you can do to keep your counter at 0.
I tried following this:
http://forum.xda-developers.com/showthread.php?t=1580070
"INSTRUCTIONS" part:
* RECOVERY: FACTORY RESET IF YOU WERE USING ANOTHER ROM!
* RECOVERY: Install Rom: Download
* RECOVERY: Install Gapps, ALWAYS-EVEN FOR UPDATES: Download (find the latest one that carries the "jb" tag)
* RECOVERY: Wipe Cache Partition
* RECOVERY: Wipe Dalvik Cache
* Reboot and enjoy
Click to expand...
Click to collapse
did all the above, never forgot any of the 3 wipes/resets that were necessary.
used this rom file:
http://goo.im/devs/paranoidandroid/roms/i9100g
(latest one)
for my Galaxy Samsung S II GT-i9100g.
I had CWM and also had a rooted android 2.3.
first boot it showed me the normal samsung boot screen, for 45 minutes....
so I restarted and the phone gave me the same behaviour..
so I removed the battery to turn off the phone, and attempted to reinstall the whole thing, going through this process again from scratch
not forgetting any of the wipes etc...
now every time I boot it, it leads me to CWM instead of the normal boot screen and the expected paranoid rom eventually...
I followed this path because CM 10 failed me because upgrading from 2.3 to 4.x requires going through something that is called "stock" or as I think it actually is - google's /manufacturer's original firmware/rom production line thingy
and after that it needs me to re-enable root on that stock rom all over again. And only then I may attempt to install CM10...
so I picked paranoid instead, because in it's instructions is showed me no such constraint. heck it can't give me that constraint because there is no "stock" of android 3.x for smartphones
but then this issue happened... so I need your help.
I found similar search results but couldn't figure out their solutions or how whatever triggered that same problem (which isn't mentioned in those threads) is related to what I did to my phone... (so that I will not repeat the same mistake)
your help is much appreciated as I need it so so much!
Huh?
Just flash a stock ROM, get back on your feet and go CM or paranoid.
Sent from the little guy
gastonw said:
Huh?
Just flash a stock ROM, get back on your feet and go CM or paranoid.
Sent from the little guy
Click to expand...
Click to collapse
by "flash"ing you mean the option "install from a zip file" in CWM in recovery mod?
if I have some rom, the only way for me to install another would always be by going through that middle step of also installing a 'stock' rom as well?
there is no way around it?
installing a 'stock' rom, wouldn't it make me loose my root I have on the phone and force me to root it all over again before I can continue install anything at all?
thats the reason I wanted to try out the paranoid way of doing this instead of the CM10, because I have no interest in rooting my already rooted phone and I hoped that paranoid does not need me to go to stock first....
Couple of things:
Stock: why, when in trouble, we suggest stock?
Stock is the original state of the phone.
Samsung write it for our device to work flawless, so, by flashing stock we can check if our device is fully functional.
Imagine you flash a custom ROM and you lose IMEI, you go "wtf?" right?
In order to check if your EFS folder is f&#cked up, you flash stock and check if your IMEI is still there.
We can always use stock to take a long breath "phew, we're fine" after a f*&k up.
You can flash stock via CWM (zip file), Odin (tar file, md5) and mobile Odin (tar, zip and md5).
CWM: custom recovery, you can get it by flashing a custom kernel or by flashing it via stock Recovery (generally comes with BusyBox and SuperUser app, which gives you Root).
Odin: Just download any version and follow directions.
Mobile Odin: Well, this is a hell of an app, you need Root to run it.
It does all that Odin does, plus it roots your ROM (only stock ROMs) while it's flashing it, all by itself. Costs 5 bucks, but it's damned worthwhile.
Wanna know the best scenario?
You get M.O Pro, you get a nandroid back up online app, you get CWM zip files (sitting on your SD).
With that line up, you can flash whatecer the hell you want and you will ALWAYS have root.
Sent from the little guy
some questions
ONE QUICK IMPORTANT QUESTION BEFORE THE REST:
If I use mobile odin, will I be able to use it to install stock rom and also root it at the same time?
SECOND IMPORTANT QUESTION:
you said I could flash whatever I want and still have root, but my problem was not 'not having root', it was not having the flash process complete successfully... how do I attack that?
THIRD IMPORTANT... info... :
My "BUILD" version is "GINGERBREAD.XXKL5", isn't that a 'stock' one?
If you don't have a lot of time,
then the rest of this post is not as important as the 2 questions above...
gastonw said:
Couple of things:
Stock: why, when in trouble, we suggest stock?
Stock is the original state of the phone.
Samsung write it for our device to work flawless, so, by flashing stock we can check if our device is fully functional.
Imagine you flash a custom ROM and you lose IMEI, you go "wtf?" right?
In order to check if your EFS folder is f&#cked up, you flash stock and check if your IMEI is still there.
We can always use stock to take a long breath "phew, we're fine" after a f*&k up.
You can flash stock via CWM (zip file), Odin (tar file, md5) and mobile Odin (tar, zip and md5).
CWM: custom recovery, you can get it by flashing a custom kernel or by flashing it via stock Recovery (generally comes with BusyBox and SuperUser app, which gives you Root).
Odin: Just download any version and follow directions.
Mobile Odin: Well, this is a hell of an app, you need Root to run it.
It does all that Odin does, plus it roots your ROM (only stock ROMs) while it's flashing it, all by itself. Costs 5 bucks, but it's damned worthwhile.
Wanna know the best scenario?
You get M.O Pro, you get a nandroid back up online app, you get CWM zip files (sitting on your SD).
With that line up, you can flash whatecer the hell you want and you will ALWAYS have root.
Sent from the little guy
Click to expand...
Click to collapse
the saddest part is that I couldn't figure out most of what you just said
what is 'nandroid'? 'flashing'? do you mean like dd in linux? copying to the entire flash storage device?
'IMEI'? huh..? O_O
at the moment I was able to 'get back on my feet', I restored everything back to normal with manual copying of important parts of the CWM corrupted backup from this week, and old stuff for a CWM backup made few months ago.
now that I am at a 'normal' state.. I want to install paranoid or CM10 on my GT-I9100g.
which one of those 2 does not force me going through installing stock?
I have this fear of installing stock that it will take away my root and that I will have to use adb from command line to re-enable root afterwards, which I have bad experience with.
I need to know a few things before I attempt to install stock via CWM,
will installing stock disable my root? will installing stock disable my ability to load recovery boot menu CWM?
is 'root' an attribute or state that belongs to the running rom itself after boot has been completed and to that only?
or does it also belong to the state the device is at while in the recovery boot menu CWM ?
I tried messing around with ADB in the past to see if I could root devices via that way but it wasn't very successful so thats why I'm afraid of having to attempt it again.
bumpitybump
even though a year later, I would still love some replies
resurrecting my motivation to do this once again.
copy paste from my other post;
before flashing, you will need these;
-stock rom (get it from Sammobile, sign in and select your country and phone model)
-blazing kernel for recovery (search in XDA)
-custom rom (CM, PA, Supernexus...your choice)
-backup your data
-GApps (get the latest one)
-you must know what are you doing and dont flame/blame other member if something wrong
how to flash;
-make sure you are on latest stock rom (mine is JellyBean 4.1.2), if not like the OP, flash the latest stock rom using Odin;
*reboot your phone in Download Mode
*open Odin and in PDA option select your stock rom and then Start
*if done it will display Done and disconnect your phone, it will boot up
*if bootloop, reboot into Recovery Mode, and then wipe data and cache, and then reboot normally
-after updating your phone to latest stock rom, copy your custom rom, GApps, and Blazing kernel into external SD card, then reboot into Recovery Mode
-choose "apply update from external storage" and choose Blazing kernel, wait for it to finish update
-reboot normally, and then reboot back to Recovery Mode. this time you will notice that your recovery is different from the previous one
-select install zip > choose from external storage/sdcard 1 > and then choose your custom rom. then wait for it to finish update
-repeat the above step to install GApps, and after that reboot normally
-if bootloop, reboot back to Recovery Mode and then wipe data, cache and dalvik and then reboot
-done, now you are running on custom rom
Click to expand...
Click to collapse
and about the root, i believe that almost all custom rom rooted
Hey Folks,
I'm Freaking out atm -.-
On Saturday my Phone just shut down, restartet and hung in a bootloop. Doing Wipes and Factory Resets didnt helped me. So i pulled the last Joker and flashed as its metioned here. First few Times nothing happend (But ODIN gave me PASSED after Procedure).
Today I tried again with Odin 3.04, Firmware from the Thread (and Vodafone GER Firmware, Factory Reset / Wpies via Android Recovery) and Wooooooow, Phone is booting. BUT its just booting up, I can make some Settings like Choose Language, Connect to WiFi and so on. After ~30 Seconds the Phone reboots, 3-6 Times, then its stucks on Bootanimation (not looping). After a while Phone gets hot on the Bottom.
Soooooo, any can tell me whats wrong with my Buddy?
Cant send it to Service cause i cannot reset the flashcounter (cant install Apps due to the lack of time phone is active)
Im able to root Phone again / replace stock recovery with CWM -Maybe flashable Zip for resetting the counter?
Installing CustomRom will give me a Loop on Splash Screen
I need my freakin Phone
Cheers
try formatting entire phone(all the internal memory) from cwm recovery. then install a stock rom via odin.
sriram231092 said:
try formatting entire phone(all the internal memory) from cwm recovery. then install a stock rom via odin.
Click to expand...
Click to collapse
Okay What I did:
- Stock Vodafone Germany ROM is installed (but not booting right)
- Rooted with CF-Root 6.4 via Odin again - now i can access CWM Recovery
- Wiped everything (system, data, cache, dalvik, battery, preload)
- Flashed Stock ROM via Odin
- Recovery Droid showed up with blue loading bar under it
- Phone is running blue samsung bootanimation twice
- Phone gives me bootsplashloop twice
- Phone shows blue bootanimation and gets stuck on breathing samsung logo (last part of the bootanimation), blue notification LED is breathing
any guess?
after flashing stock ROM via Odin, go to the stock recovery and do a factory reset
Glebun said:
after flashing stock ROM via Odin, go to the stock recovery and do a factory reset
Click to expand...
Click to collapse
Now its looping the bootsplash 3 or 4 times and than Screen turns black.
After wiping Dalvik, and Factory Reset again Phone boots to Bootanimation (Samsung Logo breathing), Bootanimation starts a Second Time Without Sound, than Boot Splash, Bootsound and blue Bootanimation again.
Sometimes with Graphical glitches (the blue circle around samsung text)
But going not further than Bootanimation, no System showing up
is the phone model name (i9300) present in download mode?
aslo, does the recovery say anything about the efs folder?
Glebun said:
is the phone model name (i9300) present in download mode?
aslo, does the recovery say anything about the efs folder?
Click to expand...
Click to collapse
Yep, Model Name is visible in Download Mode.
Odin Mode
Product Name: GT-9300
Custom Binary Download: Yes (14 counts)
Current Binary: Samsung Official
Current Status: Custom
What should the Recovery say about EFS-Folder? Or where can I find some Info about?
-------------Edit--------------------
Oh, wow, cant enter Stock Recovery now...... god damnit -.-
------------Edit2------------------
Works again.... Strange
One Error Msg:
failed to comapre 'system/csc/common/system/app/AppSelect_v3_1_12_PRO_RC1_GA.apk' '/system/app/AppSelect_v3_1_12_PRO_RC1_GA.apk'(No data available)
No ption Found for getting EFS Info
Hello,
I am stuck in a boot loop.
I can't access stock recovery mode ( holding +, -, and the power butoon).
I CAN access the download mode.
I CAN flash with ODIN with no trouble.
Short description of actions leading to this:
1. Tried to upgrade to the latest CyanogenMod 10.1, Kernel at that time: SGH-I777-ATTGalaxyS2RootStockZedomaxKernel
2. Upgraded successfully, but my pone SIM got locked. I panicked and loaded a backup from CWM.
3. Phone returned to stock ROM (I believe) with Zedomax Kernel. DIdn't fix the SIM lock. Managed to unlock with Galaxy S Unlock app.
4. Decided to Flash a new rom + kernel. ROM: rr_i9100_Resurrection_Remix_V4.0.7_Sep-01-13 KERNEL: AJK-v3.9-AOSP
5. Successfully installed ROM, KERNEL. Installed wrong GAPPS, wiped cache and other cahce (in Advanced), installed correct APPS.
6. Everything works perfectly. SIM locks again. Try the Samsung S Unlock app, IT FAILS. (Because i had a back up of prievious EFS from the stock andorid os and didn't delete it?)
7. Restored EFS, Deleted olf EFS back up, did all 3 steps. SIM still locked. Restored old EFS
8. Loaded backup to Cyanogen Mod 9 (i believe) with Zedomax kernel.
9. Phone doesn't load, can't access CWM, or normal recovery.
10. Flashed Odin3 One-click Downloader I-777 UCKH7 Stock + Root No Bootloaders.
11. Phone stuck in boot loop, can't access Recovery mode. (To try and factory reset, because i think i need to reset cache for everything to work)
12. Flased Zedomax KERNEL, thinking it would give me CWM, but it doesn't.
I have read A LOT of posts regarding similar problems, but i decided to ask for help, seeing as every single situation is different.
[ I think that the unwiped cache and data from the REssurection ROM and AJK KERNEL are interfering with the stock ROM, KERNEL. But i can not enter recovery mode to reset data. These are just my thoughts ]
Please help me.
First, follow just step one below and then enter recovery and perform a wipe data/factory reset.
If that does not solve the problem, continue with steps 2 to 6.
Instructions to clear nand read/write corruption.
Odin3 v1.85 is recommended.
1) Download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA. Without ticking Re-Partitioning
2) Flash the Tar.md5 of the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
3) If that is successful you are done. If it is not, then:
4) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning.
5) Flash the Kernel, as in step 1.
6) Flash the full stock Gingerbread distribution, as in step 2.
If I may add step 7) Stay away from Zedomax/his site; his rooting method, files and information are wrong and outdated.
Problem resolved. Thank you very much for your help!
Hi,
I need to send my phone (Galaxy sII) for warranty and I need to install the factory rom. I'll do that, but i've heard that I also have to install original recovery mode (now i'm running clockworkmod).
Does restoring original rom with odin also restores the original recovery mode or do I have to do it anyway? If so - how?
Original rom will restore the stock recovery
But u should first ..triangle away to reset the binary counter..
Then flash stock rom
Yeah I did that. It shows 0 now. Thanks.