Before flashing a custom rom on my new tab I decided to make a Roto Backup for myself and to share for anyone else with a Telstra tab who might need to go back to stock.
Please note this is not an official rom, for more information please see Roto's thread
http://forum.xda-developers.com/showthread.php?t=850359
I followed his instructions exactly, including generating the tar for flashing with Odin which is what I'm posting here.
I have a Desire but doing this sort of thing with Samsung devices is new to me, however I have successfully flashed this on my Tab with Odin, once saving me after trying to flash a bad download of the MCR kernel.
I factory reset beforehand so it's clean except for superuser & root Z4Root worked straight up on this so I imagine it should unroot just as easy.
If you have converted your filesystem then you will need to re-partition with Odin, I don't think this rom will work with ext4. I originally attached my backup pit but it doesn't seem to work, I've attached the pit from Roto-JME-Full-v4.
http://www.multiupload.com/KQF09AELMR
Tar MD5SUM - A75722008429EF469568E96F6F81F40A
Telstra modem.bin
http://www.multiupload.com/T04FXM8R5B
Bin MD5SUM - D1857CF262EFB929F73533C79D6B71AC
All thanks to rotohammer!
Thank you very much for your sharing!!!!
I'm using Galaxy Tab P-1000T Telstra, too.
Thank you - tucked away safely
thank you kind sir!
Many thanks for this - have used it several times now as I was too lazy to make an initial backup. Works just fine, and prerooted too!
Sent from my GT-P1000T using XDA Premium App
legand
I am on telstra also.
first of all, thank you.
my question here is how do i restore the stock firmware? i have a desire and restoring it to stock is just running the RUU provided but with GT, i'm clueless.
I was able to restore this with Odin happily. Just use it with the 'PDA' option.
BeauGiles said:
I was able to restore this with Odin happily. Just use it with the 'PDA' option.
Click to expand...
Click to collapse
Hi BeauGiles, will you be able to provide some simple instructions? what version of odin you are using? i found 2 version on the xda (odin3_1.70 and 1.31)
thank you.
I suggest having a look at the installation guide for the Overcome ROM, specifically the "Re-stocking" section as it has photos and things for Odin which makes it pretty clear. It's attached to the first post here
http://forum.xda-developers.com/showthread.php?t=932082
The process is basically the same, use the pit file and re-partition and select the telstra rom under PDA, you won't need to add the modem separately as it's already inside the telstra rom tar.
If any apps or settings carry over just do a factory reset.
Sarsippius said:
The process is basically the same, use the pit file and re-partition and select the telstra rom under PDA, you won't need to add the modem separately as it's already inside the telstra rom tar.
Click to expand...
Click to collapse
thank you.
Hi Sarsippius,
Thank you for the TELSTRA ROM.
I have a problem here, everytime i press the power button, my tab reboots, and also when the tab autolock. It also doesn't load the recovery mode when i press the power + up button(and then release the power button). Does anyone here having the same problem? Please share the solution.
Thank you again!
You hold the volume up button until the samsung logo appears, I personally hold it in until the recovery mode appears. Up to you...
Sarsippius said:
it's clean except for superuser & root
Click to expand...
Click to collapse
So how did you root it and how do I unroot it?
Only asking cause I suspect that not removing z4root is what baffed my official gingerbread update.
z4root is an app you can use to root certain Samsung devices, it worked on early Tab firmwares like those on the Telstra tab, it doesn't work on more recent firmwares but I haven't really looked at it lately.
Anyway, you open the app, hit the root button and it roots the tablet, it will also unroot although I never tested this. Give that a go otherwise do a search as there are instructions on this forum to manually unroot.
All good and sorry for the dumb question. was tired and late when I posted .
I assumed having z4root still kicking around when I let the official GB upgrade install was what was stopping me root using Doomlords method
Turns out samsungs use/abuse of the system directory was the issue and using the instructions later in the post Post 208sorted things out.
FYI: If anyone uses the above the code sample goes into the bat file after...
"@echo --- remounting /system
@files\adb shell "/data/local/tmp/busybox mount -o remount,rw /system"
do you think this would work on an australian optus tablet providing I change the modem to suit..?
I don't know of any reason why it wouldn't work but I'm not sure why you would want to do that.
ahh because i want the "stock" ROM so I can sell it.
I forgot to take a backup before I put Overcome then CM7 on it
senectus said:
do you think this would work on an australian optus tablet providing I change the modem to suit..?
Click to expand...
Click to collapse
Remembering that you'll have the stock Telstra bloat.. Er, apps on there such as Foxtel, BigPond, etc.
---
I am here: http://maps.google.com/maps?ll=-33.897667,151.175675
Related
Hi All,
Just curious how I would go about flashing a replacement bootloader to a Samsung Galaxy S?
I am trying to do this because my phone doesn't allow the 3 button boot mode into recovery or download mode.
I know you can activate it by running
adb reboot recovery
or
abd reboot download
However if I end up with a bad flash I will never be able to do that 3 button recovery so in essense I will brick my phone.
From the BML map
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S#Modifications
My guess is the bootloader I am looking for is at BML5
I have sucessfully backed up my BML5 from my 'neutered' phone and tonight will be backing up a BML5 from a phone which has 3 button mode active.
I backed them up using this command
dd if=/dev/block/bml5 of=/sdcard/bml5.bak
I will compare the two after this but am pretty confident they will be different. If they are different how can I go about copying a 3 button recovery mode bootloader to my device?
This post
http://forum.xda-developers.com/showpost.php?p=7610625&postcount=29
suggests there is a way to write to the bml however it is strongly discouraged.
Is there another way I can copy a non 'neutered' bootloader?
keep up the good work,
it'll be cool if you or anyone with that knowledge can get it working.
then we wont have to go back to the stores to exchange the Neutered phones
Odin?
Sent from my GT-I9000 using XDA App
it may be unwise to flash only the bml5. if the bml4 is different between the two phones, and references something in the bml5 that is also different, it may cause a brick state.
i would suggest backing up bml1-12 and comparing them. at the least bml4 and bml5 as they both deal with the secondary program loader, which should enable the 3button boot to recover if there is an error.
good work none the less
Odin doesn't work because one essential condition for Odin working is phone conected in download mode. Or, without phone in downloadmode Odin is no working.
Oef, difficult one. But what is the chance of having a bad flash by flashing a tar-ed Sbl.bin and/or boot.bin with Odin? Just wondering...
dentimarius said:
Odin doesn't work because one essential condition for Odin working is phone conected in download mode. Or, without phone in downloadmode Odin is no working.
Click to expand...
Click to collapse
Well you can get the phone into download mode by running
adb reboot download
so that isn't a problem... however I still am unsure how to flash it...
I suppose this would possibly work (in su)
dd if=/sdcard/bm5.bak of=/dev/block/bm5
but I am not game to run that until someone here with a bit more knowledge knows if it will work.
phoenixdigital said:
Hi All,
Just curious how I would go about flashing a replacement bootloader to a Samsung Galaxy S?
I am trying to do this because my phone doesn't allow the 3 button boot mode into recovery or download mode.
I know you can activate it by running
adb reboot recovery
or
abd reboot download
However if I end up with a bad flash I will never be able to do that 3 button recovery so in essense I will brick my phone.
From the BML map
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S#Modifications
My guess is the bootloader I am looking for is at BML5
I have sucessfully backed up my BML5 from my 'neutered' phone and tonight will be backing up a BML5 from a phone which has 3 button mode active.
I backed them up using this command
dd if=/dev/block/bml5 of=/sdcard/bml5.bak
I will compare the two after this but am pretty confident they will be different. If they are different how can I go about copying a 3 button recovery mode bootloader to my device?
This post
http://forum.xda-developers.com/showpost.php?p=7610625&postcount=29
suggests there is a way to write to the bml however it is strongly discouraged.
Is there another way I can copy a non 'neutered' bootloader?
Click to expand...
Click to collapse
I see that you are going in a very good hackable way ...
Contact @ Cotulla
phoenixdigital said:
Well you can get the phone into download mode by running
adb reboot download
so that isn't a problem... however I still am unsure how to flash it...
I suppose this would possibly work (in su)
dd if=/sdcard/bm5.bak of=/dev/block/bm5
but I am not game to run that until someone here with a bit more knowledge knows if it will work.
Click to expand...
Click to collapse
i would definitely recommend odin for that! did you try to flash a international firmware version like XWJM2 as it contains a bootloader that allows the 3 button goto download/recovery mode? you can use odin to just flash boot.bin and Spl.bin to just replace the 1st and 2nd bootloader...
what is your exact hardware version of the device? i think you have to be very careful when you want to replace the bootloader(s) to not brick your phone!!
jodue said:
i would definitely recommend odin for that!
Click to expand...
Click to collapse
how would I package up the backup via dd into something that odin would be able to use?
jodue said:
did you try to flash a international firmware version like XWJM2 as it contains a bootloader that allows the 3 button goto download/recovery mode? you can use odin to just flash boot.bin and Spl.bin to just replace the 1st and 2nd bootloader...
what is your exact hardware version of the device? i think you have to be very careful when you want to replace the bootloader(s) to not brick your phone!!
Click to expand...
Click to collapse
My device is
My phone specs
Model: GT-I9000
Firmware: 2.1-update1
Baseband: I9000DTJG3
Kernel: 2.6.29 [email protected] #2
Build Number: ECLAIR.DTJG4
Would that be suitable for the XWJM2?
Thanks for the response too.
Ok I have backed BML4 and BML5 for the following
1) My 'neutered' phone on DTJG4 - I will call this NEUT1
2) A 3 click working phone on DTJG3 - I will call this 3Click1
3) A 3 click working phone on DTJG4 - I will call this 3Click2
the BML5 backup from all of the phones just contains FFFFFFFFFF data and nothing else
BML4 is definitely different between NEUT1 and 3Click2
BML4 is the same for 3Click1 and 3Click2 so the JG4 update doesn't touch the bootloader...
Soooooooo.... How do I write this working BML4 to my NEUT1 device
Anyone? Bueller?
phoenixdigital said:
how would I package up the backup via dd into something that odin would be able to use?
My device is
My phone specs
Model: GT-I9000
Firmware: 2.1-update1
Baseband: I9000DTJG3
Kernel: 2.6.29 [email protected] #2
Build Number: ECLAIR.DTJG4
Would that be suitable for the XWJM2?
Thanks for the response too.
Click to expand...
Click to collapse
i think so but i am curious why your device doesn't allow the 3 button combo in the first place? is it provider bound? if yes, which one? i'm not sure if you can flash a open firmware onto a branded sgs but i think so! does anybody else has experience with that? btw. you can find boot.bin & Spl.bin in the pda archive of the firmwares but i wouldn't flash them before you can be sure it won't brick your sgs...
jodue said:
i think so but i am curious why your device doesn't allow the 3 button combo in the first place? is it provider bound? if yes, which one?
Click to expand...
Click to collapse
It is OPTUS Australia... in recent weeks there have been a few phones being released by Optus which have the 3 button click disabled. So it appears either Samsung or Optus are disabling it.
If someone else in Australia who has rooted their phone and knows a bit of unix can run this command from a terminal on their phone
su
dd if=/dev/block/bml4 of=/sdcard/bml4.bak
then post the bml4.bak file up somewhere I can compare it to the ones I have.
It doesn't even have to be australia anyone's would be good to compare.. just let me know what firmware you are running too.. and if the 3 click mode works for you.
jodue said:
i'm not sure if you can flash a open firmware onto a branded sgs but i think so! does anybody else has experience with that? btw. you can find boot.bin & Spl.bin in the pda archive of the firmwares but i wouldn't flash them before you can be sure it won't brick your sgs...
Click to expand...
Click to collapse
I have heard of people in Australia using these Eurpoean firmwares so I should be safe there.
I wont be flashing anything until we get some advice from some senior members of this forum. I am still thinking
dd if=/sdcard/bml4.bak of=/dev/block/bml4
should do the trick but I am too scared to run it
Ok I grew a pair and flashed JM5... It flashed successfully but the 3 button mode still doesn't work...
Hmmmmmm... so the 3 button mode isn't in boot.bin or Spl.bin???
I extracted bml4 and it has not changed at all?
phoenixdigital said:
Ok I grew a pair and flashed JM5... It flashed successfully but the 3 button mode still doesn't work...
Hmmmmmm... so the 3 button mode isn't in boot.bin or Spl.bin???
I extracted bml4 and it has not changed at all?
Click to expand...
Click to collapse
strange because it should be in the 1st bootloader ...
sorry for the stupid question but i haveto ask the obvious. are you sure pressing the 3 buttons doesn't work at all? it can be tricky and often it doesn't work so maybe you are just doing something wrong? have you tried holding home+voldown and then just press power once? this is all very strange! why forbid the key combination and still allow adb boot download? makes no sense to me!
jodue said:
sorry for the stupid question but i haveto ask the obvious. are you sure pressing the 3 buttons doesn't work at all?
This is all very strange! why forbid the key combination and still allow adb boot download? makes no sense to me!
Click to expand...
Click to collapse
Yep definitely pressing them right. I performed it perfectly on the non neutered phone just an hour ago and it worked perfectly.
phoenixdigital said:
Yep definitely pressing them right. I performed it perfectly on the non neutered phone just an hour ago and it worked perfectly.
Click to expand...
Click to collapse
have you tried re-extracting the bml4 from your neut1 phone and see if it is identical to the bml4 you extracted from the 3click phones? maybe it didn't flash correctly if at all?
phoenixdigital said:
Ok I grew a pair and flashed JM5... It flashed successfully but the 3 button mode still doesn't work...
Hmmmmmm... so the 3 button mode isn't in boot.bin or Spl.bin???
I extracted bml4 and it has not changed at all?
Click to expand...
Click to collapse
Here's a Quote from another thread:
mike.sw said:
Hey again
I'm looking the flash.bat and see it need two files that my firmware (I9000JPJG8) don't have in zip/tar file:
-boot boot.bin -sbl Sbl.bin
How heimdall will handle it? Is it safe to go on?
Click to expand...
Click to collapse
Seems like some firmwares out there don't contain the bootloader. Therefore, when you flash such a firmware, the bootloader section will remain unchanged even after flashing. Maybe you should check JM5 if it even contains the bootloader section in it or not.
wang1chung said:
have you tried re-extracting the bml4 from your neut1 phone and see if it is identical to the bml4 you extracted from the 3click phones? maybe it didn't flash correctly if at all?
Click to expand...
Click to collapse
I think that was the issue actually. When I flashed JM5 in odin I selected the
PIT
PDA
PHONE
CSA
I also ticked Re-Partition (Is this really needed if you are remaining on 512-PIT?)
When it rebooted the phone went through some terminal screens and appeared to give an error. Something to do with there being two CSC config files... can't remember the exact error. So it's possible it never got to the section where it replaced the bootloader...
It did however manage to update the firmware for PDA as the JM5 European firmware was definitely installed.
So a few questions about ODIN
Is it flashing the phone directly or just uploading the .bin and .rfs files to the phone?
If it's just uploading the .bin and .rfs files when the phone reboots after a flash does the phone then install/flash these .bin and.rfs files to the final location when it reboots after ODIN?
So in short is ODIN flashing or is the phone actually flashing after ODIN has uploaded the update files?
Do you really need to tick re-partition if you are staying on 512-PIT?
just a FYI
according to a post in the General forums, Samsung is aware of the problem, and might release the fix with their next official ROM
Hey guys, im new to the scene, and while fiddling around with my Galaxy S3, i have managed to brick it! Here is what happened.
I rooted the phone using a tutorial from here:
http://galaxys3root.com/galaxy-s3-r...gh-t999sgh-i747sph-l710-fail-proofnoob-proof/
Everything worked fine and the phone successfully rooted. But than i came across roms ... and i found a tutorial that told me how to install CyanogenMod 9:
http://forum.xda-developers.com/showthread.php?t=1778165
I tried to follow the instructions, but i would get (Error 7), and i realized that this tutorial instructed me to install the ClockworkMod Recovery version 5.8.4.7. So i downloaded the file from ClockworkMod's website, and it was in a .img format. When i had rooted my phone and installed ClockworkMod i used a .tar version via Odin, and this time i had a .img. After going through many tutorials, i found someone that showed how to install the .img varient via Android Terminal Emulator. So i followed the instructions:
http://forum.xda-developers.com/showthread.php?t=1363132
After i was finished following the instructions i rebooted the phone. And boom, it would not turn on. I tried all variants of holding the external buttons etc. Than i plugged the phone into a Windows PC. and the phone shows up in device manager as "QHSUSB DLOAD". So after tirelessly researching, i finally found the drivers for this and installed them. And know the phone shows up in Odin as COM10 in yellow. So i tried to flash the stock Image. I fire up Odin, select PDA, than the stock image, and click start. This is all that happens in the "Message Log":
<ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
(I have attached a screenshot of the above)
Please guys, i just got the phone and now it is bricked, any help would be greatly appreciated. Thanks!!
First download the correct version of Odin and drivers for s3's here ;
http://forum.xda-developers.com/showthread.php?t=1722686
Then download and flash the full stock rom from here;
http://forum.xda-developers.com/showthread.php?t=1752729
Hopefully that will get your phone to boot.
Then once you have reapplied the rooted system image download "rom manager" from the market and flash the updated recovery from there to avoid the error you encountered when attempting to flash cm9.
Good luck!
Hi, Thanks for your reply. I tried using a "Jig" and it did not put the S3 into download mode. LIke i said previously. When the S3 is connected to my PC it shows up as "QHSUSB DLOAD". And no Samsung drivers would work with it. I had to research and find the drivers that finally worked and allowed Odin v1.85 to see the phone as "COM10", and i select the ROM under the PDA and click the "Start" button. But than it does not go past SetupConnection. I thought maybe the "Jig" was faulty and didnt work, but i tested it with another working Samsung Galaxy S2, and it worked exactly as it was supposed to. Should i still try your suggestion or is it pointless?
neubauej said:
First download the correct version of Odin and drivers for s3's here ;
http://forum.xda-developers.com/showthread.php?t=1722686
Then download and flash the full stock rom from here;
http://forum.xda-developers.com/showthread.php?t=1752729
Hopefully that will get your phone to boot.
Then once you have reapplied the rooted system image download "rom manager" from the market and flash the updated recovery from there to avoid the error you encountered when attempting to flash cm9.
Good luck!
Click to expand...
Click to collapse
Ouch.
It sounds like your bootloaders might be borked, so kinda pointless.
I would get ahold of Josh at www.mobiletechvideos.com as it sounds like jtag might be required.
Hey, Thanks for the info. But the image i flashed via the Android mobile terminal app on the phone, i was flashing a ClockworkMod v5.4.8.1, that was made for the AT&T i747 (I have the Bell i747M, which i am told is the same thing?) , is that the bootloader? I know someone here that is local that does the jTag repair. But im not sure if the problem i have is in relation to the bootloader. Please let me know. As the phone still does show up when connected to the PC.
neubauej said:
Ouch.
It sounds like your bootloaders might be borked, so kinda pointless.
Get ahold of Josh at as it sounds like jtag might be required.
Click to expand...
Click to collapse
I tried your solution. The phone when connected to the PC with does not show up in Odin 3.07 (Correct version for my phone, from your link), But if i turn on Odin 1.85, the phone shows up fine in that as COM10 in yellow. So does my phone need a jTag? Samsung Canada told me to send the phone in for service and they will reset it and send it back. At the moment the phone does not turn on or go into download mode, and when connected to the computer it shows up as HS-USB QDLoader. So my question is: If i send it to Samsung, will they discover that i have Rooted it and void my warranty and not fix the phone?
neubauej said:
First download the correct version of Odin and drivers for s3's here ;
http://forum.xda-developers.com/showthread.php?t=1722686
Then download and flash the full stock rom from here;
http://forum.xda-developers.com/showthread.php?t=1752729
Hopefully that will get your phone to boot.
Then once you have reapplied the rooted system image download "rom manager" from the market and flash the updated recovery from there to avoid the error you encountered when attempting to flash cm9.
Good luck!
Click to expand...
Click to collapse
If you send it to Samsung its unlikely they will notice or care that its rooted.
I have sent them 2 devices that I wanted them to reflash after I did stupid things and hardbricked, fully expecting to pay for it, and it was returned to me flashed and at no charge. This was after I told the customer service rep that I was flashing custom firmware and i screwed it up.
YMMV.
The worst case scenario there is they void your warranty and charge you a minimal fee to reflash it.
As for your bootloaders, you pushed a custom recovery that failed, corrupted, or was an incorrect application. The recovery lies in the bootloader..
If it doesn't power up, won't go into download mode, and Odin won't flash it I'd say its jtag or send it to sammy time.
I see, well i do not care if they charge me anything. Money is not an issue, Ok well i just got the email from Samsung with the shipping label. Thanks for your information.
neubauej said:
If you send it to Samsung its unlikely they will notice or care that its rooted.
I have sent them 2 devices that I wanted them to reflash after I did stupid things and hardbricked, fully expecting to pay for it, and it was returned to me flashed and at no charge. This was after I told the customer service rep that I was flashing custom firmware and i screwed it up.
YMMV.
The worst case scenario there is they void your warranty and charge you a minimal fee to reflash it.
Click to expand...
Click to collapse
Goodluck!
Fyi 5.4.8.7 is the clockwork version I'm running.
After doing some more research, i found that another person with a different Samsung phone. Followed the same instructions to flash ClockworkMod via Android Mobile Terminal using the same instructions i did and got the same problem. On his post somebody told him that the flash was made to the wrong partition or something like that. So ... Lesson for next time. READ EVERYTHING BEFORE TRYING IT!
neubauej said:
Goodluck!
Fyi 5.4.8.7 is the clockwork version I'm running.
Click to expand...
Click to collapse
Yeah just go to Samsung. Its too bad u never read that the newer versions of CWM recovery don't work on the 747m. The 747 and our m variants are close but still a bit different in a few ways although when coming here for rooms and stuff we have to use this at&t 747. Section. There is a great rooting post under the development stickies and it mentions the UNICERSAL VERSION OF CWM RECOVERY FOR 747m phones and that is the one I used and all of us 747m users should install. 5.4.0.4 or something like that. Definitely not 5.8.x.x. I could have told u that would brick your phone and most proper posts would too. And unfortunately yes the recovery resides in the boot loader area so it can cause a brick.. so keep that in mind when u get your phone fixed. Either use the earlier cwm rec version or just change to TWRP RECOVERY which I just did and many recommend now anyways.
Good luck and I'll come back to post the link with the best root and cwm rec install forOUR 747M phones and remember there are some differences and not all 747 mods will work for us so please read up first
Sent from my SGH-I747M using xda premium
pchemerys said:
Yeah just go to Samsung. Its too bad u never read that the newer versions of CWM recovery don't work on the 747m. The 747 and our m variants are close but still a bit different in a few ways although when coming here for rooms and stuff we have to use this at&t 747. Section. There is a great rooting post under the development stickies and it mentions the UNICERSAL VERSION OF CWM RECOVERY FOR 747m phones and that is the one I used and all of us 747m users should install. 5.4.0.4 or something like that. Definitely not 5.8.x.x. I could have told u that would brick your phone and most proper posts would too. And unfortunately yes the recovery resides in the boot loader area so it can cause a brick.. so keep that in mind when u get your phone fixed. Either use the earlier cwm rec version or just change to TWRP RECOVERY which I just did and many recommend now anyways.
Good luck and I'll come back to post the link with the best root and cwm rec install forOUR 747M phones and remember there are some differences and not all 747 mods will work for us so please read up first
Sent from my SGH-I747M using xda premium
Click to expand...
Click to collapse
I don't think the version he used was the issue as other Canadian users report that 5.8.x.x works fine.
http://forum.xda-developers.com/showthread.php?p=29664739
Edit: the link with instructions for terminal emulator on the op is for the lg thrill which writes the recovery onto block 6. On this phone it needs to be written to block 18.
Sent from my HTC One S using xda app-developers app
Frowben said:
I don't think the version he used was the issue as other Canadian users report that 5.8.x.x works fine.
http://forum.xda-developers.com/showthread.php?p=29664739
Edit: the link with instructions for terminal emulator on the op is for the lg thrill which writes the recovery onto block 6. On this phone it needs to be written to block 18.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Ah yes..that makes sense. That would pooch the phone. As for cwm it appears I was mislead as I read on few posts that newest versions don't work or not recommended for Canadian variant but it appears u might be right and I'm now seeing more and more report that it is installable. I'll have to check it out. Thanks
You flashed a recovery for the LG Thrill 4G. At what point in time did you assume it was the same phone as the I747M? You have bricked your phone. It needs JTAG service. Samsung will probably cover it under warranty, or you can pay someone that has the equipment to do it. You have no other options at this point. When you get it back from repairs, make sure you only flash AT&T/Bell/Telus/Rogers I747(M) software to the phone....
Ya i got the phone back from Samsung after waiting 3 weeks. They had to change the motherboard on the phone. Yes, it was the wrong instructions i followed which screwed me over! Since than i re-rooted how i did the first time i got the phone. Just a few days ago i saw the new CyanogenMod 10 M1 Rom, which i wanted to install. And again like last time in order to install it i had to upgrade my CWM to the newest version. This time i did not rush into it like last time and consulted with my buddy who is an expert in Android. The problem i had last time was i downloaded the new CWM in an .img file, and this time i ended up finding the newest CWM in a .tar and used Odin to flash it successfully. Than i just installed the rom and was good to go. My main reason for wanting to install a custom rom was i was getting absolutely HORRIBLE battery life from my S3. I ended up buying a juice pack which greatly helped me out. But now that i have CM10 my battery life is phenomenal, + the juice pack i now go maybe 2 days without having to charge. Now my sister who has the Wind Mobile S3 T999V wants me to upgrade her rom to the same as mine. I have found the T-Mobile CWM for her phone, and all the relevant software, but i am still hesitant to install the CWM on her phone. The T-Mobile CWM 6.0.1.2 is compatible with the Wind Mobile S3 T999V right? Or do i have to use a different version?
just to be clear about where you went wrong (im sure its been said already)
the guide you followed to install cwm is from the lg thrill forum. so the command dd if=... of=... had the wrong device id which is the most common cause of a brick
its actually pretty difficult to mess up your phone as long as you don't use mods designed for other devices
jefferson9 said:
just to be clear about where you went wrong (im sure its been said already)
the guide you followed to install cwm is from the lg thrill forum. so the command dd if=... of=... had the wrong device id which is the most common cause of a brick
its actually pretty difficult to mess up your phone as long as you don't use mods designed for other devices
Click to expand...
Click to collapse
Yes, i know that. I realized after i had done everything that the instructions where for another phone. Now im trying to find the CWM 6.0.1.2 for my sister phone T-Mobile S3 T999V that is in a .tar file already. Any suggestions on where i can get it?
I use cwm 5.8 .0.4 i think and it works fine go to the dev stickies and its there
Sent from my SAMSUNG-SGH-I747 using xda premium
JB calhoun said:
I use cwm 5.8 .0.4 i think and it works fine go to the dev stickies and its there
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Ya for my sisters phone i have that version as a flashable tar, however to install CM 10 M1 i need to install CWM 6.0.1.2.
Did u try rom manager
Sent from my SAMSUNG-SGH-I747 using xda premium
Hello Everyone. First and foremost, thanks for all the helpful tips you guys have provided, been lurking here for a year or so.
Okay so heres the deal. I used skunkApes rooting method to root my phone last year. I just used the files included there and didn't do any custom roms or anything.
The last OTA update, didnt remove my root so after a few drinks and seeing that notification bar, i said why not. Well this one did. I checked SuperSU and it said no binary files found, must re-root. And my root checker says no root access. In developer menu, i dont see a tab for root to tick.
I tryed unistalling superSU, and that didnt work when i reinstalled. I can get to Download mode, but when I do recovery, it looks like its the stock android recovery.
Any help woul be much appreciated.
oh and sorry if this is in the wrong place, i wasnt sure if should had tagged this in teh "How to root" thread.
Phone infor- Spring G3, USA,
SPH-L710android version 4.3
Thanks
Use caution. If you aren't already aware, the 4.3 OTA update came with a sneaky bonus in the form of the KNOX bootloader. You're definitely going to want to familiarize yourself with it if you've got it because it looks like it's here to stay and it's got real potential for screwing you.
As for regaining root, all the resources you're likely to need are here: http://forum.xda-developers.com/showthread.php?t=2541900
I've been preaching that link all morning as my own personal Jesus Christ.
cwm
FallenZen said:
Use caution. If you aren't already aware, the 4.3 OTA update came with a sneaky bonus in the form of the KNOX bootloader. You're definitely going to want to familiarize yourself with it if you've got it because it looks like it's here to stay and it's got real potential for screwing you.
As for regaining root, all the resources you're likely to need are here: http://forum.xda-developers.com/showthread.php?t=2541900
I've been preaching that link all morning as my own personal Jesus Christ.
Click to expand...
Click to collapse
Hey Fallenzen, Thanks for the response, i see that you have been busy helping members this week!
Ok, so, when I try to go to recovery, Vol Up,menu and power, it looks like my clockwork recovery is gone and it shows the default one. No option to clear cache or make back up, just the android in surgery picture.
How do I get it back?
Thanks
Praz21 said:
Hey Fallenzen, Thanks for the response, i see that you have been busy helping members this week!
Ok, so, when I try to go to recovery, Vol Up,menu and power, it looks like my clockwork recovery is gone and it shows the default one. No option to clear cache or make back up, just the android in surgery picture.
How do I get it back?
Thanks
Click to expand...
Click to collapse
I've really just been trying to share what I learned from my recent update nightmare, I'm still just another noob. Anyhow, you should just be able to reflash CWM using ODIN. I am uncertain whether or not this will trip the KNOX warranty bit though (I don't know when I triggered mine since I wasn't even aware it existed until too late). If you haven't already triggered it, you might want to exercise patience and just keep reading what the devs are figuring out because once KNOX fires there's no going back, short of replacing the motherboard, at this time on account of the physical change it makes to your hardware.
I don't have a link handy, but I've been reading about Root De La Vega, which exploited a hash vulnerability to allow custom flashing without triggering KNOX. Samsung has patched the vulnerability, so it may or may not be an option for you but it's probably at least worth looking into.
FallenZen said:
I've really just been trying to share what I learned from my recent update nightmare, I'm still just another noob. Anyhow, you should just be able to reflash CWM using ODIN. I am uncertain whether or not this will trip the KNOX warranty bit though (I don't know when I triggered mine since I wasn't even aware it existed until too late). If you haven't already triggered it, you might want to exercise patience and just keep reading what the devs are figuring out because once KNOX fires there's no going back, short of replacing the motherboard, at this time on account of the physical change it makes to your hardware.
I don't have a link handy, but I've been reading about Root De La Vega, which exploited a hash vulnerability to allow custom flashing without triggering KNOX. Samsung has patched the vulnerability, so it may or may not be an option for you but it's probably at least worth looking into.
Click to expand...
Click to collapse
Custom recovery and custom ROMS will trip knox. If you have knox you can not flash backwards (back to 4.1.2 or lower than 4.3) because it will brick ur device. If ur not worried about tripping knox...iv got a note 3 and I tripped knox the first day I bought it...then by all means root and flash a custom recovery. If u haven't updated yet don't if you want the ROMS that are 4.1.2 or check out the 4.3 options in android development that left the knox bootloader out. If you choose to flash one of those that do not have the knox bootloader you can flash backwards. I'd suggest reading cnexus' "knox and you" in general. Lots of good info out here...keep reading and asking questions.
http://i.imgur.com/qrByUGN.jpg
same issue
I got the same issue here. Did not expect to lose root with the 4.3 OTA update, but I have! I got ODIN to flash CWM recovery and I got into recovery boot mode, and was able to install superuser. Once the phone booted up I got that bullS*it gray shield icon notice about "attempt to access secure area" (KNOX?) and now I cant get root access. WTF?! Please help, I need TrevEMod back in my life!
question
Since i am so new I cant post this reply in the following thread,
http://forum.xda-developers.com/showthread.php?t=2541900
but Ill ask here.
Will flashing this ROM work AFTER updated to 4.3 OTA with this KNOX already installed? I dont know, havent tried it yet?
onion root
bigpappags3 said:
Custom recovery and custom ROMS will trip knox. If you have knox you can not flash backwards (back to 4.1.2 or lower than 4.3) because it will brick ur device. If ur not worried about tripping knox...iv got a note 3 and I tripped knox the first day I bought it...then by all means root and flash a custom recovery. If u haven't updated yet don't if you want the ROMS that are 4.1.2 or check out the 4.3 options in android development that left the knox bootloader out. If you choose to flash one of those that do not have the knox bootloader you can flash backwards. I'd suggest reading cnexus' "knox and you" in general. Lots of good info out here...keep reading and asking questions.
Thanks for the info. Yea, my phone is already a year old so from what Ive read from that thread is that it just voids the warranty.
I guess i have to re-visit the rooting process. I just would like to get root back so I could use my wifi teather and bluput to control my ps3 again.
Any help is much appreciated.
Click to expand...
Click to collapse
Guessing I'm going to wait until a .tar file is released to flash custom recovery and root. I need a flawless phone and a lot of issues being reported in the use of cnex 4.3 rom release.
Sent from my SPH-L710 using xda app-developers app
SwellVermin said:
Since i am so new I cant post this reply in the following thread,
http://forum.xda-developers.com/showthread.php?t=2541900
but Ill ask here.
Will flashing this ROM work AFTER updated to 4.3 OTA with this KNOX already installed? I dont know, havent tried it yet?
Click to expand...
Click to collapse
Simple answer I believe is no. ... You have the knox bootloader. . That room will brick you device because ur trying to put an older bootloader on your phone.
http://i.imgur.com/qrByUGN.jpg
Got Root Back
But not all apps functioning. I used ChainFire's Auto Root method in ODIN to get root back, downloaded SuperSU from play store and used it to disable KNOX.
Now TrevEMod WifiTether not working. Help?
SwellVermin said:
But not all apps functioning. I used ChainFire's Auto Root method in ODIN to get root back, downloaded SuperSU from play store and used it to disable KNOX.
Now TrevEMod WifiTether not working. Help?
Click to expand...
Click to collapse
Out of curiosity is your SELinux status "Permissive" or "Enforcing"? Also, tethering is a known issue on 4.3 stock update, TrevEMod probably isn't going to work regardless. Is that the only app giving you problems?
We have a member who figured out a wireless tether fix on Android Forums, check out this link:
http://androidforums.com/virgin-mobile-galaxy-s3-all-things-root/800923-solved-mk5-4-3-stock-working-wireless-tether.html
It is for Virgin Mobile but should still work for Sprint or Boost for that matter since all three are SPH-L710.
SwellVermin said:
Since i am so new I cant post this reply in the following thread,
http://forum.xda-developers.com/showthread.php?t=2541900
but Ill ask here.
Will flashing this ROM work AFTER updated to 4.3 OTA with this KNOX already installed? I dont know, havent tried it yet?
Click to expand...
Click to collapse
That ROM worked for me after the OTA update to 4.3 screwed up my phone. I have the KNOX bootloader. I have tripped the Warranty Void bit, but since my phone is flashed from Sprint to Verizon I don't much care about that. My phone, with this ROM and the appropriate fixes (sprint hotspot, wifi, etc) works flawlessly. I have observed a bit of response lag on the lock screen, but it is not excessive and the lag is display-oriented as I can enter my lock code at full speed and it detects every touch just fine. I don't even notice it at this point.
Hope that helps.
Mr. Struck said:
Out of curiosity is your SELinux status "Permissive" or "Enforcing"?
Click to expand...
Click to collapse
What? lol Where is this setting found?
---------- Post added at 03:53 PM ---------- Previous post was at 03:41 PM ----------
FallenZen said:
That ROM worked for me after the OTA update to 4.3 screwed up my phone. I have the KNOX bootloader. I have tripped the Warranty Void bit, but since my phone is flashed from Sprint to Verizon I don't much care about that. My phone, with this ROM and the appropriate fixes (sprint hotspot, wifi, etc) works flawlessly. I have observed a bit of response lag on the lock screen, but it is not excessive and the lag is display-oriented as I can enter my lock code at full speed and it detects every touch just fine. I don't even notice it at this point.
Hope that helps.
Click to expand...
Click to collapse
But if this is the only way to get my wifi hot spot back, then I guess ill try it out. Theres a lot of steps to do to get this working correctly, huh? Im not that advanced and Im afraid Ill F something up!!
SwellVermin said:
What? lol Where is this setting found?
---------- Post added at 03:53 PM ---------- Previous post was at 03:41 PM ----------
But if this is the only way to get my wifi hot spot back, then I guess ill try it out. Theres a lot of steps to do to get this working correctly, huh? Im not that advanced and Im afraid Ill F something up!!
Click to expand...
Click to collapse
Well, here are my notes from my installation procedure. You can judge for yourself whether or not you're comfortable doing so, but be aware that this WILL trip your KNOX Warranty Void bit.
These notes were created for my own use in the event that I want to duplicate this procedure later since my pre-KNOX notes were rendered useless by the OTA update.
----------------------------------------
http://forum.xda-developers.com/showthread.php?t=2541900
Save all files to the phone's internal memory and remove microSD card.
Use ODIN3 to flash CWM-Recovery-LTE-SGS3-v5.tar.md5 to the phone with the PDA function.
Boot phone into the Recovery Console.
- Install SPHL710_MK3_rooted_odexed.zip
Use ODIN3 to flash CF-Auto-Root-d2spr-d2spr-sphl710.tar.md5 to the phone using the PDA function.
* Note, after this you might find you need to flash CWM Recovery to the phone again if the Android recovery console reappears.
From the CWM Recovery Console:
- Install Knox_APP_remover.zip
- Install wifi_fix_mk3.zip
- Install UPDATE-SuperSU-v1.80.zip
- (optional) Install MK3HotspotMod-odex.zip
- (optional) Install MK3_more_toggles.zip
Reboot the phone. If all goes well, it should load smooth as silk. Then all you need to do is execute the SuperSU app before attempting to operate any other apps that require root access and you should be golden.
----------------------------------------
It should be noted that I use ODIN 3.07 for this and am no longer on v1.85
Let me know if you need any clarification on the notes and I'll do my best.
Edit:
Also, do NOT use TriangleAway. I haven't tried it, but all of my reading suggests that it is a one way ticket to Bad News Blvd.
SwellVermin said:
What? lol Where is this setting found?
Click to expand...
Click to collapse
Settings/About Phone, scroll to the bottom. More of an issue for 4.4 than 4.3, as the default for 4.3 is Permissive and the default for 4.4 is Enforcing. In Enforcing mode it will sometimes block root-related apps, but it can manually be set to Permissive for 4.4 users.
FallenZen said:
Well, here are my notes from my installation procedure. You can judge for yourself whether or not you're comfortable doing so, but be aware that this WILL trip your KNOX Warranty Void bit.
These notes were created for my own use in the event that I want to duplicate this procedure later since my pre-KNOX notes were rendered useless by the OTA update.
----------------------------------------
http://forum.xda-developers.com/showthread.php?t=2541900
Save all files to the phone's internal memory and remove microSD card.
Use ODIN3 to flash CWM-Recovery-LTE-SGS3-v5.tar.md5 to the phone with the PDA function.
Boot phone into the Recovery Console.
- Install SPHL710_MK3_rooted_odexed.zip
Use ODIN3 to flash CF-Auto-Root-d2spr-d2spr-sphl710.tar.md5 to the phone using the PDA function.
* Note, after this you might find you need to flash CWM Recovery to the phone again if the Android recovery console reappears.
From the CWM Recovery Console:
- Install Knox_APP_remover.zip
- Install wifi_fix_mk3.zip
- Install UPDATE-SuperSU-v1.80.zip
- (optional) Install MK3HotspotMod-odex.zip
- (optional) Install MK3_more_toggles.zip
Reboot the phone. If all goes well, it should load smooth as silk. Then all you need to do is execute the SuperSU app before attempting to operate any other apps that require root access and you should be golden.
----------------------------------------
It should be noted that I use ODIN 3.07 for this and am no longer on v1.85
Let me know if you need any clarification on the notes and I'll do my best.
Edit:
Also, do NOT use TriangleAway. I haven't tried it, but all of my reading suggests that it is a one way ticket to Bad News Blvd.
Click to expand...
Click to collapse
Ok, tried to do the first step here. This is what ODIN says when I try to load the CWM-Recovery-LTE-SGS3-v*.tar.md5 file.
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> CWM-Recovery-LTE-SGS3-v5.tar.md5 is invalid.
<OSM> End...
Not sure what to do here. Please let me know what you think?
I just tried to boot into recovery mode and of course it's the stock android recovery. Bah!
SwellVermin said:
Ok, tried to do the first step here. This is what ODIN says when I try to load the CWM-Recovery-LTE-SGS3-v*.tar.md5 file.
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> CWM-Recovery-LTE-SGS3-v5.tar.md5 is invalid.
<OSM> End...
Not sure what to do here. Please let me know what you think?
I just tried to boot into recovery mode and of course it's the stock android recovery. Bah!
Click to expand...
Click to collapse
I'm not sure, but the first thing I'd suggest is to try redownloading the file. Possibly from another source. Sounds like a bad download. If it continues to be a problem, I'll compile the exact files from my computer and make 'em accessible on my dropbox or something so you can try to use them... But that shouldn't be necessary. Also, remember that you want to flash the file via ODIN using the PDA option and make sure that both Auto Reboot and F. Reset Time are checked but that nothing else is.
yeah I tried that
FallenZen said:
I'm not sure, but the first thing I'd suggest is to try redownloading the file. Possibly from another source. Sounds like a bad download. If it continues to be a problem, I'll compile the exact files from my computer and make 'em accessible on my dropbox or something so you can try to use them... But that shouldn't be necessary. Also, remember that you want to flash the file via ODIN using the PDA option and make sure that both Auto Reboot and F. Reset Time are checked but that nothing else is.
Click to expand...
Click to collapse
I downloaded from 3 different sources, all the same result when loading the file into ODIN via PDA function. Hmph! Is it because I am on a stock recovery and ROM?
SwellVermin said:
I downloaded from 3 different sources, all the same result when loading the file into ODIN via PDA function. Hmph! Is it because I am on a stock recovery and ROM?
Click to expand...
Click to collapse
Shouldn't be... I'm also on a stock recovery and ROM. What version of ODIN are you using?
Does anyone have a stock firmware of their S6 Edge T-Moible? that's ODIN flashable. I bricked my S6 trying to root it and had the KNOX security on. Now it just boot loop. :crying:
Protomize said:
Does anyone have a stock firmware of their S6 Edge T-Moible? that's ODIN flashable. I bricked my S6 trying to root it and had the KNOX security on. Now it just boot loop. :crying:
Click to expand...
Click to collapse
hey you're not alone! a lot of people are in your situation right now including me. we have to wait until there is a firmware available on Sammobile. hang tight.
samanbabah said:
hey you're not alone! a lot of people are in your situation right now including me. we have to wait until there is a firmware available on Sammobile. hang tight.
Click to expand...
Click to collapse
I managed to find a solution. Go here: http://forum.xda-developers.com/tmo...ow-to-brick-s6-s6-edge-knox-security-t3075720
Protomize said:
I managed to find a solution. Go here: http://forum.xda-developers.com/tmo...ow-to-brick-s6-s6-edge-knox-security-t3075720
Click to expand...
Click to collapse
That doesn't fix issues for those of us that need to have the full stock firmware to re-Odin with. Guess those of us in the same boat wait a week or so. My problem was removing the knox files with root explorer. Bad move. Makes the phone unbootable. Called Samsung tech support and they confirmed that. Rooting no problem. Recovery screen totally blank. Never get to see the the white/green screen some say they have for a recovery screen. The magic use volume up keys 7 times etc I have seen posted don't work for me. Samsung specifically told me the stock firmware is proprietary, so they wouldn't give it to me. I can wait a week or so for developers to get their hands on appropriate files, including a custom recovery that actually works...like good old TWRP :victory:
Protomize said:
Does anyone have a stock firmware of their S6 Edge T-Moible? that's ODIN flashable. I bricked my S6 trying to root it and had the KNOX security on. Now it just boot loop. :crying:
Click to expand...
Click to collapse
have you tried to flash the S6 file? not the S6 edge but the S6. Try to get yourself in download mode and do that. Make sure you are using the correct odin. That is what happened to me and I was able to obtain ROOT.
If you can get into download mode, you can now use Kies to install the stock firmware. Just did it about 3 mins ago.
SuperSport said:
If you can get into download mode, you can now use Kies to install the stock firmware. Just did it about 3 mins ago.
Click to expand...
Click to collapse
Where did you get the stock firmware. I'm not talking rooting file. I'm talking the full on tar to use to ODIN and flash the complete full stock firmware.
Docmjldds said:
Where did you get the stock firmware. I'm not talking rooting file. I'm talking the full on tar to use to ODIN and flash the complete full stock firmware.
Click to expand...
Click to collapse
I used Kies to restore the Firmware. Unfortunately, I was unable to find the Firmware file on my computer (Or could not figure out how to use it). I did see a temp file that was the correct size, but it's name and extension were wrong. I tried to open the file using 7-Zip and WinRar, but neither would open it. At that point, I just allowed Kies to do it's job, and it worked well. Removed ROOT and am now running Stock Firmware and Stock Recovery. KNOX is still tripped, but I don't care at this point.
In Kies, use the option: "Firmware Upgrade and Initialization". You will need your Model Name and Serial Number. Found on the box or in Settings if you can get there. I've got a T-Mobile Edge, so my Model Name is SM-G925T. Your serial will be unique.
SuperSport said:
I used Kies to restore the Firmware. Unfortunately, I was unable to find the Firmware file on my computer (Or could not figure out how to use it). I did see a temp file that was the correct size, but it's name and extension were wrong. I tried to open the file using 7-Zip and WinRar, but neither would open it. At that point, I just allowed Kies to do it's job, and it worked well. Removed ROOT and am now running Stock Firmware and Stock Recovery. KNOX is still tripped, but I don't care at this point.
In Kies, use the option: "Firmware Upgrade and Initialization". You will need your Model Name and Serial Number. Found on the box or in Settings if you can get there. I've got a T-Mobile Edge, so my Model Name is SM-G925T. Your serial will be unique.
Click to expand...
Click to collapse
I deleted via root explorer a slew of knox fies. Samsung told me by doing this, it renders the phone non bootable. That is why I need a full stock firmware tar file I can use in Odin, to flash the original complete firmware for my 925 Edge.Removing root, re-rooting, will not help. Chainfire said that SamMobile rleased the firmware files but all I get is web page not available. Grrrrr. Really wish someone would post the file in the Development sections or at least provide a working link.
Docmjldds said:
I deleted via root explorer a slew of knox fies. Samsung told me by doing this, it renders the phone non bootable. That is why I need a full stock firmware tar file I can use in Odin, to flash the original complete firmware for my 925 Edge.Removing root, re-rooting, will not help. Chainfire said that SamMobile rleased the firmware files but all I get is web page not available. Grrrrr. Really wish someone would post the file in the Development sections or at least provide a working link.
Click to expand...
Click to collapse
I had also removed all of the KNOX files, and most of the Samsung Files trying to get close to AOSP, but it became unstable. Kies re-installed the COMPLETE firmware again and all the stock files returned. I don't mean it removed ROOT only, it flashed the complete firmware. Kies uses ODIN internally to do the flash.
SuperSport said:
I had also removed all of the KNOX files, and most of the Samsung Files trying to get close to AOSP, but it became unstable. Kies re-installed the COMPLETE firmware again and all the stock files returned. I don't mean it removed ROOT only, it flashed the complete firmware. Kies uses ODIN internally to do the flash.
Click to expand...
Click to collapse
it's weird I can't use Kies at all.
samanbabah said:
it's weird I can't use Kies at all.
Click to expand...
Click to collapse
I can't use Kies either. Says phone not supported. I get the same exact error message. Oh my life savings for a nice .tar file to odin with
Wait
I think you should wait until pushed ODIN firmware over web...
dreamytricks said:
I think you should wait until pushed ODIN firmware over web...
Click to expand...
Click to collapse
Well, someone (Pagel) already posted the 920 stock tar file in the S6 thread. so there MUST be a source currently. Wish I knew why Sammobile web site returns errors for me about unable to open web page. That's the source most state is where to go.
Docmjldds said:
I can't use Kies either. Says phone not supported. I get the same exact error message. Oh my life savings for a nice .tar file to odin with
Click to expand...
Click to collapse
Okay I was able to find a workaround on how to restore my phone through Kies without getting an error.
do the following: 1) open Kies, click on tools, Firmware upgrade and initialisation, enter your model number and serial number and let it download the firmware, after an hour or so depending on your connection speed the firmware will be downloaded and your phone will reboot into recovery to install the firmware. done
samanbabah said:
Okay I was able to find a workaround on how to restore my phone through Kies without getting an error.
do the following: 1) open Kies, click on tools, Firmware upgrade and initialisation, enter your model number and serial number and let it download the firmware, after an hour or so depending on your connection speed the firmware will be downloaded and your phone will reboot into recovery to install the firmware. done
Click to expand...
Click to collapse
That's exactly what I was saying to do a few posts back. Did it yesterday and it worked fine.
EDIT: I'm going to run through it again and see if I can find the downloaded file. I believe I found it last time, but it was not a TAR file, rather a temp file specific to MY phone. But I'll try again, and if I get it, will post it here.
SuperSport said:
That's exactly what I was saying to do a few posts back. Did it yesterday and it worked fine.
EDIT: I'm going to run through it again and see if I can find the downloaded file. I believe I found it last time, but it was not a TAR file, rather a temp file specific to MY phone. But I'll try again, and if I get it, will post it here.
Click to expand...
Click to collapse
oh OK I didn't see your previews post.
samanbabah said:
oh OK I didn't see your previews post.
Click to expand...
Click to collapse
No problem, as long as we all get there at some point. The temp file that Kies downloads is called tmpE635.tmp It ends up being about 1.6GB in size. I tried to open it using 7-Zip and WinRar, but neither will open it. I'll post it in case anyone wants to try using it in ODIN. I don't know if it is specific to MY phone, or the T-Mobile S6 Edge in general (SM-G295T).
But, honestly, I would suggest you use Kies yourself so you are positive to get the correct file. You WILL get the error message that says Kies does not support your phone, just ignore that and keep going.
Phone Serial Number
I just realized that the Serial Number Kies is asking for is not on my Box. It's in the settings/about/status menu, and also on a sticker that is stuck to the Plastic Wrap that was around the phone in the box. Looks sort of like this: R58G31D1PBA. So, if you cannot get into your settings, or don't have that plastic, I'm not positive how you will get it to start the download. Maybe if you just use someone elses serial number, that will start the download???
EDIT: Link to the Temp File from Kies (not sure you'll be able to do anything with it)
https://mega.co.nz/#!39gwRAKS!H81yfo1vCQkMOujTaQJaU2INXoPNtUF6cgnF46jAfXI
WTF
Had the download stall on me twice, 35 and 47 percent.
WHATS THIS?
This is my port of CF-AUTOROOT for the Samsung Galaxy TAB E.
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE or a TWRP backup in case of problems. This will trip the knox counter.
Flash with ODIN 3.10.7 in the AP slot.
Load the respective file below into the AP slot and hit start.
cfautoroot_sm-t377p.tar
cfautoroot_sm-t560nu.tar
NOTE: ON SOME 5.1.1 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
STOCK TWRP IMAGE FOR SM-T377P
This is a link to the stock system, boot, modem image for the T377P in case anyone needs it. Needs to be restored with twrp.
Thanks to @shawn1976 for providing this.
https://www.dropbox.com/s/skuwsbzm2zigd83/sm-T377PVPU1AOJ5-boot-system-modem-only.zip?dl=0
Credits: Chainfire and my testers - Phrozen99 and nates730
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
FRP lock
Any suggestions on getting pass an FRP lock? My niece tried to root it but didn't turn on the enable OEM unlock. I just literally got it so don't have a back up and stock rom is no where I can find online even tried the Samsung Switch software and the T377P is not an option.
Jasn7766 said:
Any suggestions on getting pass an FRP lock? My niece tried to root it but didn't turn on the enable OEM unlock. I just literally got it so don't have a back up and stock rom is no where I can find online even tried the Samsung Switch software and the T377P is not an option.
Click to expand...
Click to collapse
Isn't there a recovery mode in the SS software that allows the firmware to be reflashed?
ashyx said:
Isn't there a recovery mode in the SS software that allows the firmware to be reflashed?
Click to expand...
Click to collapse
That was my plan ...however they do not support this model number yet so its not available to be reflashed. I checked sammobile as well figuring I could download firmware and use Odin to reflash and same situation.
There's a chance the sm-t377R4 firmware may flash as it's practically identical to the sprint firmware just a different csc.
Okay....will try and find that one.
Hi, I had a question. The Samsung Tab E is my first android device (I am a IOS user, so i know how to Jailbreak, but I don't know how to root!). My friend told me to root it, but I don't really know how to do it. Can you post a step by step tutorial. Also, after i rooted can i update my device to a newer version or do i have to remove the root. Lastly, how do you back up your device? Thank you! I appreciate your hard work!
Badob said:
Hi, I had a question. The Samsung Tab E is my first android device (I am a IOS user, so i know how to Jailbreak, but I don't know how to root!). My friend told me to root it, but I don't really know how to do it. Can you post a step by step tutorial. Also, after i rooted can i update my device to a newer version or do i have to remove the root. Lastly, how do you back up your device? Thank you! I appreciate your hard work!
Click to expand...
Click to collapse
You can follow the tutorial below, it's for the Tab A but the procedure is identical.
Obviously don't use the cf_autoroot file in the tutorial use the one here. Also note the PDA button in Odin is now called AP.
http://techchomps.com/how-to-root-the-samsung-galaxy-tab-a-9-7/
ashyx said:
You can follow the tutorial below, it's for the Tab A but the procedure is identical.
Obviously don't use the cf_autoroot file in the tutorial use the one here. Also note the PDA button in Odin is now called AP.
Click to expand...
Click to collapse
Thanks Man!!! Had some last questions: Can i update my device to a newer version (if available) or do i have to remove the root and how do you back up your device? Thank you again!
Badob said:
Thanks Man!!! Had some last questions: Can i update my device to a newer version (if available) or do i have to remove the root and how do you back up your device? Thank you again!
Click to expand...
Click to collapse
You can update your device with odin anytime you want but not via ota.
To back up you device you need to install TWRP.
Search Google for info on using TWRP.
ashyx said:
You can update your device with odin anytime you want but not via ota.
To back up you device you need to install TWRP.
Search Google for info on using TWRP.
Click to expand...
Click to collapse
Thanks For the help!
Where do I get TWRP for Tab E T560, and how do I install it?
Thank you.
Edit: Found the answer.
ashyx said:
There's a chance the sm-t377R4 firmware may flash as it's practically identical to the sprint firmware just a different csc.
Click to expand...
Click to collapse
I tried the t377R4 firmware that didn't work. Any idea on where I could track down a copy of the t377p? Odd I can't even use the Samsung Smart Switch or even Kies as it doesn't recognize the model number. Or if anyone has a backup available they can share please let me know.
I have a US Cellular Samsung Tab E SM-T377R4 and I rooted it using the procedure below. The root process went fine and everything is working well except Recovery Mode does not work. It just boots to a black blank screen when I try to go to Recovery Mode. But that's no big deal to me.
ashyx said:
You can follow the tutorial below, it's for the Tab A but the procedure is identical.
Obviously don't use the cf_autoroot file in the tutorial use the one here. Also note the PDA button in Odin is now called AP.
http://techchomps.com/how-to-root-the-samsung-galaxy-tab-a-9-7/
Click to expand...
Click to collapse
Stevenwsmith said:
I have a US Cellular Samsung Tab E SM-T377R4 and I rooted it using the procedure below. The root process went fine and everything is working well except Recovery Mode does not work. It just boots to a black blank screen when I try to go to Recovery Mode. But that's no big deal to me.
Click to expand...
Click to collapse
Surprised recovery doesn't work, considering the 2 devices are identical specs.
Try installing Twrp, you'll probably find that works OK.
Jasn7766 said:
I tried the t377R4 firmware that didn't work. Any idea on where I could track down a copy of the t377p? Odd I can't even use the Samsung Smart Switch or even Kies as it doesn't recognize the model number. Or if anyone has a backup available they can share please let me know.
Click to expand...
Click to collapse
Same problem here... I've been looking all over for a copy of the SM-T377P stock ROM. Anyone that happens to have a copy/link for it please share.
JohnICon said:
Same problem here... I've been looking all over for a copy of the SM-T377P stock ROM. Anyone that happens to have a copy/link for it please share.
Click to expand...
Click to collapse
What's the issue?
Rooting gone bad... Rooted my SM-T377P with KingRoot and there is an FRP Lock that comes up a week later. All of the custom ROM versions I have keep getting rejected by ODIN every time I try to flash them. The only other way I can think of doing this is to flash the stock ROM for the device.
JohnICon said:
Rooting gone bad... Rooted my SM-T377P with KingRoot and there is an FRP Lock that comes up a week later. All of the custom ROM versions I have keep getting rejected by ODIN every time I try to flash them. The only other way I can think of doing this is to flash the stock ROM for the device.
Click to expand...
Click to collapse
You realise you can't flash a custom rom with odin?
Also when you flash the stock t377r4 firmware what part fails?
The aboot fails every time I try to flash it