Related
When I have had trouble with a custom ROM, or changing file format, I usually odined back to 2.1 JDF with JAC's odin file and start again with a clean stock base. Doing this is kind of a PITA, having to root again and flash CWR before I could flash a custom rom.
Is there any benefit of using odin to revert to JDF anymore or can I get the same results if I use CWR to flash a rooted, de-odexed, stock 2.2 rom IE re-setting the phone and getting a clean "stock" base from which to flash a custom rom?
SykesAT said:
When I have had trouble with a custom ROM, or changing file format, I usually odined back to 2.1 JDF with JAC's odin file and start again with a clean stock base. Doing this is kind of a PITA, having to root again and flash CWR before I could flash a custom rom.
Is there any benefit of using odin to revert to JDF anymore or can I get the same results if I use CWR to flash a rooted, de-odexed, stock 2.2 rom IE re-setting the phone and getting a clean "stock" base from which to flash a custom rom?
Click to expand...
Click to collapse
Not sure if you've done this, but when you've first flashed CWR did you do a back up? From what I understand, with that back up you can just flash back to how your phone was prior to flashing the custom rom. I've never tried it though, I've always odin back to stock just in case.
Yea I normally make a nadroid backup via CWR and Ti backup of apps, then copy the SD card to my desktop. A nadroid backup will not re-flash the modem or kernel. The only way to do this was odin but now CWR can. This is part of my reason for asking the question in the OP. If CWR can flash rom, kernel and modem, is there any benefit to using ODIN to get back to a clean stock rom?
Flashing back to stock is always the cleanest way to go. You do not risk
"ghost" remnants from old flashings. Nice clean slate... is always the best way to go. Reverting back to stock from CWR backup I have not do that it would defeat the purpose of wiping old data from the firmware. So, I always do a reflash back to stock when putting Real new software. I do not if I am just upgrading from older version of custom rom xx to a newer version.
Oka1,
thanks. Do you use JAC's JFD, link, or is there a mildly tweaked Odin file that will give a rooted stock?
SykesAT said:
Oka1
thanks. Do you use JAC's JFD, link, or is there a mildly tweaked Odin file that will give a rooted stock?
Click to expand...
Click to collapse
If you go to the vibrant directory bible there are stock rims that have been rooted.
tc7276 said:
If you go to the vibrant directory bible there are stock rims that have been rooted.
Click to expand...
Click to collapse
Thanks. Although the bible has CWR rooted roms, I do not see any that are ODIN. Which was sort of the reason for this thread, CWR vs ODIN to get a clean, ghost free, platform to flash a custom rom.
So, disclaimer. I'm an idiot today. Don't mind me.
So today I decided to go to jt's CM7 from ComRom 2.1 (non gingerbread)
Backed up everything, made a nandroid, wiped everything installed cwm 3.x.
Went and started to flash CM7. That didn't exactly like me too much as it went into a 45min long bootloop saying that it failed. No big deal. Nows the fun part. Rewiped everything, started to reinstall the ComRom. That didnt like me either, it says that it cannot mount Cache/recovery/log etc. So I thought. Okay, well I can always ODIN!
Ideas folks?
Thanks in advance.
Sorry about the bump/post, forgot to edit this one instead.
OK! Ignore above, used odin so now im on stock eb01 but still when i use odin to flash cwm 3.0.2.8x it still says it cannot open or mount cache/recovery/log and recovery/last_log.
At this point, I just want to get it so I can nandroid back to where i was on comrom.
Ideas?
What I did, ODIN the atlas2.2 and ebo1 Froyo package, boots up to stock fine no problem.
Attempted to flash CWM 3.0 in ODIN. flashes fine.
3 finger salute. doesnt boot, have to hold it for about a second then cwm just pops up saying it cant mount recovery.
Then I re ODINd eb01, deleted all voodoo, cwm, update.zip etc from sdcard.
re tried to flash cwm 3.0
same thing.
Completely lost haha
New ; odin's dl09, OTA'd up to current. What steps should I take next given my issues with CWM?
By deleting the file named clockworkmod on your sd card, you most likely deleted all of your nandroid backups. unless you backed up you sd card to your computer, im pretty sure they are gone. Im sorry. As far as the rest of your problems... I know a stock kernal will overwrite clockworkmod every reboot.
schu9120 said:
By deleting the file named clockworkmod on your sd card, you most likely deleted all of your nandroid backups. unless you backed up you sd card to your computer, im pretty sure they are gone. Im sorry. As far as the rest of your problems... I know a stock kernal will overwrite clockworkmod every reboot.
Click to expand...
Click to collapse
I did back up everything, made sure of that haha. So I should try reflashing a kernal? or would that have been included in the ODIN package/ OTA updates I did?
Thanks
tkirane said:
I did back up everything, made sure of that haha. So I should try reflashing a kernal? or would that have been included in the ODIN package/ OTA updates I did?
Thanks
Click to expand...
Click to collapse
there may have been a kernel in the ota updates, the problem us you need a non stock kernel..stock ones over write recovery in every boot
My suggestion....
odin eb01 with the atlas 2.2pit and repartition checked.
Fully boot after eb01 flash
Odin cwr 3-30-all and immediately three finger boot into cwr....wipe everything
Flash cm7 build 7/4 completely reboot
Use the power menu to access recovery...this time it will be cwr 4.x.x.x flash the
Cm7 build your want with no wiping, thats what works for me
Sent from my SCH-I500 using XDA App
efan450 said:
there may have been a kernel in the ota updates, the problem us you need a non stock kernel..stock ones over write recovery in every boot
My suggestion....
odin eb01 with the atlas 2.2pit and repartition checked.
Fully boot after eb01 flash
Odin cwr 3-30-all and immediately three finger boot into cwr....wipe everything
Flash cm7 build 7/4 completely reboot
Use the power menu to access recovery...this time it will be cwr 4.x.x.x flash the
Cm7 build your want with no wiping, thats what works for me
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I believe I attempted that last night at home, I will definitely try again after I am out of work. Would you happen to have a link to download of cwr 3-30-all?
Also, would I be correct in the assumption that same steps would apply to ComRom installation.
Also too, I am currently on the ED04 non-rooted stock OTA. Do same rooting methods that I used way back on dl09 still apply?
Sorry for the multiple idiotic questions, just much different this time around do to the inability for CWM (either 2.5 or 3.0) to be able to locate/mount the cache/recovery/log.
Would that have to do with Root? thats my main concern is getting into CWM for it to say it cannot mount. After this point I have it reboot system and it does not boot up again. It boots into CWM immediately. So it is unable to bot back into the actual phone mode. So then I reflash dl09 or eb01 in ODIN and start over.
tkirane said:
I believe I attempted that last night at home, I will definitely try again after I am out of work. Would you happen to have a link to download of cwr 3-30-all?
Also, would I be correct in the assumption that same steps would apply to ComRom installation.
Also too, I am currently on the ED04 non-rooted stock OTA. Do same rooting methods that I used way back on dl09 still apply?
Sorry for the multiple idiotic questions, just much different this time around do to the inability for CWM (either 2.5 or 3.0) to be able to locate/mount the cache/recovery/log.
Would that have to do with Root? thats my main concern is getting into CWM for it to say it cannot mount. After this point I have it reboot system and it does not boot up again. It boots into CWM immediately. So it is unable to bot back into the actual phone mode. So then I reflash dl09 or eb01 in ODIN and start over.
Click to expand...
Click to collapse
rooting has no effect on wheather or not recovery (cwm) sticks, its the stock kernel that is overwriting it as soon as you boot. com rom 2.0 comes with a kernel in the flash so if you do this exactly you'll be on comrom rooted with recovery
The steps for going to com rom would be the same this method may be overkill but it should get you cleared up....you said you odin'd ebo1 and the atlas pit before in your previous post,so im going to assume you know how to properly get into download mode and what do, and not do in odin, so down load cwr 3-30-fix all here, and save it on your pc in your odin folder
http://forum.xda-developers.com/attachment.php?attachmentid=556634&d=1301538947
download com rom (ukb) 2.0 either from your phone or from your pc, connect your usb cord and move it to the root of your sd card.(ie.not in a folder)
pull the battery,and odin the ebo1 tar with the atlas 2.2 with repartition checked, when its done insert batt and boot fully.
when done pull batt, odin cwr 3-30-fix all, when done insert batt and right away hold volume up, down, and power and continue to hold until your see the red cwr screen.
wipe data(factory reset)/wipe cache/go to advanced and wipe dalvik
go to install zip from sd, and find the comrom ukb zip and select install...when its done select reboot and done...at this point your phone will look like its not doing anything and its important to be patient you will hear the voodoo lady talking to you and this is good, when your phone fully boots hit the power button and select recovery and at the recovery screen go to backup and restore and select nandroid backup and run it, when its done reboot and enjoy
if you want to go to ukb 2.1 just download the patch, boot into recovery and flash, no wipe needed.
as a side note the 3-30 file you odined will not be your recovery after this is complete because comrom comes with its own recovery, after you get on to this rom the recovery that came with it will be the one you see.
i used these same steps to go to cm7 but i have only had success by, odin cwr 3-30 fix all, wipe everything and then install build date 7/4 and reboot completely, and power menu to recovery and flash the 7/13 build.
efan450 said:
rooting has no effect on wheather or not recovery (cwm) sticks, its the stock kernel that is overwriting it as soon as you boot. com rom 2.0 comes with a kernel in the flash so if you do this exactly you'll be on comrom rooted with recovery
The steps for going to com rom would be the same this method may be overkill but it should get you cleared up....you said you odin'd ebo1 and the atlas pit before in your previous post,so im going to assume you know how to properly get into download mode and what do, and not do in odin, so down load cwr 3-30-fix all here, and save it on your pc in your odin folder
http://forum.xda-developers.com/attachment.php?attachmentid=556634&d=1301538947
download com rom (ukb) 2.0 either from your phone or from your pc, connect your usb cord and move it to the root of your sd card.(ie.not in a folder)
pull the battery,and odin the ebo1 tar with the atlas 2.2 with repartition checked, when its done insert batt and boot fully.
when done pull batt, odin cwr 3-30-fix all, when done insert batt and right away hold volume up, down, and power and continue to hold until your see the red cwr screen.
wipe data(factory reset)/wipe cache/go to advanced and wipe dalvik
go to install zip from sd, and find the comrom ukb zip and select install...when its done select reboot and done...at this point your phone will look like its not doing anything and its important to be patient you will hear the voodoo lady talking to you and this is good, when your phone fully boots hit the power button and select recovery and at the recovery screen go to backup and restore and select nandroid backup and run it, when its done reboot and enjoy
if you want to go to ukb 2.1 just download the patch, boot into recovery and flash, no wipe needed.
as a side note the 3-30 file you odined will not be your recovery after this is complete because comrom comes with its own recovery, after you get on to this rom the recovery that came with it will be the one you see.
i used these same steps to go to cm7 but i have only had success by, odin cwr 3-30 fix all, wipe everything and then install build date 7/4 and reboot completely, and power menu to recovery and flash the 7/13 build.
Click to expand...
Click to collapse
I definitely know my way around odin and recovery haha thank you very much for the help. I'll try it out once I am out of work and let you know how it goes. I was doing just that only with cwr 3.0 not the fix all. so hopefully that does the trick. Hopefully I wont be seeing and mount cache errors.
So I did use the recovery-all last night to no avail, still says that it cannot mount certain items.
I have to three finger salute it, then let go after a while for it to boot to CWM, then it cannot mount cache:recovery/command and recovery/log and dev/block/st111
Also when trying to wipe data it cannot mount datadata
Then I do reboot system now and it reboots to CWM with same errors.
EDIT : Found an ODIN for EC01 ComRom 2.0
Going to try that out and see what happens.
I'm an idiot. I realized I kept ODIN'ing pit with CWM, aka, BAD idea. All fixed and running.
Thanks everyone!
tkirane said:
I'm an idiot. I realized I kept ODIN'ing pit with CWM, aka, BAD idea. All fixed and running.
Thanks everyone!
Click to expand...
Click to collapse
Lol glad to hear your up and running...I've had my share of idiotic moments and lucky our phones are pretty brick proof...and now we can add to the list that using a pit file and trying to odin cwr while it won't allow your phone to work..... you can still recover even from this with out perma-bricking!
Sent from my SCH-I500 using XDA App
Well, I was previously running Comm rom, and i decided to switch to CM7 7/13
This didn't go so well. I Odin'd DL09 with atlas and repartitioned then installed Cmw and still Status 7 when I try to install. Then I tried installing 7/4 and it would just say something like "Checking BML" Or something, i forgot... and it would just reboot into cwm. I was running JT's cwm fix, and i tried with cwm all... I don't know what to do. Now my fascinate won't install comm rom, and every rom install just leads up to booting up in cwm.. no samsung logo.. Help??
Edit: Phone is now in "Manual mode"
i guess samsung recovery? but it wont boot. It just reboots into the same recovery after i press "reboot system now"
please? :'(
Just do this
after fighting with my phone yesterday trying to get it running this is what i did
Step one may be unnecessary but this is what i did.
1) Odined ED01 image let it boot. then Odind CWM3 3 finger salute. Flashed CommRom 2.0 when that was done i booted into CWM and disabled the VooDoo rebooted when the conversion was done.... i did step 2
2) in the OP of cm7 flash or odin the cwm
then flash the 07/04...
once that is up use the shutdown menu to access the Orange [cwm 4.0] cwm.
if you do a three finger salute it takes you to the RED [CWM 3.0] cwm.
Then flash the updates.
And suspect there was an issue with the Voodoo even though it said it was disabled. Good Luck
xwhofarted said:
Just do this
after fighting with my phone yesterday trying to get it running this is what i did
Step one may be unnecessary but this is what i did.
1) Odined ED01 image let it boot. then Odind CWM3 3 finger salute. Flashed CommRom 2.0 when that was done i booted into CWM and disabled the VooDoo rebooted when the conversion was done.... i did step 2
2) in the OP of cm7 flash or odin the cwm
then flash the 07/04...
once that is up use the shutdown menu to access the Orange [cwm 4.0] cwm.
if you do a three finger salute it takes you to the RED [CWM 3.0] cwm.
Then flash the updates.
And suspect there was an issue with the Voodoo even though it said it was disabled. Good Luck
Click to expand...
Click to collapse
That's the thing... It wont boot to anything i install on it.. But it sure as hell boots to ANY cwm i install... and it also boots to normal recovery in the absence of a cwm....
Can you get back to stock using odin? If you can try flashing a custom kernel after you flash the cwm recovery.
Sent from my SCH-I500 using XDA App
garywojdan81 said:
Can you get back to stock using odin? If you can try flashing a custom kernel after you flash the cwm recovery.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I can flash the DL09 with odin... but ive been there... 20 times. I havent tried a kernel but it probably wouldnt work seeing as it only boots back into cwm. I'm desperate...
EDIT: flashed EB01 voodoo... still boots into CWM... omg.
jamespweb1503 said:
I can flash the DL09 with odin... but ive been there... 20 times. I havent tried a kernel but it probably wouldnt work seeing as it only boots back into cwm. I'm desperate...
EDIT: flashed EB01 voodoo... still boots into CWM... omg.
Click to expand...
Click to collapse
Have you tried flashing the official vzw eb01..(not dl09 and not eb01voodoo) file with pit and repartition checked? If not do that and let it boot completely. You need to do this to make sure your ext4 partition is formatted to remove voodoo.
After you odin official vzw eb01 with the pit file and repartition checked let it boot fully.then odin 3-30 recovery and immediately boot to cwr...if it boots up fully you will have to re odin recovery.
At this point wipe everything and flash com rom 2.0 that will give you root, recovery and the rom....from there you can go to com rom 2.1or whatever your want but your phone should be up and running
Sent from my SCH-I500 using XDA App
efan450 said:
Have you tried flashing the official vzw eb01..(not dl09 and not eb01voodoo) file with pit and repartition checked? If not do that and let it boot completely. You need to do this to make sure your ext4 partition is formatted to remove voodoo.
After you odin official vzw eb01 with the pit file and repartition checked let it boot fully.then odin 3-30 recovery and immediately boot to cwr...if it boots up fully you will have to re odin recovery.
At this point wipe everything and flash com rom 2.0 that will give you root, recovery and the rom....from there you can go to com rom 2.1or whatever your want but your phone should be up and running
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I love you <3
OK, so it has been a while since I have had to flash recoveries etc... Anyway, I Odin'ed back to stock today because I had to go to the Verizon store to talk about my replacement phone so I wanted to have it unrooted. Anyway, now I am trying to get CM7 back on for the time being but I can't get in to CWM. I tried pushing the cwm_recovery_all tar file via ODIN and when I do the three finger boot, it still brings me to the stock recovery and when I hit apply update.zip it fails.
What the heck am I doing wrong? I figured I could just get recovery on there and not have to worry about "rooting" since all the ROM's have that built in anyway.
Any help is appreciated!
Nevermind, I think I figured it out
For those of you that don't know, you have to flash a custom kernel before letting the phone boot after flashing CWM, since the stock kernel will overwrite it on boot
Kevin Gossett said:
For those of you that don't know, you have to flash a custom kernel before letting the phone boot after flashing CWM, since the stock kernel will overwrite it on boot
Click to expand...
Click to collapse
Nope, all you have to do is leave the battery out and as soon as ODIN passes and resets the phone, unplug the phone from the PC so it can't reboot. Then just use the 3 button method to get in to recovery.
Overall it is pretty simple. Here were my steps to get back to CM7 from 100% stock ED04:
1) Push cwr_recovery_3_30_fix (or something like that) tar file in ODIN wit hthe battery pulled
2) Let ODIN finish and say RESET, then PASSED and pull the USB cable out so the phone can't reboot.
2a) Put battery back in
3) Once in red recovery, flash jt's cwm4 fix zip in CM7 thread
4) Flash CM7
5) Flash gapps
6) Profit
I didn't have to flash any custom kernels or anything.
xceebeex said:
Nope, all you have to do is leave the battery out and as soon as ODIN passes and resets the phone, unplug the phone from the PC so it can't reboot. Then just use the 3 button method to get in to recovery.
Overall it is pretty simple. Here were my steps to get back to CM7 from 100% stock ED04:
1) Push cwr_recovery_3_30_fix (or something like that) tar file in ODIN wit hthe battery pulled
2) Let ODIN finish and say RESET, then PASSED and pull the USB cable out so the phone can't reboot.
2a) Put battery back in
3) Once in red recovery, flash jt's cwm4 fix zip in CM7 thread
4) Flash CM7
5) Flash gapps
6) Profit
I didn't have to flash any custom kernels or anything.
Click to expand...
Click to collapse
I'm not trying to be a jerk so don't take this the wrong way, but kevin is right..it is the kernel that re-writes recovery on boot.
The way you are doing it, jt has a kernel included with the rom and that kernel Is whats making your recovery stick when you flash the rom. if you were to odin recovery on Stock phone and just flash a rom w/o a kernel and try to get to recovery again it would be the original stock recovery.
Don't get me wrong what you did is correct, I just want to make sure if you have to do this again, you don't have problems, it is the kernel that is what prevents the stock recovery from coming back.
Sent from my SCH-I500 using XDA App
efan450 said:
I'm not trying to be a jerk so don't take this the wrong way, but kevin is right..it is the kernel that re-writes recovery on boot.
The way you are doing it, jt has a kernel included with the rom and that kernel Is whats making your recovery stick when you flash the rom. if you were to odin recovery on Stock phone and just flash a rom w/o a kernel and try to get to recovery again it would be the original stock recovery.
Don't get me wrong what you did is correct, I just want to make sure if you have to do this again, you don't have problems, it is the kernel that is what prevents the stock recovery from coming back.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
My point is that I was able to boot in to red recovery (2.5.1.x) BEFORE flashing any custom kernel. I understand that CM7 has a kernel built in, but I was able to boot in to both the red recovery and jt's cwm 4 fix (4.0.1.0) before flashing any ROMs/Kernels. I wasn't even rooted (flashing CM7 is what rooted me).
After re-reading what he wrote, the way he says it is correct. I must have read it wrong the first time. So I apologize for saying "Nope." For some reason I read it as if he was saying I had to flash a custom kernel before being able to boot in to any recovery. He is just saying that you can't let the phone fully boot after pushed the recovery (which is what I ended up doing in my steps).
Sorry for the confusion.
No problem...glad you didn't take offense I'm just nearly thinking of all the noobs that are just getting into this kind if stuff and when they read the thread they might be misinformed...
that being said I've been on cm7 for a while and I know not to flash with anything other than the included recovery, I can confirm power button menu gets you to the new blue recovery but if you three finger salute it (done on accident just out of habit) you will get to an older recovery! In my case the old red one....Weird having both on the phone simultaneously, but it's no prob as long as we only use the new recovery to flash anything.
Sent from my SCH-I500 using XDA App
Every ROM zip file I attempt to flash via CWM or TWRP doesnt work. I was on stock ICS (4.0.4) which I flashed using Odin. Every JB rom, stock or custom I attempt to flash with a recovery freezes either at boot up or first screen of initial setup. No errors are given on actual flash, it always looks good. . I wiped everything I can wipe, which is everything but emmc I think. What could be the problem? I have now flashed official JB through Odin twice with no issues.
Do you check that the ROM is downloaded properly by checking the md5 hash?
EVOO2 said:
Every ROM zip file I attempt to flash via CWM or TWRP doesnt work. I was on stock ICS (4.0.4) which I flashed using Odin. Every JB rom, stock or custom I attempt to flash with a recovery freezes either at boot up or first screen of initial setup. No errors are given on actual flash, it always looks good. . I wiped everything I can wipe, which is everything but emmc I think. What could be the problem? I have now flashed official JB through Odin twice with no issues.
Click to expand...
Click to collapse
Try flashing a new recovery using odin then try to flash the rom in recovery afterwards.
Sent from my SGH-T989 using Tapatalk
richardlibeau said:
Try flashing a new recovery using odin then try to flash the rom in recovery afterwards.
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Ive flashed twrp 2.5 twice through odin and then tried to flash a rom with no improvement. Im really stumped 'cause flashing roms with odin works fine everytime, so it would seem nothings physically wrong with my device. Should I try a different recovery program? Using cwm and twrp give the same result, so Im skeptical a third recovery would be any different.
cheers
EVOO2 said:
Ive flashed twrp 2.5 twice through odin and then tried to flash a rom with no improvement. Im really stumped 'cause flashing roms with odin works fine everytime, so it would seem nothings physically wrong with my device. Should I try a different recovery program? Using cwm and twrp give the same result, so Im skeptical a third recovery would be any different.
cheers
Click to expand...
Click to collapse
Only thing i can think of is look at the file format that youre trying to flash.
Is it zip? tar?
I may be wrong but cwm only works for .zip files from my experience. not .tar md5 etc.
why do you need to flash it via cwm? if its flashing through odin whats the problem?
It sounds like what ^^^^ is saying. Recovery flashes zip files and Odin flashes tar files. Don't confuse the zip files your pc uses to download the files with these.
When using odin I have to use ROM s which are .tar, so this basically limits me to stock ROMS. The custom ROMS are .zip which I can only flash with a custom recovery like twrp or cwm. I'd obviously like to flash the custom ROMS which are .zip , however it isn't working for me as I mentioned in the opening post . Not sure how to fix this problem .
EVOO2 said:
When using odin I have to use ROM s which are .tar, so this basically limits me to stock ROMS. The custom ROMS are .zip which I can only flash with a custom recovery like twrp or cwm. I'd obviously like to flash the custom ROMS which are .zip , however it isn't working for me as I mentioned in the opening post . Not sure how to fix this problem .
Click to expand...
Click to collapse
extraxt the rom that your saying is .zip. it "should" extract a file that will be something odin will recognize
dweeezy said:
extraxt the rom that your saying is .zip. it "should" extract a file that will be something odin will recognize
Click to expand...
Click to collapse
Good idea. In a recovery zip file will be a couple of folders. One of them will have a tar file you can flash in the phone or pda a lot in Odin.
Thanks for the suggestion but I had no luck . I have tried extracting padawan JB and a debloated stock JB rom and they extract many files, folders, apks but no tar I could locate. Also I am not sure even if there was a tar i could use if it would be safe to use. If all this was good, it would still be a cumbersome workaround and wouldnt fix my problem of not being able to get a ROM installed via recovery to work.If I have no choice I'll use odin to flash custom ROMs (if there is a way) but Id rather get it to work with recovery.
EVOO2 said:
Thanks for the suggestion but I had no luck . I have tried extracting padawan JB and a debloated stock JB rom and they extract many files, folders, apks but no tar I could locate. Also I am not sure even if there was a tar i could use if it would be safe to use. If all this was good, it would still be a cumbersome workaround and wouldnt fix my problem of not being able to get a ROM installed via recovery to work.If I have no choice I'll use odin to flash custom ROMs (if there is a way) but Id rather get it to work with recovery.
Click to expand...
Click to collapse
If you're flashing between TW based to AOPS, or pretty much from a rom to a completely different rom, you will need to WIPE your data too, or better, do a complete wipe (factory reset). I had this issue when moving from Stock TW-based rom to Padawan JB rom. I did a factory reset (complete wipe) and it booted fine. But then again, I'm used to TW so I flashed that back.
fbauto1 said:
If you're flashing between TW based to AOPS, or pretty much from a rom to a completely different rom, you will need to WIPE your data too, or better, do a complete wipe (factory reset). I had this issue when moving from Stock TW-based rom to Padawan JB rom. I did a factory reset (complete wipe) and it booted fine. But then again, I'm used to TW so I flashed that back.
Click to expand...
Click to collapse
I've wiped everything I can wipe between flashes (includes factory reset), many times trying both TWRP and CWM for flashing and wiping with no luck unfortunately. The wiping doesnt seem to help, different custom recoveries don't help, so I'm stumped as to what the problem could be.
EVOO2 said:
I've wiped everything I can wipe between flashes (includes factory reset), many times trying both TWRP and CWM for flashing and wiping with no luck unfortunately. The wiping doesnt seem to help, different custom recoveries don't help, so I'm stumped as to what the problem could be.
Click to expand...
Click to collapse
What roms are you trying to flash? Sometimes ive seen where you must rename them or do specific things.
dweeezy said:
What roms are you trying to flash? Sometimes ive seen where you must rename them or do specific things.
Click to expand...
Click to collapse
Ive tried padawan JB, debloated rooted canadian JB rom, and debloated ATT rom.
dweeezy said:
What roms are you trying to flash? Sometimes ive seen where you must rename them or do specific things.
Click to expand...
Click to collapse
Ive tried padawan JB, debloated rooted canadian JB rom, and debloated ATT rom.
OP, are you still having this issue? Were you able to resolve it?
I have the exact same issue as you. Exactly the same.
513263337 said:
OP, are you still having this issue? Were you able to resolve it?
I have the exact same issue as you. Exactly the same.
Click to expand...
Click to collapse
Me too. Every rom freezes during the app optimization screen...usually at about 3/4th the way through. What's going on???
*edit* Tried to restore factory w/Odin. I'm bricked now. Time for some JTAG love.
Exactly the same issue here.
Every jelly bean ROM, 4.1 or 4.2, stock or custom, as long as I install them via recovery, it either doesn't boot up or gets stuck on the first screen.
If I use ODIN to install the stock ROM, it works fine.
Driving me nuts...
Just throwing suggestions out there but try sideloading the rom and see if itll install that way? Also are you odin flashing recovery? Maybe try to load twrp through goomanager and see if maybe recovery is corrupted?
Sent from my SAMSUNG-SGH-I717 using xda premium