Related
PREPARATION STEP! download sgs kernel flasher from the market (must be rooted I believe) and do a kernel backup as this process changes your kernel.
SPRINT TAB INSTRUCTIONS THAT WORKEDFOR MANY SPRINT TAB OWNERS. IT MAY NOT WORK FOR YOU!
Ok here it is, Thank koushs for this product, cruiserbax for his awesome instructions and Benjamin Dobell for giving up Heimdall flashing utility and install instructions.
I NOR THE ANYONE LIST ABOVE ARE RESPONSIBLE FOR THIS NOT WORKING!!! OR ANY DAMAGE IT MAY DO TO YOUR TAB!!
To get the zip file containing the zimage download it from here. http://www.megaupload.com/?d=SV6IKL1D
To flash the zimage you will need to use Heimdall which can be downloaded here. http://www.glassechidna.com.au/products/heimdall/ <--------click on the binaries link for 1.1.1
instruction are below.
Heimdall install instructions
1. Download Heimdall here http://www.glassechidna.com.au/products/heimdall/
2. Download Microsoft Visual C++ 2010 Redistributable Package (x86) and install it. http://www.microsoft.com/downloads/...5E-6DE6-4D3A-A423-37BF0912DB84&displaylang=en <------only if you are using Microsoft widows
2. Unzip Heimdall and you should have several files in the folder called Heimdall.exe, Heimdall-Frontend.exe, QtCore4.dll, QtGui4.dll, Readme.txt and drivers folder containing zadig.exe
3. Put you tab into Download mode(while the tab is OFF hold Volume Down + Power Button). Hook the tab up to you PC and Run Zadig.exe to install the drivers.
4. From the menu chose Options -> List All Devices.
5. From the USB Device list chose "Samsung USB Composite DEvice".
6. Press "Install Driver", click "Yes" to the prompt and if you receive
a message about being unable to verify the publisher of the driver
click "Install this driver software anyway".
7. Done. This only needs to be done once.
ClockWorkMod Install Instructions
1. First root you tab (use one click root or z4root) then downloaded rom manager.
2. Unzip the flash_image_VZW_zimage.zip. It will have have two files flash_image and zimage. you only need to use the zimage file. Open Heimdall-Frontend.exe and browse to where you unzipped the zimage to and select it. Make sure the box infront of zimage is checked. Hit start and it should flash the zimage and reboot the tab.
when it reboots it will get stuck at the samsung screen long hold the power button to shut it off. boot into recovery (cwm) power button plus volume up button it will start backing up to do the fs conversion but it will fail at /data and /cache. it will leave you in recovery.
3. While still in recovery select factory reset/data wipe when finished also do a cache wipe.
4. select reboot system, if you let it try to boot it will loop/hang on the SAMSUNG logo, this is not an issue just hold power key until it powers off.
5. while off hold volume up + power until you see the SAMSUNG logo then release both keys! NOTE: if step 4 does not fully power off and reboots just keep holding the power button until the screen blanks again then let go and quickly hold down only volume up + power until you see the SAMSUNG logo.
6. once it boots back into recovery (cwm) it will start the same backup/conversion process again, this time it will finish and leave you in recovery.
7. select reboot system and wait for it to load the tab back to froyo. (it will be back to factory defaults with the activation screen again)
8. Your tab will still be rooted so install terminal emulator and run "mount" to verify that your partitions are ext4.
9. Power off then boot back into recovery with volume up + power, it will boot back into recovery (cwm)
10. Do a backup and reboot your tab.
Source:
http://www.thegalaxytabforum.com/index.php?/topic/1775-clockworkmod-for-sprint-galaxy-tabs/
Yes, I tried this and it works great but be aware that certain kernels seem to mess it up.
Which Kernel Seems To Work The Best?
@ lloydcabraham
Which kernel is the most stable?
I rooted my tab last night in preparation for the HC port, and I'm curious about whether CWM is necessary... seems everything needs to be flashed via Heimdal or Odin, so is the advantage to having CWM installed just the wipe capabilities? I'm used to my EVO, and flashing/rooting/modding which is obviously different, I just don't understand what the differences are, I guess. THANKS SO MUCH FOR THE STEP BY STEP! Simpletons like me find them EXTREMELY useful!
Great work, and thanks again!
Sent from my PC36100 using XDA Premium App
I'll have to try this soon.
IP IHI II IL said:
I rooted my tab last night in preparation for the HC port, and I'm curious about whether CWM is necessary... seems everything needs to be flashed via Heimdal or Odin, so is the advantage to having CWM installed just the wipe capabilities? I'm used to my EVO, and flashing/rooting/modding which is obviously different, I just don't understand what the differences are, I guess. THANKS SO MUCH FOR THE STEP BY STEP! Simpletons like me find them EXTREMELY useful!
Great work, and thanks again!
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Somewhat Offtopic:
Chances are the honeycomb port will come to GSM Devices First, We can only hope that it comes to Sprint and Verizon devices.
I believe the build being worked on right now in here is based on a cdma device...
Not off topic at all. THE ONLY HC port is currently being built by spacemoose (reading more than one thread on one website helps) and that wasn't the focus of my question. Please read before you quote/insinuate. Don't wanna be tagged with the troll label...
cdguider said:
Somewhat Offtopic:
Chances are the honeycomb port will come to GSM Devices First, We can only hope that it comes to Sprint and Verizon devices.
Click to expand...
Click to collapse
Sent from my PC36100 using XDA Premium App
Clockworkmod has many advantages if you flash different roms, or say wanted to backup your current sprint rom & settings before testing Honeycomb Port.
As far as Honeycomb Port goes,
Again Chances are Honeycomb will port to Gsm Devices First,
Honeycomb is still Closed Code.
I said somewhat off topic, which it was, considering the thread is titled Clockworkmod.
Get your facts straight.
cdguider said:
@ lloydcabraham
Which kernel is the most stable?
Click to expand...
Click to collapse
I like Bauxite but you will get a flaky camera (Sometimes won't initialize without reboot) and seems to mess up CWM (Although redoing these steps fixes it) but I do love running @ 1.4 super stable!
cdguider said:
Clockworkmod has many advantages if you flash different roms, or say wanted to backup your current sprint rom & settings before testing Honeycomb Port.
As far as Honeycomb Port goes,
Again Chances are Honeycomb will port to Gsm Devices First,
Honeycomb is still Closed Code.
I said somewhat off topic, which it was, considering the thread is titled Clockworkmod.
Get your facts straight.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=11780452&postcount=1
3/26/11 #2:...Second... The "dirty" port will be for CDMA devices, but as soon as the CDMA version is released I'll look into getting a GSM version out asap. Shouldn't be hard. Instead of using my own kernel for this one, I'm using a modified version of Boushh's kernel and can probably hack together a suitable kernel for other devices as well. My own kernel for the larger project is still in fluctuation as I have to make changes to suit the build on a regular basis, but when I finalize that kernel I'll release it as an update and it will get a repo of it's own.
Click to expand...
Click to collapse
The quote was for what?
Re-read it one more time...
Really
I still stand by my message.
It's also apparent you didn't go back to page 1 otherwise you would have known I acknowledged spacemoose1 Honeycomb Port.
Despite someone working on Honeycomb port for Sprint / CDMA devices.
Chances are someone else is working on it for GSM, as with damn near anything, GSM devices will most likely get it first,
KEYWORD: most likely, and if you read the previous post - keyword is chances are
Bottom line is who cares who gets it first.
I'm well aware of most developments going on XDA
can u guys just drop it already!
Ok im stuck I followed steps but I am stuck at the samsung screen won't boot into recovery I don't know what I did wrong... I need help I have it stuck! (sigh) uSING hEIMDALL It isn't specific on which box I should use the zimage in which box using heimdall... I used it in the recovery under other made sure the box was checked. It ran through backups 2 times then looked like it was launching into recovery cwr 3.0 but when I picked it up it turned off when I turned on all I get is the samsung logo FOREVER... I have tried using heimdall again and tried to use it under FACTORYFS but same result. Please help. All I have now is a Huge Expensive Paper Weight. HELP
*** Ok after further review *SIGH* I understand I probably should have studied the damn thing better there is an option for zImage there... So how bad did I mess this thing up and is there a way to UnDue what I have Done?
Update-
So I was able to flash the Zimage and get to recovery but when I tried to wipe/data/cache and load K-lean rom I got this ---->http://img819.imageshack.us/img819/8655/imag0061y.jpg
I was also able to boot in but couldn't launch because every one of the launchers would fc.
I will attempt another ROM but I fear it is bricked.... I don't give up easily so any help would be awesome.
Thanks in advance.
Damn,
Can you boot into recovery at all? Ifa ll fails, put your Tablet in downloader mode, and flash the file below, follow the instructions in the zip file, if you have done some of the steps skip them, however read very carefully.
http://www.gsmelite.com/Sprint Galaxy Tab EA24 Flasher Odin.zip
cdguider said:
Damn,
Can you boot into recovery at all? Ifa ll fails, put your Tablet in downloader mode, and flash the file below, follow the instructions in the zip file, if you have done some of the steps skip them, however read very carefully.
http://www.gsmelite.com/Sprint Galaxy Tab EA24 Flasher Odin.zip
Click to expand...
Click to collapse
So I was able to flash the Zimage and get to recovery but when I tried to wipe/data/cache and load K-lean rom I got this ---->http://img819.imageshack.us/img819/8655/imag0061y.jpg
I was also able to boot in but couldn't launch because every one of the launchers would fc.
I will attempt another ROM but I fear it is bricked.... I don't give up easily so any help would be awesome.
Thanks in advance.
Thanks for the link... Will give it a try.
Really don't know what to say about the error message, My tab was messed up with errors like can't mount....., some other stuff, I had to send mine in to get replaced, never would go past the samsung logo. At the time the only thing Sprint users had was the Stock DJ30 With Modem.
Now we have no modem.
EA24 Stock
Ext 4
Honeycomb Port In Progress.
cdguider said:
Damn,
Can you boot into recovery at all? Ifa ll fails, put your Tablet in downloader mode, and flash the file below, follow the instructions in the zip file, if you have done some of the steps skip them, however read very carefully.
http://www.gsmelite.com/Sprint Galaxy Tab EA24 Flasher Odin.zip
Click to expand...
Click to collapse
Before I tried that I loaded the Honeycomb ROM well it isn't but the Khasmek's AOSP beta 1 and it worked everything working but the real question is what to do now... If I reboot does it load agian? Should I use Rom manager and run a recovery Backup? what would you advise?
****Update
So after getting everything setup I tried to do a boot to recovery through Rom Manager and low and behold back to dreaded SAMSUNG screen with NUTIN happening. Will try your steps next
****Update
After following steps and flashing image with odin... I was able to boot up fine... Downside---> My Verizon tab is now a Sprint Tab ... I need to find the .tar for VZW anyone? ANYONE? *SIGH*
Ok either I'm just plain stupid, or somethings wrong. Every link I try to get TWRP Recovery for my Tab 3 8.0 just gives me a damn img file that I can do nothing with. Can't mount it, can't burn it, and I'm certainly not finding the TWRP file. My Tab is saying no OS in TWRP so I'm trying to recover it, but I can't find the damn correct file :/
Thanks for any help
Listen @meffie you record shows you are an old user 2009, but This is your 1rst Post!!! So I have no Idea what knowledge you really have.
So you could be playing st2p1d for us. Or you in fact need a lot to read. So read, read a little more and if you have more time read what left.
First I do not understand why you are saying "My Tab is saying no OS in TWRP so I'm trying to recover it"!!!
I am juts going to clarify a few things.
There is a goo reading trad for you to try it. But understand that You and only you decide what thread to follow. It is all at your own risk.
Let's amuse you follow this one:
Samsung Galaxy Tab 3 > Galaxy Tab 3 General > Root the Samsung Galaxy Tab 3 8.0 and Install Custom Recovery =>http://forum.xda-developers.com/showthread.php?t=2525630
You may find there that you download "TWRP_T31x_r3.tar"
A "*.tar" type of recovery can be use by Odin, but it is more common to see a "*.tar.md5" The difference is that the one with "*.tar.md5" is more safe to use because it has a MD5 hash that is use by Odin to certify that the file is not corrupt before installing it.
If you follow the tread you are ask to:
Code:
1. Extract Odin307.zip to a folder on your desktop.
2. Copy TWRP_T31x_r3.tar to the extracted Odin307 folder.
So it tell you just to place "TWRP_T31x_r3.tar" in the same folder where you Extracted Odin. Yes the "TWRP_T31x_r3.tar" intact. No extraction needed.
Clearly you misunderstood and did in fact extracted "TWRP_T31x_r3.tar". And yes in fact you found your self a "recovery.img".
Using Odin is a Very Dangerous thing you can screw you device if you do something wromg. My best sugetion is for you to read more.
Now in the same general forum you may find:
Samsung Galaxy Tab 3 > Galaxy Tab 3 General > [VIDEOS] Galaxy Tab 3 7in How to root, recovery, roms, & Kitkat =>http://forum.xda-developers.com/showthread.php?t=2459817
Yes this tread is not for you device, but it can give you a good Idea. In particular see: "TWRP INSTALL PLUS ROOT"
I have not seen that video nor I have a TAB3 7" nor 8" mine is 10". But I bet it pretty similar process. I do not know what the video shows but you could take my advice . DO NOT mark "Re-Partition" you will brick your device. In Options I suggest you let mark ONLY "F.Reset Time". As you see NO "Auto Reboot" neither. This will prevent you device from booting after it finish. So when are you going to know it as finished. Well you will see in Odin say "Recovery" while installing and after it finish it will change to a Blue "Reset". It is at this time that your are going to press [Power]+[Volume Up]+[Menu]. And TWTP will show in your screen.
Good Luck. DO not forget to READ.
r2d23cpo said:
Listen @meffie you record shows you are an old user 2009, but This is your 1rst Post!!! So I have no Idea what knowledge you really have.
So you could be playing st2p1d for us. Or you in fact need a lot to read. So read, read a little more and if you have more time read what left.
First I do not understand why you are saying "My Tab is saying no OS in TWRP so I'm trying to recover it"!!!
I am juts going to clarify a few things.
There is a goo reading trad for you to try it. But understand that You and only you decide what thread to follow. It is all at your own risk.
Let's amuse you follow this one:
Samsung Galaxy Tab 3 > Galaxy Tab 3 General > Root the Samsung Galaxy Tab 3 8.0 and Install Custom Recovery =>http://forum.xda-developers.com/showthread.php?t=2525630
You may find there that you download "TWRP_T31x_r3.tar"
A "*.tar" type of recovery can be use by Odin, but it is more common to see a "*.tar.md5" The difference is that the one with "*.tar.md5" is more safe to use because it has a MD5 hash that is use by Odin to certify that the file is not corrupt before installing it.
If you follow the tread you are ask to:
Code:
1. Extract Odin307.zip to a folder on your desktop.
2. Copy TWRP_T31x_r3.tar to the extracted Odin307 folder.
So it tell you just to place "TWRP_T31x_r3.tar" in the same folder where you Extracted Odin. Yes the "TWRP_T31x_r3.tar" intact. No extraction needed.
Clearly you misunderstood and did in fact extracted "TWRP_T31x_r3.tar". And yes in fact you found your self a "recovery.img".
Using Odin is a Very Dangerous thing you can screw you device if you do something wromg. My best sugetion is for you to read more.
Now in the same general forum you may find:
Samsung Galaxy Tab 3 > Galaxy Tab 3 General > [VIDEOS] Galaxy Tab 3 7in How to root, recovery, roms, & Kitkat =>http://forum.xda-developers.com/showthread.php?t=2459817
Yes this tread is not for you device, but it can give you a good Idea. In particular see: "TWRP INSTALL PLUS ROOT"
I have not seen that video nor I have a TAB3 7" nor 8" mine is 10". But I bet it pretty similar process. I do not know what the video shows but you could take my advice . DO NOT mark "Re-Partition" you will brick your device. In Options I suggest you let mark ONLY "F.Reset Time". As you see NO "Auto Reboot" neither. This will prevent you device from booting after it finish. So when are you going to know it as finished. Well you will see in Odin say "Recovery" while installing and after it finish it will change to a Blue "Reset". It is at this time that your are going to press [Power]+[Volume Up]+[Menu]. And TWTP will show in your screen.
Good Luck. DO not forget to READ.
Click to expand...
Click to collapse
No indeed I haven't posted. I just try and read. As I'm not heavily into rooting and moding, I have little to say, as such I don't feel the need to post.
I am legit in my question, and maybe I just need to be a little clearer.
I rooted the tab and have had it rooted for a while now. When I originally rooted it, I didn't realize I would've ever be able to update it again, so after the new kitkat updates came out and I couldn't update it, I decided I would unroot it and go back to stock.
That being said, like an idiot, instead of reading about unrooting first, I went into TWRP and wiped it, thinking that would restore the device. After I wiped it, it booted back into TWRP and now says "No OS installed".
I of course came back to the forum and started reading the recovery thread, although you did answer my question. I did not realize Odin reads the tar, instead of the imagine inside, so that's where my confusion came from. Now that I know I just need to give Odin the tar I will proceed and hope the I can get my tab restored. If I can't return to stock, hopefully I can just reflash a new rom. I'd hate to think my actions bricked it.
That being said, I appreciate you answering my question and not just assuming I'm trolling because I don't post.
I'll let you know how it goes, thanks!
So I was able to load the TWRP recovery through Odin, reboot back into TWRP and it is still telling me no OS installed. I'm not quite sure where to go from here. All the threads Im finding are about rooting and recovering, nothing really says anything about No OS installed. Any additional help would be appreciated.
I have included a screen cap for reference.
Thanks
When you wiped everything you deleted the OS. You will need to download a ROM or flash a stock through ODIN
Sent from my ATRIX HD using XDA Free mobile app
Thanks for the Picture, I never seen that before.
*bmatney is right, the safe way to proceed is to "download a ROM or flash a stock through ODIN". This will require to download the 1.5G Stock Recovery. Listen I strongly suggest to download the Old 4.2.2 Stock Not the KK-4.4.2 one! The new one comes with new bootloaders.
*Not many people agree with me, but this bootloaders could be dangerous. Or ask the few Samsung SG4 users that got Stock with Lock booloaders!! Beware, make your own decision.
*Now I never seen this "No OS installed". My best guess is that TWRP should still allow you to place a copy of your old "Rom.zip" (the one you where using and should have available) inside the external sdcard and install zip from external sdcard. Do not forget to wipe cache and dalvik before installing.
*This is important, the original problem "after the new kitkat updates came out and I couldn't update it". I bet you you are a P5210 Wifi owner, And you had previously install old TWRP that all of us used. The problem is that that TWRP was build to be use in a P5200-3G model. So when in Recovery the Tab think it is a P5200 and do not allow you to install a P5210 Rom!!! The solution is to install new version from :
Samsung Galaxy Tab 3 > Galaxy Tab 3 10.1 Android Development > [Recovery] Philz Adv CWM 6.55.0 - CWM 6.0.5.0 - TWRP v2.7.1.0 - AROMAFM GT-P5210 => http://forum.xda-developers.com/gal...ockworkmod-recovery-6-0-5-0-gt-p5210-t2830871
But please do that Recovery change after you have repair and have a valid OS. Do not put you self in a position where you have no OS and no Recovery!! First install a Rom.
Good Luck
I got the stock 4.4.2 flashed, it's working again. Thanks so much for the help guys, I greatly appreciate it.
I have been searching the forum and google and have been unable to reach a solution yet.
I am not a noob, but i am not an expert either so use small words ha.
I have a Samsung Galaxy Tab 3 10.1 5210 with the most recent OTA update.
Last night I attempted to root my device using this:
androidxda (DOT) com/root-samsung-galaxy-tab-3-10-1-gt-p5210
It claimed successful and my device started to reboot and hung up at the Samsung GALAXY TAB 3 screen. I am unable to get to recovery mode on the device. Only able to go to download mode. I have tried several options but have been unable to find a way to flash it successfully. The flashes i have tried downloading were all in .zip and that obviously isn't able to be used in Odin. I have researched how to convert the files into a .tar but I don't have linux. Can someone please help me because I need my tablet. I know it can be saved but I can't seem to locate the answers. I am also getting concerned that it is unable to charge the battery being in the condition it is in now so I am trying to conserve the battery on the tablet until it is absolutely needed. Thanks.
cameron72 said:
I have been searching the forum and google and have been unable to reach a solution yet.
I am not a noob, but i am not an expert either so use small words ha.
I have a Samsung Galaxy Tab 3 10.1 5210 with the most recent OTA update.
Last night I attempted to root my device using this:
androidxda (DOT) com/root-samsung-galaxy-tab-3-10-1-gt-p5210
It claimed successful and my device started to reboot and hung up at the Samsung GALAXY TAB 3 screen. I am unable to get to recovery mode on the device. Only able to go to download mode. I have tried several options but have been unable to find a way to flash it successfully. The flashes i have tried downloading were all in .zip and that obviously isn't able to be used in Odin. I have researched how to convert the files into a .tar but I don't have linux. Can someone please help me because I need my tablet. I know it can be saved but I can't seem to locate the answers. I am also getting concerned that it is unable to charge the battery being in the condition it is in now so I am trying to conserve the battery on the tablet until it is absolutely needed. Thanks.
Click to expand...
Click to collapse
First of all - Welcome to xda
Your tab is soft bricked, something has gone wrong with your system files... Honestly it seems like you know enough to get it done, but are struggling a bit with the file formats. You are correct in saying that Odin won't use zip files, but you shouldn't have to convert anything to tar or download linux! If you extract the zip files, you should find a .tar or .tar.md5 file (inside the zip file) that Odin can use, put it in the PDA mode box, etc etc... If your downloads don't have the correct files inside them, try THIS thread.
Let me know if you get it sorted :good:
bob23bk said:
First of all - Welcome to xda
Your tab is soft bricked, something has gone wrong with your system files... Honestly it seems like you know enough to get it done, but are struggling a bit with the file formats. You are correct in saying that Odin won't use zip files, but you shouldn't have to convert anything to tar or download linux! If you extract the zip files, you should find a .tar or .tar.md5 file (inside the zip file) that Odin can use, put it in the PDA mode box, etc etc... If your downloads don't have the correct files inside them, try THIS thread.
Let me know if you get it sorted :good:
Click to expand...
Click to collapse
I had already tried the method and file in the forum you linked me to. It failed almost instantly. That's when I turned everything off and tossed it all to the back seat of my work truck before it got thrown at the windshield. I keep seeing people saying they have trwp or whatever. I don't even know what that is haven't researched that. Is it something i need as well?
I've never successfully rooted a Samsung device. I used to do this stuff a lot back with the droid x with Linux and everything was pretty simple. Does Samsung change their bootloader with each update like Motorola did then? I was wondering that when trying to install a firmware of a previous version that maybe that was the problem.
All I wanted root for was to just tweak some things and be happy. It has turned into a nightmare.
C,
hi,
the consistent/common thread of this problem is/seems to be taking the ota and trying unverified/gimmicky
root methods.
there are recoveries for the gt-p52xx in the tab 10.1 forum
the majority of samsung devices root as follows;
if a custom recovery exist, flash it.
then download recent or latest version of chainfire's supersu update zip, reboot to recovery
backup your rom first, then flash supersu, if everything goes well, once you have set up your stock rom with root in place
make a new backup.
samsung ota's are death incarnate, reject them.
goto the tab 10 forum and get busy ! you said it yourself, you're not a noob, you know the drill. :good:
m
moonbutt74 said:
C,
hi,
the consistent/common thread of this problem is/seems to be taking the ota and trying unverified/gimmicky
root methods.
there are recoveries for the gt-p52xx in the tab 10.1 forum
the majority of samsung devices root as follows;
if a custom recovery exist, flash it.
then download recent or latest version of chainfire's supersu update zip, reboot to recovery
backup your rom first, then flash supersu, if everything goes well, once you have set up your stock rom with root in place
make a new backup.
samsung ota's are death incarnate, reject them.
goto the tab 10 forum and get busy ! you said it yourself, you're not a noob, you know the drill. :good:
m
Click to expand...
Click to collapse
I have tried the recoveries in the forum and it failed seconds after starting.
I don't do this stuff regularly as I don't hardly have the time. I haven't done anything of this nature in years so I'm well out of the loop on things..
cameron72 said:
I have tried the recoveries in the forum and it failed seconds after starting.
I don't do this stuff regularly as I don't hardly have the time. I haven't done anything of this nature in years so I'm well out of the loop on things..
Click to expand...
Click to collapse
okay, hmm, when you say it fails, do you mean odin fails to flash and if so what is the reason/ouput ?
or do you mean that you are now in a recovery bootloop ?
note- though i go the full route of packing recovery.img's for odin flashing, the md5 checksum always seems to
come up as invalid, the working "remedy" is to remove the .md5 extension from the "odin-flashable-recovery".tar.md5 file
by renaming the file to "odin-flashable-recovery".tar
odin will no longer attempt the checksum verification but the recovery file will flash.
make sure you have samsung-usb-drivers for windows installed. on the main page of my devhost archive [link is in my signature]
you will find the tools you need. the possible problem is that the ota you installed may have overwritten your bootloader, for that i don't
have a reliable fix, so if anything make sure you also have the stock recovery ready to go as well as supersu update zip
already downloaded onto your device for rooting.
after you flash the custom recovery [with auto-restart in odin disabled] run the flash and wait for the res-ok message, give it another second or two then disconnect the tab and force reboot to recovery, home,vol-up and power, once in recovery make a full backup, then flash supersu zip and reboot, if you do go into recovery loop, force reboot to odin mode, home,vol-down and power, follow the on screen instruction, now reconnect your tab to pc and use odin to flash back stock recovery.
m
Okay guys I appreciate the help. I finally got it. I tried the method on Zachisimo's post on unbricking and finally got it installed.
After it installed, it left me with a bootloop and I was actually able to go into recovery mode this time and do a factory data reset and wipe cache then everything went well. I am a happy dude now.
Going to attempt rooting it again and does anyone have any suggestions on what ROM to install? I have never used any custom ROM's before so that is a new area for me. Feeling more confident knowing how to save it from the dead. :good::good::good:
cameron72 said:
Okay guys I appreciate the help. I finally got it. I tried the method on Zachisimo's post on unbricking and finally got it installed.
After it installed, it left me with a bootloop and I was actually able to go into recovery mode this time and do a factory data reset and wipe cache then everything went well. I am a happy dude now.
Going to attempt rooting it again and does anyone have any suggestions on what ROM to install? I have never used any custom ROM's before so that is a new area for me. Feeling more confident knowing how to save it from the dead. :good::good::good:
Click to expand...
Click to collapse
Hi,
Alright !'m glad you got it working, as to roms , all available roms currently are stock modifications , I use cag-rom, there's also pimp-droid
both kitkat.
m
moonbutt74 said:
Hi,
Alright !'m glad you got it working, as to roms , all available roms currently are stock modifications , I use cag-rom, there's also pimp-droid
both kitkat.
m
Click to expand...
Click to collapse
If you use it then thats what i shall try. First i gotta find a root, then I have seen many people recommend philz recovery, and then the rom?
question why does Restl3ss say wait 10minutes after installing a rom before doing anything?
cameron72 said:
If you use it then thats what i shall try. First i gotta find a root, then I have seen many people recommend philz recovery, and then the rom?
question why does Restl3ss say wait 10minutes after installing a rom before doing anything?
Click to expand...
Click to collapse
for root look up supersu update zip
ask Restl3ss :silly:
m
cameron72 said:
Okay guys I appreciate the help. I finally got it. I tried the method on Zachisimo's post on unbricking and finally got it installed.
After it installed, it left me with a bootloop and I was actually able to go into recovery mode this time and do a factory data reset and wipe cache then everything went well. I am a happy dude now.
Going to attempt rooting it again and does anyone have any suggestions on what ROM to install? I have never used any custom ROM's before so that is a new area for me. Feeling more confident knowing how to save it from the dead. :good::good::good:
Click to expand...
Click to collapse
Glad it worked out, recovering from brick does set you free from the stress induced by the disclaimers imo :silly:
Sorry if I'm posting in the wrong forum here, but I wasn't sure where to start.
I got an ATT Note 8 unlocked running Nougat that would not come up on the Verizon network using my working SIM card. I had read that there were known issues with this and that an upgrade to oreo would fix things. Googling around I found an upgrade zip file from N950USQS2BQK2 to N950USQU2CQL1. I used the recovery method to upgrade from that file and at first things seems to be fine. I started having lots of issues with apps dying, eg Contacts, Phone and Bixby and started to wonder if perhaps the OS could be further upgraded. I hunted around and installed the samfirm tool and downloaded the file
SM-N950U_1_20181126150901_ouxwmh265r_fac.zip and extracted out all the parts. Using Odin (13.1) I tried to install this file but it got hung installing
system.img.ext4. Realizing that it would likely cause problems I powered off the phone after a couple of hours with no progress. As expected the phone was pretty pissed off when I tried to boot it up. It was stuck in trying to upload a crash file and took a lot of fiddling around to convince it to go back to download mode, thanks to one of the posts from this site I was able to make it work.
I've tried the same file again and it is stuck again at the same place. So the question is should I be using a different file? If at all possible I'd just like to run the standard Verizon load, in hunting around it seems for the latest Oreo I should use N950USQS5CRK1. but I can't figure out where to get that file in the format that Odin uses I've looked on the firmware.science website but have only come up with the zip version that would work with the recovery mode. Unfortunately with the state my phone is currently in I don't think I can get to recovery mode. It is in the endless upload mode, hitting the down & power button will shut it down but it comes right back to the upload screen. Any advice would be greatly appreciated. Sorry for the rambling post.
rphaddad said:
Sorry if I'm posting in the wrong forum here, but I wasn't sure where to start.
I got an ATT Note 8 unlocked running Nougat that would not come up on the Verizon network using my working SIM card. I had read that there were known issues with this and that an upgrade to oreo would fix things. Googling around I found an upgrade zip file from N950USQS2BQK2 to N950USQU2CQL1. I used the recovery method to upgrade from that file and at first things seems to be fine. I started having lots of issues with apps dying, eg Contacts, Phone and Bixby and started to wonder if perhaps the OS could be further upgraded. I hunted around and installed the samfirm tool and downloaded the file
SM-N950U_1_20181126150901_ouxwmh265r_fac.zip and extracted out all the parts. Using Odin (13.1) I tried to install this file but it got hung installing
system.img.ext4. Realizing that it would likely cause problems I powered off the phone after a couple of hours with no progress. As expected the phone was pretty pissed off when I tried to boot it up. It was stuck in trying to upload a crash file and took a lot of fiddling around to convince it to go back to download mode, thanks to one of the posts from this site I was able to make it work.
I've tried the same file again and it is stuck again at the same place. So the question is should I be using a different file? If at all possible I'd just like to run the standard Verizon load, in hunting around it seems for the latest Oreo I should use N950USQS5CRK1. but I can't figure out where to get that file in the format that Odin uses I've looked on the firmware.science website but have only come up with the zip version that would work with the recovery mode. Unfortunately with the state my phone is currently in I don't think I can get to recovery mode. It is in the endless upload mode, hitting the down & power button will shut it down but it comes right back to the upload screen. Any advice would be greatly appreciated. Sorry for the rambling post.
Click to expand...
Click to collapse
Download this odin firmware and FIRST extract it one time and the files for odin will be in the extracted folder and flash. You must flash AP, BL, CP and CSC all at the same time. Fill all the slots in odin.
https://androidfilehost.com/?fid=11410963190603879881
MrMike2182 said:
Download this odin firmware and FIRST extract it one time and the files for odin will be in the extracted folder and flash. You must flash AP, BL, CP and CSC all at the same time. Fill all the slots in odin.
Thanks for this. One question, I had the same issue the last time, there is a CSC and a HOME-CSC file included in the zip archive, which of these should be used with Odin?
thanks again
Click to expand...
Click to collapse
rphaddad said:
MrMike2182 said:
Download this odin firmware and FIRST extract it one time and the files for odin will be in the extracted folder and flash. You must flash AP, BL, CP and CSC all at the same time. Fill all the slots in odin.
Thanks for this. One question, I had the same issue the last time, there is a CSC and a HOME-CSC file included in the zip archive, which of these should be used with Odin?
thanks again
Click to expand...
Click to collapse
Never mind found that in another post.
thx
Click to expand...
Click to collapse
if I wanna odin without losing data I use home instead of CSC correct?
I would suggest also using Samsung Smart Switch before doing it. It gives you the option to back up pretty much your whole phone including just about all your apps, settings and customizations to an SD card. It also saves your custom icon groups too if you do that. The it makes it a breeze to restore after doing an Odin flash. It has helped save me a time or 2.
Eta: After rereading the OP, looks like you may not be able to use this as you need to be able to boot all the way up.
Right, I was not able to boot so smart connect isn't an option, but luckily it's a new phone so no data to transfer. I did run into an issue using Odin with USB C on my laptop to the phone, I think that is how I got into that predicament in the first place with Odin downloads failing to complete. Works fine with USB 2.
Phone is all set now and working fine. Thanks for your help.
Here used to be a bad guide please don't follow it I learned that people where rightfully pissed at me and I have decided to replace it with this Im gonna flash lineage again and document my exact procedure and try to make a better guide than the garbage I posted here.
error : can't load losq-v
hey man,
Thanks for the effort but I only got one problem that whenever I enter this command "fastboot flash system losq-v lineage.img" I get the error saying "can't load losq-v" so what should I do.
Thanks in advance
KFC99 said:
hey man,
Thanks for the effort but I only got one problem that whenever I enter this command "fastboot flash system losq-v lineage.img" I get the error saying "can't load losq-v" so what should I do.
Thanks in advance
Click to expand...
Click to collapse
The reason is losq-v is the start of the filename pretty sure you can just press tab and it will autocomplete so the command would be "fastboot flash system losq-v"(after losq-v type rest of your filename or press tab to autocomplete (do not add a space in between losq-v and rest of filename))
Sry for forgetting that I did it like that to future proof the guide
camera not working
kamilkamjy said:
camera not working
Click to expand...
Click to collapse
Well it should. Ask the guys in the a71 group
Can it flash on U3 ui2.5 or 2.1?
Blocklisted said:
Well it should. Ask the guys in the a71 group
Click to expand...
Click to collapse
LoL
Posting "tutorials" in XDA is something else than copy and paste things you expect to work but never tested yourself.
Two persons get in trouble by the crap you copy and pasted here, and instead of take responsibility when things go bad, the only crap you can say is: ask THE GUYS in telegram rofl
What age are you? 12?
I hope no one follow this crappy " tutorial" here...
Odin Recovery Fails
I go step by step but when I hit start on Odin to flash recovery I get two error messages
1. one in Odin in the log section with the following message "failed (auth)"
2. the other on the phone in the download mode in red something along the lines "you can only install official binaries"
I searched the forums and found a few suggestions, turning on USB debugging, applying magisk patches etc.... I never saw anyone confirming any method that would have worked. Whatever I tried to do it either didn't work or I couldn't do it because of lack of skills or it wasn't possible. For example when I tried to use magisk in the descriptions I had install buttons in the manger but I'm missing these on my phone so I suspect that recovery is required first to make those patches or there's something that I don't know how to do it. Either way following the instructions doesn't work for me and I tried a bunch of things and none worked. Different versions of Odin 3.14.1, 3.14.4. If anyone has any idea please help. I reset the whole phone to factory hoping it would help, there's no data on it right now but I still get the same error.
Thanks
rb1979 said:
I go step by step but when I hit start on Odin to flash recovery I get two error messages
1. one in Odin in the log section with the following message "failed (auth)"
2. the other on the phone in the download mode in red something along the lines "you can only install official binaries"
I searched the forums and found a few suggestions, turning on USB debugging, applying
《Cutting》
Either way following the instructions doesn't work for me and I tried a bunch of things and none worked. Different versions of Odin 3.14.1, 3.14.4. If anyone has any idea please help. I reset the whole phone to factory hoping it would help, there's no data on it right now but I still get the same error.
Thanks
Click to expand...
Click to collapse
To back to original Android:
-Odindownload.com last Odin
- https://github.com/ivanmeler/SamFirm_Reborn/releases download samfirm reborn and use it to get latest original Samsung firmware
Unzip it with 7-ZIP !!!!!! www.7-zip.org
On the Odin website there is a YouTube video how to proceed. But do NOT use any PIT file you find somewhere like the vid shows in example, you will almost for sure brick it if you don't know exact exactly what you r doing! Be warned!
After unzipping you see files beginning with AP BL CP CSC , put them in Odin where they should be.
Under options ONLY mark AutoReboot and F reset time and nothing else.
I hope you get your phone back to working state with this, remember you will not be able to get updates OTA any more since you broke the Efuse.
From there on if I were you I only would root the phone and wait till official TWRP is out, or hopefully some day an official LineageOS.
So far nothing official means lack of maintanance after a while, no updates, bugs, bad assistance and more crap, just like this thread is written by someone who gathered info from just here and there and made this "tutorial" with copy and paste and added b.s. for trying to become a star on Telegram-ish group and look populair there.
Just Root it, debloat it and live with it.
andreoide said:
To back to original Android:
-Odindownload.com last Odin
- https://github.com/ivanmeler/SamFirm_Reborn/releases download samfirm reborn and use it to get latest original Samsung firmware
Unzip it with 7-ZIP !!!!!! www.7-zip.org
On the Odin website there is a YouTube video how to proceed. But do NOT use any PIT file you find somewhere like the vid shows in example, you will almost for sure brick it if you don't know exact exactly what you r doing! Be warned!
After unzipping you see files beginning with AP BL CP CSC , put them in Odin where they should be.
Under options ONLY mark AutoReboot and F reset time and nothing else.
I hope you get your phone back to working state with this, remember you will not be able to get updates OTA any more since you broke the Efuse.
From there on if I were you I only would root the phone and wait till official TWRP is out, or hopefully some day an official LineageOS.
So far nothing official means lack of maintanance after a while, no updates, bugs, bad assistance and more crap, just like this thread is written by someone who gathered info from just here and there and made this "tutorial" with copy and paste and added b.s. for trying to become a star on Telegram-ish group and look populair there.
Just Root it, debloat it and live with it.
Click to expand...
Click to collapse
Thanks andreoide for your honest answer :good:
My phone's working, I didn't get far with it, never broke it, just unlocked it. I guess the installation failed during the validation before actually doing any physical changes because my Samsung stock system still runs. The phone is given to me by my company. I just took out the sim card and put it in my private dual-sim phone. So this phone is on the shelf, it's been there for the last few months. I wish I could use it it's higher end than my personal but can't deal with Samsung stock system. I had two phones with lineage (and whatever the name was before) and loved it so I'm hoping I can use it again.
Anyway, it was just explaining my situation, I guess I'll be checking this forum and hoping for more positive news. Meanwhile the phone goes back on the shelf and waits for better times, thanks again for straitening things up for me. :good:
Blocklisted said:
Here used to be a bad guide please don't follow it I learned that people where rightfully pissed at me and I have decided to replace it with this Im gonna flash lineage again and document my exact procedure and try to make a better guide than the garbage I posted here.
Click to expand...
Click to collapse
Well, since you come clear and admit the guide you posted before was pure crap, i have to rise my thumbs up to you.
I think this is a mature respond.
:good: