Root SM-T210/R using Heimdall - Galaxy Tab 3 General

I took a little time playing around with Heimdall. It's....... different.
I have taken the time to simplify some of the steps for everyone, and built the required file myself.
I used TWRP 2.8.0.0 "img" file from their website. All development credit go to TeamWin, I've just converted it to the proper file format for Heimdall.
edit: The file use is actually a port to the Tab 3 by gr8nole. I was wrong about a couple of things. So, credit goes to TeamWin for original dev, and to gr8nole for porting it to the Tab 3 for us
Before reading farther, please remember:
ALL FLASHING IS DONE AT ONE's OWN RISK, I'M NOT RESPONSIBLE.
Please take adequate precautions to be able to recover your device from a soft brick.
This method is for KitKat users.
I used the Pit mapping for the T210. The recovery partition is "mmcblk0p10." I checked the partition info on my T210R using Partition Table by Lakshman. The T210R also has its Recovery partition on "mmcblk0p10," so I expect it to work no problem. And TWRP Odin flashables tend to be compatible with several 7.0 variants.
1. Open Heimdall. Reboot your device into download mode (power+volume down+home, then volume up).
2. Attach tablet to computer.
3. Select "Load Package" tab if it isn't already.
4. Click the "Browse" button under "Heimdall Firmware Package."
5. Select the ".tar.gz" file attached to this thread.
6. Click "Load/Customize." This will jump you to the "Flash" Tab.
7. Make sure that the "Repartition" check-box is unselected.
8. Click "Flash."
9. After flashing, reboot into your new recovery and install SuperSU and BusyBox.
As of this point, I have not been able to test this. I hope it goes well for anyone who tries it
Update:
As of now, I have been able to test this file on my own T210R. I already had this version of TWRP installed, so can't confirm actual update, but Heimdall said it flashed, and it didn't brick it, so I'd say good to go! (Take appropriate precautions anyways, because you never know what will happen.)

Worked well, thanks

Greaper88 said:
I took a little time playing around with Heimdall. It's....... different.
I have taken the time to simplify some of the steps for everyone, and built the required file myself.
I used TWRP 2.8.0.0 "img" file from their website. All development credit go to TeamWin, I've just converted it to the proper file format for Heimdall.
Before reading farther, please remember:
ALL FLASHING IS DONE AT ONE's OWN RISK, I'M NOT RESPONSIBLE.
Please take adequate precautions to be able to recover your device from a soft brick.
I used the Pit mapping for the T210. The recovery partition is "mmcblk0p10." I checked the partition info on my T210R using Partition Table by Lakshman. The T210R also has its Recovery partition on "mmcblk0p10," so I expect it to work no problem. And TWRP Odin flashables tend to be compatible with several 7.0 variants.
1. Open Heimdall. Reboot your device into download mode (power+volume down+home, then volume up).
2. Attach tablet to computer.
3. Select "Load Package" tab if it isn't already.
4. Click the "Browse" button under "Heimdall Firmware Package."
5. Select the ".tar.gz" file attached to this thread.
6. Click "Load/Customize." This will jump you to the "Flash" Tab.
7. Make sure that the "Repartition" check-box is unselected.
8. Click "Flash."
9. After flashing, reboot into your new recovery and install SuperSU and BusyBox.
As of this point, I have not been able to test this. I hope it goes well for anyone who tries it
Update:
As of now, I have been able to test this file on my own T210R. I already had this version of TWRP installed, so can't confirm actual update, but Heimdall said it flashed, and it didn't brick it, so I'd say good to go! (Take appropriate precautions anyways, because you never know what will happen.)
Click to expand...
Click to collapse
You say you took TWRP from TeamWin's website? Can you show me that, because I'm pretty sure they don't support this device.

gr8nole said:
You say you took TWRP from TeamWin's website? Can you show me that, because I'm pretty sure they don't support this device.
Click to expand...
Click to collapse
Maybe not their official website... oops.
The file I used you've uploaded... my mistake, thought you were part of their project.

Well the TWRP image file worked well enough for me... Either way...
I think this is the main way to root the T210(R) if updated to KitKat. Since it is quite possible that it's the last update it's ever going to see, I'd say it's good time to root it now and put Xposed on it for good measure.

xaueious said:
Well the TWRP image file worked well enough for me... Either way...
I think this is the main way to root the T210(R) if updated to KitKat. Since it is quite possible that it's the last update it's ever going to see, I'd say it's good time to root it now and put Xposed on it for good measure.
Click to expand...
Click to collapse
This version of TWRP is still compatible with JellyBean. I restored and booted my stock OS using this flash. And this is the same method that I had used to root before the update. (using Odin rather than Heimdall though.)

@Greaper88 did you test other files to confirm that functionality is working well (just curious) ?
Heimdall is interesting tool but i haven't tested it myself.

mkaymuzik said:
@Greaper88 did you test other files to confirm that functionality is working well (just curious) ?
Heimdall is interesting tool but i haven't tested it myself.
Click to expand...
Click to collapse
Do you mean other Heimdall installer files?
I've not tested other files as I've only messed with my Tab 3, and any flash files have to be built from a raw ".img" (image) file and the device's PIT (Partition Information Table). This presents challenges that I haven't tried to overcome.
I saw a request somewhere in another thread for a walkthrough on rooting the Tab 3 with Heimdall, and I figured out and posted this since it was only the recovery, and that much was actually somewhat easy.
My idea was, if you get custom recovery, you can then install your choice of ROM. Although I don't know if there is a TWRP flashable stock KK ROM yet...
I'm confident that the method in this thread for mentioned devices works based on my own flash and on "xaueious'" posts.
To port this method to other devices, one just needs the device's PIT and the recovery image file, "recovery.img" for example in order to build a flash file. The process is actually easy once you know how.
Full ROMs would be more difficult I think because there are other files besides ".img" files that have to be written to the flash, and a XML file has to be built as well to handle all of that. I haven't had time to mess with all of that...

Greaper88 said:
Do you mean other Heimdall installer files?
I've not tested other files as I've only messed with my Tab 3, and any flash files have to be built from a raw ".img" (image) file and the device's PIT (Partition Information Table). This presents challenges that I haven't tried to overcome.
I saw a request somewhere in another thread for a walkthrough on rooting the Tab 3 with Heimdall, and I figured out and posted this since it was only the recovery, and that much was actually somewhat easy.
My idea was, if you get custom recovery, you can then install your choice of ROM. Although I don't know if there is a TWRP flashable stock KK ROM yet...
I'm confident that the method in this thread for mentioned devices works based on my own flash and on "xaueious'" posts.
To port this method to other devices, one just needs the device's PIT and the recovery image file, "recovery.img" for example in order to build a flash file. The process is actually easy once you know how.
Full ROMs would be more difficult I think because there are other files besides ".img" files that have to be written to the flash, and a XML file has to be built as well to handle all of that. I haven't had time to mess with all of that...
Click to expand...
Click to collapse
Thx for the info mate. Going test this out.

I'm lost, I was working on my hubby's tablet and somehow the backup I made got wiped when I tried to Samsung Galaxy Tab 3 7.0 WiFi SM-T210/T210R Performance Upgrade MOD. I'm assuming that it doesn't work under KitKat as I was running TranchidaKat v2.2 [4.4.2 SM-T210/R Rom. Anyway whatever I did no matter what I wipe I keep getting one error from Odin, ""can't mount ES' I'd sure appreciate a hand on this thing if your around. I've been trying to run Heimdall but it always fails in Odin. What really confused me on your directions is you saying to open the package and select Load the Package. I'm not sure exactly what that means but I have Odin 3.07 through 3.10 and I don't see anything like that, could you clarify. I can load the regular 2.8 TWRP using the img file that has nothing to do with Heimdall so I can get into recovery but that's where I'm stuck. Any thoughts???
Krissy

Odin is leaked Samsung Software. Heimdall is an open source substitute, and is not related to Odin. Heimdall requires the TWRP file posted in the OP in this thread to work, but it will not work in Odin.
If you have a custom recovery installed that you can boot into, check out:
http://forum.xda-developers.com/gal...-stock-sm-t210r-4-1-2-jellybean-twrp-t2951850
If you've lost your backup files, then these ones might work for you unless the device flash has been overly corrupted.
If that doesn't work, check out:
http://forum.xda-developers.com/galaxy-tab-3/general/tab-3-7-0-sm-t210-r-stock-4-4-2-kitkat-t2930075
That's intended to be flashed directly from Odin, and will make the device stock KitKat.
I then like to use the Werewolf Kernel, since it overclocks the Tablet and improves overall speed that way.
Other thoughts: have you tried another USB cable/port? I've had similar errors simply because Odin didn't like my USB cable, or the USB port I was connected to.

Related

[Q]Unable to root my device from recovery

I Am unable to mount system or cache either and also i cant flash certain files from my CWM recovery I think it is because I forgot to root my device before flashing the CWM from stock recovery. Now I can't do nandroid backup or root the device either i need help. The data speed is too slow at my home I'll not be able to download stock rom (it would take days to download)... Is there any way??
smartananallavan said:
I Am unable to mount system or cache either and also i cant flash certain files from my CWM recovery I think it is because I forgot to root my device before flashing the CWM from stock recovery. Now I can't do nandroid backup or root the device either i need help. The data speed is too slow at my home I'll not be able to download stock rom (it would take days to download)... Is there any way??
Click to expand...
Click to collapse
Recovery Mode doesn't need root to function. Try the Universal GB Root package and tell me what happens, a bit more information would be helpful, like, if an error shows, or something like that...
EDIT: OH! I just realized what is happening! You are using CWM with a Stock ROM that you want to root, right? Well, CWM does NOT support .EFS file systems. It can't mount the /system/ partition to write on it. When you install a custom ROM with it, it re-formats the system partition to EXT4. So, you can't use both a Stock ROM and CWM. They do not support each other. You need to flash a custom ROM. Or use the Stock Recovery to flash the Root Zip.
another trouble.....
thanks i figured that out but also now there is another problem...please help me.
I downloaded the stock rom and it has only two files ( a .dll and an file HOME.tar) but i loaded the file as PDA in
odin and now there comes the problem.... the drivers are setup and the ID:COM section turns yellow and then in the
logs everything proceeds good and gets stuck at the setupconnection stage. I'll try to post the screen shot
smartananallavan said:
thanks i figured that out but also now there is another problem...please help me.
I downloaded the stock rom and it has only two files ( a .dll and an file HOME.tar) but i loaded the file as PDA in
odin and now there comes the problem.... the drivers are setup and the ID:COM section turns yellow and then in the
logs everything proceeds good and gets stuck at the setupconnection stage. I'll try to post the screen shot
Click to expand...
Click to collapse
Ok, i'll wait for the screenshot =)
Also, this is a first i have ever heard of this problem. If the drivers are OK, Odin is showing the COM Port, and the Setup begins, my only guess is that you got the wrong flash files... Are you sure you'r device is "s5670"? not some other model? Also, i recommend downloading official firmware from SamFirmware. But for now, i wait for screenie =)
smartananallavan said:
thanks i figured that out but also now there is another problem...please help me.
I downloaded the stock rom and it has only two files ( a .dll and an file HOME.tar) but i loaded the file as PDA in
odin and now there comes the problem.... the drivers are setup and the ID:COM section turns yellow and then in the
logs everything proceeds good and gets stuck at the setupconnection stage. I'll try to post the screen shot
Click to expand...
Click to collapse
Don't load it as PDA, instead load it as One Package(home.tar.md5 file)
my samsung doesnt open
i tried to install cyanogen 10.4.1 jelly bean to my galaxy fit but i didnt root it first i realized that later and it couldnt wipe and couldnt install the update. the problem is that it doesnt open any more. it stays at galaxy fit screen what can i do to restore it?
Stay Calm Bro
koukis32 said:
i tried to install cyanogen 10.4.1 jelly bean to my galaxy fit but i didnt root it first i realized that later and it couldnt wipe and couldnt install the update. the problem is that it doesnt open any more. it stays at galaxy fit screen what can i do to restore it?
Click to expand...
Click to collapse
Hi @koukis32
Dnt wry Bro ur cell is just fine please download the Firmware pages that you want to flash from the link below by entering your phone model number or i shall also paste link where in you can download the package directly also.
You can find the required ODIN Firmware Package as you wish for the ODIN tool
http://www.sammobile.com/firmwares/ and put in the Device Model Number and download it
or complete Firmware Package of Gingerbread 2.3.6 DDKT3 you can find the link below
http://hotfile.com/dl/146050815/b3b9...2_INU.zip.html in case this link doesn't work please download the Packages from above link as I can't check it from my office so dntmnd
For ODIN Flashing Tool:
http://www.downloads.techdiscussion....ting-software/
and Procedure to Flash is:
- Shutdown Galaxy Fit and restart it in Recovery Mode. For that hold the volume down key + Home key and power key. Hold it for some seconds and leave it. The device will boot in recovery mode. When the yellow triangle, connect cell phone and a computer with a USB cable.
- Launch ODIN on your system. In that look under ID:COM section. The section will turn to yellow once the device is connected and detected.
- Now click on OPS. It will ask you to browse the downloaded firmware package. Browse to GIO_1.0.ops. Once it is selected click on One Package and choose S5670DDKT3_S5670ODDKT2_S5670DDKT2_HOME.tar.md5.
- Now click on Start. The update process has started and it will take few minutes to complete.
- Once it is done, the device will reboot itself. Later on you can go in Settings and checkout the firmware version.
And considering still you still in Galaxy Fit Page then go take a break and relax and follow the instructions in the link which I have shared you phone will come back to life.
http://www.androidauthority.com/how...xy-fit-s5670-android-2-3-4-gingerbread-35369/
follow the picture carefully.
:good::fingers-crossed::fingers-crossed::fingers-crossed:
AXAz0r said:
Ok, i'll wait for the screenshot =)
Also, this is a first i have ever heard of this problem. If the drivers are OK, Odin is showing the COM Port, and the Setup begins, my only guess is that you got the wrong flash files... Are you sure you'r device is "s5670"? not some other model? Also, i recommend downloading official firmware from SamFirmware. But for now, i wait for screenie =)
Click to expand...
Click to collapse
thaks for helping sorry for the long Delay. solved the problem!!!! just downloaded a stock deodexed rom.zip and flashed...... booted up fine

Please help me! Cant install any ROM on my OnePlus!

Hi Everyone!
Because of having issues i can´t fix on my OnePlus, i´m finally asking for some professional help here, as it´s getting more and more complicated and i don´t want to ruin my phone.
What was my plan?
Installing CM11S 44S on my OPO, which had the 05Q Version as factory setting.
Also i wanted to install a franco kernel.
I hoped, if i do both steps successfully, my OPO will have a good battery life (44S seemed to be the most efficient version, according to some forums).
What did i do so far?
First i set up an adb backup for my data, but not for the OS. However, i installed SDK plus tools and drivers.
Next step was installing a new recovery, which is able to flash a new version of CM11S, so i set up TWRP with fastboot, which means my device is "unlocked" now.
Everything worked well so far, i also made an backup in TWRP.
The problem:
I wanted to reboot my OPO at some point and TWRP asked me for rooting my device. Accidentally i swiped over so it started rooting process, but i didn´t want to root it, so i immediately shut the device down.
By now TWRP recovery/fastboot is working, but my OS 05Q is lost and i can´t install a new ROM because im getting the Report:
--
Checking for MD5 file...
Skipping MD5 check; no MD5 file found
Error flashing zip /<path to .zip file>
--
Can anyone help me to get 05Q back or the 44S with the franco kernel?
I know there might be some other threads that deal with similar problems, but actually none of them helped me so far. For example: do i need a fastboot image or signed flashable zips (which i have)? In which order do i install the kernel and the ROM?
Some Information:
I can access my device via fastboot and my OPO is also shown as a adb device on my MAC.
When starting in TWRP, i can also access the device in USB Mode, transfering files is also possible.
I´m not really competent with android modding or programming, so i will need some noob-friendly answers, but i bet you guys know how to help me out here.
Thank you very much for your help, i really don´t know what to do anymore.
EDIT:
I found out how to place a md5 file to the referring version, but it still sais: MD5 does not match.
I´m so done with it right now that i wish i had my OPO back as it was few days ago.
Well, i cant really help here as i have not face this problem but ur mistake was that u Immediately shut the device down the moment it was installing root. It may have corrupted the partitions of the phone and left it at that state, so maybe restoring the partitions of that section may help. Like i said im not knowledgeable about this
Agreed, you shouldn't have shut down the phone while it was modifying a partition. The root wouldn't have mattered anyway because you were about to overwrite the system partition by flashing a ROM. Go to my guide thread and look at section 8 to flash the stock images for the build you desire:
http://forum.xda-developers.com/showthread.php?t=2839471
Heisenberg said:
Agreed, you shouldn't have shut down the phone while it was modifying a partition. The root wouldn't have mattered anyway because you were about to overwrite the system partition by flashing a ROM. Go to my guide thread and look at section 8 to flash the stock images for the build you desire:
http://forum.xda-developers.com/showthread.php?t=2839471
Click to expand...
Click to collapse
Can i follow all these instructions altough im using a mac?
I will try it out today, hopefully this will fix the problem.
Thyrix said:
Can i follow all these instructions altough im using a mac?
I will try it out today, hopefully this will fix the problem.
Click to expand...
Click to collapse
Yes you can still use fastboot on a Mac, but you'll need to Google how to set it up on a Mac first.
Heisenberg said:
Yes you can still use fastboot on a Mac, but you'll need to Google how to set it up on a Mac first.
Click to expand...
Click to collapse
Alright, so fastboot is ready, but i need to know, if i will need one of those "unofficial stock rooted fashable zips" a fastboot image. or anything else? sorry to ask for
Can i trust an android version anyone rooted...?
Thyrix said:
Alright, so fastboot is ready, but i need to know, if i will need one of those "unofficial stock rooted fashable zips" a fastboot image. or anything else? sorry to ask for
Can i trust an android version anyone rooted...?
Click to expand...
Click to collapse
You need the fastboot images.
Heisenberg said:
You need the fastboot images.
Click to expand...
Click to collapse
Got stuck at step 2: It Terminal said error: cannot determine image filename for sbl1.mbn - although the name is correct and the file is in the correct folder :/
EDIT:
Fixed it, forgot to type sbl1 2 times, im sorry
And it worked, thank you sooooo much!!!

Help greatly appreciated - S6 G920F Bootloop after odin flash

Hello folks. Today I did a cache, system, data wipe in TWRP on my G920F. After that I tried to restore a nandroid backup, but it failed and when I tried to restart it said there was no OS installed. So the phone wouldn't boot. I figured I did something wrong so I downloaded a 5.1.1 stock rom (UK) and flashed it with odin. But after the flash the phone would just bootloop. How can I revive the phone? Tried flashing the firmware again using another version of odin and also, I did a factory reset from the stock recovery, but no dice. Any ideas? Thanks in advance
Hey there,
check this thread here, should help (use TWRP to flash a ROM instead of Odin, links in thread).
Good luck!
Managed to make it work flashing another official rom, then factory reset. Lost all my files though...
Can be closed. Thanks!
Sent from my SM-G925F using Tapatalk
kendall1004 said:
Hey there,
check this thread here, should help (use TWRP to flash a ROM instead of Odin, links in thread).
Good luck!
Click to expand...
Click to collapse
How can i make TWRP flash a rom when Galaxy S6 doesn't have SD card to put the rom in the phone?
Immoblize said:
How can i make TWRP flash a rom when Galaxy S6 doesn't have SD card to put the rom in the phone?
Click to expand...
Click to collapse
Connect the phone to your PC and copy the ROM file to its root folder (just open "phone" and drop it there).
Using TWRP's "install" menu, you can browse your files and point it to this one; usually you're already in the right directory.
kendall1004 said:
Connect the phone to your PC and copy the ROM file to its root folder (just open "phone" and drop it there).
Using TWRP's "install" menu, you can browse your files and point it to this one; usually you're already in the right directory.
Click to expand...
Click to collapse
I wish that was so easy. I am on bootloop on my second day and i can fix it. I am getting crazy here. Nothing work - Kies, Smart Switch or Odin.
Immoblize said:
I wish that was so easy. I am on bootloop on my second day and i can fix it. I am getting crazy here. Nothing work - Kies, Smart Switch or Odin.
Click to expand...
Click to collapse
None of these three will help, i'm afraid.
The bootloop issue is a result of system write protection with 5.1.1 version, the phone tries to override a flashed recovery-
if it succeeds in automatically rebooting after you flashed, you're stuck on bootloop.
You have to flash a new kernel and root user via Odin, then flash TWRP and use it to install a new ROM.
A short description in this thread here, have a look.
As long as you can get into download mode, don't worry, nothings bricked :good:
kendall1004 said:
None of these three will help, i'm afraid.
The bootloop issue is a result of system write protection with 5.1.1 version, the phone tries to override a flashed recovery-
if it succeeds in automatically rebooting after you flashed, you're stuck on bootloop.
You have to flash a new kernel and root user via Odin, then flash TWRP and use it to install a new ROM.
A short description in this thread here, have a look.
As long as you can get into download mode, don't worry, nothings bricked :good:
Click to expand...
Click to collapse
THANKS A LOT for the info. I have today worked for about 8-9 hours to fix it. I will try read tomorrow on the site you put there and also read about how to put files to TWRP - since i don't have a SD card on my S6.
Immoblize said:
THANKS A LOT for the info. I have today worked for about 8-9 hours to fix it. I will try read tomorrow on the site you put there and also read about how to put files to TWRP - since i don't have a SD card on my S6.
Click to expand...
Click to collapse
Sleep over it, tomorrow is another day
Also, browse my recent postings here; most of them revolving around your issue, this will surely help.
kendall1004 said:
None of these three will help, i'm afraid.
The bootloop issue is a result of system write protection with 5.1.1 version, the phone tries to override a flashed recovery-
if it succeeds in automatically rebooting after you flashed, you're stuck on bootloop.
You have to flash a new kernel and root user via Odin, then flash TWRP and use it to install a new ROM.
A short description in this thread here, have a look.
As long as you can get into download mode, don't worry, nothings bricked :good:
Click to expand...
Click to collapse
Okay, i have done almost all of what you said.
But what im thinking about is the thread your refering to is to a S6 Edge and not for SM-G920F model.
But so far so good.
What kernel to you want me to flash? How can i root via Odin when i don't have USB-debugging on - But i can according to the thread, install SuperSU via TWRP.
I didn't know what kernel i had on, but i managed to install TWRP, install SuperSU via TWRP, pushing my stock rom to TWRP. But when installing the stock rom, it says "no md5 file found" or something like that. What am i doing wrong?
Immoblize said:
Okay, i have done almost all of what you said.
But what im thinking about is the thread your refering to is to a S6 Edge and not for SM-G920F model.
But so far so good.
What kernel to you want me to flash? How can i root via Odin when i don't have USB-debugging on - But i can according to the thread, install SuperSU via TWRP.
I didn't know what kernel i had on, but i managed to install TWRP, install SuperSU via TWRP, pushing my stock rom to TWRP. But when installing the stock rom, it says "no md5 file found" or something like that. What am i doing wrong?
Click to expand...
Click to collapse
Should work on both Edge and normal.
I have the G920F and did it this way, i also had problems, by the way:
http://forum.xda-developers.com/showpost.php?p=62550973&postcount=29
I recommend chosing an XtreStoLite ROM, the odexed version is an "improved stock" one, comes with a modified UniKernel and runs much smoother than stock.
Anyway, in TWRP, there is an option to skip md5 checking for backup files and for skipping the zipfile-check; not sure if you can also disable md5sum-checks.
Maybe you should try downloading the ROM from here or sammobile.de, verify the md5-sum yourself to make sure it is fine, and flash that one.
If TWRP doesn't think the ROM file is ok, it probably isn't ...
here's the odexed version of XtreStoLite:
http://forum.xda-developers.com/galaxy-s6/development/rom-xtrestolite-pure-edition-1-0-beta-1-t3082467
kendall1004 said:
Should work on both Edge and normal.
I have the G920F and did it this way, i also had problems, by the way:
http://forum.xda-developers.com/showpost.php?p=62550973&postcount=29
I recommend chosing an XtreStoLite ROM, the odexed version is an "improved stock" one, comes with a modified UniKernel and runs much smoother than stock.
Anyway, in TWRP, there is an option to skip md5 checking for backup files and for skipping the zipfile-check; not sure if you can also disable md5sum-checks.
Maybe you should try downloading the ROM from here or sammobile.de, verify the md5-sum yourself to make sure it is fine, and flash that one.
If TWRP doesn't think the ROM file is ok, it probably isn't ...
here's the odexed version of XtreStoLite:
http://forum.xda-developers.com/galaxy-s6/development/rom-xtrestolite-pure-edition-1-0-beta-1-t3082467
Click to expand...
Click to collapse
Okay, i have flashed TWRP, installed the kernel and Super SU (http://forum.xda-developers.com/gal...p-recovery-2-8-7-1-g925f-android-5-1-t3144866). But i can't flash the modem and bootloader for the XtreStoLite because it gives me Nand write error. I tried then to install XtreStoLite from TWRP which installed correctly but still doesn't fix the bootloop. I can read that i WILL get the bootloop if not using the correct modem and bootloader, but for some reason i am not able to flash them. Any help here? Or am i doing everything wrong here?
Immoblize said:
Okay, i have flashed TWRP, installed the kernel and Super SU (http://forum.xda-developers.com/gal...p-recovery-2-8-7-1-g925f-android-5-1-t3144866). But i can't flash the modem and bootloader for the XtreStoLite because it gives me Nand write error. I tried then to install XtreStoLite from TWRP which installed correctly but still doesn't fix the bootloop. I can read that i WILL get the bootloop if not using the correct modem and bootloader, but for some reason i am not able to flash them. Any help here? Or am i doing everything wrong here?
Click to expand...
Click to collapse
Alright, you have root access and TWRP is running.
All you have to do is install the ROM file (unextracted, as a .zip) from your phone`s root folder; if your model is a G920F, the bootloader should be 5.1.1 and work, no need to change.
When exactly does Odin give you the error message, right after you click start or after a few secs of flashing?
I suspect the issue to be related to first reboot after flashing the recovery,.
When finished flashing TWRP, did you successfully boot into recovery menu be pressing vol up+home+power?
If you saw the bootloop screen then, you`ll have to do it again, i'm afraid:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. (...) Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
I know, it`s annoying; but give it another try:
use Odin 3.1.0.7 (run with admin rights), do a full wipe and install TWRP 2.8.7.
When doing so and Odin gives you the "finished/successfully flashed" message, immediately press & hold the key combo to get into recovery; don`t wait for the scrteen to change or unplug the phone, you need to be damn quick here.
If you have done it right, you are in TWRPs recovery menu.
From there, install the XtreStoLite ROM after doing a factory reset; reboot and you should be fine.
Aaaarrgh we will get this thing running, goddammit
kendall1004 said:
Alright, you have root access and TWRP is running.
All you have to do is install the ROM file (unextracted, as a .zip) from your phone`s root folder; if your model is a G920F, the bootloader should be 5.1.1 and work, no need to change.
When exactly does Odin give you the error message, right after you click start or after a few secs of flashing?
I suspect the issue to be related to first reboot after flashing the recovery,.
When finished flashing TWRP, did you successfully boot into recovery menu be pressing vol up+home+power?
If you saw the bootloop screen then, you`ll have to do it again, i'm afraid:
I know, it`s annoying; but give it another try:
use Odin 3.1.0.7 (run with admin rights), do a full wipe and install TWRP 2.8.7.
When doing so and Odin gives you the "finished/successfully flashed" message, immediately press & hold the key combo to get into recovery; don`t wait for the scrteen to change or unplug the phone, you need to be damn quick here.
If you have done it right, you are in TWRPs recovery menu.
From there, install the XtreStoLite ROM after doing a factory reset; reboot and you should be fine.
Aaaarrgh we will get this thing running, goddammit
Click to expand...
Click to collapse
What i did was install stock android via Odin.
Flashed TWRP
Flashed Alex V kernel first, then SUPER SU.
Flashed XtreStoLite and it still gives me bootloop.
What i can't manage to do is after flashing TWRP, then i am not fast enough to press Shutdown button, home button, and volume up button before the Samsung logo appears. I think that is the problem.
:silly:
Immoblize said:
What i did was install stock android via Odin.
Flashed TWRP
Flashed Alex V kernel first, then SUPER SU.
Flashed XtreStoLite and it still gives me bootloop.
What i can't manage to do is after flashing TWRP, then i am not fast enough to press Shutdown button, home button, and volume up button before the Samsung logo appears. I think that is the problem.
Click to expand...
Click to collapse
That IS the problem, i think :fingers-crossed:
Solved the same problem at reddit, take a look: reddit thread
Unfortunately, you must flash TWRP again to try once more, as soon as the samsung logo apperars, your custom recovery is overridden and thats it.
So now, take a deep breath, lean back and try again.
As soon as you have clicked to start the flashing procedure, press the 3 butons firmly, simultaneously and quick as lightning-
hold them down till it boots into TWRP.
Come on, even i have managed it after a few tries
kendall1004 said:
:silly:
That IS the problem, i think :fingers-crossed:
Solved the same problem at reddit, take a look: reddit thread
Unfortunately, you must flash TWRP again to try once more, as soon as the samsung logo apperars, your custom recovery is overridden and thats it.
So now, take a deep breath, lean back and try again.
As soon as you have clicked to start the flashing procedure, press the 3 butons firmly, simultaneously and quick as lightning-
hold them down till it boots into TWRP.
Come on, even i have managed it after a few tries
Click to expand...
Click to collapse
HMMM. I see.
It's not possible for me to boot into TWRP without the Samsung logo appears. I press the start, the same time i press the start, i press Power, Home and Volume Up button but still the logo appears. It takes 4 sec and it have flashed the TWRP. It's not possible...
Immoblize said:
HMMM. I see.
It's not possible for me to boot into TWRP without the Samsung logo appears. I press the start, the same time i press the start, i press Power, Home and Volume Up button but still the logo appears. It takes 4 sec and it have flashed the TWRP. It's not possible...
Click to expand...
Click to collapse
So, for some reason you can't enter recovery mode.
This could be
a) TWRP is not installed correctly (did you use the .img ot the .tar-file? Odin needs the .tar-format: link )
or
b) the kernel you flashed doesn't work with this-
here is the one i have used to root my S6.
I would try to reflash above Unikernel first, if you used the .img-file of TWRP rather than the .tar to flash TWRP,
do it again with the .tar file instead.
If this fails, the last thing would be to flash a unmodified stock ROM to restore the original setup including the bootloader...
i will look into this now a little bit deeper, there has to be a workaround.
Best of luck for now, we stay in touch
EDIT: the developer of XtreStoLite recommends another way with Chainfire's root:
Flash CF-Root for your model with Odin - Make sure you have an custom recovery installed (I advise you to use TWRP) (2.8.7.1 or newer REQUIRED for v.2.1 > of this ROM!!)
Click to expand...
Click to collapse
If the bootloader is your problem, you can update to the newest versions of bootloader and modem for your model following these instructions:
edgarf28`s instructions
I will do this right now, for a new version of XtreStoLite was just released today and i will upgrade.
Keep me informed
kendall1004 said:
So, for some reason you can't enter recovery mode.
This could be
a) TWRP is not installed correctly (did you use the .img ot the .tar-file? Odin needs the .tar-format: link )
or
b) the kernel you flashed doesn't work with this-
here is the one i have used to root my S6.
I would try to reflash above Unikernel first, if you used the .img-file of TWRP rather than the .tar to flash TWRP,
do it again with the .tar file instead.
If this fails, the last thing would be to flash a unmodified stock ROM to restore the original setup including the bootloader...
i will look into this now a little bit deeper, there has to be a workaround.
Best of luck for now, we stay in touch
EDIT: the developer of XtreStoLite recommends another way with Chainfire's root:
If the bootloader is your problem, you can update to the newest versions of bootloader and modem for your model following these instructions:
edgarf28`s instructions
I will do this right now, for a new version of XtreStoLite was just released today and i will upgrade.
Keep me informed
Click to expand...
Click to collapse
I can enter the recovery mode (TWRP) but not before the Samsung logo appears when i install TWRP. I have tried many times and i still can't enter TWRP before the samsung logo appears for 1-2 secs.
I am not able to flash Edgar28s bootloader and modem because it always gives me nand write error fail. I think it's because i'm not rooted with CFautoroot - and to get rooted with that way, i have to have USB debuggin on which i don't have.
What i think is, that i was very close but i still can't manage to enter TWRP (after installing) without the samsung logo appears for 1-2 secs. Because what you said before "Unfortunately, you must flash TWRP again to try once more, as soon as the samsung logo apperars, your custom recovery is overridden and thats it."
So what do you think now?
And btw thanks for all the help so far. I'm trying my best and following your steps but i always think i'm very close. I'm also so close to destroy my phone but i've read so many places that "it's only a softbrick, that can be fixed very easy".
Immoblize said:
I can enter the recovery mode (TWRP) but not before the Samsung logo appears when i install TWRP. I have tried many times and i still can't enter TWRP before the samsung logo appears for 1-2 secs.
I am not able to flash Edgar28s bootloader and modem because it always gives me nand write error fail. I think it's because i'm not rooted with CFautoroot - and to get rooted with that way, i have to have USB debuggin on which i don't have.
What i think is, that i was very close but i still can't manage to enter TWRP (after installing) without the samsung logo appears for 1-2 secs. Because what you said before "Unfortunately, you must flash TWRP again to try once more, as soon as the samsung logo apperars, your custom recovery is overridden and thats it."
So what do you think now?
And btw thanks for all the help so far. I'm trying my best and following your steps but i always think i'm very close. I'm also so close to destroy my phone but i've read so many places that "it's only a softbrick, that can be fixed very easy".
Click to expand...
Click to collapse
OK, so you can enter the TWRP menu and install a ROM, right?
Any stock ROM from sammobile.com includes firmware, kernel and bootloader, so flashing the right one of these should reset all this.
Give it a try, for i think TWRP is actually working- otherwise you wouldn't get to the screen.
If the phone runs again with stock firmware, you can then flash a custom ROM.
And yeah, we're close, this can be only a minor flaw...it's near impossible to brick your android phone, so they say.
Don't worry mate, and be assured you're not the only one:
i just got stuck on bootloop also for a few minutes after upgrading to the newest version of XtreStoLite, which came out today.
Using TWRP, i could just flash back the previous version and all's good again.
Cya tomorrow...
EDIT:
I read through your previous comments again; the "md5sum"- issue seems to be a problem with the ROM file itself (corrupted or wrong version).
I'd bet that flashing the correct stock firmware for your carrier and model will solve the problem.
So enter the exact model number (like G920FXXU3COI9 or such) you have, get the right ROM and flash it with Odin 3.10.7
I couldn't find a denmark carrier on sammobile, eventually you have to look here at XDA, there's a list of stock imges as well.
Read lots of threads around this issue, almost all solved the problem flashing a stock ROM again.
Fingers crossed :fingers-crossed:
OK, so you can enter the TWRP menu and install a ROM, right?
Any stock ROM from sammobile.com includes firmware, kernel and bootloader, so flashing the right one of these should reset all this.
Give it a try, for i think TWRP is actually working- otherwise you wouldn't get to the screen.
If the phone runs again with stock firmware, you can then flash a custom ROM.
And yeah, we're close, this can be only a minor flaw...it's near impossible to brick your android phone, so they say.
Don't worry mate, and be assured you're not the only one:
i just got stuck on bootloop also for a few minutes after upgrading to the newest version of XtreStoLite, which came out today.
Using TWRP, i could just flash back the previous version and all's good again.
Cya tomorrow...
EDIT:
I read through your previous comments again; the "md5sum"- issue seems to be a problem with the ROM file itself (corrupted or wrong version).
I'd bet that flashing the correct stock firmware for your carrier and model will solve the problem.
So enter the exact model number (like G920FXXU3COI9 or such) you have, get the right ROM and flash it with Odin 3.10.7
I couldn't find a denmark carrier on sammobile, eventually you have to look here at XDA, there's a list of stock imges as well.
Read lots of threads around this issue, almost all solved the problem flashing a stock ROM again.
Fingers crossed
Click to expand...
Click to collapse
Yeah, i've never had problems entering TWRP menu. I can flash stock firmware via Odin but i can never do it via TWRP because it's says no md5 file found error - tho i can flash XtreStoLite (i think it's because it says aroma installer).
I've read many places about the md5 file error, but for some reason, i can't figure out how to fix it.
No, there is no Denmark model, but we have NEE (Nordic). The only stock firmware i can install is XEF (i don't remember where i got that from actually).
I will try agian and flash stock android via TWRP AND read about the md5 file error now/later. Tomorrow i will call the store i got the phone from and tell them i have a hardware issue or something like that. The guy owns a store for sellings covers, cases and stuff like that. He got the phone from Samsung free and sold it brand new in the package with 1 year warranty, so i will contact him tomorrow if i can't figure out how to flash stock android via TWRP or if it gives me error about the md5 file.
Talk to you tomorrow.
Update: I can not flash NEE model via Odin. Only XEF model - i also found out it was French firmware.

So now what can I upgrade my Stock ROM to?

Hello, I'm a noob at this so please be kind. I followed the below:
http://forum.xda-developers.com/tra...inners-guide-unlock-custom-rom-tf300-t3061648
I successfully:
Unlocked my TF300T's Bootloader
Installed custom recovery using fastboot
Rooted my tablet
Debloated the Tablet (Titanium Backup)
Backup up my current (OEM) SYSTEM ROM to microSD
So now I'm onto attempting a custom ROM. I'm a bit bored with 4.2.1 and would like to go to the same version of ROM my Note 7 has which is 6.0.1 Marshmallow or even try the new 7.0 Nougat.
I'm a little confused as to what ROM will or will not work. I see a few ROMS worth trying, but there install instructions reference a different Bootloader multiple flashes such as SuperSU or gapps.
Whats the best fool proof method to flash a new ROM with what I have and are there any simple one file ROM/ZIP/ Blob etc.. file that would do what I want?
Thank you.
broderp said:
Hello, I'm a noob at this so please be kind. I followed the below:
http://forum.xda-developers.com/tra...inners-guide-unlock-custom-rom-tf300-t3061648
I successfully:
Unlocked my TF300T's Bootloader
Installed custom recovery using fastboot
Rooted my tablet
Debloated the Tablet (Titanium Backup)
Backup up my current (OEM) SYSTEM ROM to microSD
So now I'm onto attempting a custom ROM. I'm a bit bored with 4.2.1 and would like to go to the same version of ROM my Note 7 has which is 6.0.1 Marshmallow or even try the new 7.0 Nougat.
I'm a little confused as to what ROM will or will not work. I see a few ROMS worth trying, but there install instructions reference a different Bootloader multiple flashes such as SuperSU or gapps.
Whats the best fool proof method to flash a new ROM with what I have and are there any simple one file ROM/ZIP/ Blob etc.. file that would do what I want?
Thank you.
Click to expand...
Click to collapse
Congratulations! Everything you did looks fine. So you are ready to install a custom rom. I would like to suggest one of the best: http://forum.xda-developers.com/transformer-tf300t/development/rom-t3453702 (You may follow up the tread and report there!)
Please take care very exactly on the installation instruction in post #1 given by Timduru. And don't forget that you need Kang TWRP [email protected] Download here: http://forum.xda-developers.com/transformer-tf300t/development/recovery-twrp-t3046479. That's mandatory!
Good luck!
ebonit said:
Congratulations! Everything you did looks fine. So you are ready to install a custom rom. I would like to suggest one of the best: http://forum.xda-developers.com/transformer-tf300t/development/rom-t3453702 (You may follow up the tread and report there!)
Please take care very exactly on the installation instruction in post #1 given by Timduru. And don't forget that you need Kang TWRP [email protected] Download here: http://forum.xda-developers.com/transformer-tf300t/development/recovery-twrp-t3046479. That's mandatory!
Good luck!
Click to expand...
Click to collapse
Thanks. As simple as the process was, as a noob (first time attempting this) I was really concerned about screwing this up and bricking my tablet.
The one you linked to was one of the ones I was considering and hence my question regarding what works with what I have already done. The noob mind (mine anyways) finds a dozen questions at every turn. In this case I would ask the following:
Q-Do I have to use Kang TWRP?
Q-How is it different than the TWRP I used on my Tablet?
Q-Will I need to constantly change TWRP versions depending on what ROM I want to use?
Q-Is there a danger to switching TWRPs?
Q-Doesn't flashing SuperSU after I flash Gapps overright and erase SuperSU or is there some unique way to flash (push?) both at the same time?
Q-Many more I'm sure!
To the noob, almost all the instructions I read appear to be written for someone who as done this many times. The level of detail needed for the novice is just not there or lost between the jargon used, with many steps not fleshed out because the author assumes a certain level of expertise.
I will definitely read these threads as best I can, but in the interim, is there any ROM that are known to be able to be flashed via the TWRP I currently have? The author of the version I used certainly made it seem like it was that simple, load the ROM/ zip file onto the MicroSD card and when in Custom recovery simply use the INSTALL feature to navigate to the file and press a button to flash and ..."BAM!!" you are running a new ROM.
ebonit said:
...
Please take care very exactly on the installation instruction in post #1 given by Timduru. And don't forget that you need Kang TWRP [email protected] Download here: http://forum.xda-developers.com/transformer-tf300t/development/recovery-twrp-t3046479. That's mandatory!
Good luck!
Click to expand...
Click to collapse
That version of KANG appears to be dead, as the thread has been closed and abondoned by the OP. So no new questions or help there....
Can I install that version over the top of my current version of TWRP the same way I did the first time? (change file to TWRP.blob etc.)
broderp said:
That version of KANG appears to be dead, as the thread has been closed and abondoned by the OP. So no new questions or help there....
Can I install that version over the top of my current version of TWRP the same way I did the first time? (change file to TWRP.blob etc.)
Click to expand...
Click to collapse
Please don't brick your tablet. First download Kang TWRP. It isn't dead. Try this https://www.androidfilehost.com/?fid=24052804347781183.
broderp said:
Can I install that version over the top of my current version of TWRP the same way I did the first time? (change file to TWRP.blob etc.)
Click to expand...
Click to collapse
Yes you can.
However Kang TWRP is a xxx.img file. You also can use your current TWRP and flash the image file. Attached you will find an image and a zip version.
ebonit said:
Please don't brick your tablet. First download Kang TWRP. It isn't dead. Try this https://www.androidfilehost.com/?fid=24052804347781183.
Click to expand...
Click to collapse
Sorry, bad choice of words on my part. By dead I meant that the thread was closed and I'm concerned getting answers would be harder as the OP was no longer actively looking there for questions.
ebonit said:
Yes you can.
However Kang TWRP is a xxx.img file. You also can use your current TWRP and flash the image file. Attached you will find an image and a zip version.
Click to expand...
Click to collapse
Ok, so if I read your comment correctly, I can copy the .img file to an SD card, boot into recovery and flash it from there OR I can fire up fastboot and the same steps I originally did to install custom recovery from my PC to accomplish the same thing... either way I should still have custom recovery, but with the KANG version. Right?
THANKS TO BOTH OF YOU FOR RESPONDING TO MY PREVIOUS POST. I appreciate the support.
Oh no....
Well crap. I put the .img file on my SD card and boot the tablet into recovery, I flashed the .img file to the rovery not boot partition. All appeared well....but when I go back to see if I have KANG recovery, it hangs anbd says Booting Failure Unrecoverable bootloader error (0x000000000)
EDIT: After I cleaned my pants, I used abd and fastboot to flash the original Blob file using my PC. This restored the custom recovery. I was freaking out for a few minutes.
I didn't change the file name of the kang .img file. Should I have done something different?
EDIT: Successful recovery to Kang2.8.7.2 !! :good::good: I used adb and my PC to send the .img file (renamed "twrpkang.img" for simplicity) and it worked great. I'm a pro..:silly:
broderp said:
Well crap. I put the .img file on my SD card and boot the tablet into recovery, I flashed the .img file to the rovery not boot partition. All appeared well....but when I go back to see if I have KANG recovery, it hangs anbd says Booting Failure Unrecoverable bootloader error (0x000000000)
Click to expand...
Click to collapse
Bad luck! Could you please describe what does it mean? : "I flashed the .img file to the rovery not boot partition."
ebonit said:
Bad luck! Could you please describe what does it mean? : "I flashed the .img file to the rovery not boot partition."
Click to expand...
Click to collapse
Not sure what I did wrong. I tried to do it within the old recovery menu and it hosed it. It found the file and mounted it successfully, but it seemed weird to be within the partition I was overwriting and writing to it. Kind of like you cant install windows while your using Windows...
The new version is much smoother.... Thanks, not to learn about this gapps super SU and how to flash all of these and in what order along with the ROM..as well as this wipe vs format thing...so confusing...

How do I install Clockworkmod on my SM-G920F?

I've tried ROM Manager via Play Store but ROM Manager doesn't list Samsung Galaxy S6 as one of compatible devices. Only S3 is listed. I've already tried Googling it but can't find anything. I'd really appreciate any help.
Clockworkmod & ROM Manager is really outdated and should'nt be used.
forumber2 said:
Clockworkmod & ROM Manager is really outdated and should'nt be used.
Click to expand...
Click to collapse
I see. It looks like TWRP is the other option. But CWM is one of the requirements for this:
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
Thoughts?
E: Looks like TWRP will do. Where should I look for installation guides?
I tried using TWRP Manager from Play Store but that didn't work. The app is just stuck on the start screen. I guess I really need to use ADB for this.
RelQM said:
I see. It looks like TWRP is the other option. But CWM is one of the requirements for this:
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
...
Click to expand...
Click to collapse
CWM was written in that thread because was the standar recovery for almost every phone, but TWRP on S6 is a must because the only CWM based (Philz by arter) for S6 is too out dated.
For get TWRP just download the latest from the TWRP official website for S6 and flash through Odin, then you're done.
CWM was written in that thread because was the standar recovery for almost every phone, but TWRP on S6 is a must because the only CWM based (Philz by arter) for S6 is too out dated.
For get TWRP just download the latest from the TWRP official website for S6 and flash through Odin, then you're done.
Click to expand...
Click to collapse
Thanks a lot! I wouldn't have known that without reading through the entire thread. I really appreciate it.
TENN3R said:
CWM was written in that thread because was the standar recovery for almost every phone, but TWRP on S6 is a must because the only CWM based (Philz by arter) for S6 is too out dated.
For get TWRP just download the latest from the TWRP official website for S6 and flash through Odin, then you're done.
Click to expand...
Click to collapse
Sorry to bother you again. But there are two files with the same version on that page. One is "twrp-3.0.2-1-zeroflte.img.tar" and the other is "twrp-3.0.2-1-zeroflte.img." What does .tar mean and what difference does it make? I honestly have no clue which one to use and what to do with them.
E: After a couple of Google results, it looks like .tar is some kind of archive. Although I still don't know how to use it.
OK so apparently, I need the .tar file because that's what ODIN uses. But I would still be happy to know what the other file is used for. I'll post results for anyone who may have the same questions.
Just flashed TWRP using ODIN. Everything looks fine. Also created NANDroid backup. TWRP up and running! Thanks for the help, @TENN3R.
RelQM said:
Sorry to bother you again. But there are two files with the same version on that page. One is "twrp-3.0.2-1-zeroflte.img.tar" and the other is "twrp-3.0.2-1-zeroflte.img." What does .tar mean and what difference does it make? I honestly have no clue which one to use and what to do with them.
E: After a couple of Google results, it looks like .tar is some kind of archive. Although I still don't know how to use it.
OK so apparently, I need the .tar file because that's what ODIN uses. But I would still be happy to know what the other file is used for. I'll post results for anyone who may have the same questions.
Just flashed TWRP using ODIN. Everything looks fine. Also created NANDroid backup. TWRP up and running! Thanks for the help, @TENN3R.
Click to expand...
Click to collapse
Perfect, yes Odin format is .tar, but if you want just to update your TWRP you can download the .img (new version from site) and flash directly from TWRP :good:
TENN3R said:
Perfect, yes Odin format is .tar, but if you want just to update your TWRP you can download the .img (new version from site) and flash directly from TWRP :good:
Click to expand...
Click to collapse
Thanks again! You're the best!

Categories

Resources