I had been running CM10.0 for a while when it decided to lose my internal SD card. I think it has somethin gto do with TWRP and unmounting/remounting sdcards. In any case... I decided to flash CM10.1 just because it would be something to do and maybe it would solve the problem.
It got stuck at the splash screen.
I flashed back to CM10.0 and cleared cache/dalvik and got the same result. At this point I was S-On.
I re-locked and RUU'd. Everything seemed to work fine (including the sdcard issue). Sweet .
I unlocked it (HTC-Dev), flashed TWRP 2.4.4.0, flashed CM10.1 and it gets stuck on the splash screen.
Long story short, I RUU'd and updated everything OTA (1210 radio, etc).
I then used dirty Racun (with Baby Racun) and wen't S-Off.
This put me at 2.09 (was there already) and radio 1119, with S-Off.
I then flashed TWRP 2.4.4.0 again...
So ....
I'm S-Off, Unlocked, Radio 1119, HBoot 2.09, 3.15.651.16...
If I flash CM10.1, then Gapps from 20130312 I still get stuck at the cm boot screen. Same thing happens with the latest nightly, the M2 and the 10.0 that I was running before.
Any ideas? I've serached the forum (the best I could... I can't get any results unless I try to make a thread and just take a look at the "related results" it comes up with)...
I just tried flashing the boot.img from the CM10.1 nightly through fastboot directly and nothing doing. Same issue.
So I was in the middle of running the RUU found at unlimited.io here --> (Won't let me post a URL yet... The 2.09 RUU anyway...) which I've done a few times during this project to get back to a stock ROM. I just do a few of the middle steps starting with locking the device and it happened to reboot into the OS instead of fastboot this time when I locked it...
And it booted into CM10.1...
WTH?
Well whatever... Anyway...
I'm going to make a backup and then try to unlock (HTC Dev token) the recovery and then if that works I'll be good to go...
Weird...
I know this is a little late, but did you try flashing another ROM besides CM? It shouldn't matter, really...just a thought.
How long were you stuck at the boot animation? Did you try using an older twrp?
Sent from my EVO using xda premium
Thank you for the reply...
Once I got into CM10.1 I realized I couldn't send texts... so I messed around with APN's etc, and finally came across an "error 16..." thread that indicated that my phone had been newly locked out of the sprint network due to the S-Off state. So I called Sprint and had that solved in a few moments...
But I had already RUU'd and updated everything to stock, S-Off, re-locked...
So I thought "Sweet... now that I know what that solution is I'll go for CM10.1 again..."
Now I'm stuck at the boot screen again . I tried what seemed to have worked before (fastboot oem relock) and that doesn't seem to have done the trick this time.
Still kicking at it though .
To answer you questions... I tried TWRP 2.4.4.0 and TWRP 2.3.1.0, and as far as how long it sat in the boot animation... I left until the battery died once...
Related
So after unlocking the boot loader today and loading up the stock rooted OTA rom my phone started randomly boot looping. It was sitting on my desk then randomly rebooted and now its been doing the same thing despite my best tries to fix it.
I had Amon Ra recovery installed initially, then flashed CWM via Rom manager. At this point I can't boot into recovery (or factory reset). It all happens very quickly, but it looks like the recovery menu loads up then the phone reboots. I am able to get into fastboot and reflash any of the recovery img's. I've tried the Amon Ra newest, the CWM normal and touch recovery and none of them will let me in. I've tried to get into recover with the 4G sim out and with the SD card out.
The phone does boot into an OS but after about 10 seconds it reboots. I did some digging and thought it might be the older bootloop issue with the network type. It does it with the sim out and in airplane mode so I'm not all that confident that its that issue.
At this point I am looking at tried to re-stock via Hboot RUU's. I have the P98IMG-1.02.605.6.zip on an SD card and that does flash but at the end of the verification it tells me "the main version is older." So I'm either looking for another package that will let me re-stock and give it a try again... or open to any other suggestions?
Hoping the phone isn't totally hosed, though based on what I can still get into I think there may be hope yet.
Anyone?
thanks in advance!
Have you tried CleanFlash? Also you are getting the mainver because you updated with the OTA. Google ruu_vigor. You are looking for the one that starts with 2.01.
Sent from my VTAB1008 using xda premium
This may help...
Get the 2.____.11 RUU from the 'Vigor Shipped' post in development. Follow the directions in the word file in post 2 from here:
http://forum.xda-developers.com/showthread.php?t=1487981
And then flash that RUU in HBOOT.
I had 99 problems with the RUU exe and spent the last week trying to get it to take. That tip to extract the PH file finally got me there. It fixed all kinds of issues for me and got me to stock.
Don't forget to relock.
(I think if you ran the ICS leak RUU you may still have issues, but you could follow those steps with that RUU as well probably and it would hopefully get you cleaned up)
Thanks for the help so far.
I got the newer RUU and got it flashed via hboot after i relocked. *edit* after the second time flashing it it seems to be working.
You guys rock.
I've found myself in a bootloop, and would like some informed help before I potentially dig my hole deeper. I'm pretty n00b, knowing just enough to get by.
Phone History:
I was originally OTA 1.50, and when the ability to flash back to 1.40 came out, I made that modification, giving me S-OFF, clockwork, etc. I was still locked and never unlocked. I think I ran MEAN ROM for some time then. About 6 months ago, I flashed MIUI ROM which ran fine.
I recently flashed to the latest MIUI (3.1.19, 3.2.1, 3.2.8) but they all seemed to have issues with powering off sometimes, weird Wifi issues. I knew something was not right. Figuring maybe the ROM just was not right for my build, I tried CyanogenMOD 10, and had similar issues. It seemed to flash fine (via clockwork) and would boot, but had weird issues (wifi, messaging, some display weirdness)
I did some reading and convinced myself maybe I needed new firmware on the phone to be able to run these ROMs successfully.
I followed the instructions here: http://forum.xda-developers.com/showthread.php?t=1808150
to get new firmware (and Superwipe) and then reflashed to CyanogenMOD 10. This had me in a bootloop. I also tried reinstalling MIUI 3.2.8 and get a bootloop with it as well.
Currently I am:
*** LOCKED ***
SHOOTER XC SHIP S-OFF RL
HBOOT-158.0000
RADIO-1.09.00.0706
OpenADSP-v02.6.0.2226.00.0217
eMMC-boot
May 17 2012,15:06:44
What is the best way to get out of this bootloop? I am hoping it's a relatively easy fix, being S-OFF, but will do what is needed.
Thanks!
Also...
I should add, that when I attempt to do a "wipe data/factory reset" in clockwork, it gets the following error:
E:format_volume: make_extf4fs failed on /dev/block/mmcblk1p2"
Everything else wipes fine.
Also, I am in fastboot, :-/
You're saying your a noob. so the safe way to go is download the RUU Here. Go through the update process and then you can flash a custom recovery. ditch clockwork and go with 4EXT Recovery.
Astrikz said:
You're saying your a noob. so the safe way to go is download the RUU Here. Go through the update process and then you can flash a custom recovery. ditch clockwork and go with 4EXT Recovery.
Click to expand...
Click to collapse
Thanks for the intel Astrikz. I'm looking into that now. Your post makes me wonder... is there a not so noob route? Does being S-Off help me in this?
Thanks again, researching your links.
lecosmique said:
Thanks for the intel Astrikz. I'm looking into that now. Your post makes me wonder... is there a not so noob route? Does being S-Off help me in this?
Thanks again, researching your links.
Click to expand...
Click to collapse
Sure does help. Plus it will save you some time.
Heres a quick guide by ramjet73 that will help you . [Guide] Quick And Dirty RUU Flashing for CDMA S-OFF Users
Spot on Astrikz. Ramjet73's post was quite helpful.
After running through all the steps, I was able to get booted into a stock 2.89 ROM, update 4ext, busybox, etc.
I then tried to flash back onto CM10, first creating a backup in 4ext of my functioning stock ROM. I was on HBOOT JBear 1.58.58.58 at the time, but realized that CM10 did not function with that HBOOT. Attempting to boot into it caused the previously seen loop... boots, spins the CM10 logo for a few seconds, and then reboot. I downgraded the flash to JBear 1.50.50.50 to see if that would fix the issue.After the HBOOT downgrade, I wiped everything (but SD) and reinstalled CM10. Booting still yielded the same bootloop issue I had previously. I also tried booting into MIUI 3.2.8, and got the same issue. They start to boot, Show a bit of their splash screen, and then lock and reload. I was able to boot meanROM2.17.651.5, although it seems a bunch of things in it were broken.
So... I'm still battling, but making some progress. Any ideas on what might be the cause of the bootloops? II even tried booting with no SD card in, just in case something on my card was causing the issue. But, I got the same bootloop when booting with no SD card.
Tried out Venom 1.6.3 and was able to get that one to work. Still not sure why I had the bootloop issues.
bootloops
My problem is similar.
I've got
S-On Hboot 1.53
Previously got
4ext recovery
CoolICS Rom
.. and when I going to recovery my bootloops started
Normal boot or trying to recovery boot giving the same results.
I can: go to fastboot, changing cid, lock/unlock bootloader, flash boot/recovery/system from fastboot.
Even flashung RUU it's complete but when phone restarts, still got bootloops
My EVO is GSM and it need help.
I can buy a beer if someone can help
---------- Post added at 05:41 PM ---------- Previous post was at 04:55 PM ----------
Got some progress:
After flashing Ruu, i've flashed a boot.img form CM-9-20130210-NIGHTLY-shooteru.
Got HTC screen(first screen), and starting second screen(HTC quietly brilliant).
But got bootloops at half of drawing this animation.
Is the unbricking method got sense? Maybe I'll try this way
I'm not going to bother everyone with a full account of the things that have gone wrong in the last week with this phone. That being said, I need some help.
I flashed CM9-vigor unofficial through Amon-ra 3.15. I am S-ON, but I loaded recovery through fastboot,
Code:
fastboot boot recovery-ra-vigor-3.15-gnm.img
The ROM Loaded with no issue, so I rebooted. I am now at the CM9 loading screen. I can reboot into recovery or bootloader with no problem.
Knowing that with S-ON I would have had to reflash the PH98IMG.zip file after loading the ROM had I not loaded recovery through fastboot, I decided to try that and see what might happen. Long story short, nothing happened.
Is there a simple thing I am missing to fix this? Or am I going to have to start over? Do I need to flash RUU? If so, how? I've never done that bit before.
Thanks in advance for any help, it is greatly appreciated. :good:
Extract the boot.img from the ROM package and flash it in fastboot with "fastboot flash boot boot.img"
thanks shrike1978
I should have mentioned that I already did that. I did it again and the same happens.
Could it be the firmware?
Sent from my Amazon Kindle Fire using Tapatalk HD
So I gave up and used your CounterStrike ROM, shrike1978. Followed instructions for S-ON in your OP. I flashed the ROM with no issues and then rebooted into bootloader and flashed bootloader.
I am back once more to the cyanogenmod loading screen with nothing else happening.
Any help will be good.
Thanks again.
What is your hboot/radio version?
HBOOT is 2.11.0000
That doesn't sound right...
I finally fixed this last night, so for completion's sake I will tell how I think I did it.
I realized that the h-boot of 2.11.0000 sounded odd, aso I tried flashing radios and got the mainver error. So I went ahead and installed the Critical Strike ROM once again for S-ON. But after the ROM finished, and before I rebooted to the bootloader, I mounted the SDCARD and changed the mainver number to a slightly larger value than my 2.11.0000. Then I updated the zip, and rebooted to the bootloader. I flashed the PH98IMG.zip with the altered mainver and then reboot.
First boot took a looong time, but after that everything worked fine.
Thanks for the help, sometimes just bouncing stuff off of people can make you see things you keep overlooking.
So I have my phone rooted. s-off with the "wire trick".
ClockworkMod installed.
Trying to use CM10 (Gangnam style). No matter what I do, I get CONSTANT reboots.
I tried doing the all the wipes (data, cache, etc....)
I got it to boot up once, for about 5 minutes. In the middle of trying to figure out why I couldn't get any service (changing the APN from what I could figure out) the phone rebooted and got stuck in its boot loop again.
No matter what I do, boot loop. Basically gets to the CM10 loading screen, loads for about 2 seconds, reboots.
Restore to my backed up file, phone works perfect.
Any suggestions?
I realize I'm a n00b here, but I've successfully rooted and ran CM10 on my Acer Iconia A500 (CM9 then up to CM10) and my brothers HP tablet (CM9) without major issues I couldn't handle. For some reason it doesn't seem anyone else has had the reboot issue with at least this specific CM10.
Any help would be greatly appreciated. I hate the virgin mobile boot up screen and moreover I LOVE 4.1.2.
I also tried 4.2.2 WILD FOR THE NIGHT but I just get error Status 7. I even made sure to update my 4Ext recovery (was using clockwork recovery before), update to latest firmware. Updated to latest firmware, wiped everything but my SD card, still got Error Status 7 on 4.2.2 and constant reboot on 4.1.2. This is driving me nuts, I've searched the forum and did not find a solution so far (which is why I finally decided to sign up and become a member!!!)
By the way, im on JuopunutBear HBOOT 1.57.5757 with S-OFF.
The reason for the boot loops is your hboot version needs to be downgraded. Once thats done you'll be fine.
sent from my 1920 overclocked note 2 running jedi xp11
markbencze said:
The reason for the boot loops is your hboot version needs to be downgraded. Once thats done you'll be fine.
sent from my 1920 overclocked note 2 running jedi xp11
Click to expand...
Click to collapse
Downgraded to 1.4. Now I get a constant bootloop with no splash screen. Can't even do anything now because bootloader asks me every time if I want to update to the file on my SDcard
Used my old phone to take the file off the SDcard. Tried the WILD FOR THE NIGHT 4.2.2 again. Still not booting even to splash screen for CM10.
What version should I be using? So afraid I bricked my phone....
whoops!
Now I feel like a dumbass.
Downgraded to hBoot 1.4
Wiped everything.
Format everything (except SDcard).
Loaded 4.2.2.
Booted up! Thanks! Been fighting this for days!!!
http://forum.xda-developers.com/showthread.php?p=32032629
This is the version of hboot that works well for me. But if you got it working you're good. No need to change. Basically after you downgrade your hboot I booted into recovery and moved the hboot zip into a different folder on my sd card. If its in the root of 5he card bootloader will keep asking... then you can flash away and delete the file as you no longer need it. Glad I was able to help. I just actually figured this out last nigth when I was playing with my old evo. I tried to flash and it boot looped so I had to do some thinking and then it occurred to me that the hboot was likely to blame.
Enjoy
sent from my 1920 overclocked note 2 running jedi xp11
markbencze said:
This is the version of hboot that works well for me.
Click to expand...
Click to collapse
That's a GSM hboot and the OP is on Virgin Mobile USA which is CDMA so he wouldn't want to flash that version or he could damage his phone.
ramjet73
Hello all, I need some help if there are any ideas what could be going on with this phone. I can usually fix my own phone problems, but this one has stumped me...
I bought a rezound dirt cheap that was stuck on the white HTC screen and would not boot into the stock rom. At the time I bought it, it was s-on and I could get in the HBOOT and run fastboot commands.
Since buying it, I have tried many things to get this thing working. I've tried to RUU (with PH98IMG and .exe) and apparently after it completes it is once again in a boot loop on the white HTC screen. I have been able to unlock and flash a custom recovery onto it (amon-ra) and install any cm/aokp rom onto it and boot into that. The only issue with that is when in the rom, my wifi and bluetooth will not connect at all. It wont even toggle on in settings and it is not greyed out. 4G and everything else seems to work ok.
At this time, I'm thinking there is some kind of hardware failure but I'm open to suggestions.
In summary...
I have been able to s-off
I have tried different firmware combos of HBOOTs/radios
I have flashed custom recoveries and roms and can boot into them without wifi or bluetooth
I have been unsuccessful to RUU to anything stock, it'll just boot loop the white HTC screen
Right now, I have installed Tron 2.1 onto it. I did notice post:http://forum.xda-developers.com/showthread.php?t=2272781&highlight=no+wifi
When I go into system/lib, there was no /modules folder. I went ahead and created it and put in bcmdhd.ko and rebooted, but still no go. I'm not sure why the /modules folder was missing, but this reaches the extent of my knowledge on what is supposed to be there.
I believe I have tried everything and done fairly thorough searches to get this phone working properly and am at a loss what to do next. If anybody has a thought of something to try, I'm all for it. Fortunately if this phone doesnt work out, its not a big deal to me.
I don't want this to sound like another "stuck on HTC screen" thread. I have been through all those and this doesn't seem like the same problem.
Your help is greatly appreciated!
tacoman said:
Hello all, I need some help if there are any ideas what could be going on with this phone. I can usually fix my own phone problems, but this one has stumped me...
I bought a rezound dirt cheap that was stuck on the white HTC screen and would not boot into the stock rom. At the time I bought it, it was s-on and I could get in the HBOOT and run fastboot commands.
Since buying it, I have tried many things to get this thing working. I've tried to RUU (with PH98IMG and .exe) and apparently after it completes it is once again in a boot loop on the white HTC screen. I have been able to unlock and flash a custom recovery onto it (amon-ra) and install any cm/aokp rom onto it and boot into that. The only issue with that is when in the rom, my wifi and bluetooth will not connect at all. It wont even toggle on in settings and it is not greyed out. 4G and everything else seems to work ok.
At this time, I'm thinking there is some kind of hardware failure but I'm open to suggestions.
In summary...
I have been able to s-off
I have tried different firmware combos of HBOOTs/radios
I have flashed custom recoveries and roms and can boot into them without wifi or bluetooth
I have been unsuccessful to RUU to anything stock, it'll just boot loop the white HTC screen
Right now, I have installed Tron 2.1 onto it. I did notice post:http://forum.xda-developers.com/showthread.php?t=2272781&highlight=no+wifi
When I go into system/lib, there was no /modules folder. I went ahead and created it and put in bcmdhd.ko and rebooted, but still no go. I'm not sure why the /modules folder was missing, but this reaches the extent of my knowledge on what is supposed to be there.
I believe I have tried everything and done fairly thorough searches to get this phone working properly and am at a loss what to do next. If anybody has a thought of something to try, I'm all for it. Fortunately if this phone doesnt work out, its not a big deal to me.
I don't want this to sound like another "stuck on HTC screen" thread. I have been through all those and this doesn't seem like the same problem.
Your help is greatly appreciated!
Click to expand...
Click to collapse
i would like you to do the following.
flash this http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
2 times. it will make sure we have a solid base to work on.
after that has ran 2 times. boot into the stock rom one time.
after that flash this https://dl.dropboxusercontent.com/u/12405441/new.global.firm.PH98IMG.zip
once this is done let it boot into the rom.
from here you should be good to flash any rom that is out there to date. (note please dont restore any system data, only app data)
ALSO MAKE SURE YOU HAVE 100% battery. doing an ruu can brick the phone if its interrupted.
report back when done
Thanks for replying. I have flashed that RUU several times in a row in the past, but I'm redownloading it now to make sure my copy isnt corrupt. Earlier experience when I double flashed this it still remained a white HTC screen loop.
Currently estimated at 6hrs to download, so I wont be able to reply for a bit with my findings...
tacoman said:
Thanks for replying. I have flashed that RUU several times in a row in the past, but I'm redownloading it now to make sure my copy isnt corrupt. Earlier experience when I double flashed this it still remained a white HTC screen loop.
Currently estimated at 6hrs to download, so I wont be able to reply for a bit with my findings...
Click to expand...
Click to collapse
When the Rezound first came out a bunch of people had boot loop problems because the phone was set to wcdma or some such thing instead of cdma. I'm just a noob hack but that's my memory of it. The cure was to boot without the back cover on which contains the antenna and then change the setting.
Ok, I have re downloaded the AndroidPolice RUU and flashed twice, but was not able to boot into it no matter how long I waited (20 min+). It would just loop the HTC white screen. I then went ahead and flashed your global update firmware and have the same result after waiting (20 min+), it just loops the HTC white screen.
I have tried this process several times last night, but still no progress.
As the phone sits now:
*** UNLOCKED ***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.28.0000
RADIO-2.23.10.0123r/2.23.10.0124r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Sep 20 2012, 17:40:22
tacoman said:
Ok, I have re downloaded the AndroidPolice RUU and flashed twice, but was not able to boot into it no matter how long I waited (20 min+). It would just loop the HTC white screen. I then went ahead and flashed your global update firmware and have the same result after waiting (20 min+), it just loops the HTC white screen.
I have tried this process several times last night, but still no progress.
As the phone sits now:
*** UNLOCKED ***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.28.0000
RADIO-2.23.10.0123r/2.23.10.0124r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Sep 20 2012, 17:40:22
Click to expand...
Click to collapse
You need stock recovery and a locked bootloader
- "Is it dark in there?"
drynyks said:
You need stock recovery and a locked bootloader
- "Is it dark in there?"
Click to expand...
Click to collapse
S/he ran the RUU so they are stock.
Sounds like the symptoms of a kernel issue. Try pulling the boot.img from this stock OTA ROM and flashing it.
http://forum.xda-developers.com/showthread.php?t=2260154
fastboot flash boot boot.img
I have the exact same you. Been this way for months. Maybe once a month BT/Wifi will turn on but only for a few hours maybe. Phone will reboot itself and come back up with the 2 broken again.
feralicious said:
S/he ran the RUU so they are stock.
Sounds like the symptoms of a kernel issue. Try pulling the boot.img from this stock OTA ROM and flashing it.
http://forum.xda-developers.com/showthread.php?t=2260154
fastboot flash boot boot.img
Click to expand...
Click to collapse
Well I finally booted into stock sense after flashing that boot.img which is a big step from before. For a brief moment, it saw wifi networks in my office but when I went to connect to one, wifi died and it no longer sees any wifi network. Bluetooth appears to still be an issue as well, i.e. will not turn on.
Flyhalf205 said:
I have the exact same you. Been this way for months. Maybe once a month BT/Wifi will turn on but only for a few hours maybe. Phone will reboot itself and come back up with the 2 broken again.
Click to expand...
Click to collapse
Unfortunatly that doesnt sound very good for me if you've been battling this wifi/BT problem for months.
synisterwolf said:
i would like you to do the following.
flash this http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
2 times. it will make sure we have a solid base to work on.
after that has ran 2 times. boot into the stock rom one time.
after that flash this https://dl.dropboxusercontent.com/u/12405441/new.global.firm.PH98IMG.zip
once this is done let it boot into the rom.
from here you should be good to flash any rom that is out there to date. (note please dont restore any system data, only app data)
ALSO MAKE SURE YOU HAVE 100% battery. doing an ruu can brick the phone if its interrupted.
report back when done
Click to expand...
Click to collapse
can you explain what you mean by flash the ruu twice once I have saved it to the root of my sd card? Does that just mean get to the bootloader, watch as it reads the the ph98img file and let it do that twice, or do I need to reboot in between, or do I need to put in a command?
fivedezs said:
can you explain what you mean by flash the ruu twice once I have saved it to the root of my sd card? Does that just mean get to the bootloader, watch as it reads the the ph98img file and let it do that twice, or do I need to reboot in between, or do I need to put in a command?
Click to expand...
Click to collapse
when you let hboot flash the zip, the first time is super short. it updates hboot, stock recovery, and splash i think. then it will reboot back to bootloader and ask to be flashed again. this time it will take some time to update because it does the whole system.
---------- Post added at 08:25 AM ---------- Previous post was at 08:24 AM ----------
tacoman said:
Well I finally booted into stock sense after flashing that boot.img which is a big step from before. For a brief moment, it saw wifi networks in my office but when I went to connect to one, wifi died and it no longer sees any wifi network. Bluetooth appears to still be an issue as well, i.e. will not turn on.
Click to expand...
Click to collapse
something doesnt seem right. the RUU would have flashed the boot.img for you. can you link me to the downloaded ruu that you have? also before you run the ruu did you do fastboot oem lock the bootloader?
Edit:
i remember an old trick from the inc days. after the RUU boot back into hboot and do a "factory reset" then boot into the phone. it use to fix the radio errors somewhere getting after a RUU. no clue why we did it. it just worked. try that when you are on stock recovery locked bootloader
Here is the RUU I have re downloaded. It was also the original I used in the past on my other Rezound
https://www.dropbox.com/s/1570h8l0ba1u7qp/rezound_AndroidPolice_4.03.605.2_PH98IMG.zip
I have also tried the RUU 3.14.605.12.exe and a couple other different RUU versions, but have the same issue with that as well. Even on MicroMod777's OTA-Global-Stock-4.05.605.14 710RD-Rooted 5/1/13 flashed through amon-ra, I get the bootloop. I have done these as locked and unlocked bootloader with no difference. I have also tried the factory reset with locked bootloader.... no go with that either.
I was only able to finally boot in to stock by fastboot flashing the boot.img, and that is where this phone sits now. My major issue at this point is I dont have wifi or bluetooth and have dug through numerous posts and tried different things, and nothing is working on it. What was strange as I said in my previous post, the very first time I was able to boot into stock sense by flashing the boot.img, it briefly saw wifi networks but disappeared and disabled as soon as I tried to connect to one. I have not been able to replicate that since then.
On a sidenote and possibly related, since this phone has been sitting at my desk I decided to try and flash Newt's NOS JB v1.0.0 ROM and it bootloops also at the droid eye screen. I never was able to get it going on this phone. My other rezound boots this just fine.
I think I have reached the limits of my android knowledge of what to try on this thing. I am satisfied with it not having wifi/bluetooth since my wife wont be using those features. I would like to understand what the heck is going on though.