Related
Here was my situation, and how I got out of it:
I was running the Perception build 7 ROM. It was great, no issues except that I needed to get some kernel modules for it, and was unable to get the info I needed to re-create the kernel build environment. I decided to return to stock. There were lots of threads, all going in different directions with inconsistent advice. The wiki I was looking at has what appeared to be a ClockworkMod (CWM) backup.
I had already tried to restore my own CWM backup, but (after disabling lagfix) would restore, but then seemed to loop trying to start the lock screen. Same thing with the version on the wiki. I didn't want to restore to the ATT version and I didn't have windows to run Odin...
So this should work from Windows, Linux and Mac.
get param.lfs from http://forum.xda-developers.com/showpost.php?p=9663090&postcount=58
get FIRMWARE from http://forum.xda-developers.com/showpost.php?p=9109370&postcount=697
Get Odin.rar from http://forum.xda-developers.com/showpost.php?p=8802897&postcount=1
Get Heimdall from http://www.glassechidna.com.au/products/heimdall/
Install Heimdall and any drivers it requires.
Extract the .pit file from Odin.rar. I have heard other people say don't use the pit file…I did…
Unzip the firmware
start Heimdall
FactoryFS
- factory.rfs
Kernel
- zImage
Param.lfs
- param.lfs - though I didn't use this
Primary Bootloader
- I left this blank
Secondary Bootloader
- I left this blank
Cache
- cache.rfs
Modem
- modem.bin
FactoryFS
- factory.rfs
Click Start
Phone will do it's thing. I did receive an error at the very end but all went well. I'd welcome some additional info on the Primary/Secondary Bootloader.
Curious if this restored the bootloader from at&t back to the rogers one?
Excellent! Another successful restore of Rogers stock with Heimdall. Thank you for the write up, gin032.
@Gin Which driver did you install ? WinUSB or libusb ?
Does your Start button starts greyed out ?
I tried both drivers and the only time the Start button is active is when i put a file in primary bootloader. I tried opening heimdall prior and after the phone is in download mode but the Start button always stay inactive. Odin on the other hand always detect my phone in download mode.
Just trying to figure out both apps
I had the same troubles is well.
silvertag said:
@Gin Which driver did you install ? WinUSB or libusb ?
Does your Start button starts greyed out ?
I tried both drivers and the only time the Start button is active is when i put a file in primary bootloader. I tried opening heimdall prior and after the phone is in download mode but the Start button always stay inactive. Odin on the other hand always detect my phone in download mode.
Just trying to figure out both apps
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I896 using XDA App
I'm running on the Mac and Linux so I haven't tried the Windows version yet. I'll try to take a look over the next few days.
silvertag said:
@Gin Which driver did you install ? WinUSB or libusb ?
Does your Start button starts greyed out ?
I tried both drivers and the only time the Start button is active is when i put a file in primary bootloader. I tried opening heimdall prior and after the phone is in download mode but the Start button always stay inactive. Odin on the other hand always detect my phone in download mode.
Just trying to figure out both apps
Click to expand...
Click to collapse
gin032 said:
I'm running on the Mac and Linux so I haven't tried the Windows version yet. I'll try to take a look over the next few days.
Click to expand...
Click to collapse
Heimdall might not work for you on Mac, that requires an official Froyo update with fixed secondary bootloader. Should work fine on Linux if you followed readme file instructions.
Sent from my SAMSUNG-SGH-I896 using XDA App
This seems to be correct. I tried Heimdall on both Windows 7 32-bit and Mac OS X Leopard and neither worked for me.
I could never select the "Start" button on either, and it seems your assertion that a secondary boot loader is required for Mac OS X is bang on.
I instead used Odin with the Pit file from this thread and the stock Rogers firmware and it seems to have worked.
Only the AT&T World Phone boot screen still shows up as a remnant of my previous flashing to Cognition.
I think I would have stayed with Cog if not for the reduced battery life, GPS lock-on slowness and static with BlueTooth head sets, as otherwise it is a fabulous ROM.
Either way, thanks to the OP for at least giving us the tips we needed to restore our older, but better than AT&T firmware!
sshvetsov said:
Heimdall might not work for you on Mac, that requires an official Froyo update with fixed secondary bootloader. Should work fine on Linux if you followed readme file instructions.
Sent from my SAMSUNG-SGH-I896 using XDA App
Click to expand...
Click to collapse
soooo why is the "start" button grayed out???
soooo why is the "start" button grayed out???
Probably because you didn't read instructions and to prevent you from unknowingly bricking your phone. You most likely didn't uncheck the repartition option.
Sent from my SAMSUNG-SGH-I896 using XDA App
SteveCheeseman said:
soooo why is the "start" button grayed out???
Click to expand...
Click to collapse
10ee said:
This seems to be correct. I tried Heimdall on both Windows 7 32-bit and Mac OS X Leopard and neither worked for me.
I could never select the "Start" button on either, and it seems your assertion that a secondary boot loader is required for Mac OS X is bang on.
I instead used Odin with the Pit file from this thread and the stock Rogers firmware and it seems to have worked.
Only the AT&T World Phone boot screen still shows up as a remnant of my previous flashing to Cognition.
I think I would have stayed with Cog if not for the reduced battery life, GPS lock-on slowness and static with BlueTooth head sets, as otherwise it is a fabulous ROM.
Either way, thanks to the OP for at least giving us the tips we needed to restore our older, but better than AT&T firmware!
Click to expand...
Click to collapse
sshvetsov said:
Probably because you didn't read instructions and to prevent you from unknowingly bricking your phone. You most likely didn't uncheck the repartition option.
Sent from my SAMSUNG-SGH-I896 using XDA App
Click to expand...
Click to collapse
sshvetsov is 100% correct. If it wasn't for the fact I put in functionality to grey out the start button you'd now have a bricked device. You can not repartition your device unless you provide all the necessary files.
It doesn't help that for a long time the samfirmware website was spreading misinformation about requiring you specify a PIT file in Odin without repartition checked. There's no need to select a PIT file when you're not repartitioning, in fact Odin will just ignore the fact that you have done so.
The start button isn't greyed out when you don't have a working secondary bootloader. Instead, after you press Start, you will receive a message saying your device couldn't be detected.
Benjamin Dobell said:
sshvetsov is 100% correct. If it wasn't for the fact I put in functionality to grey out the start button you'd now have a bricked device. You can not repartition your device unless you provide all the necessary files.
It doesn't help that for a long time the samfirmware website was spreading misinformation about requiring you specify a PIT file in Odin without repartition checked. There's no need to select a PIT file when you're not repartitioning, in fact Odin will just ignore the fact that you have done so.
The start button isn't greyed out when you don't have a working secondary bootloader. Instead, after you press Start, you will receive a message saying your device couldn't be detected.
Click to expand...
Click to collapse
In my case, I did re-partition....but in the interest of fullness, where can one find such a secondary bootloader?
Bricked my rogers i896 while trying to mash up different kernels for a rom, odin didnt work so i tried heimdall with the procedures thanks to OP.
The only difference was I did not use the pit file. Everything worked flawlessly and I still managed to maintain my data on root sd although i lost root access. The ATT splash screen also was removed (thank goodness) and model number changed back to i896 in the "About". It is now back to pretty much stock, though I did lose the APN settings (can easily reenter it). Last step now is just to re-root and restore via Titanium Backup.
Thanks for the helpful information everyone!
Now that 2.2 is out on Kies, it should become a lot simpler to restore to stock Rogers.
All we need is an ODIN image from the 2.2 release.
loonieryan said:
Now that 2.2 is out on Kies, it should become a lot simpler to restore to stock Rogers.
All we need is an ODIN image from the 2.2 release.
Click to expand...
Click to collapse
This please!
I've tried this, but use zadig.exe my phone shows up as Gadget Serial. So I installed anyways, it says successful, but nothing happens in the frontend that shows the phone and it doesn't allow me to start anything.
ootz0rz said:
Curious if this restored the bootloader from at&t back to the rogers one?
Click to expand...
Click to collapse
+1 this is important!
Tried doing this and my phone is now a brick. It's stuck at the following image:
Phone...Yellow exclamation...PC
Edit: Just got download mode back but still not working for me
Edit: Got Odin3 to work finally. Flashing JL1. Hoping it works.
ok, I have a real challenge.
I made the derp of giving my phone temp root using Z4root, then I ran OneClickLagFix on the phone. The phone rebooted & now just goes to a black screen after the rogers logo. it is on but does not respond to anything (capacitive butons light up when pressed).
I tried the steps listed here to revert to factory but it didn't help. Any ideas?
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?
Hi,
I was trying to root and install a custom rom on a friends phone. She has T-Mobile Galaxy S 4G. I was rushing through the whole project cause I had work and accidentally installed T-Mobile Vibrant Stock 2.1 using Heimdall. It was my fault. I did a google search for SGH-T959, but failed to realize that SGH-t959U is Vibrant and SGH-T959V is Samsung Galaxy S 4G...
After flashing the wrong ROM, I could not get it back into Download mode. I removed the SIM, SD card, Battery, and then tried putting it back into download mode (without the SIM or SD card) and that worked. I was able to get it into download mode at that point, but it would still not turn on or boot into recovery.
After realizing it was the wrong Flash, I searched online and found this http://forum.xda-developers.com/showthread.php?t=1358498 , after searching for users who bricked their phone previously and this was listed as a solution... the phone doesn't boot now however. It loads into Samsung Recovery (3e) and gives the error:
--Applying Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/TMB/system/'
Successfully applied multi-CSC
Each time i try to 'reboot system now' it just loops back to recovery with the same error. On that link i listed above, it says to install bootloaders if that CSC issue exists. Problem is, each time i try, it says PIT failed and then it just disconnects and wont reboot, requiring me to reflash the package all-together.
This phone was originally on 2.3.6 and the problem is I tried rooting using Vibrant instructions which was to go back to 2.1, then flash root, then CWM, then custom ROM.
How do i get this phone working again. I can pick up where i left off as far as rooting and installing a custom ROM. I have experience with it... But I have no idea how to get this phone out of this soft-brick. Can anyone please assist me. I feel terrible for messing up my friends phone.
Thanks a bunch!
TL;DR - Soft bricked SGS4G by flashing Vibrant ROM, tried to correct using SuperOneClick heimdall, doesnt work. please help. Originally was completely stock.
Read the second link in my signature and see if it helps you with Heimdal.
lumin30 said:
Read the second link in my signature and see if it helps you with Heimdal.
Click to expand...
Click to collapse
Yeah, I've read that when I was searching for a fix on my lunch break. My laptop is a MAC however. Which is why I didn't ODIN. I lost my Windows partition a while ago, along with my Windows CD.... Is there anyway I can get some MAC instructions?
JGonzo1299 said:
Yeah, I've read that when I was searching for a fix on my lunch break. My laptop is a MAC however. Which is why I didn't ODIN. I lost my Windows partition a while ago, along with my Windows CD.... Is there anyway I can get some MAC instructions?
Click to expand...
Click to collapse
Get heimdall 1.3.1 for mac os x here. There is 1.3.2 and 1.4.0-rc1, but don't use them, just use 1.3.1 for now!
Read the install instructions here.
After that, you should be able to do the oneclick on your mac.
Just replying to the OP... Still follow the instructions in my previous post.
JGonzo1299 said:
the phone doesn't boot now however. It loads into Samsung Recovery (3e) and gives the error:
--Applying Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/TMB/system/'
Successfully applied multi-CSC
Each time i try to 'reboot system now' it just loops back to recovery with the same error. On that link i listed above, it says to install bootloaders if that CSC issue exists. Problem is, each time i try, it says PIT failed and then it just disconnects and wont reboot, requiring me to reflash the package all-together.
Click to expand...
Click to collapse
The CSC error is just a red herring. Don't worry about that error. The one to worry about is not being able to flash the PIT!
JGonzo1299 said:
This phone was originally on 2.3.6 and the problem is I tried rooting using Vibrant instructions which was to go back to 2.1, then flash root, then CWM, then custom ROM.
Click to expand...
Click to collapse
Yea... Don't do that. Follow only instructions for the SGH-T959V, Galaxy S 4G. Do not ever, EVER, follow instructions for any other phone, unless you know exactly what you are doing.
JGonzo1299 said:
How do i get this phone working again. I can pick up where i left off as far as rooting and installing a custom ROM. I have experience with it... But I have no idea how to get this phone out of this soft-brick. Can anyone please assist me. I feel terrible for messing up my friends phone.
Thanks a bunch!
TL;DR - Soft bricked SGS4G by flashing Vibrant ROM, tried to correct using SuperOneClick heimdall, doesnt work. please help. Originally was completely stock.
Click to expand...
Click to collapse
Make sure you only follow instructions for the SGH-T959V, Galaxy S 4G! As I said above.
Either follow the instructions in my oneclick sticky thread, or follow lumin30's guide.
Make sure you try different usb cables. Make sure the ports on the computer and phone are clear of obstructions. Check in the cable connectors too. If all that still doesn't work, try a different computer. You could have bad usb ports. This has happened to me before, but it was a double whammy. I had bad usb ports on my computer and a bad usb cable.
bhundven said:
Get heimdall 1.3.1 for mac os x here. There is 1.3.2 and 1.4.0-rc1, but don't use them, just use 1.3.1 for now!
Read the install instructions here.
After that, you should be able to do the oneclick on your mac.
Click to expand...
Click to collapse
With that in mind, does anyone have a link to the most up to date Stock ROM not rooted. The Sticky Page has a dead link and the workaround link takes me to the OneClick ROM install that gave me the problem to begin with. I'd rather use the instructions to flash it myself and choose the file instead of doing the OneClick option. Does that make sense?
bhundven said:
Just replying to the OP... Still follow the instructions in my previous post.
The CSC error is just a red herring. Don't worry about that error. The one to worry about is not being able to flash the PIT!
Yea... Don't do that. Follow only instructions for the SGH-T959V, Galaxy S 4G. Do not ever, EVER, follow instructions for any other phone, unless you know exactly what you are doing.
Make sure you only follow instructions for the SGH-T959V, Galaxy S 4G! As I said above.
Either follow the instructions in my oneclick sticky thread, or follow lumin30's guide.
Make sure you try different usb cables. Make sure the ports on the computer and phone are clear of obstructions. Check in the cable connectors too. If all that still doesn't work, try a different computer. You could have bad usb ports. This has happened to me before, but it was a double whammy. I had bad usb ports on my computer and a bad usb cable.
Click to expand...
Click to collapse
Yeah i followed Vibrant instructions on accident. It was a careless mistake. Ill ignore the CSC error then and Ill try using a different USB port. My usb cable is brand new from my SIII. I don't think its a problem. But my mac USB ports are pretty old.
JGonzo1299 said:
With that in mind, does anyone have a link to the most up to date Stock ROM not rooted. The Sticky Page has a dead link and the workaround link takes me to the OneClick ROM install that gave me the problem to begin with. I'd rather use the instructions to flash it myself and choose the file instead of doing the OneClick option. Does that make sense?
Click to expand...
Click to collapse
Uhm, In the very first post of this thread, is this link. This is the totally back to stock oneclick.
I just downloaded it. Link works fine.
Yes, I realize you'd like to just run "heimdall" to flash everything, but it is so error prone.
The oneclick works for me on mac, linux, and windows. Again, if you have problems, list out each step you made and the results and we'll help
Just open a terminal, type:
Code:
java -jar T959VUVKJ6_STOCK-UVKJ6-One-Click.jar
and go...
bhundven said:
Uhm, In the very first post of this thread, is this link. This is the totally back to stock oneclick.
I just downloaded it. Link works fine.
Yes, I realize you'd like to just run "heimdall" to flash everything, but it is so error prone.
The oneclick works for me on mac, linux, and windows. Again, if you have problems, list out each step you made and the results and we'll help
Just open a terminal, type:
Code:
java -jar T959VUVKJ6_STOCK-UVKJ6-One-Click.jar
and go...
Click to expand...
Click to collapse
OK. I followed this. It DIDNT work. Ill list the steps i did.:
1) Redownloaded the one click listed above to ensure its not a corrupted download and verified
2)Placed file in my user folder (MAC Terminal defaults to this folder which is why i chose it)
3) Checked my Java version using Software update on MAC. Java was already up to date.
4)Opened Terminal
5) typed ls to confirm i was in the correct directory.
6) typed 'java -jar T959VUVKJ6_STOCK-UVKJ6-One-Click.jar'
7) Terminal began doing its thing.
8) I already have the Samsung Drivers. I've had Samsung Facinate and i currently have SIII so thats all up to date. Once i verified, i skipped the samsung drivers step.
9)I skipped the x86 step cause i know MAC has its own version of it already installed. My MAC version is 10.6.8
10) Connected phone to USB port, put in download mode.
11) Waited til phone was recognized with OneClick AND my MAC,
12) Ready to Flash
13) Clicked Flash
14) Flash successful, phone automatically powers down, reboots
15) Phone automatically loads into Android Recovery (3e) and gives error CSC mumbo jumbo i quoted in my first post
16) I needed bootloaders since I accidentally put Vibrant ROM. (per instructions from http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2 )
17) Removed Battery, Reconnected to MAC and placed in Download Mode
18) Clicked Flash Bootloaders, bypassed the warning, clicked Flash.
19) Uploading PIT, PIT upload failed!, Ending Session..., Rebooting Device...
20) Phone shuts off and never reboots, stays as a black screen, cant turn it on, load into recovery. I can ONLY load it into Download mode.
I followed these instructions as directed http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2 . Tried different USB cables and also tried BOTH USB ports. Please help. Thanks in advance.
JGonzo1299 said:
OK. I followed this. It DIDNT work. Ill list the steps i did.:
1) Redownloaded the one click listed above to ensure its not a corrupted download and verified
2)Placed file in my user folder (MAC Terminal defaults to this folder which is why i chose it)
3) Checked my Java version using Software update on MAC. Java was already up to date.
4)Opened Terminal
5) typed ls to confirm i was in the correct directory.
6) typed 'java -jar T959VUVKJ6_STOCK-UVKJ6-One-Click.jar'
7) Terminal began doing its thing.
8) I already have the Samsung Drivers. I've had Samsung Facinate and i currently have SIII so thats all up to date. Once i verified, i skipped the samsung drivers step.
9)I skipped the x86 step cause i know MAC has its own version of it already installed. My MAC version is 10.6.8
10) Connected phone to USB port, put in download mode.
11) Waited til phone was recognized with OneClick AND my MAC,
12) Ready to Flash
13) Clicked Flash
14) Flash successful, phone automatically powers down, reboots
15) Phone automatically loads into Android Recovery (3e) and gives error CSC mumbo jumbo i quoted in my first post
16) I needed bootloaders since I accidentally put Vibrant ROM. (per instructions from http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2 )
17) Removed Battery, Reconnected to MAC and placed in Download Mode
18) Clicked Flash Bootloaders, bypassed the warning, clicked Flash.
19) Uploading PIT, PIT upload failed!, Ending Session..., Rebooting Device...
20) Phone shuts off and never reboots, stays as a black screen, cant turn it on, load into recovery. I can ONLY load it into Download mode.
I followed these instructions as directed http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2 . Tried different USB cables and also tried BOTH USB ports. Please help. Thanks in advance.
Click to expand...
Click to collapse
Just double checking, This is t959v, not t959w... right? T959W has some issues with heimdall and odin that are still being worked out.
When i originally encountered the problem. I downloaded the 'back to Factory stock rom' for vibrant. It was an ODIN file so it was .tar, I downloaded its associated PIT file.
I loaded the PIT file into heimdall under the 'flash' tab
i extracted the .tar file and found 6 files. i took each file and loaded them individually to heimdall 1.3.1 under the 'flash' tab.
I had 6 files in there: cache, dbdata, factoryfs, modem, param, zImage.
Once I flashed those it wouldnt boot and was just black. could only go into download mode.
Then I realized i messed up and used the wrong ROM.
Came into this thread for SGS4G
Found the right files.
Phones been broken since and ive been following the instructions listed above. hope that makes sense. im at my work desk. sorry. Ill try to find the link of the go back to factory stock file i found on the vibrant forums but it was whatever vibrant came with out of the box. and it was a verified stock ROM. I just followed the instructions to the T until I encountered problems.....
bhundven said:
Just double checking, This is t959v, not t959w... right? T959W has some issues with heimdall and odin that are still being worked out.
Click to expand...
Click to collapse
Yes. I popped the battery out and im looking at the label in the back of the phone and it says SGH-959V.
JGonzo1299 said:
Yes. I popped the battery out and im looking at the label in the back of the phone and it says SGH-959V.
Click to expand...
Click to collapse
Ok, so it sounds like you need to try a different computer.
I know this is a pita, and I'm not trying to make things more difficult then they are, but as I said before. I've had this issue and had to buy a new computer. :crying:
Just thinking aloud, could try the kc1/kd1(froyo) firmware? Then move to gingerbread.
bhundven said:
Ok, so it sounds like you need to try a different computer.
I know this is a pita, and I'm not trying to make things more difficult then they are, but as I said before. I've had this issue and had to buy a new computer. :crying:
Click to expand...
Click to collapse
I'm going to try my friends PC. I'll try ODIN if I can find ODIN files, if not ill try heimdall instructions on a PC.
champ1919 said:
Just thinking aloud, could try the kc1/kd1(froyo) firmware? Then move to gingerbread.
Click to expand...
Click to collapse
Where do I find these? Can you post the link? I can probably try to flash this while im still at work for the next 2 hours lol
JGonzo1299 said:
I'm going to try my friends PC. I'll try ODIN if I can find ODIN files, if not ill try heimdall instructions on a PC.
Where do I find these? Can you post the link? I can probably try to flash this while im still at work for the next 2 hours lol
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=27374477
I think it's still a good link in that thread... I'm on my phone, I did try and something started.
JGonzo1299 said:
I had 6 files in there: cache, dbdata, factoryfs, modem, param, zImage.
Click to expand...
Click to collapse
So out of curiosity I just unpacked this Ravers KJ6 for Odin which was harder to find than I thought because Raver likes to spell offical instead of official. But I digress. The kicker here is that there are only 5 files.
cache.rfs
factoryfs.rfs
modem.bin
Sbl.bin
zImage
If I where the OP I'd DL that then unpack it. Reverse engineer what you did the first time by using the proper .tar through heimdall. If it worked once to totally hose you it just might work again to save you. Or it might not. Either way it's worth a shot. Good luck man.
hechoen said:
So out of curiosity I just unpacked this Ravers KJ6 for Odin which was harder to find than I thought because Raver likes to spell offical instead of official. But I digress. The kicker here is that there are only 5 files.
cache.rfs
factoryfs.rfs
modem.bin
Sbl.bin
zImage
If I where the OP I'd DL that then unpack it. Reverse engineer what you did the first time by using the proper .tar through heimdall. If it worked once to totally hose you it just might work again to save you. Or it might not. Either way it's worth a shot. Good luck man.
Click to expand...
Click to collapse
So you mean Download this and do exactly what I did that bricked the phone in the first place. but use these files instead. Cause these are for SGS4G. Correct?
I'll try that now. But dbdata is missing. Is that an issue? What is dbdata for anyway?
champ1919 said:
http://forum.xda-developers.com/showthread.php?p=27374477
I think it's still a good link in that thread... I'm on my phone, I did try and something started.
Click to expand...
Click to collapse
Thank you. I'm going to try this after I try what i just posted above first. Will post results later tonight around 11 EST. Work computer wont let me download any links.
JGonzo1299 said:
So you mean Download this and do exactly what I did that bricked the phone in the first place. but use these files instead. Cause these are for SGS4G. Correct?
I'll try that now. But dbdata is missing. Is that an issue? What is dbdata for anyway?
Click to expand...
Click to collapse
Yes that is what I mean.
I don't own a vibrant so I have know idea what dbdata is for. Maybe someone will chime in with a better answer. Doing it this way you should be able to get the phone back to where it was. Again this is my best guess at how to try to fix it. Plus it's really hard to brick a brick(bad joke I know but i had too).
Hi guys since today im a proud owner of a Galaxy Note 10.1 N8000 stock 4.1.2, but now comes the question, is it possible to Root it without flashing anything?
I only need root access to install a few apps, FolderMount, Titanium, Root explorer, etc.
I own too a Galaxy S2 that I rooted by the method of "rooting without flashing unsecure kernel" is it possible to apply the same method to the Note 10.1?
THANKS for any help given.
pedrohell said:
Hi guys since today im a proud owner of a Galaxy Note 10.1 N8000 stock 4.1.2, but now comes the question, is it possible to Root it without flashing anything?
I only need root access to install a few apps, FolderMount, Titanium, Root explorer, etc.
I own too a Galaxy S2 that I rooted by the method of "rooting without flashing unsecure kernel" is it possible to apply the same method to the Note 10.1?
THANKS for any help given.
Click to expand...
Click to collapse
Welcome to the club. Take a look at all the sections for the tablet and make sure you read the stickies too.
Method #2 and youl be good to go.
http://forum.xda-developers.com/showthread.php?t=1831152
I had already read that stickie and if I have correctly read, Method 2 (and the others) involves Odin and flashing something and that is what I dont want.
Isnt there a way to root without flashing?
pedrohell said:
I had already read that stickie and if I have correctly read, Method 2 (and the others) involves Odin and flashing something and that is what I dont want.
Isnt there a way to root without flashing?
Click to expand...
Click to collapse
Let me ask you this, why no flashing? As far as I know it's either Odin or flash. You need to get a custom recovery on it in order to root.
---------- Post added at 05:31 PM ---------- Previous post was at 05:30 PM ----------
Also with the s2 the recovery and kernel are in one. This is not.
Thanks for your help and time spent helping me, but I think I will pass the root on the Note, I thought there was a more easier/safe method like that on the S2.
Thanks
pedrohell said:
Thanks for your help and time spent helping me, but I think I will pass the root on the Note, I thought there was a more easier/safe method like that on the S2.
Thanks
Click to expand...
Click to collapse
No problem, but it don't get any easier than odin or recovery.
pedrohell said:
Thanks for your help and time spent helping me, but I think I will pass the root on the Note, I thought there was a more easier/safe method like that on the S2.
Thanks
Click to expand...
Click to collapse
There was an Exynos exploit method but Samsung patched the security hole a few updates ago.
The method in the link that was posted does alter your flash count and that can be correct but you are the owner of the device and if you are not comfortable flashing you tablet I wouldn't.
I have flashed mine and tried a few rom's but I always ended up resetting my flash counter and going back to stock.
Folder mount works great and that was the reason I rooted in the first place but you can store your files on the ext drive and transfer them back and forth manually but I found with my fast wifi I'm better off re-downloading the data along with "Helium - App Sync and Backup" to backup and restore my data and you do not need root, only draw back is that you have to have a computer connection for backup and restore to work.
.
Yes, its just a matter of not feeling confortable, and there is also the risk of blocking the camera. (had a similar issue with 4.1.2 on S2 needed to downgrade to 4.0.4).
But it seeems to me a bit odd that to grant root access we need to flash the rom.
I don't think you read that right. You're not flashing a ROM, just a custom recovery through ODIN, then a root app. It's actually very simple. (Any simpler and I would be concerned about rogue app exploits)
Fyi: I'm also new to Samsung devices and bought my tablet this week. Rooted it this morning by following the stickies, but sticking with the stock ROM for now. I'm more than happy with the tablet so far.
Sent from my GT-N8013 using xda app-developers app
pedrohell said:
Yes, its just a matter of not feeling confortable, and there is also the risk of blocking the camera. (had a similar issue with 4.1.2 on S2 needed to downgrade to 4.0.4).
But it seeems to me a bit odd that to grant root access we need to flash the rom.
Click to expand...
Click to collapse
There is no flashing a rom with method 2. You Odin the custom recovery then you have to flash the superuser into the system. You need superuser to get root and Odin is the easiest way.
Trust me we have all been in your shoes about being nervous, I've been doing this a long time and this method is really easy.
You can also use this method - http://forum.xda-developers.com/showthread.php?t=1957002
It does require ODIN but as has been stated this is the norm. You are not replacing any kernels or flashing another rom, you are just adding the root components. Using this method also leaves stock recovery intact...
If you woory about flash counter then run triangleaway after to reset the flash counter and recoveries....
I found doing this, doing a factory reset from settings then reflashing the Stock rom using Mobile ODIN pro gave me a stock standard, but rooted, rom with all statuses "Official" and 0 flash count....
A lot of work I know but then worthwhile things generally require it...
Ok, I followed the Method 2 made everything like on video, after pressing Power+Volume Up, I entered on STOCK Recovery, not the CWM,even so, I apply the .zip and I get:
MANUAL MODE
--Appling Multi-CSC....
Applied the CSC-code:LUX
Successfully applied multi-CSC.
--Install /sdcard....
Finding update package....
Opening update package....
Verifying update package.....
E:FAILED TO VERIFY WHOLE-FILE SIGNATURE
E:FAILED TO VERIFY WHOLE-FILE SIGNATURE
E:signature verification failed
I also retryed and turned off auto-reboot in Odin before starting the process but I get the same thing, now what should I do?
Its not rootable?
Ok, Its finally rooted, What I had to do,
On Odin unthick auto-reboot, When Odin finished doing its thing, dont shutdown the Tablet but press Power+Volume Up and go directly to CWM recovery and there follow the rest of instructions.
Thanks to everybody that took time to help me, thats why I love this forum.
A BIG THANK YOU.
pedrohell said:
I had already read that stickie and if I have correctly read, Method 2 (and the others) involves Odin and flashing something and that is what I dont want.
Isnt there a way to root without flashing?
Click to expand...
Click to collapse
I see that I'm probably too late now to answer the OP.
But maybe others can be interested.
I find that the easiest way to root (without odin and without installing a custom recovery) is Framaroot.
It uses some Exynos exploits, and has been also recently updated by the developer to counteract Samsung's patches.
It may work or it may not work on some devices and with some of the more recent firmware.
In any case giving it a try doesn't cost anything. It's just an app.
If it works the app can also be used to temporarily remove the root.
For me it worked with Firmware N8000XXCLL3 and I know that it works with some more recent fw too.
Furthermore it doesn't change the counter and even the Devices Status remains "Official". Well, actually the devices status may change to "Custom" after few days with the tablet on, but it returns Official after a simple reboot.
pedrohell said:
Ok, Its finally rooted, What I had to do,
On Odin unthick auto-reboot, When Odin finished doing its thing, dont shutdown the Tablet but press Power+Volume Up and go directly to CWM recovery and there follow the rest of instructions.
Thanks to everybody that took time to help me, thats why I love this forum.
A BIG THANK YOU.
Click to expand...
Click to collapse
Awesome to hear! I ran into the same thing you did, forgot to go straight to recovery from odin.
Enjoy!
Stuck
Please help..
I get this error when i try to install: View attachment 2066244
What did i do wrong ?
brix696 said:
Please help..
I get this error when i try to install: View attachment 2066244
What did i do wrong ?
Click to expand...
Click to collapse
I don't use CWM, but see if there is a signature seeing to turn it off. Also make sure your md5 of the zip is correct.
brix696 said:
Please help..
I get this error when i try to install: View attachment 2066244
What did i do wrong ?
Click to expand...
Click to collapse
What were your options on the page right before that? What option did you select to initiate that?
Maybe try using the files from here instead:
http://droidviews.com/2013/root-and...ung-galaxy-note-10-1-n8000-n8010-n8013-n8020/
bigtoysrock said:
I don't use CWM, but see if there is a signature seeing to turn it off. Also make sure your md5 of the zip is correct.
Click to expand...
Click to collapse
Where should i look for a signature ? I have downloaded the file 3 times, just to manke sure that i wasen't bad.
Before that, it was the page where i choose "apply update from external storage"
I have tryed the CF, still the same
brix696 said:
Where should i look for a signature ? I have downloaded the file 3 times, just to manke sure that i wasen't bad.
Before that, it was the page where i choose "apply update from external storage"
I have tryed the CF, still the same
Click to expand...
Click to collapse
I would use the touch cwm, and what rom are you trying to install?
I am hoping someone can help me because I have run out of ideas. I had Candy5 5.1.1 rom on my Tab2 10.1 and it was working for a while with intermittent reboots. Then it suddenly would reboot after just a few seconds. Nothing I have tried has worked, including:
1) a hard reset-I have tried wiping and resetting from CWM and from the settings but when I reboot it nothing is wiped or reset.
2) installing a new rom- I have tried installing multiple other roms from both the SD card, the internal sd card, and odin. They flash successfully but when I reboot I am right back to Candy5 and the reboot loop after a few seconds.
3) using odin-I have tried using oding to flash stock firmware, custom firmware, and a new recovery. Odin will say FAIL for the stock firmware, but for the others it will say PASS but there is still the same CWM and Candy5.
4) Sideloading- same results as above
5) installing a new recovery from SD card-nope.
6)Using ADB and fastboot-Fastboot will not recognize my device even though I have the correct drivers installed--I have also tried all the USB ports available with no change. ADB won't recognize my device for a wipe, but it will for installing another custom rom or recovery which of course does not work.
7) A few times I have had time before it reboots to try uninstalling apps. It tells me they are uninstalled but when I reboot they are back.
8) Also when it stayed I tried going into superuser settings to reset them but even though it says they are reset nothing happens after reboot.
A couple things to note:
1) it is a p5113 but has a p5110 rom and identifies itself as p5110 in download mode. This however, has not been a problem before.
2) I am running Clockworkmod Recovery v6.0.2.3
3)When I try to exit recovery I get the error message "Root access possibly lost. Fix?" and then the Yes response is "Yes-Fix root (/system/xbin/su). If I choose yes, though, it does nothing and simply reboots. Same if I choose no.
4) gapps are installed and I am certain I installed the correct version of these.
Thank you for any help you can give me. It's an old tablet but I have gotten a lot of great use from it until now!
Insight67 said:
I am hoping someone can help me because I have run out of ideas. I had Candy5 5.1.1 rom on my Tab2 10.1 and it was working for a while with intermittent reboots. Then it suddenly would reboot after just a few seconds. Nothing I have tried has worked, including:
1) a hard reset-I have tried wiping and resetting from CWM and from the settings but when I reboot it nothing is wiped or reset.
2) installing a new rom- I have tried installing multiple other roms from both the SD card, the internal sd card, and odin. They flash successfully but when I reboot I am right back to Candy5 and the reboot loop after a few seconds.
3) using odin-I have tried using oding to flash stock firmware, custom firmware, and a new recovery. Odin will say FAIL for the stock firmware, but for the others it will say PASS but there is still the same CWM and Candy5.
4) Sideloading- same results as above
5) installing a new recovery from SD card-nope.
6)Using ADB and fastboot-Fastboot will not recognize my device even though I have the correct drivers installed--I have also tried all the USB ports available with no change. ADB won't recognize my device for a wipe, but it will for installing another custom rom or recovery which of course does not work.
7) A few times I have had time before it reboots to try uninstalling apps. It tells me they are uninstalled but when I reboot they are back.
8) Also when it stayed I tried going into superuser settings to reset them but even though it says they are reset nothing happens after reboot.
A couple things to note:
1) it is a p5113 but has a p5110 rom and identifies itself as p5110 in download mode. This however, has not been a problem before.
2) I am running Clockworkmod Recovery v6.0.2.3
3)When I try to exit recovery I get the error message "Root access possibly lost. Fix?" and then the Yes response is "Yes-Fix root (/system/xbin/su). If I choose yes, though, it does nothing and simply reboots. Same if I choose no.
4) gapps are installed and I am certain I installed the correct version of these.
Thank you for any help you can give me. It's an old tablet but I have gotten a lot of great use from it until now!
Click to expand...
Click to collapse
Have you tried TWRP recovery from odin? use android-andi's or try from flashify app from your tab? I think you have done most of the things that needed to be done. the only thing left after this is try flash stock firmware with a pit file. but then if you have some other things as well to try.
it's not a regular bug, it's quiet strange, your candy rom tab looks like invincible here, or maybe the emmc has become read-only?(how on earth that happened??)
billysam said:
Have you tried TWRP recovery from odin? use android-andi's or try from flashify app from your tab? I think you have done most of the things that needed to be done. the only thing left after this is try flash stock firmware with a pit file. but then if you have some other things as well to try.
it's not a regular bug, it's quiet strange, your candy rom tab looks like invincible here, or maybe the emmc has become read-only?(how on earth that happened??)
Click to expand...
Click to collapse
Hi billysam, thanks for the response. I did try TWRP both as a zip install from the external sdcard and a sideload, as well as odin. They all tell me it was successfully installed but when I boot directly into recovery (if I did the auto reboot option I would go straight into the candy rom), I am back at CWM. I also tried the stock firmware with pit which fails during the factoryfs part.
I am not able to install any apps. If there is enough time before reboot, the app says it installed but when I reboot it is not there.
It does seem like the hard drive is read-only, or at least something is preventing me from writing to the disc.
Insight67 said:
Hi billysam, thanks for the response. I did try TWRP both as a zip install from the external sdcard and a sideload, as well as odin. They all tell me it was successfully installed but when I boot directly into recovery (if I did the auto reboot option I would go straight into the candy rom), I am back at CWM. I also tried the stock firmware with pit which fails during the factoryfs part.
I am not able to install any apps. If there is enough time before reboot, the app says it installed but when I reboot it is not there.
It does seem like the hard drive is read-only, or at least something is preventing me from writing to the disc.
Click to expand...
Click to collapse
Was the tab encrypted?
Can you get logs?
Well it's going to be a case study since I too can't find anything that could come close to your tab issue.
billysam said:
Was the tab encrypted?
Can you get logs?
Well it's going to be a case study since I too can't find anything that could come close to your tab issue.
Click to expand...
Click to collapse
It was not encrypted.
When I try to access the logs, this is what I get:
ClockworkMod Recovery v6.0.2.3
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
init.svc.ueventd=running
init.svc.recovery=running
service.adb.root=1
init.svc.adbd=running
I: Checking for extendedcommand...
I: Skipping execution of extendedcommand, file not found...
I Can't partition non-vfat: datamedia
I: Can't format unknown volume: /emmc
Thanks again!
When in recovery, flash twrp. Then reboot recovery. It should go to twrp then. I think your issue is recovery related.
Sent from my GT-P5110 using Tapatalk
Insight67 said:
It was not encrypted.
When I try to access the logs, this is what I get:
ClockworkMod Recovery v6.0.2.3
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
init.svc.ueventd=running
init.svc.recovery=running
service.adb.root=1
init.svc.adbd=running
I: Checking for extendedcommand...
I: Skipping execution of extendedcommand, file not found...
I Can't partition non-vfat: datamedia
I: Can't format unknown volume: /emmc
Thanks again!
Click to expand...
Click to collapse
Looks like a emmc issue my friend. I am afraid anything else going to work than replacing emmc.
The only reason I see here is that your tab emmc is somehow corrupted or there is bad sectors. That has virtually turned the tab into a read only and can't even read certain parts. No kind of flashing can do this to a tab. A virus attacked and is not letting you do it? Chances are no. Cause no virus can let you stop flashing from odin.
Correct Stock firmwares and pit file failed too at factoryfs part. sure you got the right files?
My suspect - the dreaded emmc issue of tab 10.1
Well do post if you find anything else.
Good luck
homephysician said:
When in recovery, flash twrp. Then reboot recovery. It should go to twrp then. I think your issue is recovery related.
Sent from my GT-P5110 using Tapatalk
Click to expand...
Click to collapse
Thank you for replying. I have tried that, but TWRP will not install. I am unable to install anything unfortunately.
billysam said:
Looks like a emmc issue my friend. I am afraid anything else going to work than replacing emmc.
The only reason I see here is that your tab emmc is somehow corrupted or there is bad sectors. That has virtually turned the tab into a read only and can't even read certain parts. No kind of flashing can do this to a tab. A virus attacked and is not letting you do it? Chances are no. Cause no virus can let you stop flashing from odin.
Correct Stock firmwares and pit file failed too at factoryfs part. sure you got the right files?
My suspect - the dreaded emmc issue of tab 10.1
Well do post if you find anything else.
Good luck
Click to expand...
Click to collapse
Yeah, I figures it might be that. It makes sense as to why I can't install anything and why fastboot won't recognize the device. My confusion was that my laptop does recognize it as at p5110 device and I can access the drive and it's folders on my laptop. I just can't delete anything. I don't know of any viruses and I had only a few select video streaming apps on it. I tried the p5110 and the p5113 from sam mobile so if you know of any other stock firmware links or toolkits I would love to try them. I hate to get rid of a tablet that isn't really bricked.
Insight67 said:
I hate to get rid of a tablet that isn't really bricked.
Click to expand...
Click to collapse
Same feeling goes here but wait, it does connect to your laptop and you can access files from it! You can transfer new files on it? And does it stay even after reboot?
Well I am looking for a new way out here, something that hasn't been tried on our devices to recover a tab from a difficult situation, a different approach. But will need help from our community. I will share that on a new thread once I am done researching myself. But sadly I have a P5100. But we will see what can be done.
billysam said:
Same feeling goes here but wait, it does connect to your laptop and you can access files from it! You can transfer new files on it? And does it stay even after reboot?
Well I am looking for a new way out here, something that hasn't been tried on our devices to recover a tab from a difficult situation, a different approach. But will need help from our community. I will share that on a new thread once I am done researching myself. But sadly I have a P5100. But we will see what can be done.
Click to expand...
Click to collapse
Well, it's a bit stranger than that. My laptop recognizes it as a p5110 and I can go into the files. I can even (if it doesn't immediately start rebooting) delete folders. But, when I reboot, the folders are back as if they were never deleted.
I was also able to sideload a rom onto my sdcard (not external sd) and it tells me install is complete. But nothing changes.
This is what I am getting when I install, which makes me think there is a piece of the factory firmware that is still around interfering with the custom rom:
Installing update....
Warning: No file_contextsdetected filesystem ext4 for /dev/block/platform/omap/omap)hsmmc.1/by-name/FACTORYFS
Then after the logo of the rom:
(*) Running backup scripts...
detected filesystem ext4 for /dev/block/platform/omap/omap)hsmmc.1/by-name/FACTORYFS
(*) Done.
Patching system image unconditionally...
detected filesystem ext4 for /dev/block/platform/omap/omap)hsmmc.1/by-name/FACTORYFS
unmount of /system failed: no such volume
script succeeded: result was [ ]
Install from sd card complete
Thank you again for your help. If I figure anything else out I will post as well in case anyone else has this issue.
Insight67 said:
Well, it's a bit stranger than that. My laptop recognizes it as a p5110 and I can go into the files. I can even (if it doesn't immediately start rebooting) delete folders. But, when I reboot, the folders are back as if they were never deleted.
I was also able to sideload a rom onto my sdcard (not external sd) and it tells me install is complete. But nothing changes.
This is what I am getting when I install, which makes me think there is a piece of the factory firmware that is still around interfering with the custom rom:
Installing update....
Warning: No file_contextsdetected filesystem ext4 for /dev/block/platform/omap/omap)hsmmc.1/by-name/FACTORYFS
Then after the logo of the rom:
(*) Running backup scripts...
detected filesystem ext4 for /dev/block/platform/omap/omap)hsmmc.1/by-name/FACTORYFS
(*) Done.
Patching system image unconditionally...
detected filesystem ext4 for /dev/block/platform/omap/omap)hsmmc.1/by-name/FACTORYFS
unmount of /system failed: no such volume
script succeeded: result was [ ]
Install from sd card complete
Thank you again for your help. If I figure anything else out I will post as well in case anyone else has this issue.
Click to expand...
Click to collapse
it's the same message that I get while installing a custom rom. but mine does write it on the system and it did change my rom.
Okay, we should concentrate on the firmware file that should flash through odin without fail.
why is it not flashing it, while others are getting flashed?
You did download it from sam mobile, that's the best place to get it.
pit file, is almost identical for all the p51xx 16gb variant, I was going through the same right now. so no chance of getting wrong pit partitioned. (by any chance, you ever flashed a different pit file on your tab?)
try to flash on a different pc/laptop? download stock firmware again, this is your best bet. any other options are just beating around bushes.
billysam said:
it's the same message that I get while installing a custom rom. but mine does write it on the system and it did change my rom.
Okay, we should concentrate on the firmware file that should flash through odin without fail.
why is it not flashing it, while others are getting flashed?
You did download it from sam mobile, that's the best place to get it.
pit file, is almost identical for all all the p51xx, I was going through the same right now. so no chance of getting wrong pit partitioned.
try to flash on a different pc/laptop? download stock firmware again, this is your best bet. any other options are just beating around bushes.
Click to expand...
Click to collapse
That is a good idea. I have been using the same laptop for all of this. I will try a different PC and let you know how it goes.
Thanks again!!
billysam said:
it's the same message that I get while installing a custom rom. but mine does write it on the system and it did change my rom.
Okay, we should concentrate on the firmware file that should flash through odin without fail.
why is it not flashing it, while others are getting flashed?
You did download it from sam mobile, that's the best place to get it.
pit file, is almost identical for all the p51xx 16gb variant, I was going through the same right now. so no chance of getting wrong pit partitioned. (by any chance, you ever flashed a different pit file on your tab?)
try to flash on a different pc/laptop? download stock firmware again, this is your best bet. any other options are just beating around bushes.
Click to expand...
Click to collapse
I tried a different computer but still got the fail from odin. If I come up with anything that works I'll be sure to post it. Thanks for all your help!
Just a shot in the dark, but did not see "Factory reset" mentioned.
Nobody wants to hear that but sometimes it's the only solution.
Pp.
PanchoPlanet said:
Just a shot in the dark, but did not see "Factory reset" mentioned.
Nobody wants to hear that but sometimes it's the only solution.
Pp.
Click to expand...
Click to collapse
Oh, yes, tried that numerous times. It won't reset. Thanks for the reply, though!
Insight67 said:
Oh, yes, tried that numerous times. It won't reset. Thanks for the reply, though!
Click to expand...
Click to collapse
http://wiki.cyanogenmod.org/w/EMMC_Bugs
Found it. That explains all.
billysam said:
http://wiki.cyanogenmod.org/w/EMMC_Bugs
Found it. That explains all.
Click to expand...
Click to collapse
Thanks billysam! If I am reading this correctly, only replacing the motherboard would work.
Insight67 said:
Thanks billysam! If I am reading this correctly, only replacing the motherboard would work.
Click to expand...
Click to collapse
Yes, according to that post. For me, I don't know because I haven't faced it myself, for you, you can try the options between changing emmc or changing motherboard or replacing a new tab or Jtag. Of course Whatever the technical guys you take your tab to for repair and which doesn't cost you much. Although people said changing emmc or jtag won't work. But you never know until tried. Also I won't suggest you try yourself. Good luck. It was good learning experience here.
billysam said:
Yes, according to that post. For me, I don't know because I haven't faced it myself, for you, you can try the options between changing emmc or changing motherboard or replacing a new tab or Jtag. Of course Whatever the technical guys you take your tab to for repair and which doesn't cost you much. Although people said changing emmc or jtag won't work. But you never know until tried. Also I won't suggest you try yourself. Good luck. It was good learning experience here.
Click to expand...
Click to collapse
Thank you!