Database Users

[Q] Help

tried to install custom rom, didn't work out. tried to do a restore the phone gets to a point where it stops and says "lost+found" and won't go any further. any suggestions?
Thanks
Also when i try to reboot in recovery i get this "E:can't open/cache/recovery/log" and stops right there. Any ideas??

Odin is your friend look it up!!
Sent from my SPH-D700 using XDA App

Have odin and still can't get past the places on my previous post. Every time i try to reboot i get the "clockworkMod Recovery v2.5.1.0"
"E:can't open /cache/recovery/log"
just like that half way down the screen. won't go any further. need some serious help.

you shouldnt be using recovery mode, you need to be in download mode. power off your device then hold 1 and power on again. you should get a little android with a shovel. thats the mode your phone needs to be on in order to odin it back

Skrewup5 said:
you shouldnt be using recovery mode, you need to be in download mode. power off your device then hold 1 and power on again. you should get a little android with a shovel. thats the mode your phone needs to be on in order to odin it back
Click to expand...
Click to collapse
At this point the only way i can power it down is to remove the battery and even when i hold 1 and power back up it goes into clockwork recovery mode instead of download mode.

thats incredibly strange. ive had the same problem as you before when i installed a bunk rom but it didnt affect download mode. see if you can flash over stock dk28, after factory resetting 3 times, wiping cache and then dalvik. i think the reason its stuck on the samsung screen is because the last rom you installed is conflicting with something. but if you can get another to work, it may hopefully at least allow you to enter recovery so you can odin.
i may just be talking out my ass here, but its def a software issue, as opposed to hardware.
or it may even be a kernel conflict, make sure the one youre using is compatible with the rom

Skrewup5 said:
thats incredibly strange. ive had the same problem as you before when i installed a bunk rom but it didnt affect download mode. see if you can flash over stock dk28, after factory resetting 3 times, wiping cache and then dalvik. i think the reason its stuck on the samsung screen is because the last rom you installed is conflicting with something. but if you can get another to work, it may hopefully at least allow you to enter recovery so you can odin.
i may just be talking out my ass here, but its def a software issue, as opposed to hardware.
or it may even be a kernel conflict, make sure the one youre using is compatible with the rom
Click to expand...
Click to collapse
A friend at work, who has an EVO wanted to work on my phone while I was out of the office on business. He was able to finally get it to enter download mode, flashed odin and froyo DK28 and got me back up. Just a temporary glich that took several tries for some reason. Anyway I'm back on 2.2.1 and looking forward to rooting again but probably going to download a different rom. Thanks for help and advise. also good to have phone savy friends at work. Thanks Ashley.
Dana

Im glad it was all resolved haha. try the new bonsai4all 2.0. its very easy to install

stuck on white htc screen

So i have a desire hd from Three, which is unlocked and unbranded, i rooted the phone via the visionary method, got s-off, used rom manager to install clockwork mod recovery which was 2.5.1 something rather, then i created a backup, upgraded to clockwork 3.0.0.1, tried to install the cyanogenmod 6.1.3 via rom manager but didnt work, so i downloaded the zip file manually and tried to update via clockwork mod recovery now in 3.0, restarted, and am now stuck at the main HTC screen. Pulled the battery, then went back into clockwork recovery, tried to recover the backup i made, rebooted, but still stuck on htc white screen... dont know what to do help!

You could try flashing a RUU to go back to stock 1.32 would be best or you would need to downgrade to root, or you could try getting another rom image on your SD card isnt clockwork 3 4 ginger bread nightlies?
Just throwing ideas out there. Personally I would go woth the RUU.

Thanks for the reply, i remember finding some links with ruu's but i'm not sure which one i need and how to use it ?

Sorry just thought the other thing is how long did you leave it. I have read about people leaving for 30 mins and then it boots..

Start downloading this. Its the RUU_Ace_HTC_WWE_1.32.405.6_Radio_12.28b.60.140e_26 .03.02.26_M_release_155891_signed
http://www.multiupload.com/N333WKVW6M
while downloading leave your phone to boot it might surprise you..

I left it for a while but maybe not long enough, perhaps 15 minutes at one point? i'll try again, should i wipe data in clockwork and then reflash the cyanogenmod again? is it ok to keep the phone plugged into the computer via usb?

Sorry, once downloaded just run the EXE, it will walk you through the steps.
The Dev section has a lot of useful stuff in it for this sort of thing the 1st post http://forum.xda-developers.com/showthread.php?t=936214 is pretty usefull.

djamorpheus said:
I left it for a while but maybe not long enough, perhaps 15 minutes at one point? i'll try again, should i wipe data in clockwork and then reflash the cyanogenmod again? is it ok to keep the phone plugged into the computer via usb?
Click to expand...
Click to collapse
Worth a go whilst downloading, I would wipe 1st. Its good you still have your recovey partition (clockwork) so you should be fine. Use the RUU as the last resort as it will wipe recovery part and loose SOFF etc.. But should fix the phone.

Right so i've wiped data/factory reset and cache partition and dalvik cache, then went to choose zip from sd, chose update-cm-6.1.3-DesireHD-signed.zip, says Welcome to CyanogenMod-6.1.2-desireHD (strange?) completed. Now went to Reboot system now and waiting, still on HTC screen.

is it possible to put another rom on the sd card? i dont have a computer that i can plug the mini sd into, possible in recovery mode?

djamorpheus said:
is it possible to put another rom on the sd card? i dont have a computer that i can plug the mini sd into, possible in recovery mode?
Click to expand...
Click to collapse
yes, but i dont know how of the top of my head, i will have a look in the dev forums, i think you use fastboot and u can push files. Hopefully someone with a bit more knowledge will see this post soon. I will have a look though.

so its been 30 minutes, and it's still at the htc screen... what should i do? should i try the RUU ? i dont want to brick my phone...

from what i can find fastboot will not push files, adb but may not connect on splash screen. You could just try pulling the battery and leaving it again to boot for a bit, mine has hung before like that. The Ruu should go through and connect to phone and go through flashing. Do you have another phone that could take the SD card? im gonna boot my phone to recovery and try to push a rom to it or file.

ok i am reading this post,http://forum.xda-developers.com/showthread.php?t=558812
what i would do is goto recovery mode,
he command is:
adb shell mount /sdcard
adb push c:\******.*** /sdcard
exemple with g:\update.zip :
adb push g:\update.zip /sdcard
usefull when wrong rom flashed and no sdcard reader ^^

So i downloaded a cyanogenmod 7 nightly build, installed with with clockwork 3.0.0.5, and it worked, booted in, but had a continuous logo loop, going to try leedroid

Good luck, Leedroid rocks, thats what i use. I would say if it is still looping try the ruu and then start again. The RUU will esentially factory reset.

Installed the latest Cyanogen nightly build #23, and it works perfectly now should i keep it? or should i try leedroid? i kind of want to keep using htc sense, as i have all my contacts on it..

Up to you really. I went back to leedroid because it seems faster and more stable for me and I like some of the sense widgets.
Sent from my Desire HD using XDA App

[Q] EVO Rom/Root problems

I am having some serious issues with my evo. I have tried 10 different methods, googled 100 different help guides and still no fix.
I had originally rooted my phone using simple root and put the "fixed" froyo rom on there. Everything worked fine, but I was outdated and having some really slow issues so I wanted to try a new rom...Fresh.
Well I tried a few methods, but I somehow reverted my evo back to a nonroot of the original OS. Whenever i go into hboot, my recovery does not work. I push the PC36img and load it, then restart then I attempt to go to my recovery where it gives me the error picture with the yellow/red triangle. I then select recovery (after pressing UP volume and powerbutton) and try to load update from sd card. Everytime I do that I get a Failed error.
I've tried to reroot using several methods off this website, I've done everything I can to get it working but can't. Any help would be GREATLY appreciated!

Try reflashing your recovery image.

BTW I have hboot 79.0 with S-ON, so it looks like I def became unrooted.

noweakness said:
BTW I have hboot 79.0 with S-ON, so it looks like I def became unrooted.
Click to expand...
Click to collapse
Not sure how it would have just unrooted itself. I would run an RUU from here: http://forum.xda-developers.com/showthread.php?t=884060
Then, I would re-root and start clean again.

Heaterz16 said:
Try reflashing your recovery image.
Click to expand...
Click to collapse
I have a recovery-ra.img, how do I tell it to flash it?
I pulled up this list of recovery files, is there a particular one I should use?
htt p://goo-inside.me/amon_ra/supersonic/

Heaterz16 said:
Not sure how it would have just unrooted itself. I would run an RUU from here: http://forum.xda-developers.com/showthread.php?t=884060
Then, I would re-root and start clean again.
Click to expand...
Click to collapse
Ok I downloaded the top item:
RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed
Ran the exe, surprisingly picked up my phone and started the image update. My phone restarted and it forced closed the app on my computer. Now I have a new HTC logo for about 5 min on my phone not doing anything. Should I wait it out or restart my phone?

noweakness said:
Ok I downloaded the top item:
RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed
Ran the exe, surprisingly picked up my phone and started the image update. My phone restarted and it forced closed the app on my computer. Now I have a new HTC logo for about 5 min on my phone not doing anything. Should I wait it out or restart my phone?
Click to expand...
Click to collapse
I would have waited about ten minutes then restarted the phone. If the phone is stuck at the HTC logo, then I would go ahead and re-run the RUU.
Let me know how it turns out.

Heaterz16 said:
I would have waited about ten minutes then restarted the phone. If the phone is stuck at the HTC logo, then I would go ahead and re-run the RUU.
Let me know how it turns out.
Click to expand...
Click to collapse
ok, finally got it working. Had to restart the phone manually and try it on a different computer. It updated it to the newer version of android and hboot, thank goodness! That was the easiest and most productive thing I've been able to do so far, thanks!
Well now I try to boot into recovery and get the same error:
can't open /cache/recovery/command
Then I get :
E: signature verification failed
Installation aborted
When i try to load update from sdcard

noweakness said:
ok, finally got it working. Had to restart the phone manually and try it on a different computer. It updated it to the newer version of android and hboot, thank goodness! That was the easiest and most productive thing I've been able to do so far, thanks!
Well now I try to boot into recovery and get the same error:
can't open /cache/recovery/command
Then I get :
E: signature verification failed
Installation aborted
When i try to load update from sdcard
Click to expand...
Click to collapse
Ok, so, I think you said you got the RUU working which would have completely restored the phone to unrooted and stock from factory.
Now, you need to re-root your phone using one of the methods on xda. I used the manual method here: http://forum.xda-developers.com/showthread.php?t=829045. However, many people have had success with the one-click methods.
After you re-root (which will likely included installing a recovery), select a rom you want to try, boot to recovery, wipe and flash it. A great starter ROM is MikFroyo 4.6 or 4.5.

Try downloading the PC36IMG.zip from here: http://forum.xda-developers.com/showthread.php?t=705026
put that on the root of your SD card, then boot into HBOOT and it should find that PC36IMG.zip after a few seconds and ask if you want to flash it. Choose yes and let it finish. Should then be able to reboot into recovery.

ok thanks, i'll try it when I get back home

jesuspgt said:
Try downloading the PC36IMG.zip from here: http://forum.xda-developers.com/showthread.php?t=705026
put that on the root of your SD card, then boot into HBOOT and it should find that PC36IMG.zip after a few seconds and ask if you want to flash it. Choose yes and let it finish. Should then be able to reboot into recovery.
Click to expand...
Click to collapse
Ok, I tried this method...the filesize of pc36img.zip is only 3.5mb, but it didn't seem to work. It scanned the file then just went back to the hboot screen with my options never asking to flash.
I'm going to try to reroot using the other method now...

So I clicked the link and he forwarded to the autoroot.bat page so I used his method. It worked well (the 2nd time around) all the way until it started to push amon_ra_1.8-mod.... then after that it says rebooting into the bootloader, and it reboots into it and just says waiting for phone...
It does appear that my phone is rooted now, but my recovery is still not working. If I use ROM manager will it work since my phone is rooted or do I need to have a rooted ROM to run it off of?

noweakness said:
So I clicked the link and he forwarded to the autoroot.bat page so I used his method. It worked well (the 2nd time around) all the way until it started to push amon_ra_1.8-mod.... then after that it says rebooting into the bootloader, and it reboots into it and just says waiting for phone...
It does appear that my phone is rooted now, but my recovery is still not working. If I use ROM manager will it work since my phone is rooted or do I need to have a rooted ROM to run it off of?
Click to expand...
Click to collapse
Does your phone show s-off while in the bootloader? If so you should be able to run the FlashZip script and use that to flash the pc36img-sprintlovers zip. That one contains everything needed to bring your phone up to date and will leave you with a rooted rom and recovery.
Sent from my PC36100 using XDA Premium App

xHausx said:
Does your phone show s-off while in the bootloader? If so you should be able to run the FlashZip script and use that to flash the pc36img-sprintlovers zip. That one contains everything needed to bring your phone up to date and will leave you with a rooted rom and recovery.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
FINALLY! Thanks a million! My recovery is now working and it installed the built in sprinter lovers rom, I guess the anti-virus was stopping it so I disabled it and ran the flash script. I was able to install Fresh on there, just to try it out. I do have a few questions though:
1. I noticed after going through many pages that to update to a newer ROM version you don't always have to wipe clean, you can just install (or flash) the new update? I noticed in Fresh there is a built in app that does that. Is this true for most ROMS or only certain ones?
2. I assume I am using the RA recovery. I noticed the backup/restore feature on there. What exactly does that backup and when should I use it?
3. I've noticed I've been very low with memory on my phone (not SD card), I have about 258MB free. How can I clear space and when I mount my phone what files are important to keep and can I get rid of, is it okay to get rid of my rom.zip's and radio.zip's?
Thanks again to everyone, autoroot was def the most painless root ever.

noweakness said:
FINALLY! Thanks a million! My recovery is now working and it installed the built in sprinter lovers rom, I guess the anti-virus was stopping it so I disabled it and ran the flash script. I was able to install Fresh on there, just to try it out. I do have a few questions though:
1. I noticed after going through many pages that to update to a newer ROM version you don't always have to wipe clean, you can just install (or flash) the new update? I noticed in Fresh there is a built in app that does that. Is this true for most ROMS or only certain ones?
2. I assume I am using the RA recovery. I noticed the backup/restore feature on there. What exactly does that backup and when should I use it?
3. I've noticed I've been very low with memory on my phone (not SD card), I have about 258MB free. How can I clear space and when I mount my phone what files are important to keep and can I get rid of, is it okay to get rid of my rom.zip's and radio.zip's?
Thanks again to everyone, autoroot was def the most painless root ever.
Click to expand...
Click to collapse
1) You'll want to always wipe your cache/dalvik (I do everytime I'm in the recovery) but the Data depends on the ROM. Usually if you are going from one sense rom to another you are ok and the same for AOSP to AOSP. Going from Sense to AOSP you'll need to wipe data though.
2) Autoroot comes with a modified version of AmonRA, they are mostly just speed tweaks. To make a complete backup of your ROM select Boot (kernel), System (ROM), Data (Apps & Settings) and .android (apps on SD card)
3) You can delete the zips from your sd card if you don't need them but that's about normal for free memory.

[Q] Malladus 1.2.5 stuck at boot.

I've heard ranting and raving about Malladus and I decided to flash it yesterday. It won't take the flash no matter what I do.
I've tried: Flashing 1.2.4, downloading both again to make sure it wasn't a download issue, using different gapps package, using a different lg apps package, using CWM, using TWRP, side-loading... ETC
Bottom line: My phone will not take the ROM. It flashes the LG logo and gets stuck at a black screen where the back-light is on but nothing is displayed on the screen.
I am an experienced flasher and I have no idea what is going on. I am backed up and can get into TWRP to restore so I am all good as far as not being bricked goes but I really want to try out this damn rom.
Any help would be much appreciated. Thanks.

Bump I'm having the same problem, I'm on Verizon.

NBushyy said:
Bump I'm having the same problem, I'm on Verizon.
Click to expand...
Click to collapse
Yeah same here. Verizon. Forgot to mention it.

Still a problem. Bumping.

I am in the boat with you. I thought it was just me.

Same Black Screen issue
Did anyone have any luck resolving this? Ive tried with both twrp and cwm and same issue...?

Same problem on my Verizon model. Using twrp 2.6.3.3. Other roms work fine.

How long have you left it at the black screen? Sometimes a fresh load can take up to 10 minutes.
Also, the rom will work without gapps and lgapps, so try just loading the rom. I know you downloaded twice, but did you check the md5 sum either time?

heleos said:
How long have you left it at the black screen? Sometimes a fresh load can take up to 10 minutes.
Also, the rom will work without gapps and lgapps, so try just loading the rom. I know you downloaded twice, but did you check the md5 sum either time?
Click to expand...
Click to collapse
I left it there for a good 15 minutes. I also had it plugged into my laptop. It kept detecting the phone as plugged in. Seems like it is stuck in a bootloop or something. I also tried installing only the ROM without the gapps and lgapps and had the same result. I also checked the MD5 sum and it matched. (I know I'm kinda hijacking this original post, but I think we are all having the exact same issue)

try this
trackstar1414 said:
I left it there for a good 15 minutes. I also had it plugged into my laptop. It kept detecting the phone as plugged in. Seems like it is stuck in a bootloop or something. I also tried installing only the ROM without the gapps and lgapps and had the same result. I also checked the MD5 sum and it matched. (I know I'm kinda hijacking this original post, but I think we are all having the exact same issue)
Click to expand...
Click to collapse
Can you restore your nandroid and flash say, CleanROM 1.0 or DigitalDream 2.1? OR try this:
1. Hold the power button until the device is OFF.
2. Download LG drivers to the PC (LG VZW_United_WHQL_v2.11.1) and LG mobile support tool (B2CAppSetup).
3. Install these packages.
4. Plug in you USB cable into the phone but not the computer.
5. Hold volume up and insert the USB cable to the PC- the phone should boot to 'download mode'.
6. Open the support tool and click Options>Upgrade Recovery, follow the prompts.
7. At the first prompt indentify your phone using IMEI/ESN, then click OK
8. Let it do its thing, the phone will reboot and most likely have a bunch of error messages and some FC's. Just hit okay to all messages, the phone will settle after 2 minutes or so.
9. Download freegee from market and reflash recovery of your choice.
10. Make sure you have a ROM saved to the SD to flash
11. Use freegee to reboot to recovery
12. Once in recovery you can reflash the ROM as normal.
13. Reboot and Profit!
*$* Or you could go back to Stock and start fresh!
*$* BEFORE ANY FLASH ALWAYS STOP and MAKE A NANDROID BACKUP!
Good Luck and if you get stuck let me know

geosnipe said:
Can you restore your nandroid and flash say, CleanROM 1.0 or DigitalDream 2.1? OR try this:
1. Hold the power button until the device is OFF.
2. Download LG drivers to the PC (LG VZW_United_WHQL_v2.11.1) and LG mobile support tool (B2CAppSetup).
3. Install these packages.
4. Plug in you USB cable into the phone but not the computer.
5. Hold volume up and insert the USB cable to the PC- the phone should boot to 'download mode'.
6. Open the support tool and click Options>Upgrade Recovery, follow the prompts.
7. At the first prompt indentify your phone using IMEI/ESN, then click OK
8. Let it do its thing, the phone will reboot and most likely have a bunch of error messages and some FC's. Just hit okay to all messages, the phone will settle after 2 minutes or so.
9. Download freegee from market and reflash recovery of your choice.
10. Make sure you have a ROM saved to the SD to flash
11. Use freegee to reboot to recovery
12. Once in recovery you can reflash the ROM as normal.
13. Reboot and Profit!
*$* Or you could go back to Stock and start fresh!
*$* BEFORE ANY FLASH ALWAYS STOP and MAKE A NANDROID BACKUP!
Good Luck and if you get stuck let me know
Click to expand...
Click to collapse
I am able to restore my nandroid backup so I'm not completely stuck without a phone. I will try flashing one of the other ROMs and see how it goes now. Thanks for the help so far.

trackstar1414 said:
I am able to restore my nandroid backup so I'm not completely stuck without a phone. I will try flashing one of the other ROMs and see how it goes now. Thanks for the help so far.
Click to expand...
Click to collapse
I was able to install the digital dream rom without any issue. At this point I think its the sequence I did everything. I did the latest ota before installing any Recovery. I used the loki method to install the recovery. In looking at all the roms, it appears that malladus may not be "loki patched" for people already on 12b? Other roms I have tried mention that so thats why I'm speculating this. I am by no means a developer so I might be out in left field on this one. I guess I'll stick with stock or another ROM for now until his next update.
It also looks like people are discussing this on the main ROM forum as well so hopefully it will work in the future.
Thanks again for the help and suggestions.

trackstar1414, say thanks by using the "Thanks' button like this.. keep me informed, CHEERS!

trackstar1414 said:
I was able to install the digital dream rom without any issue. At this point I think its the sequence I did everything. I did the latest ota before installing any Recovery. I used the loki method to install the recovery. In looking at all the roms, it appears that malladus may not be "loki patched" for people already on 12b? Other roms I have tried mention that so thats why I'm speculating this. I am by no means a developer so I might be out in left field on this one. I guess I'll stick with stock or another ROM for now until his next update.
It also looks like people are discussing this on the main ROM forum as well so hopefully it will work in the future.
Thanks again for the help and suggestions.
Click to expand...
Click to collapse
Wanted to share this if you haven't read it..
http://forum.xda-developers.com/showthread.php?t=2449670

I had issues originally and had to flash back to 1.2.3.
What I ended up doing was switching to CWM 6.0.4.4 ( I was using TWRP 2.6.3.3).
His boot skipped the set up wizard as well, which was odd.
His was also the only ROM I ever got stuck on the fastboot screen while using twrp.
Try ( at your own risk obviously) flashing back to an older malladus (wipe all and boot till you get through the set up wizard),
Then back to recovery, do a wipe, without wiping the system partition, Data Cache and Davlik, and flash back to 1.2.5.
I didn't try it on 1.2.5. But that's how I got into 1.2.4.

Srvisg0d said:
I've heard ranting and raving about Malladus and I decided to flash it yesterday. It won't take the flash no matter what I do.
I've tried: Flashing 1.2.4, downloading both again to make sure it wasn't a download issue, using different gapps package, using a different lg apps package, using CWM, using TWRP, side-loading... ETC
Bottom line: My phone will not take the ROM. It flashes the LG logo and gets stuck at a black screen where the back-light is on but nothing is displayed on the screen.
I am an experienced flasher and I have no idea what is going on. I am backed up and can get into TWRP to restore so I am all good as far as not being bricked goes but I really want to try out this damn rom.
Any help would be much appreciated. Thanks.
Click to expand...
Click to collapse
Are you on 12B OTA? If so, that would be your issue. I took the 12B OTA and tried flashing Malladus and got the same issue you have. You can revert your phone to 11A and that should resolve your issue. http://forum.xda-developers.com/showthread.php?t=2448960 it will erase everything on your phone and go back to unroot.

[Q] Recovery Rebooting Issue

Hello,
I sure could use some help here! I just upgraded to BajaROM 16 in my stock rom slot. All was fine until I did a boneheaded thing. I wanted to go into recovery to attempt to install another ROM in slot 1 so by mistake I clicked on "recovery" in the drop screen that also has the restart and shut down buttons. Now I appear to be in a endless loop trying to find recovery. I have no idea what to do now. I tried doing the three button approach but nothing happened. I have pulled the battery and waited a few minutes but as soon as I re-start the phone, I get that damn "Recovery Reboot" message again on the top left side of the screen.
Any ideas?
Thanks!

I'm in the same boat, phone has been constantly rebooting for the last 12 hours and I can't figure out how to make it work again...

same boat here.
edit...
Resolved...

I have encountered this as well. I fixed it by Odin flashing the modem back to the phone. Once flashed, it rebooted and I had Safestrap and my rom back. Just be sure you flash the right modem file as the wrong one will brick your phone. I have done that in the past as well.

Bizack said:
same boat here.
edit...
Resolved...
Click to expand...
Click to collapse
What was the resolution? I'm in the same boat and can't get ODIN to recognize the phone.

tdamore said:
What was the resolution? I'm in the same boat and can't get ODIN to recognize the phone.
Click to expand...
Click to collapse
Whoa, Odin wont recognize the phone in download mode?
vol dn + home & Power?
You need to not use USB3, switch USB ports, change cables, if your computer wont recognize switch computers.
Open up Kies3 and re-install drivers.
Many options, try them all, don't give up. It your shot won't even turn on, then take that **** back!!!
What IO did to achieve salvation...
I flashed NC4, Rooted using towl root, then busy box and Safe Strapped flashed the NC2 kernel and bamm(no relation) back on Baja16....
(there is a process, please don't follow the steps above, go here...)

I was in the same boat...
tdamore said:
What was the resolution? I'm in the same boat and can't get ODIN to recognize the phone.
Click to expand...
Click to collapse
I was also rebooting into recovery mode over and over again after my first boot up of the recent Baja and rebooting into Recovery after updating to the new version of SS.
The only thing I could do was pull the battery and it would do again. I read the above about updating the modem, but unsure what that was, I tried rebooting into download mode again. From here, instead of hitting UP VOLUME to continue, I hit DOWN VOLUME and low and behold, I got the baja flash and it booted up my phone again.
PHEW!
Just thought I'd share what worked for me...

what am i doing wrong i did the root methods and setup the safestrap(3.75) and have been trying all evening to install bigginsRom+v6. i go thru all the steps and when i hit continue for it to reboot it just dies and does nothing. i have to pull the battery and get it back to safestrap and reinstall the stock rom. i am supposed to set it up on slot 1 instead of stock right?

downloaded another rom and tried it in another slot and the same thing. the only one i can get to load is the stock backup. anything else it just goes black and does nothing. have to pull the battery to even get it to power back on

BigHoss3 said:
what am i doing wrong i did the root methods and setup the safestrap(3.75) and have been trying all evening to install bigginsRom+v6. i go thru all the steps and when i hit continue for it to reboot it just dies and does nothing. i have to pull the battery and get it back to safestrap and reinstall the stock rom. i am supposed to set it up on slot 1 instead of stock right?
Click to expand...
Click to collapse
BigHoss3 said:
downloaded another rom and tried it in another slot and the same thing. the only one i can get to load is the stock backup. anything else it just goes black and does nothing. have to pull the battery to even get it to power back on
Click to expand...
Click to collapse
Guys, Please Go here.
Follow these directions to the letter.
First ting is figure out where you are at and use the correct method to get your s**T back up and running...

Bizack said:
Guys, Please Go here.
Follow these directions to the letter.
First ting is figure out where you are at and use the correct method to get your s**T back up and running...
Click to expand...
Click to collapse
It took some work but I got it booted back to the stock rom

I also had problems getting Odin to see my phone. In my case I just needed to unistall the USB drivers bundled with my phone and install the latest drivers FROM Samsung's website.