Related
So, this happened recently, and I fixed it. Link: http://forum.xda-developers.com/showthread.php?t=1735119
Well, outta no where, same basic issue, but with a twist.
This afternoon while I was asleep my GTab rebooted. It came back to the "Samsung Galaxy Tab 7.0 Plus" splash screen and is stuck. I *can* get into download mode, and I can almost get into recovery. When I try to go into recovery, it loads what looks like it will be recovery, then says:
# Manual Mode #
-- Updating Application
Then a minute or so later it reboots right back to the GT7+ splash screen and stays there...
Twist:
So, knowing what I did last time, I installed Odin and the Samsung drivers on my POS computer at home, booted into Download Mode, and did the "PDA" option with the correct FW (same as I used last time for the T869 from SamMobile, I saved all the files). It runs through just fine, gets to the end and the Tab reboots. It then goes into recovery and and does a few things (I believe it said it was deleting the cache and a few other processes). Then, lastly, it again says:
"# Manual Mode #
-- Updating Application
... followed by a reboot, and back to hanging on the boot logo.
Any ideas?!? Ironically, I put it on CL today to see if I can sell it for enough to cover a Nexus7. I woke up to an offer, and a bricked Tab. Figures.
Any thoughts/help are greatly appreciated. The sooner the better. lol
Is it possible that I need to flash a good recovery in Odin? If so, what's the procedure. and can someone link me to the one I would need for the US TMobile 4G version of the GT7+?
Also, since flashing the stock FW isn't fixing anything, and it seems like a possible Recovery issue, a friend at work is suggesting I choose the option in Odin to delete the partitions.
Thoughts??? (quickly)
Damn dude, again?
I think there is 3 or 4 threads about this on this forum and same amount on 7.7 forum. None come to a cause our solution, seems like people repeats some procedures and out of nothing it works again.
When it happened to me a let its battery drain fully to the point it won't turn on anymore let it this way for some time. Then fully charged, this is a little harmful to your bat, for the record. Then try to turn on, it will take some time but eventually it could enter on the system.
I think the data partition got corrupted.
Sent from my GT-P6210 using Tapatalk 2
Yup.
So, I tried the option in Odin to re0make the partition, and every time I try it fails with an error of "Can't Open Package" (or something along those lines).
I have reinstalled the FW through Odin no less than 10 times, nogo. The first time I open recovery after flashing, It says it is installing a package, clearing cache, etc, and the last line always says "-- Updating Application". After 10-15 seconds, that goes away and it reboots only to hang on the GT7Plus splash screen again. Then, any time I go into recovery after that first post-Odin instance, if says:
"# Manual Mode #
-- Updating Application
Should I be trying to reinstall Recovery? If so, what do I use (link)? Also, how do I do that in Odin...
I believe that for use remake partition you have to provide the pit file if your stock does not have it.
Anyway I did that also about 3 times, providing the pit and the md5, they flashed ok, but the problem was the same. Did you tried the battery thing? Some guy give a tip to start with the usb plugged.
Sent from my MB525 using Tapatalk 2
leodfs said:
I believe that for use remake partition you have to provide the pit file if your stock does not have it.
Anyway I did that also about 3 times, providing the pit and the md5, they flashed ok, but the problem was the same. Did you tried the battery thing? Some guy give a tip to start with the usb plugged.
Sent from my MB525 using Tapatalk 2
Click to expand...
Click to collapse
Where was that tip? Link?
Also, any one have that .pit file I can try with?
http://forum.xda-developers.com/showthread.php?p=28574760
Sent from my MB525 using Tapatalk 2
Hey buddy..
Which fw u using? T869 came shipped with 2 different, search for both of them and try each one...don't use repartition without the correct pit file...
Maybe not here but I google sgh-t869 factory and found a website with both tar
Sent from my Galaxy Nexus using xda app-developers app
statuzz said:
Hey buddy..
Which fw u using? T869 came shipped with 2 different, search for both of them and try each one...don't use repartition without the correct pit file...
Maybe not here but I google sgh-t869 factory and found a website with both tar
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I'm not sure which file it is that I'm using, I'll have to look at home in a couple of hours. This happened to me a few weeks ago (link in original post), and I flashed this FW with Odin and it recovered, and has been fine since (till now), so I know it's at least a usable FW. I'll try to find the other one today.
I just tried finding the stock pit file for the TMo SGH-T869, but I can't find it. Anyone have a link to it by chance? Also, once I get it, what do I do (options to choose) in Odin to flash it?... and do I do it at the same time as the FW?
Thanks for any help! I was really hoping to sell it in the next day or two to fund the Nexus7, so now I'm really frustrated.
ETA: Also, I let it completely die, to the point it wouldn't boot. Then charged it for a bit and booted. Same issue.
I think that if u find the pit file they should be flash at the same time...fw in pda and pit in phone...(this need to be check to confirm) after flashing.. reboot into factory recovery wipe everything and try to boot
Hopefully u fix that today
Sent from my Galaxy Nexus
When it happened to me, i flashed the pit first and at the same with stock with re partition checked, didnt help. I did everything that I could find and I feel like it only worked again by itself
You can look every single thread of this exact problem, the ones that got it back working can't really say how, they flash everything many times and it suddenly works.
The good things are that flash the stock ones don't increase you flash count, and as long as you can enter download mode you are not really s#%
Sent from my MB525 using Tapatalk 2
Thanks for the help...
Anyone have a link to the .pit for this model (T869)?
Also, I had a thought. When I go into Recovery, I get the following and then it reboots again:
# Manual Mode #
-- Updating Application
1. Is it possible that recovery is hosed, and overwriting it with a fresh version will allow me to wipe the device, set to factory and then boot? Maybe this is the issue?
2. Is it even possible to just flash a fresh copy of the recovery over whatever is there (or replace it)?
2.a. If it is possible, what file should I use, and do I do it though Odin? Anyone have a link to what I should use?
Thanks :good:
VisualOddity said:
Thanks for the help...
Anyone have a link to the .pit for this model (T869)?
Also, I had a thought. When I go into Recovery, I get the following and then it reboots again:
# Manual Mode #
-- Updating Application
1. Is it possible that recovery is hosed, and overwriting it with a fresh version will allow me to wipe the device, set to factory and then boot? Maybe this is the issue?
2. Is it even possible to just flash a fresh copy of the recovery over whatever is there (or replace it)?
2.a. If it is possible, what file should I use, and do I do it though Odin? Anyone have a link to what I should use?
Thanks :good:
Click to expand...
Click to collapse
The problem is that there's is not development for t869 so there's not much to look for...just factory images and root method
Sent from my Galaxy Nexus
Can anyone link me to the proper pit file? Also, in the linked thread a few posts back, there are a couple of files, will those work for this?
Can someone post the proper pit file for me so I can repartition? I'm doing this on my wife's phone because my internet at home is down till tomorrow...
Lastly, recovery. Since when I go into recovery it says "manual mode" then reboots, can I replace recovery only? Then I can wipe and whatnot in it and maybe that will do the trick. If so, can someone link me to the proper recovery and tell me how to do it in Odin? What happens if I watch the FW flash, then right after it completes the recovery portion, I unplug it? Bad?
VisualOddity said:
Can anyone link me to the proper pit file? Also, in the linked thread a few posts back, there are a couple of files, will those work for this?
Can someone post the proper pit file for me so I can repartition? I'm doing this on my wife's phone because my internet at home is down till tomorrow...
Lastly, recovery. Since when I go into recovery it says "manual mode" then reboots, can I replace recovery only? Then I can wipe and whatnot in it and maybe that will do the trick. If so, can someone link me to the proper recovery and tell me how to do it in Odin? What happens if I watch the FW flash, then right after it completes the recovery portion, I unplug it? Bad?
Click to expand...
Click to collapse
i think u should forget about the pit file, couz the firmware have the pit repackage with the tar, im gussing u will only need the pit file in case u want to change the phone partitions, try to get those 2 fw and try them :good:
That's why I'd like the pit file, so I can check the option in Odin to re-partition.
So, I have internet at home now. I have now tried again letting it completely die, then completely charge, same issue. I have also tried 2 different versions of the SGH-T869 firmware.
Any thoughts?
Also, given what I have done so far, I posted this yesterday, any thoughts?
"Lastly, recovery. Since when I go into recovery it says "manual mode" then reboots, can I replace recovery only? Then I can wipe and whatnot in it and maybe that will do the trick. If so, can someone link me to the proper recovery and tell me how to do it in Odin? What happens if I watch the FW flash, then right after it completes the recovery portion, I unplug it? Bad? "
Yes. Unplug is bad. Possibly fatal. you should be able to.find a stock recovery.img in a stock Odin.tar, flash it with heimdall. Recommend factory reset beforeand after doing so.
I dont know about tmobile tabs but international ones look to apply CSC files after displaying that manual mode message. Perhaps something has gone awry with a CSC,etc.
chrisrotolo said:
Yes. Unplug is bad. Possibly fatal. you should be able to.find a stock recovery.img in a stock Odin.tar, flash it with heimdall. Recommend factory reset beforeand after doing so.
I dont know about tmobile tabs but international ones look to apply CSC files after displaying that manual mode message. Perhaps something has gone awry with a CSC,etc.
Click to expand...
Click to collapse
Thank You. A few questions:
Would that stock recovery.img have to be model specific. i.e. for the SGH-T869, or could it be from any GT 7 Plus (or is it generic on all devices with HoneyComb)? I *think* from experience it has to be T869 specific, but it's worth asking.
Also, about Heimdall, where do I get that, and how do I use it to flash? I've heard of it, but never used it.
Lastly, about the CSC files. That makes sense seeing as what it's doing, so that *could* be the whole issue. How can I overcome that? Can I download and flash those files somehow? Do you have a link to them?
Thanks for the help everyone. I'm hoping that in doing all this, maybe whatever ends up fixing this will be a guide for everyone else having the issue...
OK, I saw a couple of you guys mention the 7.7 people having this issue, so I went there to research. If I am reading right, it *sounds* like this could be a solid mix of a data system being corrupted, and the stock recovery (Samsung e3?) being bad.
Someone mentioned that you can pull the stock recovery.img from a the firmware, make a .tar with only that, then flash that. Once that's done you can do a full wipe in recovery, flash the full FW, and hopefully be back in business.
I want to try this, and if it works, maybe we will have a proven solution for the people getting this issue. However, not only have I never created a .tar, I have especially never created a flashable .tar, so...
What do I do? Other than pulling the recovery.img from the FW, how do I do this?
[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 need help fixing this problem I'm having, I've tried everything I can think of, in the first pic this is what the phone reboots to after flashing official firmware with Odin and the second pic is what I get when I try to factory wipe. Please help me!!!!
JrTech said:
I need help fixing this problem I'm having, I've tried everything I can think of, in the first pic this is what the phone reboots to after flashing official firmware with Odin and the second pic is what I get when I try to factory wipe. Please help me!!!!
Click to expand...
Click to collapse
Try first to install TWRP recovery instead of Samsung recovery using odin with the phone in the downloading mod
Then wipe every thing using Twrp
Then flash that rom using twrp
I installed twrp 3.0.3-0 and i still can't wipe anything, unable to mount data,storage and cache,tried changing the data partition type to vfat but no matter what I try it all ends with unable to mount data, storage and cache
Bro flash 4 firmware file that 100% it will be fix
---------- Post added at 04:44 PM ---------- Previous post was at 04:34 PM ----------
https://forum.xda-developers.com/galaxy-j7/development/j700h-marshmallow-update-method-rom-t3399433
---------- Post added at 04:45 PM ---------- Previous post was at 04:44 PM ----------
Just flash 4 firmware AP. CP. BL. CSC and tell me bro..
amarshah said:
Bro flash 4 firmware file that 100% it will be fix
---------- Post added at 04:44 PM ---------- Previous post was at 04:34 PM ----------
https://forum.xda-developers.com/galaxy-j7/development/j700h-marshmallow-update-method-rom-t3399433
---------- Post added at 04:45 PM ---------- Previous post was at 04:44 PM ----------
Just flash 4 firmware AP. CP. BL. CSC and tell me bro..
Click to expand...
Click to collapse
Hey thanks for the input, sorry I haven't replied, but believe it or not everything I do on the internet is with my mobile data and I had no data,I'm in a remote area at the moment but I should be in the city tomorrow, there I'll have access to the WiFi and I'll download and let you know what happens:fingers-crossed:
JrTech said:
Hey thanks for the input, sorry I haven't replied, but believe it or not everything I do on the internet is with my mobile data and I had no data,I'm in a remote area at the moment but I should be in the city tomorrow, there I'll have access to the WiFi and I'll download and let you know what happens:fingers-crossed:
Click to expand...
Click to collapse
Ok bro try it and say me?
Hey bro I tried it and got the same result, so here I go again downloading another one, will let u know what happens.
JrTech said:
Hey bro I tried it and got the same result, so here I go again downloading another one, will let u know what happens.
Click to expand...
Click to collapse
I'm beginning to think this is hardware related, I've already flashed four different firewares including the one you told me to use and the phone boots up rite back to the same error!!! I'm kinda sceptical though because the Odin flashing always goes well, everything loads until Odin says pass.
JrTech said:
I'm beginning to think this is hardware related, I've already flashed four different firewares including the one you told me to use and the phone boots up rite back to the same error!!! I'm kinda sceptical though because the Odin flashing always goes well, everything loads until Odin says pass.
Click to expand...
Click to collapse
Sounds like your partitions are jacked up, might try flashing a new pit file
Sent from my SM-J700P using Tapatalk
JrTech said:
I'm beginning to think this is hardware related, I've already flashed four different firewares including the one you told me to use and the phone boots up rite back to the same error!!! I'm kinda sceptical though because the Odin flashing always goes well, everything loads until Odin says pass.
Click to expand...
Click to collapse
Flash the firmware with the PIT file and check re-partition.
How did the device arrive at this state?
ashyx said:
Flash the firmware with the PIT file and check re-partition.
How did the device arrive at this state?
Click to expand...
Click to collapse
Hey thanks for the input guys, this phone got wet and when it was dried and turned on again this is the state its started in. I took out the logic board and checked for any damage from the water (corrosion) and its all clean, I even sprayed it with WD (water displacement), allowed it to drain and then heated it with the heat gun which vaporized the WD. I flashed with the pit file and all goes well, but it just reboots back to same errors. Fellas feel free to msg me on WhatsApp +5926792003 anytime. I'm just happy to know there is a place I can ask for help and get it! Here in Guyana the few phone techs I've talk to don't seem to be this in depth with some of the stuff I've learned from here, all these Guyanese tell me to do is change the board but I'd rather be sure that its beyond repair before I invest my hard earned money which is not easy to come by. The cost of the board is around 23000 Guyana dollars, which would be about 105 USD.
I forgot to mention, when I flashed twrp, in the advance wipe option, when I choose repair, I can see an actual size on the system and cache partition, but all other partitions show 0mb.
JrTech said:
Hey thanks for the input guys, this phone got wet and when it was dried and turned on again this is the state its started in. I took out the logic board and checked for any damage from the water (corrosion) and its all clean, I even sprayed it with WD (water displacement), allowed it to drain and then heated it with the heat gun which vaporized the WD. I flashed with the pit file and all goes well, but it just reboots back to same errors. Fellas feel free to msg me on WhatsApp +5926792003 anytime. I'm just happy to know there is a place I can ask for help and get it! Here in Guyana the few phone techs I've talk to don't seem to be this in depth with some of the stuff I've learned from here, all these Guyanese tell me to do is change the board but I'd rather be sure that its beyond repair before I invest my hard earned money which is not easy to come by. The cost of the board is around 23000 Guyana dollars, which would be about 105 USD.
I forgot to mention, when I flashed twrp, in the advance wipe option, when I choose repair, I can see an actual size on the system and cache partition, but all other partitions show 0mb.
Click to expand...
Click to collapse
Bro don't ever flash the pit. Go to www.sammobile.com and download the J700TUVU2APK6 firmware. Extract the zip on your PC and open Odin. Now go to Options (2nd tab) and unclick auto reboot. Click bootloader update, Nanderase all and reset time. Put the tar in the AP slot and flash it. When it completes flashing pull your battery. Boot into recovery holding the right buttons and let the phone erase and update the system. When it finishes it should boot into recovery by itself, if it doesn't pull your battery and boot into recovery again. Then let the phone boot and you're good to go. When you root this time and install TWRP make sure OEM unlock and USB debugging are ticked in developer options this time.
Metabolic12 said:
Bro don't ever flash the pit. Go to www.sammobile.com and download the J700TUVU2APK6 firmware. Extract the zip on your PC and open Odin. Now go to Options (2nd tab) and unclick auto reboot. Click bootloader update, Nanderase all and reset time. Put the tar in the AP slot and flash it. When it completes flashing pull your battery. Boot into recovery holding the right buttons and let the phone erase and update the system. When it finishes it should boot into recovery by itself, if it doesn't pull your battery and boot into recovery again. Then let the phone boot and you're good to go. When you root this time and install TWRP make sure OEM unlock and USB debugging are ticked in developer options this time.
Click to expand...
Click to collapse
Hey thanks bro, going to try this now, will post what happens.
Metabolic12 said:
Bro don't ever flash the pit. Go to www.sammobile.com and download the J700TUVU2APK6 firmware. Extract the zip on your PC and open Odin. Now go to Options (2nd tab) and unclick auto reboot. Click bootloader update, Nanderase all and reset time. Put the tar in the AP slot and flash it. When it completes flashing pull your battery. Boot into recovery holding the right buttons and let the phone erase and update the system. When it finishes it should boot into recovery by itself, if it doesn't pull your battery and boot into recovery again. Then let the phone boot and you're good to go. When you root this time and install TWRP make sure OEM unlock and USB debugging are ticked in developer options this time.
Click to expand...
Click to collapse
Please don't make statements when you're not sure what it is your advising.
Flashing the firmware hasn't worked as already posted.
The device is beyond simply flashing the firmware. It is fine to flash the PIT file with the state the device is already in.
@JrTech
It seems your partitions are damaged. There is hope if the system partition can be mounted which means the EMMC isn't totally dead.
Boot to TWRP and save the recovery log. Post the recovery.log file here (not the output).
ashyx said:
Please don't make statements when you're not sure what it is your advising.
Flashing the firmware hasn't worked as already posted.
The device is beyond simply flashing the firmware. It is fine to flash the PIT file with the state the device is already in.
Click to expand...
Click to collapse
I was just checking on the firmware he advised to download and wondering how would this be compatible with my j700h, because this is a T-Mobile update
JrTech said:
I was just checking on the firmware he advised to download and wondering how would this be compatible with my j700h, because this is a T-Mobile update
Click to expand...
Click to collapse
Exactly, it's the wrong firmware.
Did you ensure to check Re-partition when flashing?
ashyx said:
Please don't make statements when you're not sure what it is your advising.
Flashing the firmware hasn't worked as already posted.
The device is beyond simply flashing the firmware. It is fine to flash the PIT file with the state the device is already in.
@JrTech
It seems your partitions are damaged. There is hope if the system partition can be mounted which means the EMMC isn't totally dead.
Boot to TWRP and save the recovery log. Post the recovery.log file here (not the output).
Click to expand...
Click to collapse
Cool will post the log in a few mins
ashyx said:
Exactly, it's the wrong firmware.
Did you ensure to check Re-partition when flashing?
Click to expand...
Click to collapse
Yes I did, and I do think when I add the pit file Odin automatically checks re-partition, I checked to make sure and it is set to re-partition, all with the same result as before.
Hey ashyx I'm out running an errand, but I'll post the log as soon as I get back in. Thanks for your help and patience bro!
JrTech said:
Hey ashyx I'm out running an errand, but I'll post the log as soon as I get back in. Thanks for your help and patience bro!
Click to expand...
Click to collapse
No rush, I'm at work for the next few hours, so won't be able to examine the log until then.
I am using the latest stable nightly build for me, the one released in 04-04 of the LineageOS.
The build is working fine, however, I need to go back to stock firmware.
Last time I tried to do it using newest Odin, I was on latest build (the one that has all those crashes) and right at the beginning of the flashing process, the writing of system.img to System partition fails and the device was bricked.
Bricked up to the point where a restore using Samsung Switch was the only apparent solution. So I went for it. I have to say it is a really annoying procedure, you will need your device serial number and a good internet connection. When the download was finished, the software instructed me to go into install mode. The installation started anf seemed to be doing fine, but sadly the process has failed at 67%.
I'm afraid that the same thing could happen again.
Could you please help me out?
Thanks.
use Odin
Sent from my SM-G930F using Tapatalk
bustyouup4free said:
use Odin
Click to expand...
Click to collapse
I used latest odin for all operations. Flashed all files, including home and the other CSC. The write error occured the whole time.
hemp_invader said:
I used latest odin for all operations. Flashed all files, including home and the other CSC. The write error occured the whole time.
Click to expand...
Click to collapse
First - Wrong section, this is development not help, https://forum.xda-developers.com/galaxy-s7/help
Second maybe your download is corrupted, or the wrong model, in odin double check sections you know csc, modem, bootloader, and ap, check your drivers and usb cable
Check Your usb cable, don't use an usb hubs, also check is your battery is good
Give log from odin