Related
I'm in Canada using Bell (i9000m)
I have rooted my phone. I've used the 1 click lag fix. I've overclocked it a bit using an app/widget.
Other than that, I haven't done anything else to my phone.
I know these are noob questions, but i just hope someone can help me.
I can't for the life of me access Keis (tried everything)
I am curious: how do I update my firmware? what about the 2.2 froyo update? will it be OTA? will I still get it? What about the GPS fix?
Basically im wondering how will I be able to get these updates and fixes if I can't access Keis -- and my phone is rooted (does that even matter?) ?
Thanks in advance guys
No one?
Just basically wondering about future updates (gps fix / froyo 2.2) --- will I still be able to receive these if I rooted my phone?
What if I can't access Kies ?
I don't think the Galaxy S has an OTA function
Which means, it's either KIES or Odin
Arkanius said:
I don't think the Galaxy S has an OTA function
Which means, it's either KIES or Odin
Click to expand...
Click to collapse
Christ. This phone is bar none the best avail. But easily has the WORST software I've ever seen.
KIES is messed and will never work with my phone/computer. It doesn't recognize anything.
So my only option is ODIN? is there anything I should be worried about with ODIN? is it really simple to flash? or do I gotta make partitions etc.
Any chance you have launcher pro installed?
im a newbie so im just providing info i have read my self and so far that ive seen odin is very simple to follow proper instructions theres a youtube video when ur flashing something your given step by step instructions by who ever uploaded the file and if you have the 3 button combo working your good to go as you can always reflash
The phone actually does have software capable of doing OTA updates. It probably isn't set up to work yet though.
The lagfix won't affect your upgrading though, just remember to uninstall it before doing the upgrade!
Root will have zero effect too, as it is just an extra (special) application at it's core.
it needs to switch back to TwLauncher for KIES to work
you can use Home Switcher
link http://forum.xda-developers.com/showthread.php?t=765081
Bobler420 said:
im a newbie so im just providing info i have read my self and so far that ive seen odin is very simple to follow proper instructions theres a youtube video when ur flashing something your given step by step instructions by who ever uploaded the file and if you have the 3 button combo working your good to go as you can always reflash
Click to expand...
Click to collapse
I'm with Bell - my 3 button combo DOESN'T work
ivanchin99 said:
Any chance you have launcher pro installed?
Click to expand...
Click to collapse
Yes.
Do i have to uninstall it? or just use TW as my default ?
RyanZA said:
The phone actually does have software capable of doing OTA updates. It probably isn't set up to work yet though.
The lagfix won't affect your upgrading though, just remember to uninstall it before doing the upgrade!
Root will have zero effect too, as it is just an extra (special) application at it's core.
Click to expand...
Click to collapse
What happens if you DONT uninstall the lag fix before the update ?
I used Ryan's 1-click lag fix --- is there a one-click to reverse it ?
is it easy to reverse the lag fix?
cheers
Funkadelick said:
Yes.
Do i have to uninstall it? or just use TW as my default ?
Click to expand...
Click to collapse
No you don't have to uninstal just go to settings>applications>manage applications
select launcher pro and then click on the clear defaults button. Next press the home key, it will ask you to choose a home app, choose TW.
Kies does not work untill you do that.
Other things to check is go to settings>status>usb mode select kies
Usb debuging should be OFF
Try to have the pc and phone on a fresh restart before trying to connect.
Basicly it should work.
Yes, Kies works only with TW. Also with the latest Froyo JPC firmware you get yor GPS fixed already.
Sent from my GT-I9000 using XDA App
Funkadelick said:
Yes.
Do i have to uninstall it? or just use TW as my default ?
Click to expand...
Click to collapse
Yes, you need to use the default TW. I had the exact problem as yours, uninstalled my launcher pro then Kies is able to detect the phone from there.
Allgamer made a good point. I cant find anyway to return to the default screen so i just click uninstall
OlegZh said:
Yes, Kies works only with TW. Also with the latest Froyo JPC firmware you get yor GPS fixed already.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Well this is the problem: I don't know how to flash (yet) so I'm just trying to learn slowly.
I am not sure if i want to flash it with Froyo FW's -- I kinda wanna wait for Bell to release their 2.2 froyo update (b/c my 3 buttons don't work and hopefully it will fix it AND the GPS)
So basically you guys have helped me with the Kies. But I am curious about the 1-click-lag-fix (I found the APP on the market and it worked) -- i don't wanna mess up my phone cuz the 3 button thing don't work.
So I just use the APP again to Un-root, use the APP again to remove/uninstall the lag-fix, then use Keis (or odin) to install/flash the new 2.2 froyo Bell update (when it comes out) ? then im good to go ?
After I update to 2.2 -- then I root again, and lag fix?
Funkadelick said:
Christ. This phone is bar none the best avail. But easily has the WORST software I've ever seen.
KIES is messed and will never work with my phone/computer. It doesn't recognize anything.
So my only option is ODIN? is there anything I should be worried about with ODIN? is it really simple to flash? or do I gotta make partitions etc.
Click to expand...
Click to collapse
I have a Bell i9000m, rooted, unlocked and on Rogers.
After installing Samsung drivers ( PRIOR TO connecting via usb) Kies worked on first attempt (Win7 64bit). The driver pack is 18 mb and I found it somewhere here on the forms (looking for the link).
Hope that helps.
Hi, I also having GPS problem previously and I hated samsung which produce so bad gps phone but after a while I think I finally found why causes the gps issues. Ok if you go into the GPS test mode by *#1472365*# you will notice that we are using SUPL. SUPL true GPS which will in coorporate with the compass and stalite to fix our position and direction. But our phone compass some how need to be calibrated. Just key in *#0*# then click on sensor. If your compass showing need to be calibrate then just hold your phone by verticaly and rotate it untill you get 3. Now reboot it and try the GPS.
Samfirmware tweet 3hr ago that the new Froyo JPC firmware have some bootloader problem.
Any clue about this? Does it will permanently damage your phone?
I'm considering Flash this via ODIN or the HK one.
Yeah a lot of people are flashing it because it WILL permanently damage your phone.... just think about it for a sec.
MomijiTMO said:
Yeah a lot of people are flashing it because it WILL permanently damage your phone.... just think about it for a sec.
Click to expand...
Click to collapse
Simple english please.
I don't think anyone more should flash this fw.
It's buggy and crazy.
Also your nv-data.bin is modified.
I don't want my warranty to be un-voidable(by flashing original firmware).
I flashed through KIES and I believe this doesn't damage your phone. It's only thorugh Odin??
No, Kies modifies your /efs data as well. Flashing this firmware in any way shape or form will more or less permanently alter your phone
Zilch25 said:
No, Kies modifies your /efs data as well. Flashing this firmware in any way shape or form will more or less permanently alter your phone
Click to expand...
Click to collapse
Implying restoring a backup of the /efs folder after flashing back an original firmware will not undo any changes made by JPC.
I've restored the stuff in /efs to get my phone back to working order- I still have goofed up build numbers and things like that. It's unfair to imply that this is totally safe for anyone to do, especially those that aren't super comfortable screwing around with protected areas on their phones. It's doubly unfair for people to have the impression that odin is the only unsafe way to install it =P
dutchcow said:
Implying restoring a backup of the /efs folder after flashing back an original firmware will not undo any changes made by JPC.
Click to expand...
Click to collapse
So essentially I'm f*cked then.
Thread Astaire said:
So essentially I'm f*cked then.
Click to expand...
Click to collapse
Not necessarily, it's too soon to tell if it will effect anything... take comfort in the fact that 85% of the SGS XDA community flashed this. Even if there IS an issue people will find ways around it =P
So what exactly is stored in the /efs folder and why is it such a bad thing that JPC has modified it? I've flashed this firmware. Does this mean I can't go back to an older firmware now?
I'm not sure of everything contained in the efs folder, but it contains your nv_data.bin files which contain all the unlock codes and such, so at least for people who have carrier locked phones it causes a mandatory network unlock request. You can get around that by restoring the backup files that the firmware conveniently makes.
Those are really the only show-stopping bugs, the rest of them are a bit more subtle, such as marking your phone as being a korean variant =P Though this problem apparently hasn't cropped up for everyone.
ed10000 said:
So what exactly is stored in the /efs folder and why is it such a bad thing that JPC has modified it? I've flashed this firmware. Does this mean I can't go back to an older firmware now?
Click to expand...
Click to collapse
You can, I flashed back JP3 after having a lot of errors with JPC
Zilch25 said:
I'm not sure of everything contained in the efs folder, but it contains your nv_data.bin files which contain all the unlock codes and such, so at least for people who have carrier locked phones it causes a mandatory network unlock request. You can get around that by restoring the backup files that the firmware conveniently makes.
Those are really the only show-stopping bugs, the rest of them are a bit more subtle, such as marking your phone as being a korean variant =P Though this problem apparently hasn't cropped up for everyone.
Click to expand...
Click to collapse
Ah that's good to hear. Mine is the international version, so it should be fine. I thought the new recovery mode and stuff had problems or something.
EDIT:
iuzar said:
You can, I flashed back JP3 after having a lot of errors with JPC
Click to expand...
Click to collapse
After flashing back to JP3, do you still have the new recovery mode or back to the old one? Can you use Clockwork Recovery now?
ed10000 said:
Ah that's good to hear. Mine is the international version, so it should be fine. I thought the new recovery mode and stuff had problems or something.
Click to expand...
Click to collapse
It does, you've got to flash your stock I9000 kernel before trying to apply update.zip files- since your power button wont work as the selector haha So far that's the only issue I know of with it though
Edit: Make sure you flash back to the JPC kernel before you try to actually boot
Zilch25 said:
It does, you've got to flash your stock I9000 kernel before trying to apply update.zip files- since your power button wont work as the selector haha So far that's the only issue I know of with it though
Click to expand...
Click to collapse
Are you sure? Because right after flashing JPC, I went into recovery mode and did a Factory Reset. The volume up/down buttons worked fine for navigating through the menu and the Home button worked fine for clicking a menu item.
ed10000 said:
Are you sure? Because right after flashing JPC, I went into recovery mode and did a Factory Reset. The volume up/down buttons worked fine for navigating through the menu and the Home button worked fine for clicking a menu item.
Click to expand...
Click to collapse
That might be an issue for me because I'm on a captivate No physical home for me haha. I know for I9000 people rooting though they had to flash the original kernel to get it to work (Stole their trick but substituted the I897 kernel to get it to work for me), but I'm not sure why that is
Samsung have disabled the test keys in all firmwares after JP2. We don't have a real key yet, so gotta flash back to JP2 or before in order to apply an update.zip
Hopefully someone will find a new root-workaround soon.
windy31 said:
Samfirmware tweet 3hr ago that the new Froyo JPC firmware have some bootloader problem.
Any clue about this? Does it will permanently damage your phone?
I'm considering Flash this via ODIN or the HK one.
Click to expand...
Click to collapse
Perhaps SamFirmware had his SGS brick when he try to flash it with odin3.
Sent from my GT-I9000 using XDA App
Thanks for the clarification Ryan
As for samsung firmwares it seems he's just erring on the side of caution, he's got a post in Dutch up there that seems to roughly translate into him trying to avoid throwing up a suspicious firmware (the EFS changes etc) and potentially screwing tons of people, gotta respect that
Yes, especially since Samsung put this firmware up as a "beta" in kies withouth worrying about screwing people...
Any ideas?
I have been experimenting with upgrading and down-grading my tab, it now seems that I can't flash any ROM that contains a hidden.rfs, the flash will just stop near the end of flashing the hidden.rfs and never continue, then I have to go through recovery processes to get a working tab back.
I managed to get my Tab back to CPW standard UK JJ3 by dumping the ROM from my other Tab and writing it, I then tried to update with Kies, which also hung at what seems to be exactly the same place.
I have tried repartitioning several times with the p1_add_hidden.pit but it just doesn't seem to work.
Any ideas? Can I check the size of the hidden partition see if that' the problem? Then modify the hidden.rfs to make it smaller so it fits?
Nobody at all got any feedback on this?
Anyone had any luck with this? I'm guessing it's a partitioning issue but it'd be good to know.
alias_neo said:
Nobody at all got any feedback on this?
Click to expand...
Click to collapse
It sounds like you're currently partitioned without the hidden partition. I would think flashing a full ROM like JJ4 with the P1_add_hidden.pit in Odin would be the fix.
After thats up and running, use my JMC upgrade package to safely upgrade.
rotohammer said:
...use my JMC upgrade package to safely upgrade.
Click to expand...
Click to collapse
Time to upgrade to JMD me thinks
rotohammer said:
It sounds like you're currently partitioned without the hidden partition. I would think flashing a full ROM like JJ4 with the P1_add_hidden.pit in Odin would be the fix.
After thats up and running, use my JMC upgrade package to safely upgrade.
Click to expand...
Click to collapse
Roto i wanna ask you something. You say "safely" upgrade why ? Because on your FW's you remove the boot.bin and the SBL.bin ? So that a user wont be able to flash them and something go wrong ?
As far as i know my tab ( A euro one ), is factory unlocked and i will have no problem whatsoever in upgrading the bootloader and the baseband.
Isnt that right ?
sedde said:
Roto i wanna ask you something. You say "safely" upgrade why ? Because on your FW's you remove the boot.bin and the SBL.bin ? So that a user wont be able to flash them and something go wrong ?
As far as i know my tab ( A euro one ), is factory unlocked and i will have no problem whatsoever in upgrading the bootloader and the baseband.
Isnt that right ?
Click to expand...
Click to collapse
Unlocking is unrelated. I say safely because flashing a bootloader is the only thing that makes me squirm. If it fails your device is toast. I never want to give anyone firmware that has the potential to destroy their device. I'd feel bad
daniel.weck said:
Time to upgrade to JMD me thinks
Click to expand...
Click to collapse
Me too : ) maybe tonight after my guests leave.
rotohammer said:
Unlocking is unrelated. I say safely because flashing a bootloader is the only thing that makes me squirm. If it fails your device is toast. I never want to give anyone firmware that has the potential to destroy their device. I'd feel bad
Click to expand...
Click to collapse
And you are so right in removing them...
The leaks from Samsung's servers of JM6/JMA/JMC/JMD flash a signed recovery, after flashing it is impossible to flash unsigned sbl, boot, and zImage. No more downgrade (and possibly upgrade).
rotohammer said:
It sounds like you're currently partitioned without the hidden partition. I would think flashing a full ROM like JJ4 with the P1_add_hidden.pit in Odin would be the fix.
After thats up and running, use my JMC upgrade package to safely upgrade.
Click to expand...
Click to collapse
I thought my original post covered this? I can't flash _any_ ROM that uses the hidden partition. I have tried repartitioning a dozen times wit hthe p1_add_hidden.pit, that goes through fine, but NO ROM, full or otherwise, down or up from my current one will successfully complete flashing the "hidden" partition.
alias_neo said:
I thought my original post covered this? I can't flash _any_ ROM that uses the hidden partition.
Click to expand...
Click to collapse
You never mentioned JJ4 or Odin specifically, hence my post. Unless you spell out exactly which firmwares you tried and which software you used to flash with, how can anyone offer assistance?
If you've tried ALL firmware and All flashing software, that leaves only your computer or Tab at fault.
rotohammer said:
You never mentioned JJ4 or Odin specifically, hence my post. Unless you spell out exactly which firmwares you tried and which software you used to flash with, how can anyone offer assistance?
If you've tried ALL firmware and All flashing software, that leaves only your computer or Tab at fault.
Click to expand...
Click to collapse
Im not really worried about my Tab, i just think its a cause for concern that somehow iv stumbled on this problem. If its just the flash in my tab thats damaged its not a problem.
I have tried every firmware available on samfirmware as well as ripping the firmware from an identical tab i have.
Neither Heimdall, Kies nor Odin (either version) would get past flashing hidden and they all stop at about the same point. I have tried flashing various firmware without hidden with no problems. If i then repartition it will flash about 80% of the hidden then just stops.
Problem isnt my pc, i have tried several machines and virtual machines.
I think its a curious problem that would be good to find the cause of.
alias_neo said:
I think its a curious problem that would be good to find the cause of.
Click to expand...
Click to collapse
I agree. Do you have time to jump on irc #ModADroid-Galaxy-Tablet?
rotohammer said:
I agree. Do you have time to jump on irc #ModADroid-Galaxy-Tablet?
Click to expand...
Click to collapse
Cant at the mo, just off out to visit family, xmas and all...
Ill get back to you later tonight?
alias_neo said:
Cant at the mo, just off out to visit family, xmas and all...
Ill get back to you later tonight?
Click to expand...
Click to collapse
Sure, we're about to get a blizzard on the east coast of the US, so I may be cancelling my family visiting plans. Just ping me later.
rotohammer said:
Sure, we're about to get a blizzard on the east coast of the US, so I may be cancelling my family visiting plans. Just ping me later.
Click to expand...
Click to collapse
I'm around and will hop on the channel now. Don't have too long but maybe we can look into this a bit.
I just noticed what has veen going on with tje secured boot loaders etc. I will check mine with the script once I get home from my trip tomorrow to see if any info froem my tab is relevent to fixing the problem. I noticed a mention of creating jigs, im not sure what hardware is required but I have a couple of usb-rs232 connectors on order for an unrelated project so if it requires the same hardware I can put a spare one to use and build a jtag/jig cable for the tab and see if I can help the cause.
Sent from my GT-P1000 using XDA App
Question for rotohammer
Once upon a time I bricked my Verizon Galaxy Tab trying to flash a custom ROM, the only way I could bring it back was by using Odin and flashing the hidden pit. Now every time I install the original verizon rom my tab is extremely, extremely slow. I have been trying to reformat and wipe clean to start over, but I haven't had any luck.
Any suggestions on how to: either flash the right pit on it or remove the hidden partition? Anything I can do to bring my tab to full speed. I have also tried the overclocked rom with voodoo5, and at this point anything I put there is extremely slow. The only way I can get it to operate normally (Kind of) is to flash the Honeycomb Alpha rom, then restore to a day when it was working fine, however this breaks my auto rotate sensor.
That is how I use it now a days, but it sucks that I cannot use it on landscape mode.
Any help will be greatly appreciated.
Follow up from my previous question to rotohammer
By the way, just in case you were wondering, the rom I flashed to unbrick it was a GSM ROM, that was the only way to make it past the Samsung logo.
So, my theory is that I have problems with it because now I am trying to flash CDMA roms to a GSM partition/files system? Excuse me if my post does not make much sense or I am using the wrong terminology, I am extremely new a this. I just know enough to get myself in trouble.
Thank you again for any help.
I've encountered the same problem as the original poster. SGT with CPW CSC causes problems with the hidden.rfs when trying to flash ROMs. Does appear to be a size issue with the hidden partition - I wonder whether this has been sized incorrectly when it was originally flashed as re-partitioning doesn't help. I'm currently on a XEU ROM so I guess I'll find out when Gingerbread is officially released whether I can flash that or not. If not, I think it'll need to the internal SD card repartitioning.
Anyone got any tips on how to do this?
I will send my stock I897UCKB2 phone back when I get a new one due to USB connectivity problems. I plan to search for all files newer than a certain date on the new KB2 and my existing (which is rooted with CWM) and then delete or replace files to get my old phone back to "normal" before sending it back. I don't know if all changes show up in files off of "/" though. I assume bootloaders do not but does everything else? I know some files are updated through normal use but items like turning off boot sounds via SGS Tools (requires root) creates backup sound files, etc which I plan to delete. Should searching for updated files allow me to clean up traces before running "unroot"?
i suggest using the odin3 1-click to go back to stock 2.1 and then master clearing to delete all of the files that arent supposed to be there
dsilvan55 said:
i suggest using the odin3 1-click to go back to stock 2.1 and then master clearing to delete all of the files that arent supposed to be there
Click to expand...
Click to collapse
I think one of the reasons they haven't released I897UCKB2 via KIES is so they will know if we do that. If they give you a refurb now and you flash anything else, you can not get KB2 back. KB1 (via KIES) may be the same software but KB2 is kind of "signed". If you change it, your done getting refurbs...
I'm speculating but it makes sense to me. Therefore, I am sending it back as KB2 but planning to erase all tracks of root. I'd like to know what others think though, and if they agree, my question is applicable.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Yes thats true. Plus if your phone is above version 1010 it could mess up your phone pretty badly. Im wondering how did you get kb2 in the first place?
edit: I think you can master clear still without going to stock jf6. i think it will just delete all the files and add the needed files back such as sdcard/dcim/ or sdcard/android/
dsilvan55 said:
Yes thats true. Plus if your phone is above version 1010 it could mess up your phone pretty badly. Im wondering how did you get kb2 in the first place?
edit: I think you can master clear still without going to stock jf6. i think it will just delete all the files and add the needed files back such as sdcard/dcim/ or sdcard/android/
Click to expand...
Click to collapse
Thanks. I recently got a warranty replacement which is how I have KB2 and it is a 1012 so I agree JF6 would cause problems. I agree a master clear simply formats the internal SD card (user part) so I plan to do that. I'm trying to find how to clear the system file changes such as CWM, superuser, etc
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Enter these codes in the dialer
Hard reset: *2767*3855#
Factory data reset: *#*#7780#*#*
studacris said:
Enter these codes in the dialer
Hard reset: *2767*3855#
Factory data reset: *#*#7780#*#*
Click to expand...
Click to collapse
Just wondering what does a hard reset do compared to factory?
What does the hard reset do?
xThe Enforcer said:
Just wondering what does a hard reset do compared to factory?
Click to expand...
Click to collapse
I'm wondering the same thing. Does a hard reset wipe basically do a factory reset (clearing user data) and also wipe the internal SD (the 14G compared to the 2G)? I think I read that somewhere but couldn't confirm when searching.
Not sure honestly....but since you're about to wipe your phone do one and see what it did then do the other and post results
studacris said:
Not sure honestly....but since you're about to wipe your phone do one and see what it did then do the other and post results
Click to expand...
Click to collapse
Well I tested both of them. Factory data reset (the code you listed) does the same thing as what you see if you choose it under Privacy in settings - You see a dialogue saying it will erase everything, etc. You have to click confirm a couple of times and then you see big red letters about formatting the system. It then reboots in 3e recovery briefly and installs "default apks". The phone has all apps wiped and the internal SD (the 14G) is wiped.
The only difference with the "hard" reset is you don't get the dialogue about erasing everything - it goes straight to the red letters and the result is the same.
Also, the extra files in /system/xbin are still there. Before I did the wipes above, I got the computer to briefly see the phone - if I jiggle the connector on the phone just right and don't touch it -it works (sometimes). While it was connected, I ran "unroot" from SuperOneClick 1.95 which got rid of superuser (but not the files). I then did the factory resets.
Sweet, thanks for the 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