I tried flashing the Droid DNA Cubed Kernel 2.4.2, but forgot to flash the modules before rebooting. When the phone loaded up, all I got was a black screen with a title bar that would restart when I tried to unlock. I then restarted, flashed the modules, and I continued to get the same black screen. I even tried flashing back to the stock kernel with no luck. The only thing that fixed it was doing a factory reset. I had rooted stock with an unlocked bootloader. I didn't see mention of a required factory reset, so what went wrong? Thanks.
I'm not sure what went wrong, and factory reset is not required.
How did you flash the kernel?
I flashed the boot.img from fastboot, then installed the modules in TWRP after the blackscreen.
StormChaser46 said:
I flashed the boot.img from fastboot, then installed the modules in TWRP after the blackscreen.
Click to expand...
Click to collapse
That's normally what I do but I flash the modules before booting, which is how it should be done.
Exact same thing happened to me. I did the factory reset and started from the beginning again. It really scared me but now I have actual root access with superSU having no issues. So much happier now.
Anyways, the point is. If you mess that step up, just factory restore and do it again... The right way lol
Sent from my HTC6435LVW using xda app-developers app
Just flashed back to stock kernel from Flash Image GUI because I kept getting crashes/restarts on cubed, and no black screen this time. Not sure what the problem was, just hope it doesn't happen again lol.
StormChaser46 said:
Just flashed back to stock kernel from Flash Image GUI because I kept getting crashes/restarts on cubed, and no black screen this time. Not sure what the problem was, just hope it doesn't happen again lol.
Click to expand...
Click to collapse
So you did a factory reset and tried cubed again but still didn't work?
It did work after a factory reset, but I got crashes/reboots out of nowhere. I saw other people were also reporting occasional crashing, so I'll stick with stock til it's a little more stable.
Understandable, I get a random hangups every other day or so and it restarts... But the pro's outweigh the cons imo. But I agree with you as well .
Coming from a DX, I got used to random reboots here and there after rooting hahah
Sent from my HTC6435LVW using xda app-developers app
Related
Hi all
I'm not new to flashing but I'm new to flashing cm7.
I odin back to stock jfd eclair. Root and Install CWM 2.xxx. I downloaded the stable cm7 and I started flashing. (after I wipe data/cache of course)
IN recovery, it said finding package, opening package, then my phone processed a series of lines and reboot automatically. On the startup, it says VIBRANT SAMSUNG, then GALAXY S CYANOGEN(mod) then the same recovery screen with many lines. It moved too fast into another reboot I couldn't read what was on the screen. And it kept doing this for quite 10 mins now.
Is it normal? if not, what did I do wrong? I can get into download mode and odin back to stock but I did it last night and I couldn't think what i did wrong.
Please help!
Hmmmm..... seems a bit wierd, try going into recovery and wiping and reinstalling with a new download.
Sent from my Nexus S 4G using XDA App
stumpyz9 said:
Hmmmm..... seems a bit wierd, try going into recovery and wiping and reinstalling with a new download.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
No i don't think its a bad dl. I checked md5. I'm odin back to stock again now.
wavestar92 said:
No i don't think its a bad dl. I checked md5. I'm odin back to stock again now.
Click to expand...
Click to collapse
Try reflashing cwm when your rooted, may have not flashed right
Sent from my Gewgle Phone via XDA App
This happened to me also, I went directly back to recovery, 3 button, and reflashed. Worked the second flash for some reason.
Thanks. I turn it off, get into recovery again, and re flash it successfully
Same exact thing happened. I have no idea how many time I odened back to stock trying to figure it out.
I did as you guys said, as soon as that loop began, pulled the battery and got back into recovery. flashed again and worked just fine!
same thing happened to me...i got back into recovery...i noticed cwm updated to 5.0.2.8 then i reflashed and all good...when i tried to flash at first. cwm was 2.5 ..maybe thats the issued it wont flash on that...has to be cwm 5.0
anyway getting ready enjoy some cm7 on my vibrant...
Hi guys. So here's my problem. I recently tried to update my phone to the latest version of NRG's Energy Rom using CWM. In the process I did a factory data wipe, and wiped the dalvik cache. I then flashed the rom as normal, but when I rebooted all I got was the white screen with the green HTC logo. It refuses to go any further. I can still get into recovery if needed, and I've tried a ton of different things, but to no avail. Anybody have any ideas as to what I need to do or is this thing hosed?
The phone is S-ON at the moment with an unlocked bootloader.
Any help is appreciated.
Mr.Moo52 said:
Hi guys. So here's my problem. I recently tried to update my phone to the latest version of NRG's Energy Rom using CWM. In the process I did a factory data wipe, and wiped the dalvik cache. I then flashed the rom as normal, but when I rebooted all I got was the white screen with the green HTC logo. It refuses to go any further. I can still get into recovery if needed, and I've tried a ton of different things, but to no avail. Anybody have any ideas as to what I need to do or is this thing hosed?
The phone is S-ON at the moment with an unlocked bootloader.
Any help is appreciated.
Click to expand...
Click to collapse
Flash the wipe script, flash the rom you wanted, when the phone boots up, let it sit for a few minutes, like 10 should be good.
Well I'll be damned. I could have sworn I tried that, but there we go. Thank you so much for the help.
Mr.Moo52 said:
Well I'll be damned. I could have sworn I tried that, but there we go. Thank you so much for the help.
Click to expand...
Click to collapse
Also, get rid of CWM and use 4ext recovery. It's in the dev section... And its the preferred recovery by most amaze users. I have a thread in Dev section
It allows you to flash kernel automatically when flashing ROM, that way you don't have to use a kernel flasher. Plus many other features.
Sent from my HTC_Amaze_4G using Tapatalk 2
Thanks for the info. I've been looking at recent posts and it seems I'm behind on a few things, including getting s-off.
Weird Problem
I had the same problem but I don't want to lock and re-unlock my bootloader. And this has never happened but my CWM Recovery isn't working. I didn't use 4ext bc this happened last time with that recovery. Is there any way to find the wipe script to use it from fastboot?
Tried kernel flashing; re-flashing recovery...second time this happened with s-on on speed rom
Had to re-wipe phone and re-flash everything...Got it working again! Weird problem though?!?!
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
Has anyone else had a boot loop problem with the new V of TWRP?? I'm running SOAv3 ROM and had ZERO problems, upgraded my twrp and had about a dozen restarts and freezes and then when I tried to boot into recovery, it boot looped. Fixed it with ODIN, then tried installing it fresh, and got the same thing. Went back to my older version and things are fine once again just wondered if this is isolated or just a known bug??
Yes its a know issue right now go back to the previous working version of twrp and wait for it to get fixed.Also be sure to check big Biff's twrp page before trying to update again to make sure everything is good.
Sent from my SGH-I717 using xda premium
Just update from Padawan V8 to SOA build 3. Was skeptical for a day or so but finally did it last night. Was just about to update to the New TWRP, thank fully I read through all those pages before I did, I usually don't. Saved me a head ache except I forgot to wipe cache's before installing the GAPPS, going to have to re-do that I believe to get the new camera functions from what I've read.
Demmonnixx said:
Just update from Padawan V8 to SOA build 3. Was skeptical for a day or so but finally did it last night. Was just about to update to the New TWRP, thank fully I read through all those pages before I did, I usually don't. Saved me a head ache except I forgot to wipe cache's before installing the GAPPS, going to have to re-do that I believe to get the new camera functions from what I've read.
Click to expand...
Click to collapse
you are correct Sir.....wipe caches and re-flash gapps.....g
psycoartwork said:
Has anyone else had a boot loop problem with the new V of TWRP?? I'm running SOAv3 ROM and had ZERO problems, upgraded my twrp and had about a dozen restarts and freezes and then when I tried to boot into recovery, it boot looped. Fixed it with ODIN, then tried installing it fresh, and got the same thing. Went back to my older version and things are fine once again just wondered if this is isolated or just a known bug??
Click to expand...
Click to collapse
How did you fix with odin? I can't get mine into the download mode to connect to odin. it just keeps boot looping?
whitebrw said:
How did you fix with odin? I can't get mine into the download mode to connect to odin. it just keeps boot looping?
Click to expand...
Click to collapse
Hold volume down and power ...it will go into download mode
Sent from my SGH-I717 using xda app-developers app
thanks but no thanks, when i do that it does the same thing as any other way of starting, just loops.
check out my post if you want.
http://forum.xda-developers.com/showthread.php?t=2202663
Fixed but I have no idea how or why. If any can explain I would appreciate it.
I was on TWRP and flashed Hyperdrive which caused me to Boot loop at the Samsung screen. I then tried to restore my backup which failed. I then went through and wiped all the data and tried a different rom (Clean rom) this caused boot issues too.
I ODIN using factory image which still boot looped. I then went into recovery ( i lost TWRP when I odin'd) and wiped everything and still boot looped. I wiped everything again 3 times and this time I was able to get into my stock rom.
I am confused with is happening inside the phone that caused the boot loop and why I still had boot loops even after a ODIN restore.
SuperKerp said:
Fixed but I have no idea how or why. If any can explain I would appreciate it.
I was on TWRP and flashed Hyperdrive which caused me to Boot loop at the Samsung screen. I then tried to restore my backup which failed. I then went through and wiped all the data and tried a different rom (Clean rom) this caused boot issues too.
I ODIN using factory image which still boot looped. I then went into recovery ( i lost TWRP when I odin'd) and wiped everything and still boot looped. I wiped everything again 3 times and this time I was able to get into my stock rom.
I am confused with is happening inside the phone that caused the boot loop and why I still had boot loops even after a ODIN restore.
Click to expand...
Click to collapse
sometimes it just takes a little while. was it actually looping or just stuck there? Ive had to wait 10 minutes before it actually got passed that screen.
Yeah, you probably just didn't wait long enough...
Sent from my SCH-I545 using xda premium
theidoctor said:
sometimes it just takes a little while. was it actually looping or just stuck there? Ive had to wait 10 minutes before it actually got passed that screen.
Click to expand...
Click to collapse
nfederic said:
Yeah, you probably just didn't wait long enough...
Sent from my SCH-I545 using xda premium
Click to expand...
Click to collapse
Wow, 10 minutes? Yeah ok, I definitely didn't wait that long before. I started to freak out a bit when it started resetting continuously. I thought the waiting would be just sitting at the boot screen and then when my restore failed the worst things were going through my head.
I am having the same issue after I reinstalled hyperdrive v6 where do I wait 10mins at?
My bootlooping starts at the language selection screen do I wait 10mins at the installation page?
Fixed it.... it was the Walkman player.
i have the answer!!
dont install any of the audio hacks and also dont install the walkman musci player just use the samung one ... peace!!!!!