hey guys,
i dun think thr is a similar thread regard my issue, here is a picture of what i get when i stuck at login screen for very long, decide to flash stock rom using ODIN and i did.
After which it boots to system recover and this is what it shows.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
helpppppppppppp
Identical to mine, gave up on it, sds
Sent from my SM-N910G using Tapatalk
Does it go to this after the flash with Odin or whenever you go into recovery
Sent from my Moto G using Tapatalk
ramien said:
hey guys,
i dun think thr is a similar thread regard my issue, here is a picture of what i get when i stuck at login screen for very long, decide to flash stock rom using ODIN and i did.
After which it boots to system recover and this is
helpppppppppppp
Click to expand...
Click to collapse
looks like partition table corrupted. reflash stock rom with CORRECT pit file may help (DO IT AT YOUR OWN RISK)
For me, I couldn't flash with Odin no matter what I tried, can't remember the error but essentially odin couldn't even begin the process.
I have flashed 100s of times previously with Odin too, so it really is kaput once this sds happens.
Yes, this is symptom of corrupted partition table, or at least it means the partition table is not as needed by stock Samsung firmware. Most (all?) 3rd party recoveries cause this; they are ok with custom rom but cause problems with stock (other great symptom is you can make nand backup of stock but it will be unusable after restore).
Solution is to again use odin, this time with pit file and stock image. I have done this a few times, no problems.
tonymy01 said:
For me, I couldn't flash with Odin no matter what I tried, can't remember the error but essentially odin couldn't even begin the process.
I have flashed 100s of times previously with Odin too, so it really is kaput once this sds happens.
Click to expand...
Click to collapse
try another usb port, those on the rear are preferred usually. if it fails, connect to another pc
I tried two computers, with SDS Odin will not be able to flash no matter what you try(trust me,I tried multiple different pit,f/w downloads).
Sent from my SM-N910G using Tapatalk
tonymy01 said:
I tried two computers, with SDS Odin will not be able to flash no matter what you try(trust me,I tried multiple different pit,f/w downloads).
Sent from my SM-N910G using Tapatalk
Click to expand...
Click to collapse
looks like u have to find a way to access the phone via adb and repartition yourself
ykkfive said:
looks like u have to find a way to access the phone via adb and repartition yourself
Click to expand...
Click to collapse
Stock recovery gives nearly no options in adb shell, and thanks too not being able to mount anything, is next to useless. Research about SDS, once a phone is in this state due to SDS, it is not recoverable.
Sent from my SM-N910G using Tapatalk
ykkfive said:
try another usb port, those on the rear are preferred usually. if it fails, connect to another pc
Click to expand...
Click to collapse
yeah for me it took ages to figure out it was usb ports.
wait for odin to detect. start. fails. new usb port. same thing. back to the old one. try usb3.0. try 2.0. try 1.0 etc. was a nightmare
also make sure u install drivers for usb
Do you used 1.9 extra space partition ? See here http://forum.xda-developers.com/showthread.php?t=2773758
In that case, try to load the stock pit via Odin.
yeah it can go to odin still, but after flashing stock roms, its still the same, when it goes to recovery, it shows all that. =( someone help pls?
so which PIT file to be used? there is so many out there =\
ramien said:
so which PIT file to be used? there is so many out there =\
Click to expand...
Click to collapse
I've attached a zipped pit for 16GB GT-N7105. I've used it, it's fine.
btw, after trying out different recoveries I found that the only one that has worked reliably on my GT-N7105 is twrp-2.8.7.0-t0lte.img.tar (version number is probably unimportant, that just happens to be the latest). It has to be installed using odin. Both cyanogen and cwm recovery images (such as cm-12.1-20151024-NIGHTLY-t0lte-recovery.img or recovery-clockwork-touch-6.0.4.1-t0lte.img) have left me with partition table problems which became apparent on trying to return to stock samsung.....which is why I needed the pit file and why I know it's good.
TWRP has been excellent and also let me root stock samsung in a simple way (normal supersu.zip or even just from the prompt in the recovery) instead of needing CF-Auto-Root-t0lte-t0ltexx-gtn7105.zip.
Anyway I hope the pit is suitable (you do have a 16GB device?) and that you get it all fixed.
i tried to use ODIN, PIT with the twrp file, it fail.
helppppppppppppppppppp
It is SDS, there is no software recovery at this point,I have tried everything.
Sent from my SM-N910G using Tapatalk
julian67 said:
I've attached a zipped pit for 16GB GT-N7105. I've used it, it's fine.
btw, after trying out different recoveries I found that the only one that has worked reliably on my GT-N7105 is twrp-2.8.7.0-t0lte.img.tar (version number is probably unimportant, that just happens to be the latest). It has to be installed using odin. Both cyanogen and cwm recovery images (such as cm-12.1-20151024-NIGHTLY-t0lte-recovery.img or recovery-clockwork-touch-6.0.4.1-t0lte.img) have left me with partition table problems which became apparent on trying to return to stock samsung.....which is why I needed the pit file and why I know it's good.
TWRP has been excellent and also let me root stock samsung in a simple way (normal supersu.zip or even just from the prompt in the recovery) instead of needing CF-Auto-Root-t0lte-t0ltexx-gtn7105.zip.
Anyway I hope the pit is suitable (you do have a 16GB device?) and that you get it all fixed.
Click to expand...
Click to collapse
tonymy01 said:
It is SDS, there is no software recovery at this point,I have tried everything.
Sent from my SM-N910G using Tapatalk
Click to expand...
Click to collapse
SDS is stuck SDS can load to home page, mine is not SDS. i still can go ODIN and go recovery page, just that when i factory reset, it shows errors.
any new solutions guys? Devs? i love you, please help me..
ramien said:
i tried to use ODIN, PIT with the twrp file, it fail.
Click to expand...
Click to collapse
1st thing: don't use pit with twrp or other recovery. Pit is for use with ROM image, typically stock ROM.
Ignore the guy who keeps injecting "SDS" every other reply. It is just noise.
So be calm and start over.
Plan A:
Make sure your phone has at least 75% battery, if possible.
Start Odin.
Put your phone in Download Mode and connect to Odin in the usual way.
Check the Re-Partition box and select your pit file.
Check the PDA box and select your Original Samsung Firmware. NOT your TWRP recovery image.
Odin will take a minute to check the PDA image. When that is done then press Start and be patient. Very patient. Do not disconnect your phone before completion. When Odin shows "Pass" in green box then you can disconnect.
Power down the phone. It won't boot yet.
Boot to Recovery (Volume Up+Home+Power buttons)
Choose "wipe data/factory reset" and proceed.
Next Choose "wipe cache partition" and proceed (actually I am sure that "factory reset" includes "wipe cache" but anyway, no harm in doing it twice).
Now "reboot system now".
Be patient. Very, very patient. It could even take 15 minutes to start the first time.
If the above doesn't help then it's time for.....
Plan B!
Plan B is the same except you are going to be brave.
Back to Odin:
Check the Re-Partition box and select your pit file.
Also select "Nand Erase All"
Check PDA and load Samsung firmware
Proceed as described in Plan A complete with rebooting to recovery and performing factory reset and so on.
I have done this myself. It worked. Ignore the people who have some religious-type terror of checking re-partition and nand erase boxes. This situation is what those boxes are for.
Once the NAND flash is dead from SDS, it really depends on which part of the flash is no longer readable or writable as to the symptoms. But you can keep trying, you never know..
Sent from my SM-N910G using Tapatalk
Related
So I had my GS3 rooted using tookit and I was running FreeGS3 on it for a while. I wanted to try a nightly of CM10 so I got everything ready. So I wiped everything entirely including the ROM of FreeGS3 installed, and flashed CM10. It said it failed. I tried to reboot the phone to the homescreen, but after that it just got stuck. So I pulled the battery out, and now its stays stuck at the Samsung logo. I can't get into recovery mode, but I can get into download mode. Only thing is, I have no way to turn on USB debugging. Pleeeeeeease tell me there is something I can do!!!
rickjs said:
So I had my GS3 rooted using tookit and I was running FreeGS3 on it for a while. I wanted to try a nightly of CM10 so I got everything ready. So I wiped everything entirely including the ROM of FreeGS3 installed, and flashed CM10. It said it failed. I tried to reboot the phone to the homescreen, but after that it just got stuck. So I pulled the battery out, and now its stays stuck at the Samsung logo. I can't get into recovery mode, but I can get into download mode. Only thing is, I have no way to turn on USB debugging. Pleeeeeeease tell me there is something I can do!!!
Click to expand...
Click to collapse
It didn't boot because u wiped the ROM. And didn't replace it. You can't boot to a system that isn't there. I assume u didn't do a nandroid which would help here. I.doubt you messed up recovery if dl mode is fine. Should still be able to boot to it using vol+up home and pwr. Cm10 probly failed Cuz it was corrupt. Either DL a new ROM n flash in recovery or DL the stock tar and flash in odin
Stock tar for Odin http://www.hotfile.com/dl/161492098/9fa8372/L710VPALEN_L710SPRALEN_SPR.zip.html
Odin http://samsung-updates.com/Odin307.zip
billard412 said:
It didn't boot because u wiped the ROM. I assume u didn't do a nandroid which would help here. Cm10 probly failed Cuz it was corrupt. Either DL a new ROM n flash in recovery or DL the stock tar and flash in odin
Click to expand...
Click to collapse
Yeah I know that's why it didn't boot, and unforunately no, I didn't make a backup. I really should have. Do I need to have USB debugging enabled to use ODIN? Because like I said, I can't turn USB debugging on since I can't get into the phone's settings.
rickjs said:
Yeah I know that's why it didn't boot, and unforunately no, I didn't make a backup. I really should have. Do I need to have USB debugging enabled to use ODIN? Because like I said, I can't turn USB debugging on since I can't get into the phone's settings.
Click to expand...
Click to collapse
No there is no debugging in DL mode cuz there's no system to debug. Reboot to DL mode and plug it in. Then load tar in PDA slot and flash.
billard412 said:
No there is no debugging in DL mode cuz there's no system to debug. Reboot to DL mode and plug it in. Then load tar in PDA slot and flash.
Click to expand...
Click to collapse
OH WOW, Thank you so much man! I'm sure it seemed like a stupid question but I honestly thought I just lost a phone! I'm so very grateful :highfive:
rickjs said:
OH WOW, Thank you so much man! I'm sure it seemed like a stupid question but I honestly thought I just lost a phone! I'm so very grateful :highfive:
Click to expand...
Click to collapse
Not that I'm very experienced, but it would seem that for the most part, if you can get into download or recovery mode, then your phone is probably fine. But that's just from my personal experience.
Sent from my SPH-L710 using xda app-developers app
Wearespacepeople said:
Not that I'm very experienced, but it would seem that for the most part, if you can get into download or recovery mode, then your phone is probably fine. But that's just from my personal experience.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Yup why I never reccomend anything other than Samsung.if u got a screen, ur not a paperweight. Unless of course u own a note or s2 then the brickbug comes into the mix and u might be phuckd lol
I did the same exact thing but I can get into download mode and recovery!!!
I cant restore backups and everytime I odin a stock rom or flash a custom rom with CWM my phone continues to get stuck at the samsung screen right before it comes on!
Any Ideas would really help right now!
Thanx
Odin stock rom but keep cwm recovery. Immediatly after the odin flash wipe data/factory reset from within recovery. it will boot. If you have cwm now you can open the stock tar in 7zip and remove the stock recovery from the tar to keep cwm. you could also dl a rom from here and flash in recovery as an alternative to odin. make sure you wipe EVERYTHING including /system first.
pls help
hai there ..i cant on my hp and i get stuck when i am planning to flash a new rom in odin..
the problem is in odin mode seem the added text dosen't appear when i plug the hp...pls sort this issue
billard412 said:
Yup why I never reccomend anything other than Samsung.if u got a screen, ur not a paperweight. Unless of course u own a note or s2 then the brickbug comes into the mix and u might be phuckd lol
Click to expand...
Click to collapse
The eMMC hard brick bug was fixed in 4.1.2 on the s2, not sure about the Note tho
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i m not able to enter my phone (galaxy spica gt i5700) i am stuck at recovery mode with logo and exclamation at center and phone beside it i cant wipe any data or do nothing but i can go in download mode but odin is not detecting it plzzzzzz help
MATANG008 said:
i m not able to enter my phone (galaxy spica gt i5700) i am stuck at recovery mode with logo and exclamation at center and phone beside it i cant wipe any data or do nothing but i can go in download mode but odin is not detecting it plzzzzzz help
Click to expand...
Click to collapse
You have stock recovery. Try different cables and ports. Odin is your only hope. You could also try a different version of Odin. Also make sure you have the Samsung Driver Suite (from Samsung's website) installed on your PC or Odin won't recognize it.
^^^^^yes try different cables and make sure you have updated drivers from Samsung......also check device manager and see if your computer is even detecting your phone
bilgerryan said:
You have stock recovery. Try different cables and ports. Odin is your only hope. You could also try a different version of Odin. Also make sure you have the Samsung Driver Suite (from Samsung's website) installed on your PC or Odin won't recognize it.
Click to expand...
Click to collapse
i have tried to use different cable then also not working ,but i dont have drivers installed name "samsung composite usb driver" insteda i have only usb composite driver if possible plz share the latest driver link.... and when i start odin it displays "image path and some chinese letters " pls help and tell me what does it means
I know this is a common problem but my Galaxy Note 2 is stuck on the boot screen and keeps restarting like a loop . I would do a factory reset but I don't have a custom recovery and I can't even get pass the boot logo .
Is there any way to factory reset it without custom recovery ? Or solve this problem any other way ? Thanks in advance , cheers
You can factory reset from stock recovery also ....
Sent from my SPH-L900 using Xparent BlueTapatalk 2
Epix4G said:
You can factory reset from stock recovery also ....
Sent from my SPH-L900 using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Oh yeah , I forgot to mention , I don't know why , when I boot into recovery , it doesn't have the Wipe Data and Wipe cache etc options . It only has factory tests .
fireboylolz said:
Oh yeah , I forgot to mention , I don't know why , when I boot into recovery , it doesn't have the Wipe Data and Wipe cache etc options . It only has factory tests .
Click to expand...
Click to collapse
I would not recommend this but it worked for me after I had the same issue after a bad flash.
Prerequisite is a backup image made by TWRP.
To fix used GNTK to have ODIN load an insecure image with TWRP. Still boot looped. Entered TWRP and Wiped everything (did not leave or reboot.) loaded the backup stock image made with TWRP initially from SD.
darksoul21 said:
I would not recommend this but it worked for me after I had the same issue after a bad flash.
Prerequisite is a backup image made by TWRP.
To fix used GNTK to have ODIN load an insecure image with TWRP. Still boot looped. Entered TWRP and Wiped everything (did not leave or reboot.) loaded the backup stock image made with TWRP initially from SD.
Click to expand...
Click to collapse
Urmm , can I get a step by step guide ? I'm kind of lost .
Apologies for missing/mangled links; I'm not allowed to post any.
Download one of garwynn's ma7 Odin packages here:
sxtpdevelopers.com/showthread.php?t=154
I'd suggest the one labeled "Rooted - KEEPS user data" if you do not have a backup.
Use the one labeled "Rooted- ERASES user data" if you do, or if you don't care about your memory/data.
Here's the procedure:
On the phone: Turn it off (remove the battery if you need to).
Hold volume down, the big button on front, and the power button (stick the battery back in if it's out)
The phone will immediately say "Warning!! A custom OS will melt your phone, eat your dog, etc etc".
Let go of all the buttons and then press Volume up.
The "ODIN MODE" screen will come up (it has a big green picture of the Android guy and says "ODIN MODE" at the top left).
Unplug the phone if it's connected to anything.
Put the .exe file you downloaded above on a Windows PC. Connect the phone to the Windows machine with a good USB cable (even new ones can be bad; cheap cables made for battery charging don't always have all the wires that a USB cable should).
On the Windows PC, go to samsung.com/us/support/owners/product/SPH-L900#
Hit "Manuals & Downloads, then the "Software" sub-tab, and click "Download File EXE". (The only file available for download is the USB driver.)
Install the USB driver.
Connect the phone, and make sure the PC doesn't complain that it doesn't have a driver for the device. Disconnect the phone.
Launch the .exe you downloaded from garwynn's recovery ROM post.
Connect the phone. You should get a message like, "<ID:0/009> Added!!" in the Odin window.
Push "Start".
Poof, a stock or near-stock MA7 phone, with or without a user data wipe, depending which version you downloaded.
Stuck in bootloop of some sort
Hi Guys. I am in serious problems. My note 2 kept on going off as much as 5-9 times a day. I decided to flash a new stock ROM. I did this three with three different stock ROM times with similar problem of switching off. On the last time however, my phone went on a bootloop. It keeps on showing "Samsung Galaxy Note 2 N7100" then the android robot(like the one which appears when the phone is doing a factory reset or update, then back to "Samsung Galaxy Note 2 N7100"....
1. I have tried restoring the phone with ODIN unsuccessfully.
2. Kies does not work at all(in fact Kies does not even connect to the phone. When i try using Emergency Firmware Recovery it states "Please enter recovery code from previous PC.." I had previously taken it to the Samsung service center here but i am not sure if Kies is a recovery process they tried using.
3. The Samsung Service Center here in Kenya cannot restore it either.
4. I cannot access the recovery menu at all: the phone only boot loops when i press the recovery combo.
5. I can only access the download mode which i have tried flashing different stock ROM unsuccesfully.
6. Currently the phone bootloops and has even refused to communcate with the computer(not recognised-maybe something related to the USB drivers)
Anyway, i love this phone greatly and i have heavily invested in it. I would not love to lose it. I heard of people losing IMEI because of ROM flashes- might this be something that affected me?
PLEASE HELP!
kennethwendo said:
Hi Guys. I am in serious problems. My note 2 kept on going off as much as 5-9 times a day. I decided to flash a new stock ROM. I did this three with three different stock ROM times with similar problem of switching off. On the last time however, my phone went on a bootloop. It keeps on showing "Samsung Galaxy Note 2 N7100" then the android robot(like the one which appears when the phone is doing a factory reset or update, then back to "Samsung Galaxy Note 2 N7100"....
1. I have tried restoring the phone with ODIN unsuccessfully.
2. Kies does not work at all(in fact Kies does not even connect to the phone. When i try using Emergency Firmware Recovery it states "Please enter recovery code from previous PC.." I had previously taken it to the Samsung service center here but i am not sure if Kies is a recovery process they tried using.
3. The Samsung Service Center here in Kenya cannot restore it either.
4. I cannot access the recovery menu at all: the phone only boot loops when i press the recovery combo.
5. I can only access the download mode which i have tried flashing different stock ROM unsuccesfully.
6. Currently the phone bootloops and has even refused to communcate with the computer(not recognised-maybe something related to the USB drivers)
Anyway, i love this phone greatly and i have heavily invested in it. I would not love to lose it. I heard of people losing IMEI because of ROM flashes- might this be something that affected me?
PLEASE HELP!
Click to expand...
Click to collapse
Just experienced the same issues while switching from the a custom rom back to stock LJ1. Stuck at the samsung screen. Took me back to my Original Epic. Downloaded the LJ1 kernel, reflashed custom recovery, flashed it, cleared dalvik, rebooted and bam! up and running. Keep getting an error about Chameleon has stopped that I am working on fixing but it is up and running so I am pleased.
kuroyoma said:
Just experienced the same issues while switching from the a custom rom back to stock LJ1. Stuck at the samsung screen. Took me back to my Original Epic. Downloaded the LJ1 kernel, reflashed custom recovery, flashed it, cleared dalvik, rebooted and bam! up and running. Keep getting an error about Chameleon has stopped that I am working on fixing but it is up and running so I am pleased.
Click to expand...
Click to collapse
It happened because you tried to flash backwards. With JB you can only flash forward.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
-Team Nocturnal Like A Boss :flipoff2:
-Galaxy Note II Lab Rats 2.1 Edition Goodness Theme- "Mine"
-Galaxy S2 Goodness Edition- "Wifes"
Elw00d said:
It happened because you tried to flash backwards. With JB you can only flash forward.
-Team Nocturnal Like A Boss :flipoff2:
-Galaxy Note II Lab Rats 2.1 Edition Goodness Theme- "Mine"
-Galaxy S2 Goodness Edition- "Wifes"
Click to expand...
Click to collapse
I had JB v15 and had to flash this file because I was stuck on the flash screen, after I flashed this file, it loads the phone, but it will not allow me to use the touchscreen and keeps rebooting..I need to chk debugging mode and also see what version I have now after flashing this file...pls HELP!!!!
I can't use my phone..
fechina said:
I had JB v15 and had to flash this file because I was stuck on the flash screen, after I flashed this file, it loads the phone, but it will not allow me to use the touchscreen and keeps rebooting..I need to chk debugging mode and also see what version I have now after flashing this file...pls HELP!!!!
I can't use my phone..
Click to expand...
Click to collapse
I stuck with my phone too.
I was partition my sd card and copying somes apps there and then it crashes and reboots.
Stucked in boot loop.
Already wipe data/ factory reset.
Flash stock via odin and cwm via odin.
Format sdcard in recovery (excepts /data)
Still is on boot loop
Dalvik?
Sent from the little guy
Hello to all guys I desperately need your help, this morning I installed it on my notes 2, application Swapper 2, damn I say, because I restarted the phone and it is in an infinite bootloop, I tried the same thing any firmware I can not solve the problem, i also tried the Help and Rescue Deep Clean but nothing to do, the rescue does not recognize me the files that I put on odin I tried 5 times the result is always FAIL. What can I do? 1000 Thanks to all. I posted in the other thread of aid, they told me to post it here.
P.S Sorry for my Englesh i'm italian
luca260786 said:
Hello to all guys I desperately need your help, this morning I installed it on my notes 2, application Swapper 2, damn I say, because I restarted the phone and it is in an infinite bootloop, I tried the same thing any firmware I can not solve the problem, i also tried the Help and Rescue Deep Clean but nothing to do, the rescue does not recognize me the files that I put on odin I tried 5 times the result is always FAIL. What can I do? 1000 Thanks to all. I posted in the other thread of aid, they told me to post it here.
P.S Sorry for my Englesh i'm italian
Click to expand...
Click to collapse
Can you get to your custom recovery? Vol up+home+power, keep holding till Samsung Galaxy Note 2 pops up and it goes to recovery. Which recovery are you using? What ROM are you on? These need to be known to help you
Android...A New Digital Revolution Of Incredible Developers...
ianmb said:
Can you get to your custom recovery? Vol up+home+power, keep holding till Samsung Galaxy Note 2 pops up and it goes to recovery. Which recovery are you using? What ROM are you on? These need to be known to help you
Android...A New Digital Revolution Of Incredible Developers...
Click to expand...
Click to collapse
Yes I can install the TWRP Recovery, and I have the Samsung Stock Rom. I can go in download mode. In the stock recovery I have 2 errors: E: Failed to mount / efs (invalid argument) and Faied mount / sdcard No such file.
Sorry for my Englesh I'm Italian
Question
Did you save a stock backup so you can reinstall if something happens.
luca260786 said:
Yes I can install the TWRP Recovery, and I have the Samsung Stock Rom. I can go in download mode. In the stock recovery I have 2 errors: E: Failed to mount / efs (invalid argument) and Faied mount / sdcard No such file.
Sorry for my Englesh I'm Italian
Click to expand...
Click to collapse
If you are rooted you need to use TWRP and not stock recovery. You cannot flash a different ROM on stock recovery.
Android...A New Digital Revolution Of Incredible Developers...
ianmb said:
If you are rooted you need to use TWRP and not stock recovery. You cannot flash a different ROM on stock recovery.
Android...A New Digital Revolution Of Incredible Developers...
Click to expand...
Click to collapse
Yes i can also install the root, but then the galaxy will not start is always the same in writing samsung and does not go ahead I also flashed 13 times than the stock firmware and not a single one all the stops to boot. I do not know how to fix it.
luca260786 said:
Yes i can also install the root, but then the galaxy will not start is always the same in writing samsung and does not go ahead I also flashed 13 times than the stock firmware and not a single one all the stops to boot. I do not know how to fix it.
Click to expand...
Click to collapse
Was it a stock ROOTED rom? And all this was from installing an app? What did you wipe in TWRP? Did you try Advanced Wipe in TWRP...Cache/Dalvik/Data/System? Then try a rooted rom made for your phone.
Android...A New Digital Revolution Of Incredible Developers...
ianmb said:
Was it a stock ROOTED rom? And all this was from installing an app? What did you wipe in TWRP? Did you try Advanced Wipe in TWRP...Cache/Dalvik/Data/System? Then try a rooted rom made for your phone.
Android...A New Digital Revolution Of Incredible Developers...
Click to expand...
Click to collapse
I have already done all this that you have written, I have not solved the problem. When I installed Swapper 2 I had a custom rom rooted.
Hi
Three weeks ago my note 2 started to reboot on its own and then the phone wouldn't boot. at first it was stuck on the samsung logo but then it became stuck on the note 2 logo. I surfed the internet for solutions and started to work on repairing it but it was no good. At first I started to put a new firmware via odin 3v1.85 but it stopped the process then I closed odin and then when I boot my phone it says "Firmware upgrade encountered an issue. Please select recovery mode in kies and try again" then I tried putting a new firmware but it didn't work and tried a pit file and it failed.
My note 2 was rooted but I never placed a custom rom and before all of this my sandisk sd card got corrupted is it connected to the problem?
I am a noob at these stuff please help me
Which firmware you have installed?
Was it 4.1.1? It seems SDS
What exactly you getting on rt upper corner while device on download mode
And what exact error you getting on odin
Sent from my GT-N7100 using xda premium
dr.ketan said:
Which firmware you have installed?
Was it 4.1.1? It seems SDS
What exactly you getting on rt upper corner while device on download mode
And what exact error you getting on odin
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
It was from samsung-updates
No, it was 4.1.2
Odin Mode
PRODUCT NAME: GT-N7100
CUSTOM BINARY DOWNLOAD: YES (1 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
Now the error is NAND Write Start!!, but for the first firmware as soon as I get to my home I will post it here
Good, at least last msg I can say chances of sds rare.
It is likely connection issue
-reboot to recovery and wipe cache and data, it may revive device. Otherwise flash rom
-check kies is not running in background
-try other usb port. And don't use any extension cable/hub to connect device and directly connect device to PC
-close firewall and antivirus
Sent from my GT-N7100 using xda premium
dr.ketan said:
Good, at least last msg I can say chances of sds rare.
It is likely connection issue
-reboot to recovery and wipe cache and data, it may revive device. Otherwise flash rom
-check kies is not running in background
-try other usb port. And don't use any extension cable/hub to connect device and directly connect device to PC
-close firewall and antivirus
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Sorry for the silly question but how do I flash a rom, I already downloaded Android Revolution to my PC but I don't know how to flash it.
For custom ROM if it is available in flashable zip then you have to flash using CWM recovery
For stock ROM, there is guide on my signature, read 'N7100 All in one' from my signature.
I am getting this error again
i39.tinypic(.)com/34xn9.jpg
Then I tried another ROM I got this error
i39.tinypic(.)com/23lgj8o.jpg
better you go with stock ROM and flash using odin
here 1st post have all the instructions.
http://forum.xda-developers.com/showthread.php?t=1896696
Can you put a link for a pit file for the n7100, because I think I flashed a S3 pit on my note 2 by accident.
http://d-h.st/Dlv
Download and extract above file
select for PIT table, that will auto select repartition option
and select ROM file for PDA and flash both togather
I am getting another error which is can't open the serial(com) port, what shall I do?
BattleOfNuts said:
I am getting another error which is can't open the serial(com) port, what shall I do?
Click to expand...
Click to collapse
That may be error from PC side
try re installing driver
Try different port
disable firewall/anti virus
Now I am getting this error There is no PIT partition.
Try flashing only pit first
Then both pit and rom
Sent from my GT-N7100 using xda premium
I flashed the only the pit file first but it gave me the same error
And I want to note that sometimes the process hang in SetupConnection for couple of minutes and then fail. And sometimes it finishes with a fail and the process take approximately 35 seconds. Does that matter?
Try different cable and pc
Sent from my GT-N7100 using xda premium
After trying 2 PCs and 1 laptop with windows 7 and 1 laptop with windows xp and 3 cables I got this massage on odin mode in my note 2
Product Name:
Custom Binary: No
Current Binary: Samsung Official
System Status: Custom
and when I boot my note 2 I get this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What shall I do?
chances are very high it's SDS and time to send to service station.
dr.ketan said:
chances are very high it's SDS and time to send to service station.
Click to expand...
Click to collapse
Exactly in what condition is unrecoverable for Note 2? My friend ph is stuck at boot logo and I'm gonna blind invest for it Thanks in advance
Ok the backround. about 5 days ago the software update started. All seemed ok but then I was getting reboots 4-5 times a day. Brought it to AT&T and they tried to reflash. After backing up info I signed the release form holding them not liable for bricking the phone. Asked the tech how many have bricked on him and he said none. Sorry I was his first...maybe. Screen asking for Kies program to repair. AT&T tech not allowed to use Kies. I downloaded Kies but no luck.
Got the bugger to go to the Boot screen of "Warning...a custom OS....". Then the "Downloading, do not turn of target" screen. It is stuck there or I should say I have left it there. Top of screen says Odin Mode (in red), Produce Name: SGH-I747, Current Binary: Samsung Official, Qualcomm SecureBoot: Enabled, Warranty Bit: 0, Bootloader Ap SWREV: 3.
I have downloaded Odin 3.09. I have the USB drivers installed. I want to restore last known version of AT&T android 4.2.2 or the upgrade 4.3 that didn't seem to take. I am not sure which version it was running before the crash. My wife's S3 is running 4.3.
What Next? Where do I get the file to upload to the phone? Thanks.
So your s3 was trying to upgrade from 4.1.2 or 4.3?
thenexusgeneration said:
So your s3 was trying to upgrade from 4.1.2 or 4.3?
Click to expand...
Click to collapse
Not sure. I think I checked the build version after the install and it read 4.2.2. Can't be absolutely certain when i saw that build number. Would make sense to check it after the install assuming the install happened at all. But again the wife and I bought the two S3's at the same time and hers is running 4.3.
If you got the ota a few days ago, and judging from the SWREV (Software Revision), you are currently on 4.4.2 firmware (NE4). This means you cannot flash older firmware on Odin (or any other way, OT it'll really brick). From now on you can only flash NE4 firmware.
You can, however, flash older roms.
If you haven't already, try factory resetting from recovery. (This will wipe all your data including the internal sdcard)
If that doesnt work, my only other suggestion is to flash TWRP via Odin, then boot TWRP recovery and flash the stock NE4 rom from enewman17.
DocHoliday77 said:
If you got the ota a few days ago, and judging from the SWREV (Software Revision), you are currently on 4.4.2 firmware (NE4). This means you cannot flash older firmware on Odin (or any other way, OT it'll really brick). From now on you can only flash NE4 firmware.
You can, however, flash older roms.
If you haven't already, try factory resetting from recovery. (This will wipe all your data including the internal sdcard)
If that doesnt work, my only other suggestion is to flash TWRP via Odin, then boot TWRP recovery and flash the stock NE4 rom from enewman17.
Click to expand...
Click to collapse
I can't get to the factory reset screen, only the warning screen before pressing volume up to load a custom OS. I'm confused....well on may levels but I digress. I thought ROM and firmware were the same thing.
Also the TWRP site has two files, same file I Assume, in different formats, md5 and tar. Are they the same file? Do I use one over the other? To flash TWRP using Odin what screen should I start with on the S3? thanks.
To boot recovery hold volume up, home and power. When it vibrates release power only.
A rom (as we use it here) is just the O/S on the /system partition and is usually flashed in recovery. They also include kernels most of the time. The firmware is this, and more. It includes images for multiple partitions. (aboot, sbl2, sbl3, tz, rpm, modem, recovery, boot, system, cache)
Around here you'll see a lot of folks refer to this as just the bootloaders, but they are talking about the base firmware. Sorry if I confuse anyone with that btw, I try to remember to call it the bootloaders, but am just used to using the term firmware.
As for flashing twrp from odin, it must be a .tar or .tar.md5. Both are used by odin. The .md5 extension just tells odin a hash value is included. It will then run an md5 checksum to verify the file about to be flashed is valid, or not corrupted. Either one will work, but the .tar.md5 is safer. If the download gets corrupted somehow, odin will catch it and refuse to flash.
When flashing anything in odin you need to be in Download mode.
DocHoliday77 said:
To boot recovery hold volume up, home and power. When it vibrates release power only.
A rom (as we use it here) is just the O/S on the /system partition and is usually flashed in recovery. They also include kernels most of the time. The firmware is this, and more. It includes images for multiple partitions. (aboot, sbl2, sbl3, tz, rpm, modem, recovery, boot, system, cache)
Around here you'll see a lot of folks refer to this as just the bootloaders, but they are talking about the base firmware. Sorry if I confuse anyone with that btw, I try to remember to call it the bootloaders, but am just used to using the term firmware.
As for flashing twrp from odin, it must be a .tar or .tar.md5. Both are used by odin. The .md5 extension just tells odin a hash value is included. It will then run an md5 checksum to verify the file about to be flashed is valid, or not corrupted. Either one will work, but the .tar.md5 is safer. If the download gets corrupted somehow, odin will catch it and refuse to flash.
When flashing anything in odin you need to be in Download mode.
Click to expand...
Click to collapse
Thanks Doc, when I try the boot recovery hold volume up, home and power I get the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." message. If I use the hold volume down, home and power combo I get to the "Warning!! A custom Os can cause....." screen. If I press volume up it goes to the "Downloading...Do not turn off target!!" screen. If I press volume down it reboots to the "Kies" screen. Which screen mode should I be in when attempting to flash the TWRP file with Odin? thanks.
OK I tried to flash the TWRP file. Put S3 in download mode, Opened Odin, plugged in S3, Odin showed "added", tried to load the TWRP file into Odin but it freezes Odin. Non responsive Odin. Tried 4 times with and without plugging in phone. any clues?
Try downloading the file again. Could be a corrupted download. Also, what version of Odin are you using?
Oh, and kies interferes with Odin. Uninstall it and try odin again.
DocHoliday77 said:
Try downloading the file again. Could be a corrupted download. Also, what version of Odin are you using?
Oh, and kies interferes with Odin. Uninstall it and try odin again.[/QUOTE
Thanks I tried 3.09 first then 3.07. 3.09 hangs right away. 3.07 doesn't say "not responding" but nothing happens. Looks like it will but no. I wait for about 45 min. I will try everything from scratch. I did uninstall Kies with no help. Kies can't find the device - generic code 43.
Is it the Bootloader ap SWREV: 3 that indicates I need 4.4.2?
If its an older version such as 4.3 can i/should I still install 4.4.2?
Where do I find 4.4.2. Thanks for all your help because this is like finding a specific needle in a stack of needles without even fulling understanding what a needle is! God I miss DOS.
I've been doing all the above without sim or sd card installed. Does that make any difference.
Click to expand...
Click to collapse
IT's BACK ALIVE! Now what?
What happened? None of the .MD5 files would load and would just lock the Odin. Since I had nothing to loose I used a 2.6 version of the .tar file without the .MD5 check. It loaded fine, rebooted and there is my phone screen with all my apps and info. I'm afraid to even unplug it from the cable (silly I know). Checked the version and it reads 4.4.2., baseband version I747UCUFNE4, Kernel version 3.4.0-1514807, build number KOT49H.I171UCUFNE4, SE for Android status Enforcing SEPF_SAMSUNG-SGH-I747_4.4.2_0016.
Am I done? Is it safe to put back in service or should I do something else? thanks
Weird! Sounds like something on your system didn't like the md5sum. Never seen that before!
But if it appeared to flash ok, rebooted and it says PASS in Odin, you should be good to go.
First though, what exactly did you flash? Can you link to it? To my knowledge there is no NE4 firmware package available. Ive been trying to make one but it hasn't worked yet....
DocHoliday77 said:
Weird! Sounds like something on your system didn't like the md5sum. Never seen that before!
But if it appeared to flash ok, rebooted and it says PASS in Odin, you should be good to go.
First though, what exactly did you flash? Can you link to it? To my knowledge there is no NE4 firmware package available. Ive been trying to make one but it hasn't worked yet....
Click to expand...
Click to collapse
Just flashed the TWRP http://true-android.blogspot.com/2014/01/install-twrp-recovery-2631-on-at-galaxy.html. It passed it and phone rebooted to the normal reboot and my old screen. Weird? I do weird all the time. I used Odin 3.09. I have run it through some of its apps. I will wait 24 hours to see if it reboots by itself.
Cool, sounds like it should be ok then. Hopefully it'll make it through your testing period!
DocHoliday77 said:
Cool, sounds like it should be ok then. Hopefully it'll make it through your testing period!
Click to expand...
Click to collapse
Well it's functioning but we are back to the reboots 4-5 x a day. I can get to the recovery screen now. Anyone have a guess of my best next option?
Not sure, could be a faulty power switch though. Lots of these have been going bad in recent months, but it usually happens all the time, not just a few times a day.
Sent from my SGH-T999 using Tapatalk
Just a F/U. The reboot was getting to be a problem. Also had a problem with back up and restore apps. Found one that worked so I did a factory reset. All is good again. Love my S3 again. Still not happy with how AT&T handled the problem though.
Hey guys,
My girlfriends S4 mini has bricked. I've tried flashing a totally stock firmware via odin to recover it. This doesn't seem to help at all, it still gets stuck at the splash screen. I've tried flashing TWRP via odin too but that fails as well, AFAIK drivers are installed correctly, odin detects the device, it wouldn't do so if drivers weren't install correctly surely? The only mode I can get it into is download mode, if I try to reboot into recovery mode it'll say 'booting recovery' for 5 seconds or so then reboot and get stuck at the splash screen again.
Any help is appreciated, I'm a samsung noob, thanks.
What recovery was on it prior to having this problem?
I read that someone was having a slight problem like you (twrp recovery), and they flashed PhilZ tar using Odin, in order to boot back into recovery.
You could try a older version of PhilZ foie your device might help...
Look here>> http://goo.gl/2xlUCO
And have you tried using the kies emergency firmware recovery? That saved a device I flashed with a stock firmware, and then the phone wouldn't boot, soft brick.
Ran the kies emergency firmware, it downloaded what was needed, then flashed it on the phone. Takes about 20-30 mins.
Keep in mind if you do try that method, no need to put the phone into download mode. Kies will recognize the phone when you connect it thru usb. And it will do the rest.
Hope this can help you fix the phone.
Bajanman said:
What recovery was on it prior to having this problem?
I read that someone was having a slight problem like you (twrp recovery), and they flashed PhilZ tar using Odin, in order to boot back into recovery.
You could try a older version of PhilZ foie your device might help...
Look here>> http://goo.gl/2xlUCO
And have you tried using the kies emergency firmware recovery? That saved a device I flashed with a stock firmware, and then the phone wouldn't boot, soft brick.
Ran the kies emergency firmware, it downloaded what was needed, then flashed it on the phone. Takes about 20-30 mins.
Keep in mind if you do try that method, no need to put the phone into download mode. Kies will recognize the phone when you connect it thru usb. And it will do the rest.
Hope this can help you fix the phone.
Click to expand...
Click to collapse
Thanks, I'll be sure to try that a bit later when I get back later.
It was 100% stock when the issue occurred, no root, no custom recovery, knox is still 0x0
matt4321 said:
Thanks, I'll be sure to try that a bit later when I get back later.
It was 100% stock when the issue occurred, no root, no custom recovery, knox is still 0x0
Click to expand...
Click to collapse
Wow then yes that is kinda crazy then being fully stock set-up.
Then you'll want to try the kies emergency firmware fix.
Lmk how it works out for you.
I'll keep an eye on this thread for your feedback.
matt4321 said:
Hey guys,
My girlfriends S4 mini has bricked. I've tried flashing a totally stock firmware via odin to recover it. This doesn't seem to help at all, it still gets stuck at the splash screen. I've tried flashing TWRP via odin too but that fails as well, AFAIK drivers are installed correctly, odin detects the device, it wouldn't do so if drivers weren't install correctly surely? The only mode I can get it into is download mode, if I try to reboot into recovery mode it'll say 'booting recovery' for 5 seconds or so then reboot and get stuck at the splash screen again.
Any help is appreciated, I'm a samsung noob, thanks.
Click to expand...
Click to collapse
Try doing @Bajanman said
If it doesnt work then try a new firmware which isnt for your carrier or maybe a different country. This is because samsung has this long lasting tradition of some of its firmware being corrupted/not booting. Screw you samsung moment when you realize that the firmware you have cooked/themed on is bullcrap
Thanks @SkywalkerZ and @Bajanman for your help,
the current situation is that I've tried the kies recovery method, but when doing tools > emergency recovery mode, it asks for a recovery code which I dont have,
If I try tools > firmware upgrade and initialization, it asks for the model name ( GT-I9195 ) and the seriel number, which I also enter. But it then says 'GT-I9195 does not support initializing'.
I'm currently downloading a new firmware of sammobile which I can try flash through odin right?
matt4321 said:
Thanks @SkywalkerZ and @Bajanman for your help,
the current situation is that I've tried the kies recovery method, but when doing tools > emergency recovery mode, it asks for a recovery code which I dont have,
If I try tools > firmware upgrade and initialization, it asks for the model name ( GT-I9195 ) and the seriel number, which I also enter. But it then says 'GT-I9195 does not support initializing'.
I'm currently downloading a new firmware of sammobile which I can try flash through odin right?
Click to expand...
Click to collapse
Yeah, odin
let us know
SkywalkerZ said:
Yeah, odin
let us know
Click to expand...
Click to collapse
So I tried that, unfortunatly the same issue occured, when the flash is done, it trys to reboot into recovery, fails, then reboots to the splash screen, reboots, then back to the splash screen and so on until I remove the battery
matt4321 said:
So I tried that, unfortunatly the same issue occured, when the flash is done, it trys to reboot into recovery, fails, then reboots to the splash screen, reboots, then back to the splash screen and so on until I remove the battery
Click to expand...
Click to collapse
Can I ask what recovery is installed? And have you tried flashing a different custom recovery thru Odin? To see if it will help boot the phone..
Someone else was going thru the same as you, and that help get them back in order.
Bajanman said:
Can I ask what recovery is installed? And have you tried flashing a different custom recovery thru Odin? To see if it will help boot the phone..
Someone else was going thru the same as you, and that help get them back in order.
Click to expand...
Click to collapse
Yeah I've tried flashing a custom recovery, nothing seems to stick, it's so strange.
Everything is 100% stock and knox is still 0x0, I'm running out of ideas. Might have to send it off.
It's frustrating though because I can get it into download mode, but the flashing doesn't seem to work
matt4321 said:
Yeah I've tried flashing a custom recovery, nothing seems to stick, it's so strange.
Everything is 100% stock and knox is still 0x0, I'm running out of ideas. Might have to send it off.
It's frustrating though because I can get it into download mode, but the flashing doesn't seem to work
Click to expand...
Click to collapse
I can understand the frustration you're going thru trust me.
I know you know what you're doing, but the person who said they fixed a soft brick, flashed a really old version of PhilZ to get it back. Then flash a custom Rom to get the phone up and running.
But I know you've tried Odin back to stock and nothing is working for you. What's the crazies part is that the phone was completely stock. And it's still broke...
If I see/find any thing that may help you I'll post it here ok.
Bajanman said:
I can understand the frustration you're going thru trust me.
I know you know what you're doing, but the person who said they fixed a soft brick, flashed a really old version of PhilZ to get it back. Then flash a custom Rom to get the phone up and running.
But I know you've tried Odin back to stock and nothing is working for you. What's the crazies part is that the phone was completely stock. And it's still broke...
If I see/find any thing that may help you I'll post it here ok.
Click to expand...
Click to collapse
Appreciate the help mate!
So I tried an old Philz recovery, that didn't stick either. I'm wondering what is really happening since if I flash a custom recovery then knox should void right? but anytime I flash TWRP or Philz, then head back to download mode it still says knowx 0x0.
What drivers did you install on your PC, do you have a link? I'm starting to think maybe that is the issue, but surely odin would refuse to flash at all if no samsung drivers were installed...?
matt4321 said:
Appreciate the help mate!
So I tried an old Philz recovery, that didn't stick either. I'm wondering what is really happening since if I flash a custom recovery then knox should void right? but anytime I flash TWRP or Philz, then head back to download mode it still says knowx 0x0.
What drivers did you install on your PC, do you have a link? I'm starting to think maybe that is the issue, but surely odin would refuse to flash at all if no samsung drivers were installed...?
Click to expand...
Click to collapse
Sorry i lost touch with this thread and busy with studies
The only drivers that are needed are the ones that will be installed with KIES
Nothing else is needed
This is really weird of how it doesnt want to boot up even after flashing stock firmware via odin
Just a quick check, ..what options did you choose in odin ?
SkywalkerZ said:
Sorry i lost touch with this thread and busy with studies
The only drivers that are needed are the ones that will be installed with KIES
Nothing else is needed
This is really weird of how it doesnt want to boot up even after flashing stock firmware via odin
Just a quick check, ..what options did you choose in odin ?
Click to expand...
Click to collapse
These are the options, see the photo.
I've tried trying a few different options. Is this how it should look?
I'm a full on Samsung noob
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
matt4321 said:
These are the options, see the photo.
I've tried trying a few different options. Is this how it should look?
I'm a full on Samsung noob
Click to expand...
Click to collapse
Hi, re-partition should be not ticked!, download firmware from sammobile, select it only as AP.
N0Ntoxic said:
Hi, re-partition should be not ticked!, download firmware from sammobile, select it only as AP.
Click to expand...
Click to collapse
Cheers for the reply, so I've tried that before, saw the instructions in another thread, I'll give it another try though and untick re-partition
May I ask which firmware exactly are you trying to flash?
From your pictures youre trying Bml4 i think its a jb with Knox , if the phone has a kk it will fail install
Why are you trying to flash with repartition and pit file?
Did you messed somehow with the partition table?
What is exactly the the phone got bricked, normal usage overheat, water damage, dropped if you have no signs damage if it's under Warranty and knox 0x0 Send it to service.
matt4321 said:
These are the options, see the photo.
I've tried trying a few different options. Is this how it should look?
I'm a full on Samsung noob
Click to expand...
Click to collapse
yeah, as another user said
Re partition shouldn't be ticked
Now hopefully this does the trick
and also, if your phone came with 4.4.2, flash 4.4.2
dont downgrade. to 4.2.2
Try this:
Flash a custom recovery
wipe internal sd
Flash stock firmware and try booting up
Hopefully that will fix it