Hello.
I decided to flash the new CM10 on my GS3 tonight and I ran into a problem
i was following the steps here:
http://forum.xda-developers.com/showthread.php?t=1762709
Step 2: Download and open the EZ recovery app from HERE (If your coming from section 1 or 2 and already have a custom recovery, reboot recovery and skip to step 4).
Step 3: Open app, select CWM recovery, then tap the pulldown menu, choose CWM 6.0.1, select flash, then reboot recovery.
Step 4: From CWM recovery, Perform a nandroid backup from the "backup/restore" menu(Optional but recomended).
Step 5: Wipe data/factory reset, then under the "mounts & storage menu" Format System.
Step 6: Navigate to "install zip from sdcard", from there "choose zip from sdcard", and finally install the rom you downloaded in step 1 part A.
Step 7: Again, Navigate to "install zip from sdcard", from there "choose zip from sdcard", and finally install the gapps package you downloaded in step 1 part B.
I downloaded the ROM i wanted and I got to step 6 and I forgot to download the Gapps file.
IN CMW i went back and rebooted the phone after i wiped the data off it and everything, I thought this would just boot to stock ICS.
Now my phone will not boot up and it just stays in the GS3 logo screen.
I was wondering if there is a manual way that i could just make it boot into the old ICS so i can place the Gapps file back on my SD card?
Or is my device bricked?
Please let me know.
Thank you
Just go back into CWM and flash the ROM you downloaded. Once its flashed wipe data/cache again then go to advanced and fix permissions. Then boot into your new ROM, it will take a little while to boot into it because it will be like the first time you turned your phone on and set it up after you got it. I really don't know why your phone is getting stuck at the boot screen but....
Anyway once you have booted into your new ROM use the browser and go download the gapps you need and reboot into recovery, wipe data/cache, flash gapps, go into advanced and hit fix permissions again (it will take longer this time), and reboot.
Just a heads up, if you downloaded a version of EZ Unlock above 1.2 then you will have to go back to stock via Odin ( if you're on PC) because versions above 1.2 don't really unlock your bootloader so it causes a soft brick. If you used 1.2 or any version before it then you should be fine. But if you get a message after you flash your rom that says something about not being approved by Verizon and please take it to your nearest store well you didn't unlock your bootloader. If you get that message just use Droidstyle's guide to go back to stock via Odin and then start over again.
As long as you used a EZ Unlock 1.2 or lower you will be OK to flash your ROM, reboot into ROM, download gapps, reboot into recovery, flash gapps, etc. Just use the steps above and all should be fine.
Sent from one of the many Anthropomorphic Personalities on the Disc
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank You for your cooperation
Friendly Neighborhood Moderator
Thanks!
shangrila500 said:
Just go back into CWM and flash the ROM you downloaded. Once its flashed wipe data/cache again then go to advanced and fix permissions. Then boot into your new ROM, it will take a little while to boot into it because it will be like the first time you turned your phone on and set it up after you got it. I really don't know why your phone is getting stuck at the boot screen but....
Anyway once you have booted into your new ROM use the browser and go download the gapps you need and reboot into recovery, wipe data/cache, flash gapps, go into advanced and hit fix permissions again (it will take longer this time), and reboot.
Just a heads up, if you downloaded a version of EZ Unlock above 1.2 then you will have to go back to stock via Odin ( if you're on PC) because versions above 1.2 don't really unlock your bootloader so it causes a soft brick. If you used 1.2 or any version before it then you should be fine. But if you get a message after you flash your rom that says something about not being approved by Verizon and please take it to your nearest store well you didn't unlock your bootloader. If you get that message just use Droidstyle's guide to go back to stock via Odin and then start over again.
As long as you used a EZ Unlock 1.2 or lower you will be OK to flash your ROM, reboot into ROM, download gapps, reboot into recovery, flash gapps, etc. Just use the steps above and all should be fine.
Sent from one of the many Anthropomorphic Personalities on the Disc
Click to expand...
Click to collapse
Thanks for the information!
I got it to work somehow but this is what I did.
I got it to boot via CMW and restored the backup that I first created. Then i downloaded the Gapps file and placed it on Sd card and just continued the steps on the tutorial.
Luckly the tutorial asked me to download 1.2 so that is what I did and I am glad that I did it.
Thanks for the help but I have JB 4.1.2 installed and everything seems to be working fine.
Just so you know some ROMs like Paranoid work best if you flash the ROM boot and let it settle for 30 mins and then rebbot into recovery and then flash gapps and fix permissions. If I had know you had made a CWM backup I would have just told you to restore that, I must have just missed that part in the OP. Either way, its not always a necessity to flash your gapps with the ROM, I always boot into the ROM and let it settle first and then flash em. I also wipe data/cache/dalvik, if I am flashing a ROM, or just cache/dalvik, if just gapps or similar, 3 times.
I am happy everything worked out for you. Sport I wasn't of more help sooner
Sent from one of the many Anthropomorphic Personalities on the Disc
shangrila500 said:
Just so you know some ROMs like Paranoid work best if you flash the ROM boot and let it settle for 30 mins and then rebbot into recovery and then flash gapps and fix permissions. If I had know you had made a CWM backup I would have just told you to restore that, I must have just missed that part in the OP. Either way, its not always a necessity to flash your gapps with the ROM, I always boot into the ROM and let it settle first and then flash em. I also wipe data/cache/dalvik, if I am flashing a ROM, or just cache/dalvik, if just gapps or similar, 3 times.
I am happy everything worked out for you. Sport I wasn't of more help sooner
Sent from one of the many Anthropomorphic Personalities on the Disc
Click to expand...
Click to collapse
Thanks for the help.
I have another question..I installed the "stable" version of CM10 from their website and ever since I installed it i have noticed that my signal is not as strong as it was before.
Is there anything else that I need to do to the phone to increase signal strength? I usually have around 3-4 bars in my house now i have one. At work i used to get 2 bars now I have none.
Let me know if you can help with this.
Thank you
Itzvik said:
Thanks for the help.
I have another question..I installed the "stable" version of CM10 from their website and ever since I installed it i have noticed that my signal is not as strong as it was before.
Is there anything else that I need to do to the phone to increase signal strength? I usually have around 3-4 bars in my house now i have one. At work i used to get 2 bars now I have none.
Let me know if you can help with this.
Thank you
Click to expand...
Click to collapse
Try flashing the latest vrblj1 radio. No need to do anything special, just follow the radio portion of section 6. Fyi you dont ever need to wait to flash gapps or wipe everything 3 times...what the guide says is what works best. Trust me i have tried every method imagineable.
droidstyle said:
Try flashing the latest vrblj1 radio. No need to do anything special, just follow the radio portion of section 6. Fyi you dont ever need to wait to flash gapps or wipe everything 3 times...what the guide says is what works best. Trust me i have tried every method imagineable.
Click to expand...
Click to collapse
It may have worked for you, but a lot of people on the PA thread have had problems with it when they flash gapps right after the rom without rebooting in between, just trying to help the OP before he gets started crack flashing. The first time I flashed PA on this phone I did rom + gapps and when.I rebooted everything was buggy as hell, so I did reboot into recovery and fixes permissions and when I rebooted it showed a screen that said Activating Please wait. Every single time I rebooted I got that screen, that is just the most annoying bug that I experienced with that flash, and when I asked for help I was told to flash ROM, reboot, then go into recovery and flash gapps and fix permissions.
On Liquid on the other hand I never experienced any problems whatsoever with flashing the ROM and gapps in the same session, but for ROMs that I have never used before I flash rom, reboot, flash gapps, fix permissions, reboot and go. I also flash 3 times because I uber paranoid about stuff being left over from whatever ROM I was running, and I did experience problems with stuff being left over when using CWM 6.0.1.2 when flashing and just wiping everything once so I Odined back to stock, which I learned thanks to you and your guide which I love btw, and then rooted, unlocked, and flashed TWRP this time since CWM wasn't working for me. And even with TWRP I wipe everything 3x now just to be extra cautious because I don't want a repeat of that episode.
I hope you don't take this the wrong way droidstyle, I'm not trying to start a fight like so many others on the forums do, just sharing what's happened to me and my phone and trying to help others. I learned everything I needed to know about flashing ROMs on a phone that has its bootloader unlocked from your thread. It is the most comprehensive thread I have seen for noobs about flashing and everything else. Thank you so much for it!
Also to the OP's question about service, I have flashed every radio and have never gotten better signal in AOSP roms, the connection was better but it didn't actually get stronger. I have 2 more 3g bars on TW ICS and I have 1 on AOSP. You should definitely go to the newer radio and test it out, but I've never seen an increase on my phone, but that all depends on where you are and how good your towers are too.
Sent from my SCH-I535 using Tapatalk 2
droidstyle said:
Try flashing the latest vrblj1 radio. No need to do anything special, just follow the radio portion of section 6. Fyi you dont ever need to wait to flash gapps or wipe everything 3 times...what the guide says is what works best. Trust me i have tried every method imagineable.
Click to expand...
Click to collapse
Thanks!
if its not to much to ask can you link me to a tutorial and the radio version that you are talking about?
I would like to do this tonight when I get home.
Thanks,.
Itzvik said:
Thanks!
if its not to much to ask can you link me to a tutorial and the radio version that you are talking about?
I would like to do this tonight when I get home.
Thanks,.
Click to expand...
Click to collapse
Download the top radio here, it will be VRLJ1 like droidstyle said:
http://rootzwiki.com/topic/34053-of...zon-sgs3-sch-i535-odin-or-recovery-flashable/
The only radio tutorial you will need is on droidstyles guide, not sure what step but I know its there. Just download the Recovery Installable version of VRLJ1, also download the rpm for VRLJ1 there is a link right above the modem downloads. No one really knows for sure if the rpm are necessary for sure of not from what in have read but I always flash the corresponding one when I flash a new radio.
Also if you want to try out the other radios and see if they give you any better service, sometimes they will depending on area but so far the newest is the best so far for me, just go to the website above and download any of the Recovery Installable radios and their corresponding rpm's just like this one and flash it. There is no reason to clear data or cache when flashing as that won't be affected. Also you only need to flash the radio once. It stays no matter what ROM/anything else you flash.
Sent from one of the many Anthropomorphic Personalities on the Disc
RPM
Is there a difference between the RPMS?
the most downloaded RPM is the VRBLJ1 yet the radio is named VRLJ1.
Let me know because I am ready to flash this radio!
Thanks!
You download the rpm that matches the radio you want to flash. So you want to flash the VRLBJ1 radio you also wanna flash the VRLBJ1 rpm.
I think maybe invisiblek misnamed the files or maybe I'm missing something. Either way for that radio that you have get the latest rpm which is VRLBJ1
Sent from one of the many Anthropomorphic Personalities on the Disc
I just flashed the new radio and RPM provided in the links above and it seems like nothing changed. I checked the radio version in the settings and it is matching what I flashed but still service is still terrible 1 or two bars.
any other ideas on what I should do?
That's the same way it is with mine, but when I flash the new JB leak it works way way better, service wise, than even stock TW did. I have better overall service and I have not lost service or had to continue resending texts cause they won't go through, like on AOSP ROMs.
Things are supposed to get better, data wise, when the Ril and a few other things are incorporated from TW JB. I had read, before the leak, that service will be better on AOSP ROMs because they would be able to incorporate the leaks RIL. Now after there has been a TW JB leak I have read that the devs are waiting on the JB source code from Samsung so they can incorporate the Ril. I don't know which it is, I have seen one dev post he was waiting on a JB TW leak for the ril but it was a dev working on a TW ROM soooo..... I haven't seen an update to any of my favorite ROMs since the before first leak came, I'm talking about MIUI, Paranoid, and Liquid, so I don't know if they are in fact working on incorporating the Ril or if they are just taking longer than usual.to put out an update cause they're working on bugs. They could've also been waiting on the 4.2 source code to come out, I really don't know.
That's pretty much the long way of saying there's no way to get better service on AOSP that I've been able to find, all the radios have done for me have made the 3g/4g handoff a little better and faster. Hopefully the AOSP ril will get better soon and we can have as good of service as we have on the TW JB leaks.
Sent from one of the many Anthropomorphic Personalities on the Disc
Well thanks anyway.
I just installed the latest version and left it at that..hopefully CM10 improves and sends out a new update to fix a few bugs that I have found.
They post nightlies every night, so hopefully someone will post some code for bugfixes on their github that will be incorporated and we can have better working AOSP!
Sent from my SCH-I535 using Tapatalk 2
Related
I soft bricked my phone playing with ICS, I got a JIG and solved the problem
I can now ODIN back to any version and once rooted I can install any samsung based rom, the problem comes when I try to flash aosp both CM7 and any ICS beta
What happens is I select the zip, it runs a script and the phone reboots, I see the AT&T logo and then it mounts the sd card, it says it can't find the zip file.
I've tried Froyo, Eclair, even gingerbread (I know your not supposed to flash cm7 from gingerbread, I'm just running outta ideas) I have froyo bootloaders, I reinstalled them with heimdal. I've also done a master clear and erased the internal sd card
Does anyone have an idea of why this is happening?
Are you trying to install the zip from ClockworkMod?
Most likely, the rom is incompatible with the flash method you are choosing which bricks your phone. I had this happen to me twice from either flashing a rom the wrong way or just trying to flash the wrong rom all together and killing my system, but I ended up telling AT&T Techs that it happened when I tried upgrading to 2.2 to avoid warranty issues and they replaced my whole device with a refurbished unit =]
However keep in mind that they cannot jig your device and you will have to do that yourself to get your data off your device before you try getting a new one via this method.
Possible Solution:
1. If you can, flash cm7 to your device
2. Flash This ICS rom
http://forum.xda-developers.com/showthread.php?t=1363760
If you have already tried this then I apologize, but I hope this helps.
Another problem
Ok, everything I see says I should flash from a captivatemtd recovery, but when I install Rom manager and select captivatemtd, it says their are no offical recoveries for it, I'm currently running cognition froyo 2.2 with froyo bootloaders
Does anyone know where I can manually get the captivatemtd CWM? and how do I install it?
kataishin said:
Most likely, the rom is incompatible with the flash method you are choosing which bricks your phone. I had this happen to me twice from either flashing a rom the wrong way or just trying to flash the wrong rom all together and killing my system, but I ended up telling AT&T Techs that it happened when I tried upgrading to 2.2 to avoid warranty issues and they replaced my whole device with a refurbished unit =]
However keep in mind that they cannot jig your device and you will have to do that yourself to get your data off your device before you try getting a new one via this method.
Possible Solution:
1. If you can, flash cm7 to your device
2. Flash This ICS rom
http://forum.xda-developers.com/showthread.php?t=1363760
If you have already tried this then I apologize, but I hope this helps.
Click to expand...
Click to collapse
I can't flash cm7 either
movielover76 said:
Ok, everything I see says I should flash from a captivatemtd recovery, but when I install Rom manager and select captivatemtd, it says their are no offical recoveries for it, I'm currently running cognition froyo 2.2 with froyo bootloaders
Does anyone know where I can manually get the captivatemtd CWM? and how do I install it?
Click to expand...
Click to collapse
I'll go over my method of installing(I've had ZERO issues flashing from/to any ROM)
1. I FTS/MC using Odin 1 Click. My phone build is 1008
2. Root with 1 click root(I have to do steps 2 and 3 because I do not have 3 button recovery)
3. Sideload and install ROM Manager(Rom manager, and CWM update.zip are in the Sideload zip that's attached)
4. Copy CWM Update.zip and ROM to device. Reboot and install CWM
5. Reboot into recovery and install ROM
Odin 1 Click(If you can use it)
http://dl.dropbox.com/u/12100225/Odin I897UCJF6-final-OCD-REV0.zip
Root 1 Click
http://dl.dropbox.com/u/12100225/Root.zip
Sideload Wonder Machine and ROM Manager
http://dl.dropbox.com/u/12100225/Sideloading.zip
Edit** What is the build number of your phone?
Here's what you need
Just download this rom
http://download.cyanogenmod.com/get/cm_captivatemtd_full-181.zip
And then watch this video!
http://www.youtube.com/watch?v=iBPu-GqM9RE
Flash CM7 using odin
then flash ICS using clockwork mod using the instructions I gave you before.
That's the easiest way I found to do it and that's how I went from stock rom to CM7 rom and then finally to ICS
kataishin said:
Most likely, the rom is incompatible with the flash method you are choosing which bricks your phone. I had this happen to me twice from either flashing a rom the wrong way or just trying to flash the wrong rom all together and killing my system, but I ended up telling AT&T Techs that it happened when I tried upgrading to 2.2 to avoid warranty issues and they replaced my whole device with a refurbished unit =]
However keep in mind that they cannot jig your device and you will have to do that yourself to get your data off your device before you try getting a new one via this method.
Possible Solution:
1. If you can, flash cm7 to your device
2. Flash This ICS rom
http://forum.xda-developers.com/showthread.php?t=1363760
If you have already tried this then I apologize, but I hope this helps.
Click to expand...
Click to collapse
Tried this to the letter still doesn't work, could it be because of rom manager not finding a recovery for captivatemtd, some pages say I need that recovery but it isn't available in rom manager.
Finnally
Finnally got CM7 installed the problem was I had to do the three button boot into recovery twice, the first time updates clockworkmod to version 5.x
Now to try ICS again, wish me luck
Thanks
Thanks for all the suggestions, the tip in the video about flashing the speedmod kernel did help I think, I've successfully flashed
teamhacksung's ICS Port for Captivate (BUILD 9) again.
A couple notes here:
1 when your flashing cm7 from cwm( NOT 3e RECOVERY THOUGH) you need to flash the. Zip file, then reboot system, IT WILL PROBABLY BOOT LOOP, three button back to recovery and flash again, then while in recovery still flash gapps. Reboot and it will install fine. You should ONLY need to do the two time flash the first time going to cm7.
2. When you go to rom manager and choose manual flash overide from hitting the menu button you will get the unsupported recovery, DON'T WORRY about it and hit ok. Then another popup will come up and choose 3.x and it will work.
Sent From My KickAss ATT SGS2 SPORTING CM7
I tried to flash a aokp rom and before flashing made a back up. Now when I flashed the rom and rebooted the phone im stuck at samsung boot. I can get into recovery. At first it was a messed up recovery i tried to get to an old rom and reinstalled inimitable on reboot still stuck at samsung but can get into red recovery. Backup when reinstalling says cant mount system/! please help me asap I cant do anything I need my phone I am in panic mode.
Have tried reflashing The ROM again...or if you just want to go back to stock see my signature for links to the one click method
...btw your in the wrong section to post this...
The OP for aokp does state to flash twice...did you?...first time with wipes, then you can pull battery ...go back to cwm and reflash...again.
going back to stock is your way. clear all that crap out
http://forum.xda-developers.com/showthread.php?t=1524081
Post one to stock.....
Post two to put cwm back on....
Read with detail...the thread I provided....
Your probably going to need to go back to stock, but just so you know, flashing any ICS rom while on Gingerbread bootloaders will get you a "Messed up recovery" You'd have to flash ICS bootloaders, but doing that means you can't flash any non ICS roms, I personally still have a rainbowed recovery on the off chance I want to flash GB rom.
soulysephiroth said:
Your probably going to need to go back to stock, but just so you know, flashing any ICS rom while on Gingerbread bootloaders will get you a "Messed up recovery" You'd have to flash ICS bootloaders, but doing that means you can't flash any non ICS roms, I personally still have a rainbowed recovery on the off chance I want to flash GB rom.
Click to expand...
Click to collapse
We have no ics boot loaders...froyo boot loaders make the recovery look funky...gingerbread boot loaders fix that problem and can be used with froyo, gingerbread and ics ...not trying to be rude or a jerk just informing you
Sent from my SGH-I997 using XDA
Actually the "messed up" or rainbow recovery is from the lack of gingerbread boot loaders, just figured this out this morning when I attempted to flash aokp uniporn. Once I did the heimdall one click with bootloaders checked (gingerbread boot loaders) I was able to successfully flash the aokp rom and recovery works perfectly. Its really better not to reply when one does not know what they are talking about oh and I was still able to reflash a gingerbread rom as well although I probably won't go back to gingerbread again since aokp is the **** and runs super smooth
Sent from my SGH-I997 using xda premium
Please move this thread from the Development Section.
edit- Thanks for moving it.
Sorry about posting so quickly in wrong section. I just know the guys who post in here are pros. I used heimdall and everything is back to stock, no superuser. Should that be right, am I now not rooted? I havent tried to boot into recovery, but I think I have it still. Can I just follow root methods if I want to go back to root? Thanks again.
I my experiences, I've noticed our phones use a form of "Cumulative" Upgrade system, where You have to essentially go from Froyo to GB to ICS or things go haywire when you actually start using your ICS Rom..
I've tried using Heimdall to flash back to stock, but it doesn't seem to fix all my files from time to time, so I still use GTGs Ultimate Unbrick, and once it starts up as you're in Recovery Mode do a Factory Reset/Wipe Cache Partitions, it helps with not having the "Google Authentication Failed".
It's a long process from start to finish either way, so i figure save yourself the hassle for the long run and wipe it fresh...
I used heimdall without clicking the GB bootloaders checkbox. Upon reboot after sucessfully flashing everything, my phone shows the rainbow color thing then boots normally. I have no seen any issues other than that, however I only got it back up and running about an hour ago. I will see as the day progresses what happens. I just would like to know where I go from here to reacquire root priveleges. When I try to boot into recovery with the button combo I get a rainbow colored screen and nothing else showing, should I re-run heimdall with gb bootloaders box checked?
IME, one flash will lock on Samsung logo, 3 finger back to recovery, wipe everything, flash the rom again and flash the gapps and it would have been fine...
I have that happen everytime I have flashed an AOKP ics..it always works out fine..
Those instructions are in most of the OP's...
Its very important to read that and have an understanding of what exact steps there are before you just start flashing away...
drnecropolis said:
IME, one flash will lock on Samsung logo, 3 finger back to recovery, wipe everything, flash the rom again and flash the gapps and it would have been fine...
I have that happen everytime I have flashed an AOKP ics..it always works out fine..
Those instructions are in most of the OP's...
Its very important to read that and have an understanding of what exact steps there are before you just start flashing away...
Click to expand...
Click to collapse
Upon flashing the first time i did reboot into recovery but it was so buggy i couldnt see what to select. I am back to non rooted stock i believe now but when trying to get to recovery it just hangs on a rainbow like screen.
Sent from my SAMSUNG-SGH-I997 using XDA
Cjohns8792 said:
Upon flashing the first time i did reboot into recovery but it was so buggy i couldnt see what to select. I am back to non rooted stock i believe now but when trying to get to recovery it just hangs on a rainbow like screen.
Sent from my SAMSUNG-SGH-I997 using XDA
Click to expand...
Click to collapse
I would use the one click heimell run it twice on the 2nd time check the box for bootloaders....
bigjoe2675 said:
I would use the one click heimell run it twice on the 2nd time check the box for bootloaders....
Click to expand...
Click to collapse
It actually doesnt allow me to select it. The box is "greyed" out yet says phone connected and ready.
Cjohns8792 said:
It actually doesnt allow me to select it. The box is "greyed" out yet says phone connected and ready.
Click to expand...
Click to collapse
Aft your 1st flash...dont close program...but put your phone back into download mode again and then it should allow you to check the box...then..
You probably can't mount until you format system, data, and cache. I had this issue before as well, Go to mounts and storage and Format system, data, and cache and then try mounting again.
Axiomkid said:
You probably can't mount until you format system, data, and cache. I had this issue before as well, Go to mounts and storage and Format system, data, and cache and then try mounting again.
Click to expand...
Click to collapse
Can't access recovery, it just shows a full rainbow screen.
Cjohns8792 said:
Can't access recovery, it just shows a full rainbow screen.
Click to expand...
Click to collapse
my suggestion is do the method i mentioned..
HOLD ON UPDATING!!! There are a bunch of people having data and wifi issues with this release. I have not had them but that doesn't mean you won't. Update at your OWN risk. You've been warned.
If you would like to update the software but not the baseband (probable cause for data/wifi issues) then just use my Nandroid linked below and leave your current baseband.
To everyone that keeps trying to relock their phones and flash the RUU to get the update it will NOT work. If you look at your software version you will see that it has added and R2 in it. I don't know why it does this, maybe it's a why for HTC to screw over the hackers yet again. Here is how to get the update.
There are 2 ways to get the update.
First: Use my Stock Rooted 1.84 Nandroid that I posted here. Simple but you will have to flash the radio separate.
Second: More steps but worked for me. NOTE: Only works if your on stock rooted phone. Will not work on custom ROM. Get Stock 1.53 Nandroid here. Credit to Reviewers for posting.
This will NOT wipe your phone nor do you need to wipe your phone if you are on Stock Rooted.
1a - This step only needed if you are on a custom ROM. If your on Stock Rooted then proceed to step 1b.
Download the above linked Nandroid (for 1.53) and restore it in Recovery. Reboot.
1b - Download this tool and use it to flash stock recovery. It will auto reboot your phone into bootloader so just start with your phone normally booted.
Credit goes to hasoon2000 for creating the tool!
2 - Your phone will reboot, once booted back up go to Settings>About Phone>Software Update. It will find the update and download then prompt to install. Select yes and let your phone update and reboot.
3 - Fire up the tool from step 1b again and this time flash CWM Recovery (whichever you prefer).
4 - After reboot is complete reboot again back into recovery and flash this to restore SU permissions (seems the update breaks them, at least for me).
Credit goes to Chainfire for creating this!
5 - Reboot, Done.
Any way to force the update if you have already received it once? I downloaded it yesterday but it failed because I had CWM installed at the time. I've flashed back to stock recovery but when I check for an update it says one isn't available.
I wonder if I could call T-Mobile and have them push it again?
DigitalMonk said:
Any way to force the update if you have already received it once? I downloaded it yesterday but it failed because I had CWM installed at the time. I've flashed back to stock recovery but when I check for an update it says one isn't available.
I wonder if I could call T-Mobile and have them push it again?
Click to expand...
Click to collapse
Did you totally wipe your phone? If not then the update is in your " download" folder
Sent from my HTC One S
Yeah, I know it's in Download, I posted about that in another thread yesterday. But is there some way to flash it now from that file? I thought from reading the other threads there was no flashable version yet, or was that only if you are running CWM?
DigitalMonk said:
Yeah, I know it's in Download, I posted about that in another thread yesterday. But is there some way to flash it now from that file? I thought from reading the other threads there was no flashable version yet, or was that only if you are running CWM?
Click to expand...
Click to collapse
Try deleting that file and checking again. Back it up to your computer first of course.
setzer715 said:
Try deleting that file and checking again. Back it up to your computer first of course.
Click to expand...
Click to collapse
Didn't work for me. I got about 2 downloads out of the servers, and then they aren't sending it anymore. Weak.
No go so far. Copied it to my PC, deleted it from my Download folder, re-booted and then checked for an update 3 different times and nothing so far.
With all of the people having wifi and data issues TMO may have stopped sending it until they figure out what is going on. I do know for a fact that TMO tests any software update the send so something may have gone haywire with it. Maybe got radio mixed up.
DigitalMonk said:
I thought from reading the other threads there was no flashable version yet, or was that only if you are running CWM?
Click to expand...
Click to collapse
Wait.. I didn't know this. You mean even if we "unroot" and flash stock recovery (and using stock ROM of course), we cannot flash this ourselves?
I currently have the CWM touch recovery and root, u/l bootloader, etc., and TMO has sent me 2 updates, both were in the Downloads folder. I didn't notice that it updated (as I never confirmed) but they obviously didn't install.
But I would have done the above if I had known we couldn't just flash it ourselves. WTF T-mobile?? Those of us who know how to flash a file should at least not be prevented from doing so (especially since we need to have the original recovery installed).
Sent from my HTC One-S (rooted), stock ROM
This happened before but I can't remember how I fixed it.
1. Flashed TWRP (over codename if that helps)
2. it bootlooped back to recovery instead of starting the system
3. tried flashing another rom/ didn't work
4. finished season 2 of the walking dead
5. reflashed TWRP didn't help (TWRP flashing failed even tho it was the same file I used to get TWRP in the first place)
6. Took the battery out but that didn't help either
I really don't want to odin or use one click any ideas??
lonoguge said:
This happened before but I can't remember how I fixed it.
1. Flashed TWRP (over codename if that helps)
Click to expand...
Click to collapse
Where did you get twrp?
lonoguge said:
2. it bootlooped back to recovery instead of starting the system
3. tried flashing another rom/ didn't work
Click to expand...
Click to collapse
What is "another rom"?
lonoguge said:
4. finished season 2 of the walking dead
5. reflashed TWRP didn't help (TWRP flashing failed even tho it was the same file I used to get TWRP in the first place)
6. Took the battery out but that didn't help either
I really don't want to odin or use one click any ideas??
Click to expand...
Click to collapse
Meh, lets start with the first two...
To stop the reboot to recovery, you must flash eollie's oneclick with bootloaders (so flash it twice, second time flash bootloaders) and go back to mtd.
bhundven said:
Where did you get twrp?
What is "another rom"?
Meh, lets start with the first two...
To stop the reboot to recovery, you must flash eollie's oneclick with bootloaders (so flash it twice, second time flash bootloaders) and go back to mtd.
Click to expand...
Click to collapse
I got it from what I thought was the official XDA TWRP thread but I'm not sure if it was official or not
at first I tried reinstalling codename but now I'm trying Beam (Tuk edition) and it seems to be working
TWRP Major Boot Loop
hey guys, im new here and i desperately need help with my phone!
the other day i was flashing a rom on my samsung galaxy s 4g. Things were turning out fine, until i had some complications on my phone.. so, i removed the rom. when i rebooted my phone, it went directly into the team win recovery project boot loop and every time i try to reboot my phone, it goes into the twrp. I also can't wipe anything and i can't delete anything! Does anybody know how I can solve this or is my phone basically bricked
more details would be helpful..
As in what rom, or what kernel.... etc... and make sure you have the corret phone.
Same problem with t959p
Looks like I'm not alone.......here's my story
the other day I wanted to switch from a stock rom to a custom, so I flashed redux 1.3 which was actually a froyo rom, and it started draining my batt like crazy so I flashed another rom on top of the froyo rom not realizing what I was doing and somehow messed it up cuz now it will only boot into recovery.
Now just to be clear I know this was my fault, I know I should have odin'd back to stock first, but I wasn't thinking at the time.....Ohh and just so you know I've flashed this sucker hundreds of times and was always able to get out of any mess I got in.
So here is the situation as it stands now, 3 button combo to enter download does not work. I can only get it into download with the jig I made. the problem is even in download mode none of my pc's will detect the device as a Samsung composite device, so odin will not see it. I've installed every possible 32 n 64 bit driver I could find including reinstalling kies. Kies wont even see it. I've tried flashing a few roms that I know worked and still it just boots into recovery. Now one thing I'll tell you is that depending on which rom I flash I can get recovery to switch from cwm to twrp. right now I left it with cwm 6.x.
what I need is a cwm flashable stock telus t959p rom complete with bootloaders or at the very least a cwm flashable zip file containing the bootloaders to see if I can recover the phone.
ohh and if your thinking about telling me to google search for the answer then don't bother.......I've spent the last 4 days reading posts and going to different websites and repositories trying to find something that would help me and so far nothing has.
the only thing that might work as a last resort is pushing the bootloaders as per one of raver's or whitehawks posts but it's a little more complicated for me as I would have to set up a laptop with Linux as I don't think i'll be able to pull it off with any of my windows pc's, win7 and win 8 only.
so if anyone has the files I need or can make them please let me know....or if you think you have another solution I could try i'm all ears err eyes.
thanks
Jedi
Have you tried heimdall one-clicks? Maybe it's showing up as gadget or something like that. I've had luck using zadig and heimdall to bring it back from the brink of death.
http://forum.xda-developers.com/showthread.php?t=1358498
EDIT
Woops replied to the wrong thread .
Nothing to see here, move along
Would like to revive a slightly dead thread.
I upgraded to a Galaxy S3 and no longer use my SGS4G for daily use. I had AOKP and disliked it, FC's and didn't like the feel. I have been trying to install a new rom ( old rom, VH Black Ed. ). Every time It loads into TWRP I have the ability to select the zip, install, it says complete, but reboots right back to TWRP menu. I've tried flashing CWM and it will install, flash the rom, reboot, and right back to this TWRP B.S... what am I doing wrong? I want to continue to use this SGS4g for music and internet duties.
How can I install CWM and have it stay even after a reboot? This TWRP is starting to me off
Did you happen to one click to stock before you went ham at the recovery?
Sent from my SGH-T959V using Tapatalk 4
So I rooted my brother's infuse 4G because it was slow as sin and needed A. a data/cache wipe and B, I wanted to give him Jellybean
I followed all the instructions I could; rooted, installed the modded 3e (or thought I did), got a CWM installed afterwards, and then set about installing first CM9 (as the Jellybean ROM post says I should) followed by the actual ROM and its Gapps. Well, I installed CM9 (although it seemed to take all of 30 seconds, rather fast...) when I tried to wipe data/factory reset, CWM froze. I rebooted and from then on I had it softbricked. Stuck booting at the samsung logo, and when I tried to return to the recovery, the recovery was a garbled mess that looked like a scrambled TV channel. I used Heimdall and did the one-click reset to stock, and here I am. The phone boots to stock just fine, but my recovery is still completely boned.
Do I re-root? How do I install CWM again without being able to install 3e? (can't install 3e without a working recovery in the first place, after all..)
One anomaly of note - when I was going about all this, booting the phone into recovery always got me 3e, even after installing CWM. I had to manually install CWM by using an update.zip and "reinstall packages" every time I wanted to use CWM. ROM manager would boot me to CWM, but it took several reboots and a flashable CWM zip before I could even get CWM installed in the first place - ROM manager refused to do it the easy way.
What did I do wrong, and more importantly, how do I get back on track? What do I do to put a fixed recovery back on this thing? Odin? ADB?
Today was the first time I ever used Heimdall, I've been a fair weather flasher since the beginning, I've never had to ADB or Odin.
It sounds like you didn't install cwm recovery properly, but I'm not sure I've never ran into this problem before. If you go here
http://forum.xda-developers.com/showthread.php?t=1524081 and carefully read over the first and second post you should end up with gb and red cwm recovery. The way I've done it was to put the phone in dl mode and flash the first package (the stock gingerbread att rom). After it is installed and booted up, I then power it off and go back into dl mode. Then flash the second package, which is just the kernel and red cwm recovery, (be patient because it takes awhile). Once that is done then go into recovery and wipe data/factory reset, wipe dalvik cache, wipe system, and install cm9. I think it only installs the kernel and recovery the first installation after formatting and creating the partitions, but after its done you have to go through the menus and tell it to reboot. After it reboots it will be stuck at the cyanogenmod galaxy s logo, so you will have to go into recovery once more. When you're there you should have blue cwm (only continue if you do) and install jb, without actually having to install the full cm9. When you navigate to which ever jb rom you want to install, a prompt will appear stating that there is incompatible partition layout and to confirm installation you will have to reselect the jb zip again to install. It will flash pretty quick because at this point its doing the same thing as when you went from gb to cm9 and only installs the kernel, recovery, and reformat/creates the partitions, (I think). It will reboot on its own but it will take you back into recovery. At this point all you have to do is navigate to the same jb zip you want to install and flash it, followed by gapps, and then reboot system. This process has worked for me but I highly recommend reading and following the instructions given in the post above.
Use goo.I'm app. Also you need to flash GB bootloaders in Odin . is recovery all colorful? If you see recovery fine just get goo app on play store and install a recovery
Sent from my SAMSUNG-SGH-I317 using Tapatalk
I would go the ODIN route, I have bricked so many times because i try to make the impossible possible. Just search for a already rooted pda,mdr file. I skipped the cm9 part idk if that would make things better or not but as my post says im a risk-taker
One thing I'd like to point out, flashing to ICS from GB requires 2 flashes. First flash sets the new partitions. You reboot and pull the battery, then boot back into recovery and reflash with the gapps.
That was the first problem I saw, and now commenting while on the Nexus I can't see the OP so that's all I'll comment on.
Sent from my Nexus 7 using xda premium
UnhoIy said:
One thing I'd like to point out, flashing to ICS from GB requires 2 flashes. First flash sets the new partitions. You reboot and pull the battery, then boot back into recovery and reflash with the gapps.
That was the first problem I saw, and now commenting while on the Nexus I can't see the OP so that's all I'll comment on.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
but if don't have any problems i'm good right or should i go back and do it
MajorLeagueROM said:
but if don't have any problems i'm good right or should i go back and do it
Click to expand...
Click to collapse
I've never skipped ICS and gone straight to JB like you, that's risk I've yet taken. I guess if you've had no problem then you're good, but I've gone back to stock and to JB at least 12 times now and used the same process every time without a hitch. In the case of OPs problem, I would just go back to stock and try again. Although I always go back to 2.2 stock...
Sent from my SGH-I997 using xda app-developers app
UnhoIy said:
I've never skipped ICS and gone straight to JB like you, that's risk I've yet taken. I guess if you've had no problem then you're good, but I've gone back to stock and to JB at least 12 times now and used the same process every time without a hitch. In the case of OPs problem, I would just go back to stock and try again. Although I always go back to 2.2 stock...
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
I'll just do it tonight then maybe my phone will run better, i thought i'd be a waste of time. thanks for the info
MajorLeagueROM said:
I'll just do it tonight then maybe my phone will run better, i thought i'd be a waste of time. thanks for the info
Click to expand...
Click to collapse
Lucky me, I get to go back to stock tonight for soft-bricking for the first time having this phone. It's what I get for trying to port a ROM with only a nights worth of research.
Oh well.
UnhoIy said:
Lucky me, I get to go back to stock tonight for soft-bricking for the first time having this phone. It's what I get for trying to port a ROM with only a nights worth of research.
Oh well.
Click to expand...
Click to collapse
lol it happens to the best of us