Related
Alright, we will start with a story - I am a fairly experienced root user. I had a fascinate, droid x, and now I have a thunderbolt. I had all three rooted and never had problems until now.
I have root access as well as a custom ROM on my thunderbolt. (I am currently using liquid 3.2).
The problem is that when I try to flash any other rom (I tried two: CM7.2 by ThunderShed and Infected by Virus) they do not work at all. I flash data, davik, and all that stuff. Infected gets stuck on HTC logo and CM7 gets further but freezes on startup after initial setup shows up.
My friend recomended flashing all different radios and I did that, but still having an issue. (I have 1.48.... and 0.0178... on now).
A few things.....check the md5 when you download. Wiping........wipe data/factory reset, then wipe cache, then go advanced and wipe dalvik cache, then go format/mount and format /system. Then install the .zip. If that doesn't do it, I have no idea, never had a problem flashing ROMs, only have problems once I start messing with them on my own.
I had to change to different recovery
Sent from my ADR6400L using xda premium
First, the roms do flash - just not boot up after. Both go through the process fairly well. Like I said - the only that actually works is Liquid 3.2, both Infected and CM 7.2 flash just get stuck at a different stage when booting up.
I'm going to download yet another rom and see whether that does it.
The recovery that I have is 5.0.2.1. I was going to install touch recovery and see if that was more reliable. I'll post later and see whether it was just the two roms possibly being bad (both downloaded from RootzWiki and not XDA).
Run superwipe after you wipe everything, then flash your rom.
Sent from my ADR6400L using XDA
Try flashing a stock kernel first.
I also had the droid, droidX, droidx2, incredible2, thunderbolt, and now the galaxy tab. Also fairly familiar with rooting and flashing, and I had the same problem and couldn't figure it out. My clockwork was out of date. Updated, and everything was right in the world again. Check your Recovery. I didn't think if the update during flash took that it was my recovery but I was wrong.
flashing problem...
did you make sure usb debugging is on, and allow mock locations and non market downloads, and try deleting the current infected rom and re-download it just to make sure it was a clean download...i love the infected roms, especially eternity with darkhorsetheme. if that doesn't do it idk man. best of luck and try to get a hold of a developer maybe
Thank you guys!
Alright, so first off - I made sure my recovery was up to date.
I did wipe format /system and that caused infected to load, but after about an hour of using it - it froze and then when I pulled the battery, it wouldn't go past HTC logo.
I did load CM 7.1 and that works well.
I'll keep digging at it and see if I can figure it out. Thank you everyone!
Did you ever find a solution? I am having the same problem. I have tried 3 roms. It starts the boot screen and then after a minute it reboots into recovery.
It's the recovery folks.
Cwm = fail
4ext = win
donnyp1 said:
Run superwipe after you wipe everything, then flash your rom.
Sent from my ADR6400L using XDA
Click to expand...
Click to collapse
Using super wipe fixed this issue for me. Even after triple wiping dalvik didn't work, super wipe did. :good:
I was curious to see how ICS worked so I finally gave in and flashed Black Widow ROM. I followed this exact instructions:
Requirements:
•Android Version 2.3.6 (6.12.17x - 6.12.181)
•Safestrap 1.09 or Bootstrap v2 (safestrap 1.07 will not work)
•Download and move zip/s to sdcard-ext
•Reboot into Recovery
•Create a Backup! (dont say i didnt warn you)
•YOU MUST Wipe Data/Factory Reset
•Wipe Cache partition
•(in Advanced) Wipe Dalvik cache
•(in Mounts and Storages) Format System
•Install zip from sdcard
•Flash ROM (do not flash Gapps or DarkGapps)
•Reboot System now
This isn't my first time using Bootstrap. I flashed many ROMs using it on my D2. It installed and then I rebooted. Now it sits on the screen with Motorola symbol with Dual Core Technogoly. I did make a backup but I'd really like to use this ROM before reverting back. Any suggestions?
JDunc said:
I was curious to see how ICS worked so I finally gave in and flashed Black Widow ROM. I followed this exact instructions:
Requirements:
•Android Version 2.3.6 (6.12.17x - 6.12.181)
•Safestrap 1.09 or Bootstrap v2 (safestrap 1.07 will not work)
•Download and move zip/s to sdcard-ext
•Reboot into Recovery
•Create a Backup! (dont say i didnt warn you)
•YOU MUST Wipe Data/Factory Reset
•Wipe Cache partition
•(in Advanced) Wipe Dalvik cache
•(in Mounts and Storages) Format System
•Install zip from sdcard
•Flash ROM (do not flash Gapps or DarkGapps)
•Reboot System now
This isn't my first time using Bootstrap. I flashed many ROMs using it on my D2. It installed and then I rebooted. Now it sits on the screen with Motorola symbol with Dual Core Technogoly. I did make a backup but I'd really like to use this ROM before reverting back. Any suggestions?
Click to expand...
Click to collapse
If it's stuck at the M logo you'll probably have to RSDLite back to GB. Remember, that M logo can be there for up to 5 to 6 minutes on the first boot, if that's not applicable then fastboot that bad larry back! (I got to be VERY proficient at flashing back, let me know if you need help)
Is there anyway I can get my phone in working order without having to RSD back to GB? I don't understand why it didn't work when I follow the instructions and I have experience in flashing.
JDunc said:
Is there anyway I can get my phone in working order without having to RSD back to GB? I don't understand why it didn't work when I follow the instructions and I have experience in flashing.
Click to expand...
Click to collapse
I haven't really messed with Safestrap or bootstrap that much, I tend to just run one OS. The problem is that you can't even get to the start up screen for those. Simple when you think about it, right now (if i understand correctly) you're stuck at the M, which leaves you only 1 possible way out of that screen and that's to send it to recovery which will only wipe or RSD your phone.
Anyone else think of any other options that he has or experience with this ROM??
Yea I went to stock recovery to wipe data/cache just to see what happened. Of course that didn't do anything. In order to RSD, what screen do I need to be on? I assume the screen its frozen on will not be the screen I need.
JDunc said:
Yea I went to stock recovery to wipe data/cache just to see what happened. Of course that didn't do anything. In order to RSD, what screen do I need to be on? I assume the screen its frozen on will not be the screen I need.
Click to expand...
Click to collapse
You'll need to hold down both Vol buttons when you power it up then go to AP Fastboot. Do you need a link to the tutorial? You can YouTube RSDLite DROID RAZR and should get plenty. Let me know if you need any additional info.
Sent from my DROID RAZR using XDA
I think I can figure the rest out. That's all I really needed to know. Thanks!
Also MAKE SURE you're at at least 50% battery!!
Sent from my DROID RAZR using XDA
Not sure how I can check this....phone was on 66% before ROM install but screen is stuck on and I don't know how to power off phone. Battery is draining but more than likely slowly.
This was a previous post on another thread and from what I understand it works:
"Try following Steps:
Boot in AP Fastboot > Connect your Wall Charger > Press Power
If you're a lucky your RazR will pass the red M and jump into the Battery Screen.
If your system is broken, you have to order an Factory Cable. With this you can flash the correct system signed or use the modded Utility for CDMA Leaks, to get your Phone back to life."
When they say "Factory Cable" is this not just a USB cable?
Nope. Its different from what i understand. Thanks for reminding me to get one on eBay before all the ICS madness starts. Lol.
I mean you can risk it but I've never had to mess with it as I'm almost always above 70% so I'm kinda out of the loop on that problem.
Sent from my DROID RAZR using XDA
I tried what you said...Went to AP Fastboot and it only goes back to the Motorola screen. So am I completely screwed here? Thought I need that screen to RSD?
JDunc said:
I tried what you said...Went to AP Fastboot and it only goes back to the Motorola screen. So am I completely screwed here? Thought I need that screen to RSD?
Click to expand...
Click to collapse
You just need to get to the AP fastboot screen then flash it. I think you'll be okay to flash. I've seen people do it with 40%. Just make sure as soon as it boots you put that puppy on the charger.
Should take about 15-20 mins. If you're gonna do it, best to do it sooner rather than later.
Sent from my DROID RAZR using XDA
I don't even know if I can get to that AP Fastboot screen. When I try it, it does nothing and goes back to my Motorola screen. I'm about to be off work so I can see what happens when I have a laptop around.
Yeah you're gonna need the laptop. Also, when you select AP fastboot you'll want to hit the vol+ button to select it. Hitting the power button just restarts the phone. Vol+ = Enter. That's probably what you did the first time.
Sent from my DROID RAZR using XDA
Indeed it is. Maybe I can try the charger now.
Yeah, its like learning a foreign language sometimes but with only 3 physical buttons they have to make do. Lol!
Sent from my DROID RAZR using XDA
JDunc said:
Not sure how I can check this....phone was on 66% before ROM install but screen is stuck on and I don't know how to power off phone. Battery is draining but more than likely slowly.
Click to expand...
Click to collapse
Hold the power button and volume down to force a hardware reboot.
Sent from my DROID RAZR using XDA
It's actually Power button + volume up and down and yes I've done this.
Since the last time I flashed CM7, RSD (any version) with any SBF file doesn't wipe my phone the way it used to. It's gotten to the point I can no longer flash custom ROMs. If I don't wipe data/cache first, it will flash a new SBF yet leave the apps that were on it before hand. And when I try to flash a custom ROM, I get an error every time. Did I mess up something down in the locked areas that can never be fixed? Is there another way to wipe the phone to a more original or basic point? Right now I'm completely wiping the int and ext sd-cards, wiping data/cache/dalvik, SBFing to 2.2.2, and OTAing back up to see what happens, though I'm doubting it will help.
edit: Didn't work. Still can't flash a custom ROM. I can run rooted stock 2.3.5 though, guess that's what I'm stuck with. Better than nothing.
Performing an SBF does not wipe any user data from the phone. Wipe the phone using the stock recovery before performing the SBF. There are many threads on here on how to SBF, root, and install your favorite ROM.
RyanThaDude said:
Performing an SBF does not wipe any user data from the phone. Wipe the phone using the stock recovery before performing the SBF. There are many threads on here on how to SBF, root, and install your favorite ROM.
Click to expand...
Click to collapse
It doesn't matter if I wipe everything or not, I still can't flash a custom ROM. Get an error every time, and have to SBF to get it bootable again. I had weird issues the first time I ran CM7 and tried to SBF back to stock. Took multiple battery pulls and random button pushing while rebooting before I could get it back into RSD mode. This last time let me SBF back fine, but I get the PASS result instead of the REBOOT PHONE MANUALLY now and can't flash anything.
Scur827 said:
It doesn't matter if I wipe everything or not, I still can't flash a custom ROM. Get an error every time, and have to SBF to get it bootable again. I had weird issues the first time I ran CM7 and tried to SBF back to stock. Took multiple battery pulls and random button pushing while rebooting before I could get it back into RSD mode. This last time let me SBF back fine, but I get the PASS result instead of the REBOOT PHONE MANUALLY now and can't flash anything.
Click to expand...
Click to collapse
Try this a files sometimes corrupt.
Download all new. Perform the sbf, while the phone reboots do the volume down power button thing to get into Android Recovery. Once there wipe data and cache....
I have about 10 cables in my house...only two or three work for flashing and such...try a different cable....
DROID DOES, Apple did...like I forgot when
Pixelation said:
Try this a files sometimes corrupt.
Download all new. Perform the sbf, while the phone reboots do the volume down power button thing to get into Android Recovery. Once there wipe data and cache....
I have about 10 cables in my house...only two or three work for flashing and such...try a different cable....
DROID DOES, Apple did...like I forgot when
Click to expand...
Click to collapse
I have a couple good cables that always work, tried them both. Wiped data and cache on SBF reboot, too. Rooted with One click and Pete's both. So far, nothing works.
are you sure, sbf is flashing correct?
try different version like 2.2.3 or 2.3.5
and check system info after to verify
then update.zip or flash 2.3.4 sbf
or try ezsbf to flash and/or root
Sent from my MB870 using xda premium
i've seen usb cables work with one device and not another, can be hard to tell
Sent from my MB870 using xda premium
sd_shadow said:
are you sure, sbf is flashing correct?
try different version like 2.2.3 or 2.3.5
and check system info after to verify
then update.zip or flash 2.3.4 sbf
or try ezsbf to flash and/or root
Sent from my MB870 using xda premium
Click to expand...
Click to collapse
I've tried 2.2.2, 2.3.3, and 2.3.4 all, then updated. I've tried 3 different versions of RSD. Exact same result. Haven't heard of ezsbf though, I'll check it out.
http://www.droidxforums.com/forum/droid-x2-hacks/41697-tool-ezsbf-dx2.html
it's an iso file you burn to cd or thumb drive, reboots pc to a Linux os
with options to flash sbf and root with zergrush
works for some, when rsd lite or rooting failed
Sent from my MB870 using xda premium
... Have you thought that maybe the recovery your using is corrupted? Download that apk again (the plain one not the patched cm7/9 version) and give that
Sent from my MB870 using xda app-developers app
Scur827 said:
Since the last time I flashed CM7, RSD (any version) with any SBF file doesn't wipe my phone the way it used to. It's gotten to the point I can no longer flash custom ROMs. If I don't wipe data/cache first, it will flash a new SBF yet leave the apps that were on it before hand. And when I try to flash a custom ROM, I get an error every time. Did I mess up something down in the locked areas that can never be fixed? Is there another way to wipe the phone to a more original or basic point? Right now I'm completely wiping the int and ext sd-cards, wiping data/cache/dalvik, SBFing to 2.2.2, and OTAing back up to see what happens, though I'm doubting it will help.
edit: Didn't work. Still can't flash a custom ROM. I can run rooted stock 2.3.5 though, guess that's what I'm stuck with. Better than nothing.
Click to expand...
Click to collapse
The reason why you can't flash custom ROMs such as CM7 or CM9 is that you keep going to 2.3.5 or maybe even trying on 2.2.2 or 2.3.3. I have a check to prevent you from using any version besides 2.3.4. Restoring a nandroid won't cut it either. You must SBF back to 2.3.4, wipe data/cache, root (using zergRush or Pete's Root Tools), install the unpatched BSR, and flash CM7 or CM9.
As for why your apps show up still after an SBF, like you said, you didn't wipe data/cache and the apps are stored in the data directory on your phone. An SBF does not wipe data or cache.
LordRalh3 said:
... Have you thought that maybe the recovery your using is corrupted? Download that apk again (the plain one not the patched cm7/9 version) and give that
Sent from my MB870 using xda app-developers app
Click to expand...
Click to collapse
That's the only thing I haven't tried I think, I'll give it a try. Good idea.
Droid X2 > Eclipse 2.2.1 > Tapatalk
dragonzkiller said:
The reason why you can't flash custom ROMs such as CM7 or CM9 is that you keep going to 2.3.5 or maybe even trying on 2.2.2 or 2.3.3. I have a check to prevent you from using any version besides 2.3.4. Restoring a nandroid won't cut it either. You must SBF back to 2.3.4, wipe data/cache, root (using zergRush or Pete's Root Tools), install the unpatched BSR, and flash CM7 or CM9.
As for why your apps show up still after an SBF, like you said, you didn't wipe data/cache and the apps are stored in the data directory on your phone. An SBF does not wipe data or cache.
Click to expand...
Click to collapse
I haven't tried to flash CM7 or CM9 since the last time I came off of it. I really like having the camcorder around my daughter. That was my only problem with either. they worked great when they were on. I've mostly been trying to get Eclipse back on.
I think that CM7 had something to do with my problem, though. I've flashed it twice before. The first time was hell coming back to stock, I thought my phone was bricked for about an hour. It took multiple boot attempts, battery pulls, and button mashing before I finally could get back to RSD mode to flash a SBF.
Everything seemed fine for a couple months, until I tried CM7 once again. When I tried to come back off of it the second time, RSD gave it a PASS at the end instead of hanging on REBOOT PHONE MANUALLY like it always did before, and has every time since then (was hit and miss before). Now I can still flash a SBF and update an OTA (but only after doing a *228 to download and install it, can't flash an OTA file from recovery), but if I try to flash any ROM (and I've tried a half dozen of them) while using any root method, I get an error while flashing, and have to wipe everything possible to be able to SBF back to stock. I've tried flashing ROMs at least 20 times over the past few days. Either something got messed up, somewhere in an area that both RSD and recovery don't touch, or it's a hardware issue. That's the only thing I can come up with.
Now, I don't believe it's CM7's fault. At all. There are just too many people who enjoy. I simply believe there was something odd or wrong about my phone.
Its like you know the words but not which ones go with what things... Flashing and sbfing are two completly different things, and there is no button mashing involved pull your battery one time, hold power and volume up at the same time, that puts you in rsd mode to sbf, to get over a bootloop just go to android recovery (power button and volume down then cycle to recovery) you don't flash roms in this recovery just wipe data/cache. If you grabbed the right sbf file (check your android version in about phone should be 2.3.4 ) you can root with motorola one click and install the bootstrap recovery program NOT THE CM7 VERSION, Plug phone into the wall bsr WIPE DATA/CACHE and flash cm7, its a standard process and your phone is not special
Sent from my MB870 using xda app-developers app
LordRalh3 said:
Its like you know the words but not which ones go with what things... Flashing and sbfing are two completly different things, and there is no button mashing involved pull your battery one time, hold power and volume up at the same time, that puts you in rsd mode to sbf, to get over a bootloop just go to android recovery (power button and volume down then cycle to recovery) you don't flash roms in this recovery just wipe data/cache. If you grabbed the right sbf file (check your android version in about phone should be 2.3.4 ) you can root with motorola one click and install the bootstrap recovery program NOT THE CM7 VERSION, Plug phone into the wall bsr WIPE DATA/CACHE and flash cm7, its a standard process and your phone is not special
Sent from my MB870 using xda app-developers app
Click to expand...
Click to collapse
Fine, I don't FLASH an SBF file. But I've flashed ROMs on the X2 alone at least a hundred times, I know what's what. I know the difference between stock recovery and BSR. I know the difference between BSR and the CM7 version, and when to switch over. I know what wiping data does, what wiping cache does, what the Dalvek cache is and what wiping it does, what fixing permissions really does.
When I say I couldn't SBF out of CM7, I mean after flashing CM7 the first time, I ran RSD Lite and used SBF 2.3.4-380 to get back to stock. RSD gave me an error, and stopped. I couldn't reboot the phone, it just hung up on the red M. Holding vol down+power hung up on the red M. Holding vol up+power hung up on the red M. So I would pull the battery and try it again. And again. And again. No buttons, every button. Letting it sit on the red M for 30 mins. Eventually I got a weird RSD message at the top (and no, not the vol up+power RSD message), different from the others, and I could SBF again. I still got an error, but could vol down+power into the regular menus, so once I got into the standard RSD mode the next SBF went fine, except I got a pass at the end instead of having RSD hang up on the reboot phone manually message it always got before. And since then I don't get the boot loops after it reboots like it used to, though the pass message is hit and miss. I've SBFed dozens and dozens of times since then, used fresh downloads and different versions of everything, and I've never seen another boot loop afterwards. Something, somewhere, is definitively different. I have a few good cables that have always worked, and I've switched them out. I've wiped and formatted everything possible on the phone several times. It's just not the same as it was before CM7. And after coming off of CM7 the second time, I've gotten a pass at the end of the SBF every single time. Another new thing after a CM7 flash.
Like I said, I don't think it's a CM7 issue, I just think there is something wrong with my phone on a level I can't touch, and it really didn't like CM7. It isn't operator error. Give me any instructions you like for getting me on, say, Molten (since it's 2.3.4-380 and the simplest to flash). I'll follow them to the T, but it won't work. I can't *228 anymore, so I can't download a system update, and I get a file signature error if I try to flash an update from stock recovery. I'm stuck on stock 2.2.2, 2.3.3, 2.3.4, or 2.3.5. I can still root them using any method, except 2.3.5 since it requires carrying root over with OTA Rootkeeper from 2.3.4.
Sorry if i came off too negatively btw its just that this phone is SOOOOO close to indestructible programming wise... Your next step is to burn ezsbf and head to someone elses computer and try that
Sent from my MB870 using xda app-developers app
LordRalh3 said:
Sorry if i came off too negatively btw its just that this phone is SOOOOO close to indestructible programming wise... Your next step is to burn ezsbf and head to someone elses computer and try that
Sent from my MB870 using xda app-developers app
Click to expand...
Click to collapse
Me too, just woke up.
I tried ezsbf yesterday on a laptop, no change. Tried a fresh copy of BSR from a different source this morning, no luck there either. I'm completely out of ideas now, there's nothing I haven't tried alternatives to. But I have a fully functional phone rooted on 2.3.4, and sometime in the near future I'll be getting something new and shiny, so it could be worse. When I do get a new one, this one will be perfect to have GrooVe IP on it for my 8 yr. old daughter, and the big screen is nice for games.
Droid X2 > Eclipse 2.2.1 > Tapatalk
Scur, I uploaded a nandroid of eclipse 2.3
don't know if that will work any better
but who knows, it just might work for you
http://www.mediafire.com/?7b71gn1j3r2dwrj
edit: if you problem is kernel related, it's not going help
also have you been checking the kernel,
System version:
1.3.418
Android version:
2.3.5
Baseband version:
N_03.13.31P
Kernel version:
[email protected]#2
sd_shadow said:
Scur, I uploaded a nandroid of eclipse 2.3
don't know if that will work any better
but who knows, it just might work for you
http://www.mediafire.com/?7b71gn1j3r2dwrj
edit: if you problem is kernel related, it's not going help
also have you been checking the kernel,
System version:
1.3.418
Android version:
2.3.5
Baseband version:
N_03.13.31P
Kernel version:
[email protected]#2
Click to expand...
Click to collapse
Here's where I am now. With a method to root 2.3.5, I can SBF it and root. It will let me flash Eclipse 2.3, but will lose root when it flashes. So I can get Eclipse 2.3, but it's unrooted and I haven't found a way to root it after flashing yet. Odd there. I have a couple abd tips to try to get it going, but I'm going to try your nandroid first. Much thanks.
Droid X2 > Rooted 2.3.5 > Tapatalk
The nandroid worked like a charm, I thank you good sir.
Droid X2 > Eclipse 2.3 > Tapatalk
I cannot get a single CM based ROM to install. I've tried PACman v5, CM 10, MoKee.....none of them will boot. I've followed the instructions to the tee, and tried several times with each. Upon reboot, it waits a few seconds, I get the short vibrate, and then nothing. No boot loop, nothing. I've deleted ROM slots, and recreated them several times. I've tried ROM slot 1 and 2. Nothing works. Any suggestions would be much appreciated.
When I installed cm10, the first boot took quite long. Try waiting 10 minutes to boot.
Sent from my Tricked out DROID RAZR MAXX.
rocksteady said:
When I installed cm10, the first boot took quite long. Try waiting 10 minutes to boot.
Sent from my Tricked out DROID RAZR MAXX.
Click to expand...
Click to collapse
Thanks for the response. I tried waiting 10+ minutes. Nothing. So, here is my install process:
Delete ROM slot 1
Re-create ROM slot 1
Wipe cache/Dalvik
Install CM10.1
Install GAPPS
Wipe cache/dalvik
reboot
After less than a minute, I will get a short vibration, but the screen stays black. From there, nothing further happens....no matter how long it sits. No boot screen....nothing. Just a black screen, as though the phone is turned off.
Any suggestions?
ddodge68 said:
I cannot get a single CM based ROM to install. I've tried PACman v5, CM 10, MoKee.....none of them will boot. I've followed the instructions to the tee, and tried several times with each. Upon reboot, it waits a few seconds, I get the short vibrate, and then nothing. No boot loop, nothing. I've deleted ROM slots, and recreated them several times. I've tried ROM slot 1 and 2. Nothing works. Any suggestions would be much appreciated.
Click to expand...
Click to collapse
May be These Video tutorials can help?
Try them, see them and then try again alongside
ALL RAZR GSM Tutorials u Need Under 1 thread! [Regularly Updated]
Hit Like button if it was helpful & subscribe to thread
hrishi21007 said:
May be These Video tutorials can help?
Try them, see them and then try again alongside
ALL RAZR GSM Tutorials u Need Under 1 thread! [Regularly Updated]
Hit Like button if it was helpful & subscribe to thread
Click to expand...
Click to collapse
I watched your video, even though my phone is CDMA. Unfortunately, I am still unable to get any CM ROM to boot. I had Butter working, prior to today, and I backed it up, before trying to install CM (both require slot 1), but I can't even get Butter back on.....with fresh install, or restore. Frustrated.
I had a similar problem and it was because i had bad downloads ... Try And download again the files and check again...
Sent from my XT910 using xda premium
ddodge68 said:
I watched your video, even though my phone is CDMA. Unfortunately, I am still unable to get any CM ROM to boot. I had Butter working, prior to today, and I backed it up, before trying to install CM (both require slot 1), but I can't even get Butter back on.....with fresh install, or restore. Frustrated.
Click to expand...
Click to collapse
Steven87 said:
I had a similar problem and it was because i had bad downloads ... Try And download again the files and check again...
Click to expand...
Click to collapse
As Steven said....try CM site http://get.cm/?device=spyder
n download the STABLE version or RC5 version...and see
Finally got CM 10.1 installed. Thanks for the help, everyone!!!
If someome helped dont just say thanks lol... There is a thanks Button
Sent from my XT910 using xda premium
Steven87 said:
If someome helped dont just say thanks lol... There is a thanks Button
Sent from my XT910 using xda premium
Click to expand...
Click to collapse
I used the "thanks" button, before I even posted my "thanks" comment...
OK so here's the story. Gonna be as detailed as possible. So I been running 4.3 Meanbean lately, and it's been running great. So I decided to flash Devil kernel and all was well. Well this morning my phone froze so I did a battery pull, wiped cache and dalvik and rebooted into a bootloop. Weird thing is the pick language screen flashes for a split second and back into a bootloop. I've tried 3 different TW ROMs all with clean flashes with the same result. Here's the kicker, AOSP boots just fine. Trying to avoid having to ODIN and CASUAL if possible. I don't know to try next. Thanks in advance to anyone willing to attempt.
Sent from my GT-P3110 using xda app-developers app