Dont want to muck up the CM7 thread and no thread was started.
FB Im wondering if twrp is fully wiping when you run the wipe option. I used the kj6 heimdall one-click to get back from a bad flash. However once I finally was able to get everything set back up I had restored some apps through Titanium Backup, but only app no data. Amazon app store was one and I had to delete the backup and uninstall the app, reboot clear cache and then re-install it to get it to work. The theme chooser app was fcing on me until I did the same thing.
After I did this I applied a theme apk that borked me. I was stuck on the team acid logo. No boot loop just stuck. I then one clicked to kj6 again, then used antonx kernel one click. Made a new backup of my efs, wiped everything including boot img. Flashed the twrpcm7 zip and followed the directions to finish.
I know anything is possible but is it likely that twrp is seeing something not wiped in the bml to mtd conversion and its causing conflicts?
If your not comfortable with the possibility of bricking your phone do not follow my steps and format everything. Formatting boot has the possibility to brick your device.
Hmm, well /data isn't getting wiped in R11. Bryan submitted a patch for updater.sh that should take care of this though I haven't tested it. I haven't tested a BML->MTD (cm7-twrp) flash though, but I'll have to look into it in the next few days. I'm running a rom build right now, so I'll probably test that out tonight.
I didn't wipe anything, I just flashed the twrp boot.img. I am running Team Kick Asses MIUI Revenge (MTD). After I flashed and the phone booted, wifi would not turn on, and it said error underneath the button. Pulled a logcat but all it said was wifi failed to initialize. Is that error due to the fact I didn't wipe anything or factory reset/fix perms?
Either way, it is super sweet recovery!
Max says its a driver issue. Ill find the post and link it.
m4xm4n said:
The reason wifi didn't work is because the wifi module needed to be from the same kernel build. I'm not sure how FB built the two builds, so I don't know if he included a module from a different kernel build or not.
Try the R11B with TWRP and then install R11(not B) with inject TWRP enabled.
Sent from my SGH-T959V using XDA
Click to expand...
Click to collapse
Now that you have twrp make a cwm zip for the r11 kernel, flash it via twrp and leave the "inject twrp" option enabled. You should get working wifi and twrp
Sent from my SGH-T959V
Like I said on cm thread the wifi module is different from the one Max used on his new boot.img which is why twrp and the new boot.img doesn't work with the current miui build ...the first release of dianxin os had the new boot.img fb sent me and that was the wifi issue.
sent from my batcave
I flashed miui on with twrp doing a wipe firs and it installed miui fine, with wifi and everything seems to be fully functional. Just to be safe I wanted to test out twrp on miui, however the only way I could get to it was volume up+down+ power. But that loads it right up, and I flashed a few different modems to see which gave me the best signal, and it worked each time. Btw, nice work fb twrp is great.
Sent from my SGH-T959V using xda premium
Which modems did you flash? If the modem flash DID work you should be able to go into Settings > About Phone and check under baseband version. I'm not sure if that's the exact menu on MIUI but there should be something very similar.
I just flashed kg4 and that's what it says under baseband version, I flashed kd1 earlier and that's what it said before I just flashed kg4. Just to make sure it was working. I think it says t959vuvkg4 or something to that effect, it definately just changed though from kd1
Sent from my SGH-T959V using xda premium
Hey guys just a progress report on this. I've been messing with a twrp injection cwm zip all evening. After some discussion with bhundven, the way we're going to go about this is to NOT include twrp by default in cm7. It's been really hard to get a working copy compiled and included with cm7 and if we can't do this automatically there's no point to doing it at all.
The CWM zip will (hopefully) allow us to give you the option of using TWRP even if you're using CWM at the moment. The benefits are the following:
You won't need to mess around with kernel features that don't work (wifi was broken, ffc was broken)
You only really need to inject twrp once via CWM since twrp comes with an inject option before you flash a CM7 update.
It'll make it easier on us since we'll have less releases and thus have to provide less support.
At the moment I'm trying to have something for you guys tonight, but the chances are slim for that happening.
FB
For some reason TWRP can't Flash Zip file like Mtd modem kd1. I try to make a nandroid bk and didn't work. Also I try to save error logs on sd card didn't work.
My english is not the best, sorry
Sent from my SGH-T959V using xda premium
Please post the logs here.
What errors did you get when trying to flash the kd1 modem or make the nandroid backup? I've tried making and restoring a nandroid backup using CM7 R11 with twrp injected by the zip and it's worked fine for me.
What rom/kernel combination are you using?
Error: Unable to open zip file
I try nandroid backup again and for some reason did work but wasn't working.
Am using CM7 R11B & CWM TWRP
Everyting else is working good thanks!!!!
Sent from my SGH-T959V using xda premium
Related
So I spent the weekend working on some things, and one of them was trying to get CWM fixed up. I believe that I have all of the problems fixed, but I can only do so much testing on my own. The button mappings work, and I have been using this and similar versions (bugfixes and such added since then) for about a week now. I completely removed backup/restore as my attempt to get it to work properly didn't work, so I'm guessing something else is wrong with it than what I initially found and reported to Koush. I will try to keep this updated as updates come out for CWM as well. Flash with Odin/Heimdall
Button Mapping
Vol Up / Home - Go up
Vol Dn / Menu - Go Down
Back - Go Back
Power / Search - Select Item
Flashing Tips
Use the rear USB Ports on your computer if possible, and without a USB extension cable.
When in Download mode with the battery out, put the battery back in and uncheck Auto-Reboot in Odin. When done flashing, remove the battery and USB cable, put the battery back in and reboot - credit to jami2976
Changelog
0302
"Fix" fix_permissions - mount all partitions under mounts and storage prior to running
1209
Put fat.format back in place so restore and data wipes work properly.
1207
CWM 5.x Update
0817
Fix backup/restore
0807/0808 - Not posted
Update to the latest CWM source
Fix the fix_permissions script
0730
Using stock CWM Source
-> No more advanced options that aren't in stock CWM
0713
More updates, hopefully fixed restore problem too.
0709
Updated to the latest CWM Source
Backup/Restore has been added back
-Has had some successful testing, but no large scale testing or use so be careful for now
Odin dump function expanded
0611
Initial release
Known Issues
CWM Getting over-written by stock recovery - Flash a custom kernel or delete /system/etc/install-recovery.sh
Failed to mount /sdcard error(s) - Perform the following commands with ADB:
Code:
adb shell
umount /sdcard
rm -f /sdcard
mkdir /sdcard
exit
Type each line in and press enter. Do not skip a line, or you may loose data It seems to have worked for anyone that tested and had this issue.
Download
Everything works for me. Thank you. I didn't test backup tho or restore
Sent from my SCH-I510 using XDA Premium App
imnuts said:
So I spent the weekend working on some things, and one of them was trying to get CWM fixed up. I believe that I have all of the problems fixed, but it needs testing to verify. If anyone would like to try it out and see if there are any more problems, please download and flash with Odin. The button mappings work, and I have been using it for a day and flashing things and that works as well. I have not tested out backup/restore, though I did find an issue that may have been causing the problem and put in a fix, so I'm hoping that it works as well. If all goes well, we can start using this full time, or go back and look for anything else that may be causing problems.
Button Mapping
Vol Up/Down - Navigate through the menus
Power - Select Item
Menu/Home/Back/Search - Go Back to the previous menu
Download
Click to expand...
Click to collapse
Ill test it. But first, did the people who bricked their phone ever find a way to unbrick it after trying a cwm restore?
ShotgunSam said:
Ill test it. But first, did the people who bricked their phone ever find a way to unbrick it after trying a cwm restore?
Click to expand...
Click to collapse
Some have and some haven't. People that are having issues can't flash the package that I put together for the fix, but others have flashed it without issue.
One thing that may also be "broken" is data wipe in CWM, as it may get stuck on deleting /sdcard/.android_secure and I'm looking for why it's doing it and how to fix it.
My data wipe is good. I'm still trying to grow a pair and backup and restore lol
Sent from my SCH-I510 using XDA Premium App
ShotgunSam said:
Ill test it. But first, did the people who bricked their phone ever find a way to unbrick it after trying a cwm restore?
Click to expand...
Click to collapse
I was never able to get it to flash the packages unfortunately. It seems hit and miss, works for some, and not others.
Imnuts can we install this CWM any other way than Odin? I have been trying to get the Voodoo Kernel and CWM-2 installed but its an either or situation. If I install Voodoo kernel then CWM, I get a soft brick even though CWM says it passed.
RaptorMD said:
Imnuts can we install this CWM any other way than Odin? I have been trying to get the Voodoo Kernel and CWM-2 installed but its an either or situation. If I install Voodoo kernel then CWM, I get a soft brick even though CWM says it passed.
Click to expand...
Click to collapse
You can flash with Heimdall as well, just extract and put recovery.bin in the proper place.
Well it doesnt work lol
1. it backsups fine it seems.
2. During restore it said it couldnt mount system but hey it formatted it
3. seemed to flash a rom but everytime i reboot it goes into cwm.
4. I was able to odin fine
nevermind im stuck in recovery now. Can i restore with odin even tho i have the voodoo lagfix enabled before cwr bricked my phone?
i got voodoo sound. what im noticing is it says its starting and finishes in seconds then back to brick
papi92 said:
Well it doesnt work lol
1. it backsups fine it seems.
2. During restore it said it couldnt mount system but hey it formatted it
3. seemed to flash a rom but everytime i reboot it goes into cwm.
4. I was able to odin fine
Click to expand...
Click to collapse
Thanks for being the first one to test the waters....
Can someone else verify that it indeed is malfunctioning on restore?
anyone have a pit file or have been able to fix a bricked phone. Im desperate.
papi92 said:
anyone have a pit file or have been able to fix a bricked phone. Im desperate.
Click to expand...
Click to collapse
try the restore fix files, couldn't hurt, considering the situation.
http://forum.xda-developers.com/showthread.php?t=1111486
thank you i hope that works. im dying
You can flash ANY Odin file to your phone regardless of what you were on and what you are flashing as long as you aren't flashing a kernel that does not understand EXT4 to your phone and you had lagfix enabled. If you are flashing a non-voodoo kernel (or one that doesn't understand ext4) make sure you are also flashing /system, /data, /cache, and /dbdata so that they get wiped out.
well my problem is i had lagfixed enabled. I flashed your cwr and i knew the risk. Know im stuck with the same problem as everyone else. lol so how do i disable lagfix? i can only get into download mode and the ed1 cwr fix isnt flashing. I still have lagfix since i never disabled before trying restoring. My backup was a rom that had the lagfix.
Thank you im fixed
Sent from my SCH-I510 using XDA Premium App
papi92 said:
well my problem is i had lagfixed enabled. I flashed your cwr and i knew the risk. Know im stuck with the same problem as everyone else. lol so how do i disable lagfix? i can only get into download mode and the ed1 cwr fix isnt flashing. I still have lagfix since i never disabled before trying restoring. My backup was a rom that had the lagfix.
Click to expand...
Click to collapse
Are you getting the stock recovery screen now? and the cmdline=7 message?
brabe1979 said:
Are you getting the stock recovery screen now? and the cmdline=7 message?
Click to expand...
Click to collapse
That is what he was getting. But he was able to fix w/ the help of imnuts. I'm sure he will post the steps and files to fix, whenever he gets a chance.
Hi All
Finally plucked up the courage to register and ask a question after lurking for the good part of 2 years.
I've an i9020A and have flashed CyanogenMod 9 v4.0.3 v1.0 which is great, however I wanted to try Steve Garon's kernel which just wont take.
I reboot into Recovery, wipe Dalvik Cache a couple of times, install Steve's kernel which apparently flashes no problem.
I reboot and get the optimising Android applications screen then check my kernel under settings.
It is still the original KalimochoAz kernel and I cannot turn on my wireless.
Now this has happened previously when trying to also update my kernel under CDTDroid's AndroidMe 1.2 which I could only fix by restoring back to 1.1.
Any idea on what may be wrong here guys?
Appreciation in advance.
Lally
Have you tried just flashing again? A bad flash often results in wifi not working and may be the cause of the about page showing the old kernel. Remember to wipe dalvik cache again, too.
Thanks for the reply Harbb, do you mean a re flash of the Kernel or ROM? If Kernel then yeah I have done, same scenario. I'll also try a re download of the Kernel to see if that improves anything but this is much akin to me trying to update from Speedy3 to Speedy4 under AndroidMe 1.2 which was unsuccessful.
Just the kernel, as you've already tried. Just remember to do a NANDroid backup (CWM --> backup & restore --> backup) when you have a stable, working ROM. Can save you alot of trouble if you don't have a relatively recent one.
Also, are you using CWM 5.0.2.0? And could it be that your phone isn't particularly happy about the 1100mhz OC with Steve Garon's kernel?
I'd suggest updating CWM recovery to the latest version.
Sent from my Nexus S using xda premium
Cheers for the help guys.
Yes, using 5.0.2.0, but something is not right cause I just tried to flash CWR again from within Rom Manager (4.8.1.3) and it gets to around 95% and the app gives 'Rom Manager is not responding.
Looks like I'll have to try a complete wipe and reflash.
Will report back the results.
Forget rom manager all together.
Download the recovery you want to use.
Flash it via fastboot
flash kernel.
I'd do what albundy said - flash a new recovery through fastboot and make sure the bootloader is unlocked (vol. up + power --> bootloader: unlocked)
Ok, downloaded CM9 1.1, redownloaded Steves kernel, reinstalled recovery from fastboot.
Wiped and formatted everything twice then installed from scratch.
So far everything is good, still getting errors on Superuser, but installing again via recovery seems to fix that issue.
Cheers chaps.
Good to know Lally, happy you got it sorted out.
Cheers Harbb, the test will be when I want to change the kernel again I suppose, one complete wipe and install a day is enough
I brought my phone to stock. Installed a rom. Fine. Went back into CWM recovery. Every time I reboot the phone (power button or in recovery) it returns to recovery.
I brought my phone back to stock again. Installed another rom. Went back to TWRP. Again, I can't reboot the system, only return to recovery.
Is there a way to fix this, or can I never use recovery after installing a rom?
{I'm sure this question has probably been asked before, but I've been searching for hours and can't find a fix.)
Did you wipe data & caches? What did you flash and how? Cwm, heimdall or Odin? Sgh-t959v under battery?
Find lumin30's guides. They/he will steer you straight.
Sent from my SGH-T959V using xda app-developers app
t1op said:
I brought my phone to stock. Installed a rom. Fine. Went back into CWM recovery. Every time I reboot the phone (power button or in recovery) it returns to recovery.
I brought my phone back to stock again. Installed another rom. Went back to TWRP. Again, I can't reboot the system, only return to recovery.
Is there a way to fix this, or can I never use recovery after installing a rom?
{I'm sure this question has probably been asked before, but I've been searching for hours and can't find a fix.)
Click to expand...
Click to collapse
This would occur for me when I had installed an incompatiable kernel with the ROM I am trying to install. I would fix this problem by either looking at the thread for a compatiable kernel if it does not come with one, or if it is an ICS ROM, Team Acid's ICS Kernel works fine. I think Team Acid's ICS kernel is included in their unofficial AOKP release if you have that downloaded. I hoped this help!
WayTooGosu said:
This would occur for me when I had installed an incompatiable kernel with the ROM I am trying to install. I would fix this problem by either looking at the thread for a compatiable kernel if it does not come with one, or if it is an ICS ROM, Team Acid's ICS Kernel works fine. I think Team Acid's ICS kernel is included in their unofficial AOKP release if you have that downloaded. I hoped this help!
Click to expand...
Click to collapse
All of our ROM's have kernels. It is the kernel you flash from that makes a difference. And once you flash the ROM, the kernel that is packaged with the ROM replaces the kernel you previously had/flashed from. However, the OP of the ROM's usually specify what you need to do to flash the ROM.
lumin30 said:
All of our ROM's have kernels. It is the kernel you flash from that makes a difference. And once you flash the ROM, the kernel that is packaged with the ROM replaces the kernel you previously had/flashed from. However, the OP of the ROM's usually specify what you need to do to flash the ROM.
Click to expand...
Click to collapse
Ah I see. But my point was that some ROMs state that the user must be on an ICS ROM/Kernel to flash this. I guess I wasn't very clear as I am new here and lack understanding.
champ1919 said:
Did you wipe data & caches? What did you flash and how? Cwm, heimdall or Odin? Sgh-t959v under battery?
Find lumin30's guides. They/he will steer you straight.
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
I used Odin to return to stock. I used Super One Click to root. I used root explorer modify the recovery to allow me to boot into "CWM final for Froyo". That much each and every time.
The first time I installed
[TFQ - 30/12/2012]X.A.O.K[Kanged - Xperia Style]
That is an ICS rom. Installed fine with a new CWM.
The second time I installed the same.
The third time I installed
ROM-MTD-TWRP-ICS-4.x-Audiophile
That is another ICS rom. Installed fine with TWRP.
Each and every time, when returning to recovery to flash more, I got stuck. I can't boot to anything except recovery.
My brother suggested that the problem is using the Volume up and down and power button ("three finger salute") to return to recovery instead of from OS power down menu.
For a fourth time I started over again. Now, using the reboot>recovery, everything works fine.
One thing, you need to have ginger bread bootloaders. So, when you say Odin back to stock, are you referring to kj6?
You could cut down some of the work by using Odin to flash a kernel with recovery & root in it. Antonx & drhonk both have kernels that will do that with odin.
I flash bhundven's cm9 Rom before jumping to any of the others(and wipe between). I believe some of the Rom authors have that in their instructions.
Sent from my SGH-T959V using xda app-developers app
Yeah... GB bootloaders, not Froyo. Your return to stock should be a return to GB stock, not Froyo... and your return to stock can be a return to a rooted stock. If you want to make your life less painful.
It's about MTD to BML, not really about the base version. You just don't want to wipe out what allows later stuff to actually work properly...
Thanks for the advice. I haven't used custom roms very much. Trying to figure out which ones to choose was difficult. I started on stock Gingerbread, but everything I encountered in searching indicated that I needed to go back to Froyo to get CWM then go from there. ...Perhaps I kept running into very old instructions? In any case, should I need to go back to stock again some day, I'll try to figure out which GB roms I could use, including root and custom recovery.
I guess the solution to my problem is: 1) flash back to Froyo or Gingerbread; 2) after flashing an ICS+ rom, only go to recovery from OS reboot menu (never "three finger salute").
I'm actually surprised that people don't run into this problem more often, enough to create a sticky about it. I'm sure I'd still be pulling my hair out if my brother hadn't run into the problem on his Fascinate a year ago.
On mine, the 3 finger boot to recovery works fine. Then again, I haven't been on Froyo since Samsung and TMo said to stop using Froyo back in November (October?) 2011 with the official 2.3.6 update. And the only boot-loops I have, whether recovery is booted through the menu or salute, are when I flash something invalid.
Theraze said:
On mine, the 3 finger boot to recovery works fine. Then again, I haven't been on Froyo since Samsung and TMo said to stop using Froyo back in November (October?) 2011 with the official 2.3.6 update. And the only boot-loops I have, whether recovery is booted through the menu or salute, are when I flash something invalid.
Click to expand...
Click to collapse
Interesting... Perhaps if I went back to a gingerbread stock then upgraded to ICS the problem wouldn't occur?
I'll have to try that the next time I might need to return to stock.
Hello,
First I just want to say thank you to the mods for running a great forum and to the devs for keeping this device current.
I just struggled over a period of days with this issue.
The end result being, that you need to go to CM9 BEFORE you try JellyBean or later!
Just hope this helps someone else who missed that instruction.
Thanks devs/mods/everyone for keeping this device alive!!!! :good::good::good:
*EDIT* correction... i THINK you need to go CM9 Before trying something else
Not all ICS ROMs require CM9, but you must have at least CWM5 recovery to be able to flash CM9 or these ROMs. Follow ROMs' OP instructions.
I personally tested HebMIUI flash over Stock GB with CWM5 (Basic with a twist kernel) without going through CM9.
RESOLVED
This is 4th brick and i normally know how to fix it but this time i cant fix it
Ok so one day my phone was acting up it wouldn't turn on
I flashed repartioned and flashed csc/phone/froyo from hawk (ODIN) - everything was ok
Then i flashed gingerbread (odin)- phone turned on everything worked
Afterwards i rooted it (super one click)- it worked
got sgs kernel flasher
Flashed antonx kernel for gb
when i tried to install cm9 it didnt work i checked logs and got this (im using cmr 6.0.1.2)
I: Cant partition unsafe device: /dev/block/mmcb1k0p
I:Cant format unknown volume :/external_sd
I: cant format unknown volume: /emmc
Any ideas?
Also i was trying to do this
flash froyo + everything from hawk
Flash gingerbread
root
get sgs kernel flasher
flash kernel
install cm9
install cm10
restore my cm10 backup
That's a lot of steps that aren't needed.
http://forum.xda-developers.com/showthread.php?t=1358498 2nd post, eollie's one click to stock.
1)Run that, you have stock GB, root, and CWM all in 1 click.
2)Reboot to recovery, wipe and install CM9
3)Profit??
Ill try that
getochkn said:
That's a lot of steps that aren't needed.
http://forum.xda-developers.com/showthread.php?t=1358498 2nd post, eollie's one click to stock.
1)Run that, you have stock GB, root, and CWM all in 1 click.
2)Reboot to recovery, wipe and install CM9
3)Profit??
Click to expand...
Click to collapse
Thanks for the quick reply ill try that
What CM where you trying to install? Are phone doesn't use /emmc or /external_sd. That's why it failing. Wrong zip from the wrong phone. Look under your battery and tell us what the model number says before you go any further and end up with a true brick.
cmr
... after i installed antonx's kernel i tried to install cyanogen mod 9 and i was using the recovery included in that
And yes i know what phone i have.. sgs4g (sgh-t959v)
What Cm9? It's trying to write to partitions that this phone doesn't use. Link the ROM please.
link
Here you go
http://forum.xda-developers.com/showthread.php?t=1730954
That's really weird that your getting those errors. We don't use emmc or external_sd. Heimdall will get you set back up but I've never seen ANYONE in all the time I have had this phone report that error. That's why I was trying to make sure you had the right phone and ROM before you went any further.
now what?
hechoen said:
That's really weird that your getting those errors. We don't use emmc or external_sd. Heimdall will get you set back up but I've never seen ANYONE in all the time I have had this phone report that error. That's why I was trying to make sure you had the right phone and ROM before you went any further.
Click to expand...
Click to collapse
Ok so im back onto stock 2.3.6 and rooted... what kernel do i install? oh yea and hermdal doesnt want to work something net framework isnt installing (keeps on failing) and ive tried downloading it from microsoft too
Well, since antons didn't seem to work for you, flash the other one. lol
http://forum.xda-developers.com/showthread.php?t=1828171
-
how do i go from stock to mtd rom? (im on the "other one" i have a 32 gig sd card with EVERY single rom on that list, every kernel, every modem so basicly i dont have to download them)
before i just installed it through cmr but is that right?
I want to go from stock to cyanogen mod 9 MTD
Im creating a backup right now incase i mess up later
That's will work as long as the recovery is CWM 5.x or later. You used to have to flash CM7 first but I'm pretty sure Team Acid fixed it in the new CM9 build. Just check the MD5 of that zip you where trying to flash. Those errors are very strange and I'm thinking you might have accidentally gotten the wrong CM9.
hechoen said:
That's will work as long as the recovery is CWM 5.x or later. You used to have to flash CM7 first but I'm pretty sure Team Acid fixed it in the new CM9 build. Just check the MD5 of that zip you where trying to flash. Those errors are very strange and I'm thinking you might have accidentally gotten the wrong CM9.
Click to expand...
Click to collapse
Ok im installing..
Also if this works can i just restore my cm10 backup? or do i have to install cm 10 then the backup?
You can try to restore it. If it's the same version of CWM that you backed up from it should work. Just do all the wipes including system and data before you restore. If that doesn't work for some reason just flash CM10 than do an advanced restore of data only.
Works
ok it works... cid kinda scares me
I guess im going to restore my cm10 backup then...
And thanks for all the help
wow i have to wait five minutes between posts that sucks
restore
got an err when trying to restore E:/format_volume: format_rfs_decive failed on system
Guess im going to install cm10 then restore
What an exciting day... i went from froyo to gingerbread to ics and now to jb
Ahh
Ok so i found out that when i flashed kc1 to kc6 on odin i left the repartiton checked... so some files were missing and i guess that was the problem... what is phone efs clear on odin again? isnt it have to do with something with celluar communications
ok everything is back to normal (except a few apps) And thanks for helping out!
Some apps don't restore. Like xda for example. If I restore a backup it will say app not installed. When I reDL it from Play all my settings are still there though. So it's saving the cache and not the app. I've never really cared enough to look into it. lol
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