Hi there. Today, I set out to install a new rom. My old one was the NinjaAtrix, but lately the GPS lock has been very, very slow.
So, I wiped everything, and used Tenfar's CWM to flash the Aura rom and Faux's overclock kernel, remembering to wipe cache.
Upon boot, my wifi didn't work and my data/calls/text didn't work, AND I couldn't boot into CWM!
I encountered this before, and simply started over from installing a new SBF, and re-rooting it. It had already been unlocked, but I tried to unlock it again anywyas, with a message "Phone has already been unlocked."
Well, I looked and saw RomRacer's CWM was the preferred, and promptly ran the Fastboot commands. All seemed successful, but I can't boot into CWM. It acts as if it isn't there, and simply boots into the phone when I reboot with a USB cable plugged into a wall charger.
I read elsewhere to try installing the CWM via Rom Manager, which brings similar results.
I just tried flashing the rom with Rom Manager, to exhaust all my options, but it led me to an infinite boot animation. I'm going to re-flash the SBF and get back to the stock rooted rom, and see what solutions you guys can come up with.
I've spent the better portion of the past 6 hours tinkering with this darn'd thing.
Though, I didn't get introduced to the world of fastboot.
why do people not listen to me....
Try deleting "install-recovery.sh" @ /system/etc, then reinstall ROM Racers CWM and boot into Recovery.
Sent from my MB860 using xda premium
Erm, you need to hold volume down + power when powering on, than use volume down to pick recovery and start it with volume up. There's no wall charger in booting to romracers recovery. And ye delete the script that was already suggested.
Swiftks said:
why do people not listen to me....
Try deleting "install-recovery.sh" @ /system/etc, then reinstall ROM Racers CWM and boot into Recovery.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
I meant to mention that. There was no install-recovery.sh in /system/etc.
I used File Expert, with R/W permissions. I read that, don't worry. I also read another one of your posts where you mention this.
Now, I used Root Explorer, and couldn't find it. I'm running a search on the entire phone now.
Related
So like the title states I'm having some difficulties flashing a rom. I just updated to froyo 2.2 with root and I'm trying to flash nero v5.0. The problem I'm having is when I boot into clockwork i keep getting an E:can't open /cache/update.zip. I've tried both method 1 and 2 from here http://forum.xda-developers.com/showthread.php?t=732458
Did you make sure to take step 2 on the tutorial? "Flash clockwork recovery"?
If so, I would try it again to see if it helps. Another step is to uninstall ROM manager, then re-install it taking all the steps again. It sounds like you may have accidentally deleted the update.zip file that should be on the root of your SD card.
yea, i tried it. I flashed it. I even clear the data and uninstalled rom manager and reinstalled. I also never touched update.zip as well. This was the first time I've actually mounted my phone to my computer and opened up my internal/external sdcard.
OP, here is a thread I made for issues in the past.
Try this and let me know how it goes:
http://forum.xda-developers.com/showthread.php?t=875890
still no luck, i boot into recovery and get the same message still
Well, Hmm... You could try the steps in the noob guide and use ODIN to install froyo+root. This is the ALT METHOD in the guide. This is what I personally use.
Not really certain what's going on man, but doing this can't hurt.
I recently followed your guide, I could try again it wouldn't hurt my phone right?
No, you are not going to hurt your phone...
lets troubleshoot.
List to me step by step what you have done... If need be I will ODIN to JFD tonight and we can go through it together. I'm certain it's something silly though. No reason it should not work. You have a a Vibrant on T-Mobile right?
yea i have a tmobile vibrant so this is what i just did right now.
1) Flashed froyo+root from your noob guide followed all the steps (i.e. wipe data etc)
2) downloaded rom manager and flashed clockwork recovery.
3) placed nero v5.0 into the root of the phones internal sdcard.
4) went to rom manager and roboot. E: Can't open /cache/update.zip
(Bad)
Installation Aborted
nvm i think i got it to work
Do i need to do anything special for the longer battery life for nero v5.0
^^ what was the issue?
^ nothing special... you may want to recalibrate your battery. Drain it down to it powers off on its own (or really close)... charge it full... leave it on maybe an hour longer after fully charged... you can bump charge it (DO NOT do this a lot)... all this means is once full, unplug and then plug back in... your "full" battery will accept more charge....
dont boot up, but go straight to CWR and then Advanced > Wipe Battery Stats
reboot with the power cord still connected. Once its booted unplug and use like normal.
I repeat, do not bump charge often, this will hurt your battery.
I just flashed froyo again and used the update zip on the fix thread
Sent from my SGH-T959 using XDA App
How to you go straight to clockwork recovery?
Sent from my SGH-T959 using XDA App
krazy2o6 said:
How to you go straight to clockwork recovery?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
long press the power button and a list of options will show up, select "Recovery"
Hi, I am pretty new to this stuff, so bear with me here.
I recently rooted and installed eclipse v 0.5. Everything went well except I did not get my contacts and figured I did something wrong in the original ROM. I decided to go back to my original rom...but decided to wipe data because I thought that was the right thing to do. Now I have no idea how to restore the nandroid backup because I don't know how to get to clockwork recovery.
Help would be appreciated.
Thanks
morlakai said:
Hi, I am pretty new to this stuff, so bear with me here.
I recently rooted and installed eclipse v 0.5. Everything went well except I did not get my contacts and figured I did something wrong in the original ROM. I decided to go back to my original rom...but decided to wipe data because I thought that was the right thing to do. Now I have no idea how to restore the nandroid backup because I don't know how to get to clockwork recovery.
Help would be appreciated.
Thanks
Click to expand...
Click to collapse
Ever Think About Booting Into Recovery And Following The Same Steps Just Switch Backup To Restore. I'm Sorry But I Can't Believe You Asked This. I Mean How Did You Flash Eclipse You Must've Used The Bootstrap.
MikeJ92YJ said:
Ever Think About Booting Into Recovery And Following The Same Steps Just Switch Backup To Restore. I'm Sorry But I Can't Believe You Asked This. I Mean How Did You Flash Eclipse You Must've Used The Bootstrap.
Click to expand...
Click to collapse
agreed, u should still have bootstrap installed. are in in the os and dont know how to perform the nandroid restore or are you in the recovery and dont know where to go from there?
After you flash a rom the first time you use bootstrap you have to click install recovery
Sent from my DROID X2 using XDA App
MikeJ92YJ said:
Ever Think About Booting Into Recovery And Following The Same Steps Just Switch Backup To Restore. I'm Sorry But I Can't Believe You Asked This. I Mean How Did You Flash Eclipse You Must've Used The Bootstrap.
Click to expand...
Click to collapse
It has been my experience that after wiping data the bootstrap recovery is gone. Or I guess I shouldn't say gone but it will not boot into recovery after data wipe.
Sent from my DROID X2 using Tapatalk
Interesting Until The Atrix Port That Was The First Time I've Had To Flash The Recovery Again.
MikeJ92YJ said:
Interesting Until The Atrix Port That Was The First Time I've Had To Flash The Recovery Again.
Click to expand...
Click to collapse
weird, I had root and bootstrap still installed after wiping data/cache and dalvik cache.
That Might Have Been Read Wrong, By Flashing Recovery I Meant Pressing The Install Button. To Me That's Flashing The Recovery.
Have you tried just plugging in the phone to the wall charger. Yes wall. And wait to see if it goes to recovery mode.
If it doesn't work all I think you can do is sbf and start again.
Sent from my DROID X2 using XDA App
ok:
what do you do if said event happens where your recovery doesn't load through after the rom installs with the wipe/cache wipe
your phone boots, however your usb conditions are stuck on usb mode rather than charge mode.
the initial setup starts but is stuck in a loop of force closes that never end.
i have successfully used Roms in the past, no big deal. when **** hits the fan i use sbf; but i'm stuck in limbo where both recovery and sbf are seeming to be out of my options - unless i can change usb mode to charge mode by some strange form of buttons pressed.
electroniko said:
Have you tried just plugging in the phone to the wall charger. Yes wall. And wait to see if it goes to recovery mode.
If it doesn't work all I think you can do is sbf and start again.
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
tried the wall charger - what i had used initially to get into said recovery, i left it sit for more than 3 hours to see if maybe i was just being impatient, well its pretty much not doing anything for me
SubVirus said:
ok:
what do you do if said event happens where your recovery doesn't load through after the rom installs with the wipe/cache wipe
your phone boots, however your usb conditions are stuck on usb mode rather than charge mode.
the initial setup starts but is stuck in a loop of force closes that never end.
i have successfully used Roms in the past, no big deal. when **** hits the fan i use sbf; but i'm stuck in limbo where both recovery and sbf are seeming to be out of my options - unless i can change usb mode to charge mode by some strange form of buttons pressed.
tried the wall charger - what i had used initially to get into said recovery, i left it sit for more than 3 hours to see if maybe i was just being impatient, well its pretty much not doing anything for me
Click to expand...
Click to collapse
Unplug your phone. Hold volume up and power on until you see the m logo and rsd protocol starting.
Sent from my DROID X2 using Tapatalk
well that allows rsd to find it but - it won't just flash it and call it good. i'm getting all sorts of errors from rsd saying something about my ini
Code:
Failed flashing process. Unable to retrieve initialization value from INI file (0x7029)
i get this error before the above error (before i actually "start" it)
Code:
Chipset type 53 is not supported
restarted computer:
updated drivers:
no dice, same errors
EDIT: the problem was in the RSD version i was using, i got everything working now. thanks!
Hello guys.. I got a serious problem with my atrix.
today morning , I tried to install the CM7 and it was success. It works well,
but It's not my style so I wanted to go back to pure stock rom.
I used RSD and flashing olympus 4.5.91 rom. and my Atrix died.
it was just appeared M logo and turn off, and appeared M logo and turn off again and again.
what should I do in this happen? OMG................. i have to use my phone asap..................................
plz help me clever guys!!!!
Thanks
Can you get into recovery? You should've flashed fruitcake. RSD is a no-no.
Sent from my MB860 using XDA App
Nono flashing a gingerbread. Sbf wont hurt anything. But fruitcake is easier yes. Also plug your phone into the wall outlet. Let it do its thing. Then pull the battery out while its still plugged in. Leave it out 30 seconds. Then stick it back in and see if it charges.
Sent from my MB860 using Tapatalk
Phalanx7621 said:
Nono flashing a gingerbread. Sbf wont hurt anything. But fruitcake is easier yes. Also plug your phone into the wall outlet. Let it do its thing. Then pull the battery out while its still plugged in. Leave it out 30 seconds. Then stick it back in and see if it charges.
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
Hi guys, I'm having the same problem as the OP. Here's my story:
- Got my phone with 2.3.4/4.5.91.
- Used Automatic Scripts to unlock BL and root.
- Everything was working fine.
- Flashed Tenfars' recovery.
- Everything fine again.
- Switched to RomRacer's recovery to test it.
- All good so far.
- Flashed CM7 thru recovery and it all went down.
- Got in a bootloop, showed CM7 boot animation and rebooted.
- Tried to ditch CM7, so restored my backup previously done via Recovery.
- Bootloop again, instead of CM7 animation, showed the M logo and reboot.
- Freaked out.
Fastboot and recovery work. Connected the charger and displayed the battery charging. Am thinking about installing some "Official Motorola 2.3.4/4.5.91 MSU" that is recommended on the Auto Script.
dr_tracker said:
Fastboot and recovery work. Connected the charger and displayed the battery charging. Am thinking about installing some "Official Motorola 2.3.4/4.5.91 MSU" that is recommended on the Auto Script.
Click to expand...
Click to collapse
Since you can get into fastboot and recovery, just try flashing a fruitcake.
Are you still using romracer's CWM? Was the backup you're trying to flash made with romarcer's or Tenfar's? I now people had issues when trying to flash backups made with tenfar's after upgrading to romracer's. I think it had to do with how each CWM formats.
ghost_og said:
Since you can get into fastboot and recovery, just try flashing a fruitcake.
Are you still using romracer's CWM? Was the backup you're trying to flash made with romarcer's or Tenfar's? I now people had issues when trying to flash backups made with tenfar's after upgrading to romracer's. I think it had to do with how each CWM formats.
Click to expand...
Click to collapse
Thanks, downloading fruitcake as we speak, the one that reads "2.3.4 System and Boot NO Webtop (Updated Newest Script)", right???
Backup was made with Tenfar's, I instaleld Romracer and flashed CM7, switched back to Tenfar prior to restore, so not to mix backups.
One Q, after I flash this fruitcake, can I restore my backup and go on with my stock motoblured life???
TIA.
dr_tracker said:
One Q, after I flash this fruitcake, can I restore my backup and go on with my stock motoblured life???
TIA.
Click to expand...
Click to collapse
That I don't know. Don't see why not. But I don't want to give advice on something I haven't done personally. Plus I have never used tenfar's recovery. ( I believe it's out of date?) Search time
Sent from my MB860
You can't restore backups made with tenfars recovery with romracers later on.
Thanks alot guys, fruitcake did the trick. At the Motoblur registration screen, just rebooted to recovery and restored my backup, everything is up again.
My thunderbolt got stuck in boot loop about a week later after flashing Liquid ICS MR3V1. If I attempt to reboot the phone numerous times it will eventually boot up and work fine. The phone will not allow me to get into recovery - it will just go into boot loop once recovery is selected. I did manage to get the phone to go into recovery one time and I wiped everything and installed an infected eternity rom that I have been running for a long time without any issues. I thought I was okay once I flashed this rom but when I restarted the phone it went into the boot loop sequence again. Currently after 15+ attempts at starting the phone I got it to boot up without the SD card. I rooted my thunderbolt through revolutionary...if it matters?
From reading other threads it appears I need to install an RUU? Can I just install a RUU that will not un root my phone or do I need to change my modded Hboot, go back to s on and unroot? I flashed roms numerous times without issues and I always wipe multiple times and I am not sure what happened here. Unfortunately I do not have any backups to revert back to -- since I read flashing an RUU without the proper steps can brick my phone I wanted to seek advice to make sure I do it properly.
ys RUU can help you . just my own thought.
good luck to you :laugh:
xcmtnbiker82 said:
My thunderbolt got stuck in boot loop about a week later after flashing Liquid ICS MR3V1. If I attempt to reboot the phone numerous times it will eventually boot up and work fine. The phone will not allow me to get into recovery - it will just go into boot loop once recovery is selected. I did manage to get the phone to go into recovery one time and I wiped everything and installed an infected eternity rom that I have been running for a long time without any issues. I thought I was okay once I flashed this rom but when I restarted the phone it went into the boot loop sequence again. Currently after 15+ attempts at starting the phone I got it to boot up without the SD card. I rooted my thunderbolt through revolutionary...if it matters?
From reading other threads it appears I need to install an RUU? Can I just install a RUU that will not un root my phone or do I need to change my modded Hboot, go back to s on and unroot? I flashed roms numerous times without issues and I always wipe multiple times and I am not sure what happened here. Unfortunately I do not have any backups to revert back to -- since I read flashing an RUU without the proper steps can brick my phone I wanted to seek advice to make sure I do it properly.
Click to expand...
Click to collapse
Sounds like something is just wrong with you recovery. Try flashing another recovery. Also, IF you're using the boot manager app, it may be acting up. If the boot manager app is on your phone, I'd recommend removing it.
Sent from my ADR6400L using xda premium
RBarnett09 said:
Sounds like something is just wrong with you recovery. Try flashing another recovery. Also, IF you're using the boot manager app, it may be acting up. If the boot manager app is on your phone, I'd recommend removing it.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
Do you mean try re installing cwm? I currently can't get into cwm because it goes into the boot loop sequence. I will try this later tonight and see if it helps. I do not have a boot manager app, I believe when I rooted through revolutionary it modifies hboot? (I have been rooted for over a year now withoutproblems)
xcmtnbiker82 said:
Do you mean try re installing cwm? I currently can't get into cwm because it goes into the boot loop sequence. I will try this later tonight and see if it helps. I do not have a boot manager app, I believe when I rooted through revolutionary it modifies hboot? (I have been rooted for over a year now withoutproblems)
Click to expand...
Click to collapse
No, boot manager is just an application from the play store.
Yes, try downloading cwm recovery again.
Sent from my ADR6400L using xda premium
RBarnett09 said:
No, boot manager is just an application from the play store.
Yes, try downloading cwm recovery again.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
Update - I reinstalled CWM and got the phone into recovery, and did a reset, wiped everything and got stuck in boot loop. I eventually got the phone to boot up and I deleted a couple roms, etc in my download folder. After this was done I power cycled the phone twice without any issues.
So I've had the joy of rooting/unlocking a Thunderbolt and a Galaxy Nexus and now my DNA, so I'm vaguely familiar with how it works.
I had unlocked and rooted the phone about two months ago. I think I'm running a stock ROM with all the bloat removed I couldn't tell you exactly which one, but I think it's just the one that's deodexed with bloat removed. Had been running fine for awhile. Decided to use the Cubed DNA Kernel 2.4.2, roughly after I did this my phone would start to randomly reboot, which started about 2 weeks ago.
I didn't think anything of it up to this point and thought I'd fix it at some point. Today it rebooted once again, but this time it would never make it back into the Android OS, or if it did make it it would immediately freeze and I'd have to force reboot it. At this time I could still get into the CWR and the Bootloader. But that's really all I could do. I attempted to roll back to previous backups, this didn't work. So then I thought maybe it's the Kernel, so I was going to put it back to stock. Per the instructions I attempted to flash the boot.img file before flashing the stock kernel modules zip file.
After I did the flash for the boot.img, I can no longer get into CWR. I can still get into the bootloader, but that's really about it.
Unfortunately I have no device to fall back on. So any help or suggestions would be extremely helpful.
What happens when you try to go into recovery?
And just so you know, it was your kernel that was causing the reboots. It is a known issue with cubed kernel that dsb is working hard to fix.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
What happens when you try to go into recovery?
And just so you know, it was your kernel that was causing the reboots. It is a known issue with cubed kernel that dsb is working hard to fix.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
It basically just reboots. It says "entering recovery" at the top of the HTC boot screen, then reboots immediately after that again and attempts to boot normal, it then goes into the droid boot animation and just hangs there.
cowprince said:
It basically just reboots. It says "entering recovery" at the top of the HTC boot screen, then reboots immediately after that again and attempts to boot normal, it then goes into the droid boot animation and just hangs there.
Click to expand...
Click to collapse
Try redownloading and reflashing the boot.img in fastboot. And if that doesn't work than flash a different recovery and see if that helps.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
Try redownloading and reflashing the boot.img in fastboot. And if that doesn't work than flash a different recovery and see if that helps.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Thanks Big, I was going to try it before I went to work this morning, but now it seems like the device is completely dead.
Will not power on and I get no lights when I attempt to charge it. I've tried multiple USB cables and charging methods, none result in any charging LED...
cowprince said:
Thanks Big, I was going to try it before I went to work this morning, but now it seems like the device is completely dead.
Will not power on and I get no lights when I attempt to charge it. I've tried multiple USB cables and charging methods, none result in any charging LED...
Click to expand...
Click to collapse
I should have been more clear there now that I've reread it, I never got the chance to try your suggestion, it's as if the battery died overnight and won't charge now.
cowprince said:
I should have been more clear there now that I've reread it, I never got the chance to try your suggestion, it's as if the battery died overnight and won't charge now.
Click to expand...
Click to collapse
Plug it in & Hold the power button down for about 15 to seconds for a hard reboot. If you can get it to boot, then try to flash the original stock kernal (link is located in dsb cubed kernel thread or here http://d-h.st/Ma1 ).
Once you flashed the original kernel flash dsb's other kernel stock cubed kernal here http://forum.xda-developers.com/showthread.php?t=2064066 . This one works real good, its basically stock but you can read/write and it has the hsic fix for a little better battery life.
You can use the stock cubed until the full cubed kernel is up and running with its fixes.
Hope this helps...
Jrocker23 said:
Plug it in & Hold the power button down for about 15 to seconds for a hard reboot. If you can get it to boot, then try to flash the original stock kernal (link is located in dsb cubed kernel thread or here http://d-h.st/Ma1 ).
Once you flashed the original kernel flash dsb's other kernel stock cubed kernal here http://forum.xda-developers.com/showthread.php?t=2064066 . This one works real good, its basically stock but you can read/write and it has the hsic fix for a little better battery life.
You can use the stock cubed until the full cubed kernel is up and running with its fixes.
Hope this helps...
Click to expand...
Click to collapse
Thanks Jrocker, I just hope I can get the thing to charge and/or boot when I get home.
Well it's not completely dead. Looks like I made it back into the bootloader. I can't seem to flash the boot.img file though:
fastboot flash boot boot.img
sending 'boot' (5412 KB)...
OKAY [ 0.839s]
writing 'boot'...
FAILED (remote: battery low)
finished. total time: 0.863s
So first thought would be, well ok charge the phone. However, I'm not so sure it's actually charging.
I have it plugged into the AC adapter while the bootloader is showing and it says FASTBOOT AC, however I see no solid orange LED telling me that the device is charging.
Also is there a way to push files to the SD card using fastboot. For example the stock kernel zip file?
OK I'm pretty sure I know what happened. Same thing has happened to me a few times. Apparently it only happens on some phones. I think the /data partition on your phone got borked. As in corrupted. It has done this to me about 3 times, each time I was running a custom kernel. Now that I know that my phone is one of the susceptible ones, I've been running DSB's stock system write kernel and have not had any issues since.
If this is the case, it sucks but the only thing you can do to fix it is to factory reset. When this has happened to me I have run fsck2 (disk checker) on my /data partition and it comes up with multiple errors and fixes them, but the phone still won't boot. I know dsb is aware of the issue, as are others, but there is no fix as of now besides either running stock kernels until it is fixed, or getting a new device (which may or may not be susceptible.) You can run fsck2 on your data partition and see if maybe it boots after fixing the errors, but I've had no luck 3 out of 3 times. Hope this helps.
EDIT: didn't realize that your recovery partiton got borked too, that's weird. Never had that happen. Reflash your recovery and then you should be able to go from there.
BotsOne said:
OK I'm pretty sure I know what happened. Same thing has happened to me a few times. Apparently it only happens on some phones. I think the /data partition on your phone got borked. As in corrupted. It has done this to me about 3 times, each time I was running a custom kernel. Now that I know that my phone is one of the susceptible ones, I've been running DSB's stock system write kernel and have not had any issues since.
If this is the case, it sucks but the only thing you can do to fix it is to factory reset. When this has happened to me I have run fsck2 (disk checker) on my /data partition and it comes up with multiple errors and fixes them, but the phone still won't boot. I know dsb is aware of the issue, as are others, but there is no fix as of now besides either running stock kernels until it is fixed, or getting a new device (which may or may not be susceptible.) You can run fsck2 on your data partition and see if maybe it boots after fixing the errors, but I've had no luck 3 out of 3 times. Hope this helps.
EDIT: didn't realize that your recovery partiton got borked too, that's weird. Never had that happen. Reflash your recovery and then you should be able to go from there.
Click to expand...
Click to collapse
So ultimately if I just do a factory reset and then restore one of my old backups after flashing the stock kernel boot.img I should be good then? Or should I still run fsck2?
cowprince said:
So ultimately if I just do a factory reset and then restore one of my old backups after flashing the stock kernel boot.img I should be good then? Or should I still run fsck2?
Click to expand...
Click to collapse
If you plan on restoring a backup there's no need to wipe. Recovery will wipe the data partition before it restores the old one. After that just flash your kernel and modules and you should be back up and running.
Fsck2 is not necessary. The only reason you might want to run fsck2 would be to:
1. verify that this is indeed your problem.
2.you have have a (slim) chance of fixing your data partition, saving you from wiping. Like I said I tried it and it did fix the disk errors, but still wouldn't boot.
Well it looks like I cannot do a restore of an old backup, I get an error saying that it can't mount /system
Am I doing this all in the right order?
reboot to bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
reboot to bootloader
reboot to recovery
factory reset
flash kernel
restore recovery backup
reboot
cowprince said:
Well it looks like I cannot do a restore of an old backup, I get an error saying that it can't mount /system
Am I doing this all in the right order?
reboot to bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
reboot to bootloader
reboot to recovery
factory reset
flash kernel
restore recovery backup
reboot
Click to expand...
Click to collapse
You might be able to fix that error by flashing a newer version of whatever recovery you are using. Not sure, never had that error. If you can't get your backup to flash do this (I'm assuming you already have a custom recovery installed/working since you tried to restore a backup)
1. reboot into bootloader
2. fastboot flash boot boot.img (dsb's stock kernel img)
3. reboot into recovery
4. factory reset
5. flash modules (dsb's stock kernel modules)
6. wipe cache and dalvik for good measure
7. cross fingers
8. reboot
If it doesn't boot after that I think I would reflash the rom and try again starting at step 4, but I think that^^ should do the trick.
Looks like I'm back in business, went ahead and flashed the stock system writable kernel and CWR, then the kernel module zip, a fresh ROM the Genome ROM and was good to go again.
However I still have one remaining problem. The wifi errors out and won't turn on.
cowprince said:
Looks like I'm back in business, went ahead and flashed the stock system writable kernel and CWR, then the kernel module zip, a fresh ROM the Genome ROM and was good to go again.
However I still have one remaining problem. The wifi errors out and won't turn on.
Click to expand...
Click to collapse
Glad to hear you're back up and running! Wifi not turning on is a telltale sign that you need to reflash your modules for whatever reason.
BotsOne said:
Glad to hear you're back up and running! Wifi not turning on is a telltale sign that you need to reflash your modules for whatever reason.
Click to expand...
Click to collapse
That's kinda what I had assumed.
Now I just need to hope for an AOSP ROM and some email widgets not bound to the Sense UI...
Actually no dice on the reflashing of the kernel modules. Maybe I should do the boot.img as well?
cowprince said:
Actually no dice on the reflashing of the kernel modules. Maybe I should do the boot.img as well?
Click to expand...
Click to collapse
U should do the boot.img 1st then boot into recovery and wipe cache/davik cache and flash the module. If u still having problems then get the stock DNA kernel
sent from my beastly powered viper DNA using Tapatalk 2