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
Related
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.
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
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 currently running safe strap 3.65. Been flashing roms for quite a while but always left the stock slot alone. I'm wondering if there were any real down sides or things to be careful about when flashing a custom rom/kernal to the stock slot. There's the obvious, that a rom wouldn't work and I would have no working roms, but i'm not worried about that as I could easily flash another. Thanks in advance.
Also wondering. I did a backup of stock but it doesnt exist now! And flashed cm10.1.3 and it won't boot.....
Sent from my SCH-I535 using Tapatalk
Does anyone know how to install CM 10.1.3 or 10.2 to stock slot? I tried it, but it won`t boot. I had a stock slot with root and safestrap enabled, then i wiped stock slot in safestrap. After that my phone didn`t do anything, it seems that safestrap has deleted itself while wiping stock slot. So i had to restore my system with RSD Lite.
I did exact same thing. I even backed up before flashing and then the back up dissappear or didn't actually back up
Sent from my SCH-I535 using Tapatalk
It works now. Installed Stock with RSD lite, rooted it, installed SS3.65 and did a wipe cache, data and factory reset. Then i installed CM 10.2, Avatar rom 4.3 over stock system. Then i installed Gapps and JBX kernel 1.5. It is running great.
Just wanted to update this since I hadn't received any responses about the actual pros and cons. I decided to jump right in and do it and see what happened. Here's what I did.
SafeStrap 3.65:
Activate stock slot
wipe: cache, dalvik cache, android secure, data, system
repeat (I always repeat this step to be sure everything is clear)
Flash CM11 12/15 Nightly
Flash PA Gapps
Flash WiFi Access Point Patch
Flash JBX 2.0 Kernal
Wipe Cache and Dalvik Cache
Reboot.
Everything works perfectly on stock slot.
Sent from my Nexus 10 using xda app-developers app
I prefer to leave the stock side alone for a couple of reasons. I like to always have it there as a fall back boot option. Also, if you have to delete ROM slots and are down to the option of having none left, you need to be able to activate the stock slot so that you can delete the last slot.
Seems the biggest pro for flashing over stock is saving storage space.
Sent from my XT912 using Tapatalk
moparfreak426 said:
I did exact same thing. I even backed up before flashing and then the back up dissappear or didn't actually back up
Click to expand...
Click to collapse
Is the Backup maybe on the SD card and you searching in the internal storage, or other way round?
Just set it completely stock, rooted and deleted everything for **** and hdmi so annoying hdmi quits popping up forcing landscape mode
Sent from my SCH-I535 using Tapatalk
How did you wipe system and your safestrap still works? If i wipe system, safestrap wipes itself and the recovery stops working after the wipe, phone is bricked. Only RSD helps fixing it
Einheit-101 said:
It works now. Installed Stock with RSD lite, rooted it, installed SS3.65 and did a wipe cache, data and factory reset. Then i installed CM 10.2, Avatar rom 4.3 over stock system. Then i installed Gapps and JBX kernel 1.5. It is running great.
Click to expand...
Click to collapse
Lol, I made a thread a long while ago, and that was my exact setup that I posted in that thread...
Einheit-101 said:
How did you wipe system and your safestrap still works? If i wipe system, safestrap wipes itself and the recovery stops working after the wipe, phone is bricked. Only RSD helps fixing it
Click to expand...
Click to collapse
Using 3.73 / 3.75 I no longer have this problem. 10 out of 10 times
Lol never tried with 3.73/75 but i dont use the XT910 anymore so i dont care anymore about this. Just waiting for a Root exploit for my new Droid Maxx.
guys im trying to fix my friends phone whici is samsung galaxy s2, heres what he did, he was on cynogen mod and then directly went to another rom without changing the bootloader and then he change it again to kitkat rom hoping it would fix things now what i did was first fix the bootloader cause im trying to restore its backup which is the original os 4.1.2 i was able to enter cwm which is 6.0.2.7 now i was able to restore the backup but still on bootloop. any tips?
rarela1234 said:
guys im trying to fix my friends phone whici is samsung galaxy s2, heres what he did, he was on cynogen mod and then directly went to another rom without changing the bootloader and then he change it again to kitkat rom hoping it would fix things now what i did was first fix the bootloader cause im trying to restore its backup which is the original os 4.1.2 i was able to enter cwm which is 6.0.2.7 now i was able to restore the backup but still on bootloop. any tips?
Click to expand...
Click to collapse
Wipe data
Sent from my GT-I9100 using xda premium
Flash stock sammy rom with odin.
If wiping data doesnt work, try flashing kernel. If that doesn't work, flash stock 4.1.2 via odin
Sent from my SGH-I317 using XDA Premium 4 mobile app
i just installed the stock firmware which is 4.1.2 and then tried wipe but theres a message in the system recovery says failed to mount /efs? any clue? thanks in advance.
flash latest philz kernel from here http://forum.xda-developers.com/showthread.php?t=1877270 ,boot to recovery,then restore your efs backup from there(you should have one in your external sd)
Sent from my blazing fast Note 2, running MIUI 5x and pleasantly surprised by it.
just installed philz kernel and went to recovery im searching for restoring the efs but cant find it though. still on bootloop.
i think this phone has other problem already tried 3 different stock firmware for this phone and then go to recovery wipe still on bootloop. tried installing kernel from philz its desame but only thing i noticed is every time i installed a new rom and go to recovery is says failed to mount efs. can it be one of the reason why its on boot loop? and also my friend didnt back up his efs thats why i think this is happening.
do you have a nandroid backup of any previous rom?
yup he has nandroid backup which has on the stock rom but i doubt cause when i installed the stocked rom then installed philz cwm which was 6.0.2.7 i was able to restore the back up but its still on bootloop so i dont know if the cwm is the ones not compatible or the rom.
after you restore your backup do a factory reset in cwm.
now i tried what you said and its showing md5 mismatch when i try to restore.
could be a corrupted backup.did you tried factory reset on your current rom?
argghh im on the blink on giving up on this phone already tried different methods.............
assuming you're now on stock 4.1.2,i suggest you to flash dorimanx 8.43 kernel,,if it doesnt boot,reboot to recovery,do a factory reset.If that doesnt help,try to restore nandroid from this cwm.Of course before restoring do a factory reset and format system and preload partitions.
ayt will try this now!!!
still no luck not working T_T..
you mean you can't restore your backup?And dont forget to wipe cache and dalvik cache when doing factory reset.As for efs,did you looked for it in internal sd too,in clockwork folder?It can be either in tar.gz,img.gz or zip formats.It's stuck at boot probably because of corrupted efs partition.If I remember well,you can restore efs partition from nandroid backup in philz touch cwm.
Have you done a stock samsung rom install usin odin? That should get you back to sqaure 1. If your backup is currupt it will never work.
Sent from my SGH-I317 using XDA Premium 4 mobile app