So... I have TeamWin bootloader (I think).
I'm trying to update to Bean's 4.3 update from late December. Can I get a quick... how do I do this? I see there are 3 different downloads (2 seem to be the same about 1GB and one is for the modem and wifi).
Basically, how to do I get it?! Thanks in advance and sorry if I'm doing this wrong...
sukimysuki said:
So... I have TeamWin bootloader (I think).
I'm trying to update to Bean's 4.3 update from late December. Can I get a quick... how do I do this? I see there are 3 different downloads (2 seem to be the same about 1GB and one is for the modem and wifi).
Basically, how to do I get it?! Thanks in advance and sorry if I'm doing this wrong...
Click to expand...
Click to collapse
Are you currently on a 4.1.2 base? Either stock or rooted. Are you rooted, if so what recovery are you using and are you on the most update recovery either Newest Philz, CWM (6.0.4.3) or TWRP (2.6.3.1)? If these are yes, then download a 4.3 roms from Beans, Sophisticated, Alliance, R3D Nep...so on. If not rooted and on 4.1.2 base, download casual script and root your phone and it will install a custom recovery for you, TWRP 2.5.0.0. Next, Download the Wifi/Modem Beans has posted. Make a back up of your current rom in the recovery of your choice (system, data, cache, radio(modem). Wipe user/data, cache, dalvik, 3x. Then install the rom, boot up to make sure you did it right. Reboot into recovery, open ODIN 3.07, check the PDA box, select the PDA box to open the new modem.tar, flash it, wait for it to complete, once completed wipe data/user, cache, dalvik, reboot into ROM and you should now have the 4.3ROM with MJ9 Radio. If you don't your WIFI should not work and you will have no service. Also, if you go to Settings < Phone < Status, you will see Unknown in lots of boxes.
Related
So i managed to solve the problem that i had.
When i said that i could flash only the stock one, i was flashing XXKI3 as one file after each failed attempt to flash a custom one.
So i tried and flashed another stock rom, again as 1 file. after the flash was done the phone again stucked at first screen wit the triangle.
After that i thought that something was really messed up in the phone and flashed again XXKI3 with PIT and multiple files and offcourse RE-Partition.
After that flash a stock rom with 1 file and modified bootloader from Intratech's thread, this way you can also reset the binary caunter with a jig (can find many on ebay).
After finish flashing and first boot
root with CF kernel and flash any custom rom. It worked as it should. Now i am on a custom rom and trying to see which one suits me best.
Thank Jiganet for some may be needed modified bootloader which is recommended so you can reset binary counter.
Everyone tha nk you for your suggestions and help.
any rom that i install is not getting beyond the bootlogo. i had xxki3 stock with cf-root xxki3 kernel.
every install i make full wipe on everything before(data, cache, dalvik).
any body any idea?
only stock rom working.
The first boot takes some time. Are you waiting that long?
mariosraptor said:
any rom that i install is not getting beyond the bootlogo. i had xxki3 stock with cf-root xxki3 kernel.
every install i make full wipe on everything before(data, cache, dalvik).
any body any idea?
only stock rom working.
Click to expand...
Click to collapse
1. Enter Clockworkmod recovery
1a. Do a Backup (not a must, but i suggest) from the cwm recovery of your current rom/settings.
2. Wipe Data/Cache Factory reset
3. Flash the new rom you want
4. Again (not needed but well..) Wipe Data/Cache Factory Reset
5. Wipe Cache
6. Advanced -> Wipe Dalvik Cache (this is why you get bootloops)
7. Reboot to system
Wait 4-5 minutes and you will have your new, shiny working rom.
Hope it helps, cheers
yes. more than 10 minutes.
kanefox said:
The first boot takes some time. Are you waiting that long?
Click to expand...
Click to collapse
i am not getting any bootloops. it just gets stucked at the first screen with the triangle.
i have no experience in samsung but i have done all that you mention.
still no luck. i will try once more and let you know in about 20 minutes.
thanks for your help.
rembrandtlnx said:
1. Enter Clockworkmod recovery
1a. Do a Backup (not a must, but i suggest) from the cwm recovery of your current rom/settings.
2. Wipe Data/Cache Factory reset
3. Flash the new rom you want
4. Again (not needed but well..) Wipe Data/Cache Factory Reset
5. Wipe Cache
6. Advanced -> Wipe Dalvik Cache (this is why you get bootloops)
7. Reboot to system
Wait 4-5 minutes and you will have your new, shiny working rom.
Hope it helps, cheers
Click to expand...
Click to collapse
Mh strange, the strange is.. with the stock rom is working.
Looks like your phone dosnt like the rom you are flashing so the quesion now is:
Are you sure, you are flashing a rom your phone can read? I know the i9100G and the AT&T versions cant be flashed with the standard (i9100) S2 roms (there is a specific thread i think here on xda for those versions)
mine is an unbranded i9100 from Greece. i am flashing the correct roms.
rembrandtlnx said:
Mh strange, the strange is.. with the stock rom is working.
Looks like your phone dosnt like the rom you are flashing so the quesion now is:
Are you sure, you are flashing a rom your phone can read? I know the i9100G and the AT&T versions cant be flashed with the standard (i9100) S2 roms (there is a specific thread i think here on xda for those versions)
Click to expand...
Click to collapse
the same. more than 15 minutes of waiting time. flashing stock again.
Im sorry cant rly help you then, let's wait for some more experienced user answer
thanks. no worries. stock is good. matter of speaking
rembrandtlnx said:
Im sorry cant rly help you then, let's wait for some more experienced user answer
Click to expand...
Click to collapse
next time when u flash try formatting system.
In CWM >mounts and storage> format system
Please state detailed steps you did when flashing a ROM and what kind of ROM.. That will help alot on trouble shooting your problem.
Sent from my GT-I9100 using xda premium
every body read first post managed to solve this.
Hi was there a solution to this problem as I seem to get it with EVERY rom I try to install from zip?
Hi to all, this is my first Post and this is my First Android I come from an iPhone 2G, iPhone 3g, iPhone 3GS and my last phone was an iPhone 4!!! now I'm extremely happy with my new SGS2!!!
I have been searching a lot!!! for a solution for this flash loop issue,
1 - I have flash to a stock 2.3.5 KI3 samfirmware,
2- then I have Odin>PDA>cf-root-KI3-4.2.tar to root my phone.
3 - After that I downloaded 3 custom roms, DarkyROM2_KI3, VillainROM-3.0.0-signed and Cyanogen cm_galaxys2_full-112. put them on my root internal sdcard.
4 - booted to ClockworkMod Recovery menu.
5 - Wipe Data/Factory Reset
6 - Wipe Partition Cache.
7 - Install Zip from sdcard.
and every thing seems ok, but when i restart, it stays on the boot loop, even if i manage to enter to CWM Recovery menu it says that E: Can't Mount ... bla bla bla
I had been trying to put a custom rom so much that my binary counter is now on 10
I'm going to try what you wrote on the first post!
Restore to stock KI3 firmware using pit file and repartition.
after that install the cf-root kernel. Restart and try to install any custom firmware.
Hope it works
Not it did not work, Maybe the problem was Wipe Partition cache after installing new rom, going to stock and repeating
I'm having this exact same problem, please post here if you find an answer to your problem.
I first installed checkrom with no problems, then i decided to wipe and try install dlevrom but after rebooting i'm left with the same problem as above.
It's only when i flash stock 2.3.5 KI3 through odin with pit, repartition, all checked that my phone works.
I then repeat the steps of flashing cf root through odin and then try flash a custom rom, either checkrom or dlevrom and neither work.
Another try another fail!
I have no idea on what else can I do!!! tried again and nothing! I tied cf-root 4.1 and nothing and cf-root 4.2 and nothing!.
I'm having this exact same problem, please post here if you find an answer to your problem.
I first installed checkrom with no problems, then i decided to wipe and try install dlevrom but after rebooting i'm left with the same problem as above.
It's only when i flash stock 2.3.5 KI3 through odin with pit, repartition, all checked that my phone works.
I then repeat the steps of flashing cf root through odin and then try flash a custom rom, either checkrom or dlevrom and neither work.
Click to expand...
Click to collapse
After i got the stuck on boot! I can restore to stock by only using the PDA, I don't need to set the pit file again!, but I'm usign all the files on Odin to see If that makes any difference but nothing!!!
I wonder how mariosraptor did it!!!! Can you throw us a light???
I have explained it on first post. Just follow step by step the first post directions.
Sent from my GT-I9100 using xda premium
Nope it didn't work
The steps I did:
1. Restore to stock using PIT, PDA, PHONE, CSC.
2. After it boots root the phone with cf root 4.1 for ki3
3. Use CWM Recovery to flash the new rom on internal sdcard.
I have been doing it with wipe data, wipe cache, wipe develk.
Nothing is there a step that im missing?
Thanks
SOLVED!!!!!! JAJAJA
The only problem, was one minor thing, a little thing called Bootloader!
I installed the old bootloader!
find it here: http://forum.xda-developers.com/showthread.php?t=1075278
And after that every thing worked perfectly, no boot loops!!!!
Hope it helps!!!
I have a sch-i500 that is rooted with cwm working.
I am very interested in running liquid smooth v 2.9 found here: http://forum.xda-developers.com/showthread.php?t=2245120
so I did a format, wiped the cache and davlik. when I installed the zip from external sd card the phone immediately gave me a screen for CWM v 6.0.3.3.
I can still navigate and restore old back ups but the phone does not go past the Samsung logo on the boot screen. Any advice is appreciated.
I was previously running stock 2.3.5 E09 if that helps
http://forum.xda-developers.com/showthread.php?t=1026746
seems to be the best way for me to recover from this (looks like I flashed a non voodoo rom without removing voodoo) but I am unable to get the phone into download mode with or without the battery in the phone.
please help......(update) Alright, I am a moron. needed to have a powered usb port. on my way to recovery. thanks for having all this great info in one place.
aircooledbusses said:
so I did a format, wiped the cache and davlik. when I installed the zip from external sd card the phone immediately gave me a screen for CWM v 6.0.3.3.
I can still navigate and restore old back ups but the phone does not go past the Samsung logo on the boot screen. Any advice is appreciated.
I was previously running stock 2.3.5 E09 if that helps
Click to expand...
Click to collapse
Oh so close.
When coming from 2.3.x ROM you will need to flash the rom (liquid: or other 4.2.x) you will need to flash 2 more times...
The 1st flash get you into the new recovery only,,, as you found out.
2nd flash will pop up with an error message about incompatible partition and telling you to re-flash again,,,
So 3rd flash actually installs your new ROM
Then install a current/compatible Google gapps
.
Enjoy
.
Thank you, I am getting closer.
still on the second and third flash of the rom I get a satus 7 error which I think is a bootloader issue.
I have flashed the GBbootloader.tar through odid to no avail and am following Section:4 How to flash any ICS 4.0.x & 4.x.x JellyBean based rom
http://forum.xda-developers.com/showthread.php?t=1238070
anythoughts?
aircooledbusses said:
Thank you, I am getting closer.
still on the second and third flash of the rom I get a satus 7 error which I think is a bootloader issue.
I have flashed the GBbootloader.tar through odid to no avail and am following Section:4 How to flash any ICS 4.0.x & 4.x.x JellyBean based rom
http://forum.xda-developers.com/showthread.php?t=1238070
anythoughts?
Click to expand...
Click to collapse
what does the error say besides status 7?
did you odin the CWM4 fixed for cm7 then install the ROM 3 times?
can you get a pic up for us to see?
just to be sure......using odin, I repartitioned with the pit, and flashed a E03 rom. rebooted the phone fine.
flashed the CWM4 fix for 7 and redid the GB bootloaders as well.
went into recovery and factory reset, wiped cache, and dalvik.
installed liquid-JB-v2.7-Official-fascinatemtd.zip this time first time took me directly to clockwork where I flashed again. prompted with install from sdcard complete. repeated and got same message.
factory reset, wipe, wipe and flashed gapps. Everything seems to have worked this time with the v2.7Official instead of 2.9. I will play with this for just a bit and probably try it again tonight with a fresh downloaded copy of v2.9. I really do appreciate your assistance and help and I would not have gotten this far without the forum.
update:
flawless installation of v2.9 since 2.7 was already installed. (installed via cloclwork mod recovery)
It was most likely an operator error that prevented me from installing 2.9 after E03. But I don't see the benefit of going back to recreate why it didn't work. Thanks again all is good and right.
So I have been rooting and customizing phones for a while now, but this one has me totally stumped.
Running A Sprint Note 3, I used auto root to root the phone. Using CWM recovery and both install fine.
These are the steps I took:
wipe data/factory reset
wipe cache partition
wipe dalvik cache
format system
format data
format cache
reboot back into recovery and then install Sacs Rom from zip
It installs fine when it reboots it hangs on the Samsung splash screen
I have let it sit for hours and it does not move.
Any help and advice would be great.
First, we need to know which sacs rom 4.4 you are referring to there is more than one. Next we need to know what version of KitKat you are running. The first thing I would do is get fresh download of the sacs rom. To eliminate the possibility of a bad download the first time. Next pick another rom try and flash that one. Eliminate the possibility of a bad recovery install.
I run stock, rooted, KK 4.4.2 NC5 with Philz custom recovery, version 6.12.9
If you want a stock copy of NC5 here is the link http://forum.xda-developers.com/showthread.php?t=2712205 if you need a copy of the recovery here is the link https://goo.im/devs/philz_touch/CWM_Advanced_Edition/hltespr/ to root I used SuperSu v 2.02 is the latest version here is the link http://forum.xda-developers.com/showthread.php?t=1538053 and from your post you already have Odin but I use version 1.85 here is the link http://www.downloadodin.info/download-odin-1-85
Remember, once you are at KK 4.4.2 NC5 the custom rom that you are going to install has to have a kernel that is compatible with NC5 and it's bootloader.
I installed one latest firmwares to try it, and hate it. Anyway I went to install CM13 even blisspop and it won't install and gives error 7. I can odin stock rom but can't flash any asop is my sm-g900T dead lol.
enzodad said:
I installed one latest firmwares to try it, and hate it. Anyway I went to install CM13 even blisspop and it won't install and gives error 7. I can odin stock rom but can't flash any asop is my sm-g900T dead lol.
Click to expand...
Click to collapse
Are you doing a full wipe before installing any AOSP ROM? I.e. in TWRP, there is an option for Advanced Wipe. Before your first time installing any AOSP ROM, coming from stock ROM, you must wipe system, data, cache, and dalvik. Also when you say latest firmware, you mean FOL1, right? Because that's the latest. Finally, are you using the right ROM file. This phone's development codename is klte, as opposed to kltespr, kltedv, kltevzw, klteusc, etc.
thisisapoorusernamechoice said:
Are you doing a full wipe before installing any AOSP ROM? I.e. in TWRP, there is an option for Advanced Wipe. Before your first time installing any AOSP ROM, coming from stock ROM, you must wipe system, data, cache, and dalvik. Also when you say latest firmware, you mean FOL1, right? Because that's the latest. Finally, are you using the right ROM file. This phone's development codename is klte, as opposed to kltespr, kltedv, kltevzw, klteusc, etc.
Click to expand...
Click to collapse
Yes I've install hundreds of roms on this phone, I know it's klte I do a full advanced wipe in twrp
I believe it was FOL1- I've never had a problem before. Figured maybe new firmware made impossible flash asop or something.
enzodad said:
Yes I've install hundreds of roms on this phone, I know it's klte I do a full advanced wipe in twrp
I believe it was FOL1- I've never had a problem before. Figured maybe new firmware made impossible flash asop or something.
Click to expand...
Click to collapse
I googled it and error 7 is a problem with the assert. So double check you have the correct ROM file, then edit the first line or two out of the updater-script (located in META-INF/com/google/android/)
So this is my first post, but whatever.
So it's safe to say I screwed up, I accidentally deleted my stock (rooted) Samsung OS. I somehow managed to download Paranoid Android 6.0.1 onto the Samsung Galaxy S3 GT-I9300 I received. I heavily dislike Paranoid Android, and I would like to give Cyanogen 14.1 a shot. The problem is since I wiped everything, every time I do a factory reset for my device, it goes into a bootloop, even if I flashed CM 14.1.
I have TWRP installed, if that helps, and all files (that I know of) are installed on my computer (Odin, CM14.1 ZIP, and Paranoid is backed up).
I'd like to thank everyone who even comes and reads this thread, and I'd be very grateful if I managed to get CM 14.1 on the Samsung Galaxy S3 GT-I9300.
Which version of TWRP is installed? If you have 2.87, try 3.02. Are you performing a full system and data wipe before installing cm14.1?
Hi bro
I am agree with the first reply to you.
All You need the official CM14.1 ROM
Download here https://download.cyanogenmod.org/?device=i9300
And then download Gapps for android 7.1 pico
Download here http://opengapps.org/
If yoy havn't twrp recovery ! Download it from here
https://dl.twrp.me/i9300/
The file end with (tar) it flashing with Odin.
And the file end with (img) it is update from other version to new with Flashify app (you can find the app in playstore free)
Now You have all requirements files
Let's flashing Your device:
Move the files to Ext.sdcard
Make sure you have 80% battery charge
Then reboot your device to (recovery mode)
Turn off your device and Push (Power+home+volume up) keys at the same time for 5 sec untill u see the recovery icon
Now go to wipe your phone choose advance wipe check the dalvilk + cache + system + data + inernal storage ,, done
Now go back and choose install
Search to your Ext.sdcard then choose the CM14.1 at the same time click on Add more zips
And choose Gapps 7.1 pico
Now swipe to flash
Wait to flash finish and then click on Reboot system
Done
Good luck
audit13 said:
Which version of TWRP is installed? If you have 2.87, try 3.02. Are you performing a full system and data wipe before installing cm14.1?
Click to expand...
Click to collapse
I'm using the latest TWRP, I made sure to install the latest one, and I'm performing a full data and system wipe before I install CM14.1. My question is does it HAVE to be on an external SD card, because I just port it over to a folder in my internal SD card.
It can be installed from the internal memory. Simplest way would be to boot into TWRP, mount storage, copy over CM and gapps, and flash.
Maybe try TWRP 2.87?
audit13 said:
It can be installed from the internal memory. Simplest way would be to boot into TWRP, mount storage, copy over CM and gapps, and flash.
Maybe try TWRP 2.87?
Click to expand...
Click to collapse
I've tried to do that multiple times, but everytime I try it, the S3 goes into a bootloop.
Due to the bootloop issue, I would flash a stock ROM with Odin, perform a factory wipe from stock recovery, and then see if the phone will boot properly.
Is the phone a gt-i9300 in download mode?
audit13 said:
Due to the bootloop issue, I would flash a stock ROM with Odin, perform a factory wipe from stock recovery, and then see if the phone will boot properly.
Is the phone a gt-i9300 in download mode?
Click to expand...
Click to collapse
Yeah, I managed to install the stock OS. I also tried to install CM14.1 again, following the instructions to the letter, but still no CM build. I have no idea what I'm doing wrong, since I've read multiple threads on XDA and the CM site.
Not exactly sure what you mean by in download mode, since I'm new to all this rooting business.
You need download mode to flash a stock ROM; otherwise, Odin can't install a stock ROM.
audit13 said:
You need download mode to flash a stock ROM; otherwise, Odin can't install a stock ROM.
Click to expand...
Click to collapse
Oh if that's the case, then yes. I put it in Odin mode to flash the stock ROM.
Okay, just to confirm but these are the major steps you took:
flashed the latest stock ROM to the phone;
flashed the latest tar version of TWRP using Odin;
booted into TWRP and copied CM14 to the internal memory or an SD card;
wipe data, system, and cache in TWRP;
flash CM14 in TWRP and rebooted.
Yup, those are the exact steps I took. I think I'm just going to tinker around with the Samsung a little longer, until I manage to brick it, or I'll just continue doing research. I'm already happy I managed to get out of a boot loop on my own, with and without OS.
Are you in Canada? Where did you get the i9300? The i747m is sold in Canada and the i747 is sold in the USA.
audit13 said:
Are you in Canada? Where did you get the i9300? The i747m is sold in Canada and the i747 is sold in the USA.
Click to expand...
Click to collapse
My dad got it for his work during his visit in Turkey, is that a factor during flashing of new OS's? What surprises me is that I could install Paranoid Android 6.0.1 onto it without an OS with little or no problem.
A pre-existing OS on the phone is not a requirement to flash a custom ROM.
As long as the ROM is for the i9300, you should be fine.
audit13 said:
A pre-existing OS on the phone is not a requirement to flash a custom ROM.
As long as the ROM is for the i9300, you should be fine.
Click to expand...
Click to collapse
I made sure it was for the i9300. I'm confused to where it doesn't work because I would see the CM battery charging logo, but when I wanted it to boot, it kept bootlooping for 10 minutes on end. The longest I've let it run was whilst I was sleeping, 8 hours, still nothing.
Maybe try a different version of CM14.1 or a different version of TWRP.
audit13 said:
Maybe try a different version of CM14.1 or a different version of TWRP.
Click to expand...
Click to collapse
I'll give those options a shot. I'll try out clockwork and see. I guess I'll keep going until I brick it. Thanks for aiding me, and enjoy having a happy new year.