Related
yea i tried to change recovery from a basic cwm to twrp from zip my phone isnt working and i have ubuntu it act up and how do i fix it re put cwm on my phone to work again i think its soft brick
it wont work just show the logo goes funny and does nothing please help if it nessary i use a windows but help please will thanks
Yes I looked it up I have asemi bricked my phone I was in cwm installed twrp zip and rebooted it went then loaded weird boot but loaded normal and then restarted stucked on the main logo gt n7100 and goes weird and thats it I have linux ubuntu 13.10 byt reinstall a recovery then be fine I dont want a unroot just reinstall cwm
Sent from my GT-N5110 using xda app-developers app
Can you be more specific? Using punctuation marks could make it a lot more understandable.
Also: Please post it in the questions section of the forum, the development section is for roms and mods.
@gtasmodder, try re-installing CWM from Odin again. Will fix your problem. ALSO post in Q/A forum.
Oh, and it is scared, not sacred.
You need to reflash using ODIN on a windows machine.
Go to this link - it has the instructions on how to flash CWM.
After you have got your phone back up and running you need to update it to the latest version, easiest way is to boot into your ROM, go to Play store and install ROM Manager. Now simply select to update CWM.
Search this forum for Dr.Ketan threads if you need to Root/Install Stock etc.
phlooke said:
You need to reflash using ODIN on a windows machine.
Go to this link - it has the instructions on how to flash CWM.
After you have got your phone back up and running you need to update it to the latest version, easiest way is to boot into your ROM, go to Play store and install ROM Manager. Now simply select to update CWM.
Search this forum for Dr.Ketan threads if you need to Root/Install Stock etc.
Click to expand...
Click to collapse
its stuck on the gt n7100 logo of Samsung but getting better
gtasmodder said:
its stuck on the gt n7100 logo of Samsung but getting better
Click to expand...
Click to collapse
I was in this position yesterday after a failed DN3 ROM flash.
If you follow these instructions you will be back up and running in no time:...
- Like I mentioned, flash CWM.
- Flash a stock ROM
- Root - either CF or use Dr.Ketan multitool method (search is your friend)
- Install ROM Manager, update CWM to latest
- Install <your chosen ROM> - in my case I am running CM11
Follow the above and you'll be sorted.
phlooke said:
I was in this position yesterday after a failed DN3 ROM flash.
If you follow these instructions you will be back up and running in no time:...
- Like I mentioned, flash CWM.
- Flash a stock ROM
- Root - either CF or use Dr.Ketan multitool method (search is your friend)
- Install ROM Manager, update CWM to latest
- Install <your chosen ROM> - in my case I am running CM11
Follow the above and you'll be sorted.
Click to expand...
Click to collapse
can you send a link im lost
gtasmodder said:
can you send a link im lost
Click to expand...
Click to collapse
Link to what?
Take your time, search and READ
phlooke said:
Link to what?
Take your time, search and READ
Click to expand...
Click to collapse
lots of dead ends as soon it was so post to be complete an error
gtasmodder said:
lots of dead ends as soon it was so post to be complete an error
Click to expand...
Click to collapse
I'm not sure if English is you're first language (I sincerely hope not!) so I dont really understand what you have asked there ^
My point is you need to search on this forum.
There are plenty of live threads regarding stock ROM, rooting, flashing with ODIN etc. etc.
From the front page of Android Development forum:
http://forum.xda-developers.com/showthread.php?t=1923956
...search & read.
It seems that when I connect my phone to odin a com port opens. When I put my phone into recovery mode the com port does not open so odin does not see my phone. Yes I do have the phone in debug mode. Samsung drivers are in.
BigNoobee said:
It seems that when I connect my phone to odin a com port opens. When I put my phone into recovery mode the com port does not open so odin does not see my phone. Yes I do have the phone in debug mode. Samsung drivers are in.
Click to expand...
Click to collapse
Odin is used in download mode. Are you trying to use it in recovery mode?
Larry2999 said:
Odin is used in download mode. Are you trying to use it in recovery mode?
Click to expand...
Click to collapse
Trying to root the phone. Doesn't the phone need to be in recovery mode to root it?
BigNoobee said:
Trying to root the phone. Doesn't the phone need to be in recovery mode to root it?
Click to expand...
Click to collapse
Depending on your phone model and what method you are trying to use to root, you may need to flash SuperSU via recovery. This process does not, however, start in recovery. It starts with flashing custom recovery via Odin and then manually booting to recovery to flash the SuperSU zip. To flash a custom recovery via Odin, you would need to boot into download mode. There are other methods, of course, to root that do not require either download or recovery modes. What's the model of your phone and what firmware version are you on?
Have you tried flashing a pre-rooted ROM? You have an i747 or i747m?
Larry2999 said:
Depending on your phone model and what method you are trying to use to root, you may need to flash SuperSU via recovery. This process does not, however, start in recovery. It starts with flashing custom recovery via Odin and then manually booting to recovery to flash the SuperSU zip. To flash a custom recovery via Odin, you would need to boot into download mode. There are other methods, of course, to root that do not require either download or recovery modes. What's the model of your phone and what firmware version are you on?
Click to expand...
Click to collapse
The phone is a SGH-I747M ver. 4.3
I tried rooting based on a number of videos as to easily follow the process.
audit13 said:
Have you tried flashing a pre-rooted ROM? You have an i747 or i747m?
Click to expand...
Click to collapse
I have a i747m, The situation is that odin only opens the com port when the phone is in operating mode.
BigNoobee said:
It seems that when I connect my phone to odin a com port opens. When I put my phone into recovery mode the com port does not open so odin does not see my phone. Yes I do have the phone in debug mode. Samsung drivers are in.
Click to expand...
Click to collapse
I should have stated my goal. My goal is to put kitkat on my phone. After talking to my provider (petro mobility) on the Rogers network no upgrades are going to be provided and at the very least I need an s4 or better s5 to run kitkat. Also this information I was given is NOT official but only the opinion of an employee"s personal opinion, having worked for the company for some time. The phone is not supported in any way by petro mobility but is only running on the Rogers network. If any upgrades are made it will be by Rogers. Rogers will not say anything because I am not a Rogers customer.
To flash a Kit Kat ROM, you need to have a custom recovery installed on your phone.
You can load Philz Touch via Odin.You can flash the latest tar Philz d2lte from here: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte
Boot into download mode, put the Philz tar file in the PDA section of Odin, check nothing except auto reboot and F.Reset Time.
Boot into recovery mode and you will see that Phil has replaced the stock recovery.
You can copy a custom rom to your external micro SD card and flash it.
If you just want a rooted stock ROM, look here: http://forum.xda-developers.com/sho...tmctr=(not provided)&__utmv=-&__utmk=34317218
Warning: doing all of these things can soft or hard brick your phone. Make sure you read and understand everything before proceeding. The method I described worked my i747m with 4.1.2 and another i747m with 4.3. I cannot guarantee it will work for you.
audit13 said:
To flash a Kit Kat ROM, you need to have a custom recovery installed on your phone.
You can load Philz Touch via Odin.You can flash the latest tar Philz d2lte from here: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte
Boot into download mode, put the Philz tar file in the PDA section of Odin, check nothing except auto reboot and F.Reset Time.
Boot into recovery mode and you will see that Phil has replaced the stock recovery.
You can copy a custom rom to your external micro SD card and flash it.
If you just want a rooted stock ROM, look here: http://forum.xda-developers.com/sho...tmctr=(not provided)&__utmv=-&__utmk=34317218
Warning: doing all of these things can soft or hard brick your phone. Make sure you read and understand everything before proceeding. The method I described worked my i747m with 4.1.2 and another i747m with 4.3. I cannot guarantee it will work for you.
Click to expand...
Click to collapse
GREAT !!!! GREAT !!!:laugh: Sorry for Yelling It worked for me ThanX
My next step is to go get Rom Manager from the app store...watching their video now on Rom Manager.. Very high learning curve for me- hope I don't brick the phone ....
BigNoobee said:
GREAT !!!! GREAT !!!:laugh: Sorry for Yelling It worked for me ThanX
My next step is to go get Rom Manager from the app store...watching their video now on Rom Manager.. Very high learning curve for me- hope I don't brick the phone ....
Click to expand...
Click to collapse
Now you have custom recovery, you can flash a Kit-Kat based custom ROM. There is, of course, a difference between a Kit-Kat based custom ROM and official Kit-Kat 4.4. We have information and I'm sure they are reliable enough, that Kit-Kat 4.4 will be rolled out for Samsung GS III and all its variants including the i747U/M. The expectation has, however, been on for some time and no one really knows when and if. If you are using a custom ROM, you will not be able to get OTA updates for official firmware if the official version is rolled out but manual updates will still be possible, thanks to the development community.
BigNoobee said:
GREAT !!!! GREAT !!!:laugh: Sorry for Yelling It worked for me ThanX
My next step is to go get Rom Manager from the app store...watching their video now on Rom Manager.. Very high learning curve for me- hope I don't brick the phone ....
Click to expand...
Click to collapse
I don't personally use ROM Manager as I find it redundant. Now that you have Philz which can flash pretty much any KK ROM, you can just stick with using Philz to flash.
I like the Validus ROM on the i747m. I find it works well and has great battery life and performance.
BTW, you do not need to root in order to flash a custom ROM.
It's been a long bloody time since I fiddled around with stuff on this phone. So I'm still on a rooted 4.1.2.
My questions are is it worth the upgrade to KitKat? And if so, what's the easiest way for me to do so? Hopefully retaining root, but not too necessary.
Help would be appreciated. For dummies.
Hey there.
I've gone through the process myself recently. Here is what you should do :
1. Download a custom rom from the Android Development forum. For example I downloaded the DN3 v5.2, but whatever catches your eye is fine.
2. Just follow the instructions the rom' s topic states.
3. If you have trouble getting to the recovery mode, you should flash with Odin some custom recovery. I like the cwm recovery.
4. Most guides provide info how to root your phone but if not then there is a topic in the Android Development forum about it.
I suggest backing up everything you can before- copy the phone contents to your pc, run the efs professional program to backup your efs.
Cheers
Rizaria said:
It's been a long bloody time since I fiddled around with stuff on this phone. So I'm still on a rooted 4.1.2.
My questions are is it worth the upgrade to KitKat? And if so, what's the easiest way for me to do so? Hopefully retaining root, but not too necessary.
Help would be appreciated. For dummies.
Click to expand...
Click to collapse
Hi there. I'm using n7100. N7105 is not far different to n7100. I've recently upgraded my phone from 4.3 to 4.4. I can't see a big difference from the 2 version except 4.4 consumes more battery than 4.3. I think you should consider 4.3 first before going straight to 4.4.
Just to inform you. What I know is...4.3 and 4.4 Official Rom already have Knox. So maybe you should read about them first. And Flashing Custom Recovery like PhilzTouchRecovery may trigger your Knox and increase your Binary Counter. And you may loose your warranty.
Flashing and rooting stock ROM is easy. But you have to do it right. What I did:
1. Download Odin
2. Download Samsung USB Drivers
3 Download 4.4 Firmware for my phone at sammobile.com
4. Install Samsung USB Driver
5. Run Odin
6. Put phone in Download Mode. Check if Odin successfully detected my phone
7. Once success, load the firmware to PDA Tab/Button. Don't touch anything
8. Press start. Wait till done. Wait till your phone reboot on it's own.
9. Once rebooted, check "About Device".
10. Done!
11. Download PhilzTouchRecovery 6.26
12. Put device into Download Mode again.
13. Run Odin again
14. Connect device again
15. Load PhilzTouchRecovery.tar.md5 to PDA Tab/Button
16. Uncheck Auto Reboot from Odin
17. Click start. Once Pass! Disconnect device.
18. Hold Power Button, DON'T RELEASE till you boot into your new recovery.
19. Once booted to PhilzRecovery, select reboot system now, but make sure not to overwrite with stock recovery or else you're PhilzRecovery will be reverted back to your stock recovery and you have to flash again your PhilzRecovery.
20. Once successfully flashed PhilzRecovery. Make all necessary backups (Full backup) you can't make EFS/MODEM backup yet because your not yet Rooted. You just installed Custom Recovery.
21. Once fully backed up. Copy backup files to your PC.
22. If you want to root again. Use CF-ROOT on 4.4.2 or use Dr.Ketan's Multi-Tool-Advance-V6 in 4.3. And follow their instructions.
Good Luck. HTH.
PoOoZaQ said:
Hey there.
I've gone through the process myself recently. Here is what you should do :
1. Download a custom rom from the Android Development forum. For example I downloaded the DN3 v5.2, but whatever catches your eye is fine.
2. Just follow the instructions the rom' s topic states.
3. If you have trouble getting to the recovery mode, you should flash with Odin some custom recovery. I like the cwm recovery.
4. Most guides provide info how to root your phone but if not then there is a topic in the Android Development forum about it.
I suggest backing up everything you can before- copy the phone contents to your pc, run the efs professional program to backup your efs.
Cheers
Click to expand...
Click to collapse
Thanks for that. Still wondering which one I should try all this Knox stuff is puzzling. Seems a lot of things have happened since I last had a fiddle.
asin_punk said:
Hi there. I'm using n7100. N7105 is not far different to n7100. I've recently upgraded my phone from 4.3 to 4.4. I can't see a big difference from the 2 version except 4.4 consumes more battery than 4.3. I think you should consider 4.3 first before going straight to 4.4.
Just to inform you. What I know is...4.3 and 4.4 Official Rom already have Knox. So maybe you should read about them first. And Flashing Custom Recovery like PhilzTouchRecovery may trigger your Knox and increase your Binary Counter. And you may loose your warranty.
Flashing and rooting stock ROM is easy. But you have to do it right. What I did:
1. Download Odin
2. Download Samsung USB Drivers
3 Download 4.4 Firmware for my phone at sammobile.com
4. Install Samsung USB Driver
5. Run Odin
6. Put phone in Download Mode. Check if Odin successfully detected my phone
7. Once success, load the firmware to PDA Tab/Button. Don't touch anything
8. Press start. Wait till done. Wait till your phone reboot on it's own.
9. Once rebooted, check "About Device".
10. Done!
11. Download PhilzTouchRecovery 6.26
12. Put device into Download Mode again.
13. Run Odin again
14. Connect device again
15. Load PhilzTouchRecovery.tar.md5 to PDA Tab/Button
16. Uncheck Auto Reboot from Odin
17. Click start. Once Pass! Disconnect device.
18. Hold Power Button, DON'T RELEASE till you boot into your new recovery.
19. Once booted to PhilzRecovery, select reboot system now, but make sure not to overwrite with stock recovery or else you're PhilzRecovery will be reverted back to your stock recovery and you have to flash again your PhilzRecovery.
20. Once successfully flashed PhilzRecovery. Make all necessary backups (Full backup) you can't make EFS/MODEM backup yet because your not yet Rooted. You just installed Custom Recovery.
21. Once fully backed up. Copy backup files to your PC.
22. If you want to root again. Use CF-ROOT on 4.4.2 or use Dr.Ketan's Multi-Tool-Advance-V6 in 4.3. And follow their instructions.
Good Luck. HTH.
Click to expand...
Click to collapse
Very concise steps, cheers for that. Might give all that a try. Just need a safe rom. Not sure what. Is there anything else that needs flashing, like modem files or anything?
Thanks for both your comments.
Only the rom is necessary. Shouldn't flash modem and kernel etc unless something doesn't work.
All the roms published in xda are fine and safe. I just went for the topic with the most views.
If you want you can also download stock 4.3 from www.sammobile.com
Just choose your device and you get a file flashable with odin. About 1.9 giga download.
Rizaria said:
Thanks for that. Still wondering which one I should try all this Knox stuff is puzzling. Seems a lot of things have happened since I last had a fiddle.
Very concise steps, cheers for that. Might give all that a try. Just need a safe rom. Not sure what. Is there anything else that needs flashing, like modem files or anything?
Thanks for both your comments.
Click to expand...
Click to collapse
Your current Bootloader doesn't have Knox. So you better search for a 4.3 or 4.4 rom that doesn't flash new bootloader. I think i saw it somewhere in the development.If I were not mistaken, it should be flashed thru custom recovery. Coz it's a zip file.
All I know is all rom files from sammobile.com includes new kernel, bootloader and modem. So if you flash this roms from sammobile, you will have a new kernel, bootloader and modem. It's all up to you. If I were you, I'll stay away from Knox. So find a rom that supports your current bootloader. Maybe a custom one.
Maybe this will help...
http://forum.xda-developers.com/showthread.php?t=2747963
asin_punk said:
Your current Bootloader doesn't have Knox. So you better search for a 4.3 or 4.4 rom that doesn't flash new bootloader. I think i saw it somewhere in the development.If I were not mistaken, it should be flashed thru custom recovery. Coz it's a zip file.
All I know is all rom files from sammobile.com includes new kernel, bootloader and modem. So if you flash this roms from sammobile, you will have a new kernel, bootloader and modem. It's all up to you. If I were you, I'll stay away from Knox. So find a rom that supports your current bootloader. Maybe a custom one.
Maybe this will help...
http://forum.xda-developers.com/showthread.php?t=2747963
Click to expand...
Click to collapse
Fair enough, thanks.
If I try the one below, think that'd work out alright? And which to use, deoxed or not?
http://forum.xda-developers.com/showthread.php?t=2588787
Sent from my GT-N7105 using XDA Free mobile app
Rizaria said:
Fair enough, thanks.
If I try the one below, think that'd work out alright? And which to use, deoxed or not?
http://forum.xda-developers.com/showthread.php?t=2588787
Sent from my GT-N7105 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah nice find... It should work fine... you're on the 3rd status "For those are on the 4.1.2 bootloader the rom could work normally with AGNi Kernel include in rom". I think you should go for DEODEXED for more customization and etc. Read here: http://codeversed.com/deodexed-vs-odexed-rom/.
Make sure to follow instruction precisely and strictly. And make sure to copy your Backup to your PC right after you created it. Coz if you do a Full Wipe, Reset and Clean Install, it will also delete the backup that you made. Read the instructions multiple times carefully to avoid mislead. Once you done it successfully, you will be on Custom Rom and Custom Kernel. Sounds very techie. Hahaha. Good Luck!
asin_punk said:
Yeah nice find... It should work fine... you're on the 3rd status "For those are on the 4.1.2 bootloader the rom could work normally with AGNi Kernel include in rom". I think you should go for DEODEXED for more customization and etc. Read here: http://codeversed.com/deodexed-vs-odexed-rom/.
Make sure to follow instruction precisely and strictly. And make sure to copy your Backup to your PC right after you created it. Coz if you do a Full Wipe, Reset and Clean Install, it will also delete the backup that you made. Read the instructions multiple times carefully to avoid mislead. Once you done it successfully, you will be on Custom Rom and Custom Kernel. Sounds very techie. Hahaha. Good Luck!
Click to expand...
Click to collapse
Thanks for the advice.
Really, I wanted to upgrade to Android L but then I saw it wasn't out yet so I was like...huh, KitKat time?
I'm not even sure if it'll be any better than what I have! Mostly just want something with better battery life. Even though I just bought a new battery that lets me use my phone for 3 days and a half hour. I have noticed that Screen/Android seem to be bleeding power a lot more these days, so figured it might be worth a wipe and an upgrade.
In any case, whenever I do, I have some handy guides now. Cheers~
Hello, I used to be rooted with custom ROMs ect but went back to stock I317ATTALJ2 so I can give the phone to my daughter. Well everything went smooth until an update from AT&T came through and she ran it when the battery was at 21% but I'm not sure it that matter but didn't help in matters... Anyhow it ran the upgrade and on reboot it stayed on the Galaxy Note II screen and wont do anything but sit there. I let it sit for a long time before pulling the battery and booting but it goes to same screen and same thing. I can not get into recovery (Volume Up, Home, Pwr) but I can go into download mode. With the battery being so low I read that it charges while in download mode so for the remainder of the day I put the phone in download mode and plugged into charger.
Suggestions?
After you get it charged up some and you're in download mode. Just Odin back to stock Att firmware should fix the problem hopefully...
You can find the stock firmware here>> http://bit.ly/1HNVFVJ
Guess the phone didn't like that update ?.
Bajanman said:
After you get it charged up some and you're in download mode. Just Odin back to stock Att firmware should fix the problem hopefully...
You can find the stock firmware here>> http://bit.ly/1HNVFVJ
Guess the phone didn't like that update .
Click to expand...
Click to collapse
Ok, Ill give the stock firmware (At&t Firmware I317UCALJ2 Uploaded By-Bajanman) that Bajanman supplys ill let you guys know in an hour or two its downloading now. I did try re installing the stock firmware I had that worked the first time and it was from SamMobile and it too sent me to the Galaxy Note II screen and froze so its not looking good.....
Thanks!
Oxicottin said:
Ok, Ill give the stock firmware (At&t Firmware I317UCALJ2 Uploaded By-Bajanman) that Bajanman supplys ill let you guys know in an hour or two its downloading now. I did try re installing the stock firmware I had that worked the first time and it was from SamMobile and it too sent me to the Galaxy Note II screen and froze so its not looking good.....
Thanks!
Click to expand...
Click to collapse
Ok.
Hopefully everything works out next time around.
Another thing you could try is flashing which ever recovery you previously had installed. Last time I was having issues with something similar, after re flashing my recovery everything started working again. Just just a thought that might work.
I'm monitoring this thread too see what happens ok.
Bajanman said:
Ok.
Hopefully everything works out next time around.
Another thing you could try is flashing which ever recovery you previously had installed. Last time I was having issues with something similar, after re flashing my recovery everything started working again. Just just a thought that might work.
I'm monitoring this thread too see what happens ok.
Click to expand...
Click to collapse
Recovery? can I flash the stock recovery using ODIN? If so where do I get it.... I always have used TWRP I wanted to use custom ROMs never really experimented with anything else.
Oxicottin said:
Recovery? can I flash the stock recovery using ODIN? If so where do I get it.... I always have used TWRP I wanted to use custom ROMs never really experimented with anything else.
Click to expand...
Click to collapse
Yes you can flash a custom recovery from Odin. You just have to use the (Twrp) tar file found here>>>
http://bit.ly/1y0Tyg7
Find your device model and download the tar. And make sure you're downloading the correct file for your device ok!
I to use Twrp and luv it.?
OK, well its not looking good....
1) Flashed the stock firmware suggested...... Still get same results!
2) Flashed TWRP through ODIN and it made it to the same screen and froze. Did a battery pull and button combo and it wont go into recovery.
Is there a application that will force your phone into recovery and download modes? I remember back when I messed with the captivate there was a application someone built that did such a thing.
Any suggestions?
Oxicottin said:
OK, well its not looking good....
1) Flashed the stock firmware suggested...... Still get same results!
2) Flashed TWRP through ODIN and it made it to the same screen and froze. Did a battery pull and button combo and it wont go into recovery.
Is there a application that will force your phone into recovery and download modes? I remember back when I messed with the captivate there was a application someone built that did such a thing.
Any suggestions?
Click to expand...
Click to collapse
Not sure you were on the newer 4.4.2 bootloader or not. If it was on a newer bootloader then you won't be able to downgrade.. This might help you get the phone working again since you just flashed the original firmware.
Go to this thread here>>http://forum.xda-developers.com/showthread.php?t=2502464.
Download
4.3 Param.bin and Tz.img
http://d-h.st/OYC
Step 2 (no bootloader in here)
flash this to bring wifi back
but keep your knox free 4.1.2 bootloader.
Allowing you to freely flash between 4.1.2 roms and the latest 4.3 leak
Without having to one click,Keeping Wifi Throughout and removing Knox
Click to expand...
Click to collapse
Unzip, Boot into Download mode, Open ODIN, put tar file in PDS slot, click Start.
Then you can go here for the latest stock Att firmware. If the above steps don't help you, then you could try flashing one one the rooted stock packages from this thread.
Bajanman said:
Not sure you were on the newer 4.4.2 bootloader or not. If it was on a newer bootloader then you won't be able to downgrade.. This might help you get the phone working again since you just flashed the original firmware.
Go to this thread here>>http://forum.xda-developers.com/showthread.php?t=2502464.
Download
4.3 Param.bin and Tz.img
http://d-h.st/OYC
Unzip, Boot into Download mode, Open ODIN, put tar file in PDS slot, click Start.
Then you can go here for the latest stock Att firmware. If the above steps don't help you, then you could try flashing one one the rooted stock packages from this thread.
Click to expand...
Click to collapse
Ok that worked and it booted!!!! Now im on 4.1.1 with TWRP
Not really sure what I just did? Did I downgrade my bootloader? Also, now how do I get it to the most up to date version without this again?
I downloaded an app and it says im on.....
Bootloader Version: 1317UCUBMK6
Thanks!
Oxicottin said:
Ok that worked and it booted!!!! Now im on 4.1.1 with TWRP
Not really sure what I just did? Did I downgrade my bootloader? Also, now how do I get it to the most up to date version without this again?
Thanks!
Click to expand...
Click to collapse
Ok not is back working again, which is great news ?. Go to the link I posted for the stock firmware, and use the rooted one.
But first make a backup of your working system first ok.
Bajanman said:
Ok not is back working again, which is great news . Go to the link I posted for the stock firmware, and use the rooted one.
But first make a backup of your working system first ok.
Click to expand...
Click to collapse
Ok, Im On 4.3 now and its working great.... Thank You!
Oxicottin said:
Ok, Im On 4.3 now and its working great.... Thank You!
Click to expand...
Click to collapse
You're very welcome glad I could help fix it.
Have a good day...
Ok problem solved so unsubscribing from this thread. If you run into any other problems you can always hit me up thru pm ?.
I have spent days looking, turn on goes to kies firmware screen yet when i put in the model and s/n it shuts and the new samsung app to replace kies is of no help. I can get to the download screen and odin shows it up but no ATT 10.5 Tab S Sm-T807A firmware ANYWHERE.
Please help this is a very very expensive paperweight and im not affiliated with ATT so them helping me is out of the question.
Samobile.com
info.sven said:
Samobile.com
Click to expand...
Click to collapse
They dont have it for the SM-T807A
0 Results found
You searched for "sm-t807a"
It would better if you just explain what state the tablet is in and how it got to that state.
There is no official software for the t807a.
OK here how it goes,
The tablet was completely fine.
The original owner ( a family member) tried to root it and didnt accomplish it, somehow through his process it ended up softbricked.
I can enter he download mode for odin but no firmware for this LTE model.
When I turn it on it goes to the kies screen but kies doesnt recognize it, and when I enter the serial it buffers for 2 seconds then closes the process of kies.
Also it says device isnt supported and yes I have installed the right drivers and uninstalled kies numerous times.
The new replacement prog for Kies (forgot the name) is no help either.
Im terrified of what to do next as it does go to the odin screen just no firmware as I stated.
Any update, or could someone upload the stock firmware so i can use Odin on it.
Samsung told me ATT can flash it for free onto it so its deff a possibility however I do not have a ATT account so they cant help me.
It doesn't boot because the stock recovery has been wiped/replaced.
Thats assuming you have tried to boot recovery?
The att models are all bootloader locked.
I'm surprised a bootloader locked device even allowed an unsigned image to flash or did they use something like flashify?
The stock ota update was posted by someone here a while back. Your only chance is to pull the recovery from it and try and flash it in download mode. However odin may refuse to flash it.
If I can find it I can pull out the recovery.img and post a modified cf_autoroot which will try and flash the original recovery, that's if odin will even accept the image.
I was used with something like kingroot.
"The stock ota update was posted by someone here a while back. Your only chance is to pull the recovery from it and try and flash it in download mode. However odin may refuse to flash it.
If I can find it I can pull out the recovery.img and post a modified cf_autoroot which will try and flash the original recovery, that's if odin will even accept the image."
this i would highly appreciate as the firmwares not deleted just corrupted.
i have searched the whole web.
here is the link to the pulled stock sm-t807a files from a xda member
https://drive.google.com/folderview?id=0B7ndOWpeCEJ4NFVHZmtvTFN0UFU&usp=sharing
PowerfulJY, any successfull update with your SM-T807A journey?
I have the same problem as you, and Odin refuses to flash your firmware files
synphonica said:
PowerfulJY, any successfull update with your SM-T807A journey?
I have the same problem as you, and Odin refuses to flash your firmware files
Click to expand...
Click to collapse
The images won't flash as they are raw unsigned images.
The update should contain a signed recovery image, but may still not flash with odin as the tar package you make will not be signed either and odin may refuse to flash
There may be a way though, another member managed to brick their device by flashing twrp using Heimdall, but couldn't then flash back the stock recovery with Heimdall.
If somehow the stock recovery can be forced to flash with Heimdall then there's a chance of unbricking the device.
I worked just flashed the FW part through AP did it on a friends pc all is back to new.
if you need a link for the ripped files just pm me.
also odin was used.
ashyx said:
The images won't flash as they are raw unsigned images.
The update should contain a signed recovery image, but may still not flash with odin as the tar package you make will not be signed either and odin may refuse to flash
There may be a way though, another member managed to brick their device by flashing twrp using Heimdall, but couldn't then flash back the stock recovery with Heimdall.
If somehow the stock recovery can be forced to flash with Heimdall then there's a chance of unbricking the device.
Click to expand...
Click to collapse
Unfortunately, Heimdall shows the same behaviour as Odin has.
AFAIK they are using the same protocol and seems that recovery CRC/sign check done via device internally, not via flashing tool.
PowerfulJY said:
I worked just flashed the FW part through AP did it on a friends pc all is back to new.
if you need a link for the ripped files just pm me.
Click to expand...
Click to collapse
Please explain in more detail what you have done for the benefit of others.
---------- Post added at 03:22 PM ---------- Previous post was at 03:22 PM ----------
synphonica said:
Unfortunately, Heimdall shows the same behaviour as Odin has.
AFAIK they are using the same protocol and seems that recovery CRC/sign check done via device internally, not via flashing tool.
Click to expand...
Click to collapse
Did you use command line or gui?
I used GUI, i didnt do the bootloader or choose any special clickies, I simply tried another pc with the same FW and it flashed in a hearbeast with PASS.
USB hubs are the devil, TRY EVERY USB PORT YOU HAVE
Kies sucks so does the new one.
any issues PM me and ill set you straightm any public questions ask away.
You have to download the IMG files and use the IMG to TAR app, I will provide a ZIP with all tars included but I assure you dont start ****ing around with bootloader images stick to AP.
AT&T is he devil.
The new Rockstar Whipped Strawberry OWNS, Oraneg Creme is Meh.
PowerfulJY said:
I used GUI, i didnt do the bootloader or choose any special clickies, I simply tried another pc with the same FW and it flashed in a hearbeast with PASS.
USB hubs are the devil, TRY EVERY USB PORT YOU HAVE
Kies sucks so does the new one.
any issues PM me and ill set you straightm any public questions ask away.
You have to download the IMG files and use the IMG to TAR app, I will provide a ZIP with all tars included but I assure you dont start ****ing around with bootloader images stick to AP.
AT&T is he devil.
The new Rockstar Whipped Strawberry OWNS, Oraneg Creme is Meh.
Click to expand...
Click to collapse
The gui question was for synphonica about Heimdall.
Are you saying you flashed the images with odin? Which version and which images?
This has been tried before and failed.
Also what do you mean you tried a pc with the same firmware, same firmware as what?
I'm new to rooting so be gentle, I just bought a Galaxy Tab S 10.5 sm-t807a (AT&T) with Android 5.0.2 Lollipop. I want to backup the stock ROM (firmware) so I can go back just in case I bricked it when rooting or installing custom ROM. I searched the web but there are no clear instruction on how to do it for an unrooted sm-t807a. Can someone provide me with a step-by-step instruction? I can share my backup of the stock ROM afterward since there does not seem to be one on the web. Thank you in advance for your help.
cluver53 said:
I'm new to rooting so be gentle, I just bought a Galaxy Tab S 10.5 sm-t807a (AT&T) with Android 5.0.2 Lollipop. I want to backup the stock ROM (firmware) so I can go back just in case I bricked it when rooting or installing custom ROM. I searched the web but there are no clear instruction on how to do it for an unrooted sm-t807a. Can someone provide me with a step-by-step instruction? I can share my backup of the stock ROM afterward since there does not seem to be one on the web. Thank you in advance for your help.
Click to expand...
Click to collapse
You can only root with Kingroot, don't try any other method or you'll brick it nor can you install a custom kernel or recovery.
Once you have root you can pull the partition images with EFS PRO or PARTITION BACKUP.
The best way to have a back up is to catch the stock Firmware update.
This is tricky so research how to do it.
There is one backup I know of:
https://drive.google.com/folderview?id=0B7ndOWpeCEJ4NFVHZmtvTFN0UFU&usp=sharing