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.
Hi Everyone! just a rookie here in need of a bit of advice.
I'm a Galaxy S II I9100 owner and have my phone rooted and all setup with custom roms and been comfortable with flashing for some time now. My ROM of choice recently was Vanilla Rootbox and have to say the ROM has been fantastic with very few bugs to report. Last night i recieved the OTA update via Goo Manager for Vanilla Rootbox 3.4. I downloaded the full update over wifi and flashed with all wipes no worries. Next step was to flash the latest GAPPS and i figured there would be nothing wrong with flashing the GAPPS zip i had on my sd card that i had downloaded the last time i was notified of a GAPPS update via Goo manager as well. After flashing, wiping everything and rebooting again. My phone then booted up to a series of dialog boxes indicating that many google processes had stopped functioning. apps.google.com etc etc. A similar error has been reported in the Vanilla Rootbox thread by another user but i wasnt able to report this bug their either because my post count is too low to post in a development forum. So after seeing this error i rebooted into recovery to flash my last backup but CWM recovery came back with an error messaging stating it couldnt mount either ext or int sdcard. i did a factory reset which made no difference to the problem whatsoever. I then downloaded ODIN and the latest stock ICS Rom and flashed it via ODIN with no reported errors. My phone now boots through the optus boot animation and is stuck at the Galaxy S 2 screen with the flashing red and yellow animation over the S. If i turn off the phone with the power button, the phone turns off and immediately starts again and gets stuck at the flashing s screen. I've taken the battery sim and ext sd card out and put it all back in only for the problem to persist.
If anyone could help me there's a donation and my thanks in it!
Much appreciated
Nick
tried to re flash another stock ROM?
If so, tried factory reset the phone after the flash?
As long as you can get to DL mode, you are good to keep on flashing till you are up & running.
And then you got this
Remember to update your kies and make sure you close it all up before flashing with odin. If you are in 4.0.4 beware of the brick bug.
gastonw said:
tried to re flash another stock ROM?
If so, tried factory reset the phone after the flash?
As long as you can get to DL mode, you are good to keep on flashing till you are up & running.
And then you got this
Remember to update your kies and make sure you close it all up before flashing with odin. If you are in 4.0.4 beware of the brick bug.
Click to expand...
Click to collapse
Kies has never been installed on this computer but i did use the usb drivers mentioned in the soft brick recovery guide you linked. I used some information from the guide to flash this stock rom but i couldnt flash or wipe the partition because im unsure where to get the .PIT file required? i cant get past the boot animation so no factory reset possible and yes i can still get into download mode!
darkstar117 said:
Kies has never been installed on this computer but i did use the usb drivers mentioned in the soft brick recovery guide you linked. I used some information from the guide to flash this stock rom but i couldnt flash or wipe the partition because im unsure where to get the .PIT file required? i cant get past the boot animation so no factory reset possible and yes i can still get into download mode!
Click to expand...
Click to collapse
wow wow, leave pit files alone for now, they are nasty.
What stock ROM did you flash? 4.0.4 or 4.0.3?
You can factory reset via recovery mode.
Try installing kies anyway, it can't never hurt. Just make sure all applications are closed before you re-flash.
here's jb leak, might help:
http://www.sammobile.com/2012/11/15/i9100xxlsj-%E2%80%93-galaxy-s-ii-android-4-1-2-jelly-bean-test-firmware/
Right so i flashed I9100XWLP8 stock rom (4.0.3). Just then i flashed Siyah Kernel and attempted to use the factory reset function in recovery there, i get a message down the bottom mentioning that it can't mount my internal SD.
darkstar117 said:
Right so i flashed I9100XWLP8 stock rom (4.0.3). Just then i flashed Siyah Kernel and attempted to use the factory reset function in recovery there, i get a message down the bottom mentioning that it can't mount my internal SD.
Click to expand...
Click to collapse
Tell me your:
Model
Firmware
Country
Carrier
Always mention this
try flashing jb leak (ROM, modem & kernel package).
Hello,
I recently made some mistakes with my Galaxy S2 GT-i9100 while following this a tutorial on Galaxys2root.com (Can't link to the precise article because this is my first post) I flashed the CWM recovery tool linked by this website to my device through the latest version of Odin and afterwards my phone would not turn on. I was able to get into the Clockwork recovery mode however but couldnt install anything because I had forgotten to place any ROMS on my device beforehand. To try and resolve the problem I did a factory reset in the recovery mode but this did not effect anything. I am now unsure what to do next. I would still like to root my phone so that I cant get rid of all the bloatware put on it by Orange mobile as well as update my phone to Kitkat(Currently running Android 2.2) Can someone tell me what I have done wrong and what is the next step for me to take?
Thank you for any help that you can offer
the kernel you flashed it is the problem
ZK1990 said:
Hello,
I recently made some mistakes with my Galaxy S2 GT-i9100 while following this a tutorial on Galaxys2root.com (Can't link to the precise article because this is my first post) I flashed the CWM recovery tool linked by this website to my device through the latest version of Odin and afterwards my phone would not turn on. I was able to get into the Clockwork recovery mode however but couldnt install anything because I had forgotten to place any ROMS on my device beforehand. To try and resolve the problem I did a factory reset in the recovery mode but this did not effect anything. I am now unsure what to do next. I would still like to root my phone so that I cant get rid of all the bloatware put on it by Orange mobile as well as update my phone to Kitkat(Currently running Android 2.2) Can someone tell me what I have done wrong and what is the next step for me to take?
Thank you for any help that you can offer
Click to expand...
Click to collapse
is this site you are talking about:
http://galaxys2root.com/cwmtwrp-recovery
im guessing that is the problem(Installing CWM/TWRP recovery will most likely break the ROM you are running currently as it overwrites the ROM’s KERNEL).
If iam right,that means you have to flash another kernel,i suggest Siyah kernel 2.6.14 its for gingerbread version(it has CWM recovery and auto-root):
http://forum.xda-developers.com/showthread.php?t=1263838
after that you can flash the KK rom you want through CWM .
Hello, first post here and I am hoping you guys will be able to help me.
I have here a SII that will only access download mode. I have tried re-flashing it several times with various Odin flashable files all of which returned a "Pass" but still would not allow me to pass the first "Samsung" screen. The files I have flashed include Clockworkmod, TWRP, and the stock UMCD8 firmware with and without pit file.
Is there any other option left short of replacing the motherboard?
You should be able to boot the phone after performing a wipe data/factory reset from within recovery. To enter recovery, hold all three buttons (vol+ vol- & pwr) continuously until the boot screen appears the second time, then release all three. You can perform a wipe data/factory reset from stock 3e recovery, or from a custom recovery, depending on which you have, it doesn't matter. That being said, you success will depend perhaps on what you flashed. I am assuming by ClockworkMod and TWRP you mean I-777 kernels containing those recoveries, as the I-777 does not have a separate recovery because the recovery is built into the kernel. If the kernel version does not match the system version (UCMD8 is Jelly Bean) then the phone would not boot even after a reset. But you could flash the full I777UCMD8 again, and then it should boot. If you have additional questions or issues, let us know.
creepyncrawly said:
You should be able to boot the phone after performing a wipe data/factory reset from within recovery. To enter recovery, hold all three buttons (vol+ vol- & pwr) continuously until the boot screen appears the second time, then release all three. You can perform a wipe data/factory reset from stock 3e recovery, or from a custom recovery, depending on which you have, it doesn't matter. That being said, you success will depend perhaps on what you flashed. I am assuming by ClockworkMod and TWRP you mean I-777 kernels containing those recoveries, as the I-777 does not have a separate recovery because the recovery is built into the kernel. If the kernel version does not match the system version (UCMD8 is Jelly Bean) then the phone would not boot even after a reset. But you could flash the full I777UCMD8 again, and then it should boot. If you have additional questions or issues, let us know.
Click to expand...
Click to collapse
Retried flashing the I77UCMD8 using odin 1.83 but it still wont boot. I also realized that when I try to access recovery it doesn't actually shut down, but gives me a black screen from which it will reboot if left for approximately five minutes. Is there anyway to get access to adb, like perhaps flashing a. insecure bootloader or something?
Berthfield said:
Retried flashing the I77UCMD8 using odin 1.83 but it still wont boot. I also realized that when I try to access recovery it doesn't actually shut down, but gives me a black screen from which it will reboot if left for approximately five minutes. Is there anyway to get access to adb, like perhaps flashing a. insecure bootloader or something?
Click to expand...
Click to collapse
Since you get a pass in Odin when you flash the full UCMD8 distribution, you should be able to get into recovery. Pull the battery for at least 30 seconds, then put the battery back into the phone and hold all three buttons continuously until you see the Samsung logo appear, the screen to go black, the Samsung logo appear a second time, and the screen to go black a second time, then release all three buttons.
If this does not boot the phone into recovery mode, then please describe in detail in your next post exactly what happens when you follow this procedure.
And, if the phone will not boot into recovery, then I will need additional information in order to troubleshoot the issue further. You have not given much information about the phone. What is the history of the phone before the problem manifested? Has this been your phone since new, or did you get it from another user? What was it running before the problem. Exactly what happened when the phone stopped working. Are you an individual trying to get his personal phone going, or a business trying to fix a phone to sell? Give me as much information as you can possibly think of.
creepyncrawly said:
...
Click to expand...
Click to collapse
On a side note, very honored to have issued your 3,001 'thanks'. I swear you should have triple that amount, due to the quality and depth of help you've given to the community - and continue to do so.
creepyncrawly said:
Since you get a pass in Odin when you flash the full UCMD8 distribution, you should be able to get into recovery. Pull the battery for at least 30 seconds, then put the battery back into the phone and hold all three buttons continuously until you see the Samsung logo appear, the screen to go black, the Samsung logo appear a second time, and the screen to go black a second time, then release all three buttons.
If this does not boot the phone into recovery mode, then please describe in detail in your next post exactly what happens when you follow this procedure.
And, if the phone will not boot into recovery, then I will need additional information in order to troubleshoot the issue further. You have not given much information about the phone. What is the history of the phone before the problem manifested? Has this been your phone since new, or did you get it from another user? What was it running before the problem. Exactly what happened when the phone stopped working. Are you an individual trying to get his personal phone going, or a business trying to fix a phone to sell? Give me as much information as you can possibly think of.
Click to expand...
Click to collapse
Okay. I am a student who repairs phones part-time, I am not new to the android platform or to the galaxy line however this is the first I am experiencing this particular problem.
This phone is a unlocked and refurbished device that was purchased recently by my cousin. He claims he was just installing an app when it shut down and refused to boot back up. I initially took it with the intentions of wiping the data and returning it, however I was unable to access the recovery menu.
As I had no idea what rom was on it before, other than the fact that it was a samsung original, I proceeded to trying to flash various recoveries hoping that one would load from which I could install a custom rom. Failing that I then went on to flashing the I777UCKH7 firmware which also failed to boot and/or access recovery. Unsure what to do next I then attempted to flash the I777UCMD8 firmware which also did not boot. I then made a second attempt at flashing the I777UCKH7 firmware and .pit file from your download repository which also failed to boot.
All were loaded using Odin versions 1.82, 1.83 or 1.85 (Mostly 1.85). They all returned a "Pass" status but would be stuck on the "Samsung" screen when they rebooted. It was at this point having run out of ideas that I made the O.P.
I have also tried leaving the battery out and then following your instructions for recovery, when I do so I get a black screen. If i leave it in that screen for some time (approximately 5 mins) it will reboot and again be stuck on the "Samsung" screen.
We appreciate that you aren't new to the android platform or to the galaxy-line. Regarding the i777, you are in good company, and if we know NOTHING about any other device, we know the i777 very well. We're here to help.
You mentioned that you flashed several recoveries to the device. For future reference, the recovery for the i777 is packaged with the kernel, and is not installed separately. Even the often-troublesome temporary flash-recoveries that can be found, are actually a kernel/recovery combination. The s959g (straight talk's s2) has the same partition layout as the i9100 and i777 (and several other s2's), and DOES use a separate partition for recovery.
The fact that desktop ODIN indicates PASS when the flash is complete tells us that all of the factory nand images flashed successfully (including boot). It is very common that the device needs to have the factory data reset even after the factory images have been installed via desktop ODIN, but of course that requires access to recovery. If after a successful factory flash, the vol+ & vol- & power button held-concurrently-until-recovery (<--while NOT plugged into a USB port) truly doesn't get you to recovery, then that would be a new one for me as well; all other signs (as you have stated them) point to a correctly functioning device.
I'm hesitant to point you to flash a custom kernel;
there's some unnamed part of the procedure affecting the process, and flashing another boot image won't be helpful
-or-
there's a hardware failure, and flashing another boot image won't be helpful
-or-
you're using an incorrect method to get to recovery, and flashing another boot image won't be helpful
If you want to try it anyway, custom_kernel_twrp_v2.7.1.0.tar file via desktop odin might be worth a try.
^^this will trip the flash counter
^^this will install any custom firmware, but will not boot anything below android 4.4.x
I apologize for the hijack @creepyncrawly
Berthfield said:
Okay. I am a student who repairs phones part-time, I am not new to the android platform or to the galaxy line however this is the first I am experiencing this particular problem.
This phone is a unlocked and refurbished device that was purchased recently by my cousin. He claims he was just installing an app when it shut down and refused to boot back up. I initially took it with the intentions of wiping the data and returning it, however I was unable to access the recovery menu.
As I had no idea what rom was on it before, other than the fact that it was a samsung original, I proceeded to trying to flash various recoveries hoping that one would load from which I could install a custom rom. Failing that I then went on to flashing the I777UCKH7 firmware which also failed to boot and/or access recovery. Unsure what to do next I then attempted to flash the I777UCMD8 firmware which also did not boot. I then made a second attempt at flashing the I777UCKH7 firmware and .pit file from your download repository which also failed to boot.
All were loaded using Odin versions 1.82, 1.83 or 1.85 (Mostly 1.85). They all returned a "Pass" status but would be stuck on the "Samsung" screen when they rebooted. It was at this point having run out of ideas that I made the O.P.
I have also tried leaving the battery out and then following your instructions for recovery, when I do so I get a black screen. If i leave it in that screen for some time (approximately 5 mins) it will reboot and again be stuck on the "Samsung" screen.
Click to expand...
Click to collapse
cyril279 said:
I apologize for the hijack creepyncrawly
Click to expand...
Click to collapse
On the contrary, your input is valuable and desired.
@Berthfield,
If there was actual nand damage in any partition that was flashed, you would not get a pass in Odin, as far as I know. Since you are unable to boot into any recovery, this indicates a problem with the nand memory, possibly a corruption issue. Please try the following (you might try accessing recovery after each step, and if you get to it, perform a wipe data/factory reset):
Instructions to clear nand read/write corruption. Instructions are specific; do them in order, and don't skip.
Odin3 v1.85 is recommended.
1) Download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA. Without ticking Re-Partitioning
2) Flash the Tar.md5 of the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
3) If that is successful you are done. If it is not, then:
4) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning. (Please observe normal bootloader flashing caution.)
5) Flash the Kernel, as in step 1.
6) Flash the full stock Gingerbread distribution, as in step 2.
I was away from home for a bit and so was unable to work with the phone. I have followed the instructions given above but I am still unable to boot.
I was using the "I777UCKH7-REV02-home-low-CL503881.tar.md5" file downloaded from the download repository, is this the right file or is there another Gingerbread flash that wold be better to use?
I am really puzzled at what exactly is happening with this phone.
Yes, that is correct. That is the original stock gingerbread from when the phone was first released.
I agree that it is a puzzle. Just to be sure, you followed the directions exactly? I'm not sure why, but the sequence will clear nand read/write corruption. You might try once again with the SBL -> Siyah Kernel -> Full Gingerbread, just to make sure.
1) Flash the SBL by itself and pull the battery.
2) Flash the Siyah kernel by itself and pull the battery.
3) Flash the full Gingerbread stock and pull the battery.
4) Enter recovery and perform a wipe data/factory reset.
5) Reboot.
creepyncrawly said:
Yes, that is correct. That is the original stock gingerbread from when the phone was first released.
I agree that it is a puzzle. Just to be sure, you followed the directions exactly? I'm not sure why, but the sequence will clear nand read/write corruption. You might try once again with the SBL -> Siyah Kernel -> Full Gingerbread, just to make sure.
1) Flash the SBL by itself and pull the battery.
2) Flash the Siyah kernel by itself and pull the battery.
3) Flash the full Gingerbread stock and pull the battery.
4) Enter recovery and perform a wipe data/factory reset.
5) Reboot.
Click to expand...
Click to collapse
Did the above and it is still a no go.
I have come to realize that the phone seems to think it is in recovery mode when I attempt to enter it as if it is plugged in while on the black screen it doesn't display the charging animation. This occurs regardless of the kernel/recovery combo that is on the phone and while in that state it is also not detected by the computer. To rule out possible problems I have also attempted the flash on a different computer with a different cable and it is still the same.
I remember reading about the ICS hard-brick bug and that it was possible to brick the phone is a large enough file was written to memory. Is it possible that this could be my problem or would Odin return a error if the chip was damaged? Also I am not sure if this matters but I find it odd that after flashing the Siyah kernel and CWM the phone still hasn't tripped its custom binary counter.
Berthfield said:
Did the above and it is still a no go.
I have come to realize that the phone seems to think it is in recovery mode when I attempt to enter it as if it is plugged in while on the black screen it doesn't display the charging animation. This occurs regardless of the kernel/recovery combo that is on the phone and while in that state it is also not detected by the computer. To rule out possible problems I have also attempted the flash on a different computer with a different cable and it is still the same.
I remember reading about the ICS hard-brick bug and that it was possible to brick the phone is a large enough file was written to memory. Is it possible that this could be my problem or would Odin return a error if the chip was damaged? Also I am not sure if this matters but I find it odd that after flashing the Siyah kernel and CWM the phone still hasn't tripped its custom binary counter.
Click to expand...
Click to collapse
Evidently, this situation is beyond my experience.
My understanding is that if emmc memory is damaged within a given partition, then Odin will not be able to successfully flash that partition. While I don't know exactly how Odin functions, I believe there are checks within the flashing sequence for each partition. So as stated before, it is assumed that if you get a pass in Odin, there is not emmc damage, at least not within the various partitions that Odin flashes.
There was one case I remember with the emmc super brick bug where the phone would boot, but would not function correctly. Evidently in that case, a small portion of the emmc memory was damaged. The usual symptom of that bug was a hard brick.
The charging issue could be hardware or it could be a failing or failed battery. Have you tried another battery?
Flashing the Siyah kernel and not tripping the flash counter is more than a little odd. The code that governs that behavior is in the secondary boot loader as far as I know, and you have reflashed that. Please bear in mind that anything I say is speculation, but this issue give me a lot of reasons to think it is a failed hardware issue.
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