after a FULL wipe bad flash to cm12 on my part, i restored with odin 3.09 with g900auc1ance firmware. it shows success on odin, but upon reboot, i still get the samsung "custom" with open padlock. then it attempts to boot and the samsung logo does it's thing and only completes about 80% of the logo, then goes dead/blank with blue led lightly pulsing. i took it to bestbuy to the samsung kiosk hoping the tech could help. he scolded me and showed me his at&t s5 running cm12. i'm stumped. any help would be appreciated.
i've rooted and rommed every android i've had and have always been able to fix it., all thanks to XDA.
Could it have been a bad download of ANCE. I've seen that happen before. Either a bad download or a bad transfer from comp/phone to sd card. I'd try re downloading
will do
will try that now. hoping it works.
nope. tried and same results.
Perhaps try Odin 3.10? Could it be that simple.
Also did you try a different source for the file you were trying to flash?
magnumglock said:
after a FULL wipe bad flash to cm12 on my part, i restored with odin 3.09 with g900auc1ance firmware. it shows success on odin, but upon reboot, i still get the samsung "custom" with open padlock. then it attempts to boot and the samsung logo does it's thing and only completes about 80% of the logo, then goes dead/blank with blue led lightly pulsing. i took it to bestbuy to the samsung kiosk hoping the tech could help. he scolded me and showed me his at&t s5 running cm12. i'm stumped. any help would be appreciated.
i've rooted and rommed every android i've had and have always been able to fix it., all thanks to XDA.
Click to expand...
Click to collapse
Number one you CANNOT run CM 12 or ANY AOSP or custom kernel on the G900A due to the locked bootloader whoever told you that flat lied to you
I'm assuming you've taken the 444 update correct??
Go to this thread http://forum.xda-developers.com/showthread.php?t=3021120read OP scroll down to the troubleshooting section and download the downgrade to NCE rar. Extract the downgrade to NCE tar md5 place phone in download plug it in and using Odin 3.09 place the tar in the ap slot then flash let it complete wait til phone boots then you'll be back to bone stock NCE phone.
I did the 4.4.4 and I'll give this a shot this evening. Again, thank you for the help.
*edit*
I have not tried Odin 3.10. I downloaded the files from the restore threads link to a google drive storage.
Odin 3.10 works fine. Don't forget to wipe cache and Davi. Sometimes that's all you need. And I agree, do some research first before you try flashing anything. Our locked bootloader makes us different.
Will do. I'll update what I find this evening.
magnumglock said:
I did the 4.4.4 and I'll give this a shot this evening. Again, thank you for the help.
*edit*
I have not tried Odin 3.10. I downloaded the files from the restore threads link to a google drive storage.
Click to expand...
Click to collapse
OK I figured you took the 4.4. 4 update go to the link I provided and if you read OP it states that if one has trouble with the first downgrade rar to go to the troubleshooting section.
Download the Downgrade to NCE rar in the troubleshooting section and extract the Downgrade to NCE md5 tar.
Using Odin 3.09 put phone into download mode plug it in you'll see added in the box.
Place the Downgrade to NCE tar md5 file into ap slot and press start it will work. I've done it several times myself and helped quite a few people in your place as well
Let phone completely boot up and you'll have a bone stock device ready to start over.
OPOfreak said:
OK I figured you took the 4.4. 4 update go to the link I provided and if you read OP it states that if one has trouble with the first downgrade rar to go to the troubleshooting section.
Download the Downgrade to NCE rar in the troubleshooting section and extract the Downgrade to NCE md5 tar.
Using Odin 3.09 put phone into download mode plug it in you'll see added in the box.
Place the Downgrade to NCE tar md5 file into ap slot and press start it will work. I've done it several times myself and helped quite a few people in your place as well
Let phone completely boot up and you'll have a bone stock device ready to start over.
Click to expand...
Click to collapse
this solved my problem. i cannot express how appreciative i am for your help.
magnumglock said:
this solved my problem. i cannot express how appreciative i am for your help.
Click to expand...
Click to collapse
A simple thank you is sufficient I'm glad you're squared away now.
The good thing is now if you soft brick your device you know how to get back to stock.
Happy flashing :thumbup::thumbup:
The same exact thing has happened to me.
OK, I am panicking now. My ATT GS5 is doint the exact same thing.
I will try the NCE rar too and let ya'll know how it went.
---------- Post added at 11:27 PM ---------- Previous post was at 10:59 PM ----------
Dodged that bullet. Got rid of Custom status too. Very cool
I am having the same issue but with a "there is no PIT partiton" error
I have tried everything that I could to get my phone working again. I even downloaded a so called pit file that apparently didn't work because the error keeps coming up. Is there a legit PIT file that I can download and if so could someone please point me in that direction? Also if someone could please help me to get my phone working again I would also appreciate that. I just bought this phone off of ebay and I am trying to get it working as my regular phone. when I start the phone up there are two lines at the top of the screen 1 is a white line that says MMC read fail error or something to that effect, and there's another line in red that says movinand confirmation error. After about 3 to 4 minutes of waiting the phone will go into download mode by itself and give me a whole bunch of lines one of which will say: Knox 0x0.
is there a way I can either repair or repartition the phone? I spent 6 hours trying to figure this out. I am tired.
Thanks in advance for any helpful response.
Related
I need the Stock Firmware version G900AUCU2AND3 So that I can flash back to stock. In the thread return to stock it has the previous version G900AUCU1ANCE. I get a error when trying to odin back (SW REV CHECK FAIL : [about]Fused 2 > Binary 1). So I am not sure how its done but need someone who has it do a dump or how ever its done to get it in a way that it can be flashed either by odin or in recovery... Any help will be appreciated... Thanks
i will need this too, i have my phone on at&t next and after a year i can trade it in, but if its custom os and stuff i cant return it, so i will need this too if i want to return to stock so i can upgrade to a new phone next year.
Bump: This is needed very badly. As I imagine many people had to take that bloat ware update. If anyone that has this firm ware has a problem and needs to restore back to stock. They won't be able to use the one that's listed in on this forum as its the older one, and now that there is Root. Its very likely this will happen daily that people will need it. I don't know exactly what soft bricked my phone so it can happen to anyone. My phone was fine until a reboot. Please, please, please. I'm begging everyone that has it. I asked Samsung and they wouldn't help. Next maybe going to AT&T store and having warranty claim done. I don't really want to find the out come of that.
I need this very badly as well. I rooted my phone and then tried to alter my screen density via an app I found on Google Play. It requested root, I granted the permission and then when the phone rebooted it hung on "Samsung Galaxy S5" splash screen and will no go any further. ODIN will not allow me to flash G900AUCU1ANCE firmware since I did the OTA update. If anyone could post up their G900AUCU2AND3, I would appreciate it very much.
kwikrat said:
I need this very badly as well. I rooted my phone and then tried to alter my screen density via an app I found on Google Play. It requested root, I granted the permission and then when the phone rebooted it hung on "Samsung Galaxy S5" splash screen and will no go any further. ODIN will not allow me to flash G900AUCU1ANCE firmware since I did the OTA update. If anyone could post up their G900AUCU2AND3, I would appreciate it very much.
Click to expand...
Click to collapse
I estimate we will get @ least One to two of these per-day until we get the files. Since we now have Root. It may take a bit as At&t version don't seem to have much for devs. Or ones that care to really help.(I'll probably get reamed for this. Sorry for you that help and for your time) I contacted At&t they told me they could not help but I could send my phone in for warranty exchange. Its that or go to BestBuy and they can flash it back. I don't have a Bestbuy Nearby.
Guys, check that post. Shortydoggg found a temporary fix for any soft bricks. It's for extreme cases. My phone is fine (apart from some deleted stock apps) so I'll hold off until i get some more info but if you cant boot at all, his method should come in handy.
http://forum.xda-developers.com/showthread.php?t=2785185&goto=newpost
+1 :highfive:
NotDavid said:
Guys, check that post. Shortydoggg found a temporary fix for any soft bricks. It's for extreme cases. My phone is fine (apart from some deleted stock apps) so I'll hold off until i get some more info but if you cant boot at all, his method should come in handy.
http://forum.xda-developers.com/showthread.php?t=2785185&goto=newpost
Click to expand...
Click to collapse
Thank you. The above link solved my problem. I am back up and running! At first data wasn't working other than wi-fi but I merely had to re-enter my APN that I got from here: http://forum.xda-developers.com/showthread.php?t=2746380 :good:
can you update to G900AUCU2AND3 after flashing this?
dave1977nj said:
can you update to G900AUCU2AND3 after flashing this?
Click to expand...
Click to collapse
YUP, I did the AT&T update check and got it immediately afterwards. I instead of flashing every one separately and rebooting loaded the three files so minus the Bl file. I did not have the problems of having to reload APN this way.
pcidiot said:
YUP, I did the AT&T update check and got it immediately afterwards. I instead of flashing every one separately and rebooting loaded the three files so minus the Bl file. I did not have the problems of having to reload APN this way.
Click to expand...
Click to collapse
Thanks!!! :good:
pcidiot said:
YUP, I did the AT&T update check and got it immediately afterwards. I instead of flashing every one separately and rebooting loaded the three files so minus the Bl file. I did not have the problems of having to reload APN this way.
Click to expand...
Click to collapse
A flash of the CSC file restores the APN after flashing the AP file, or flashing it together with the AP file, but it factory resets the phone. Flashing the AP file only is mostly for those who do not want a factory reset. But, a factory reset along with flashing only the AP file will indeed wipe the APN. I found all of that out through trial and error.
shortydoggg said:
A flash of the CSC file restores the APN after flashing the AP file, or flashing it together with the AP file, but it factory resets the phone. Flashing the AP file only is mostly for those who do not want a factory reset. But, a factory reset along with flashing only the AP file will indeed wipe the APN. I found all of that out through trial and error.
Click to expand...
Click to collapse
Thanks for your trials this will be useful to many.
pcidiot said:
Thanks for your trials this will be useful to many.
Click to expand...
Click to collapse
No problem.
dave1977nj said:
can you update to G900AUCU2AND3 after flashing this?
Click to expand...
Click to collapse
Yes do not root first, flash it then wait a few minutes then do a check for updates it will download the crap update with the yp yellow pages app,
then reboot and root
and take it away !!
pcidiot said:
Bump: This is needed very badly. As I imagine many people had to take that bloat ware update. If anyone that has this firm ware has a problem and needs to restore back to stock. They won't be able to use the one that's listed in on this forum as its the older one, and now that there is Root. Its very likely this will happen daily that people will need it. I don't know exactly what soft bricked my phone so it can happen to anyone. My phone was fine until a reboot. Please, please, please. I'm begging everyone that has it. I asked Samsung and they wouldn't help. Next maybe going to AT&T store and having warranty claim done. I don't really want to find the out come of that.
Click to expand...
Click to collapse
Same troubles here pcidiot!!!! soft bricked and nothing will load onto the phone. ODIN gives me the same kind of error as listed on the starting thread! I can get to recovery mode and Download (ODIN) mode on the phone but nothing wants to flash. Do we dump? Do we Erase Nand? CONFUSING!!! why is it so easy to bunk up a phone!
Achilles5410 said:
Same troubles here pcidiot!!!! soft bricked and nothing will load onto the phone. ODIN gives me the same kind of error as listed on the starting thread! I can get to recovery mode and Download (ODIN) mode on the phone but nothing wants to flash. Do we dump? Do we Erase Nand? CONFUSING!!! why is it so easy to bunk up a phone!
Click to expand...
Click to collapse
There should only be two boxes checked in odin thats f. reset time and auto reboot. Also Make sure you only check and load your firmware in the ap slot in odin. Now flash.
Achilles5410 said:
Same troubles here pcidiot!!!! soft bricked and nothing will load onto the phone. ODIN gives me the same kind of error as listed on the starting thread! I can get to recovery mode and Download (ODIN) mode on the phone but nothing wants to flash. Do we dump? Do we Erase Nand? CONFUSING!!! why is it so easy to bunk up a phone!
Click to expand...
Click to collapse
Are you following this guide?
http://forum.xda-developers.com/showpost.php?p=53454972&postcount=1
shortydoggg said:
Are you following this guide?
http://forum.xda-developers.com/showpost.php?p=53454972&postcount=1
Click to expand...
Click to collapse
Yea I did thank you. Did it today and thanked the poster too.
Want to start over! Need help!
So I want to do whats written out in step 4 of shorttydogs thread but I don't want to mess up or brick my phone. My goal is to start over and go back to stock with bloatware and everything that is available on stock if I were to go AT&T and buy it today. Here is a little background on my phone. My phone is rooted and I do have safestrap (and busybox). I backed up everything on my microSD card. I also have the g900AUCU2AND3 firmware on my phone. In addition, I deleted some but not all AT&T bloatware, which I want back. Lastly, for some reason the "add call button" during my calls is missing and was replaced with a "record" button I think this was because of me playing around with xposed. I deleted xposed framework as well as wanam and tried everything to get the "add call button" back but I couldn't. Thus, I just want to go back to stock to fix all these issues. I just have a few questions before I proceed just to make sure I'm not doing anything wrong.
1) If I flash the AP, CP and CSC files will I achieve 100% stock with bloatware?
2) Will this return my "add call button"?
3) Is it as simple as just using odin 3.09 and flashing the AP, CP, and CSC files?
4) I also understand that this will take me back to G900AUCU1ANCE but will I be able to do an OTA do go to G900AUCU2AND3?
5) Is there anything else I need to know to prevent my phone from bricking!
Sorry for the long post but I am fairly new to this stuff and don't want mess anything up!
I had battery issues with my Note GT-N7000. I purchased the original battery from samsung service center. Phone did restarted several times due to low battery. After one such incident it was not accepting my correct pattern. After some time it just stopped getting start up.
Then i tried to enter into recovery mode. It got stucked at android green logo, wheel spinning every single time.
But download mode is still working. I tried to re-flash it with stock firmware as i was running it before this problem occurred (stock with root).
I followed flashing instructions extremely carefully and as they instruct. When i put my phone into download mode, it got successfully recognized by my computer, But while flashing it got stucks at flashing factoryfs.img, ""NAND write start"" and followed by ""complete write operation failed"".
I did changed my original usb cable to another original cable. My antivirus and firewall are turned off permanently. I did tried it on another computer but same result. Downloaded my firmware from sammobile twice. Did tried different Odin versions from 1.83 to 3.07. But no luck at all. I am attaching my screenshots so that you can have a look.
Please help me out in any way you can. Any links or help will be highly appreciated from the bottom of my heart. Thanks in advance for your reply.
Did you have a ROM on it that required you to change the PIT file? If there is a different partition scheme that could cause an issue. Also try unchecking f reset time.
Sent from my SM-G900T using XDA Premium HD app
zombieplanalpha said:
Did you have a ROM on it that required you to change the PIT file? If there is a different partition scheme that could cause an issue. Also try unchecking f reset time.
Sent from my SM-G900T using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for your quick response. I do not have a ROM that require me to change PIT information. I was on pure stock with root before this issue came up. I did unchecked reset time but same error came up.
Different partition scheme...? As far as i know, i didnt do anything to my partitions.
You bricked your device. Search for threads with "factoryfs.img" and you'll find answers (repartition, replace MB or follow hg42's thread).
And you'll might find your post from Nov 2012 when you had a problem like this before but "solved" it.
ThaiDai said:
You bricked your device. Search for threads with "factoryfs.img" and you'll find answers (repartition, replace MB or follow hg42's thread).
And you'll might find your post from Nov 2012 when you had a problem like this before but "solved" it.
Click to expand...
Click to collapse
So is there any possibility of restoring the data?
Negative. Custom recovery and frequent backups along with an app like titanium backup would have been good to have before this happened
Sent from my SM-G900T using XDA Premium HD app
zombieplanalpha said:
Negative. Custom recovery and frequent backups along with an app like titanium backup would have been good to have before this happened
Sent from my SM-G900T using XDA Premium HD app
Click to expand...
Click to collapse
I do have the backup but its more than 2 months old...but i cannot go into stock recovery....i should have installed cutom recovery. Any links to follow or any proper guides to come out from it?
http://forum.xda-developers.com/showthread.php?t=1667886
ThaiDai said:
http://forum.xda-developers.com/showthread.php?t=1667886
Click to expand...
Click to collapse
As per the article and since i cannot enter into recovery mode, i tried all the PIT files provided with stock rom. But nothing has worked. Every time Odin is failing. I am attaching the screenshot of the same. I did tried to flash speedmod kernel but didnt got success message from Odin. Kindly help me.
i have used custom PIT files due to which my binary counter has increased(i dont care as its out of warranty). My phone shows a yellow warning sign on bootup and now it just dont even start the recovery mode and shows that yellow warning sign when i try to enter recovery.
Download mode is still working but i am unable to perform any write operation. NAND operation is failing everytime. When i used PIT files, it says re-partition operation failed. I can only try things mentioned in the above posts only when i can enter recovery.
Will someone be kind enough to help me out on this one as i really need urgent help? Please help me out guys.
I think you didn't read hg42's thread and didn't follow his big bold red warnings.
Brute Force experiments with different pit files made it only more difficult or impossible.
In his thread there is a link to another thread related to the problem
http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
forest describes a manual method to check for errors including a repair option by scanning the device with e2fsck in chapter 4.2.
I remember some users who solved the brick with factorfs.img with this method (at least I remember one where nokiamode gave that hint).
Try this and follow forest`s instructions carefully.
You tried flashing PhilZ-cwm6-DDLSC kernel tar file fusing odin?
ThaiDai said:
I think you didn't read hg42's thread and didn't follow his big bold red warnings.
Brute Force experiments with different pit files made it only more difficult or impossible.
In his thread there is a link to another thread related to the problem
http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
forest describes a manual method to check for errors including a repair option by scanning the device with e2fsck in chapter 4.2.
I remember some users who solved the brick with factorfs.img with this method (at least I remember one where nokiamode gave that hint).
Try this and follow forest`s instructions carefully.
Click to expand...
Click to collapse
Thanks for replying. I did read that article carefully but all steps and troubleshooting is valid only and only when your phone's recovery mode is working. In my phone, only download mode is working. So all those steps are not applicable to me.
However i went for case B where he has described solution if we are unable to access recovery mode and suggested to use blind method to use custom pit files. I followed him but it didn't worked out for me. None of the pit files worked for me and i just ended up raising my binary counter to 2 now.
I am not receiving any replies from people(Only 2 or 3 kind people like you have replied, i appreciate it). I am not getting support. Its reallly sad just because my phone is little old now.
Even if i didn't find any solution and my phone becomes a brick( i guess it has become by now) it is still fine for me But the most sad thing is no one cares to reply on a community which was built to help each others. I am continuosly searching for solutions now. Lets see how far i can go. Thanks for your time. Do let me know if you come across any thing or i am ready to try any solution/troubleshooting steps.
nokiamodeln91 said:
You tried flashing PhilZ-cwm6-DDLSC kernel tar file fusing odin?
Click to expand...
Click to collapse
I have downloaded Philz-cwm6-DDLSC tar file....I'll be flashing it soon and'll let you know for sure
vinay28761 said:
I have downloaded Philz-cwm6-DDLSC tar file....I'll be flashing it soon and'll let you know for sure
Click to expand...
Click to collapse
No progress...it just got failed again.....I will get the motherboard replaced by samsung...It'll cost me 170+ USD, original motherboard and a new original battery as well.
vinay28761 said:
No progress...it just got failed again.....I will get the motherboard replaced by samsung...It'll cost me 170+ USD, original motherboard and a new original battery as well.
Click to expand...
Click to collapse
Have you tried another pc, and genuine USB cable by Samsung?
nokiamodeln91 said:
Have you tried another pc, and genuine USB cable by Samsung?
Click to expand...
Click to collapse
Yes i tried on different pc, different cables(all are genuine)
So, I bought a rooted I537 and unrooted it with SuperUser. It has Baseband i537UCUAMF3;
Kernel Version 3.4.0-784654
[email protected] #1
Wed June 12 20:01:35 KST 2013
Build Number
JDQ39.i537UCUAMF3
I want to get to KitKat. I was attracted to the S4 for NFC payments but can't do that with 4.2.2. Can any of you figure out the problem?
change your USB cable and retry....
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app
tet1 said:
change your USB cable and retry....
I would have guessed you wrong given that Odin recognized my phone without a problem, but had nothing else to try. I tried switching to the usb cord I charge my phone with every night. That charges it fully so I thought it was a good sign. FAIL! Next, I took advantage of my daughter being out of the house and swiped her genuine Samsung cord she got with her Verizon phone. SUCCESS!
It worked. Thanks for your help!
So, for those of you playing along at home, to get to the latest Kitkat OS from a rooted 4.2.2 I537 S4, I had to unroot with SuperUser, install ML2, then NE3, then finally NH3
Click to expand...
Click to collapse
Crap, seem to have fried my phone. I tried to get from ML2 to NE3 with the OTA method. When the phone rebooted, it got stuck at the AT&T splash logo which didn't even look right. There was blue diagonally on the left bottom corner. I tried waiting to see if it would finish booting then eventually pulled the battery. When I rebooted, I saw the same damaged splash screen then it went to the initial setup screen where you choose your language. This deteriorated quickly and became unreadable
Any suggestions?
Booting into recovery mode also quickly deteriorates.
Booting into download mode looks fine, but attempting an Odin install of ML2 quickly fails.
Odin install of NE3 fails right away too.
p.s. where are you supposed to put the update.zip file? I put it in the root of my memory card.
Tried booting again. It's useable, but looks horrid. Try NH3 OTA?
Now 15 minutes later, the color is back but the touch screen is completely unresponsive.
LuckyInOhio said:
Tried booting again. It's useable, but looks horrid. Try NH3 OTA?
Now 15 minutes later, the color is back but the touch screen is completely unresponsive.
Click to expand...
Click to collapse
You should just flash the NE3 Odin package until it works. Just for future reference, you should have just upgraded to NE3 directly, there is no reason you should have flashed ML2 in the first place.
Well, trying to reflash the NE3 Odin package and it keeps failing. I think I saw "no pit partition" so I tried to find a PIT file to re-partition. I found a file named I537_18-4-2014_0-4-56.pit at 8kb in these forums, but that keeps failing too. Can anyone with a rooted i537 kitkat upload their pit file?
Hi all
I've been trying for weeks for a solution so finally making a post of my own.
I have a GG1 that I've been trying to get working on my HTC One M8 and it's all gone a bit wrong.
I had tried to Flash TWRP and then Null ROM but couldn't get it to work. I then tried to downgrade from Tizen using the Pit file and 2 .tar files that are on this forum but now it's just not doing anything like what it should.
No matter what I do (Re-partitioning, flashing stock/TWRP, flashing MK7) all I get is the Samsung Logo splash screen on boot - 'no matter what'. Any way you guys can suggest to completely start again with this? Perhaps a new Pit file that isn't the downgrade?
I can open Download mode and recovery (when TWPR is flashed) no problem. But if I try to flash anything in TWRP, all I get is something like 'E:Unable to mount /data/' - same if I try to sideload - though pushing files via adb seems to work.
Oh, it's the UK GG1 V700.
Thanks in andvance
catfinger said:
Hi all
I've been trying for weeks for a solution so finally making a post of my own.
I have a GG1 that I've been trying to get working on my HTC One M8 and it's all gone a bit wrong.
I had tried to Flash TWRP and then Null ROM but couldn't get it to work. I then tried to downgrade from Tizen using the Pit file and 2 .tar files that are on this forum but now it's just not doing anything like what it should.
No matter what I do (Re-partitioning, flashing stock/TWRP, flashing MK7) all I get is the Samsung Logo splash screen on boot - 'no matter what'. Any way you guys can suggest to completely start again with this? Perhaps a new Pit file that isn't the downgrade?
I can open Download mode and recovery (when TWPR is flashed) no problem. But if I try to flash anything in TWRP, all I get is something like 'E:Unable to mount /data/' - same if I try to sideload - though pushing files via adb seems to work.
Oh, it's the UK GG1 V700.
Thanks in andvance
Click to expand...
Click to collapse
Sounds confusing. Not knowing exactly what you tried or what you have flashed, start over. If you can get to download mode try putting on a stock image and see what that gets you. Its not bricked if it boots and you can get to download and recovery. Sounds more like a cable issue, bad download or something. Here's my copy folder that has ne9 and nf1, do ne9 first as nf1 is not a full ROM.
---------- Post added at 03:38 PM ---------- Previous post was at 03:30 PM ----------
catfinger said:
Hi all
I've been trying for weeks for a solution so finally making a post of my own.
I have a GG1 that I've been trying to get working on my HTC One M8 and it's all gone a bit wrong.
I had tried to Flash TWRP and then Null ROM but couldn't get it to work. I then tried to downgrade from Tizen using the Pit file and 2 .tar files that are on this forum but now it's just not doing anything like what it should.
No matter what I do (Re-partitioning, flashing stock/TWRP, flashing MK7) all I get is the Samsung Logo splash screen on boot - 'no matter what'. Any way you guys can suggest to completely start again with this? Perhaps a new Pit file that isn't the downgrade?
I can open Download mode and recovery (when TWPR is flashed) no problem. But if I try to flash anything in TWRP, all I get is something like 'E:Unable to mount /data/' - same if I try to sideload - though pushing files via adb seems to work.
Oh, it's the UK GG1 V700.
Thanks in andvance
Click to expand...
Click to collapse
Edited my post. Responding incase you read the original one.
Ducter said:
Edited my post. Responding incase you read the original one.
Click to expand...
Click to collapse
Thanks mate, that worked. I now have the watch back to asking me to pair with a phone.
One last thing, can you point me in the right direction to getting this rooted and ROMed without having to connect to a Samsung first? I'm on HTC One M8 so can't go down the cydia impactor route.
catfinger said:
Thanks mate, that worked. I now have the watch back to asking me to pair with a phone.
One last thing, can you point me in the right direction to getting this rooted and ROMed without having to connect to a Samsung first? I'm on HTC One M8 so can't go down the cydia impactor route.
Click to expand...
Click to collapse
People have different degrees of success with your set up. Here is a post you can read and decide for yourself. Other option is go back to android on your watch, specifically null, try that. If it fails you can delete...forgot the exact name sec.setup.Samsung or something like that from the null zip then flash it, basically turns your watch into full blown android but missing most the watch features leaving you with finding third party apps to do what you want.
I got fed up trying to get my watch working with my note 3 on aosp lollipop and ended up flashing a Samsung ROM. On kit kat everything worked well enough for me, lollipop, not so much.
if you used the ROMs I linked they are rooted already. Just Google galaxy gear on non Samsung phone, you'll find plenty of info.
It seems that I may have flashed one to many times or something else is playing up. Anywho, I came to check my phone this morning and everything was working fine. Checked the battery status and I thought it was time for a top-up . I decide to do it via USB via my computer and that's when things started to go south. I came back to check my phone and...nothing. I done a hard restart and at first everything seemed fine only to get a continuous boot-loop. I tried to enter TWRP and it hangs on the "teamwin" logo. Then I decided to flash stock via Odin and I still get the same boot-loop. I can still access downloader but that's it.
For reference the version of TWRP I was running was 2.8.6.1 (flashed back to 2.8 Nova version) and the ROM I was running was the latest version of Ressurection Remix by Maclaw.
So, I'm open to any suggestions. Any help would be much appreciated and paid forward.
Thanks for hearing me out.
So going by the lack of feedback I'm basically screwed?
Oh for ****s sake come on! I've had this up for 3 days on this site full of so called enthusiasts and "professionals" and not one response? I'm sorely disappointed.
So there is honestly no one that can help me with this?
Pathetic...
Come on there must be someone that can help me with this, otherwise I'll have to risk buying a broken one for parts.
Haven't done any custom stuff in a while but the boot loop sounds familiar, have you wiped the dalvik cache in the advanced menu also have you tried a factory reset?
---------- Post added at 12:35 PM ---------- Previous post was at 12:30 PM ----------
Use the Volume keys in order to navigate through the recovery menu.
Select “advanced” and choose “wipe dalvik cache”.
Return to main menu.
Then select “wipe data factory reset”.
Return and this time choose “wipe cache partition”.
Return and select “reboot system now”.
Your handset should start in Android OS now.
Grumpy Cat said:
It seems that I may have flashed one to many times or something else is playing up. Anywho, I came to check my phone this morning and everything was working fine. Checked the battery status and I thought it was time for a top-up . I decide to do it via USB via my computer and that's when things started to go south. I came back to check my phone and...nothing. I done a hard restart and at first everything seemed fine only to get a continuous boot-loop. I tried to enter TWRP and it hangs on the "teamwin" logo. Then I decided to flash stock via Odin and I still get the same boot-loop. I can still access downloader but that's it.
For reference the version of TWRP I was running was 2.8.6.1 (flashed back to 2.8 Nova version) and the ROM I was running was the latest version of Ressurection Remix by Maclaw.
So, I'm open to any suggestions. Any help would be much appreciated and paid forward.
Thanks for hearing me out.
Click to expand...
Click to collapse
TheMadTurnip said:
Haven't done any custom stuff in a while but the boot loop sounds familiar, have you wiped the dalvik cache in the advanced menu also have you tried a factory reset?
---------- Post added at 12:35 PM ---------- Previous post was at 12:30 PM ----------
Use the Volume keys in order to navigate through the recovery menu.
Select “advanced” and choose “wipe dalvik cache”.
Return to main menu.
Then select “wipe data factory reset”.
Return and this time choose “wipe cache partition”.
Return and select “reboot system now”.
Your handset should start in Android OS now.
Click to expand...
Click to collapse
Thanks for the feedback but as I have already stated I can't access any recovery only Odin, and desktop Odin won't allow me to re-partition only write. Still, whether it be stock or a custom ROM it is the same result: bootloop and recovery freezes on splash screen.
So any other takers? Yes? No?
Why even have a "help & troubleshooting" section if, well, I don't know, no one helps!!!
Dude you're puerile attitude is baffling, I understand you desperately want help, but do you really think you'll get it if you keep throwing toys out of your pram?
The problem you've described suggests that you're phone is 'fixable' however, it may take a few different methods to restore it. Ok, so you cannot access recovery mode, therefore you're unable to clear your phone like TheMadTurnip suggested, and you're also unable to access any backup you might have made. The downloader works so I can only recommend you try to investigate what's going wrong when you flash via Odin, does the flash show as pass or fail? Have you tried flashing using a different cable or computer, heck have you even tried using another version of Odin? Is Kies installed on your computer, if so then remove it. Have you flashed using a PIT file as well as the stock firmware? Elaborate on your situation so tailored advice can be given to you.
Kind Regards,
Pinda
Pinda007 said:
Dude you're puerile attitude is baffling, I understand you desperately want help, but do you really think you'll get it if you keep throwing toys out of your pram?
Click to expand...
Click to collapse
In light of how active this section still is I think a week is more than enough time to expect a response, I was even quite polite in my OP. Even a simple "no I can't help but maybe try this" would have sufficed. But I'll take it under advisement...
Pinda007 said:
does the flash show as pass or fail?
Click to expand...
Click to collapse
It shows a pass, won't allow me to re-partition though.
Pinda007 said:
Have you tried flashing using a different cable or computer, heck have you even tried using another version of Odin?
Click to expand...
Click to collapse
I have tried flashing using the original cable the phone came with; so I have tried 2. I even tried other USB ports. And yes I have tried another version of Odin.
Flashing doesn't seem to be a problem at the moment, just everything else.
Pinda007 said:
Is Kies installed on your computer, if so then remove it.
Click to expand...
Click to collapse
It is installed along with the Samsung USB driver. Having it installed hasn't caused a problem. I'll uninstall it if you think that will help.
Pinda007 said:
Have you flashed using a PIT file as well as the stock firmware? Elaborate on your situation so tailored advice can be given to you.
Click to expand...
Click to collapse
A pit file? And yes, as I have already mentioned I have installed the stock firmware.
Grumpy Cat said:
In light of how active this section still is I think a week is more than enough time to expect a response, I was even quite polite in my OP. Even a simple "no I can't help but maybe try this" would have sufficed. But I'll take it under advisement...
It shows a pass, won't allow me to re-partition though.
I have tried flashing using the original cable the phone came with; so I have tried 2. I even tried other USB ports. And yes I have tried another version of Odin.
Flashing doesn't seem to be a problem at the moment, just everything else.
It is installed along with the Samsung USB driver. Having it installed hasn't caused a problem. I'll uninstall it if you think that will help.
A pit file? And yes, as I have already mentioned I have installed the stock firmware.
Click to expand...
Click to collapse
As it stands it's about ruling things out to pinpoint what's going wrong, I'm no expert, merely a trial and error kind of guy. Anyway, yes, I would suggest uninstalling Kies and try the flash again, although if Odin is flashing successfully then this might not be the issue, but it's worth a shot. When I resolved my bootloop, using a PIT file was one of the things I did, so perhaps that's something you might want to look into. Also, make sure your firmware downloads are clean, basically make sure they download smoothly and aren't disturbed by a network disconnection etc. Could you post links to where you downloaded your stock firmware?
Pinda007 said:
As it stands it's about ruling things out to pinpoint what's going wrong, I'm no expert, merely a trial and error kind of guy. Anyway, yes, I would suggest uninstalling Kies and try the flash again, although if Odin is flashing successfully then this might not be the issue, but it's worth a shot. When I resolved my bootloop using a PIT file was one of the things I did, so perhaps that's something you might want to look into. Also, make sure your firmware downloads are clean, basically make sure they download smoothly and aren't disturbed by a network disconnection etc. Could you post links to where you downloaded your stock firmware?
Click to expand...
Click to collapse
I got my firmware from sammobile.com, right down to my network provider. I've flashed it before and never had any problems. I'm just trying to figure out why my phone self-bricked. I was on latest "Resurrection Remix" when it happened.
Where can I find this "PIT" file and how do I use it? I notice an option in Odin so I can probably figure that part out. At the moment my knowledge is limited to rooting, flashing custom recoveries and ROMs. Sorry.
Grumpy Cat said:
I got my firmware from sammobile.com, right down to my network provider. I've flashed it before and never had any problems. I'm just trying to figure out why my phone self-bricked. I was on latest "Resurrection Remix" when it happened.
Where can I find this "PIT" file and how do I use it? I notice an option in Odin so I can probably figure that part out. At the moment my knowledge is limited to rooting, flashing custom recoveries and ROMs. Sorry.
Click to expand...
Click to collapse
Ahh ok, yes my knowledge is also limited in that respect. I guess it's all about learning and helping each other out, which is where I guess it can be frustrating when there's a lack of 'available' support in these forums. Nevertheless, I must stop droning on, I used a PIT file for my S variant after noticing numerous users mentioning the significance of it when using Odin to flash. Here's an interesting thread to find out more (http://forum.xda-developers.com/showthread.php?t=999097). It's a sort of map if you like, which inadvertently tells the software where everything has to go on the handset, that's my noob interpretation of it anyway. I found the relevant PIT file for my variant on a XDA thread, so it might be worth scurrying through archived threads to see if you can find one for your phone, make sure there's legit feedback for it though. You just flash it with the firmware like you normally would.
Remember, I'm no expert, I'm just going by how I fixed my phone over the weekend. I apologise my attempts to help are meager, I'm still relatively new to all this, just like you.
Pinda007 said:
Ahh ok, yes my knowledge is also limited in that respect. I guess it's all about learning and helping each other out, which is where I guess it can be frustrating when there's a lack of 'available' support in these forums. Nevertheless, I must stop droning on, I used a PIT file for my S variant after noticing numerous users mentioning the significance of it when using Odin to flash. Here's an interesting thread to find out more (http://forum.xda-developers.com/showthread.php?t=999097). It's a sort of map if you like, which inadvertently tells the software where everything has to go on the handset, that's my noob interpretation of it anyway. I found the relevant PIT file for my variant on a XDA thread, so it might be worth scurrying through archived threads to see if you can find one for your phone, make sure there's legit feedback for it though. You just flash it with the firmware like you normally would.
Remember, I'm no expert, I'm just going by how I fixed my phone over the weekend. I apologise my attempts to help are meager, I'm still relatively new to all this, just like you.
Click to expand...
Click to collapse
I tried installing stock firmware with the PIT file I found here and still get the same result. I might be screwed.
Grumpy Cat said:
I tried installing stock firmware with the PIT file I found here and still get the same result. I might be screwed.
Click to expand...
Click to collapse
I think that's the exact file that worked for me
I don't know what else to suggest at the moment, the fact that you cannot get into recovery makes it that much harder.
I'll come back to you if something comes to mind.
EDIT- Have you tried re flashing a custom recovery to overwrite your current one? If you can somehow get into recovery you could trying clearing your phone of cache and installing a ROM zip-folder. Also, have you got another battery you can try in your handset? I cannot help you with the Odin method no because you've pretty much exhausted all the possible solutions that I know of, perhaps screenshot the Odin log and post it on here for more info.
My s3 mini also got same problem.any solution found