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
Related
Hi I hope someone can help me. I have searched this forum but could not find a similar situation to what I ended up in...
I tried to install a custom ROM on my Galaxy Tab 10.1 using the CWM/Odin.
This seemed succesful but was not, it did not start but was stuck in the Samsung logo.
So I tried entering the CWM and download and install an original Samsung ROM. I can get it into CWM, but CWM cannot enter the download mode only the other mode.
In this mode all options are available:
- reboot
- apply update from SD card
- wipe data/factory reset
- wipe cache partition
All options have been tried without any luck. In the update from SD card it only shows ...
or Error opening /data/media: no such file or directory
Any ideas how I could get this directory back or put a ROM on the Samsung in this situation.
Odin does see the Galaxy but as I cannot get it into Download mode I am unable to download anything to it.
All or any suggestions are very welcome!
1. CWM (Clockworkmod) =! Odin.
In the beginning, you don't have CWM installed. You install CWM, by flashing CWM on your Phone with odin.
Odin is the Windows Programm, that is used to flash Recoveries/ROM's/Kernels onto your device.
2. it seems, that you still have the default Samsung recovery installed, that meand CWM is not yet flashed on your device.
If the flashing process was succesful (I suppose it was done with odin), but you can't get past the Samsung logo, that means, you probably flashed a rom, that isn't made for your device(ex. a GTab 10.1v Rom).
If you DID flash a wrong rom, then you probably ****ed up the partition table and removed the Download Mode(Odin Mode). Strange thing is, that you still have the Stock recovery.
Could you please redirect us to the rom you downloaded?
Also, did you flash with a repartition on and/or a .pit file?
hi Kaukassus,
thanks for the reply.
OK I checked the files and what I did.
I think I totaly screwed this up. It was a theme I tried to install the AOSP_HC_v1.3_3G+KI1.
I rooted the Tab. So first when the Tab was still functioning installed it on the TAB via USB.
Than tried to install this via update from SD card.
This appeared to work initially. But hung at the start.
After that I tried (via Power Volume Up) wipe data/factory reset.
No luck.
After that I tried wipe cache partition followed by wipe data/factory reset.
And this is what I got now..
Bad news is the Tab was/is a X-mas present and I managed to screw it up even before I officially got it !-(
The valuable lesson you're learning is that you need to be aware exactly what things you're flashing and their compatibility with your device and the software it's running.
You haven't mentioned what specific device you're using or the specific things you've tried to flash (as kaukassus pointed out, direct links to threads where you got the files you tried to flash are best). Not sure if you're aware but not all GT 10.1's are equal; there are several models out there and each and every ROM is specific to a particular device. Verizon LTE GT 10.1's like mine can't take ROMs from any other device for example, it's likely that the new T-Mobile 4G one's wont be able to trade ROMs with Verizon ones . . you get the point.
When you say you installed via USB what exactly did you mean? If you simply copied a zip file via USB to the tab to flash in recovery mode that's not installing; the flashing from recovery may be but the file copy operation is not. If on the other hand you pushed things via ADB or you flash using Odin software then that's a different story.
Best thing to do at this point is to properly identify your device, look for a stock recovery image for Odin and flash that via Odin to your device. At that point you can start from scratch again to build what you want.
Thanks Muzzy996.
You are right. I was in a rush and should have taken more time.
However I am getting somewhere. Managed to get in download mode twice today, don't ask me how. This Tab just will not go into download mode!
However I did not have the stock ROM ready to be installed.
Will keep you updated.
i have the same problem. i just rooted my device was going to overclock. decided to save my rom with rom manager. saved it device went to reboot now the samsung galaxy 10.1 shows up screen goes dim then shuts off, and will cont. do this. i can get into download mode but recovery will not work. is there anyway to download my stock rom. im using verizion 4g 10.1 any help would be great, btw sorry to thread jack
Problem solved.
Managed to get it in download mode again and install stock rom via Odin.
Appeared to work fine. But kep switching off, even after full night of charging.
This morning Tab was dead after recharging whole night..
Got it back on by holding volume down and power button down.
i found a stock rom and im trying to upload it via odin, however odin does not find my tab? any ideas. btw congrats on getting ur tab back
I crashed both my I9000 (galaxy s) flashing custom roms and my tab 10.1 (editing some system files) both ended up just looping but managed to get both back. I purchased a small connector of ebay £1.59 that has just a resistor accross pins 4&5 331k I think anyway plugging this into most samsung devices boots them into download mode. Even before getting my resistor I managed to get things working I think that you'd have to be properly unlucky to really brick a samsung I've flashed both my devices with all sorts of crap with my little resistor I just reset them with ease.
Brian
h2bmess said:
i found a stock rom and im trying to upload it via odin, however odin does not find my tab? any ideas. btw congrats on getting ur tab back
Click to expand...
Click to collapse
did you ever resolve this issue? i am currently faced with the same issue.
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.
So I have a Sprint Galaxy Mega and it seems as though it may be semi-bricked. It will not boot past the GALAXY MEGA logo. It will just continuously power cycle to and from that logo. If I attempt to put it in recovery, it will say "RECOVERY BOOTING" in blue letters as usual, then power cycle right back to the GALAXY MEGA screen. It will boot into Odin mode and accept Odin files, but after attempting do do a typical "stock Odin" scenario, nothing has changed. I looked around for the Pit but cannot seem to find it. Does anyone has a reliable link to the latest Odin stock restore and the PIT file that matches it?
Maybe an error with your system data. So you can't reboot into recovery ? If you can try to wipe data and cache and reboot.
It may be an abnormal re-partition when flashing stock rock, and then I can't help you (have the i9205 international model). Some members of this section have the Sprint version, try to send them a PM if nobody can help you
Nope, no recovery. I was considering flashing a custom recovery to it to see what it does but I don't wanna kill the phone any more than it already is...
Yes I understand. But flashing custom recovery can solve your problem, only if you can boot on it. I think it can't make more damages to your phone, he just always stuck on boot phase like a brick, but if you don't want to try, wait for a developer making you a PIT file. More safe, the Galaxy Mega have a too poor development support for risk anything...
Well I went ahead and flashed TWRP to it. It will boot into TWRP just fine. Tried flashing the stock L900 ROM zip and it still won't boot.
Well I installed a custom ROM, SlimKat, and the phone boots. If I install the stock ROM located in the following link, OP's signature, the phone goes right back to bootlooping. ???
I need either the stock ROM or a ROM with dialer codes because this phone will be flashed to a regional carrier.
what recovry version you use bro. maybe recovery problem. try use your custom rom to flash another recovery from philz. the latest one. some time recovery dont work properly to downgrade from 4.4.2 to stock 4.2.2.
Great, so with Philz Touch Recovery, I never had problems for downgrade and I do this often for testing roms. Now it should not bootloop if you reflash stock.
I am using "CWM-based recovery 6.0.4.7"
I will try Philz recovery
After trying Philz recovery to flash the stock file I found, it once again bootlooped. Is there another stock ROM floating around somewhere or possibly a custom ROM that has dialer codes such as ##3282# enabled?
No idea... But actually the most complete stock based custom rom is MegaFire I think. Flash V5 (not V5x !) it should be enabled.
I don't see what is the problem while flashing stock rom... Oh ! Maybe you haven't enabled USB Debugging, I forgot to do that one time and I had some issues, in case you try to flash a firmware where Knox or others features are on with a modem without these, may cause bootloop. I've searched for 2 days before solve that little problem...
Have you tried another firmware ? If you can flash custom rom, something went wrong before flash... Odin folder is complete ?
Strange...once again a boot loop after flashing the MegaFire ROM
I'm almost certain I need the PIT file. I cannot find it anywhere.
Well I got the phone to boot from that rooted stock ROM FINALLY. I don't remember for sure but I think what I did was first flash TWRP, then flashed boot.img.tar that I found somewhere, it was listed for the Sprint Mega. I then booted into TWRP and flashed the stock rooted ROM(zip) I mentioned before. It now boots perfectly and everything works except one tiny little detail. No WiFi, no cellular signal at all. Baseband version: unknown in About phone.Already tried flashing the Sprint stock modem from the same download link as the ROM and it didn't work.
I'm having the same problem too dude, I
I download n flash all.the firmware I could find online, since I have no idea what the country of origin is. But most of them work, but no WiFi, Bluetoothand the sim card slot don't read
VirtueToVice said:
Well I got the phone to boot from that rooted stock ROM FINALLY. I don't remember for sure but I think what I did was first flash TWRP, then flashed boot.img.tar that I found somewhere, it was listed for the Sprint Mega. I then booted into TWRP and flashed the stock rooted ROM(zip) I mentioned before. It now boots perfectly and everything works except one tiny little detail. No WiFi, no cellular signal at all. Baseband version: unknown in About phone.Already tried flashing the Sprint stock modem from the same download link as the ROM and it didn't work.
Click to expand...
Click to collapse
Hello dear community
This is my very first thread I am making on this website, so please pardon me if I am on the wrong page of this website.
Anyways, I'm more or less desperate. I saw a youtube tutorial on how to install Android 4.4 Kit Kat on a Samsung Galaxy Note N7000 and I heard I'd need root AND a custom recovery.
Because I'm a total newbie to this kind of stuff, I tried the very first thing I saw that had something to do with custom recovery, because I already had my phone rooted. So, I looked up a tutorial on youtube on how to install CWM custom recovery and ended up with installing it successfully, but now my phone is stuck in a bootloop. As I already mentioned, I am a newbie and therefore I am very desperate at the moment, you know.
The only thing I can do is go to Recovery Mode, but if I try to turn the phone on it gets stuck in a bootloop (It actually doesn't loop at all, it just freezes at the moment when the Samsung Galaxy Note logo appears and doesnt do anything after that.).
I think my problem is that I actually threw a new Kernel on my phone, because the video title says "How to install Kernel with CWM [...]"
I would be very very very very very grateful if anyone was kind enough to help me get out of this!
I really need help!
Thanks!
PS.
If this helps you help me:
This happened when I had Android 4.1.2 installed.
There's going to be 2 ways to get out of this:
1) Reinstall the stock firmware via Odin.
2) Install a custom rom via recovery.
Personally, I'd go with number 2 because a) you wanted to update anyway and b) if you have the right recovery and rom, it'll be easier as you can just put the files you need on an external SD card and install via the custom recovery. Now, not all recoveries are able to flash any file. Many times you need specific ones to install the newer android versions. So, if you are wanting to install something 4.4 based, then using a recovery that was made, say, last year, probably will not work well if at all.
Another thing to try first, is to wipe the cache and dalvik cache in recovery since you said you tried to install a kernel. It is always recommended to wipe these when installing (assuming you did pick a compatible kernel with what you were trying to install).
Hello everyone,
I own a samsung galaxy s2 gt-i9100 I've been using it for a long time. A few days ago i installed cynogenmod 13 marshmallow on it but faced some severe issues like dialler problems,battery drain,google play services not working. So, i switched it back to my previous rom i.e. cm 12.1 lollipop but my old twrp recovery got replaced by cynogenmod default recovery. Now some people who may have used it know that its very basic and does not has backup,restore, has bugs,does not flashes some zips or files that i wanted so i tried to replace it with twrp/cwm through rashr,flashify,rom manager,etc. But none of it worked, whenever I'd boot after flashing the twrp/cwm recovery it'll go back to the default cynogenmod recovery. Now, me not knowing what im doing stupidly downloaded mobile odin lite app then i downloaded the cwm kernel recovery kitkat compatible and installed via mobile odin lite. After that it got screwed, it won't just startup it'll just start and go into recovery i mean continuously! It was annoying, then i read an article on a forum to download any cm nightly or stable mod and flash it but i did a little bit of tweak of removing the recovery boot img file with twrp to get preinstalled twrp recovery but i gotta admit it was the last mistake possible. Now i sit here, with a bricked phone in my hand which is looping continuously only on the samsung logo. If anyone out there can assist me correctly it'll be a life saver for me. Thanks for reading this and please reply with a solution asap. Please! Im in danger!
can you get into download mode?
if yes you can download a stock firmware and flash but you will have to hope it will work, otherwise you will get stuck on nand write start which means the nand is stuffed/corrupted and then basically only a motherboard replacement will do the job, or you can try using another computer, reinstall usb drivers..
can you get into recovery mode?
if you can, you can flash a rom
The 'nand stuffed' assumption is a last resort, tried everything and nothing works assumption. There is *plenty* to try before assuming that the nand is 'stuffed'......
It sounds like (from your description) that you may have rendered recovery useless and inaccessible.
I've a feeling what you need to do is to go into download mode and Odin flash a firmware.
Even if it doesn't boot, you should have a recovery that you can flash PhilZ recovery from and then use that to flash a custom rom. Initially, I'd stay away from the MM builds and instead flash something KK or LP based as they're less 'volatile' and have a higher degree of stability than the MM roms.
http://i.imgur.com/rVnFwJM.jpg