Related
My phone (GT-I5800) is stuck with the above message on screen.
Here is the history.
1 - Flashed XXJPU which was OK
2 - Rooted with Superoneclick which reported OK, but also reported insufficient space to install superuser and busybox.
3 - Went to Play store and downloaded superuser.
4 - Phone hung trying to install superuser.
5 - Pulled battery and phone would not boot. Just stopped at Samsung GT- I5800 splash screen.
6 - Can get into download mode OK so reflashed XXJPU
7 - ODIN reported PASS but phone gets to install screen saying "Delete files, please wait" and just sits there forever.
Hopefully someone can see my errors and help out please?
I always had errors when trying to root XXJPU as well. JPU is quite buggy for me so it might be a firmware problem. Try flashing XXJPS.
You can download JPS from this thread: http://forum.xda-developers.com/showthread.php?t=1497261
--------------------------------
Click thanks if I helped.
MicroGeek said:
I always had errors when trying to root XXJPU as well. JPU is quite buggy for me so it might be a firmware problem. Try flashing XXJPS.
You can download JPS from this thread: http://forum.xda-developers.com/showthread.php?t=1497261
--------------------------------
Click thanks if I helped.
Click to expand...
Click to collapse
Thanks, tried JPS and it still stops at the same place. It goes through installing, setting csc, then delete files and freezes.....
PSL184 said:
Thanks, tried JPS and it still stops at the same place. It goes through installing, setting csc, then delete files and freezes.....
Click to expand...
Click to collapse
Can you explain your entire flashing process?
MicroGeek said:
Can you explain your entire flashing process?
Click to expand...
Click to collapse
I'm using Odin 4.42 and fw from Sammobile.
I place ops package and put fw into the one file box.
Put phone into download mode and connect to PC.
Wait for yellow box then hit start
Odin returns a PASS but when phone reboots it just stops.
I think if I could get to recovery to reset and delete cache I might get some luck but can't get to recovery mode either....
Try using Odin 4.252 because that's the one I use. Download XXJPS from this thread. Make sure you have the right ops file name "apollo_0531.ops". Make sure you open Odin by right clicking and then clicking on "Run as administrator" and in Odin make sure you tick all the boxes EXCEPT the "Debug ONLY" box. Then click Start and wait and see. Also, after the ROM has been flashed the phone should automatically go into recovery and wipe the data and cache so you don't need to worry about that. Apart from what I've mentioned above, there is nothing wrong with your flashing process and everything should go smoothly.
Perfect, thanks for your time. All working normally again now
Can I ask your advice on rooting pls? Is Superoneclick OK to use?
Thanks again
Yes it is fine to superoneclick but I don't think its necessary since rooting itself doesnt affect the phone too much. You would have to root, then flash a custom kernel, add some tweaks/mods etc. to make a difference in performance so it would be much easier just staying unrooted if you are fine with the performance or just flash a custom ROM if you think the stock ROM is slow.
You should try out a CR based on Froyo. They are really advanced and give you all Froyo can give you. Fast phone, long battery live and everything works.
MicroGeek said:
I always had errors when trying to root XXJPU as well. JPU is quite buggy for me so it might be a firmware problem. Try flashing XXJPS.
You can download JPS from this thread: http://forum.xda-developers.com/showthread.php?t=1497261
--------------------------------
Click thanks if I helped.
Click to expand...
Click to collapse
Odd, jpu seemed the best for me
Sent from my GT-I9003 using xda app-developers app
Flash this http://www.mediafire.com/download.php?x7zq3mp7zxmqmk8 (stock, deodex, rooted XXJPU)
Jason-EX said:
Flash this http://www.mediafire.com/download.php?x7zq3mp7zxmqmk8 (stock, deodex, rooted XXJPU)
Click to expand...
Click to collapse
Thanks for the link.... Any more info on this ROM?
Its just the latest android 2.2 update for our phone but its also rooted and deodexed so it saves you the hassle. Google the benefits of deodexing if you have any issues.
Click thanks if I helped.
So long story short, my tab was running stock ICS (rooted, with temp CWM/cwm.zip). I decided to try a new rom (paranoid android) so I backed up everything via CWM and I flashed the new rom. But I forgot to do a factory reset before doing so which resulted in a bootloop. I returned to CWM to try to restore the previous ROM, all seemed to be fine and the tab restarted but was also bootlooped. Now I can't even access the stock recovery to acess CWM, I get an error message:
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC code : THL
Successfully applied multi-CSC
E :failed to mount / system (invalid argument) <in red.
Is there anything I can do to return to my stock ROM?!
Do I have the Brick Bug?
rumpypumpy said:
So long story short, my tab was running stock ICS (rooted, with temp CWM). I decided to try a new rom (paranoid android) so I backed up everything via CWM and I flashed the new rom. But I forgot to do a factory reset before doing so which resulted in a bootloop. I returned to CWM to try to restore the previous ROM, all seemed to be fine and the tab restarted but was also bootlooped. Now I can't even access the stock recovery to acess CWM, I get an error message:
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC code : THL
Successfully applied multi-CSC
E :failed to mount / system (invalid argument) <in red.
Is there anything I can do to return to my stock ROM?!
Click to expand...
Click to collapse
Can it get into download mode? If so try flash a stock rom with odin. Im not a sgt user but i am a samsung phone user and usualy when i forget to wipe all i have to do is go back into recovery. Then wipe everything and flash the same rom. NEVER go straight to a backup unless you pass setup. Then it can create a link almost so it supports going back. Or so thats what ive been told by devs on other forums...sounds kinda wierd tho but anyway if you forget to do something while flashing roms then go back indo recovery and do it again
Sent from the phone of Gamers
gmaster1 said:
Can it get into download mode? If so try flash a stock rom with odin. Im not a sgt user but i am a samsung phone user and usualy when i forget to wipe all i have to do is go back into recovery. Then wipe everything and flash the same rom. NEVER go straight to a backup unless you pass setup. Then it can create a link almost so it supports going back. Or so thats what ive been told by devs on other forums...sounds kinda wierd tho but anyway if you forget to do something while flashing roms then go back indo recovery and do it again
Sent from the phone of Gamers
Click to expand...
Click to collapse
It loads the amination for the stock recovery, then I get the error message I posted above. I need to get onto the stock recovery to get into CWM. Im not too sure what to do at the moment...
rumpypumpy said:
It loads the amination for the stock recovery, then I get the error message I posted above. I need to get onto the stock recovery to get into CWM. Im not too sure what to do at the moment...
Click to expand...
Click to collapse
Thats a messege saying the system has broke basicly because you went straight to a backup. Download mode and odin are your only hope
Sent from the phone of Gamers
gmaster1 said:
Thats a messege saying the system has broke basicly because you went straight to a backup. Download mode and odin are your only hope
Sent from the phone of Gamers
Click to expand...
Click to collapse
I forgot about download mode. I'll have a go then I'll report back.
Thanks
Now I'm stuck at the "<ID:0/005> factoryfs.img" stage!
I'm a bit scared of unplugging the tab, what would be the best thing to do now?
EDIT: If I flash a kernel or CWM, would this solve my problem?
Thanks in advance
EDIT:I managed to get CWM working, a step in the right direction
rumpypumpy said:
Now I'm stuck at the "<ID:0/005> factoryfs.img" stage!
I'm a bit scared of unplugging the tab, what would be the best thing to do now?
EDIT: If I flash a kernel or CWM, would this solve my problem?
Thanks in advance
EDIT:I managed to get CWM working, a step in the right direction
Click to expand...
Click to collapse
From CWM wipe data, cache & dalvik & reboot.
And flash this ICS zip file from CWM. if yours is 6800.
http://forum.xda-developers.com/showthread.php?t=1796866
rumpypumpy said:
Now I'm stuck at the "<ID:0/005> factoryfs.img" stage!
I'm a bit scared of unplugging the tab, what would be the best thing to do now?
EDIT: If I flash a kernel or CWM, would this solve my problem?
Thanks in advance
EDIT:I managed to get CWM working, a step in the right direction
Click to expand...
Click to collapse
If cwm works then we both know theres hope
Sent from the phone of Gamers
lsherif said:
From CWM wipe data, cache & dalvik & reboot.
And flash this ICS zip file from CWM. if yours is 6800.
http://forum.xda-developers.com/showthread.php?t=1796866
Click to expand...
Click to collapse
I did everything you said, but the progress bar has been stuck at 75% for over an hour, this has happened with all the ROMs I've tried to install. Is there anything else I could do? I red somewhere that a low battery doesn't allow ROMs to be installed properly.
Although I have no idea of my battery life, I'm just gonna leave it to charge for a bit. I hope everything turns out fine eventually
rumpypumpy said:
I did everything you said, but the progress bar has been stuck at 75% for over an hour, this has happened with all the ROMs I've tried to install. Is there anything else I could do? I red somewhere that a low battery doesn't allow ROMs to be installed properly.
Although I have no idea of my battery life, I'm just gonna leave it to charge for a bit. I hope everything turns out fine eventually
Click to expand...
Click to collapse
Battery life has nothing to do with it. People just say make sure you have high battery incase something happens. I think that it might be a very expensive brick now. Unless anyone else knows then i habe no idea
Sent from the phone of Gamers
gmaster1 said:
Battery life has nothing to do with it. People just say make sure you have high battery incase something happens. I think that it might be a very expensive brick now. Unless anyone else knows then i habe no idea
Sent from the phone of Gamers
Click to expand...
Click to collapse
:crying:
I was reading the following articles:
http://www.xda-developers.com/android/samsung-diligently-working-towards-hardbrick-fix/
http://forum.xda-developers.com/showthread.php?t=1810954
Could this Brick Bug be the source of my problems?
I was running a leaked version of ICS AND I have been using the cwm.zip so there is the possibility
Being unable to flash through either Odin or CWM surely sounds a lot like the brickbug.
If I were you, I'd reboot to download mode, and install a full ROM with repartition + PIT file. If it works, install locerra's CWM (it's one of the few recoveries for our tablet that's confirmed to be brickbug-free), and work as usual. But remember to wipe everything before installing anything through CWM...
If Odin doesn't work, you probably have been hit by the brickbug. However, all is not lost: this guy seems to have found a "fix" for many devices. It involves giving up on all your data and making your onboard storage a couple of GB smaller than it used to be, but it can make your device work again. Read the thread, try to understand it, and (if you can't find another way out) use the PIT file for the GT-6800 provided. If your tab isn't the international WiFi+3G GT-P6800, you may have to ask the guy (hg42) for a PIT tailored to your device.
The other option, in the case of a eMMC-related brick, is to remove all traces of CWM, go to a Samsung store and repair it under warranty, saying "its broke down when I were running that backie upppe thing in kies".
The other option is the better one, as i bricked my note. When i am able to revive it, i am left with 8GB space and it seems real laggy. Change a new motherboard would be better if still cover undr warrantly.
Sent from my GT-P6800 using xda premium
Thanks for the replies guy.
I have decided I will return it as faulty, in the hope it is repaired. I haven't been able to boot into CWM anymore, only the download mode, so I am guessing it is fine to return it as it is?
Thanks
rumpypumpy said:
Thanks for the replies guy.
I have decided I will return it as faulty, in the hope it is repaired. I haven't been able to boot into CWM anymore, only the download mode, so I am guessing it is fine to return it as it is?
Thanks
Click to expand...
Click to collapse
If I were you, I'd return it to something as close to stock as possible.
One suggestion: grab the latest Odin-flashable ROM for your country. You'll get a .tar.md5 file, such as P6800UBLA2_P6800ZTOLA2_ZTO.tar.md5. Try to flash it through Odin, just to see if it works; if it doesn't, write down the name of the .img file that gave you problems. If it works, congratulations, you have your tablet back, and you can stop reading.
Now, Rename that file to .tar (or, remove the .md5 extension), and open it in WinRAR/7zip/whatever. You'll see a lot of .img files inside, including the one that gave you problems. Remove it, and try to flash this new .tar file. If the flash works, proceed to the next paragraph. If it doesn't, write down the name of the .img file that gave you problems, and repeat this paragraph using your new .tar file.
After a flash that works, your device should be as close to stock as possible. Maybe it will even boot, but I wouldn't count on it (try anyway). I'd send it to the repair centre only when it is at this stage.
Steve_max said:
If I were you, I'd return it to something as close to stock as possible.
One suggestion: grab the latest Odin-flashable ROM for your country. You'll get a .tar.md5 file, such as P6800UBLA2_P6800ZTOLA2_ZTO.tar.md5. Try to flash it through Odin, just to see if it works; if it doesn't, write down the name of the .img file that gave you problems. If it works, congratulations, you have your tablet back, and you can stop reading.
Now, Rename that file to .tar (or, remove the .md5 extension), and open it in WinRAR/7zip/whatever. You'll see a lot of .img files inside, including the one that gave you problems. Remove it, and try to flash this new .tar file. If the flash works, proceed to the next paragraph. If it doesn't, write down the name of the .img file that gave you problems, and repeat this paragraph using your new .tar file.
After a flash that works, your device should be as close to stock as possible. Maybe it will even boot, but I wouldn't count on it (try anyway). I'd send it to the repair centre only when it is at this stage.
Click to expand...
Click to collapse
The tab gets stuck at 'factoryfs.img'. I'm a bit cautious since it is the biggest file in the .tar. Isn't the tab 'stock' stock enough as it is?:silly:
rumpypumpy said:
The tab gets stuck at 'factoryfs.img'. I'm a bit cautious since it is the biggest file in the .tar. Isn't the tab 'stock' stock enough as it is?:silly:
Click to expand...
Click to collapse
Thats...a...problem...if it takes longer then 15 mins its bricked...i have been a gt user and devs on other sites told me it was bricked. Maybe there is a solution but...i havnt found one. It should never take too long on one thing in odin.
Sent from the phone of Gamers
rumpypumpy said:
The tab gets stuck at 'factoryfs.img'. I'm a bit cautious since it is the biggest file in the .tar. Isn't the tab 'stock' stock enough as it is?:silly:
Click to expand...
Click to collapse
Even so, flash the other .imgs. You want to be closest to stock, including the recovery (imagine the guys at the Samsung centre manage to enter recovery, just to see CWM: your warranty is now gone). Having all partitions on stock, or at least most of them, can only help your case.
Steve_max said:
Even so, flash the other .imgs. You want to be closest to stock, including the recovery (imagine the guys at the Samsung centre manage to enter recovery, just to see CWM: your warranty is now gone). Having all partitions on stock, or at least most of them, can only help your case.
Click to expand...
Click to collapse
The warrenty is not void unless they find proof of tampering with system files. So basicly yeah...everything that guy said. Get it as close to stock as possible and send.
Sent from the phone of Gamers
Right OK, I definately don't want my warrenty void!
So would it be ok if I flashed 'P6800OXALQ1_P6800XXLQ1_HOME.tar.md5' (minus the factoryfs.img) to my tab?
Thanks
I received a Galaxy Note 1 I717 (AT&T) and it was in a bootloop. I have experience with flashing stock roms through Odin and fixing bootloops that way. So after going through recovery mode, wiping, flashing, I am still getting put into a bootloop after a successful flash on Odin. I've spent 2 days with this and tried all the little suggestions of wiping before flashing, using the original roms from XDA , trying some other stock roms specifically for my model and I'm still left with a bootloop. I'm capable of getting into download and recovery, and I've actually gotten different stock recovery modes! So the flashes are working, but it just won't boot up correctly. I looked around for the U.S. version of the Pit CSC Phone and PDA to try and re partition it, but they are absolutely NOWHERE! Any help would be greatly appreciated, whether it's a ROM suggestion, the re partition files, or whatever else.
Charles Sparkley said:
I received a Galaxy Note 1 I717 (AT&T) and it was in a bootloop. I have experience with flashing stock roms through Odin and fixing bootloops that way. So after going through recovery mode, wiping, flashing, I am still getting put into a bootloop after a successful flash on Odin. I've spent 2 days with this and tried all the little suggestions of wiping before flashing, using the original roms from XDA , trying some other stock roms specifically for my model and I'm still left with a bootloop. I'm capable of getting into download and recovery, and I've actually gotten different stock recovery modes! So the flashes are working, but it just won't boot up correctly. I looked around for the U.S. version of the Pit CSC Phone and PDA to try and re partition it, but they are absolutely NOWHERE! Any help would be greatly appreciated, whether it's a ROM suggestion, the re partition files, or whatever else.
Click to expand...
Click to collapse
A bad kernel can be the cause of this problem. Try and search for a custom kernel for your device and flash it.
I hope this will solve your problem.
Ibrahim9999 said:
A bad kernel can be the cause of this problem. Try and search for a custom kernel for your device and flash it.
I hope this will solve your problem.
Click to expand...
Click to collapse
I already tried flashing the stock Rom then flashed the kernel and got boot loops still from this XDA page http://forum.xda-developers.com/showthread.php?t=1506330 . Having a lot of trouble with this one.
Charles Sparkley said:
I already tried flashing the stock Rom then flashed the kernel and got boot loops still from this XDA page http://forum.xda-developers.com/showthread.php?t=1506330 . Having a lot of trouble with this one.
Click to expand...
Click to collapse
OK, download these files and put them on your device:
Rom: http://goo.gl/81TamM
Gapps (important!): http://goo.gl/ws5KZF
Then follow these steps exactly:
1. Boot to recovery (CWM or whatever you use)
2. Wipe data/factory reset
3. Wipe Cache
4. Wipe Dalvik cache (advanced-> wipe dalvik cache)
5. Flash rom
7. Flash the gapps
This must work, if it doesn't, please say it, maybe I can help you further.
Ibrahim9999 said:
OK, download these files and put them on your device:
Rom: http://goo.gl/81TamM
Gapps (important!): http://goo.gl/ws5KZF
Then follow these steps exactly:
1. Boot to recovery (CWM or whatever you use)
2. Wipe data/factory reset
3. Wipe Cache
4. Wipe Dalvik cache (advanced-> wipe dalvik cache)
5. Flash rom
7. Flash the gapps
This must work, if it doesn't, please say it, maybe I can help you further.
Click to expand...
Click to collapse
My bad for not properly explaining my situation, the note is stuck in a boot loop. So I can't upload files to it through drag and drop in USB. It's still capable of flashing through Odin and going into recovery with CWM, but there's no way I know of putting files onto a boot looping phone.
Charles Sparkley said:
My bad for not properly explaining my situation, the note is stuck in a boot loop. So I can't upload files to it through drag and drop in USB. It's still capable of flashing through Odin and going into recovery with CWM, but there's no way I know of putting files onto a boot looping phone.
Click to expand...
Click to collapse
Doesn't the Galaxy Note 1 I717 has a MicroSD-Card Slot?
I tought it had one..
Ibrahim9999 said:
Doesn't the Galaxy Note 1 I717 has a MicroSD-Card Slot?
I tought it had one..
Click to expand...
Click to collapse
Oh it does, would I just put those files onto a good sd card via a working phone and THEN put it into the Note?
Charles Sparkley said:
Oh it does, would I just put those files onto a good sd card via a working phone and THEN put it into the Note?
Click to expand...
Click to collapse
Yes of course, or put the files with a computer on the SDCard.
If you've put the files onto the SDCard, insert it to your Note, and follow the steps on my previous post.
Charles Sparkley said:
Oh it does, would I just put those files onto a good sd card via a working phone and THEN put it into the Note?
Click to expand...
Click to collapse
Did it work?
Ibrahim9999 said:
Did it work?
Click to expand...
Click to collapse
Just got an extra SD card my friend is letting me borrow. I'm going home tonight, putting the files on, and going to try to flash it. I'll tell you how it goes!
Charles Sparkley said:
Just got an extra SD card my friend is letting me borrow. I'm going home tonight, putting the files on, and going to try to flash it. I'll tell you how it goes!
Click to expand...
Click to collapse
OK, hope the best for you!
Ibrahim9999 said:
OK, hope the best for you!
Click to expand...
Click to collapse
Alright, so on my good phone I threw the 2 zips on my extra SD card. Then I put that SD card in the note, went into CWM, wiped the necessary areas as you said, and the dead android with a red triangle appeared. It's a long error, but the end says Error in /sdcard/cm-10.1.3-quincyatt.zip
(Status 7)
Installation aborted.
Are you sure you gave me the right ROM to install?
Charles Sparkley said:
Alright, so on my good phone I threw the 2 zips on my extra SD card. Then I put that SD card in the note, went into CWM, wiped the necessary areas as you said, and the dead android with a red triangle appeared. It's a long error, but the end says Error in /sdcard/cm-10.1.3-quincyatt.zip
(Status 7)
Installation aborted.
Are you sure you gave me the right ROM to install?
Click to expand...
Click to collapse
Status 7 means the device is incompatible, but that's impossible since we have the right ROM for your device.
OK just be sure, I'll give you another ROM and you must follow the other steps, but with the different files of course.
ROM: http://downloadandroidrom.com/file/...CARBON-JB-NIGHTLY-20131015-0513-quincyatt.zip
Google Apps: http://downloadandroidrom.com/file/gapps/gapps-jb-20130813-signed.zip
This is an Android 4.3.1 ROM so you're really up to date with this one.
Put these on a SD Card and follow the given steps in my other post.
This one has to work.
Ibrahim9999 said:
Status 7 means the device is incompatible, but that's impossible since we have the right ROM for your device.
OK just be sure, I'll give you another ROM and you must follow the other steps, but with the different files of course.
ROM: http://downloadandroidrom.com/file/...CARBON-JB-NIGHTLY-20131015-0513-quincyatt.zip
Google Apps: http://downloadandroidrom.com/file/gapps/gapps-jb-20130813-signed.zip
This is an Android 4.3.1 ROM so you're really up to date with this one.
Put these on a SD Card and follow the given steps in my other post.
This one has to work.
Click to expand...
Click to collapse
Hate to say it, but installed the new ROM file and got the same exact message. Right now I'm on CWM-based Recovery v5.5.0.4 and I flashed to stock before this, thanks for all of the help so far. Any suggestions?
Charles Sparkley said:
Hate to say it, but installed the new ROM file and got the same exact message. Right now I'm on CWM-based Recovery v5.5.0.4 and I flashed to stock before this, thanks for all of the help so far. Any suggestions?
Click to expand...
Click to collapse
Do you know for sure you're on a Galaxy Note i717 AT&T?
Because 2 roms incompatible is almost impossible.
Ibrahim9999 said:
Do you know for sure you're on a Galaxy Note i717 AT&T?
Because 2 roms incompatible is almost impossible.
Click to expand...
Click to collapse
Sorry for not getting back in a while, thanks for all the effort you've been putting into helping out.
I'm 100% positive, I'm looking at the back below where the battery goes and it says SGH-I717. I thought that model number meant for sure it was AT&T. I live in the states also if that helps.
Charles Sparkley said:
Sorry for not getting back in a while, thanks for all the effort you've been putting into helping out.
I'm 100% positive, I'm looking at the back below where the battery goes and it says SGH-I717. I thought that model number meant for sure it was AT&T. I live in the states also if that helps.
Click to expand...
Click to collapse
But don't you think it's maybe a Chinese replica with a different kernel?
If you got it cheap, that might be the case.
And can you please thank my posts?
Because the few clicks you do, help me a lot
Ibrahim9999 said:
But don't you think it's maybe a Chinese replica with a different kernel?
If you got it cheap, that might be the case.
And can you please thank my posts?
Because the few clicks you do, help me a lot
Click to expand...
Click to collapse
No it was definitely bought in the US, legit from a phone store.
Charles Sparkley said:
No it was definitely bought in the US, legit from a phone store.
Click to expand...
Click to collapse
So, for my understanding, you bought it new from the store and rooted it and then got in a bootloop?
Can you please tell me how you came in the bootloop, did you get it with flashing a ROM or a kernel etc.?
Ibrahim9999 said:
So, for my understanding, you bought it new from the store and rooted it and then got in a bootloop?
Can you please tell me how you came in the bootloop, did you get it with flashing a ROM or a kernel etc.?
Click to expand...
Click to collapse
I bought it from a friend because they had it in a boot loop. Everything on it was completely stock since they were your average user, I'm pretty sure this isn't a hardware issue either if that helps because randomly after flashing CWM one time it actually booted up and I was able to use the phone. But after rebooting, it bootlooped again :\. I haven't been able to replicate this again sadly.
Would anybody be able to provide any insight on how i could fix my s3 that appears to be stuck on boot? i received my warranty fixed device from samsung today and upon rerooting it, i forgot to unlock the bootloader i then went to the "Verizon has detected unauthorized software" screen. After which, I followed this thread http://forum.xda-developers.com/showthread.php?t=1840030 hoping to get back to stock. But after following these directions, the phone boots to a Samsung custom (Unlocked) screen and then it goes to the galaxy s3 boot screen and remains there, if anybody could provide any assistance, that would be awesome. I'd just hate to get laughed at if i bring it into a verizon store. thanks and happy holidays.
Boot into recovery and do a factory reset.
Sent from my SCH-I535 using Tapatalk 4
SlimSnoopOS said:
Boot into recovery and do a factory reset.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
I've tried that a few times already. No luck thus far
ImBarone said:
Would anybody be able to provide any insight on how i could fix my s3 that appears to be stuck on boot? i received my warranty fixed device from samsung today and upon rerooting it, i forgot to unlock the bootloader i then went to the "Verizon has detected unauthorized software" screen. After which, I followed this thread http://forum.xda-developers.com/showthread.php?t=1840030 hoping to get back to stock. But after following these directions, the phone boots to a Samsung custom (Unlocked) screen and then it goes to the galaxy s3 boot screen and remains there, if anybody could provide any assistance, that would be awesome. I'd just hate to get laughed at if i bring it into a verizon store. thanks and happy holidays.
Click to expand...
Click to collapse
What baseband are you on ?
jlyle said:
What baseband are you on ?
Click to expand...
Click to collapse
i was on vrbmf1 when i got it back but ive been trying to flash back to the stock to hopefully get out of the "unauthorized software" screen. when i tried to wipe system and data and then restart from the stock recovery menu, i got an error message saying that the directory /system didnt exist, yet ive tried flashing back to stock twice and both processes finished through odin
ImBarone said:
i was on vrbmf1 when i got it back but ive been trying to flash back to the stock to hopefully get out of the "unauthorized software" screen. when i tried to wipe system and data and then restart from the stock recovery menu, i got an error message saying that the directory /system didnt exist, yet ive tried flashing back to stock twice and both processes finished through odin
Click to expand...
Click to collapse
Are you 100% sure you was on MF1 and Verizon did not ship it to you with 4.3.
If you was on MF1 Odin should flash fine and resolve any issues. If you was on 4.3 than you have issues if you ran Odin
jlyle said:
Are you 100% sure you was on MF1 and Verizon did not ship it to you with 4.3.
If you was on MF1 Odin should flash fine and resolve any issues. If you was on 4.3 than you have issues if you ran Odin
Click to expand...
Click to collapse
1000% sure that it was 4.1.2 and MF1 because it was trying to push an OTA update that i kept canceling. should i attempt reflashing through odin again? and if so could you link me to something specifically i should flash and possibly some instructions because ive been without a phone for 2 weeks and wouldnt like to wait til october for another one....
thanks
ImBarone said:
Would anybody be able to provide any insight on how i could fix my s3 that appears to be stuck on boot? i received my warranty fixed device from samsung today and upon rerooting it, i forgot to unlock the bootloader i then went to the "Verizon has detected unauthorized software" screen. After which, I followed this thread http://forum.xda-developers.com/showthread.php?t=1840030 hoping to get back to stock. But after following these directions, the phone boots to a Samsung custom (Unlocked) screen and then it goes to the galaxy s3 boot screen and remains there, if anybody could provide any assistance, that would be awesome. I'd just hate to get laughed at if i bring it into a verizon store. thanks and happy holidays.
Click to expand...
Click to collapse
If it was fixed or replaced by Samsung they usually update to newest software before returning it. If it was on 4.3 and you tried to unlock it is now bricked beyond our ability to repair at this time.Can't unlock, flash custom recovery or downgrade to 4.1.2 or lower or it will brick. If was on 4.1.2 just need to Odin stock tar.If it hangs then a Factory reset in stock recovery will usually fix it. Need more info on what build you were actually on when started.
prdog1 said:
If it was fixed or replaced by Samsung they usually update to newest software before returning it. If it was on 4.3 and you tried to unlock it is now bricked beyond our ability to repair at this time.Can't unlock, flash custom recovery or downgrade to 4.1.2 or lower or it will brick. If was on 4.1.2 just need to Odin stock tar.If it hangs then a Factory reset in stock recovery will usually fix it. Need more info on what build you were actually on when started.
Click to expand...
Click to collapse
im completely sure it was NOT 4.3 though. it flashed fine when i ran this http://forum.xda-developers.com/showthread.php?t=2046439 i just forgot to flash the bootloader unlock through recovery so then i tried reflashing stock and now im here. and where could you point me in the direction of a stock tar and some instructions because ive been using the ones on the original thread i linked with no luck
Remove .tar from zip and flash in Odin. If was on MF! it should fix with no more than a factory reset in stock recovery. Then run Beans casual to reroot and unlock.
http://www.androidfilehost.com/?fid=23134718111254196
http://forum.xda-developers.com/showthread.php?t=2332825
prdog1 said:
Remove .tar from zip and flash in Odin. If was on MF! it should fix with no more than a factory reset in stock recovery. Then run Beans casual to reroot and unlock.
http://www.androidfilehost.com/user/settings-dev-files.php?action=show-files&flid=7111#
http://forum.xda-developers.com/showthread.php?t=2332825
Click to expand...
Click to collapse
the androidfilehost link is giving me this
"Access Denied
Sorry!
It looks like you don't have permission to access that folder. Make sure the url you are trying to access is correct.
http://forum.xda-developers.com/showthread.php?p=48799846
If you feel this is in error, please contact us."
Do you get a "PASS" when you run Odin ?. Run the tar from PR and all should be good (Iv ran it many times HA)
ImBarone said:
the androidfilehost link is giving me this
"Access Denied
Sorry!
It looks like you don't have permission to access that folder. Make sure the url you are trying to access is correct.
http://forum.xda-developers.com/showthread.php?p=48799846
If you feel this is in error, please contact us."
Click to expand...
Click to collapse
Try again with this link.
http://www.androidfilehost.com/?fid=23134718111254196
jlyle said:
Do you get a "PASS" when you run Odin ?. Run the tar from PR and all should be good (Iv ran it many times HA)
Click to expand...
Click to collapse
im currently flashing the root66.tar through odin hopefully my problem will be solved afterwards
jlyle said:
Do you get a "PASS" when you run Odin ?. Run the tar from PR and all should be good (Iv ran it many times HA)
Click to expand...
Click to collapse
ok so i no luck with the root66.tar file im going to try the other one now. should i be checking the nand erase all box?
ImBarone said:
ok so i no luck with the root66.tar file im going to try the other one now. should i be checking the nand erase all box?
Click to expand...
Click to collapse
Leave everything in odin as is..dont check or uncheck anything
Make sure u put in PDA
Make sure you have a solid connection with cable .. that will cause issues too
Your in download mode right ? HA / just checking
ImBarone said:
Would anybody be able to provide any insight on how i could fix my s3 that appears to be stuck on boot? i received my warranty fixed device from samsung today and upon rerooting it, i forgot to unlock the bootloader i then went to the "Verizon has detected unauthorized software" screen. After which, I followed this thread http://forum.xda-developers.com/showthread.php?t=1840030 hoping to get back to stock. But after following these directions, the phone boots to a Samsung custom (Unlocked) screen and then it goes to the galaxy s3 boot screen and remains there, if anybody could provide any assistance, that would be awesome. I'd just hate to get laughed at if i bring it into a verizon store. thanks and happy holidays.
Click to expand...
Click to collapse
Boot into download mode and on the screen where the option to continue or restart phone, choose to restart your phone. This worked for me just this morning, for some reason it bypasses the check.
Sent from my SCH-I535 using XDA Premium 4 mobile app
jlyle said:
Leave everything in odin as is..dont check or uncheck anything
Make sure u put in PDA
Make sure you have a solid connection with cable .. that will cause issues too
Click to expand...
Click to collapse
im trying with the stock MF1 file now. left everything checked normally as it always is in odin lets see how this goes. would it be common for a boot to hang on the "Samsung Galaxy s3" screen coming off of odin?
ImBarone said:
im trying with the stock MF1 file now. left everything checked normally as it always is in odin lets see how this goes. would it be common for a boot to hang on the "Samsung Galaxy s3" screen coming off of odin?
Click to expand...
Click to collapse
Odin will reboot your phone.. are you getting Pass in Odin ??
ImBarone said:
im trying with the stock MF1 file now. left everything checked normally as it always is in odin lets see how this goes. would it be common for a boot to hang on the "Samsung Galaxy s3" screen coming off of odin?
Click to expand...
Click to collapse
Yes. It is common for it to reboot but bootloop. Pull battery and then boot into stock recovery and factory reset. Then it should boot.
Okay, so I'm having this problem where my phone get stucks in a bootloop when I flash back to stock.
The only way it gets out of bootloop, is if I install root. The problem is I'm trying to go back to stock firmware for now, but my phone refuses to get out of the Samsung logo every single time I try and run stock.
My guess is it might have something to do with the partition.
I notice when I'm doing a factory reset/wipe.
It has consistently said how it can't mount, and I'm guessing something is wrong with my partition, because I got the right firmware for my phone. It's N-902T.
If anyone has advice on this, I'd greatly appreciate it. Right now, I have no choice but to run a rooted phone until I figure out a way to get back to stock.
Ive never seen this before
[email protected] said:
Ive never seen this before
Click to expand...
Click to collapse
Yeah, I've never seen this before either. But I've tried multiple times to simply factory reset/wipe and flash stock.
It simply stays on the Samsung logo every single time. Correct firmware and everything... I even tried smart switch and it didn't help either...
Staying rooted is the best thing you can do did you flash the wrong firmware
Sent from my SM-N920T using Tapatalk
Anthony092 said:
Yeah, I've never seen this before either. But I've tried multiple times to simply factory reset/wipe and flash stock.
It simply stays on the Samsung logo every single time. Correct firmware and everything... I even tried smart switch and it didn't help either...
Click to expand...
Click to collapse
Do this:
Backup your stuff you need first!!!
Flash root
Flash TWRP
FULL WIPE!!! EVERYTHING. Every single partition that shows, cache, internal, system, data...everything. Do it x3.
ODIN stock firmware
Jammol said:
Do this:
Backup your stuff you need first!!!
Flash root
Flash TWRP
FULL WIPE!!! EVERYTHING. Every single partition that shows, cache, internal, system, data...everything. Do it x3.
ODIN stock firmware
Click to expand...
Click to collapse
I'll try and do it and let you know how it goes.
Anthony092 said:
I'll try and do it and let you know how it goes.
Click to expand...
Click to collapse
@Jammol is correct. This method should work. Going back to stock after being rooted almost always requires a full factory reset for our device. I had to do it on my phone.
Jammol said:
Do this:
Backup your stuff you need first!!!
Flash root
Flash TWRP
FULL WIPE!!! EVERYTHING. Every single partition that shows, cache, internal, system, data...everything. Do it x3.
ODIN stock firmware
Click to expand...
Click to collapse
Akw6190 said:
@Jammol is correct. This method should work. Going back to stock after being rooted almost always requires a full factory reset for our device. I had to do it on my phone.
Click to expand...
Click to collapse
I did it, didn't work for me. Still stuck at the Samsung logo, wiped everything too..
Just to add, a few more things I did notice.
After I flashed, My System Binary is listed as Samsung Official, but the System Status is still listed as Custom, this is after I flash Stock.
Then When I go back into Recovery, to another wipe just in case after flashing, it keeps saying.
DM-Verification failed......
Need to check DRK fist...
Also says E:failed to mount/preload (No such file or directory)
Anthony092 said:
I did it, didn't work for me. Still stuck at the Samsung logo, wiped everything too..
Click to expand...
Click to collapse
Alright, try this method:
Flash latest stock firmware in ODIN
Once it's done flashing, reboot to stock recovery
do a factory reset from stock recovery
It should boot after that. This is the method I used.
---------- Post added at 10:39 PM ---------- Previous post was at 10:35 PM ----------
Anthony092 said:
Just to add, a few more things I did notice.
After I flashed, My System Binary is listed as Samsung Official, but the System Status is still listed as Custom, this is after I flash Stock.
Then When I go back into Recovery, to another wipe just in case after flashing, it keeps saying.
DM-Verification failed......
Need to check DRK fist...
Also says E:failed to mount/preload (No such file or directory)
Click to expand...
Click to collapse
In this case, use the method I posted above, but try re-downloading the latest firmware for your device from sammobile.com and flash that. It should overwrite all of your partitions and then simply require a factory reset from stock recovery to boot. If that doesn't work, you may need to flash the PIT file for your device, which I'm sure can be found somewhere around here. I'm not sure the exact method to do that, however.
Akw6190 said:
Alright, try this method:
Flash latest stock firmware in ODIN
Once it's done flashing, reboot to stock recovery
do a factory reset from stock recovery
It should boot after that. This is the method I used.
Click to expand...
Click to collapse
I tried already, didn't work, but I'll keep looking to see if I can fix it. The minute I Put root back on my phone, it immediately started working, however every single time I try to go back to stock, it never gets past the Samsung Logo, No matter how many times I do a wipe. Plus, I don't understand why it keeps showing my device as custom, but the binary as samsung official, after I'm flashing stock...
Anthony092 said:
I tried already, didn't work, but I'll keep looking to see if I can fix it. The minute I Put root back on my phone, it immediately started working, however every single time I try to go back to stock, it never gets past the Samsung Logo, No matter how many times I do a wipe. Plus, I don't understand why it keeps showing my device as custom, but the binary as samsung official, after I'm flashing stock...
Click to expand...
Click to collapse
Hm. Unfortunately this is beyond my realm of comprehension. I've read that flashing the PIT file could help, but I don't know how to do that, unfortunately. I'd do some research on that if I were you.
Anthony092 said:
I tried already, didn't work, but I'll keep looking to see if I can fix it. The minute I Put root back on my phone, it immediately started working, however every single time I try to go back to stock, it never gets past the Samsung Logo, No matter how many times I do a wipe. Plus, I don't understand why it keeps showing my device as custom, but the binary as samsung official, after I'm flashing stock...
Click to expand...
Click to collapse
Try this. Go into developer mode and see if your oem unlocking is off. Turn it on. Make sure you have Odin version .7 and make sure you update to the latest firmware for you device.
Akw6190 said:
Hm. Unfortunately this is beyond my realm of comprehension. I've read that flashing the PIT file could help, but I don't know how to do that, unfortunately. I'd do some research on that if I were you.
Click to expand...
Click to collapse
Well you tried, thank you I appreciate the help nonetheless. I'll try and research it more, for now I'll just stay rooted and explore and find options to fix it, enjoy your day.
Anthony092 said:
Well you tried, thank you I appreciate the help nonetheless. I'll try and research it more, for now I'll just stay rooted and explore and find options to fix it, enjoy your day.
Click to expand...
Click to collapse
You too, buddy. If you figure it out, report back and let us know. It may help someone in the future.
guaneet said:
Try this. Go into developer mode and see if your oem unlocking is off. Turn it on. Make sure you have Odin version .7 and make sure you update to the latest firmware for you device.
Click to expand...
Click to collapse
My OEM is on, I'm downloading the lastest firmware. I'll report back with my results
Anthony092 said:
My OEM is on, I'm downloading the lastest firmware. I'll report back with my results
Click to expand...
Click to collapse
Here is a link to the latest firmware just in case. Really fast download compared to sammobile
http://forum.xda-developers.com/showthread.php?p=64366446
guaneet said:
Here is a link to the latest firmware just in case. Really fast download compared to sammobile
http://forum.xda-developers.com/showthread.php?p=64366446
Click to expand...
Click to collapse
Thank you, very much appreciated it. I'll download from there instead =)
I've been pondering this one all day. It shouldn't be a corrupt storage device that's now dead because it would work regardless of root or not. The pit file suggested earlier should do the trick as it writes over all partitions of your device.
Another thing. It says both official and custom in download mode is an indication that something get wiped. What firmware have you been trying to flash with odin
S?ent from my SM-N920T using Tapatalk
Jammol said:
I've been pondering this one all day. It shouldn't be a corrupt storage device that's now dead because it would work regardless of root or not. The pit file suggested earlier should do the trick as it writes over all partitions of your device.
Another thing. It says both official and custom in download mode is an indication that something get wiped. What firmware have you been trying to flash with odin
S?ent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
I was flashing N902TUVU2COI5, however I'm going to try and flash the latest firmware and see how it goes.
Unfortunately, I haven't found anything exactly telling me how to the pit file, so I'm for now going to stay away from that...just waiting for the latest firmware to download and I'll flash it and post my results.