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
Related
Sorry for the long read, this is half rant and half question.
Alright, I got a captivate a long time ago (about a year and 3 months ago), loved it, rooted it and installed cyanogenmod as soon as I got home, changed roms and kernals constantly, did whatever I wanted to do.
About 3 months ago my screen stopped working.. So I take it in and they give me a refurb captivate, looked brand new so I didn't mind. However, when I tried to get into recovery it didn't work, the 3-button-method just wouldn't work at all, period, so I try to get it to work, gets stuck in bootloop.. pretty much every time I try to flash a rom something goes wrong and I get stuck in a bootloop but I can usually get into recovery or download mode because I had CWM.
So I'm on maxq's rom and it's working great for the past 2 months, decide not to mess with kernals or anything, however today I decided to try ICS, load it up, everything's fine, then I realize my soft keys aren't working, search for awhile, can't find anything, finally just manually start looking through the rom pages, and someone said that if you have the problem to just odin back to stock and try again.
I odin back to stock, but now 3 button combo doesn't work.. So more searching, find that I can run the 3e fix by TRusselo, doesn't work because I need root, more searching on how to root without recovery, find "SuperOneClick", root with superoneclick, then run 3e fix, everything is working fine, I check my email and load the ICS files onto SD card, go to restart and go into recovery mode.. Bricked, stuck in a bootloop, won't go to recovery, won't go to download, nothing.
Why the **** was I able to do anything I wanted with my old captivate, but if I even root this one it bricks? And what did I do to even brick it? I only ran the 2 programs and both of them worked flawlessly.
I guess my only option is to usb jig it, but honestly now I'm convinced that the phone is just faulty, I want to run the thing over.
-Pirate said:
So I'm on maxq's rom and it's working great for the past 2 months, decide not to mess with kernals or anything, however today I decided to try ICS, load it up, everything's fine, then I realize my soft keys aren't working, search for awhile, can't find anything, finally just manually start looking through the rom pages, and someone said that if you have the problem to just odin back to stock and try again.
Click to expand...
Click to collapse
If you would have actually searched you would have known it was a bug in the glitch. There are atleast 40 pages about that.
-Pirate said:
I odin back to stock, but now 3 button combo doesn't work.. So more searching, find that I can run the 3e fix by TRusselo, doesn't work because I need root, more searching on how to root without recovery, find "SuperOneClick", root with superoneclick, then run 3e fix, everything is working fine, I check my email and load the ICS files onto SD card, go to restart and go into recovery mode.. Bricked, stuck in a bootloop, won't go to recovery, won't go to download, nothing.
Click to expand...
Click to collapse
If you flashed ICS you should know it takes 2 flashes for it to work first time. Having a jig around is always a good idea as well.
-Pirate said:
Why the **** was I able to do anything I wanted with my old captivate, but if I even root this one it bricks? And what did I do to even brick it? I only ran the 2 programs and both of them worked flawlessly.
Click to expand...
Click to collapse
Stuff doesn't work as intended. Keep in mind everything is still in dev and not all devices are the same. But you should have searched a little more and it would have ran =/
U def don't need a jig. If it's booting it's not bricked. Try removing battery, start Odin, hold down power and down, plug in and put battery in. This should bring u to download mode.
prbassplayer said:
If you would have actually searched you would have known it was a bug in the glitch. There are atleast 40 pages about that.
Click to expand...
Click to collapse
I did start to see a few people with the problem, however many people do not follow up with what fixes their problem, and I did what a few people had said to do.
prbassplayer said:
If you flashed ICS you should know it takes 2 flashes for it to work first time. Having a jig around is always a good idea as well.
Click to expand...
Click to collapse
I should of mentioned that I did flash a few times, 3 total I think, it was getting stuck at boot.
prbassplayer said:
Stuff doesn't work as intended. Keep in mind everything is still in dev and not all devices are the same. But you should have searched a little more and it would have ran =/
Click to expand...
Click to collapse
I understand that **** happens but honestly my old captivate could always get into recover mode and download mode no matter what, it's extremely frustrating that something changed with the newer models. One of my questions was what caused the brick? I did nothing wrong from what I see and it was running perfectly until I tried to restart/boot into recovery.
Oh and mbc663, thanks but download mode doesn't work at all, nor does recovery obviously.
I can't say exactly what you are doing. Best advice I can do Re download your .zips Flash back to stock GB and try again.
-Pirate said:
About 3 months ago my screen stopped working.. So I take it in and they give me a refurb captivate, looked brand new so I didn't mind. However, when I tried to get into recovery it didn't work, the 3-button-method just wouldn't work at all, period, so I try to get it to work, gets stuck in bootloop.. pretty much every time I try to flash a rom something goes wrong and I get stuck in a bootloop but I can usually get into recovery or download mode because I had CWM.
So I'm on maxq's rom and it's working great for the past 2 months, decide not to mess with kernals or anything, however today I decided to try ICS, load it up, everything's fine, then I realize my soft keys aren't working, search for awhile, can't find anything, finally just manually start looking through the rom pages, and someone said that if you have the problem to just odin back to stock and try again.
I odin back to stock, but now 3 button combo doesn't work.. So more searching, find that I can run the 3e fix by TRusselo, doesn't work because I need root, more searching on how to root without recovery, find "SuperOneClick", root with superoneclick, then run 3e fix, everything is working fine, I check my email and load the ICS files onto SD card, go to restart and go into recovery mode.. Bricked, stuck in a bootloop, won't go to recovery, won't go to download, nothing.
Why the **** was I able to do anything I wanted with my old captivate, but if I even root this one it bricks? And what did I do to even brick it? I only ran the 2 programs and both of them worked flawlessly.
I guess my only option is to usb jig it, but honestly now I'm convinced that the phone is just faulty, I want to run the thing over.
Click to expand...
Click to collapse
Last year, I had issues with my original Cap, and got a "new" one. I learned that the bulk of the Caps going out as replacements are referbs. The one I got was a 1008 build, and does not have 3 button recovery. There are minor differences with each and every Cap that's out there. That's why some have issues with ROM's and some don't, some can over clock like crazy, and some can't at all. My guess is you have a 1008 as well, but that really doesn't matter. You just have a different device and as you seem to already have learned.
It sounds like there is more research you need to do. Even though the devices are a bit different, if you are having issues with ROM's loading, then I would say it's more of a procedure issue, than one with your device.
My procedure, is,
Remove SD/Micro SD
Odin1 Click to Stock JF6, and Master Clear(This will erase EVERYTHING)
Root with One-Click Root
Use Sideload Wonder Machine to install ROM Manager, copy update.zip and 3buttonFix to my SD, then reboot into recovery
Once in recovery I install the 3buttonFix, and install my new ROM
For me this has proven to be a very good method versus going from one ROM to another. The Master Clear cleans EVERYTHING off of your SD, so there is no chance for anything to corrupt your new install. Anytime I read a post of a install gone FUBAR, USUALLY a Flash To Stock/Master Clear (FTS/MC) fixes it
Before using Odin 1 Click, check your devices build number!! If it is higher than 1012, I would NOT recommend using 1 click, there is a higher chance of hard brick on the newer devices
Kangi...if you flash a firmware package without bootloaders, you won't have to do the 3 button fix every time. And if you keep a copy of the update.zip on your pc you don't have to even root, let alone bother with side loading ROM manager.
Cezar has a no boots jf6 and after you run that, you can still use master clear in one click.
Sounds like you got one of the refurbs that is missing the SBL. Have you looked at this thread? http://forum.xda-developers.com/showthread.php?t=1129821
I've not had this problem myself but it sounds like that might help. If I remember reading correctly, once this is flashed it should stick as long as you don't flash any other bootloaders on top of it.
Its not missing the sbl. The sbl it has doesn't respond to key combos. Derpa sherpa moment for samsung I guess?
Rofl yeah...if it was missing the sbl it would be fuggin bricked!
studacris said:
Kangi...if you flash a firmware package without bootloaders, you won't have to do the 3 button fix every time. And if you keep a copy of the update.zip on your pc you don't have to even root, let alone bother with side loading ROM manager.
Cezar has a no boots jf6 and after you run that, you can still use master clear in one click.
Click to expand...
Click to collapse
I know, thanks. I'm such a creature of habit, I started doing it like this a bit over a year ago, and has worked flawlessly for me(just jinxed myself!) so I never saw a reason to "fix what aint broke".
I'll take a look at Cezar's thanks!
Yeah, missing SBL was a poor choice of words. My bad.
kangi26 said:
Last year, I had issues with my original Cap, and got a "new" one. I learned that the bulk of the Caps going out as replacements are referbs. The one I got was a 1008 build, and does not have 3 button recovery. There are minor differences with each and every Cap that's out there. That's why some have issues with ROM's and some don't, some can over clock like crazy, and some can't at all. My guess is you have a 1008 as well, but that really doesn't matter. You just have a different device and as you seem to already have learned.
It sounds like there is more research you need to do. Even though the devices are a bit different, if you are having issues with ROM's loading, then I would say it's more of a procedure issue, than one with your device.
My procedure, is,
Remove SD/Micro SD
Odin1 Click to Stock JF6, and Master Clear(This will erase EVERYTHING)
Root with One-Click Root
Use Sideload Wonder Machine to install ROM Manager, copy update.zip and 3buttonFix to my SD, then reboot into recovery
Once in recovery I install the 3buttonFix, and install my new ROM
For me this has proven to be a very good method versus going from one ROM to another. The Master Clear cleans EVERYTHING off of your SD, so there is no chance for anything to corrupt your new install. Anytime I read a post of a install gone FUBAR, USUALLY a Flash To Stock/Master Clear (FTS/MC) fixes it
Before using Odin 1 Click, check your devices build number!! If it is higher than 1012, I would NOT recommend using 1 click, there is a higher chance of hard brick on the newer devices
Click to expand...
Click to collapse
I didn't think anyone else was going to reply to this thread, whoops.
Thank you for helping me, but I'm still having trouble.
Rom manager doesn't show up in Market, Sideload wonder machine tells me [INSTALL FAILED OLDER SDK] with any apk of Rom manager I find.
kangi26 said:
3buttonFix to my SD, then reboot into recovery
Click to expand...
Click to collapse
How do you reboot into recovery when 3buttonfix hasn't been applied yet?
This sucks and is extremely frustrating, I feel like my captivate is just trolling me.
-Pirate said:
I didn't think anyone else was going to reply to this thread, whoops.
Thank you for helping me, but I'm still having trouble.
Rom manager doesn't show up in Market, Sideload wonder machine tells me [INSTALL FAILED OLDER SDK] with any apk of Rom manager I find.
How do you reboot into recovery when 3buttonfix hasn't been applied yet?
This sucks and is extremely frustrating, I feel like my captivate is just trolling me.
Click to expand...
Click to collapse
When I get home later tonight I'll link you everything you'll need. Again, VERY important, what is your build number? If it's 1012 or higher, don't use Odin 1 click
Sent from a autonomous device
kangi26 said:
When I get home later tonight I'll link you everything you'll need. Again, VERY important, what is your build number? If it's 1012 or higher, don't use Odin 1 click
Sent from a autonomous device
Click to expand...
Click to collapse
Ok, finally got it working, I did exactly what you said, I found the rom manager 3.00.002 or whatever and that worked with sideloader, it took some messing around with but I'm running ICS now, thank you so much man, you've helped me so much, and now I can change roms and keep up to date without worrying about constantly soft-bricking.
As for my build number, I'm not sure, the only thing I see under build number in settings is: "IML74k"
-Pirate said:
Ok, finally got it working, I did exactly what you said, I found the rom manager 3.00.002 or whatever and that worked with sideloader, it took some messing around with but I'm running ICS now, thank you so much man, you've helped me so much, and now I can change roms and keep up to date without worrying about constantly soft-bricking.
As for my build number, I'm not sure, the only thing I see under build number in settings is: "IML74k"
Click to expand...
Click to collapse
The build number is actually under your battery, and looks like 10.06, 10.07, 10.08 and so on. It is the production date
Edit** And as a side note, do NOT try to use the 3buttonFix with a GB ROM, it WILL brick your phone in a really bad way. ONLY use it with 2.1 or 2.2
kangi26 said:
The build number is actually under your battery, and looks like 10.06, 10.07, 10.08 and so on. It is the production date
Edit** And as a side note, do NOT try to use the 3buttonFix with a GB ROM, it WILL brick your phone in a really bad way. ONLY use it with 2.1 or 2.2
Click to expand...
Click to collapse
Is it weird that I don't have a build number? It seems I can't post pictures without a few more posts, maybe this will work: deleted
And thanks for the warning on the 3buttonfix, I'm going to have to read more about bootloaders though, I don't understand what you and studacris were talking about earlier in the thread, haha.
-Pirate said:
Is it weird that I don't have a build number? It seems I can't post pictures without a few more posts, maybe this will work: imgurDOTcom/26sXGl.jpg
And thanks for the warning on the 3buttonfix, I'm going to have to read more about bootloaders though, I don't understand what you and studacris were talking about earlier in the thread, haha.
Click to expand...
Click to collapse
I havent seen that before, there doesnt seem to be a build#
Might want to pull that photo, it's not too good having your IMEI number publicly displayed
kangi26 said:
I havent seen that before, there doesnt seem to be a build#
Might want to pull that photo, it's not too good having your IMEI number publicly displayed
Click to expand...
Click to collapse
Maybe because it's a refurb? and whoops didn't think about that.
-Pirate said:
Maybe because it's a refurb? and whoops didn't think about that.
Click to expand...
Click to collapse
I'm not sure why, mine is a referb, and I have a sticker with mine on it. Ooh well, it is what it is
Sent from a autonomous device
(Obvious Noob warning---) A friend helped me root my Thrill, install ClockworkMod Recovery, and then install CM7 on my Thrill. But I would like to try the LG GB release. Is it necessary to backtrack all the way back to stock to do this (i.e. reinstall the stock ROM, reinstall the stock recovery, unroot, etc.)?
My friend tried using the LG upgrade tool on his LG phone without going back to stock and ended up bricking it. He says that usually within a few days of release, a CMR compatible zip file (usually already rooted) appears here on XDA (I haven't seen it), which makes things easier (but obviously he didn't wait for it himself).
Will a zip be possible for the Thrill GB? (The file seems quite large (420MB), so I'm guessing there is a lot of media included.) Or should I just bite the bullet and backtrack?
Rick
Rick Tillery said:
(Obvious Noob warning---) A friend helped me root my Thrill, install ClockworkMod Recovery, and then install CM7 on my Thrill. But I would like to try the LG GB release. Is it necessary to backtrack all the way back to stock to do this (i.e. reinstall the stock ROM, reinstall the stock recovery, unroot, etc.)?
My friend tried using the LG upgrade tool on his LG phone without going back to stock and ended up bricking it. He says that usually within a few days of release, a CMR compatible zip file (usually already rooted) appears here on XDA (I haven't seen it), which makes things easier (but obviously he didn't wait for it himself).
Will a zip be possible for the Thrill GB? (The file seems quite large (420MB), so I'm guessing there is a lot of media included.) Or should I just bite the bullet and backtrack?
Rick
Click to expand...
Click to collapse
I'm assuming that the official update method was used.
Just use this method after downloading the update. No bricking.
SEE THREAD
The Dark Lestat said:
I'm assuming that the official update method was used.
Just use this method after downloading the update. No bricking.
SEE THREAD
Click to expand...
Click to collapse
Thank you for your help!
Rick
Trojan?
Sorry, but as a noob, I can't post in that other thread.
It seems that the shttp3.exe in the LG Flash Package triggers Symantec's trojan detection. Some searching seems to indicate (assuming I'm reading all the cryptic virus sites correctly) that there is something to this, although it seems that different scanners find different trojans/viruses (can't post the link, but Google for "shttp3.exe" and "trojan"). I also found that the web site for this utility is blocked at work, because it's a "malicious site."
Has anyone seen this? Has anyone been able to verify/refute this?
Rick
There is no virus, Lestat would never do that
Sent from my LG-P925 using XDA
Just my .02 .....Get rid of Symantec !! They are known for scaring people into a virus frenzy.. Yes, it is possible that it is seeing it as a potential virus because shttp is a workaround from the usual porting of windows ip services. ...
Correct me if i'm wrong somebody please !!
Get yourself Comodo and save your money...
Regards,
Dwayne
PS: somebody on here has written a script that just uses shttp temporarily while
your doing the flash procedure, and then reverts your host files back automatically after your done. You should try it.
dwaynedman said:
Just my .02 .....Get rid of Symantec !!
Click to expand...
Click to collapse
Symantec isn't really a choice on work PC.
Get yourself Comodo and save your money...
Click to expand...
Click to collapse
I'm sorry I can't give the link yet, but if you'll Google you'll see Comodo classifies shttp3.exe as "ApplicUnwnt.Win32.ServerWeb.SmallHTTP.~A" or "UnclassifiedMalware" (I guess depending on the version). A number of scanners find issues with shttp3.exe. I'm not saying it is infected, only that it is doing something suspicious.
Rick
Rick Tillery said:
Sorry, but as a noob, I can't post in that other thread.
It seems that the shttp3.exe in the LG Flash Package triggers Symantec's trojan detection. Some searching seems to indicate (assuming I'm reading all the cryptic virus sites correctly) that there is something to this, although it seems that different scanners find different trojans/viruses (can't post the link, but Google for "shttp3.exe" and "trojan"). I also found that the web site for this utility is blocked at work, because it's a "malicious site."
Has anyone seen this? Has anyone been able to verify/refute this?
Rick
Click to expand...
Click to collapse
shttp3.exe is in no way a virus. I've scanned with AVG and MalwareBytes Anti-Malware and they check out good.
Back to square one
OK, I seem to be stuck.
With paranoia in tow, I decided to take the long way back to stock. Unfortunately, when I tried to restore the backup of my stock image I made to SD card after installing CMR, the md5 checksum failed. I'm not sure what I can do about this.
So ok, I tried following the above link. The first step is to ensure the su binary is up-to-date. But when I tried this, I get a failure downloading the manifest. This is true for WiFi and HSPA+. I Googled and found a suggestion to delete the su binary. But that didn't help (I'm not sure how it would have helped anyway).
So back to the original question. Can I use the LG upgrade process to upgrade without going backwards (as you can see above, I can't) without bricking the phone? Can I start at step 3 in the link above and succeed?
Rick
The Dark Lestat said:
shttp3.exe is in no way a virus. I've scanned with AVG and MalwareBytes Anti-Malware and they check out good.
Click to expand...
Click to collapse
Thank you, sir. I hope it didn't seem accusing.
Rick
Rick Tillery said:
Thank you, sir. I hope it didn't seem accusing.
Rick
Click to expand...
Click to collapse
It's cool, my friend.
Sent from my Samsung Galaxy S II w/ CM9
Rick Tillery said:
OK, I seem to be stuck.
With paranoia in tow, I decided to take the long way back to stock. Unfortunately, when I tried to restore the backup of my stock image I made to SD card after installing CMR, the md5 checksum failed. I'm not sure what I can do about this.
So ok, I tried following the above link. The first step is to ensure the su binary is up-to-date. But when I tried this, I get a failure downloading the manifest. This is true for WiFi and HSPA+. I Googled and found a suggestion to delete the su binary. But that didn't help (I'm not sure how it would have helped anyway).
So back to the original question. Can I use the LG upgrade process to upgrade without going backwards (as you can see above, I can't) without bricking the phone? Can I start at step 3 in the link above and succeed?
Rick
Click to expand...
Click to collapse
Is it safe to ignore the su version update?
Short of this, can I override the MD5 checksum? I realize that image could be corrupt, but if I'm just going to replace it with the GB release, does that matter?
Rick
You should just put your phone in recovery mode and update through the tool
with your IMEI #. It will give you the latest update !
If you need some help on that I think Lestat or somebody has a write-up
on doing this.
Good luck,
Dwayne
dwaynedman said:
You should just put your phone in recovery mode and update through the tool
with your IMEI #. It will give you the latest update !
If you need some help on that I think Lestat or somebody has a write-up
on doing this.
Good luck,
Dwayne
Click to expand...
Click to collapse
Can you be a bit more specific?
1. By "recovery mode," do you mean into ClockworkMod Recovery, or I should revert to stock (I made a copy of it after I rooted the stock ROM, but before I installed CMR)?
2. By "the tool," do you mean the official LGMobile Software Update, or the LG Flash Package referenced in the link above?
3. By "latest update," do you mean the file directly from LG, or the copy (v20p) linked from the link above?
4. If the latter in both previous questions, which set of steps do I need to follow from the above link? Can I do only 3 (LG Flash Tool), or do I need to follow 1 (Recovery Manager), 2 (Returning to Stock), and 3?
My friend had a different LG phone, with ClockworkMod Recover and CM7 installed. He reverted the CM7 to stock, but did not replace CMR with the stock recovery. Then he used the official LG upgrade method and bricked his phone. I'm trying to avoid this.
Are you saying I don't have to worry about this on the LG Thrill 4G? Can I go straight from the current CMR+CM7 configuration to the LG GB release using the official LG process?
If you mean I should use a different process, can you point me to it? As I mentioned, I run into dead-ends using the method linked above. And I'm not even sure whether I should be doing steps 1, 2 and 3, or if I should just use step 3.
Any and all help is appreciated, but I guess I don't understand the shorthand you're using here, so if you could be a bit more specific, I wouldn't feel so lost.
Rick
Rick Tillery said:
Can you be a bit more specific?
1. By "recovery mode," do you mean into ClockworkMod Recovery, or I should revert to stock (I made a copy of it after I rooted the stock ROM, but before I installed CMR)?
2. By "the tool," do you mean the official LGMobile Software Update, or the LG Flash Package referenced in the link above?
3. By "latest update," do you mean the file directly from LG, or the copy (v20p) linked from the link above?
4. If the latter in both previous questions, which set of steps do I need to follow from the above link? Can I do only 3 (LG Flash Tool), or do I need to follow 1 (Recovery Manager), 2 (Returning to Stock), and 3?
My friend had a different LG phone, with ClockworkMod Recover and CM7 installed. He reverted the CM7 to stock, but did not replace CMR with the stock recovery. Then he used the official LG upgrade method and bricked his phone. I'm trying to avoid this.
Are you saying I don't have to worry about this on the LG Thrill 4G? Can I go straight from the current CMR+CM7 configuration to the LG GB release using the official LG process?
If you mean I should use a different process, can you point me to it? As I mentioned, I run into dead-ends using the method linked above. And I'm not even sure whether I should be doing steps 1, 2 and 3, or if I should just use step 3.
Any and all help is appreciated, but I guess I don't understand the shorthand you're using here, so if you could be a bit more specific, I wouldn't feel so lost.
Rick
Click to expand...
Click to collapse
Remove your battery and keep the phone unplugged
Launch the mobile updater tool
Hold the volume+ button plug the phone in and keep holding the volume+ till the computer downloads the drivers your phone is now in download mode
Once the phone is picked up go to customer support on the LG updater tool and click on recovery phone put your imie number in click check (make sure its the right model) an let the updater tool do its job. Once its done flashing launch into recovery volume- plus power plus 3D button do a complete wipe and factory reset and reboot your phone ... you'll lose cwm and root and be back to full stock
Sent from my LG-P925 using XDA
Bricked?
No joy. Following the steps, the upgrade stopped at 6%. Trying a number of times, it eventually forced me to exit the program (no more restarts). Rerunning the updater (and downloading the 420 MB image yet again on a VERY slow connection) I tried again and again, with different combinations of battery and plug order with power and volume buttons, but nothing worked. Checking elsewhere I found some issues had been reported with Windows Vista/7, so I tried on an XP machine. Now the "Start Updating" bar is red (it was always gray with W7). But now when I try to restore (or even update for that matter), it asks for my S/N (it never did that before) and then says it is "no longer able to upgrade." Reading around, it seems this is an indication of the device being bricked.
Rick
It sounds like you are very close to getting it working Rick.
My update did the same thing, looped over and over until it
finally kicked me out. Just plugging and unplugging the phone etc....
And when my update stuck at 6% the last time, i took my battery out and then in real quick and that seemed to work.
Does the phone still vibrate when you plug the usb cable into it while holding volume..? If it does then I highly doubt that your phone is bricked, just in a semi flashed state....No worries
Should Rick be trying to run LG Updater as administrator ? I didn't, but it might not hurt.
Regards & Luck,
Dwayne
http://forum.xda-developers.com/showthread.php?p=22417769
Have you tried this yet cause if you can get the LG logo to come up then you can reflash the phone and get it working send a pm to the dark lestat he may be able to team viewer you and help you out
Sent from my ****ty supported LG Thrill
dwaynedman said:
It sounds like you are very close to getting it working Rick.
Click to expand...
Click to collapse
I wouldn't have believed you early this morning, but now maybe...
My update did the same thing, looped over and over until it
finally kicked me out. Just plugging and unplugging the phone etc....
And when my update stuck at 6% the last time, i took my battery out and then in real quick and that seemed to work.
Click to expand...
Click to collapse
I tried a bunch of different combinations...none seemed to make the app happy. I finally punted Windows 7 and moved to an XP machine, only to get the "no longer able to update" message. At that point I assumed I was screwed (effectively bricked).
Does the phone still vibrate when you plug the usb cable into it while holding volume..? If it does then I highly doubt that your phone is bricked, just in a semi flashed state....No worries
Click to expand...
Click to collapse
It never really vibrated, but I was able to get back into CMR. Unfortunately NONE of my backups work at all. They all have MD5 checksum failures. I tried a trick I found online and got past that step, only to have it say a failure restoring /system. So much for CMR.
JReeher said:
http://forum.xda-developers.com/showthread.php?p=22417769
Have you tried this yet cause if you can get the LG logo to come up then you can reflash the phone and get it working send a pm to the dark lestat he may be able to team viewer you and help you out
Click to expand...
Click to collapse
Which step? As I mentioned above, I can't even get the first step of the first section (updating the su binary). And if I start at the 3rd section, Symantec prohibits me from using shttp3.exe (I tried to unquarantine it, but it gives a permission error, even as Administrator, when I try to run it), so I'll have to use a different machine.
I was able to reinstall the CM7 3/15 release, so that's something. I was going to restore the stock recovery backup I made, but even that doesn't seem to work. I'm having issue with backups :-(
Rick
i have never been able to restore a backup. i dont know why... but i have tried several times in several different instances.
---------- Post added at 11:56 AM ---------- Previous post was at 11:50 AM ----------
rick tillery, if you want to get your phone back to alive and well i'd suggest doing this:
http://forum.xda-developers.com/showthread.php?t=1558723&page=3
4th post i think
I used ODIN and all the correct files/methods to work with the Mini for my friend. The whole reason behind flashing CWM to it was so I could make a backup of it before flashing CM7.. It says completed and that I can remove the cable but just sits at the "ANDROID" logo when trying to enter recovery; WTD?! Anyhelp?
Has no-one developed a better way of flashing custom recovery, hell the wildfire was "S-on" and they figured a hardware-less way of removing it which was FREE.
Any help is appreciated!
I'm afraid that you haven't flashed the correct CWM recovery for you device, because you stated above that ODIN says COMPLETED and it's not the right word, it must show PASS with a blue background on the top left corner and in the message field you should get:
PASS!!!
Destroy instant..
Killed timer
so to avoid doubt Try removing battery for a little bit, then put it again; if it goes nowhere, in this case retry the flash procedure.
if it stuck again that prove that the CWM it's not the correct one.
so go this thread:
http://forum.xda-developers.com/showthread.php?t=1342190
and download the appropriate CWM file from attachments then follow the instructions given there....GOOD LUCK
abdovar said:
I'm afraid that you haven't flashed the correct CWM recovery for you device, because you stated above that ODIN says COMPLETED and it's not the right word, it must show PASS with a blue background on the top left corner and in the message field you should get:
PASS!!!
Destroy instant..
Killed timer
so to avoid doubt Try removing battery for a little bit, then put it again; if it goes nowhere, in this case retry the flash procedure.
if it stuck again that prove that the CWM it's not the correct one.
so go this thread:
http://forum.xda-developers.com/showthread.php?t=1342190
and download the appropriate CWM file from attachments then follow the instructions given there....GOOD LUCK
Click to expand...
Click to collapse
Or for a better version, go to http://forum.xda-developers.com/showthread.php?t=1529863 and download 5.0.2.8, a touch version that works great on the Mini.
The Odin and Tass in the link you provided are still fine though.
---------- Post added at 03:19 PM ---------- Previous post was at 03:15 PM ----------
JackJack762 said:
I used ODIN and all the correct files/methods to work with the Mini for my friend. The whole reason behind flashing CWM to it was so I could make a backup of it before flashing CM7.. It says completed and that I can remove the cable but just sits at the "ANDROID" logo when trying to enter recovery; WTD?! Anyhelp?
Has no-one developed a better way of flashing custom recovery, hell the wildfire was "S-on" and they figured a hardware-less way of removing it which was FREE.
Any help is appreciated!
Click to expand...
Click to collapse
A few things, first of all, you cannot backup stock roms with CWM, you can back up data and apps with other backup programs.
You could have used your stock recovery to flash a CWM.zip file instead but that wouldn't have helped you either if you have the wrong version of CWM.
Regarding your last comment... You're not making any sense at all.
Basically, you did something wrong with your friends mini and now you want to blame anything but yourself for your own mistakes, that's not going to fix the mini.
abdovar said:
I'm afraid that you haven't flashed the correct CWM recovery for you device, because you stated above that ODIN says COMPLETED and it's not the right word, it must show PASS with a blue background on the top left corner and in the message field you should get:
PASS!!!
Destroy instant..
Killed timer
so to avoid doubt Try removing battery for a little bit, then put it again; if it goes nowhere, in this case retry the flash procedure.
if it stuck again that prove that the CWM it's not the correct one.
so go this thread:
http://forum.xda-developers.com/showthread.php?t=1342190
and download the appropriate CWM file from attachments then follow the instructions given there....GOOD LUCK
Click to expand...
Click to collapse
Yeah it said PASS sorry, I hadnt had the phone for one or two days so I just put Complete as a stand-in for the word PASS. I'll give it a try and hope for the best
Jinxxed said:
Or for a better version, go to http://forum.xda-developers.com/showthread.php?t=1529863 and download 5.0.2.8, a touch version that works great on the Mini.
The Odin and Tass in the link you provided are still fine though.
---------- Post added at 03:19 PM ---------- Previous post was at 03:15 PM ----------
A few things, first of all, you cannot backup stock roms with CWM, you can back up data and apps with other backup programs.
You could have used your stock recovery to flash a CWM.zip file instead but that wouldn't have helped you either if you have the wrong version of CWM.
Regarding your last comment... You're not making any sense at all.
Basically, you did something wrong with your friends mini and now you want to blame anything but yourself for your own mistakes, that's not going to fix the mini.
Click to expand...
Click to collapse
I'll give that a try too, I wasn't blaming anything but my self.. I was just saying that this way is an over complicated system; There are better programs and ways that have been developed for most other Android devices like my R800i or my girlfriends ACE. Ok I didn't know about the back-up issue but I've done that via Supermanager anyway.
JackJack762 said:
Yeah it said PASS sorry, I hadnt had the phone for one or two days so I just put Complete as a stand-in for the word PASS. I'll give it a try and hope for the best
I'll give that a try too, I wasn't blaming anything but my self.. I was just saying that this way is an over complicated system; There are better programs and ways that have been developed for most other Android devices like my R800i or my girlfriends ACE. Ok I didn't know about the back-up issue but I've done that via Supermanager anyway.
Click to expand...
Click to collapse
Yeah, considering the ACE has the exact same tools, i think you are just full of sheit.
You can do it all via Rom Manager/Rom Toolbox/someotherprogram if you'd like, it's just that experience tells us that it works best if you do it in the simplest way possible because that is the most likely to work.
So either you want what works or you can search market, why didn't you do that in the first place if rebooting was too hard for you?
Just so you know, none of those apps will save your arse when your phone won't boot, right about then your knowledge about how to fix it from the recovery will save your arse in front of your girlfriend.
So say pretty please thank you and go away.
---------- Post added at 11:10 PM ---------- Previous post was at 11:07 PM ----------
JackJack762 said:
Yeah it said PASS sorry, I hadnt had the phone for one or two days so I just put Complete as a stand-in for the word PASS. I'll give it a try and hope for the best
I'll give that a try too, I wasn't blaming anything but my self.. I was just saying that this way is an over complicated system; There are better programs and ways that have been developed for most other Android devices like my R800i or my girlfriends ACE. Ok I didn't know about the back-up issue but I've done that via Supermanager anyway.
Click to expand...
Click to collapse
Wait, you used the galaxy mini versions on your R800i and a Galaxy Ace?
Didn't work? WELL OF COURSE NOT!
Err no. I think you have read what I said wrong.
I have flashed the ACE and the R800i via other methods which work alot better, no need to be an asshole. I never used "ODIN" with the ACE so you can stop being such an ass when you need to read the post prior to posting.
I used flashable CWM on the ace then flashed new roms from that. Not ODIN, I used "x10 Flash tool" for the R800i.
So no I will not say "Thanks" and go away. You see, Unlike you I don't sit inside ALL of my life I have the ability and the hardware to flash any EEPROM or pretty much anything that needs to be accessed as thats my JOB. in the BRITISH ARMY.
Grow up and find something better to do than troll people.
thx
abdovar said:
I'm afraid that you haven't flashed the correct CWM recovery for you device, because you stated above that ODIN says COMPLETED and it's not the right word, it must show PASS with a blue background on the top left corner and in the message field you should get:
PASS!!!
Destroy instant..
Killed timer
so to avoid doubt Try removing battery for a little bit, then put it again; if it goes nowhere, in this case retry the flash procedure.
if it stuck again that prove that the CWM it's not the correct one.
so go this thread:
http://forum.xda-developers.com/showthread.php?t=1342190
and download the appropriate CWM file from attachments then follow the instructions given there....GOOD LUCK
Click to expand...
Click to collapse
Thx for the link
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 can only boot into safe strap. I think I accidentally deleted everything on there. I tried a different ROM, and that didn't boot up.
Not sure all the info anyone would need.
Right now I'm looking at Odin not working. Heimdal I haven't been able to find a download for. The things that a lot of the guides talk about go to 404s since the phone's a couple years old at this point.
My main phone is a OnePlus 2 that I need to send in for a warranty repair, but there's the potential of me being able to flash a new rom on there, that has the updated drivers for the fingerprint sensor (and thus fix the issue and I don't have to go without a phone).
I figured I'd try out the whole process before I accidentally brick my main phone, haha.
I tried doing Kies, too, and it said that my model number isn't right but only after I put in the S/N so I don't know what to make of that.
I've been reading everything I could get my hands on for the past two days and so well I guess I can't figure it out.
Thanks in advance.
update:
Odin worked!
Used Odin v3.09
I'm so stinkin excited now! I still don't know what build I started with but now I've got something I can go with.
The guide I used: droidviews com install-stock-firmware-on-samsung-galaxy-devices-using-odin
It took many many many reboot cycles to get the phone to show up in Odin, and it kept going back to safestrap. Now I have a way back though if I do this again.
I didn't get any responses by the time I solved it (and also went to the storage unit to get my PC to actually do this) but I want to thank you all for having such a good set of resources.
I'll update this with the actual links n stuff after I get 10 posts.
I checked repartition (since it couldn't find /system or /systemorig ) even though the guide says
In the Options section, make sure that only the Auto Reboot and F. Reset Time boxes are checked and everything else are unchecked. (Do not, in any case, check Re-Partition box unless you have a .PIT file to flash, or it will lead to major problems including a corrupt partition table, if you don’t know what you’re doing.)
Click to expand...
Click to collapse