Related
Hi guys,
I've owned android phones since the G1, motocliq, nexus, sgs2 (intl), motodroid, all rooted, custom rom, etc etc... So when a friend asked me to unlock (for which i had to root) his i777 I thought I could handle it.
I followed the guide: http://forum.xda-developers.com/showthread.php?t=1286220
Went into download mode (could only do it with the VOL+-USB trick) and flashed CWM on Odin. Flashed fine, no problem, rebooted and only showed SAMSUNG letters on the bootup, nothing more. Tried going into CWM Recovery, no luck, Download mode, works fine. So I went over and re-flashed it, worked, but still can't get it to boot, or Recovery to work.
So then I started trying to flash other PDA's thinking i could do it, and maybe cwm was bugged, every time I try to flash ANYTHING that's not that specific CWM it says Write error, FAILED. When i reboot, the phone is softbricked (computer-phone logo saying connect recovery on kies). After this nothing at all will flash, except that CWM, which gives me download mode again... Which doesnt matter because the softbrick screen is a download mode in itself.
Im running out of options, im not sure where I should keep looking, Heimdall, installed, tried to flash, it transfers, at 99% says error writing and cancels. Tried flashing a new .pit and repartitioning, same story, wont let me.
Any suggestions would be more than welcomed :/
Sincerely,
Rodo
See if you can go back to out of box:
http://galaxys2root.com/att-galaxy-s2/how-to-unroot-att-galaxy-s2-sgh-i777/
Rodocopz said:
Hi guys,
I've owned android phones since the G1, motocliq, nexus, sgs2 (intl), motodroid, all rooted, custom rom, etc etc... So when a friend asked me to unlock (for which i had to root) his i777 I thought I could handle it.
I followed the guide: http://forum.xda-developers.com/showthread.php?t=1286220
Went into download mode (could only do it with the VOL+-USB trick) and flashed CWM on Odin. Flashed fine, no problem, rebooted and only showed SAMSUNG letters on the bootup, nothing more. Tried going into CWM Recovery, no luck, Download mode, works fine. So I went over and re-flashed it, worked, but still can't get it to boot, or Recovery to work.
So then I started trying to flash other PDA's thinking i could do it, and maybe cwm was bugged, every time I try to flash ANYTHING that's not that specific CWM it says Write error, FAILED. When i reboot, the phone is softbricked (computer-phone logo saying connect recovery on kies). After this nothing at all will flash, except that CWM, which gives me download mode again... Which doesnt matter because the softbrick screen is a download mode in itself.
Im running out of options, im not sure where I should keep looking, Heimdall, installed, tried to flash, it transfers, at 99% says error writing and cancels. Tried flashing a new .pit and repartitioning, same story, wont let me.
Any suggestions would be more than welcomed :/
Sincerely,
Rodo
Click to expand...
Click to collapse
Use my return-to-stock packages from dev forum.
Hi Entropy, I've tried but I can't seem to find an Odin flashable .tar, they're all CWM flashes and my CWM is screwed.
> http://forum.xda-developers.com/showthread.php?t=1289460
Oh and I tried flashing http://forum.xda-developers.com/showthread.php?t=1286432 with heimdall too. write error
Did you try this?
http://forum.xda-developers.com/showthread.php?t=1286432
This has the back to stock odin files, Thanks to Entropy!
This has UCKH7_stock_odin_noroot.7z which is flashable by odin. Try this.. You have to use 7zip to get the tar file..
Yup.. no luck :/
Error writing
Changed drivers, installed heimdall, used a different computer, no luck. (and works just fine with my other phones so I doubt its that.)
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> factoryfs.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Try installing Entropy's stock, or stock + root using one of these Odin3 One-Click Downloaders. That will take some of the variables out of the equation. If that doesn't go, you need to figure out if the problem in in the pc or the phone. Let us know your results.
I don't guess you need instructions, but if you do, they are in the flashing custom binaries guide linked in my sig.
Tried at least two previously, they report the same error. giant FAIL in red. I tried another computer previously, and this computer flashes my i9100 just fine (which i presume are the same drivers). In any case I installed the heimdall drivers for USB (on windows, which ruins Odin, but works fine after you uninstall those drivers) included in the package.
Still having no luck with this issue... Anyone know what could be causing that write error on download mode Odin? Perhaps I could flash a different recovery console?
Have you installed Samsung kies just to make sure you have proper drivers? Can make all the difference in the world.
Some people have a tough time getting the wrong drivers uninstalled. Easy check if that is the problem, go to a different pc that you haven't plugged your phone into and first install the right version of kies that you need.
Then plug your phone in and flash through Odin, transfer files over or redownload, hopefully all will be well.
Sent from my SAMSUNG-SGH-I777 using XDA App
Im still stuck with this issue and apparently after a few extra flashes it now shows:
Custom binary download: NO
Current Bunary: Samsung Official
Which isnt true, but w/e. It will still only flash SGH-1777 clockwork recovery and it will now not even show the samsung logo and become unresponsive as soon as you put the battery in. (the phone heats up, even if i dont try to turn it on, drains the battery dead in a couple hours)
So, I want to give it a try with heimdall and a full repartitioning, but I do not have the necessary files. Ive been looking and I cant find all the partition files, aka
PDA/Code:
FactoryFS=factoryfs.frs
Kernel(zImage)=zImage
Param.lfs=param.lfs
Primary Bootloader=boot.bin
Secondary Bootloader=slb.bin
CSC:
Cache=cache.rfs
Database Data=dbdata.rfs
In Other:
Modem=modem.bin
Recovery=recovery.bin
Could someone dump these files for me? Thanks!
A good day to all you fellow developers, trouble shooters and geeks from other corners
I wanted to create my account here some time now, but now it's been kind of necessary.
You see, i (lightly) bricked my phone... i like to call it "clayed".
I honestly thought i had done my research and everything went ok... until i used EZ-Unlock to unlock my bootloader.
I remember pressing the "unlock" button 3 times or so because the status above said "Unknown" while a small temporary message beneath said "Bootloader unlock: successful".
The next morning, when my phone shut down due to an empty battery (forgot to charge my phone, so no excessive drain or anything), i plugged it into the wall for battery charging.
Then it went directly in download mode, which i can't get past.
The screen ONLY consists of a plain android in front-view with underneath the text: Downloading... Do not turn off target!!"
So no extra text as within Odin mode.
However i CAN get into Odin mode and CWM recovery mode.
I think that the bootloader got corrupt in some way myself.
But what should i do?
Flash it with a new one? And what is the best way?
I don't have a recovery at hand... but i don't care if the whole storage needs to be wiped if needed.
====================================
INFO:
- Samsung Galaxy S GT-i9300
- Rooted
- Bootloader unlocked (Houston, we have...)
- Odin mode = possible
- CWM recovery mode = possible
====================================
Thanks for reading!
Greetings
Well for a start, the international doesn't have a locked bootloader.......and that unlock app is for gs3 Verizon, which I assume does have a locked bootloader, so either you don't have an international and are in the wrong section, or, as per most posts here, you have failed to read and understand what you are doing
Thanks for the quick response.
I apparently didn't catch the parts about not having a locked bootloader, and the fact that the app is for Verizon.
My phone is the international version.
So, i know it's my fault although i really thought i knew enough while not even being close.
There is so much to rooting (and around it).
Do you, or anyone else, perhaps know what is going on with my phone from this point... and what to do about it?
Well the best bet would be to flash a stock firmware with Odin and pray like hell, what country are you in, and have you used Odin before?
slaphead20 said:
Well the best bet would be to flash a stock firmware with Odin and pray like hell, what country are you in, and have you used Odin before?
Click to expand...
Click to collapse
Oof that doesn't sound too good.
I did use Odin (version 3.07) before to root my phone. I understand it's this desktop application which allows to flash/inject software to portable devices.
I am from the Netherlands, where i got my phone from T-Mobile.
With stock firmware, you mean like flashing my current state with the original TouchWiz ROM?
yes, then factory reset
Firstly I'd suggest downloading latest bootloader and patching it with odin even before patching anything else. You can't be sure that it's stable and won't cause any further issues after flashing.
JustArchi said:
Firstly I'd suggest downloading latest bootloader and patching it with odin even before patching anything else. You can't be sure that it's stable and won't cause any further issues after flashing.
Click to expand...
Click to collapse
Luckily i've got patience, so i waited a bit before taking action.
Patching the latest bootloader through odin first seems a good idea indeed.
But should i do only that and then try to reboot since everything else still is untouched...
or would it seem better to setup odin with the new bootloader AND the stock ROM all in 1 go?
I'd suggest starting with bootloader, then rebooting. Then on the second go flashing custom recovery and on the last step flashing rom but not through odin but through recovery.
You can find my guide on flashing custom recovery in my ArchiDroid topic if you wish.
JustArchi said:
I'd suggest starting with bootloader, then rebooting. Then on the second go flashing custom recovery and on the last step flashing rom but not through odin but through recovery.
You can find my guide on flashing custom recovery in my ArchiDroid topic if you wish.
Click to expand...
Click to collapse
Thanks so much for the help already!
I'm going to read your guide and then get to work.
I'll place the outcome here of how it went and if there were any unusual hickups along the way as feedback to potential other unfortunate tweakers like myself... although i hope other people won't be as clumsy as me.
And the last one. Flashing with odin is nearly the same but if you're flashing bootloader then download latest bootloader and place it as "Bootloader" in Odin.
JustArchi said:
And the last one. Flashing with odin is nearly the same but if you're flashing bootloader then download latest bootloader and place it as "Bootloader" in Odin.
Click to expand...
Click to collapse
Well, i've done what you specified.
And there's just a slight improvement on the bootup.
The difference with the previous experience is, that there is now a quick glimpse of the Samsung logo... but then immediately the plain download screen pops up.
I did flash a custom recovery though (Philz recovery).
I haven't tried flashing a custom ROM yet, but something tells me that that's not going to help since it's just the upper layer of everything.
Here is my Odin output:
==================
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> bootLoader_I9300XXEMC3.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
If you've flashed bootloader and actually you CAN enter recovery (through combination vol-up+home+power) then everything is fine and don't worry. Just don't forget to clean your old system.
If however you're unable to do it then we'll try to repartition your phone using PIT file. But please firstly make sure that it's absolutely necessary.
JustArchi said:
If you've flashed bootloader and actually you CAN enter recovery (through combination vol-up+home+power) then everything is fine and don't worry. Just don't forget to clean your old system.
If however you're unable to do it then we'll try to repartition your phone using PIT file. But please firstly make sure that it's absolutely necessary.
Click to expand...
Click to collapse
Yes i am able to enter recovery through vol-up+home+power.
But alright, i should then go into recovery and do:
- Wipe cache partition
- Wipe Dalvic Cache (?)
- Wipe Data/Factory Reset
- Install Zip (being the custom ROM like CyanogenMod for instance)
Firstly make sure that you have working .zip on your internal/external sdcard as it will be required.
From the recovery move to "mounts and storage" tab and click on format /system /data /cache /preload and if you have .zip on external sdcard also /sdcard.
Now you can install rom and everything should be fine.
BTW I suggest to stick with Samsung Base first, as it's proven to be stable and working. But it's up to you.
Ok, i will use the format method like you said.
I have no external sdcard so there's nothing to be done there.
One thing that's bothering me is that i should flash a new rom (Samsung's stock TouchWiz which i'm going to download) right from the recovery.
But, from how i see it, there's no way around than doing it from odin since i can't just put something onto my phone's storage like you do with the folder app inside the system.
Yeah I totally forgot that you can't connect internal sdcard with pc while being in recovery.
So basicly yes, you should flash some original soft from Samsung through Odin and eventually later put anything on your internal sdcard.
BTW it's much easier if you could find any external sdcard actually. You don't have to flash through odin then.
I had the same problem here on my galaxy s 3...
And here is what i did:
1) go to sammobile.com and download the latest firmware fot your country.
2) download odin.
3) turn your phone on and connect to your pc.
4) remember to have kies instaled (just download it from samsung's website.).
5) extract the file you donloaded from sammobile.com.
6) open odin and select PDA.
7) navigate to where you extracted the fitmware and click start.
8) thats it you are done.
It should take 4/5 minutes to complete.....
Please hit Thanks
Sent from my GT-I9300 using xda premium
Mindu99 said:
I had the same problem here on my galaxy s 3...
And here is what i did:
1) go to sammobile.com and download the latest firmware fot your country.
2) download odin.
3) turn your phone on and connect to your pc.
4) remember to have kies instaled (just download it from samsung's website.).
5) extract the file you donloaded from sammobile.com.
6) open odin and select PDA.
7) navigate to where you extracted the fitmware and click start.
8) thats it you are done.
It should take 4/5 minutes to complete.....
Please hit Thanks
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Where do i need Kies for? I'm not using it.
Digitalstone said:
Where do i need Kies for? I'm not using it.
Click to expand...
Click to collapse
KIES is the best bet to install phone drivers.
Ensure it is stopped in the Windows Task Manager before starting ODIN! Else it's a one way ticket to la-la-land for your phone. Good luck, mate! :thumbup:
Sent from my GT-I9300 using xda app-developers app
Hello,
My Galaxy s2 is stuck in boot loop, I can see only the GS2 logo.
It went into this situation after holding down power button trying to turn it off.
Tried to remove battery and nothing changed.
Entered recovery mode and did wipe cache and then reboot.
It went past the initial logo, showed samsung animation and then it went back to samsung logo boot loop. It never went to samsung animation again.
From that point on it does not boot to recovery mode, it shows the android robot with the spinning cog for a while and then it goes back to the samsung logo boot loop.
The phone can go to download mode without problem. I have not tried to install a stock firmware through odin, since I would like to get a backup of the sms messages from the phone first. I already have backup of pics, contacts, etc so I dont care about anything else besides the sms.
The phone was running the latest spanish stock JB version
GT-I9100 Galaxy S II
PDA: I9100XWLSD
CSC: I9100FOPLS4
MODEM: I9100XXLS8
Added: 2013-02-03
The only modifications to stock were
. Root when it was running ICS
. CSC change from EUR to FOP (so that it auto upgraded to JB from ICS)
The phone retained root after the auto JB upgrade
Do you know if there a solution to this situation? I am still under warranty so I can take it back to samsung so I would like to avoid installing CWM recovery kernel that would make them immediately reject service due to warranty void.
thank you in advance!
Yes, you can keep trying to flash a stock firmware in Odin. Click the link in my signature if you're having troubles with the flash failing. Flash the JB version you were on before, that's got the most chance of working with out having to wipe.
Personally, I think you're going to have to get a working recovery and factory reset to be honest.
Sent from a galaxy far, far away
Hopper8 said:
Yes, you can keep trying to flash a stock firmware in Odin. Click the link in my signature if you're having troubles with the flash failing. Flash the JB version you were on before, that's got the most chance of working with out having to wipe.
Personally, I think you're going to have to get a working recovery and factory reset to be honest.
Sent from a galaxy far, far away
Click to expand...
Click to collapse
thank you for answering, so if I install the same version through Odin, it will not wipe out the current phone contents by default?
Toliver said:
thank you for answering, so if I install the same version through Odin, it will not wipe out the current phone contents by default?
Click to expand...
Click to collapse
Correct. A 1-part firmware will not wipe by default. If you flash a 3-part firmware (JB leak, LSJ for instance) that WILL wipe by default.
If you flash something other than the firmware you were on directly before the bootloop, you've got pretty much no chance of getting out of the bootloop without a factory reset. If you flash the same firmware you were on before the bootloop, then there's a chance of getting it to boot up with all your data.
If that (flashing with the same stock ROM) doesn't work, then I'm afraid its down to a factory reset, sorry.
Hopper8 said:
Correct. A 1-part firmware will not wipe by default. If you flash a 3-part firmware (JB leak, LSJ for instance) that WILL wipe by default.
If you flash something other than the firmware you were on directly before the bootloop, you've got pretty much no chance of getting out of the bootloop without a factory reset. If you flash the same firmware you were on before the bootloop, then there's a chance of getting it to boot up with all your data.
If that (flashing with the same stock ROM) doesn't work, then I'm afraid its down to a factory reset, sorry.
Click to expand...
Click to collapse
Ok then, I will give it a try and see how it goes. Another solution that I was thinking about is to try to install CWM through odin (i'm not sure if it's possible though) then boot into CWM and get backup through it. Then if I apply a stock firmware through odin, this would remove CWM and install the stock recovery kernel back, correct?
Yes, that's possible. You can flash Philz kernel via Odin, it's stock kernel only with root CWM. Other than that its the same. You could do that procedure using his kernel. When you flash stock rom via Odin then yes, you'd get rid of the custom recovery.
Depending on what you want to do (warranty etc) read up about the flash counter and then triangle away.
Sent from a galaxy far, far away
regarding the 1-part firmware, I downloaded from sammobile the I9100XWLSD_I9100FOPLS4_FOP.zip.
The zip archive contains a tar.md5 file I9100XWLSD_I9100FOPLS4_I9100XXLS8_HOME.tar.md5 and a dll file SS_DL.dll.
So I should use only the tar.md5 in the PDA section of odin, right? should I keep this dll in the same folder as the tar.md5 in case odin needs it?
Also does it make any difference which odin version should I use?
thaks again
Well I suppose it can't hurt to put it in the same directory, but I don't know if it really does anything. Yes, flash it in the pda section.. Which version? Take your pick. I usually use 3.0.4 but have also used others. Click my signature if you want a zip file with a few versions.
Sent from a galaxy far, far away
I tried flashing the same rom as it was installed but nothing changed, after the first boot I see the robot with the cog, a thin progress bar filling below it and then it goes to boot loop. No luck getting into recovery, still the same symptom... Besides the sms backup I am thinking about how to recover it, should I try installing 4.0.3 that was the factory default? Any more ideas??
thanks again
The odin log seems clean though, no error or anything else
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSD_I9100FOPLS4_I9100XXLS8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> cache.img
<ID:0/007> NAND Write Start!!
<ID:0/007> factoryfs.img
<ID:0/007> hidden.img
<ID:0/007> modem.bin
<ID:0/007> boot.bin
<ID:0/007> param.lfs
<ID:0/007> Sbl.bin
<ID:0/007> zImage
<ID:0/007> RQT_CLOSE !!
<ID:0/007> RES OK !!
<ID:0/007> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/007> Removed!!
And can you try a factory reset from the stock recovery? You're not on 4.0.4 so it'll be safe.
@gastonw, can you have a look here? I know that I've seen Odin passing but still no boot... I just can't remember how on earth it was fixed. It seems I didn't bookmark it either.
Sent from a galaxy far, far away
Hopper8 said:
And can you try a factory reset from the stock recovery? You're not on 4.0.4 so it'll be safe.
@gastonw, can you have a look here? I know that I've seen Odin passing but still no boot... I just can't remember how on earth it was fixed. It seems I didn't bookmark it either.
Sent from a galaxy far, far away
Click to expand...
Click to collapse
Could you provide more details on how to do a factory reset from stock recovery? Do you mean to flash 4.0.3 via odin? Or is it some options in odin that would enforce factory reset?
More details are to search for it mate. It's covered so many times that it's just plain spoonfeeding if I'm to post it.
Sent from a galaxy far, far away
Eventually I made it work by installing the 4.0.3 EUR via odin. I did not allow it to boot into the OS, as soon as it finished flashing via odin, I rebooted into recovery mode. This time it went in successfully. Then I used the CWM recovery kernel that just runs from the sd (it does not install) and got the full backup. Later on by using nandroid manager I recovered the sms messages + more (apps, etc). Thanks for all the help!
Stupidly, I took the update (to MI1) after getting my new S4. I later discovered this meant Safestrap was my only option for installing custom ROMS.
Even more stupidly, I decided I wanted to do a 'clean' install of my ROM, so I wiped everything with Safestrap.
Now I can only boot into download mode. Attempting to boot normally or into recovery mode results in the "Firmware upgrade encountered an issue. Please use Software Repair Assistant & try again." screen.
Kies is a no-go since I can't access my serial number now.
So far, everything I've tried to flash with Odin (both 1.85 and 3.09) results in:
...
<ID:0/005> aboot.mbn
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
including the ME7 image which fixed a similar problem in this thread.
Is there any hope?
ANBHF said:
Stupidly, I took the update (to MI1) after getting my new S4. I later discovered this meant Safestrap was my only option for installing custom ROMS.
Even more stupidly, I decided I wanted to do a 'clean' install of my ROM, so I wiped everything with Safestrap.
Now I can only boot into download mode. Attempting to boot normally or into recovery mode results in the "Firmware upgrade encountered an issue. Please use Software Repair Assistant & try again." screen.
Kies is a no-go since I can't access my serial number now.
So far, everything I've tried to flash with Odin (both 1.85 and 3.09) results in:
...
<ID:0/005> aboot.mbn
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
including the ME7 image which fixed a similar problem in this thread.
Is there any hope?
Click to expand...
Click to collapse
Use the ml1 image. Once upgraded you cant go backwards in firmware.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
You didn't really screw yourself as much as you think, if you were on ME7 before upgrading to MI1 then it wouldn't have mattered since ME7 has a locked bootloader, thus Safestrap is the only option. If you had MDK however... then yeah you screwed yourself, but if you just bought it that's very unlikely
Yeah, box says it was ME7.
So I got the (rooted) MI1 ROM from this thread , in flashed it with Odin (using the PDA button in v1.85). It completed, and Odin isn't claiming there were any problems, but I still can't get it to boot normal or into recovery mode. If I try to do either, the upper left corner of the screen says, in red, "Could not do normal boot." and it goes back into downloading mode.
Guessing that's still not the right ROM or I installed it wrong?
UPDATE:
Problem solved. I followed the steps in this thread, using the ROM provided there, and the exact version of Odin listed.
I will not go into detail but suffice to say I was running my Samsung Galaxy S3 GT-I9300 on a stock Samsung Android 4.1.2 ROM and it was rooted and had a custom CWM Recovery.
I then flashed to CM 10.0.0 but encountered problems and tried to revert to my original ROM. This resulted in my phone displaying the initial black background boot screen with the words "Samsung Galaxy SIII GT-I9300". It stuck there and I could not switch it off nor could I get into Recovery Mode.
I was able to get into Download mode and connect to Odin to reflash my original ROM but Odin continually got stuck in the process at "Setup Communication" and on the odd occasion it got past that it then stuck on "Get Pit Mapping".
After much research of this and other forums found one lone article about Samsung introducing new ROMS from July 2013 onwards which had efs2 and that once upgrading to an efs2 ROM you could not go back to a previous efs1 ROM which I think I tried to do.
I eventually decided therefore to bite the bullet and I downloaded GT-I9300.pit and flashed it using Odin with Re-Partition selected. I was then able to flash Samsungs latest Android 4.3 (I9300XXUGMK6) ROM for the I9300.
The result is that whilst the phone is again fully functional I am unable to install a custom recovery nor can I root my phone.
I thought that if I used the GT-I9300.pit file it would re-partition the phone as a I9300 should be partitioned but it seems I was wrong.
I am happy with my phone now that I have recovered it but would like to be able to backup my rom but I need root to do that. Does anyone know what I have done with my phone and are you able to advise as to how I might now root it again?
Thanks
matrixmainframe said:
I am happy with my phone now that I have recovered it but would like to be able to backup my rom but I need root to do that. Does anyone know what I have done with my phone and are you able to advise as to how I might now root it again?
Thanks
Click to expand...
Click to collapse
After flashing the stock rom when coming from a custom rom is always best to do a factory reset to clear the phone.
You can root with CF auto root from my signature it works perfectly well on stock 4.3 MK6, then use TWRP or Philz recovery both are in the Dev section
ag4751 said:
After flashing the stock rom when coming from a custom rom is always best to do a factory reset to clear the phone.
You can root with CF auto root from my signature it works perfectly well on stock 4.3 MK6, then use TWRP or Philz recovery both are in the Dev section
Click to expand...
Click to collapse
When I try to flash a recovery or try to root I get the following.
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-m0-m0xx-gti9300.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
As you can see from the above it looks as though the process falters at "<ID:0/003> Get PIT for mapping.." which would appear to have something to do with the fact that I had to re-partition using GT-I9300.pit and that is what prompted my question in the first place.
It appears to me that the GT-I9300.pit file has altered my partitions in a non I9300 way despite having I9300 in the filename and that is why I posted the question in the hope someone would know what I had done and hopefully know a way I could either reverse what I had done or suggest a way to root despite my apparently new partition format?
matrixmainframe said:
When I try to flash a recovery or try to root I get the following.
It appears to me that the GT-I9300.pit file has altered my partitions in a non I9300 way despite having I9300 in the filename and that is why I posted the question in the hope someone would know what I had done and hopefully know a way I could either reverse what I had done or suggest a way to root despite my apparently new partition format?
Click to expand...
Click to collapse
Have a look here then you my be able to recover your device, it is Korean based so will default to KOR not BTU but it could repair the PIT problem if that is what you have.
ag4751 said:
Have a look here then you my be able to recover your device, it is Korean based so will default to KOR not BTU but it could repair the PIT problem if that is what you have.
Click to expand...
Click to collapse
Please read my initial post(#1).
I have already recovered my phone and it is working correctly on Samsung Official Stock 4.3 ROM (Android 4.3 - I9300XXUGMK6) EXCEPT that I cannot flash a custom Recovery nor can I root the phone. I have several apps that only operate on a rooted phone so just rooting it without a custom recovery would suffice.
If someone tells me that it is no longer possible to root my phone then I will be disappointed but I can live with it. I just thought someone might know the answer.
That problem in Odin might be related to incorrect drivers for your phone.
Remove any kies or Samsung softwares and reboot pc. Reinstall kies and connect phone 2 pc for drivers install. Then try a different usb port to flash smth on the phone.
Trimis de pe al meu GT-I9300 folosind Tapatalk
matrixmainframe said:
Please read my initial post(#1).
I have already recovered my phone and it is working correctly on Samsung Official Stock 4.3 ROM (Android 4.3 - I9300XXUGMK6) EXCEPT that I cannot flash a custom Recovery nor can I root the phone. I have several apps that only operate on a rooted phone so just rooting it without a custom recovery would suffice.
If someone tells me that it is no longer possible to root my phone then I will be disappointed but I can live with it. I just thought someone might know the answer.
Click to expand...
Click to collapse
I think i had the same problem with rooting and done reinstalling drivers and change the port so it is now rooted.
Also try unticking autoreboot then after the instalation is done disconnect the phone and remove/reinsert battery and boot to recovery so the auto root files start to install...
Of course everything you do is at your own risk...
BR