I am getting very upset because every rom I try to recover using CWM produces a problem. Im trying to restore different android version ROMs and I dont understand how can them be SO INCOMPATIBLE with each other, since the core should be compatible. I am always restoring to stock and even then the rom restore fail, usually indicated by the phone reseting the CWM to default recovery mode and I'm having to reinstall CWM over and over.. other times the ROM simple don't boot, get stuck in the Vibrant logo. This is insane, what are the restrictions for restoring a rom with CWM?? shouldn't it erase everything so no incompatibility is left? Is there differences in restoring with version 2 of CWM or a 3 version? I don't even know exactly what OS version some of the roms are, so that I could try upgrade the phone to that version first and then applying the restore. Nothing works, I'm very pissed.
Related
Hey guys, I'm hoping someone can help me out. I've tried searching the forums and using different methods to recover it, but none have worked so far.
SO I flashed the ICS Domination theme over Diet ICS rom, stuff was continuously force closing, so I factory wiped with the intention of re-flashing just the rom... after a reset the phone was stuck on the samsung boot screen.
I've tried using Odin to load the stock Rogers rom, it says it worked, but trying to boot the phone up its stuck on the samsung boot screen.
Am I missing something? Is there anything you guys can suggest I try??
use ODIN to flash a new recovery.img and restore from a nandroid
I didn't make a nandroid backup (i know, retarded), where can I get one and how can I push it to my internal memory considering the phone won't start up and I can't flash from external SD
While I did find a similar posts, they were for different devices. I also tryed to search o different sites for similar problems to no avial.
What Happened: After backing up system data and app data then removing Foxhound ROM with factory reset, and installing UltimaROM i came to find that the modem did not install correctly result in no connection to my cell network. I booted into TWRP recovery to try and do a re-install of the ROM only to find that TWRP was restarting itself every 3 seconds or so. I attempted to restart the device which i found to result in a TWRP bootloop that i cannot get out of, it constantly is booting into recovery mode and i cannot get it restart the OS.
What I've tried: Since i can get into download mode i decided to attempt to re-install TWRP using Samsung Galaxy S3 Toolkit but since i do not have USB debugging on i cannot do that. I'm mainly looking for a fix before i go and claim it on the warranty saying update went bad or something. If people need more information I will try to provide it as best i can.
Summery if i confused people is that TWRP is in a bootloop, i am unable to get to the OS, but i still have download mode available.
I fixed it but not how I would have liked to. I ended up losing all data due to flashing stock ROM using ODIN. I would still much appreciate a alternative method that does not involve loss of data though just for future reference, that is if anyone knows a alternative method.
Sent from my GT-I9300 using xda app-developers app
could've tried reflashing TWRP or any other recovery through odin
I have an LG Optimus Q (LGL55c) with twrp loop. I was trying to go back to stock rom, instead I deleted all the system files in twrp when it was working...Then I rebooted back into recovery and get the loop. Does this mean I completely bricked my phone? I tried using adb, adb shell doesn't work. It does find the device. Even tried the LG update with no sucess Any ideas or suggestions?
I just read the forum title, I thought this was for the Optimus Q not the Samsung S3. Sorry mods
Temasek unofficial cm12 5.02
I was running this rom when my power button shorted and I got it replaced but then I tried to do a complete wipe and clean flash but since then it has been twrp bootlooping, tried to flash the latest recovery through Odin but still doesn't work also tried stock firmware flash but says binary not available.
This is my secondary device and I've not been in touch with Odin for a while. Any help will be appreciated.
Thanks
Download latest firnware from sammobile.com and flash it with Odin, as described on sammobile: does Odin finish with '1 succeeded'?
I'm in a very similar situation, but with my Samsung Galaxy Note 2 (N7105). It's rooted, and I am, or was using TWRP 2.7.0.2. ROM is CyanogenMod 12, 5.0.2 Lollipop.
I did a factory reset from INSIDE Android, and chose to wipe internal memory. Phone did the reset and wipe, rebooted into TWRP instead of Android, and now I have TWRP boot loop.
I posted more about it here: http://forum.xda-developers.com/showpost.php?p=60247503&postcount=3671
I have the Problem toooo!
What must i do Now!
with my S3 is the same!!!
For posterity:
With an old (2014?) version of TWRP and a custom ROM, I tried reverting to factory settings. That caused the phone to reboot TWRP, and the screen would flash every couple of seconds. I flashed a stock recovery image I found on Google, and when it restarted again, the wipe was completed successfully. My intention was to wipe all user data anyways so I can't say if this method might save it.
My Samsung Note 10.1(N8000) got stuck on boot screen at stock. No recovery only download mode. I don't know why, it was flat for about 2 weeks before I noticed.
Roms always and still flash successfully if I get the right version of odin, i think i have about 15 different odins from trying to fix this.
Things I've tried:
1.Flash stock rom
2.Flash custom recovery
3.Flash different versions of both 7+
4.Re-partition and repeat 1-3
5.Wipe the memory and repeat 4 with many many roms
Does anyone know why my tablet stopped the first time and why no roms are working to recover it. What is happening here? Is it corrupt memory or motherboard etc hardware? Is there a god .pit file or god rom that could work to make something happen? What should i try now? I am willing to try anything as it cant get any worse.
This shows a successful flash which had no effect on the tablet afterwards
http://imgur.com/oQggzKY
my bad about the dodgy title wording
any help/ideas?
So I've got this issue I never had before.
It started happening after I screwed something up with the EFS I think.
I was flashing some custom roms after the 4.3 official update and then tried to go back to 4.1 official.
Had the no network problem, but fixed it flashing the vodafone stock 4.3 official again.
Reading all the stuff about EFS confused me, and I deleted the EFS folder and copied an old backup (or so I think, because I'm not sure. I had a EFS backup on my sdcard and extsd I think).
I no longer have the no network issue, but everytime I flash a stock rom through Odin the phone gets stuck at the samsung logo, so I have to root the phone and install TWRP using Odin and then wipe. I know this way fixes this, but what I'm looking for is to fixed the problem completely so I don't have to install a custom recovery or root after using Odin to go back to official samsung rom.
Any ideas?
What should I do?
Maybe the phone gets stuck at the samsung logo because all of this EFS thing, but, like I said, I no longer have the no network issue.
All I want is for the phone to boot normally into the setup after flashing a samsung rom using Odin.
It just gets stuck every single time since I had this problem with the EFS, when before this never happened.
try to install the rom in recovery mode
Sensamic said:
So I've got this issue I never had before.
It started happening after I screwed something up with the EFS I think.
I was flashing some custom roms after the 4.3 official update and then tried to go back to 4.1 official.
Had the no network problem, but fixed it flashing the vodafone stock 4.3 official again.
Reading all the stuff about EFS confused me, and I deleted the EFS folder and copied an old backup (or so I think, because I'm not sure. I had a EFS backup on my sdcard and extsd I think).
I no longer have the no network issue, but everytime I flash a stock rom through Odin the phone gets stuck at the samsung logo, so I have to root the phone and install TWRP using Odin and then wipe. I know this way fixes this, but what I'm looking for is to fixed the problem completely so I don't have to install a custom recovery or root after using Odin to go back to official samsung rom.
Any ideas?
What should I do?
Maybe the phone gets stuck at the samsung logo because all of this EFS thing, but, like I said, I no longer have the no network issue.
All I want is for the phone to boot normally into the setup after flashing a samsung rom using Odin.
It just gets stuck every single time since I had this problem with the EFS, when before this never happened.
Click to expand...
Click to collapse
I had this problem before (flash 4.1.2 in current 4.2.2 by odin), here's my solution.
Maybe you can install your ROM in recovery mode. (CWM based)
Remember to wipe completely before installing
枫叶の故事 said:
I had this problem before (flash 4.1.2 in current 4.2.2 by odin), here's my solution.
Maybe you can install your ROM in recovery mode. (CWM based)
Remember to wipe completely before installing
Click to expand...
Click to collapse
I can flash custom roms through TWRP, but what I'm looking for is to be able to do so again through Odin without ending up stuck at boot always and having to wipe through TWRP to be able to boot properly.
Any ideas?
I'm sure there must be a fix so I don't get stuck at the boot screen after flashing a samsung rom with Odin.
I know the trick wipe factory reset but what I really want is to simply avoid getting stuck at the boot screen after flashing a samsung rom with Odin.
Sensamic said:
Any ideas?
I'm sure there must be a fix so I don't get stuck at the boot screen after flashing a samsung rom with Odin.
I know the trick wipe factory reset but what I really want is to simply avoid getting stuck at the boot screen after flashing a samsung rom with Odin.
Click to expand...
Click to collapse
Factory reset is also available in default recovery as well, then what is the issue? Flash then boot to recovery do factory reset.
KSKHH said:
Factory reset is also available in default recovery as well, then what is the issue? Flash then boot to recovery do factory reset.
Click to expand...
Click to collapse
Thanks.
I'm just trying to find out why my SGS3 now gets stuck at boot when before it never happened.
I'm hoping there's a way to fix it and go back to before, when it never got stuck at boot. There should be a way I guess.
Hi everyone
My sister updated her MEGA OTA last month. She cant remember which version she was on. I am assuming it was 4.3. shes doesnt know much,
Her phone got stuck in bootloop.
Initially a got a hard time even getting into restore mode. however after a lot of goggling and trials and errors here is where i am today :
1- I can install TWRP and/or Philz recovery and boot into them.
2- I can enter download mode
3- I have tried installing many ROMS and different versions. I was only partially successful with 4.4 versions because I get a passed message in Odin however upon restart the phone enters boot loop again.
4- I have tried multiple wipe data/dalvik cache/cache and restoring factory settings but i still get the same results.
5- Only in Philz recovery i can mount the external SD card and copy zip files. I was able to root the phone that was (but im not sure if it still is). However all ROMs zip files I tried to install (both from PC and from extSD card) wouldnt open in recovery mode.
Because I get a passed message when I install a ROM from Odin , I dont know what the issue could be. But there is something wrong that happens as soon as this phone boots up.
I seriously do not know what to do anymore. I just need this phone to be working again. At this point I dont care about warranties/ROM versions/stock or custom...
Please help and sorry for my bad English
It sounds like you need to download the stock rom and flash it in Odin (you gotta put the phone in download mode to flash in Odin). The stock rom can be found on the sammobile website in the firmware section. That should get you back to square one (stock rom, stock recovery, no root). Then you start over from scratch.
Sent from my SGH-M819N using XDA Free mobile app
Thanks
I did and I still get the same problem.
In fact after installing stock rom, i could not enter "stock" so I installed philz recovery, logged in philz and wiped cache a couple of time, did a factory reset.
and yet when i restart , the phone is stuck in bootloop.
Maybe she has a Galaxy Mega with a repaired screen. Starting with 4.4 Samsung only supports a digitizer with Synaptics brand chip. It's a big mess and there are countless screens and digitizers made worthless. I think unofficial 4.4 by Cyanogen and others might work, but not official Samsung. With some Galaxy Megas you get a bootloop. With others it boots however the digitizer and touch functions no longer work. I don't know how to go back after you are on official 4.4 because last I saw, there was no root for it. If I'm wrong, someone else please clarify and continue to help.
IMHO only one way out from such situation is try to flash MegaFire MJ2 which is derived from stock 4.2. It's only one 4.2 ROM which can be safely flashed onto KK.
Iformation about MegaFire you can find HERE