Develop Bugs

Unlocked Bootloader for 10.3

Will there eventually be an app for unlocking the bootloader on the 10.3 firmware? I don't have the factory cable and it sounds like a lot of people have bricked their device doing the downgrade to 10.2.

I hope so. I am not gonna even try it... Lol instead rooted it and used Kindlefree app to install Nova and used titanium backup. So it's "like" Android but not quite lol....
Sent from my Nexus 4 using xda app-developers app

It worked for me even with the 10.3.1 bootloader. It seems that the exploit is not closed yet.
Sent from my A2109A using Tapatalk HD

I can confirm that the utilities still work fine with the latest version of the kindle software, so you shouldn't even need to downgrade.

flopower1996 said:
It worked for me even with the 10.3.1 bootloader. It seems that the exploit is not closed yet.
Sent from my A2109A using Tapatalk HD
Click to expand...
Click to collapse
But if I downgrade my bootloader I won't have to use the whole 2nd bootloader method and all that right? Won't I then just be able to use some utility to flash TWRP and then flash a ROM? This Kindle thing is probably a little more intimidating than anything else I've messed with. I have mine rooted and a bunch of other hacks but I want pure Android on. I don't want a brick though..
Sent from my Nexus 4 using xda app-developers app
---------- Post added at 01:58 PM ---------- Previous post was at 01:58 PM ----------
jwort93 said:
I can confirm that the utilities still work fine with the latest version of the kindle software, so you shouldn't even need to downgrade.
Click to expand...
Click to collapse
Which utility did you use and did you need a fastboot cable?
Sent from my Nexus 4 using xda app-developers app

You're going to need the second boot loader no matter what
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

mindmajick said:
You're going to need the second boot loader no matter what
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Ok so if I use this http://forum.xda-developers.com/showthread.php?t=2216285 to downgrade my current bootloader then use this http://forum.xda-developers.com/showthread.php?t=2106463 to flash the freedom boot img and TWRP then I can just flash a ROM like normal through TWRP. Right?
Sent from my Nexus 4 using xda app-developers app

jcnbama said:
Ok so if I use this http://forum.xda-developers.com/showthread.php?t=2216285 to downgrade my current bootloader then use this http://forum.xda-developers.com/showthread.php?t=2106463 to flash the freedom boot img and TWRP then I can just flash a ROM like normal through TWRP. Right?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
No need to downgrade the bootloader. Install the apk from the dev. Thread and click install. Nothing else.
Sent from my A2109A using Tapatalk HD

flopower1996 said:
No need to downgrade the bootloader. Install the apk from the dev. Thread and click install. Nothing else.
Sent from my A2109A using Tapatalk HD
Click to expand...
Click to collapse
What about all that craziness I have been reading about locking up the bootloader due to the 10.3.1 bootloader? I can just forget about that and install that apk file and THEN I would be able to flash a ROM via TWRP? I thought that the thread said that this tool said it was for the old bootloader. This is great news! Can you confirm this? Are we on the same page?
Sent from my KFOT using xda app-developers app

jcnbama said:
What about all that craziness I have been reading about locking up the bootloader due to the 10.3.1 bootloader? I can just forget about that and install that apk file and THEN I would be able to flash a ROM via TWRP? I thought that the thread said that this tool said it was for the old bootloader. This is great news! Can you confirm this? Are we on the same page?
Sent from my KFOT using xda app-developers app
Click to expand...
Click to collapse
Yes the exploit stil exists. Tested by myself withe the 10.3.1 bootloader and confirmed by other people. Enjoy the freedom of flashing!
Sent from my A2109A using Tapatalk HD

flopower1996 said:
Yes the exploit stil exists. Tested by myself withe the 10.3.1 bootloader and confirmed by other people. Enjoy the freedom of flashing!
Sent from my A2109A using Tapatalk HD
Click to expand...
Click to collapse
Oh my goodness. This absolutely worked. WHY didn't I meet you like 3 days ago? LOL Any noob to Kindle should know about this. Root + Run a simple .apk WOW. Any thoughts on the best Rom going right now for KF2? Kernel?

jcnbama said:
Oh my goodness. This absolutely worked. WHY didn't I meet you like 3 days ago? LOL Any noob to Kindle should know about this. Root + Run a simple .apk WOW. Any thoughts on the best Rom going right now for KF2? Kernel?
Click to expand...
Click to collapse
Well, i personally use the aosp Rom by hashcode. It`s simple, nice and clean. But what you are using is your own choice. Flash different Roms and make your own mind.
Sent from my A2109A using Tapatalk HD

flopower1996 said:
Well, i personally use the aosp Rom by hashcode. It`s simple, nice and clean. But what you are using is your own choice. Flash different Roms and make your own mind.
Sent from my A2109A using Tapatalk HD
Click to expand...
Click to collapse
So, it looks like I have screwed something up. This figures as my luck is terrible with this freegin Kindle. So I got TWRP recovery working fine. I DL Cyanogenmod 10.1 and Gapps accordingly. Went into TWRP of course made a backup, then went to flash. I wiped EVERYTHING and went to flash the ROM. I received the error <Could Not Open .zip> So now I have nothing on file except a bad .zip. I did re-download the ROM assuming it was bad and restored my TWRP backup. Now I am stuck in what appears to be a Kindle Bootloop. The Kindle Fire (Orange) logo comes up, a few seconds later it blinks back off again and recycles. Now what? I can't get the Kindle to boot so I can put the .zip back on the machine. I am STUCK. This sucks... :crying:

jcnbama said:
So, it looks like I have screwed something up. This figures as my luck is terrible with this freegin Kindle. So I got TWRP recovery working fine. I DL Cyanogenmod 10.1 and Gapps accordingly. Went into TWRP of course made a backup, then went to flash. I wiped EVERYTHING and went to flash the ROM. I received the error <Could Not Open .zip> So now I have nothing on file except a bad .zip. I did re-download the ROM assuming it was bad and restored my TWRP backup. Now I am stuck in what appears to be a Kindle Bootloop. The Kindle Fire (Orange) logo comes up, a few seconds later it blinks back off again and recycles. Now what? I can't get the Kindle to boot so I can put the .zip back on the machine. I am STUCK. This sucks... :crying:
Click to expand...
Click to collapse
You have fastboot cable?
--
Sent from my mind to your screen.

mindmajick said:
You have fastboot cable?
--
Sent from my mind to your screen.
Click to expand...
Click to collapse
It's on the way lol. Ordered it today. What is terrible is I thought I was doing the right thing by doing a backup up TWRP. Just in case ya know? It *usually* works. Now I just need to know the next steps so I can get back where I need to be. Thought I was home free with TWRP.
Sent from my Nexus 4 using xda app-developers app

jcnbama said:
It's on the way lol. Ordered it today. What is terrible is I thought I was doing the right thing by doing a backup up TWRP. Just in case ya know? It *usually* works. Now I just need to know the next steps so I can get back where I need to be. Thought I was home free with TWRP.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I did the exact same thing when i got my kindle back in January. (Yeah, i had to order my cable right after that )
For some reason I've never been able to restore a stock TWRP backup on the kf2. It always borks the bootloader.
I know there is a special requirement that our bootloader uses a file called stack on the system partition- that's why you can't get into recovery now (when you wiped the system it wiped the stack file which let's us run the second bootloader.)
Anyway, Once you have the fastboot cable its really easy to get things going again. Pm me if you need a hand.. I've been through this myself a few times lol.
If you ever end up in the same situation again where you wiped the system and the zip is bad... Stay in twrp and use "adb sideload" to push a good zip from pc.
--
Sent from my mind to your screen.

mindmajick said:
I did the exact same thing when i got my kindle back in January. (Yeah, i had to order my cable right after that )
For some reason I've never been able to restore a stock TWRP backup on the kf2. It always borks the bootloader.
I know there is a special requirement that our bootloader uses a file called stack on the system partition- that's why you can't get into recovery now (when you wiped the system it wiped the stack file which let's us run the second bootloader.)
Anyway, Once you have the fastboot cable its really easy to get things going again. Pm me if you need a hand.. I've been through this myself a few times lol.
If you ever end up in the same situation again where you wiped the system and the zip is bad... Stay in twrp and use "adb sideload" to push a good zip from pc.
--
Sent from my mind to your screen.
Click to expand...
Click to collapse
I actually tried the side load through TWRP. When I typed "adb devices" it showed my device in host mode and the file wouldn't transfer although TWRP was in adb sideload mode. But then I just thought "oh well guess I'll restore my backup" lol. Yeah that didn't work out..
Sent you a P. M. BTW. thanks again!
Sent from my Nexus 4 using xda app-developers app

Thanks for the info guys. I'm glad I didn't have to change the firmware. The whole process was super easy and now I'm running jb 4.2. For those reading, just root->install one touch apk->make backup in twrp->factory reset->flash rom and gapps->success!

punkcitykid said:
Thanks for the info guys. I'm glad I didn't have to change the firmware. The whole process was super easy and now I'm running jb 4.2. For those reading, just root->install one touch apk->make backup in twrp->factory reset->flash rom and gapps->success!
Click to expand...
Click to collapse
**As a special note however DO NOT restore your factory backup if you have trouble. You will end up like me. Bootlooping with a fast boot cable in the mail.** if I could go back in time I would've downloaded the files via a hard line rather than slow wifi and maybe even double downloaded.. Oh well. This is a learning opportunity.
Sent from my Nexus 4 using xda app-developers app

HELP! Somehow my phone got bricked and I need help ASAP

Hi guys, longtime lurker but I've been active on Android Central. Not a noob when it comes to flashing roms, but I think I did something wrong today when trying to flash liquid smooth, coming from cm10.1. Can someone please help me, PM me and I can get a chat or phone call started?
Please and thank you.

Please tell us what you did, and what the phone is doing? Can you get into custom recovery or download mode?
Sent from the future via Tapatalk 4

Ok. So I was running CM10.1 RC4 I think, and running TWRP 2.4 or something around that version. I downloaded the latest liquidsmooth apk, gapps, and BMS kernel. Wiped cache, dalvik, the rom and system. Then I kept getting this error while wiping:
E:error not a directory
error opening "/data/lost+found
Then I flashed liquidsmooth, gaps 3/1/2013, and BMS and restarted. What was weird was The rom flashed ok and I think the kernel was fine, but I had no gapps upon booting into liquid smooth. Redid the wiping process and installing process, same result. Started googling how to fix the error I was getting and someone recommended wiping the data.
So I wiped my data. A big red triangle showed up and I thought I was doing the right thing. When I try to boot my phone, its stuck on the "Samesung Galaxy S3" screen. I try to go into recovery mode, but all that shows up is the TWRP splash screen and then my phone reboots into the bootloop.
I'd appreciate any help, I know i screwed up here.
Edit: I can get into download mode evidently, and it shows my binary count as 1.

Ok so your saying you can not boot into TWRP?
Edit: do not panic, the fact that you get to the Samsung screen is good, you are not bricked.
If you can not successfully boot into TWRP power the phone off and do power+volume down +home at the same time and see if you can get into download mode? If you can then you will need a computer and we can reflash to stock.
Sent from the future via Tapatalk 4

edfunkycold said:
Ok so your saying you can not boot into TWRP?
Edit: do not panic, the fact that you get to the Samsung screen is good, you are not bricked.
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
I can't get into TWRP. All that shows is the splash screen and then reboots. So I cant get to any of the wiping/installing options.

I think you just formated everything, as long as it still boots up, try reflashing TWRP, then try flashing again
Sent from my Nexus 4 using xda app-developers app

whisper13 said:
I think you just formated everything, as long as it still boots up, try reflashing TWRP, then try flashing again
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
How would I reflash TWRP?

If you can get into download mode you can use odin to return to stock using these files http://www.sxtpdevelopers.com/showthread.php?t=233
Real simple. Then you would just reflash your custom recovery and root your phone again.
Sent from the future via Tapatalk 4

Would using this guide be better?

Next time don't flash the ROM, the gapps and the kernel all at once.
Make sure you flashed the 3.4 kernel as well. If you downloaded the 3.0 ... You soft bricked your phone. Its fixable.
---------- Post added at 02:47 PM ---------- Previous post was at 02:44 PM ----------
@xplode196

xxStarbucksxx said:
Next time don't flash the ROM, the gapps and the kernel all at once.
Make sure you flashed the 3.4 kernel as well. If you downloaded the 3.0 ... You soft bricked your phone. Its fixable.
---------- Post added at 02:47 PM ---------- Previous post was at 02:44 PM ----------
@xplode196
Click to expand...
Click to collapse
Oh I wasn't aware I wasn't supposed to do that. I mean generally I never do that, it was just this once. How should I flash things the right way? And yeah it was the 3.4 kernel.

xplode196 said:
Oh I wasn't aware I wasn't supposed to do that. I mean generally I never do that, it was just this once. How should I flash things the right way? And yeah it was the 3.4 kernel.
Click to expand...
Click to collapse
Wipe/factory
Wipe Dalvik
Wipe cache
Flash ROM/gapps.
Set your phone settings to the way you prefer. Always let it set for about 5 minutes. Make a back up.
THEN flash kernel, giving that its flash able, which BMS is. Let kernel set for about 5 minutes as well and tweak and tinker as you please.

xplode196 said:
Would using this guide be better?
Click to expand...
Click to collapse
Idk that thread is over a year old. If you want outdated stuff.
Sent from the future via Tapatalk 4

edfunkycold said:
Idk that thread is over a year old. If you want outdated stuff.
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
Okay everythings working, rooted and stuff. But the persistent problem is when I try to wipe stuff in recovery it says:
E:error: no such file or directory
E: error opening '/data/lost+found'

xplode196 said:
Okay everythings working, rooted and stuff. But the persistent problem is when I try to wipe stuff in recovery it says:
E:error: no such file or directory
E: error opening '/data/lost+found'
Click to expand...
Click to collapse
Go download GooManager app and update your TWRP version.
Sent from the future via Tapatalk 4

xplode196 said:
Okay everythings working, rooted and stuff. But the persistent problem is when I try to wipe stuff in recovery it says:
E:error: no such file or directory
E: error opening '/data/lost+found'
Click to expand...
Click to collapse
You're most likely getting that when doing a Dalvik wipe. Just continue to wipe you're dalvik cache. And everything else before flashing your new ROM.

CWM not installing! GT-i9505

Can not for the life of me get this too boot into CWM.
I have used CF auto root and confirmed I have root access, I have deleted the recovery file in system/etc and no matter what I do, CWM just won't boot, it just keeps booting into android recovery. I even tried taking the battery out as soon as CWM is finished to prevent a boot into the os and then trying to boot into it, still nada.
Is there something I am missing?

Are you already rooted or are you trying to install CWM first and then root?
Sent from my SGH-M919 using xda app-developers app
---------- Post added at 02:38 PM ---------- Previous post was at 02:35 PM ----------
Sorry just re-read lol. Why don't you use TWRP? Personally I like that recovery better. Since you're already rooted just install goomanager and install it through there. Or you could also install CWM through rom manager.
Sent from my SGH-M919 using xda app-developers app

marcoxx626 said:
Are you already rooted or are you trying to install CWM first and then root?
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Already rooted, I read a guide that says delete install.recovery.sh, which I thought I did but it is not actually deleting, says it is but just does not disappear? wtf
EDIT: just seen your edit, I used clockwork before on my DHD, that is why i chose this. Will try it via ROM manager, if all fails I shall try your recovery choice, TY.

Ok this is weird, root checker confirms I have root, I can grant things root access (rom manager, goomanager) but they always fail when setting the permissions, also can't delete that file in system/etc...so my device is like half rooted or something? Any ideas?

Gibbo3771 said:
Ok this is weird, root checker confirms I have root, I can grant things root access (rom manager, goomanager) but they always fail when setting the permissions, also can't delete that file in system/etc...so my device is like half rooted or something? Any ideas?
Click to expand...
Click to collapse
Why are you deleting system files? I've never had to delete anything when rooting or flashing a recovery.
Sent from my SGH-M919 using xda app-developers app

marcoxx626 said:
Why are you deleting system files? I've never had to delete anything when rooting or flashing a recovery.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
install.recovery.sh installed reflashes the recovery system to the android default, I am trying to flash to clockwordmod but it just keeps booting into android recovery no matter what i do, root checker confirms i am rooted.
I am just stumped on what to do....i can't get any custom recovery on this.
Goomanager says it can not find one for my phone and rom manager says the s4 is not even supported, all apps are up to date. what gives?

Gibbo3771 said:
install.recovery.sh installed reflashes the recovery system to the android default, I am trying to flash to clockwordmod but it just keeps booting into android recovery no matter what i do, root checker confirms i am rooted.
I am just stumped on what to do....i can't get any custom recovery on this.
Goomanager says it can not find one for my phone and rom manager says the s4 is not even supported, all apps are up to date. what gives?
Click to expand...
Click to collapse
try TWRP through goomanager. its better imo, and installed in seconds with no problem. didnt have to delete anything either.
oh and btw, if this is a gt-i9505 related problem, youre in the wrong forums... might help more over in the gt-i9505 forums

The Illest 619 said:
try TWRP through goomanager. its better imo, and installed in seconds with no problem. didnt have to delete anything either.
oh and btw, if this is a gt-i9505 related problem, youre in the wrong forums... might help more over in the gt-i9505 forums
Click to expand...
Click to collapse
nah goomanager/rom manager was not installing either CWM or TWRP, however i done a factory reset of the phone, redone the rooting process and installed TWRP manually, fixed now.
Where is this mhystical forum section?

Gibbo3771 said:
nah goomanager/rom manager was not installing either CWM or TWRP, however i done a factory reset of the phone, redone the rooting process and installed TWRP manually, fixed now.
Where is this mhystical forum section?
Click to expand...
Click to collapse
http://forum.xda-developers.com/forumdisplay.php?f=2162
thats for the correct version of your phone

The Illest 619 said:
http://forum.xda-developers.com/forumdisplay.php?f=2162
thats for the correct version of your phone
Click to expand...
Click to collapse
Probably a stupid question but I guess the roms in this section will not work with my phone? the choice here compared to there is ehm....limited hehe.

[Q] It keeps rebooting... recovery is not seandroid enforcement

Hi, I had the ROM DARTHSTALKER... and then I installed the Jedi elite to try a different one, but i wanted to go back to recover some messages of a girl, so I tried to restore the DARTHSTALKER backup from the ROM Jedi. It ended up in a loop, rebooting constantly... now I tried to UN-root it to begin from 0 and it keeps rebooting and telling me at the beginning in red: recovery is not seandroid enforcement and then some times if it loads, i says: optimizing apps... and then it says Finishing boot (it stays there for a while) and then the T-Mobil logo appears (it stays there for a while) and it reboot... After that it boots until it says: "process system isn't responding" and I have 2 options, wait or close, none of them work
How can I fix this I'm using TWRP Recovery
Thanks guys

Arturofm2 said:
Hi, I had the ROM DARTHSTALKER... and then I installed the Jedi elite to try a different one, but i wanted to go back to recover some messages of a girl, so I tried to restore the DARTHSTALKER backup from the ROM Jedi. It ended up in a loop, rebooting constantly... now I tried to UN-root it to begin from 0 and it keeps rebooting and telling me at the beginning in red: recovery is not seandroid enforcement and then some times if it loads, i says: optimizing apps... and then it says Finishing boot (it stays there for a while) and then the T-Mobil logo appears (it stays there for a while) and it reboot... After that it boots until it says: "the operating system stopped working" and I have 2 options, wait or close, none of them work
How can I fix this ? I'm using TWRP Recovery
Thanks guys
Click to expand...
Click to collapse
you will need manually flash most likely the saberkernel green. Once you have it up and running, update your twrp. The older versions of recovery had restore issues.

dragonstalker said:
you will need manually flash most likely the saberkernel green. Once you have it up and running, update your twrp. The older versions of recovery had restore issues.
Click to expand...
Click to collapse
An answer! Finally hope! I work with my phone.
Ok, but how do i introduce the kernel in my phone if when I plug it in the pc in download mode it seems to load but it doesn't load in My PC (the drivers are ok)
Is there anyway to install it from the pc using a program like odin? And what do you mean the old version? Which one do u recommend me?

Arturofm2 said:
An answer! Finally hope! I work with my phone.
Ok, but how do i introduce the kernel in my phone if when I plug it in the pc in download mode it seems to load but it doesn't load in My PC (the drivers are ok)
Is there anyway to install it from the pc using a program like odin? And what do you mean the old version? Which one do u recommend me?
Click to expand...
Click to collapse
Download the kernel .zip file and place on your sdcard . Hold down home+power+volup buttons to boot into recovery. Then flash the zip like any thing else.
Once back into the rom, use goomanager from play store. click menu and install recovery scrpit. Once done, it will ask you do you want to install twrp 2.6.3.7. yes you want to do this. Twrp 2.6.3.1 dn has known issues with the Note 3

dragonstalker said:
Download the kernel .zip file and place on your sdcard . Hold down home+power+volup buttons to boot into recovery. Then flash the zip like any thing else.
Once back into the rom, use goomanager from play store. click menu and install recovery scrpit. Once done, it will ask you do you want to install twrp 2.6.3.7. yes you want to do this. Twrp 2.6.3.1 dn has known issues with the Note 3
Click to expand...
Click to collapse
But what I'm saying is that I can't see my device on my pc, when I connect it, it doesn't show, and I have the driver installed. It's like it's loading but it never loads

Arturofm2 said:
But what I'm saying is that I can't see my device on my pc, when I connect it, it doesn't show, and I have the driver installed. It's like it's loading but it never loads
Click to expand...
Click to collapse
It's not going to. It does not have to time load the drivers for you to interact with. You will need to pull your sdcard out of the phone.

dragonstalker said:
It's not going to. It does not have to time load the drivers for you to interact with. You will need to pull your sdcard out of the phone.
Click to expand...
Click to collapse
I think you don't understand my friend: http://img819.imageshack.us/img819/4251/3pih.png

Arturofm2 said:
I think you don't understand my friend: http://img819.imageshack.us/img819/4251/3pih.png
Click to expand...
Click to collapse
Think he is saying you will need an SDCARD for this and u will need to load the file on the SDCARD first and then put it back in ur phone
Sent from my SM-N900T using Tapatalk

droidkevlar said:
Think he is saying you will need an SDCARD for this and u will need to load the file on the SDCARD first and then put it back in ur phone
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Oh ok, I have an external sdcard already, but how do I copy the kernel inside the sdcard without the phone?

When you made your backup, did you also back up the EFS.
Sent from my SM-N900T using xda premium

pitbull292006 said:
When you made your backup, did you also back up the EFS.
Click to expand...
Click to collapse
I'm guessing he did not...

the kernel file is a zip file. Put the SDcard in your computer, download the file onto your SDcard put the SDcard back into your phone and install it using TWRp
Sent from my SM-N900T using xda premium

pitbull292006 said:
When you made your backup, did you also back up the EFS.
Sent from my SM-N900T using xda premium
Click to expand...
Click to collapse
dragonstalker I don't have the port to put an sdcard in my pc
I backed up everything and now I was seeing in the jedi rom that it comes with the saberkernel green...
I'm thinking to go tomorrow to Tmobil to see if i can change it, what a f..ing crap...

dragonstalker said:
the kernel file is a zip file. Put the SDcard in your computer, download the file onto your SDcard put the SDcard back into your phone and install it using TWRp
Sent from my SM-N900T using xda premium
Click to expand...
Click to collapse
On here's what you do, as I had the EXACT same problem that you have. I fixed my brickloop by doing the following:
(I would backup your efs partition before doing this, just for completeness sake)*
Installed Stock firmware via Odin,*
Installed TWRP 2.6.3.2 via odin, rebooted to recovery
Did an "adb shell" when phone is in recovery mode to run commands via TWRP
From the ADB shell: Wiped the EFS partition with the following command:
mke2fs /dev/block/mmcblk0p12*
mkdir /efs
mount -t ext4 /dev/block/mmcblk0p12 /efs
(the last two commands probably did nothing, but thats what I did anyway)
Did a Factory Reset*
Then... reboot to system
Afterwards, no more boot looping, the phone successfully registered on the mobile network, and my IMEI is there and correct. Seems like the EFS partition can rebuild itself now I guess...These commands can also be ran from TWRP
Sent from my SM-N900T using xda premium
---------- Post added at 10:54 PM ---------- Previous post was at 10:48 PM ----------
Those commands can also be ran from TRWP via the terminal option
Sent from my SM-N900T using xda premium

pitbull292006 said:
On here's what you do, as I had the EXACT same problem that you have. I fixed my brickloop by doing the following:
(I would backup your efs partition before doing this, just for completeness sake)*
Installed Stock firmware via Odin,*
Installed TWRP 2.6.3.2 via odin, rebooted to recovery
Did an "adb shell" when phone is in recovery mode to run commands via TWRP
From the ADB shell: Wiped the EFS partition with the following command:
mke2fs /dev/block/mmcblk0p12*
mkdir /efs
mount -t ext4 /dev/block/mmcblk0p12 /efs
(the last two commands probably did nothing, but thats what I did anyway)
Did a Factory Reset*
Then... reboot to system
Afterwards, no more boot looping, the phone successfully registered on the mobile network, and my IMEI is there and correct. Seems like the EFS partition can rebuild itself now I guess...These commands can also be ran from TWRP
Sent from my SM-N900T using xda premium
---------- Post added at 10:54 PM ---------- Previous post was at 10:48 PM ----------
Those commands can also be ran from TRWP via the terminal option
Sent from my SM-N900T using xda premium
Click to expand...
Click to collapse
I'm going tomorrow to the store, let's see what happens, but I don't understand.. what failed? the TWRP?

Arturofm2 said:
I'm going tomorrow to the store, let's see what happens, but I don't understand.. what failed? the TWRP?
Click to expand...
Click to collapse
What version of TWRP are you using
Sent from my SM-N900T using xda premium

There not going to do anything for you at the store if your Knox counter is tripped, that voids the warranty instantly......
Sent from my SM-N900T using xda app-developers app

Quickvic30 said:
There not going to do anything for you at the store if your Knox counter is tripped, that voids the warranty instantly......
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
That's not true they don't check anything even you go in there and relaxed a defective device. You just wanna rain on his parade
Sent from my SM-N900T using Tapatalk
---------- Post added at 11:00 AM ---------- Previous post was at 11:00 AM ----------
janjannsen99 said:
That's not true they don't check anything even you go in there and return a defective device. You just wanna rain on his parade
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Sent from my SM-N900T using Tapatalk

I'm using the latest version of teamwin rec. I heard they have problems but when will they release the new version?
I tryied to put the phone back in stock rom and.that.doesn't even work, come on guys, you know more than me about this, what could I do?

Arturofm2 said:
I'm going tomorrow to the store, let's see what happens, but I don't understand.. what failed? the TWRP?
Click to expand...
Click to collapse
Not to sound like a jerk...but this is the reason why companies lock down bootloaders and what not. You can fix this issue that you caused by following a few steps or getting an SDCARD reader for your computer and transfer the files to it that way. They are dirt cheap. It is not Tmobiles fault that you screwed up a flash. Just my 2 cents.

please help! just got it tried rooting possibly bricked?!

I've owned 3 Samsung devices and never had an issue. I downloaded the cf auto root and tried flashing it as instructed through Odin 3. I had already installed twrp before all this. It wasn't rooting properly and now it won't boot and isn't recognized in Odin anymore and I can't get into twrp. Please help!

Not being recognized... When I power it down it just keeps trying to boot bit won't go past the Samsung screen am I F'ed?!

RussellEstridge25 said:
Not being recognized... When I power it down it just keeps trying to boot bit won't go past the Samsung screen am I F'ed?!
Click to expand...
Click to collapse
dont you still have TWRP installed?
Can you get in TWRP?
Try to hold power button until it turns off. Then turn it back on
PS: OFF TOPIC:
You can root using TWRP, I was able to root mine. I think thats in the advanced settings option

RussellEstridge25 said:
I've owned 3 Samsung devices and never had an issue. I downloaded the cf auto root and tried flashing it as instructed through Odin 3. I had already installed twrp before all this. It wasn't rooting properly and now it won't boot and isn't recognized in Odin anymore and I can't get into twrp. Please help!
Click to expand...
Click to collapse
How did you install TWRP before you obtained root?

kkretch said:
How did you install TWRP before you obtained root?
Click to expand...
Click to collapse
Used the gooim app. I actually got it booted now. Left in the charger for a while and tried Odin avian and it surprisingly recognized it. And oddly enough... Now I'm rooted. But now I wanna know how to go back completely stock and wipe the flash count. Any advice?

RussellEstridge25 said:
Used the gooim app. I actually got it booted now. Left in the charger for a while and tried Odin avian and it surprisingly recognized it. And oddly enough... Now I'm rooted. But now I wanna know how to go back completely stock and wipe the flash count. Any advice?
Click to expand...
Click to collapse
You can not remove the warranty bit 1 count.

kkretch said:
You can not remove the warranty bit 1 count.
Click to expand...
Click to collapse
You serious? So its warranty broken for good? You don't think anyone will ever find a way?

Never had a samsung hold that count. Never seen warranty bit count either tho. Should have read up more. Dumb move. So is it possible to indoor for ota?

RussellEstridge25 said:
You serious? So its warranty broken for good? You don't think anyone will ever find a way?
Click to expand...
Click to collapse
It has to do with a new security feature "Knox"

kkretch said:
It has to do with a new security feature "Knox"
Click to expand...
Click to collapse
Oh well. Wish I woulda known that. No one to blame but myself. Hope nothing happens to it.

RussellEstridge25 said:
Never had a samsung hold that count. Never seen warranty bit count either tho. Should have read up more. Dumb move. So is it possible to indoor for ota?
Click to expand...
Click to collapse
I think you can get them if you install stock recovery.
Check out the CF-AUTO Root posts http://forum.xda-developers.com/showthread.php?t=2490805 Rooting Instructions
---------- Post added at 01:12 AM ---------- Previous post was at 01:09 AM ----------
RussellEstridge25 said:
Oh well. Wish I woulda known that. No one to blame but myself. Hope nothing happens to it.
Click to expand...
Click to collapse
It has been rumored that Samsung will not warrant the device if it is bricked but if the power button breaks they would most likely repair it.

kkretch said:
I think you can get them if you install stock recovery.
Check out the CF-AUTO Root posts http://forum.xda-developers.com/showthread.php?t=2490805 Rooting Instructions
---------- Post added at 01:12 AM ---------- Previous post was at 01:09 AM ----------
It has been rumored that Samsung will not warrant the device if it is bricked but if the power button breaks they would most likely repair it.
Click to expand...
Click to collapse
Tried but fails. I'm afraid to do anything now

kkretch said:
How did you install TWRP before you obtained root?
Click to expand...
Click to collapse
install using odin if you dont have root

Rooting device
Hi
I dont know what really happen to your device but here some things that might help.
1. Get the latest twrp zipfile should be 2.6.3
2. Unpack in a New directory on your PC - in this directory should be 2 files - one ODIN and one TWRP
3. Use the ODIn in that new directory only this Odin version will work.
4 load the TWRP file into ODIN
5 The only Oding Setting which should be changed is the Auto Re-Boot Option switch it off.
6 Than start the Load Process be patient can Take up to 6 Min.
This works i did it myself if any further question feel free to ask - ih this has helped a thanks would be nice-
Good Luck

FSkyman said:
Hi
I dont know what really happen to your device but here some things that might help.
1. Get the latest twrp zipfile should be 2.6.3
2. Unpack in a New directory on your PC - in this directory should be 2 files - one ODIN and one TWRP
3. Use the ODIn in that new directory only this Odin version will work.
4 load the TWRP file into ODIN
5 The only Oding Setting which should be changed is the Auto Re-Boot Option switch it off.
6 Than start the Load Process be patient can Take up to 6 Min.
This works i did it myself if any further question feel free to ask - ih this has helped a thanks would be nice-
Good Luck
Click to expand...
Click to collapse
Already got it all squared away but ty
Make sure to watch the sunset at least once a day

Wait so you could install twrp using gooim app? No computer needed
? I have a Mac and can't root
Sent from my GT-I9505G using xda app-developers app

tylerholbrook said:
Wait so you could install twrp using gooim app? No computer needed
? I have a Mac and can't root
Sent from my GT-I9505G using xda app-developers app
Click to expand...
Click to collapse
Nope. Twrp never actually installed using gooim. I used Odin instead