Hey guys! I'm trying to fix a Vodafone Nexus S that's having some serious issues. I'm pretty sure there is something wrong with the SD as in it's fried. I can either boot into Fastboot or Download mode. My computer won't pick up the phone in fastboot though, but it does with odin. I have the USB drivers installed. When I mount the SD to the computer, everytime it says that the sd card must be formatted in order to use it. So, if I do that, not using quick format, and then check to see if it was formatted, it shows everything on the card still. Or, it says Windows unable to perform Format. I just can't access anything like the backup or the ROM to reflash it. I'm hoping that by flashing a stock firmware with odin, I may be able to boot the phone into the OS and then maybe figure out what's wrong with the SD card. Right now, if I try to reboot the phone it just goes back into CWM. But, I can't find a version for the i9023 that will work on Australian Vodafone. I've searched but haven't had any luck. Would someone be able to help me or to point me in the right direction? I'd appreciate it greatly!
Odin is a tool for flashing Samsung firmware on Samsung phones only! Although the nexus s is built by Samsung it does not use Odin for flashing firmware so you will never find anything that will work with Odin.
If you can get into CWM does the card mount ok through that? Goto mounts and storage >> mount USB storage. If that works then you can copy over your CWM flashable ROM and then flash away.
You should be able to flash official firmware using from fastboot mode using ADB too. Im sure there is a guide on here somewhere.
Jamalsid said:
Odin is a tool for flashing Samsung firmware on Samsung phones only! Although the nexus s is built by Samsung it does not use Odin for flashing firmware so you will never find anything that will work with Odin.
If you can get into CWM does the card mount ok through that? Goto mounts and storage >> mount USB storage. If that works then you can copy over your CWM flashable ROM and then flash away.
You should be able to flash official firmware using from fastboot mode using ADB too. Im sure there is a guide on here somewhere.
Click to expand...
Click to collapse
I've flashed my i9023 with Odin, several times. Found everything I needed at samfirmware.com (you must register as a user to download)
These typos came from my i9023
Yes, Nexus S can use Odin
Sent from my Nexus S using Tapatalk 2
Really! Wow I never realised! Apologies for mis-informing.
Sent from my Nexus S using Tapatalk 2
Beautiful! Thank you all for the help. I'll have a look when I get home. Hopefully, throwing a new firmware on the phone will get it up and running again.
Sent from my HTC One X
EDIT: So, I checked on samfirmware.com and there isn't a firmware listed for Australia or Vodafone. Is there one that would work on the version that I have or am I out of luck?
Reptilez_DK said:
I've flashed my i9023 with Odin, several times. Found everything I needed at samfirmware.com (you must register as a user to download)
These typos came from my i9023
Click to expand...
Click to collapse
In samfiremware, I went to the additional files to get a flashprogram, when I download it and extract it. it asks me for a password. ): Idk what to do.
The password might be samfirmware
Sent from my Nexus S using Tapatalk 2
Related
[Q]
Hi,
I have nexus s GRJ22 Android 2.3.4 I904. I tried rooting it using clockwork and super user but after doing that when i reboot It stays in the google logo. I could find that i was not able to mount system in the clockwork recovery with means that its not having sufficient permissions .
1. Factory reset - not working
2. Tried fixing permissions - not working
3. tried remounting - not working
what i'm possible to do is get into fastboot mode and clockwork recovery mode and in the normal booting it stays at the google logo.
with this i can say i messed up something when i was rooting. and the phone is useless now.
The last option i know now is fastboot flashing of all the images (boot, system, recovery). How to flash everything finally and bring it back to the state which I got from the factory?
I'm looking for if any one has theses images so that I can fastboot flash it and bring it back in an operating condition.
I'm new to android development, android devices and a noob.
Please do ask If you guys need any more info.
I appreciate any answers and thanks for reading my question.
First, make sure that ClockWorkMod recovery that you installed is the right version for your NS model (sorry but I don't know what the "I904" means)
After you flashed the correct recovery then I'd suggest you go to this thread and see if there is a full OTA package for your NS model. If there is one then you can download it, connect your phone to a PC, mount SD card from the recovery, copy the package over then flash it. That should bring your NS back to life.
If there is no OTA package for your model then you can search/ask for a stock nandroid backup of your phone model. It's most likely that someone has already posted it here in xda.
suksit said:
First, make sure that ClockWorkMod recovery that you installed is the right version for your NS model (sorry but I don't know what the "I904" means)
After you flashed the correct recovery then I'd suggest you go to this thread and see if there is a full OTA package for your NS model. If there is one then you can download it, connect your phone to a PC, mount SD card from the recovery, copy the package over then flash it. That should bring your NS back to life.
If there is no OTA package for your model then you can search/ask for a stock nandroid backup of your phone model. It's most likely that someone has already posted it here in xda.
Click to expand...
Click to collapse
Thanks for the reply.
its not I904 I'm sorry its I9020 which is the model number of the phone.
I tried the link that you had posted already but it stops at getprop function in the script when i do the update and says status 7 error and the update fails because the /system is not mounting.
Kindly suggest me to bring this phone back.
Hmm, I still have the impression that you have the incorrect version of CWM. What is your service provider? As far as I remember, the I9020T and I9020A require a different version of CWM. And also what is the version of CWM installed?
If you've got the I9020T, try installing this one (from kouch's site)
But if you've got the I9020A, you should try the recovery from this guide (Part 3 - Recovery)
Sorry for the delayed response ,
I have the Tmobile carrier and its I9020T. The version of CWR is 3.0.2.4 which is running. As i said before its not monting the /system.
any other options that I have. ?
Please suggest
Thanks for your time..
I got the nandroid for GRJ22 I9020T.
I'm unable to fastboot flash boot boot.img from this ROM.
it says FAILWrite..
also tried to do the same way for system.img it says Invalid Magic Code !
thankyou suksit I recovered the ROM link that u had posted. I pushed using the adb on to the sdcard and installed from the CWR. I had tried that initially but had not worked.. but now it worked perfectly..
thanks KUDOS..
rakeshpatil1983 said:
thankyou suksit I recovered the ROM link that u had posted. I pushed using the adb on to the sdcard and installed from the CWR. I had tried that initially but had not worked.. but now it worked perfectly..
thanks KUDOS..
Click to expand...
Click to collapse
Glad you made it!
Well.. Its been 2 days it got bricked..
I still dont understand why it did not get it rooted even after i used the right CWR and superuser .. ?
Now i wont try for a while as i'l be on a vacation to India and I will need my phone..
rakeshpatil1983 said:
Well.. Its been 2 days it got bricked..
I still dont understand why it did not get it rooted even after i used the right CWR and superuser .. ?
Now i wont try for a while as i'l be on a vacation to India and I will need my phone..
Click to expand...
Click to collapse
your phone was never bricked. bricked means itll never ever work again. if your planning on using it later and using it now, then bricked is definitely not the right word to use ;-)
well then its appropriate to say
"It was broken for two days"
nexus S was in locked state...can't able to unlock thorugh "fastboot oem unlock" (FAILED <remote:ERASE FAIL>.. even all drivers were installed properly...if i try to get in to recovery mode there is an exclamtion mark...what it that..??? plzzzz help me with this
ok i have open root with htcdev went smooth second used superboot also flashed first time
after flashing namleless v1.1 starting going wrong
problem im having now is the phone loads normaly when i try clockwork recovery it hangs on logo screen same for factory reset
software is as follows
android version 4.0.3
htc sense version 4.0
software number Nameless v1.1
htc sdk api level 4.21
htc extension version _403_1_ga_9
kernal version 3.0.16-g8149866 [email protected]#1
baseband version 10.08.98.09h_1.05.98.11m3
build number 1.45.401.4 cl65553
browser version webkit/534.30
***unlocked***
golfu pvt ship s-on rl
hboot-1.28.0000
radio-1.05.98.11m3
emmc-boot
is there away to get clock work bk working have tryed reflashing it says complete but still will not load recovery or factory reset
is there a compatable ruu i can use or maybe some other flash
regards
I had this problem too with my Droid 3. I had to re-install SafeStrap like 3 times to get the recovery menu to work again. Then I had access to clockworkmod.
theGekkoST said:
I had this problem too with my Droid 3. I had to re-install SafeStrap like 3 times to get the recovery menu to work again. Then I had access to clockworkmod.
Click to expand...
Click to collapse
Is SafeStrap an app if so im even more stuck as the wirless is coming up error on my phone still must be the namless v1.1 still ??
Have you tried reflashing CWM via fastboot? Could just be your recovery got borked and you need to reflash recovery.
You can also try reflashing CWM via ROM Manager.
edit: Your img file might be corrupt, did you compare the MD5 sum? How are you flashing recovery?
orangekid said:
Have you tried reflashing CWM via fastboot? Could just be your recovery got borked and you need to reflash recovery.
You can also try reflashing CWM via ROM Manager.
edit: Your img file might be corrupt, did yo the MD5 sumu compare ? How are you flashing recovery?
Click to expand...
Click to collapse
im useing flasboot cmd fastboot flash recovery clockworkrecovery.img from android folder c
and as for apps when i try to use htc sync to load my apps comes up installation failiure pls chk the file and ensure sufficient space
did yot he MD5 sumu compare i have just downloaded this but have never used it before
after i flash namless v1.1 the broblems start as i used cwm to flash from sd card
sorry for my bad grammer btw
regards
just used md5 and it dosnt match
maybe i can find a ruu to load to start afresh maybe ?? any reply welcome pls
spiderx1972 said:
im useing flasboot cmd fastboot flash recovery clockworkrecovery.img from android folder c
and as for apps when i try to use htc sync to load my apps comes up installation failiure pls chk the file and ensure sufficient space
did yot he MD5 sumu compare i have just downloaded this but have never used it before
after i flash namless v1.1 the broblems start as i used cwm to flash from sd card
sorry for my bad grammer btw
regards
just used md5 and it dosnt match
maybe i can find a ruu to load to start afresh maybe ?? any reply welcome pls
Click to expand...
Click to collapse
No you don't have to do all of that,
Just download the correct CWM recovery.img file, CHECK the MD5, then flash via fastboot, you don't have to start fresh or anything.
edit:
what phone is this for?
I got that it's an HTC device running Sense 4 but we might help you find a better CWM recovery link if we know which device you're using on what carrier.
orangekid said:
No you don't have to do all of that,
Just download the correct CWM recovery.img file, CHECK the MD5, then flash via fastboot, you don't have to start fresh or anything.
edit:
what phone is this for?
I got that it's an HTC device running Sense 4 but we might help you find a better CWM recovery link if we know which device you're using on what carrier.
Click to expand...
Click to collapse
may i say first a big tks for rplying very greatfull tbh
my phone dare i say the name is htc desire c /gulp do i here bad news incoming lol
spiderx1972 said:
may i say first a big tks for rplying very greatfull tbh
my phone dare i say the name is htc desire c /gulp do i here bad news incoming lol
Click to expand...
Click to collapse
No you're fine, that should not be an issue.
Let's just find you a good recovery file you can flash.
edit:
Here, http://forum.xda-developers.com/showthread.php?t=1785010
download that beta2 file and flash from fastboot
orangekid said:
No you're fine, that should not be an issue.
Let's just find you a good recovery file you can flash.
edit:
Here, http://forum.xda-developers.com/showthread.php?t=1785010
download that beta2 file and flash from fastboot
Click to expand...
Click to collapse
WORKS LIKE A DREAM
doing a full bk up now gona try the rom from that page aswell
tks to orangekid rly happy now
btw was gona ask with my back i could upload it it if it would help any 1 else or by request duno the rules on uploading stuff if its ok or not
will update after loading rom
cheers all /respect for the help
spiderx1972 said:
WORKS LIKE A DREAM
doing a full bk up now gona try the rom from that page aswell
tks to orangekid rly happy now
btw was gona ask with my back i could upload it it if it would help any 1 else or by request duno the rules on uploading stuff if its ok or not
will update after loading rom
cheers all /respect for the help
Click to expand...
Click to collapse
Awesome!
Glad we got you back up and running, it can be a real pain when the issue is a bad img file and you can't seem to figure out what is going on, but people need to remember to check MD5 sums for recoveries, radios and bootloaders lest they brick.
I don't think you need to upload since that link seems to work, they can just find the CWM for that phone from the link I provided and flash via fastboot from there.
Cheers bro, let us know how it's going after you flash the ROM
orangekid said:
Awesome!
Glad we got you back up and running, it can be a real pain when the issue is a bad img file and you can't seem to figure out what is going on, but people need to remember to check MD5 sums for recoveries, radios and bootloaders lest they brick.
I don't think you need to upload since that link seems to work, they can just find the CWM for that phone from the link I provided and flash via fastboot from there.
Cheers bro, let us know how it's going after you flash the ROM
Click to expand...
Click to collapse
flashed Slim Sense 1.0 for HTC Desire C works fine got my wireless working aswell lol
But i have another question maybe me but when i used other roms in the past i couldnt use htc sync strange i no but i tested the roms to see if it was them causing the problem even formated pc but still no joy stuck at loading Apps from my pc ??
connection from phone is there when i pick drive my sd card pops up on pc when i sync phone is saying unable to open htc sync manager on your computermake sure the application is installed and open witch it is ??
Are all of the drivers installed?
Also try a different USB port.
Sent from my Galaxy Nexus using xda app-developers app
orangekid said:
Are all of the drivers installed?
Also try a different USB port.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
still trying been hours now running at like a bull but no joy yes ive used the same drivers as when it worked before think ive tryed every version of htc sync must be some think saft knowing me
spiderx1972 said:
Is SafeStrap an app if so im even more stuck as the wirless is coming up error on my phone still must be the namless v1.1 still ??
Click to expand...
Click to collapse
Yea it is, but I think it's more for Motorola devices. I don't know what HTC uses if anything different. But my phone would boot to the OS so I could still install apps via the SD card. Once I got that properly reinstalled I could access the boot menu again.
Seems like you got that issue solved by I still wanted to follow up.
Hi, I'm having and issue with my Galaxy Tab 7.7 (P6810) and don't know what is the problem, so I'm looking for assistance here. (Thanks in advance).
Let me describe my issue(s):
1. A friend went to flash the Tab and apparently used the wrong firmware, in Odin mode shows GT-P7560.
2. I already tried flashing different firmwares but when I use ICS the Tab goes into a bootloop. I can go to download (odin) mode, but can't go to recovery mode (volume up + power).
3. I flashed it with a stock firmware (P6810DTKL5_P6810XSAKL2_XSA) and got it to boot, but is asking for a password it never had.
So I'm thinking there's an issue with the partition or bootloader. Already tried a "p6810-16g.pit" file with no luck
Tried flashing different CWM versions and nothing works. So at this point I'm stuck on this issue.
What can I do to bring back my device to a functional state? Any advice would be appreciated! THANKS A LOT!! :good::laugh:
I'm attaching the images describing the issues.
edwing29 said:
Hi, I'm having and issue with my Galaxy Tab 7.7 (P6810) and don't know what is the problem, so I'm looking for assistance here. (Thanks in advance).
Let me describe my issue(s):
1. A friend went to flash the Tab and apparently used the wrong firmware, in Odin mode shows GT-P7560.
2. I already tried flashing different firmwares but when I use ICS the Tab goes into a bootloop. I can go to download (odin) mode, but can't go to recovery mode (volume up + power).
3. I flashed it with a stock firmware (P6810DTKL5_P6810XSAKL2_XSA) and got it to boot, but is asking for a password it never had.
So I'm thinking there's an issue with the partition or bootloader. Already tried a "p6810-16g.pit" file with no luck
Tried flashing different CWM versions and nothing works. So at this point I'm stuck on this issue.
What can I do to bring back my device to a functional state? Any advice would be appreciated! THANKS A LOT!! :good::laugh:
I'm attaching the images describing the issues.
Click to expand...
Click to collapse
You don't need a bootloader, it was already "flashed" when he flashed the stock official firmware - bootloader would have been included in that and PIT
If done correctly, the PIT should work, if not - unfortunately, most likely back for repair............ bummer
Without actually checking the above is HC, have you tried the official HoneyComb firmware ? Just don't factory reset in HC recovery
P6810 ICS LPP Bootloader
Here you go............
I have packaged my P6810 ICS LPP bootloader files into an ODIN flashable .tar.mD5 format.
Flashing Instructions :
Extract the Sbl.bin.zip and boot.bin.zips so that you have Sbl.bin.tar.md5 & boot.bin.tar.md5
Ensure you have the latest Samsung USB drivers installed
Disable KIES
Disable KIES process in Task Manager
Run ODIN
Ensure ONLY "auto reboot" and "reset time" are checked
Device in Download mode
Connect device to PC USB port
ODIN - Flash Sbl.bin.tar.md5 in either "bootloader" -or- "PDA" option (choose one only)
Then repeat above same method to flash boot.bin.tar.md5
** After that, try reflash the COMPLETE official stock ICS LPP package with ODIN
Best of luck
UITA
.
UpInTheAir said:
Here you go............
I have packaged my P6810 ICS LPP bootloader files into an ODIN flashable .tar.mD5 format.
Flashing Instructions :
Extract the Sbl.bin.zip and boot.bin.zips so that you have Sbl.bin.tar.md5 & boot.bin.tar.md5
Ensure you have the latest Samsung USB drivers installed
Disable KIES
Disable KIES process in Task Manager
Run ODIN
Ensure "auto reboot" and "reset time" are checked
Device in Download mode
Connect device to PC USB port
ODIN - Flash Sbl.bin.tar.md5 in either "bootloader" -or- "PDA" option (choose one only)
Then repeat above same method to flash boot.bin.tar.md5
** After that, try reflash the COMPLETE official stock ICS LPP package with ODIN
Best of luck
UITA
.
Click to expand...
Click to collapse
Hi, thanks for your assistance... here's what I just did:
1. I downloaded the bin files you attached and both are appearing as invalid md5 in ODIN, apparently the hash is invalid.
2. I renamed them from .tar.md5 to just .tar and flashed my device with both files as you described.
3. Rebooted twice, went to Download mode again.
4. Flashed with P6810XXLPP_P6810XSALJ2 (stock firmware).
5. Got bootloop again.
6. Re-flashed the "Sbl.bin" & "boot.bin" again, and still got bootloop.
7. Download mode still shows "P7560" as the installed firmware.
Any other advice?
Thanks again! :good:
edwing29 said:
Hi, thanks for your assistance...
I downloaded the bin files you attached and both are appearing as invalid md5 in ODIN, apparently the has is invalid.
Can you check them and re-upload if there's no problem?
Thanks again! :good:
Click to expand...
Click to collapse
I'll have a play around on my device first, and see if I can get them to work. Those were untested.
Sent from my GT-I9500 using xda premium
UpInTheAir said:
I'll have a play around on my device first, and see if I can get them to work. Those were untested.
Sent from my GT-I9500 using xda premium
Click to expand...
Click to collapse
Hi, I just edited the previous reply.
Check it out, Thanks.
edwing29 said:
Hi, thanks for your assistance... here's what I just did:
1. I downloaded the bin files you attached and both are appearing as invalid md5 in ODIN, apparently the hash is invalid.
2. I renamed them from .tar.md5 to just .tar and flashed my device with both files as you described.
3. Rebooted twice, went to Download mode again.
4. Flashed with P6810XXLPP_P6810XSALJ2 (stock firmware).
5. Got bootloop again.
6. Re-flashed the "Sbl.bin" & "boot.bin" again, and still got bootloop.
7. Download mode still shows "P7560" as the installed firmware.
Any other advice?
Thanks again! :good:
Click to expand...
Click to collapse
Very strange, particularly if the flash was successful.....................
Try flashing both the files at once. boot.bin in "bootloader" and SBl.bin in "PDA".
Maybe something else we haven't thought of..
If I think of anything else, will let you know, but try the stock HC firmware too, just in case.
UpInTheAir said:
Very strange, particularly if the flash was successful.....................
Try flashing both the files at once. boot.bin in "bootloader" and SBl.bin in "PDA".
Maybe something else we haven't thought of..
If I think of anything else, will let you know, but try the stock HC firmware too, just in case.
Click to expand...
Click to collapse
Tried the steps above and still the same.
I had to flash back to the stock HC firmware because the ICS led into an infinite loop, at least HC let me turn off the device.
I'll wait for any other suggestions, thanks!
Sent from my GT-I9100 using xda app-developers app
All I can suggest is to send it away for repair.
JTag (riff box) by a 3rd party or Samsung.
If it's NOT a hardware issue, JTag should be much cheaper, and if successful, faster.
http://www.jtagbox.com/riff-jtag-bo...s-unbrick-bricked-phone-riff-box-owners-list/
Sent from my GT-I9500 using xda premium
So we were trying to update my friend's Tab 2 to a 4.4.2 ROM. We got CWM 6.0.2.3 installed, and tried a ROM. Well this failed, and appeared to break other stuff as it now boot loops to CWM. Actually I think it's going every other book to CWM. Right now it's saying battery depleated. I've got it plugged intoa charger, hopefully it'll take a charge.
I did later realize we weren't using a new enough version of CWM, but regardless, any ideas how to recover from this? It does not appear to be able to go into download mode. It only goes to CWM. I've tried flashing other ROMs but that doesn't seem to be working either.
So...kinda stuck for the moment.
Thanks!
colema19 said:
So we were trying to update my friend's Tab 2 to a 4.4.2 ROM. We got CWM 6.0.2.3 installed (...)
Click to expand...
Click to collapse
We have a winner... the next one who didn't pay any attention - i.e. reading the OP post of the ROM thread.
ClockworkMod Recovery 6.0.x.y is ONLY for flashing CyanogenMod up to 10.1.3.
For flashing OMNI ROM or CyanogenMod 11 (both Android 4.4.2 at the time of writing) you _NEED_ to use TWRP (recommended for OMNI) or PhilzTouch Advanced Recovery or ClockworkMod Swipe Edition (recommended for CM11). See AndroidAndi's file repository to obtain a copy of the correct recovery for your particular model of the Tab 2.
Next thing to do: Download and install ODIN, install the "Samsung USB Drivers" (Google's your buddy), download the .tar.md5 of the recovery you want to flash (see above and make a choice), put the tablet into download mode, flash the recovery.
If that worked flash the custom ROM of choice (+gapps if CM11, +SuperSU if OMNI) through the custom recovery you just installed and be glad you didn't turn the tablet of your friend into a paperweight.
BoneWithABeagle said:
We have a winner... the next one who didn't pay any attention - i.e. reading the OP post of the ROM thread.
.
Click to expand...
Click to collapse
Speaking of not reading OPs and paying attention...I already said I realized that was the issue, and that I can't seem to get it to go into download mode, so that's likely paperweight land?
colema19 said:
Speaking of not reading OPs and paying attention...I already said I realized that was the issue, and that I can't seem to get it to go into download mode, so that's likely paperweight land?
Click to expand...
Click to collapse
If you're down to "can't get it into download mode anymore" (I start to assume the attempt to flash some 4.4.2 ROM through CWM 6.0.x.x may overwrite partitions it's not supposed to overwrite) the only way left to breathe life back into the tablet is to resort to JTAG (UART port connection, CASUAL restoration package, USB Jig to force the tablet into UART mode).
If you search on XDA you will discover tons of threads by AdamOutler dealing with that topic, maybe that's useful to you in any way to figure out if that's an option for you.
Does it stay in CWM once it boots? If so you can copy a TWRP 2.7.0.x zip file to your SD card and install it from there.
Sent from my Nexus 4 using XDA Premium HD app
shakatu said:
Does it stay in CWM once it boots? If so you can copy a TWRP 2.7.0.x zip file to your SD card and install it from there.
Sent from my Nexus 4 using XDA Premium HD app
Click to expand...
Click to collapse
I'll keewp looking, but if you have a location I can get a flashable zip that will work for this, that'd be very helpful!
Thanks
Found a flash, flashed TWRP and got CM11 on it and working.
Thanks!
Whenever I attempt to flash a Cyanogenmod Rom for P3110 (Using that because I have a P3113) I get a Status 7 Error.
Anyone know how to fix this?
I use this to get the Rom: http://forum.xda-developers.com/showthread.php?t=2583316
Picture: http://prntscr.com/43qdlq
Zackpip said:
Whenever I attempt to flash a Cyanogenmod Rom for P3110 (Using that because I have a P3113) I get a Status 7 Error.
Anyone know how to fix this?
I use this to get the Rom: http://forum.xda-developers.com/showthread.php?t=2583316
Picture: http://prntscr.com/43qdlq
Click to expand...
Click to collapse
Flash the latest @Android-Andi Philz Touch or TWRP recovery and that should solve the problem (I recommend flashing the recovery with Odin or Heimdall.) Status 7 error usually means outdated recovery.
Link to @Android-Andi's recovery thread: http://forum.xda-developers.com/showthread.php?t=2548257
Sent from my SGH-T989
Well, that may have worked but before I did anything I let it charge, this is the message I got though: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
How should I go about this? I cannot do anything in Kies because the P3113 won't turn on. Whenever I plug it in to the PC if makes the sound of connecting, then disconnecting over and over again.
Zackpip said:
Well, that may have worked but before I did anything I let it charge, this is the message I got though: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
How should I go about this? I cannot do anything in Kies because the P3113 won't turn on. Whenever I plug it in to the PC if makes the sound of connecting, then disconnecting over and over again.
Click to expand...
Click to collapse
What exactly did you do that it did this? Did you attempt to flash the recovery in Odin or Heimdall? If Odin, which version?
Sent from my SGH-T989
Since the Cyanogenmod Rom failed flashing I tried to flash the stock firmware using Odin v.1.83 (Odin v3.09 and v3.07 wouldn't open) in order to get a Rom, then I tried to re-root it using v1.83, but it died when I was trying to. So, I decided to charge it and that's what happened. At least that's what I remember. My USB connector works but doesn't charge when connected to the PC, that's why it died. Other than that I do not believe anything else was done to it.
Zackpip said:
Since the Cyanogenmod Rom failed flashing I tried to flash the stock firmware using Odin v.1.83 (Odin v3.09 and v3.07 wouldn't open) in order to get a Rom, then I tried to re-root it using v1.83, but it died when I was trying to. So, I decided to charge it and that's what happened. At least that's what I remember. My USB connector works but doesn't charge when connected to the PC, that's why it died. Other than that I do not believe anything else was done to it.
Click to expand...
Click to collapse
OK, that makes more sense. If your device died during installation that will happen. If I use Odin, I usually use v1.85, but I have found Heimdall to be more stable and consistent. Can you boot into download mode?
Edit: also, what version of windows are you running?
Sent from my SGH-T989
jrc2 said:
OK, that makes more sense. If your device died during installation that will happen. If I use Odin, I usually use v1.85, but I have found Heimdall to be more stable and consistent. Can you boot into download mode?
Edit: also, what version of windows are you running?
Sent from my SGH-T989
Click to expand...
Click to collapse
I am using Windows 8.1. Sorry for the late reply, had a little Family Reunion.
Zackpip said:
I am using Windows 8.1. Sorry for the late reply, had a little Family Reunion.
Click to expand...
Click to collapse
There have been known problem using Odin on Windows 8, but I've done it multiple times. (I had kies installed if it makes any difference)
Anyway, do you have a Linux computer laying around somewhere? Depending on what happened during I installation, one can be used to maybe trip the device into a bootloop and then from there you can boot into recovery and flash a ROM. (I had to do this with my S2 after a power glitch while using Odin.) Odin isn't needed to root the tab. All you have to do us use Odin or Heimdall to flash a custom recovery (CWM or TWRP) and then flash SuperSU.zip in recovery.
Sent from my SGH-T989
jrc2 said:
There have been known problem using Odin on Windows 8, but I've done it multiple times. (I had kies installed if it makes any difference)
Anyway, do you have a Linux computer laying around somewhere? Depending on what happened during I installation, one can be used to maybe trip the device into a bootloop and then from there you can boot into recovery and flash a ROM. (I had to do this with my S2 after a power glitch while using Odin.) Odin isn't needed to root the tab. All you have to do us use Odin or Heimdall to flash a custom recovery (CWM or TWRP) and then flash SuperSU.zip in recovery.
Sent from my SGH-T989
Click to expand...
Click to collapse
I do not have a Linux machine anywhere.. Would that be the only way to fix it?
Zackpip said:
I do not have a Linux machine anywhere.. Would that be the only way to fix it?
Click to expand...
Click to collapse
Not necessarily but it was just what I used and what worked. Does Odin detect the device on the firmware upgrade encountered an error screen?
Sent from my SGH-T989
jrc2 said:
Not necessarily but it was just what I used and what worked. Does Odin detect the device on the firmware upgrade encountered an error screen?
Sent from my SGH-T989
Click to expand...
Click to collapse
What do you mean by that? Odin shows this when I plug it in: http://prntscr.com/44yzf2
Nothing looks out of the ordinary.
Zackpip said:
What do you mean by that? Odin shows this when I plug it in: http://prntscr.com/44yzf2
Nothing looks out of the ordinary.
Click to expand...
Click to collapse
Odin does detect the device. So you SHOULD be able to go to www.samfirmware.com , click on "Firmware Database" and select the options in the drop down boxes for your tablet. Download the zip file (you'll need a sammobile account) and then extract the zip file. You should have a tar.md5 or a tar file that you can flash in Odin. Make sure your tab is charged and you run Odin as admin. After you flash that, reboot into recovery (will be stock recovery) and do a factory reset and wipe cache. Now you should be able to reboot into stock android (with TouchWIZ of course). To root from here, use Odin to flash latest @Android-Andi TWRP recovery and the flash @Chainfire's SuperSU.zip and you'll be rooted!
As always, I am not responsible for what happens to your device. Doing this will raise your flash counter and void your warranty, which is probably void already if you flashed anything before.
Sent from my SGH-T989
jrc2 said:
Odin does detect the device. So you SHOULD be able to go to www.samfirmware.com , click on "Firmware Database" and select the options in the drop down boxes for your tablet. Download the zip file (you'll need a sammobile account) and then extract the zip file. You should have a tar.md5 or a tar file that you can flash in Odin. Make sure your tab is charged and you run Odin as admin. After you flash that, reboot into recovery (will be stock recovery) and do a factory reset and wipe cache. Now you should be able to reboot into stock android (with TouchWIZ of course). To root from here, use Odin to flash latest @Android-Andi TWRP recovery and the flash @Chainfire's SuperSU.zip and you'll be rooted!
As always, I am not responsible for what happens to your device. Doing this will raise your flash counter and void your warranty, which is probably void already if you flashed anything before.
Sent from my SGH-T989
Click to expand...
Click to collapse
Well, that partially worked. It does not show that anymore and it shows the Charging animation, but I can not boot into Odin/Download mode, or Recovery mode.
Zackpip said:
Well, that partially worked. It does not show that anymore and it shows the Charging animation, but I can not boot into Odin/Download mode, or Recovery mode.
Click to expand...
Click to collapse
That is quite weird. I have done the same thing at least 2 or 3 times. Try going to https://builds.casual-dev.com/jodin3/ Make sure you plug in your device before loading the above page. Your device should be detected when the page loads. In PDA put the latest TWRP tar file. Click start. It will say something like it needs a pit file and will reboot to find it. Click OK. It might fail but thats fine. Unplug your device. It will reboot and should show a bootloop. Now you should be able to reboot into recovery. If not, you might have to JTag but I don't know. For future reference, if a ROM is bootlooping, don't flash stock in Odin. Just do a full wipe and reflash the ROM and that should fix it.
Sent from my SGH-T989
EDIT: if the tab died during installation of an important file, it can ruin the device. www.mobiletechvideos.com does have JTAG service that can be used as a last resort. It costs around 50 US Dollars.
jrc2 said:
That is quite weird. I have done the same thing at least 2 or 3 times. Try going to https://builds.casual-dev.com/jodin3/ Make sure you plug in your device before loading the above page. Your device should be detected when the page loads. In PDA put the latest TWRP tar file. Click start. It will say something like it needs a pit file and will reboot to find it. Click OK. It might fail but thats fine. Unplug your device. It will reboot and should show a bootloop. Now you should be able to reboot into recovery. If not, you might have to JTag but I don't know. For future reference, if a ROM is bootlooping, don't flash stock in Odin. Just do a full wipe and reflash the ROM and that should fix it.
Sent from my SGH-T989
EDIT: if the tab died during installation of an important file, it can ruin the device. www.mobiletechvideos.com does have JTAG service that can be used as a last resort. It costs around 50 US Dollars.
Click to expand...
Click to collapse
I used Odin to re-download the stock firmware, and that worked. Thank you so much for all your help, it is working now!
Zackpip said:
I used Odin to re-download the stock firmware, and that worked. Thank you so much for all your help, it is working now!
Click to expand...
Click to collapse
So you mean you redownloaded the firmware from sammobile and flashed with Odin or what? I couldn't figure out exactly what you meant. Glad to hear your tab is working again!
Sent from my SGH-T989
jrc2 said:
So you mean you redownloaded the firmware from sammobile and flashed with Odin or what? I couldn't figure out exactly what you meant. Glad to hear your tab is working again!
Sent from my SGH-T989
Click to expand...
Click to collapse
Yes, I did exactly that.
Zackpip said:
Yes, I did exactly that.
Click to expand...
Click to collapse
So it must have been a bad download then. You used Odin v1.87 or what? Also, you should add [SOLVED] to the thread title.
Sent from my SGH-T989