My old phone got lost so I am using my Infuse again. I decided to update it since it is still on the old version from when it first came out. I was trying forever to update through the kies software until I realized I rooted it and so this won't work. So then I found out there are roms for way better versions anyways. So I found the Cyanfox rom and I wanted to do that, but I needed to first upgrade to cm9 so I went and downloaded the cm9 file and got the clockworkrecovery, and I installed it.
Now my phone will not turn on, it sits as samsung screen. And if you try to go to recovery it is just a messed up screen with all different colors as if the screen was broken. So now my only option to bea ble to install anything on it is through odin. I can get to download mode fine.
But this damn odin software will not detect my phone for the life of me. It literally will not work. I don't understand. I have spent hours upon hours on this between the past few days. I just want to update my damn phone.
Now I have to leave for work in 30 minutes and my phone doesn't work. This is just great.
How did you install CWM?
Sent from my Asus MeMO Pad 8"
Well I tried clockworkmod through the rom manager app, but I was running the android recovery 3e and it said I needed a modified version of that to be able to install 3e. So I replaced the recovery file with the one I was given, and then I manually installed cwm by naming it update.zip and running it on the recovery
The only problem was that every time I wanted to use cwm, it would go back to android recovery 3e, and I would have to click install again to get it to go into cwm.
Either way, it doesn't work anymore and I just need the damn thing to connect to Odin so I can flash it back.
Are you using a desktop or laptop? If desktop, are you using the USB ports in the back? If laptop, have you tried different USB ports? Maybe try a different computer? I've heard that USB 3.0 doesn't play nicely with ODIN so it's good to find some 2.0 connections. What Windows version? I've heard that Win8 can cause problems. Could also try Heimdall instead of Odin.
Unless I think of anything else, is the cable in good working order (recent successful file transfer)?
Alright. I got things working somewhat. I had to use different drivers for each program for it to be able to detect it. I don't know, its annoying as hell, but it worked when I went back and forth between drivers.
Anyways, I got my device restored. But the whole point of this was that I was trying to get to the KitKat rom(Cyanfox). I am still quite a few steps away from that. I am actually further away than when I started,
This is what originally happened: I had my device rooted(from when I last used it, 1-2 years ago) and had the 3e recovery. So I found out I needed a modified 3e so I could install Clockworkmod. Got that, all was well, and the thing basically got bricked when I went to update to a new rom. It wasn't the kitkat rom, but a CM9 rom that I needed to go to first so that I could then update to kitkat.
Now I got it unbricked, and I updated it using kies. So now I am on gingerbread. So then I rooted it again. So now I have the 3e recovery again, the only problem is when I go to system/bin/ there is no file called recovery, and I can put one there but it does not affect the recovery, it still looks for signed files, meaning I cannot install Clockworkmod.
Not sure what to do...
Seems everyone follows this process (looks like you already did step one) now....
1. Either use Odin or Heimdall One-Click. Follow instruction on how to do it.
2. While phone running install sgs kernel flasher from Market/Google Play.
2a. Copy/transfer Synthesis GB Kernel to your Internal SD card.
2b. Start up sgs kernel flasher and choose it from your Internal SD card. Phone will auto-reboot after done flashing.
2c. Wait a bit while your phone convert to new partition format and activate lagfix. Your CWM recovery version should be 2.5.1.3
3. Reboot phone into CWM Recovery and DISABLE vodoo lagfix and /system lagfix. Reboot once done. Phone will convert partition to old format. If you don't turn the lagfix off the phone will hang at Samsung logo when you install new rom.
4. Prepare your flavor rom/gapp for installation by copying them to your Internal SD card.
4a. Go into CWM Recovery mode and install the rom. You will need to do this twice since the 1st time was just a warning about partition format being different.
4b. Reboot once done. You will need to REMOVE the battery to power down the booting process and put it back in.
4c. Go into the New CWM Recovery and install the rom again since the previous attempt only install the new CWM Recovery.
5. Install Gapp.
6. a. Wipe: Cache / Factory Reset <--- Probably don't need it since it's new install from stock unless you installed stuff. Just to be safe.
b. Wipe: Cache Partition
c. Wipe: Dalvik Cache
7. Reboot
Click to expand...
Click to collapse
I never tried step two myself, as I found a flashable download for ODIN that did this for me. But mine is a Rogers phone (not AT&T) so that would not work for you. Hope this helps.
Thanks you so much man. I know that is just copy/paste but I didn't see it, and it works. I was looking in Cyanfox thread, never looked at the Beanstalk thread.
Anyways I am in the process of doing this and it seems like it will work. Appreciate all your help!
Edit: Boom. Worked like a charm. Thanks so much. I am very happy now The funny thing is, half the reason I wanted this is cause everyone was group messaging, and I didn't have that capability anymore when I lost my phone(I was on such an old version). Again thanks so much.
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
Currently I am in a soft brick state- I cant remember which CM- 9 either cm-9-20120614-EXPERIMENTAL-skyrocket-alpha5.zip, or cm-9-20120709-NIGHTLY... (I can see that those are the only two I have on my sd card. I am on an ATT GS2 skyrocket
If I boot normally - it stays stuck on the CM9boot screen.
I can use the 3 finger method to boot into CWM 5.8.4.3
While searching for answers I read that this CWM is broken.
Initially I was trying to go back to an earlier recovery. CWM would see the recoveries on the SDcard, but when I tried to recover- it would not mount from the SD card.
I got to CM( by using odin to put an earlier CWM, and superuser on the phone, then installed Rom manager, then used rom manager to flash CWM (via tmobile sgs2) then updated to CWM touch...
When I tried using the CWM to factory restore and cache wipe it starts then hangs I cant install zips from the external SD card, or any recoveries...
I'm figuring worst case - I can go back to ODIN, and do stock recovery http://forum.xda-developers.com/showthread.php?t=1342348 , then flash the non touch CWM, superuser http://forum.xda-developers.com/showthread.php?t=1340526, then flash a recovery from my sd card??
Is there something else I might have missed in trying to get back to a functional state without going to odin?
Many thanks in advance for any assistance
Ihab
ihabelnaccash said:
Currently I am in a soft brick state- I cant remember which CM- 9 either cm-9-20120614-EXPERIMENTAL-skyrocket-alpha5.zip, or cm-9-20120709-NIGHTLY... (I can see that those are the only two I have on my sd card. I am on an ATT GS2 skyrocket
If I boot normally - it stays stuck on the CM9boot screen.
I can use the 3 finger method to boot into CWM 5.8.4.3
While searching for answers I read that this CWM is broken.
Initially I was trying to go back to an earlier recovery. CWM would see the recoveries on the SDcard, but when I tried to recover- it would not mount from the SD card.
I got to CM( by using odin to put an earlier CWM, and superuser on the phone, then installed Rom manager, then used rom manager to flash CWM (via tmobile sgs2) then updated to CWM touch...
When I tried using the CWM to factory restore and cache wipe it starts then hangs I cant install zips from the external SD card, or any recoveries...
I'm figuring worst case - I can go back to ODIN, and do stock recovery http://forum.xda-developers.com/showthread.php?t=1342348 , then flash the non touch CWM, superuser http://forum.xda-developers.com/showthread.php?t=1340526, then flash a recovery from my sd card??
Is there something else I might have missed in trying to get back to a functional state without going to odin?
Many thanks in advance for any assistance
Ihab
Click to expand...
Click to collapse
Hi there,
I recently experienced the same thing, and it was a hassle to fix--but I have got my phone working each time. The downside being that I /had/ to switch over to Odin. Mind you, I am not necessarily experienced with Android, so I can't really say that this is the only way.
At any rate, here's what I did to get it back to normal:
Load up Odin
Put it in download mode -- I assume you know to hold the volume keys and then plug in the USB.
Flash either the ICS leak or the stock 2.3.5 Gingerbread.
You should be back to good. I hope you backed everything up in either Kies or some other resource...else you're in for a hell of a time setting stuff up.
Oh: bad news about the 2.3.5 stock is that, as far as I can tell, you're unable to upgrade to 2.3.6. In turn, you're then unable to update to the official ICS through Kies or OTA. I assume you don't mind, considering you're trying to flash a new rom anyway.
Anyway, I do hope there is some bit of clarity on getting CM9 on the Skyrocket. As of now I have still been unable to do it. Just as you, no matter the settings I try, I end up being stuck at that screen. The only difference between your method and mine is that I completely did mine through CWM...nothing through ROM Manager. (Actually, I believe I tried a few differing methods involving the CWM touch and non-touch...followed many different guides but still no good.)
Hope you get it back to a functioning state. If you get CM9 working on the Skyrocket, I'd appreciate you sending a bit of details on how to do so.
EDIT: I am now on CM9. Through magic, ponies and friendship I have failed to accomplish this feat. But by pure science and the blood of a pony, I have successfully installed CM9.
After you've restored to 2.3.5 or the ICS leak (the one I was on), do the following:
- Grab the recovery-clockwork-touch U27 described below. Flash it.
- Download both the newest CM9 build from their website, as well as Google Apps, and then copy those to your external SD.
- Follow this guide: http://www.teamchopsticks.org/p/install-guide.html. Here's what's relevant to you:
Wipe data/factory reset.
Format /system (mounts and storage->format /system).
Install the CM9 zip from SD card.
Install the gapps zip from SD card.
ONLY IF YOU ARE ON TOUCH CWM RECOVERY: Format /cache (mounts and storage->format /cache)
Reboot. Let it sit for a few minutes after the first boot. Be patient.\
Click to expand...
Click to collapse
After ~10 minutes you should be fine. Mine took less, but I'd bet it could take longer. Please follow those directions above EXACTLY. I'll be happy to help you in any way I can if you reply to this thread/ send me a PM.
When I softbricked with the latest CWM I wasn't able to return back since it wouldnt detect my SDcard so I just loaded up odin and used recovery-clockwork-touch-5.8.1.3-hercules.tar and was able to read my SDcard again which had all my backups and CM9 files. I have flashed every version of CM9 every since and still using this CWM version and havent had any problems. :good:
All better now- I used ODIN to restore to stock, then used it again to put CWM (non-touch) back on, then added superuser, then just did a restore from SDcard! Muchas Gracias all!
Should I be able to then use a restore of when I had a working CM9 (and backed up with CWM)? Or would I have to do all the cache wiping/ factory reset like I did to install it the first time before using such a recovery? (and I will try that recovery- clockwork touch hercules... latrer tonight from home)
ODIN tar to restore back to factory. I got the boot loop too. Only until after I flashed CM9 then flashed dark side wipe cache only would CM9 work for me. Only on regular CWM though. Try and give that a go.
Sent from my SAMSUNG-SGH-I727
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
I'll preface this by saying the following:
I know there are a lot of brick guides out there, and most are relatively easy to get out of. I've worked myself into a bit of a pickle, though.
It started when I noticed that there was an update available through the CM updater. I figured, what the hell, I'm running a nightly and this is likely to be a stable release, so I went ahead and downloaded it. I got home and checked the get.cm page, and sure enough, a new, stable build had recently been released. Being the diligent soul that I am, I made sure to do a full backup before I installed the .zip. Everything worked out just fine, the backup went swell, the update finished without problems, and then I rebooted my device.
All I see is the Asus splash screen. It just stays there. So I think, no big deal, it just didn't work out like I wanted, I'll go format my data (which I didn't do the first time around, in hopes that everything would carry over) and install again. The same thing happens. I haven't started panicking yet, since I still have 3 backups (1 older Jellybean, and one much older ICS). None of them work. I wipe everything that I can think might help. Data, system, cache, dalvik, you name it. Nothing was working, and I was starting to freak out. Then I decided to try to get some action through fastboot, hoping that I could push a .zip that wasn't the CM10 update that had started everything. In my search for a push command, I thought it would be a good idea to try a wipe from fastboot. This wiped everything. Not only the system, boot, etc. partitions, but also my personal partition that had all of my data. This in itself isn't a big problem, but it also left the partitions unformatted. Now I have a device that is devoid of data and can't do anything but get into CWM and fastboot.
What the hell can I do? Am I doomed? Is there no way to get out of the hole I've dug myself into?
tl;dr failed update, things got really real, really fast.
Specs before the initial update
ROM: CM10 nightly, Jellybean 4.1.x
CWM: 5.5.0.4
Kernel Version (?): 9.4.3.30-20120604 (I'm not sure with this, it says something about "android carhu-user" before it)
same thing just happened to me. Im going to download another version of CM and try that. It might just be that.
DerangedLoofah said:
same thing just happened to me. Im going to download another version of CM and try that. It might just be that.
Click to expand...
Click to collapse
That's the thing, though, I have no idea how I'm supposed to get it to my device now...
http://forum.xda-developers.com/showthread.php?t=1989076
Have you tried this? I was just thinking about it because I can't reflash my recovery and thought this may be the way to start over.
OK I downloaded the us jb update and extracted to my external SD card and flashed it in recovery after wipes. Everything is good now.
Edit: flash recovery in fast boot.
Sent from my SCH-I535 using Tapatalk 2
Glad you got it!
nitsuj79 said:
Glad you got it!
Click to expand...
Click to collapse
DerangedLoofah managed to get it, but I still haven't had any luck.
DerangedLoofah said:
OK I downloaded the us jb update and extracted to my external SD card and flashed it in recovery after wipes. Everything is good now.
Edit: flash recovery in fast boot.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
How did you flash it in fastboot? I can't figure out how to get to something that's on the external SD card. What were the exact commands you used?
1. Download any software from this topic http://forum.xda-developers.com/show....php?t=1697227
2. Unpack it one so you have a zip without UpdateLauncher
3. Rename the zip to EP201_768_SDUPDATE.zip
4. Put on a sdcard into the root (the sdcard should be clean, no other files)
5. Boot you tablet to RCK (Volume down + power, then volume up)
6. Let the magic begin!!! Take some minutes.
Attention! JB user pleas choose a JB ROM, don't flash ICS ROM on JB bootloader.
You tried this method with no love? I was able to flash stock pretty easily doing this.
nitsuj79 said:
1. Download any software from this topic http://forum.xda-developers.com/show....php?t=1697227
2. Unpack it one so you have a zip without UpdateLauncher
3. Rename the zip to EP201_768_SDUPDATE.zip
4. Put on a sdcard into the root (the sdcard should be clean, no other files)
5. Boot you tablet to RCK (Volume down + power, then volume up)
6. Let the magic begin!!! Take some minutes.
Attention! JB user pleas choose a JB ROM, don't flash ICS ROM on JB bootloader.
You tried this method with no love? I was able to flash stock pretty easily doing this.
Click to expand...
Click to collapse
Does that work with CWM? I don't have the stock bootloader on it.
This works only if you didn't flash custom recovery, it is the best method for locked devices. But you can still flash any stock ROM from CWM (but I suggest to use TWRP, you can install it from external sd). And you can push the ROM to internal memory via adb. I think you can install stock ROM via fastboot too, I am not sure, but the command fastboot update should help.
I managed to get it working again. If you can get to fastboot, push a bootloader that supports an external SD cards (like TWRP) and then from that install one of the official ASUS firmwares. From there, you have to root again, but it's better than having a device that won't boot at all.
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