So after flashing the newest, full firmware, i tried rebooting to recovery and experienced countless bootloops and a loss of recovery.
I of course fastboot flashed a new recovery and adb sideloaded a rom and set up the new rom, but why did this happen??
It would wipe if you had stock recovery. But it doesn't explain the reboots. It happened to me that I lost recovery when I was flashing schatka and got into bootloops and screen flickering but I didn't loose any data.
Sent from my HTC6435LVW using xda premium
Yeah, I had twrp. This makes no sense. It was a full day after flashing new firmware, random.
Was the ROM you used to flash, stock or rooted? If it was a stock ROM, did you flash it in your custom recovery? If so, that would have been your issue. If not, then its possible you had a bad download. Make sure to do MD5 matches.
Just a few ideas.
Sent from my HTC6435LVW using xda app-developers app
No, i flashed newt's nos 106 but that was a week before the firmware
Related
Hey guys.
I'm on LA4 and i want to flash a custom ROM onto my SGS2.
I treid CM7 (flashed is twice) and som other ROMS but everytime i flash it, i get in a boot loop.
I hope i'm doing it the right way?
I copy the .zip file to my sdcard and press "install zip" in the recovery mode.
Did you wipe data/cache/dalvik before installing the rom? It's pretty much important, especially if you're going from LA4 to CM7
yea,sure!
before and after the flashing i wiped all
Edit: Also try format /system after you wipe the 3 said above.
Try going back to your stock image and flash a stock KERNEL afterwards, boot CWM, flash a stock image, when done, flash a stock kernel and newest radio.
I'd say it might be a kernel issue. I had it when I flashed MIUI, and in reverse when I flashed back to others..
Sent from my Galaxy Nexus using xda premium
Try avoiding wiping it afterwards. Just wipe everything out, flash it and immediately reboot.
I also hope you did a nandroid backup as well. If you did that and it still boot loops, try restoring it and going back to it and having another go.
oh my gosh i figured it out!
CuraeL, you're right.. its a kernel problem
i have to flash the kernel again after the rom update.. weird but only that way it's working!
thanks
No worries. I have had to do it on a lot of the roms I installed myself, on my SGS II, back in the days. Wonderful phone, a bit weird the way the whole kernel thing is made. But I suppose that's cause the kernels are written for 2 different "builts" of the system.
Keep it in mind, as you might need to do it again some day, lol.
Have fun. ^^
Hey All,
I had been having troubles with 4.0.3 multi-dpi, so I thought I'd flash Saurom. I flashed this, but upon reboot, I got stuck at the samsung screen. It never went past there, just sat there forever. So, I went back into cwm (holding down vol up/vol down/power), and wiped everything again, and tried to flash saurom again, but same thing happened.
I then tried to flash back to 4.0.3 multi-dpi, with same results. I can get into CWM just fine, but it seems any rom I flash hangs at the samsung boot screen.
Does anyone have any ideas? Right now I'm completely down :/
Thanks in advance for any assistance,
Sebastian
Hi sounds like a bad kernel flash.i would go into cwm, do the usually wipes, go to mounts and storage. Format data. Format system. Format cache only. Pull battery. Install any of the odin install Roms through download mode, That should fix your problem. Then you can start over and flash whatever Rom you want
Sent from my SAMSUNG-SGH-I717 using xda premium
You should restore the latest good backup you created before you flashed whatever is giving you problems.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Just a reminder, when you go to mounts and storage, do not fformat sd storage, this will wipe everything in your memory of your phone
Sent from my SAMSUNG-SGH-I717 using xda premium
A backup restore should do the trick.
-Once you go NOTE, you'd say 4 inches a Joke
Worse comes to worse you can flash stock Odin. If you one clicked for ICS, remember to flash bootloader first
Sent from my SAMSUNG-SGH-I717 using XDA
From my gathering, Saurom & ICS 4.0.3 DPI are incompatible. Meaning you can't flash one on top of the other without doing a full wipe data/factory reset. Having said that, I think the best move then would be to flash back to stock via ODIN, install cwm, redownload whatever ROM to your ex sd card, mount system & data then re-flash.
Shdowalker said:
From my gathering, Saurom & ICS 4.0.3 DPI are incompatible. Meaning you can't flash one on top of the other without doing a full wipe data/factory reset. Having said that, I think the best move then would be to flash back to stock via ODIN, install cwm, redownload whatever ROM to your ex sd card, mount system & data then re-flash.
Click to expand...
Click to collapse
I "believe" all you need to flash through Odin is the GB bootloader, then you can flash GB roms, the ICS bootloader is what causes the hang up with ROM incompatibilities
Sent from my SAMSUNG-SGH-I717 using XDA
Be sure the ROM has the radio load and remember a Nandroid does not flash the radio load. That has to be done manually.
VonEsch said:
I "believe" all you need to flash through Odin is the GB bootloader, then you can flash GB roms, the ICS bootloader is what causes the hang up with ROM incompatibilities
Sent from my SAMSUNG-SGH-I717 using XDA
Click to expand...
Click to collapse
I'm not very familiar with Saurom but from what I've read I think that's correct. ICS needs a clean slate to operate from is all I was saying.
Just bought a used phone off Swappa. It has TWRP and had Cyanogenmod installed.
I wanted to try a TouchWiz ROM so I downloaded one. Booted into recovery, made a backup to external SD Card and then flashed the ROM. It said it flashed
successfully but when rebooted, it just stayed at the Samsung Galaxy S4 Boot
screen.
I tried restoring the backup, but it failed!
I thought I might have had a bad download so I downloaded Cyanogenmod nightly and LiquidSmooth on my laptop, transfered to the SD card, popped it into the S4, boot into recovery, and tried flashing each, and both just boot to the boot screen and freeze.
What are my best options now? I saw some guides for flashing back to stock via Odin, but requires that I know if I am on VRUAME7 or VRUAMDK and I don't know. Could I have been on ME7 and running Cyanogenmod? Doesn't seem possible, no?
Me7 ota doesnt have the ability to flash custom recovery or rom, so no you werent on that beforehand. Whenever you flash a rom you need to do a wipe/factory reset and wipe caches, unless op states you can dirty flash. Doing some reading will only help you out, generally every post outlines the installation process. Boot to recovery do your wipes then try booting again. If your still in a bootloop then you will need to flash mdk via odin then start the rooting and romming process over.
Sent from my SCH-I545 using Tapatalk 2
Man, I thought I did everything right.
First, did a backup.
Then full wipe with TWRP full wipe, including cache.
Then flash ROM
I'll have to get familiar with Odin and find the MDK images.
Sometimes that happens. Could have been a bad download then it happens more often then you would think. If theres an md5 hash posted its a good idea to verify the download is good. In the dev section theres no wipe mdk images posted so you wont lose your already installed apps and data.
Sent from my SCH-I545 using Tapatalk 2
So I downloaded the factory image and flashed via Odin, but accidentally flashed via bootloader rather than PDA. It wouldn't start - still hung at the boot screen, so I re-flashed via PDA and it is still hanging at the boot screen.
Now I don't know if it is just the same problem as before, or if I messed something up with flashing through bootloader. Can I reflash something via the bootloader section of Odin to restore it?
What version of twrp? And try to go back into recovery and wipe cache and dalvik.
That worked for me on the buggy version of twrp when it wouldn't booy
Sent from my SCH-I545 using Tapatalk 2
twiz0r said:
What version of twrp? And try to go back into recovery and wipe cache and dalvik.
That worked for me on the buggy version of twrp when it wouldn't booy
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Not sure what version it was because it's now back to factory recovery. I did go back into it and did a factory wipe and it booted!
I'm facing a weird issue: when i try to flash via odin a stock rom my phone bootloops, but when i flash an aosp or a cm via recovery or restore a previous backup of them it works just fine. Nothing major, since now, but I wanted to go back to stock to get more battery. Then I'm asking: anyone has an idea about this problem, or faced and solved this before?
TIA
Did you wipe data before flashing?
Sent from my GT-I9300 using Tapatalk 4
I always do.
The only reason I can think of that a stock rom via Odin bootloops is lack of data wipe. Perhaps your wipe needs to be more thorough, using megawipe or something
Sent from my GT-I9300 using Tapatalk 4
flashed wanamlite through cwm, booted fine, now trying with odin stock
Factory reset from stock recovery should sort it, but will wipe your phone including internal sd
Just as the title says.
Here is the series of events that led up to this.
Picked up a Moto X yesterday and am giving the phone to my father. I factory wipe, clear data and cache, and also format data via TWRP. Install a copy of CleanROM 1.6 Odex on there since that has been my most stable ROM to date. Boots up fine after installation, so I reboot into recovery to create a backup of the ROM for him in case he does anything that messes it up. Go to reboot the phone after a successful backup and the phone hangs at the Galaxy S4 bootscreen.
This is where I'm at now. I have tried everything that I can to get the phone to boot up, and the only thing that will work is to do a data format again and a fresh install. That's all well and good, until I reboot the phone and then it goes right back to not booting. I never took the ME7 update or applied an ME7 ROM. Is there a way to fix the data partition issue that I believe I'm having? Is my only option to Odin back to stock?
What version of twrp are you using?
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
jd1639 said:
What version of twrp are you using?
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
2.5.0.2 I believe. What is the best version to use? It doesn't matter too much at this point since I ended up using ODIN to flash back to stock and re-rooted. I do want to install a custom ROM for him though. What version of TWRP is the best?
Check out this thread - similar issue solved.
http://forum.xda-developers.com/showthread.php?t=2325911
I had the same issue a while ago and fixed it like you did. Others are saying to "fix permissions" in TWRP
after wiping data.:good: