Related
I have tried to locate this question, but I can not find it on here, so here goes.
I have a rooted GT6210 WiFi only.
Kies shows:
Current firmware version: PDA:KL1 / CSC:KL1 (XAR)
Latest firmware version: PDA:LA3 / CSC:LA3 (XAR)
Is this OK to update, or leave it be?
Thanks.
Looked this up on google and found your thread. Wondering the same thing. Ill update this if I figure it out.
On my tab with KL2 it's only a small 8mb update to fix 'stability issues'
I haven't updated yet as it won't let me flash due to low battery
This being pushed out via OTA?
Sent from my GT-P6210 using xda premium
If all you've done is root, it should work but you might lose root. If you have a modified firmware or CWM recovery installed, it probably won't work and you'll have to use Odin to get back to stock.
You will lose root. Flashed via Kies yesterday. Re-rooted and re-installed CWM.
No worries.
Please make a CWM backup and upload the system backup. Just the system file... not data (data has personal info)
Thanks
Gary
Sent from my GT-N7000 using Tapatalk
garyd9 said:
Please make a CWM backup and upload the system backup. Just the system file... not data (data has personal info)
Thanks
Gary
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
Always good advice, Gary!
skeeterpro said:
Always good advice, Gary!
Click to expand...
Click to collapse
actually, I wanted the system archive so I could pull it apart and see if the wifi drivers are changed.
Sent from my GT-N7000 using Tapatalk
garyd9 said:
actually, I wanted the system archive so I could pull it apart and see if the wifi drivers are changed.
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
Wonder if it's to fix the SOD problem??
slonline said:
Current firmware version: PDA:KL1 / CSC:KL1 (XAR)
Latest firmware version: PDA:LA3 / CSC:LA3 (XAR)
Click to expand...
Click to collapse
FYI: The "LA" in "LA3" designates that this is from January 2012. (based on information taken from samfirmware.com.) I'm not sure what the "3" is... probably some build number - but may be a week number (I really don't know.)
You can't use garys kernal with this update can you...
Zadeis said:
You can't use garys kernal with this update can you...
Click to expand...
Click to collapse
Have you tried it? I don't have the update, so I have no idea. I'm trying to get someone who has already installed it to do a CWM Recovery backup and upload some of the files from it (so I can check compatibility.)
The firmware /system tree contains kernel modules, so if they rebuilt the kernel for that build, then there's a chance that wifi wouldn't load with my kernel.
CWM Recovery backups have some files that would help me:
"boot.img" is the kernel image
system.ext4.tar is the /system tree. This file contains NO user information, but contains what people here on XDA like to call the "ROM." It's the entire android system outside of recovery and the kernel.
Take care
Gary
Well if it worked I would try but alas I'm still waiting for samsung to give me my tablet back from having those issues I was having a couple weeks ago with having a bunch of errors in recovery and not being able to boot. I'm just asking since when I get it back I hope to be able to use your wonderful kernal again
Here's the boot image and link for dropbox for the system file.
http://dl.dropbox.com/u/60666140/system.zip
About an hour left on the upload...slow DSL
Thanks,
Jason
nevermind, folks.. I went ahead and installed the update on my own 6210. Give me a week or two to get things sorted out.
Oh.. and the update installs via the bootloader, so it will work fine regardless of any recovery, rooting, etc.
However, it'll overwrite root, recovery, etc.
Take care
Gary
---------- Post added at 01:08 AM ---------- Previous post was at 12:48 AM ----------
So far, I see nothing different. Even the ar6000.ko module has the old kernel's version string embedded (although there is a binary difference between the old and new module, they appear to have compiled it again the older kernel and haven't updated any version strings.)
---------- Post added at 01:32 AM ---------- Previous post was at 01:08 AM ----------
UNTIL I POST THAT IT WILL WORK WITH THE LA3 FIRMWARE UPDATE, DO NOT INSTALL MY KERNEL IF YOU'VE UPDATED YOUR FIRMWARE.
The tablet will boot just fine, but the wifi module won't load (meaning you won't have any wireless.)
I'll be updating the kernel thread with a proper warning...
Take care
Gary
slonline said:
I have tried to locate this question, but I can not find it on here, so here goes.
I have a rooted GT6210 WiFi only.
Kies shows:
Current firmware version: PDA:KL1 / CSC:KL1 (XAR)
Latest firmware version: PDA:LA3 / CSC:LA3 (XAR)
Is this OK to update, or leave it be?
Thanks.
Click to expand...
Click to collapse
I do not understand you. Why should it not be ok to install the new firmware that kies offers you?
Just Updated via KIES...
and lost root, etc but rerooted and installed CWM per Garyd9's " [GT-P6210][CWMRecovery][ROOT] ClockworkMod Recovery and Root (07-Jan-2012)" - no issues.
Following are just qualitative observations:
I use TouchWiz as my launcher and it's definitely smoother and seems faster, particularly when scrolling between screens.
The whole tablet seems to execute operations faster - particularly when opening/closing app drawer.
I see that my display timeout settings appear to be retained though it may be too early to tell. One of my pet peeves is that Android (or maybe Samsung) likes to reset the timeout to one minute irrespective of a user selected setting - this seems to happen after the Tab sleeps. Maybe this is one of the software fixes??? but I will report after a while.
Garyd9: if there is a dump that you can use I can do it - just tell me what youi want.
I have same setup, lost root but just re-rooted and works fine.
Is kies supposed to find the update automatically? When I connect via Kies nothing happens and when I manually check for an update it says than no updates are available.
Nevermind, kies just found it and is auto-installing....
Currently designed for the Wifi version only. Alternates available upon request.
This package includes the de-odexed system and framework folder based on a wifi model.
This is NOT a full install, so do NOT wipe before using.
This package is designed to be used with the custom recovery image. This will NOT work with Odin.
This will delete the current system and framework folders and flash the new ones in their place. This is only a temporary solution until a full rooted install is established.
De-Odexed Install Pack
Custom Recovery Image
Custom Kernel Packages
twistedumbrella said:
Currently designed for the Wifi version only. Alternates available upon request.[/url]
Click to expand...
Click to collapse
Request!
My Verizon GC120 should be here in a couple of days. As far as I know it is untouched stock. Let me know the commands to pull the files you need for this and the other dev work you are doing.
Thank you for taking the time to do the work! We all appreciate it!
Finally received a GC120 camera I can do something with. Attached are the .img files pulled. About says my phone is on 4.1.2 (LK3) but I keep getting an install update request although the folder titled as the update in /cache is empty (so there's nothing I can pull from that).
I also pulled the modem.bin but it says invalid file when I try to upload.
*These are the files for LK3
Camera updated to LL2. Updated files attached.
MC4 files attached
So maybe I screwed myself updating all the way to MK4 update. Can't root using framaroot now like I did with all the others. Gonna try a few other options.
Can someone please tell me the adb command to find whether a bootloader is locked or not? I have tried several I've found online and don't receive anything conclusive. Thanks.
Be back in a week or so. Final project is in the beta test stage so I am swamped until it reaches the release candidate.
twistedumbrella said:
Be back in a week or so. Final project is in the beta test stage so I am swamped until it reaches the release candidate.
Click to expand...
Click to collapse
can you upload samsung galaxy camera apk
Can anyone post efs.img? I've screwed up my Cam and i need to flash efs.img to mmcblk03. Was playing around with swap and screwed up!
BUMP!!!!
rudie_techie said:
BUMP!!!!
Click to expand...
Click to collapse
? It wasn't part of the system image and you didn't specify which model but even so, I doubt people are randomly checking this thread for who needs backups of radio partitions.
Its a EK-GC100 bootloader mode says EK-GC100_EUR_XX
rudie_techie said:
Its a EK-GC100 bootloader mode says EK-GC100_EUR_XX
Click to expand...
Click to collapse
I dug through everything I have but no efs.img and if I remember right, you'd need one with your IMEI. Best bet is probably a factory reset.
Didn't help... tried factory reset with stock recovery and cwm recovery... nothing helps... i don't know a way to get it fixed... will keep looking...
Finally got it fixed. As GC100 is similar to S3, downloaded efs file for S3 flashed it via odin through bootloader and voila... attaching the file for reference if anyone else gets into trouble!
rudie_techie said:
Finally got it fixed. As GC100 is similar to S3, downloaded efs file for S3 flashed it via odin through bootloader and voila... attaching the file for reference if anyone else gets into trouble!
Click to expand...
Click to collapse
It's usually easier to post it all in one thread and link to it instead of making the same posts in two threads and ending up with the same answers.
can someone please re upload or send me links in private message? I have dropbox, please I need it... my ****z bricked gotta fix it
damn can someone upload these links or the stock odin tar???
GC120_GC120VRAMH2_1366980_REV00_user_low_ship.tar.md5
?? ANYONE please.... help
[Q] WiFi/BT broken, stuck at "Starting Services" in ALL ROMs and Stock? Help please!
Hello! After a misadventure I managed to get CM 10.2 to run on my Photon Q, and it was fantastic! Wifi and BT work great. However, accidentally flashing the wrong kernel, I got stuck at the bootloader unlocked screen forever.
So, I reinstalled CM 10.2 and all seemed to be well. (I did this from CWM using a ZIP.) However, I quickly discovered WiFi and BT are both broken! If I hit ON, it goes gray for a second and tries to enable, and goes back to OFF with no error or other response. If I open the WiFi or BT menu and hit ON or SCAN, same result or it just does nothing.
So, I tried to downgrade to something older, something with ICS and not JB, which is what I prefer anyway. TwistedAsanti gets stuck forever at "Starting Services..." and the home screen never comes up, even if left overnight. I get a message that no cell networks were found asking if I want to switch to GSM. It's covered by STARTING SERVICES ... so I can't hit "No", but either way I don't have a carrier, so that's no issue. I use WiFi only. I can pull down the notification bar and go into settings. While there, I see the same problem with WiFi and BT, both are broken. I can't run any apps or get to the homescreen, still.
So, I tried to install 10.1, same result. Then MIUI, Carbon and SlimBean. Same result! I installed TWRP and flashed a backup of Stock JB from WIN files I found here on the forum. It boots up, but this time it's stuck at "Starting Services..." just like TwistedAsanti was. Notification bar works, settings menu works, homescreen won't appear, Starting services never goes away, can't run any apps. Wifi and BT still broken in the same manner.
Now downloading a backup of ICS Stock to see if that works any better, but I'm not holding my breath.
Has anyone ever experienced this? Thanks for any advice. I attached some photos that might help. I had to use my Tracfone because now that is the best camera I have access to, so sorry for the blurriness. I hope it gives you the general idea of what is going on.
EDIT: For each flash, I am wiping data, cache and dalvik cache. I also wiped modem and pds by mistake, could that be the problem? If so, how would I restore those? Thanks
Again, thanks for your time!
Jeez, how many threads do you need to post in? I have responded to all your posts in all of the various threads, INCLUDING your PM's.
Let's focus here, if you want custom we can do that. If you want stock we can do that. Please focus, what do you want.
If you want custom, perhaps you're not wiping everything properly... So boot recovery. Wipe system. Factory reset - wipe data, cache, dalvik-cache, sd-ext. Best to do the actual "factory reset" option than wiping all of those by hand, because wiping /data will wipe /data/media (internal SD) while factory reset will preserve /data/media.
Next, flash ROM of your choice. Twisted Asanti is kinda outdated, hasn't had any attention in a loooong time. Let's try something stable, CM10.1. Flash it. Flash gapps. Boot, do you still have the same issues?
Probably the wrong kernel is still flashed, you need to flash the stock kernel.
Wiping modem and pds could be the problem.
The first I would do in your position is to flash with RSD the stock ROM. This Thread -> http://forum.xda-developers.com/showthread.php?t=2095536
edit: If you post in several threads and try different things "in" different threads we won't be able to help you.
EVERYTHING in one thread and we may see what you have done and where you have had problems.
You should keep it simple and give all information in one good structured post so we don't have to read pages to see what you did.
Loader009 said:
Probably the wrong kernel is still flashed, you need to flash the stock kernel.
Wiping modem and pds could be the problem.
The first I would do in your position is to flash with RSD the stock ROM. This Thread -> http://forum.xda-developers.com/showthread.php?t=2095536
edit: If you post in several threads and try different things "in" different threads we won't be able to help you.
EVERYTHING in one thread and we may see what you have done and where you have had problems.
You should keep it simple and give all information in one good structured post so we don't have to read pages to see what you did.
Click to expand...
Click to collapse
Sorry about that. I'll keep it in one place. Thanks Still trying to get RSD to work, but it won't detect the phone for some reason. Well, on one PC it will, but then it fails to flash saying there was a Remote error (FAIL). On another PC, it won't detect. In BOTH cases, fastboot devices successfully shows the phone. I can even format partitions and flash files. I have successfully flashed TWRP this way.
trying to flash the system image doesn't work with the error "invalid sparse file format at header magi", then fastboot crashes. (What?) So, RSD doesn't work and fastboot kinda works, but not for all the images.
I got a copy of all the kernels I could find .. arrrghhh's for every FW I can think of. Searching out a stock kernel now. It says on the Peas and Q's post that it's just a stock FW with a new name, so I grabbed that too, might be worth a shot...
got CM 10.1, I guess I'll try installing that, and then what do I want, the STOCK kernel? or just use the one that it came with? (How confusing.)
To be more clear, either Stock or Custom is fine. I'm happy with either so long as it boots properly and WiFi works again. Root would be nice but I can worry about that later.
You don't have to quote whole posts (just press "QUICK REPLY").
The most important thing is to get RSD to work.
I'm not the guy where you get information about RSD and kind of. I know where to look for and show the right direction.
In the thread I posted you might get help for RSD and you could get help there.
Ask there for help as the more experienced users are reading only the "important" threads and not the "smaller" ones.
(I know this, I do this most time, but I'm not the "know-everything" guy )
As I never needed those FXZ method, I never used it and my RSD Lite experience is rather small.
You might need to install motorola drivers to get it to work but I'm not sure, you should ask in that thread.
PS: If Stock will work again, Custom will work too.
To avoid problems it might be needed to wipe data/cache/dalvik before and after flashing a ROM.
Loader009 said:
You don't have to quote whole posts (just press "QUICK REPLY").
The most important thing is to get RSD to work.
Click to expand...
Click to collapse
I got RSD to see the phone using a different PC. When I try to flash "asanti_c-user-4.0.4-7.7.1Q-6_SPR-89_ASA-36-42-release-keys-Sprint-US.xml" it gets all the way up to flashing "system", which is one of the last steps, then it says the device reported FAIL. This is the same file I couldn't get to flash with fastboot when I was trying to do it manually. But in that case, fastboot crashed entirely.
Not sure what to try now ...
Did you read the following?
Skrilax_CZ said:
NOTES
- use at least RSD Lite 6.1.5 (maybe 6.1.x will work too) or you get an error on flashing system.img.ext4
- you may have to open the zip and edit the xml, and delete the 2 lines "<step operation="getvar" var="max-download-size" />" if you get unknown command fastboot getvar max-download-size
- do not flash Sprint firmware to phone from Cellular US and vice versa unless you know what are you doing!!!
Click to expand...
Click to collapse
As I said, I never tried the FXZ method and I have no experience on error which could appear.
Ask in that FXZ thread and you may get it work soon.
Epicenter714 said:
I got RSD to see the phone using a different PC. When I try to flash "asanti_c-user-4.0.4-7.7.1Q-6_SPR-89_ASA-36-42-release-keys-Sprint-US.xml" it gets all the way up to flashing "system", which is one of the last steps, then it says the device reported FAIL. This is the same file I couldn't get to flash with fastboot when I was trying to do it manually. But in that case, fastboot crashed entirely.
Not sure what to try now ...
Click to expand...
Click to collapse
Try a different port? Different cable? Different computer? Are you using the stock cable?
Perhaps something else is broken... I'm not sure at this point. Do you have any screenshots of the failure? Any specific output from the software?
Did you edit the XML file properly? I think you did, but you said you were downgrading too - are you always trying ICS or have you tried the FXZ file for JB as well?
Useless thread bump.
Another fellow had the same issue, and was using an old version of RSD Lite. What version are you using?
I faced same problem.
Just use latest veersion of RSD lite, 6.0 is ok
and do not forget to remove two getvar commands from xml file.
I tried same and now my phone is alive. But now.IMEI/MEID is gone (zero)
WIFI and bluetooth is now connecting but not receiving any data (useless).
I tried many cdma tool to recover MEID but failed.
I thing we lost EFS partition.
Please look at my thread
http://forum.xda-developers.com/showthread.php?t=2429609
i also need help on that
If any one have EFS backup or something?
lovepreet39 said:
I faced same problem.
Just use latest veersion of RSD lite, 6.0 is ok
and do not forget to remove two getvar commands from xml file.
i also need help on that
If any one have EFS backup or something?
Click to expand...
Click to collapse
The problem WAS RSD's version! Thanks to everyone for your help. I had 5.6.4 running before and it would always die at System.img.ext4 and one other partition later on. That's on the WinXP system that would see the phone in RSD. The Win8 machine wouldn't see it at all, even in XP compatibility mode with admin rights. Go figure. I'll take this as another excuse to not be fond of Win8.
I checked and my phone has boot, system, recovery, data, pds and modem, but no EFS. I'm not familiar with that .. Isn't EFS a filesystem type, not a partition? Like EXTFS?
Epicenter714 said:
I checked and my phone has boot, system, recovery, data, pds and modem, but no EFS. I'm not familiar with that .. Isn't EFS a filesystem type, not a partition? Like EXTFS?
Click to expand...
Click to collapse
I don't understand, are you still having issues? Why are you asking about EFS?
arrrghhh said:
I don't understand, are you still having issues? Why are you asking about EFS?
Click to expand...
Click to collapse
I was replying to lovepreet39 about the EFS thing.
Epicenter714 said:
I was replying to lovepreet39 about the EFS thing.
Click to expand...
Click to collapse
EFS is a partition which contain your IMEI/MEID and Mac address information.
Please check in your settings is your IMEI/MEID there.
I gone from same problem and now IMEI/MEIS is zero.
---------- Post added at 03:54 PM ---------- Previous post was at 03:46 PM ----------
@arrrghhh
Please look at my thread, i also need help
Epicenter714 said:
I was replying to lovepreet39 about the EFS thing.
Click to expand...
Click to collapse
Yes, but he is having an issue with EFS. You, on the other hand, are not... correct?
You post seems to indicate that despite getting RSD to work, you are still having issues. I want to make sure that is not the case...
lovepreet39 said:
EFS is a partition which contain your IMEI/MEID and Mac address information.
Please check in your settings is your IMEI/MEID there.
I gone from same problem and now IMEI/MEIS is zero.
---------- Post added at 03:54 PM ---------- Previous post was at 03:46 PM ----------
@arrrghhh
Please look at my thread, i also need help
Click to expand...
Click to collapse
Hey buddy, I would love to help but that is way above my pay grade. I used my Q on Sprint, never liked mucking with that stuff personally.
@arrrghhh
Dear sir
Problem is that i wasted approx $250 on this device.
I am indian and $1 = Rs65 and $250 = Salary of one month.
I am here on XDA to save my $250.
There is no support on this phone in indian market,
If there any solution please help.
You can post here or PM me.
Or there is only by which i can only get my IMEI back, then i will apply GSM addon on it,
I do not care much about CDMA.
I know IMEI/MEID repair is illegal in USA.
For proof I can provide you original images of phone showing Zero Imei/meid
I do not want to change, only i want to restore original one.
First of all thanks for your help in advance.
I have a Galaxy Tab 2 10.1 GT-P5113 which I bought the way it is right now. It turns on and I can access recovery and download mode without any problems, but it will not boot into the actual OS. After turning on it will go straight to recovery. When rebooted from within recovery or by ODIN after flashing a ROM it will simply turn off and start charging. It will not turn on without having to unplug the cable. This is what I have tried:
- Flashed stock 4.1.1 from SamMobile using Odin 3.09 and Odin 1.85 there were no errors but same problem
- Flashed stock 4.2.2 from SamMobile using Odin 3.09 and Odin 1.85 there were no errors but same problem
- Installed CWM Touch 6.0.1.2 and wiped Dalvik cache and factory reset a few times after flashing each firmware version
- Installed TWRP 2.7.0.1 and wiped Dalvik cache, cache, data and factory reset a few times after flashing each firmware version
- Flashed each firmware and did stock factory reset and wiped cache each time
- Took it apart and removed battery for a few hours and tried every combination of what was mentioned again
- Downloaded "signed_espresso_20120220_16G.pit" and flashed a few times and redid all combinations again
On CWM no command gives any errors but on TWRP I do not get the "successful" notice when wiping Data, it kicks me out to the lock screen with no errors mentioned. Also on TWRP, when trying to fix permissions I get a failed error. When flashing stock 4.2.2 I get the "No command" and an error while trying to wipe cache follow by the device turning off. On the stock 4.1.1 ROM I get no errors whatsoever.
So as you may imagine I have spent numerous hours on Google and this forum and have not found a way to make it work. Please let me know if there is anything else I might be able to try. Thanks
I have the same problem but I know what I did to cause it.
Well, I don't know if you solved your problem, but I just registered to ask the same question. ONLY I KNOW HOW IT GOT THAT WAY. while messing around with learning how to flash new ROMs I executed a command that I didn't know what expect... mkntfs and followed through with mmcblk0p1 or mmcblk0p10... i'm not real sure which partition I messed up. but now I don't know how to reverse the thing and I have the exact problem you have.
Also I can't find a good reference source for Aroma File Manager's Terminal console. I'm just learning about Linux, CPM/android or whatever we call it these days.
Do I have to fix the kernel or is there a way to undo that command "mkntfs" in AromaFM??????
I TOO have the GT-P5113XAR but one of the aborted rom installations said it's a GT-5113RF, what is that????
GalaxyBrickMaker said:
Well, I don't know if you solved your problem, but I just registered to ask the same question. ONLY I KNOW HOW IT GOT THAT WAY. while messing around with learning how to flash new ROMs I executed a command that I didn't know what expect... mkntfs and followed through with mmcblk0p1 or mmcblk0p10... i'm not real sure which partition I messed up. but now I don't know how to reverse the thing and I have the exact problem you have.
Also I can't find a good reference source for Aroma File Manager's Terminal console. I'm just learning about Linux, CPM/android or whatever we call it these days.
Do I have to fix the kernel or is there a way to undo that command "mkntfs" in AromaFM??????
I TOO have the GT-P5113XAR but one of the aborted rom installations said it's a GT-5113RF, what is that????
Click to expand...
Click to collapse
Thanks for the reply. I frankly don't know much about what you said, but I decided to order a new board for the device and got it to work again. Now, super-duper-mega-smart-me decided to flash the same 4.2.2 ROM I got from Sammobile and guess what, the EXACT same problem occurred. I am hoping someone can helps us! Right now I am researching different ROM's and realized there are 2 kinds, XAR and XAC so I will experiment and let you know if I get any progress!
hopefully someone will read the problem and give us some advice.
I still haven't learned how to reverse a mkntfs command.
Flash P5113UEUCMK3 using PDA in Odin while in download mode should be all. You shouldn't have needed any other files or whatever...
Sent from my Nexus 4 using XDA Premium HD app
shakatu said:
Flash P5113UEUCMK3 using PDA in Odin while in download mode should be all. You shouldn't have needed any other files or whatever...
Sent from my Nexus 4 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for the reply. Actually you are right, all that had to be done was exactly that. However in my case the real problem, mentioned just so other people can see this if they have the same problem, was that the flex cable that charges the tablet was defective. I took the device apart and decided to unplug piece by piece turning the device on after each cable was unplugged and low and behold after disconnecting the charger flex it went straight to the OS instead of recovery. Weirdest thing ever, hope it helps someone else.
GalaxyBrickMaker said:
I still haven't learned how to reverse a mkntfs command.
Click to expand...
Click to collapse
In your case, based on what I have researched here is what you can try. Get into download mode, open ODIN, click on PIT and flash file "signed_espresso_20120220_16G.pit" which can be found in this forum, just do a search. After flashing the PIT go to SamMobile and download a ROM, preferably MK3 and flash using ODIN. After this it should work, hope it does for you!
Edit: Here is the link for the PIT: http://forum.xda-developers.com/showthread.php?t=2552155
thanks
"signed_espresso_20120220_16G.pit"
which can be found in this forum, just do a search.
After flashing the PIT go to SamMobile and download a ROM, preferably MK3 and flash using ODIN. After this it should work, hope it does for you!
Edit: Here is the link for the PIT:
http://forum.xda-developers.com/showthread.php?t=2552155
thank you for the informaiton I will let you know how it goes.. also can I flash any ROM after this or should I do the SAMMOBILE one first no matter what?
I already have the P5113XARUEU_P5113CSC...... file, but right before3 i messed it up I had Kit Kat running.
GalaxyBrickMaker said:
"signed_espresso_20120220_16G.pit"
which can be found in this forum, just do a search.
After flashing the PIT go to SamMobile and download a ROM, preferably MK3 and flash using ODIN. After this it should work, hope it does for you!
Edit: Here is the link for the PIT:
http://forum.xda-developers.com/showthread.php?t=2552155
thank you for the information I will let you know how it goes.. also can I flash any ROM after this or should I do the SAMMOBILE one first no matter what?
I already have the P5113XARUEU_P5113CSC...... file, but right before3 i messed it up I had Kit Kat running.
Click to expand...
Click to collapse
Sorry for the late reply, had a busy week. You probably already fixed it but it is my understanding you need to flash a stock ROM to get things going again and once that works make a backup of the working ROM using CWM recovery or similar and then flash whatever else on top of that to prevent further bricks. Thanks
more info please
Danz777 said:
First of all thanks for your help in advance.
I have a Galaxy Tab 2 10.1 GT-P5113 which I bought the way it is right now. It turns on and I can access recovery and download mode without any problems, but it will not boot into the actual OS. After turning on it will go straight to recovery. When rebooted from within recovery or by ODIN after flashing a ROM it will simply turn off and start charging. It will not turn on without having to unplug the cable. This is what I have tried:
- Flashed stock 4.1.1 from SamMobile using Odin 3.09 and Odin 1.85 there were no errors but same problem
- Flashed stock 4.2.2 from SamMobile using Odin 3.09 and Odin 1.85 there were no errors but same problem
- Installed CWM Touch 6.0.1.2 and wiped Dalvik cache and factory reset a few times after flashing each firmware version
- Installed TWRP 2.7.0.1 and wiped Dalvik cache, cache, data and factory reset a few times after flashing each firmware version
- Flashed each firmware and did stock factory reset and wiped cache each time
- Took it apart and removed battery for a few hours and tried every combination of what was mentioned again
- Downloaded "signed_espresso_20120220_16G.pit" and flashed a few times and redid all combinations again
On CWM no command gives any errors but on TWRP I do not get the "successful" notice when wiping Data, it kicks me out to the lock screen with no errors mentioned. Also on TWRP, when trying to fix permissions I get a failed error. When flashing stock 4.2.2 I get the "No command" and an error while trying to wipe cache follow by the device turning off. On the stock 4.1.1 ROM I get no errors whatsoever.
So as you may imagine I have spent numerous hours on Google and this forum and have not found a way to make it work. Please let me know if there is anything else I might be able to try. Thanks
Click to expand...
Click to collapse
Fortunately I got mine working again and now I have some more insight for you. Are there any errors showing when you're trying to install aarom?also if you use console in aroma file managercan you list all 11 or 12 partitions and aer they all available for you to access?
---------- Post added at 11:39 AM ---------- Previous post was at 11:25 AM ----------
I tried both things that you told me to try the pit file it might have helped but it didn't make it any different, there was still an error trying to find efs while flashing and I tried it almost everything the other guy here tried and nothing worked so I had to go learn some Linux and some Unix. After a couple weeks of studying what command does what, and realizing I should have learned Unix with the rest of my friends and back in high school. I came up with that make FS ext4 command.. as I said before I knew which command I used to mess it up so I figured since the mkntfs command was the one that messed itt up with them this one might work and I used it and it worked I was able to install a ROM 2 days ago. Apologize for my typing my hands hurt and I'm just using voice.
GalaxyBrickMaker said:
Fortunately I got mine working again and now I have some more insight for you. Are there any errors showing when you're trying to install aarom?also if you use console in aroma file managercan you list all 11 or 12 partitions and aer they all available for you to access?
---------- Post added at 11:39 AM ---------- Previous post was at 11:25 AM ----------
I tried both things that you told me to try the pit file it might have helped but it didn't make it any different, there was still an error trying to find efs while flashing and I tried it almost everything the other guy here tried and nothing worked so I had to go learn some Linux and some Unix. After a couple weeks of studying what command does what, and realizing I should have learned Unix with the rest of my friends and back in high school. I came up with that make FS ext4 command.. as I said before I knew which command I used to mess it up so I figured since the mkntfs command was the one that messed itt up with them this one might work and I used it and it worked I was able to install a ROM 2 days ago. Apologize for my typing my hands hurt and I'm just using voice.
Click to expand...
Click to collapse
I am glad you finally got it working. I never did play much with Aroma since my problem ended up being that defective cable but I will definitely consider learning those commands just in case.
I have a rooted StraightTalk SCH-S968C Samsung Galaxy S III (with the stock AOSP ROM) that I just screwed up. I had used EZ-Recovery to flash TWRP 2.2.0 to the phone. Now TWRP says there is no OS! I can only boot into TWRP - nothing else. It won't even let me power-down the phone. Is there some way I can recover from this, or do I now have a very expensive electronic brick (that runs TWRP)? I have adb installed on my laptop and I know it works, so that's one possible route to recovery. Any help would be much appreciated!
ScottDB said:
I have a rooted StraightTalk SCH-S968C Samsung Galaxy S III (with the stock AOSP ROM) that I just screwed up. I had used EZ-Recovery to flash TWRP 2.2.0 to the phone. Now TWRP says there is no OS! I can only boot into TWRP - nothing else. It won't even let me power-down the phone. Is there some way I can recover from this, or do I now have a very expensive electronic brick (that runs TWRP)? I have adb installed on my laptop and I know it works, so that's one possible route to recovery. Any help would be much appreciated!
Click to expand...
Click to collapse
I'm pretty sure it's possible to return it completely to stock with the COMBINATION_S968CUDUAMH1_S968CTFNAMH1_1304014_REV09_user_low_ship.tar.md5 file through Odin. I just to happen to have the file right here.. small warning though, it's 1.2 gigs.
https://mega.co.nz/#!gRI3DD5L!dRW8ORzfQI5j1JyKHVBTNifomPCXoqL14B9GF4oxvQY
aekel87 said:
I'm pretty sure it's possible to return it completely to stock with the COMBINATION_S968CUDUAMH1_S968CTFNAMH1_1304014_REV09_user_low_ship.tar.md5 file through Odin. I just to happen to have the file right here.. small warning though, it's 1.2 gigs.
https://mega.co.nz/#!gRI3DD5L!dRW8ORzfQI5j1JyKHVBTNifomPCXoqL14B9GF4oxvQY
Click to expand...
Click to collapse
That's the file I am offering to host on my Website, since nobody seems to be able to download it from Dropbox. I'm having trouble downloading it from Mega... Since the file is over 1 GB, Mega insisted I needed to download their extension, but it's not compatible with Firefox 22. I tried Chrome, and Mega says that Chrome on my laptop is "a bit outdated"... sheesh! I'll try and update it.
(added later) - I found a Dropbox link for the file and it's downloading now.
If you want to FTP the file to my Website, let me know by PM and I'll give you the username and password.
I tried using fastboot to install CWM Recovery, but fastboot is eternally "waiting for device" even though it's there (adb can see it).
Aug. 7 - Got the file I needed, but didn't use it since Windows7 would not recognize the phone even after I installed the drivers. (I think it was an issue with automatic updates being disabled...) In the meantime... I tried the button-combo for the bootloader (which I swore I tried the day before and it didn't work), and the phone booted into the bootloader! From there, I pressed "Volume down" to cancel & reboot the phone, and it went into the stock system - it was all still there! First thing I did was immediately use EZ-Recovery to flash CWM 5.8.4.5. - Issue resolved!
Deleted.
ScottDB said:
That's the file I am offering to host on my Website, since nobody seems to be able to download it from Dropbox. I'm having trouble downloading it from Mega... Since the file is over 1 GB, Mega insisted I needed to download their extension, but it's not compatible with Firefox 22. I tried Chrome, and Mega says that Chrome on my laptop is "a bit outdated"... sheesh! I'll try and update it.
(added later) - I found a Dropbox link for the file and it's downloading now.
If you want to FTP the file to my Website, let me know by PM and I'll give you the username and password.
I tried using fastboot to install CWM Recovery, but fastboot is eternally "waiting for device" even though it's there (adb can see it).
Aug. 7 - Got the file I needed, but didn't use it since Windows7 would not recognize the phone even after I installed the drivers. (I think it was an issue with automatic updates being disabled...) In the meantime... I tried the button-combo for the bootloader (which I swore I tried the day before and it didn't work), and the phone booted into the bootloader! From there, I pressed "Volume down" to cancel & reboot the phone, and it went into the stock system - it was all still there! First thing I did was immediately use EZ-Recovery to flash CWM 5.8.4.5. - Issue resolved!
Click to expand...
Click to collapse
Thank you!!!! I just had the same problem. However even when using cwm i get errors in the recovery. Unable to mount anything or do anything besides reboot. Any ideas?
need stock Firmware
Have any idea where i can get this file? Ive bricked my phone too. Durnnit!
iamwaynes said:
Have any idea where i can get this file? Ive bricked my phone too. Durnnit!
Click to expand...
Click to collapse
This is the h1 stock you need. type this in google you should find the download if not I have it.
COMBINATION_S968CUDUAMH1_S968CTFNAMH1_1304014_REV0
Dont use e-z recovery. I had the same problem neither cwm or twrp from ez recovery worked and then cwm said no os on my phine so I flashed that file from download mode and was back to stock.
How did u find a recovery that worked mine is saying the same thing
Sent from my SM-N900T using Tapatalk
iamwaynes said:
How did u find a recovery that worked mine is saying the same thing
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1771398
In that thread go down to method 2 of getting a custom recovery. I downloaded cwm touch from the link there and then installed it with android terminal emulator using the codes that it says to type in. I tried to look up that stock rom but I didnt find it. Its on the forum somewhere in a thread about how to root the straight talk s3 and how first you need to download and flash the h1 baseband stock rom
Thanks I found the stock rom fixing it now.
Sent from my SM-N900T using Tapatalk
iamwaynes said:
Thanks I found the stock rom fixing it now.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Ok I've re rooted and tried to install recovery. Odin put it in wrong place. Says no operating system . What now?
Sent from my SM-N900T using Tapatalk
iamwaynes said:
Ok I've re rooted and tried to install recovery. Odin put it in wrong place. Says no operating system . What now?
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Have you gotten recovery installed and straightened out yet?
Let me know if you need some help, tell me where you're at and what you've got going on with what you have.
I returned phone to stock. The recovery wasn't in the right place obviously. So that's where I am . Stuck back at stock. Thanks for any help you can give.
Sent from my SM-N900T using Tapatalk
iamwaynes said:
I returned phone to stock. The recovery wasn't in the right place obviously. So that's where I am . Stuck back at stock. Thanks for any help you can give.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Are you on stock not rooted or you are rooted?
Do you have stock recovery or custom.
I can get you to wherever you need or want. Tell me what you need or where you'd like to be.
Droidriven said:
Are you on stock not rooted or you are rooted?
Do you have stock recovery or custom.
I can get you to wherever you need or want. Tell me what you need or where you'd like to be.
Click to expand...
Click to collapse
I have combined 2 s3's to make one good one. This is the proper thread for the model of the chipset. The phone has been worked on buy someone who only thought they were a genious. I've found traces and from surfing the forums I'm pretty sure I know what they did even. I'm gonna grab these stock images and flash back to stock. I just wanted to put a word in now to see how dead this thread is. BTW just for the record easy safe root is achievable with safroot for Att g s 4. I've confirmed that. Root is no issue. Modem drivers are jacked up. I want what I have now with WiFi in tact and custom recovery. Just wanted to get the word in in case I hit a wall with recovery as I am now before the flash to stock. Thanks in advance for any help. Sorry for the ramble
---------- Post added at 07:23 AM ---------- Previous post was at 07:03 AM ----------
ScottDB said:
That's the file I am offering to host on my Website, since nobody seems to be able to download it from Dropbox. I'm having trouble downloading it from Mega... Since the file is over 1 GB, Mega insisted I needed to download their extension, but it's not compatible with Firefox 22. I tried Chrome, and Mega says that Chrome on my laptop is "a bit outdated"... sheesh! I'll try and update it.
(added later) - I found a Dropbox link for the file and it's downloading now.
If you want to FTP the file to my Website, let me know by PM and I'll give you the username and password.
I tried using fastboot to install CWM Recovery, but fastboot is eternally "waiting for device" even though it's there (adb can see it).
Aug. 7 - Got the file I needed, but didn't use it since Windows7 would not recognize the phone even after I installed the drivers. (I think it was an issue with automatic updates being disabled...) In the meantime... I tried the button-combo for the bootloader (which I swore I tried the day before and it didn't work), and the phone booted into the bootloader! From there, I pressed "Volume down" to cancel & reboot the phone, and it went into the stock system - it was all still there! First thing I did was immediately use EZ-Recovery to flash CWM 5.8.4.5. - Issue resolved!
Click to expand...
Click to collapse
Does anyone have a good link for h1 stock. All the links I can find including aa51 are dead. I need to go stock to fix the modem. I can handle everything from there I just need stock and I've trolled XDA , aa51, and several others. All links are dead. Probably for a long long time . any help is greatly appreciated
---------- Post added at 07:42 AM ---------- Previous post was at 07:23 AM ----------
sazendrak said:
I have combined 2 s3's to make one good one. This is the proper thread for the model of the chipset. The phone has been worked on buy someone who only thought they were a genious. I've found traces and from surfing the forums I'm pretty sure I know what they did even. I'm gonna grab these stock images and flash back to stock. I just wanted to put a word in now to see how dead this thread is. BTW just for the record easy safe root is achievable with safroot for Att g s 4. I've confirmed that. Root is no issue. Modem drivers are jacked up. I want what I have now with WiFi in tact and custom recovery. Just wanted to get the word in in case I hit a wall with recovery as I am now before the flash to stock. Thanks in advance for any help. Sorry for the ramble
---------- Post added at 07:23 AM ---------- Previous post was at 07:03 AM ----------
Does anyone have a good link for h1 stock. All the links I can find including aa51 are dead. I need to go stock to fix the modem. I can handle everything from there I just need stock and I've trolled XDA , aa51, and several others. All links are dead. Probably for a long long time . any help is greatly appreciated
Click to expand...
Click to collapse
Finally found it here
https://forum.xda-developers.com/showthread.php?t=2516498&page=28