Database Develop

Flashed ClockworkMod Recovery + MarketFix, Radio now Broken

Here's the sequence of events, wonder if anyone can point me in the right direction for repair.
I am on Froyo, the initial leak rooted by Paul.
I wanted to get my market working, so I found this billg market fix + busybox update zip.
I installed RomManager, and it suggested I flash ClockworkMod Recovery, so I did. It guessed my phone correctly (I think) as the "Nexus One (GSM)". I'm now no longer totally sure - but that IS the T-Mobile version right?
Anyway, I flashed clockworkmod recovery, and then I chose the market fix, and then I rebooted.
Everything seemed OK but the first warning sign was no graphical boot screen (no sparking multi-colour X). It booted up OK but no connection to the network at all. I can not even enable wi-fi.
Not I'm not too sure what to do, would hate to make matters worse. I can boot into recovery and it is ClockworkMod recovery, but of course there are no backups on that thing I can restore to. I was using AmonRA recovery before.
Any thoughts?
TIA Paul

paulvallee said:
Here's the sequence of events, wonder if anyone can point me in the right direction for repair.
I am on Froyo, the initial leak rooted by Paul.
I wanted to get my market working, so I found this billg market fix + busybox update zip.
I installed RomManager, and it suggested I flash ClockworkMod Recovery, so I did. It guessed my phone correctly (I think) as the "Nexus One (GSM)". I'm now no longer totally sure - but that IS the T-Mobile version right?
Anyway, I flashed clockworkmod recovery, and then I chose the market fix, and then I rebooted.
Everything seemed OK but the first warning sign was no graphical boot screen (no sparking multi-colour X). It booted up OK but no connection to the network at all. I can not even enable wi-fi.
Not I'm not too sure what to do, would hate to make matters worse. I can boot into recovery and it is ClockworkMod recovery, but of course there are no backups on that thing I can restore to. I was using AmonRA recovery before.
Any thoughts?
TIA Paul
Click to expand...
Click to collapse
find a froyo radio update from somewhere. there on alot of the rom pages
and flash a new rom after the radio and see what happens

The latest clockworkmod is buggy for me too. You can flash back to amon's recovery in fastboot.

Quick update
Flashing the Froyo radio update was no help.
I re-flashed Amon RA recovery and now I'm reapplying the original Paul's frf50.
Fingers crossed.

Phew, OK I'm back on the air.
Now I have to try to figure out how to apply the market fix without using ClockworkMod!!!
Thanks for help/advice.
Paul

paulvallee said:
Phew, OK I'm back on the air.
Now I have to try to figure out how to apply the market fix without using ClockworkMod!!!
Thanks for help/advice.
Paul
Click to expand...
Click to collapse
Is it a zip you flash in recovery?

[Q] Problem flashing from Fresh 2.4 to Cyanogen 7.0.x

I've tried to look everywhere for info on this issue and the closest I got was in the developers thread where someone was going to flash from Fresh 2.4 to CM 6. Apologies if I'm completely dense here.
There seem to be tons of ins-and-outs that I'm not yet hip to like hboot versions and clockwork vs fastboot and etc.
I am running Fresh 2.4 and I'm getting the "Low on space" trouble that others have noted. I downloaded cyanogen 7.0.3 to my SD and installed ROM Manager. I am able to boot to ClockworkMod and can select the zip to install from. After CM installs I reboot and can't get past the boot screen. (As a side note, I notice the videos all have a white background with black HTC while my boot is gray HTC on black background.)
Is there something I'm missing? The only thought I had was to revert back to completely stock ROM and try to start all over again. Thanks!

1. Are you using any other mods/tweaks - Firerat's, Data2ext or such?
2. Did you wipe everything before flashing CM? Or what steps did you take before flashing CM?

andythegreenguy said:
1. Are you using any other mods/tweaks - Firerat's, Data2ext or such?
2. Did you wipe everything before flashing CM? Or what steps did you take before flashing CM?
Click to expand...
Click to collapse
1) no other tweaks. Just put Fresh 2.4 on and started using it.
2) In the ROM Manager I backed up after flashing to ClockworkMod. I've used that backup to get my phone working again. I also checked the boxes to wipe everything as I told it to install cyanogen from the SD card. I've also tried booting to recovery manually and scrolling to wipe/restore to factory before trying to install cyanogen from zip.

Make sure you wipe EVERYTHING

YoungSinema said:
Make sure you wipe EVERYTHING
Click to expand...
Click to collapse
From manual recovery (power + volume down -> home button) I "wipe data/factory reset" and I "wipe cache partition". I also "wipe dalvik cache" and "wipe battery stats" in the advanced menu.
I still get a persistent gray HTC text on black background boot screen.

tunafishman said:
From manual recovery (power + volume down -> home button) I "wipe data/factory reset" and I "wipe cache partition". I also "wipe dalvik cache" and "wipe battery stats" in the advanced menu.
I still get a persistent gray HTC text on black background boot screen.
Click to expand...
Click to collapse
Redownload cm7 again. Could be a bad dl. Especially over 3g it could go bad so try wifi. Or try aosp's 2.3.4. Its a very stable rom with less cm bloat but still has it's features.
Also don't flash through the rom manager clockwork app. Doing everything from the recovery works better IMO. My guess is that's why it failed. Because you flashed it through the app and not in recovery. In the recovery it's says install zip from sdcard. Select that and find your cm download and load it there. Then your gapps. Bet it'll work after that.
If it doesn't load or doesn't boot up after that then its your clockwork recovery. In the manual recovery at the top it'll say what version your using. The latest is 2.0.5.7 I think. Personally I use a different recovery but for your use the latest will work just fine.
®patience is a virtue©

MattCrystal said:
Redownload cm7 again. Could be a bad dl. Especially over 3g it could go bad so try wifi. Or try aosp's 2.3.4. Its a very stable rom with less cm bloat but still has it's features.
Also don't flash through the rom manager clockwork app. Doing everything from the recovery works better IMO. My guess is that's why it failed. Because you flashed it through the app and not in recovery. In the recovery it's says install zip from sdcard. Select that and find your cm download and load it there. Then your gapps. Bet it'll work after that.
If it doesn't load or doesn't boot up after that then its your clockwork recovery. In the manual recovery at the top it'll say what version your using. The latest is 2.0.5.7 I think. Personally I use a different recovery but for your use the latest will work just fine.
®patience is a virtue©
Click to expand...
Click to collapse
Yup. Id agree.
#Root/Hack-Mod_Always*

MattCrystal said:
Redownload cm7 again. Could be a bad dl. Especially over 3g it could go bad so try wifi. Or try aosp's 2.3.4. Its a very stable rom with less cm bloat but still has it's features.
Also don't flash through the rom manager clockwork app. Doing everything from the recovery works better IMO. My guess is that's why it failed. Because you flashed it through the app and not in recovery. In the recovery it's says install zip from sdcard. Select that and find your cm download and load it there. Then your gapps. Bet it'll work after that.
If it doesn't load or doesn't boot up after that then its your clockwork recovery. In the manual recovery at the top it'll say what version your using. The latest is 2.0.5.7 I think. Personally I use a different recovery but for your use the latest will work just fine.
®patience is a virtue©
Click to expand...
Click to collapse
I've downloaded 7.0.3 twice and also 7.0.0 just for fun. All through my home internet onto a macbook pro and transferred via USB to the SD card.
I'll try again and make sure to only use the manual recovery. Also, thanks for the aosp suggestion!

It's a no-go on everything.
Formatted boot, system, data, and cache. Wiped dalvik cache and battery stats. Tried to install a fresh copy of CM7 and also tried AOSP 2.3.4 with same steps.
The only thing that doesn't stall at the boot screen is my backup.
There must be something about versions that is wrong here. Something isn't playing nice.

Excuse me sir. Don't mean to but in here. But I think you missed the part were matt suggested you reflash your recovery. Its good advice. Whatever your current recovery is try reflashing it, repeat the necessary wipes and flash your rom of choice. You can reflash your recovery threw adb or if your s-off threw an hercimg.zip or if you have a nand you can boot into you can do it threw terminal or rom manger.
#Root/Hack-Mod_Always*

Personally I bootload to flash any recovery but also I'm s-off. Its extremely easy and all you have to do is rename the file and move it to the root of the SD card. Using terminal emulator is also very easy if your not s-off. If your still unsure about some of this just keep asking us. More than willing to help. Here ill make it a little easier. Go find the s-off thread and make it happen. Ill throw you my renamed version of green lantern recovery. Trust me it works perfect. Still clockwork. Just different. Then all youll have to do is bootload the recovery then reboot to recovery. And you already know how to do that.
1st go to that s-off link
Dropbox link to greenlantern
http://db.tt/ORAwPdX
The file is named
greenlanternHERCIMG.zip, just delete the greenlatern part and it's good to go.
Heres the s-off thread. All you need is the zip in the bottom of the op. Then flash it through manual recovery as always now
Get the recovery working first then we can help fix the flashing rom if it continues
http://forum.xda-developers.com/showthread.php?t=759955
*I use bootloader just to be a dork really and watch it load for that 2 seconds it takes then reboot, but who's phone doesn't like a reboot .. honestly.
®patience is a virtue©

did the same thing bro
noob here
nandroid, nandroid , nandroid,,,got it?
wipe data,
wipe cashe,
wipe dalvic,
the only thing I do different sometimes ( when having trouble flashing)
format data,
formet cashe,
format system,
flash rom and enjoy
Learned this from a Dev that used to be here but is gone now. dont know why it works but it does.hope it helps

Update? Be nice to know what's happened
®patience is a virtue©

tunafishman said:
I've tried to look everywhere for info on this issue and the closest I got was in the developers thread where someone was going to flash from Fresh 2.4 to CM 6. Apologies if I'm completely dense here.
There seem to be tons of ins-and-outs that I'm not yet hip to like hboot versions and clockwork vs fastboot and etc.
I am running Fresh 2.4 and I'm getting the "Low on space" trouble that others have noted. I downloaded cyanogen 7.0.3 to my SD and installed ROM Manager. I am able to boot to ClockworkMod and can select the zip to install from. After CM installs I reboot and can't get past the boot screen. (As a side note, I notice the videos all have a white background with black HTC while my boot is gray HTC on black background.)
Is there something I'm missing? The only thought I had was to revert back to completely stock ROM and try to start all over again. Thanks!
Click to expand...
Click to collapse
Try Using the Firerats Tweek for the Low Space Issue!
As for the other Issue Firerats may Also Fix that Problem!
*Sent on My*
Fast as its Ever Been....
"Sprint" Hero.... Running My, *ExEnHeroC* Rom, w/Kifno's Twist, Also The XDA-BLUE.apk!! "Page 10" of My Thread!!
http://forum.xda-developers.com/showthread.php?t=957867
http://www.megaupload.com/?d=WTMLMK6M
http://www.mediafire.com/?bb1axugm0bw7oro
http://m.youtube.com/index?desktop_uri=/&gl=US#/profile?user=PMGRANDS

Please Help S-on Bootloop

I have no idea what happened, my Hero has been rooted for over a year now and never had any problems. I flashed a herodeck rom version 1.2 and after that I could not flash any more roms but could restore all my nandroids. So I used this, RUU_Hero_C_Sprint_2.27.651.5_R_signed_release.rar, to go back to stock and installed unrevoked, and all went well. I then flashed this TeamHeroC-2.3.5-01OCT-CM-V2.zip and finally it worked and was working great until last night my battery went dead and when I plugged it in to charge it powered up to the white HTC screen and has been stuck there since. I have tried to reflash , restore nandroids, and even hboot a HERCIMG and that is when I noticed S-ON. and since this has happened every file I try to flash comes up corrupt and the latest CM rom came up no signature, and I keep getting errors such as this. So right now all I can do is boot into recovery or Hboot. Please someone help me with this. I love this phone!

williams1978 said:
I have no idea what happened, my Hero has been rooted for over a year now and never had any problems. I flashed a herodeck rom version 1.2 and after that I could not flash any more roms but could restore all my nandroids. So I used this, RUU_Hero_C_Sprint_2.27.651.5_R_signed_release.rar, to go back to stock and installed unrevoked, and all went well. I then flashed this TeamHeroC-2.3.5-01OCT-CM-V2.zip and finally it worked and was working great until last night my battery went dead and when I plugged it in to charge it powered up to the white HTC screen and has been stuck there since. I have tried to reflash , restore nandroids, and even hboot a HERCIMG and that is when I noticed S-ON. and since this has happened every file I try to flash comes up corrupt and the latest CM rom came up no signature, and I keep getting errors such as this. So right now all I can do is boot into recovery or Hboot. Please someone help me with this. I love this phone!
Click to expand...
Click to collapse
Check md5sums of the zips in your sd card to verify no corrupt files. Also make sure signature verification is not toggled in CWM.

dastin1015 said:
Check md5sums of the zips in your sd card to verify no corrupt files. Also make sure signature verification is not toggled in CWM.
Click to expand...
Click to collapse
Thanks for the advice, I will check the Md5sums but I am actually using darchstar's RA recovery at the moment. Also I have formatted my sd card a couple of times and ran disk check on it and also downloaded the roms and files several times.

Hi,
If u have the time, unroot the same way again and then reroot but this time use ROM manager(free version). Update to latest recovery and then
Start over.
It sucks but without the proper knowledge its difficult to fix some issues. So starting over is easiest.
Good luck
V'sHERO on Tapatalk

I'm having the same problem but I cant even flash the stock ROM.

blacksapphire08 said:
I'm having the same problem but I cant even flash the stock ROM.
Click to expand...
Click to collapse
Can u flash anything else?
If so, u may just have a bad download or u have to do at least a factory reset b4 flashing anything.
Good luck
Unroot zip file is also EZ if u just want stock out of the box back on ur phone.
V'sHERO on Tapatalk

vidaljs said:
Hi,
If u have the time, unroot the same way again and then reroot but this time use ROM manager(free version). Update to latest recovery and then
Start over.
It sucks but without the proper knowledge its difficult to fix some issues. So starting over is easiest.
Good luck
V'sHERO on Tapatalk
Click to expand...
Click to collapse
Again thanks for the advice but I can't even do that now as I am stuck on the HTC screen and all I can do besides look at a white HTC screen is boot recovery (darchstars RA recovery) and boot into bootloader. Everything I try to flash will not verify for some reason or another(corrupt or unsigned or something crazy like that) and the RUU will not connect to the phone because it is stuck at the white HTC screen. This one has really stumped me as I have brought this phone back from some bad predicaments, or at least I thought they were. I did get it to try and flash a hercimg of an extracted RUU that is on this forum but it ends up saying no image found and just goes back to the bootloader menu.

williams1978 said:
Again thanks for the advice but I can't even do that now as I am stuck on the HTC screen and all I can do besides look at a white HTC screen is boot recovery (darchstars RA recovery) and boot into bootloader. Everything I try to flash will not verify for some reason or another(corrupt or unsigned or something crazy like that) and the RUU will not connect to the phone because it is stuck at the white HTC screen. This one has really stumped me as I have brought this phone back from some bad predicaments, or at least I thought they were. I did get it to try and flash a hercimg of an extracted RUU that is on this forum but it ends up saying no image found and just goes back to the bootloader menu.
Click to expand...
Click to collapse
Try downloading a recovery from Dastin's thread. Rename it HERC.IMG and place in the root of the SD card. Bootloader and flash. Power down then hold home and power back up to see if recovery worked. See if you can get any recovery flashed at all and if you do you can fix anything then.
¦¦self proclaimed resident prick¦¦

I finally got clockwork recovery 2.5.0.7 by using adb to push to sd card and then flashing from adb. Still can not do anything else, it is still acting the same.

http://forum.xda-developers.com/showthread.php?t=1063843
Try this there's alot of good links.
Sent from my DROID3 using xda premium

You might want to try getting s-off via darch's method. Then flash the eng-spl. Then do a fastboot erase system -w. Then reflash your recovery to see if that helps. If you need any of the files mentioned just pm me and I'll send you a dropbox link. You should be able to get back up and running this way. Good luck.
Locked & Loaded
""Shooter on Deck""

laie1472 said:
You might want to try getting s-off via darch's method. Then flash the eng-spl. Then do a fastboot erase system -w. Then reflash your recovery to see if that helps. If you need any of the files mentioned just pm me and I'll send you a dropbox link. You should be able to get back up and running this way. Good luck.
Locked & Loaded
""Shooter on Deck""
Click to expand...
Click to collapse
Ok I downloaded 1 of the zip files for darch's eng spl because the first link sems to be down. But I transfered the zip onto my sd card with card reader/writer and computer and then flashed it with clockwork 2.5.0.7 and I now have s-off again finally. So before I do anything else I am going to wait and se what you guys think I should do now. Thanks for all the help guys

williams1978 said:
Ok I downloaded 1 of the zip files for darch's eng spl because the first link sems to be down. But I transfered the zip onto my sd card with card reader/writer and computer and then flashed it with clockwork 2.5.0.7 and I now have s-off again finally. So before I do anything else I am going to wait and se what you guys think I should do now. Thanks for all the help guys
Click to expand...
Click to collapse
Are you formatting boot, system, cache, and data before flashing any of these roms? I do it 3x for each partition to make sure everything is wiped clean.
I have always thought that unrevoked was a permanent s-off unlike darch's which is temporary. I have both. I have always felt that if i can get into recovery, I'm golden. Make sure everything is wiped (not just data and cache) before you flash a new Rom.
Sent from my wildheroc using XDA App

Drunkpilot said:
Are you formatting boot, system, cache, and data before flashing any of these roms? I do it 3x for each partition to make sure everything is wiped clean.
I have always thought that unrevoked was a permanent s-off unlike darch's which is temporary. I have both. I have always felt that if i can get into recovery, I'm golden. Make sure everything is wiped (not just data and cache) before you flash a new Rom.
Sent from my wildheroc using XDA App
Click to expand...
Click to collapse
Yes, a couple of times, manually and with Light's format and Caulkin's format. and also I tried to fastboot hercimg.zip of the extracted RUU and all was going well and it actually finally asked if I wanted to apply the update like it is suppose to and it started loading and then when it finished it rebooted hboot and tried to install it again and also at this point I had s-on again. So I redone everything and am now back to s-off.

williams1978 said:
Yes, a couple of times, manually and with Light's format and Caulkin's format. and also I tried to fastboot hercimg.zip of the extracted RUU and all was going well and it actually finally asked if I wanted to apply the update like it is suppose to and it started loading and then when it finished it rebooted hboot and tried to install it again and also at this point I had s-on again. So I redone everything and am now back to s-off.
Click to expand...
Click to collapse
Are you still on a stock "sense" rom right now? What is your PRL, Radio, and PRI? Make sure everything is updated and you should be ready to go now. Since you are S-off now, I would place a HERCIMG.zip on your sd card of a recovery (I've been liking the 4.0.1.4 Orange Lantern that Dastin compiled (which is an unofficial CWM) just so that I have it at the ready in case anything goes south.

If your s-off again make a nand if you can. Also like dp asked what rom, radio, are you on???. Also imo you should flash Ra1.7 untill your back up and running for this process and just revert back when all this is done. Also you should do a fast boot erase system -w to clear everything out. Then backup your sd to your pc and format it as well. Once threw your pc and restore the defaults and then threw your recovery. Which is y I suggest Ra it makes it quick and easy. Ill check back here to see were your at threw out the day.
Edit: Pm sent.
Locked & Loaded
""Shooter on Deck""

The last rom I was on was [ROM][03-OCT-2011][TeamHeroC-2.3.7 - 2.6.35 Kernel] but I am stuck at the white HTC screen right now has been all day. When you say RA 1.7 recovery are you talking about Darchstar's RA 1.7?
Still no luck everything I try to flash fails, I kept getting an error 5 in clockwork recovery when trying to flash CyanogenMod 7 for the HTC Hero (CDMA) :: V7.1.0 (9 Oct 2011).

williams1978 said:
The last rom I was on was [ROM][03-OCT-2011][TeamHeroC-2.3.7 - 2.6.35 Kernel] but I am stuck at the white HTC screen right now has been all day. When you say RA 1.7 recovery are you talking about Darchstar's RA 1.7?
Still no luck everything I try to flash fails, I kept getting an error 5 in clockwork recovery when trying to flash CyanogenMod 7 for the HTC Hero (CDMA) :: V7.1.0 (9 Oct 2011).
Click to expand...
Click to collapse
Yes, I am.
Locked & Loaded
""Shooter on Deck""

Okay I switched recoveries to RA 1.7. I have tried several times to flash CyanogenMod 7 for the HTC Hero (CDMA) :: V7.1.0 and each time a different file comes up corrupt but I have been checking the md5's after it is on the sd card and they have been good. It is crazy, I can flash everything but Roms.

You should do a fastboot erase system -w.
Locked & Loaded
""Shooter on Deck""

Cwm bootloop

I went into CWM to do a restore of a nandroid. After the restore finished and I thought I was going to boot up the google came across the screen and I booted right back into CWM. I can not get out of CWM. I can not get to bootloader by pressing vol + - and power. Everything I do just loops me back to CWM. Can anybody help? Thank you.

Have you tried flashing a rom to see if it boots up? I would wipe everything and flash a rom.

getbuzzin said:
Have you tried flashing a rom to see if it boots up? I would wipe everything and flash a rom.
Click to expand...
Click to collapse
Yes I have flashed my backups and I have flashed JR6 and after it finishes and I touch reboot it goes to the google screen and acts like it is gonna reboot and then reboots right back to CWM.

It could be similar to the way boot flags don't (I mean, are supposed to...) work on the tf201/tf300t models...
You may have to dd away a few bytes on one of the partitions via adb.
I don't own a N7, so I can't guarantee or confirm.
Good luck!
Sent from my Galaxy Nexus using Tapatalk 2

Well did not have to worry about all that. Found my fix here. http://forum.xda-developers.com/showthread.php?t=1781250 should be able to work for anything given you have the files for your device.

[Recovery] Unofficial TWRP 2.6.3.0 for XT901 / XT907

UNLOCKED BOOTLOADER REQUIRED
Here it is: TWRP 2.6.3.0
I've tested backing up / restore, wiping, and installing an old backup (from ver. 2.6.0.0) and all seem to work. I also included the flag "HAVE_SELINUX := true" so it should be compatible with the newer 4.3 based ROMs (needs tested).
To install:
Download and unzip file ("img" was a few bytes over the 8mb forum limit)
Code:
fastboot flash recovery XT901-XT907-TWRP-2.6.3.0-recovery.img
BUGS: I have had the screen start very dim. Sometimes restarting the recovery would fix it, otherwise go to settings / screen, and set the timeout short so it goes out. Press power to turn on and it is at full brightness.
Enjoy!!
Thanks to:
TeamWin for TWRP.
Hashcode and Dhacker for STS-Dev Team source.
Djrbliss for unlocking the bootloader & providing root in the first place.
and mattlgroff

Thank you! Just tested it briefly and it works great. Glad the recovery is finally fixed to be able to use ADB. Was unable to use any TWRPs from 2.5.0.0+ as ADB was broken in the recovery.

CM 10.2 Build removed due to errors.

jbaumert said:
OP updated with link for TWRP compiled with CM10.2 sources
Click to expand...
Click to collapse
The recovery built with the 10.2 sources seems to have an issue with mounting the internal storage and sdcard, but the 1st one built is running perfect. I made a flashable zip of the 2.6.3.0 recovery for anyone who wants to simply flash it in recovery.

@mic213, Thanks for the sanity check. Any chance you have tried backup / restore of a 4.3 build?
Sent from my XT901 using Tapatalk 4

I was able to backup with it. Still hangs at reboot.
Sent from my XT907 using Tapatalk 4

netizenmt said:
Still hangs at reboot.
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
Do you mean when you reboot from TWRP? I noticed that on other builds, but didn't think much of it.

Recovery Tools is a free app on Google Play. Simply download the Recovery IMG. file from this post, and then open the Recovery Tools app. Grant it root, and now you can simply flash the img. file from the app without having to go into fastboot or compress the file into a flash able zip. Once recovery is flashed phone will reboot into whichever recovery is the most recently flashed. About as basic and straight forward as can be.
---------- Post added at 09:34 PM ---------- Previous post was at 09:22 PM ----------
The recovery file works great, only bug after about 4 days of use would be the dim menu screen in recovery. Still very readable even when bug pops up. Thanks for the great upload

Thanks. I could never get 4.3 to reboot past the initial boot after install, and now it finally does.

scottocs said:
Thanks. I could never get 4.3 to reboot past the initial boot after install, and now it finally does.
Edit....ehh maybe. Still working on it.
Click to expand...
Click to collapse
just make sure everything is wiped and that you are using 4.3 Gapps, also look up the SuperSU 1.65 update, some people have had trouble keeping root when rebooting into 4.3. Flash 4.3 ROM then GAPPS followed by SuperSU update, I would suggest running 4.3 on TWRP 2.5 or 2,6 first. Once your able to run 4.3 on one of those, then good ahead and try flashing 2.6.3. If anything on your phone is 4.2 and trying to load onto 4.3 it will never make it far past the boot screen.

Edited because I started rambling and couldn't delete.
Long story short, I have been having issues wiping, installing, and recovering.
I was flashing from a 4.3 ROM to another 4.3 ROM and decided it would be a good idea to wipe internal. Messed me up good.
I went back to 4.2 finally fixed booting issue on getting stuck at boot image. (Wasn't even making it to the boot animation.) I'll wipe everything except internal like I did before and go from 4.2 to 4.3. Last time I did this I didn't have issues.

motoroid7 said:
I'm not sure what I did, but some ROMs suggest that you wipe internal memory. I did this but now I have the issue after installing a ROM and booting it up... playing with it, if I then go to reboot the phone at all I just get stuck on my boot image (not the animation.) This happens on regardless of what ROM I've installed.
I also now can't go back to my backups. They fail on restoring. [Most recent backup was made on 2.5.0.0, previous to that 2.3.2.3]
How do I fix my phone? I'm wondering if I need to fxz back to a rooted stock ROM to fix what's going on?
Click to expand...
Click to collapse
This happened to me on TWRP too. When I went to restore, it say that it failed. However, I decided to boot into system anyway. TWRP gave me a warning that no OS was installed but I went ahead and rebooted. It booted into my backed up ROM just fine but it needed to be set up, like I just had flashed it. Basically, the restore process restored everything but my data. I did a barebones set up then booted back into recovery and went to restore the same exact ROM. This time, I got my complete ROM, just as I had saved it. This is kind of a long process, but it's better than having to FXZ or using a utility to go back to stock.

RikRong said:
This happened to me on TWRP too. When I went to restore, it say that it failed. However, I decided to boot into system anyway. TWRP gave me a warning that no OS was installed but I went ahead and rebooted. It booted into my backed up ROM just fine but it needed to be set up, like I just had flashed it. Basically, the restore process restored everything but my data. I did a barebones set up then booted back into recovery and went to restore the same exact ROM. This time, I got my complete ROM, just as I had saved it. This is kind of a long process, but it's better than having to FXZ or using a utility to go back to stock.
Click to expand...
Click to collapse
It's too bad I can't seem to locate the delete button on these posts, I'll go ahead and edit it. I was finally able to flash LiquidSmooth v2.9 (Android 4.2). It finally booted up, I just went back in and flashed gapps. It restarted fine. The real test is going to see if I go to hit a regular reboot and it boots up normally again. If that's the case I'm fixed. I would like to flash back to SlimROM that I had, but it seems that's going to probably be difficult without it messing up again. Not sure what to do if it does again. I won't be wiping internal memory anymore. I didn't have issues going from 4.2 to 4.3 when I didn't do it.
Any idea why I get a funky e:error: unknown media 'datamedia' error all the time in TWRP? I've had that error since like v2.3.x.x

motoroid7 said:
It's too bad I can't seem to locate the delete button on these posts, I'll go ahead and edit it. I was finally able to flash LiquidSmooth v2.9 (Android 4.2). It finally booted up, I just went back in and flashed gapps. It restarted fine. The real test is going to see if I go to hit a regular reboot and it boots up normally again. If that's the case I'm fixed. I would like to flash back to SlimROM that I had, but it seems that's going to probably be difficult without it messing up again. Not sure what to do if it does again. I won't be wiping internal memory anymore. I didn't have issues going from 4.2 to 4.3 when I didn't do it.
Any idea why I get a funky e:error: unknown media 'datamedia' error all the time in TWRP? I've had that error since like v2.3.x.x
Click to expand...
Click to collapse
Not 100% sure, but i believe that when you wiped your internal memory on 4.3 you deleted the ROOT. SuperSU seems to be having issues with
carrying over root on 4.3 to some peoples devices, Ive had to flash SuperSU update 1.65 from recovery otherwise when ROM boots up I get stuck in a cycle of SU Binary update/reboot. Also make sure that in Developer Options in your custom ROM, that Root Access is set to APPS and ADB and the same in SuperSU - APPS/ADB. Now to clarify I may be merging two unrelated issues together. If so, my bad lol.. But from my experience running PaCMan 4.3 since August, and now running TWRPS 2.6.3 since OP , 4.3 ROOT will not revert back to 4.2 unless Recovery is included in the backup. One final suggestion, try flashing the boot.img from 4.2 before flashing your 4.2 restore. I was able to revert back to 4.1 restores when I upgraded to 4.2 but while running 4.2 I deleted the Root Data from Internal Storage, I strongly suggest looking up arrrghhhs Sept. 15th Kernal for XT 926 which runs the same for XT 907. It damn near all the way current with CM 10.2 merges, should make running which ever 4.3 ROM you want much easier. If you want to run a 4.2 Rom , look up arrrghhhs 10.1 kernal version.
Arrrghhhs xt926/907 kernal

Kyles1329 said:
Not 100% sure, but i believe that when you wiped your internal memory on 4.3 you deleted the ROOT. SuperSU seems to be having issues with
carrying over root on 4.3 to some peoples devices, Ive had to flash SuperSU update 1.65 from recovery otherwise when ROM boots up I get stuck in a cycle of SU Binary update/reboot. Also make sure that in Developer Options in your custom ROM, that Root Access is set to APPS and ADB and the same in SuperSU - APPS/ADB. Now to clarify I may be merging two unrelated issues together. If so, my bad lol.. But from my experience running PaCMan 4.3 since August, and now running TWRPS 2.6.3 since OP , 4.3 ROOT will not revert back to 4.2 unless Recovery is included in the backup. One final suggestion, try flashing the boot.img from 4.2 before flashing your 4.2 restore. I was able to revert back to 4.1 restores when I upgraded to 4.2 but while running 4.2 I deleted the Root Data from Internal Storage, I strongly suggest looking up arrrghhhs Sept. 15th Kernal for XT 926 which runs the same for XT 907. It damn near all the way current with CM 10.2 merges, should make running which ever 4.3 ROM you want much easier. If you want to run a 4.2 Rom , look up arrrghhhs 10.1 kernal version.
Arrrghhhs xt926/907 kernal
Click to expand...
Click to collapse
To piggy back on general advice: I found I was having all sorts of problems going from 4.2 to 4.3. What finally did the trick was I wiped Dalvik, System, Cache AND I formatted data. The formatting was what did the trick.

When you wipe in twrp 2.5+ the recovery does not delete data/cache from internal (system) unless user mounts system prior to wipe. Wiping system cache, data, and dalvik cache is a full system wipe. Recommended if switching ROM rather than flashing nightly. This way no files from a AOKP ROM stick around and try to associate with your new CM based ROM.
Sent from my XT907 using Tapatalk 2

Thanks for the advice guys.
I was finally able to successfully getting my phone to work again last night (very early in the AM). It's very strange. I actually had 0 issues going from LiquidSmooth v2.9 to LiquidSmooth v3.0 (4.2 to 4.3). Though it was from the same dev could be part of it. It wasn't until I tried flashing from SlimROM/4.3 to CM10.2 nightly (where I wiped internal memory requiring me to type "yes".) Another thing is strange is even though it was saying I lost root in TWRP, I'm not sure that I ever did, unless TWRP just re-installed it when I reboot recovery automatically... because I finally told it no when asked if I wanted to re-install root? Then I was finally able to get LiquidSmooth v2.9 bootable and stable.
Again, thanks for all the help guys. I just wish I had a little bit understanding what I all did to finally get it to boot up. It was pretty early in the morning... going on 5/6AM. So I was pretty tired doing all of this. I just knew I couldn't let my phone not be up and running by morning.

I did a backup last night, flashed a 4.3 ROM which had reboot issues, and then restored with this version. I had zero issues, unlike when I was trying to restore with the previous version. Thank-you for your work.

It works with the xt902 too. Thanks!

What's the difference between the link in the first post and the one in the fourth? One of the is broken? Which one has been built with the CM10.2 sources?
I'm using a CM10.2 ROM... Which one should I peek?
Thanks!