Develop Bugs

[HOW-TO] CMW on LTE Version through Rom Manager

If you have any questions, concerns or problems, please post in the CDMA post because I will no longer be checking here.

theboo7 said:
This is a guide on how to get ClockWorkMod onto your LTE Galaxy Nexus through Rom Manager
Go to market, search "Clockworkmod"
Install Rom Manager*
Open up Rom Manager and select "Flash ClockworkMod Recovery"
A pop-up will come up called "Confirm Phone Model," of course choose "Google Galaxy Nexus CDMA"
Now let it install etc, then with a File Manager** with SU access, Go to system, click "Mount R/W"(if using Root Explorer) and then scroll down until you see "recovery-from-boot.p" and rename it to "recovery-from-boot.p.bak"
Close out off your File Manager and go to Rom Manager and select "Reboot into Recovery"
There you go
You should be able to boot into CWM
* Free version works
**I used Root Explorer
Click to expand...
Click to collapse
For starters that file doesnt exist under the directory "system"

jgrimberg1979 said:
For starters that file doesnt exist under the directory "system"
Click to expand...
Click to collapse
By "that file" I'm assuming you are referring to "recovery-from-boot.p" ?

jgrimberg1979 said:
For starters that file doesnt exist under the directory "system"
Click to expand...
Click to collapse
Could be because you are on a custom ROM. I am on Android Revolution HD and I don't see it at all as well. I also can directly boot from ROM Manager directly into CWM. I never touched this file at all and I never looked for it.

staticx57 said:
Could be because you are on a custom ROM. I am on Android Revolution HD and I don't see it at all as well. I also can directly boot from ROM Manager directly into CWM. I never touched this file at all and I never looked for it.
Click to expand...
Click to collapse
I'm on stock 4.0.2
updated OP to reflect the OS version I'm talking about.
Accidental thanks btw

theboo7 said:
I'm on stock 4.0.2
updated OP to reflect the OS version I'm talking about.
Accidental thanks btw
Click to expand...
Click to collapse
I had to do this same thing on stock to keep the stock recovery from restoring.

jermaine151 said:
I had to do this same thing on stock to keep the stock recovery from restoring.
Click to expand...
Click to collapse
Yeah it's a known bug, that's hopefully getting worked on.

Thank you for this! Now one question if I didn't do this and the stock recovery booted what would be the steps too get this recovery installed?
Sent from my Galaxy Nexus using Tapatalk

dc iz 2 legit said:
Thank you for this! Now one question if I didn't do this and the stock recovery booted what would be the steps too get this recovery installed?
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Then you would follow the steps in the OP

What are the benefits to doing this final part. Is it necessary? Some say they didn't do this? Now on the Thunderbolt I didn't have to have rom manager installed and I could still boot into recovery. Is this the same? If I rename that file (which is in my system directory) will I be able to boot into cwm at any point?
Thanks I have done everything with the exception to this. Wondering if its necessary?
Edit: I guess I should have waited for a response because I went ahead and followed the steps in the OP and it came up with an android with a red triangle. Pulled that battery and booted up ok. Any info I need to be aware of? I wasn't able to boot into recovery from rom manager at first. I can now boot into recovery after reflashing CWM recovery but cannot do anything once I am in it?

Xirix12 said:
What are the benefits to doing this final part. Is it necessary? Some say they didn't do this? Now on the Thunderbolt I didn't have to have rom manager installed and I could still boot into recovery. Is this the same? If I rename that file (which is in my system directory) will I be able to boot into cwm at any point?
Thanks I have done everything with the exception to this. Wondering if its necessary?
Edit: I guess I should have waited for a response because I went ahead and followed the steps in the OP and it came up with an android with a red triangle. Pulled that battery and booted up ok. Any info I need to be aware of? I wasn't able to boot into recovery from rom manager at first. I can now boot into recovery after reflashing CWM recovery but cannot do anything once I am in it?
Click to expand...
Click to collapse
Flashing through ROM Manager is just a simpler way to get CWM. And I'm not sure why you would have gotten the red triangle, unless you didn't rename/delete the file in system. And I haven't heard anyone say the couldn't do anything in recovery, so I'm not sure what the problem is there.

When I try and change the file name it says insufficient permissions??
I have root...
Cwm doesn't stick though. I always have to boot reflash recovery and then boot into recovery through from manager..
Any suggestion?
Sent from my Galaxy Nexus using XDA App

civicsisedan said:
When I try and change the file name it says insufficient permissions??
I have root...
Cwm doesn't stick though. I always have to boot reflash recovery and then boot into recovery through from manager..
Any suggestion?
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Your file manager doesn't have root privileges, so until you rename/delete the file you won't be able to reboot into CWM

theboo7 said:
Your file manager doesn't have root privileges, so until you rename/delete the file you won't be able to reboot into CWM
Click to expand...
Click to collapse
This. I was using astro but changed to root explorer and changed file name. Turned phone off and went into fast boot and then recovery and it worked.
To be clear, I was able to go into recovery before. I would have to open from manager, reflash cwm and boot into recovery.
I was just unable to power phone off and boot into recovery manually. Now I can.
Sent from my Galaxy Nexus using XDA App

civicsisedan said:
This. I was using astro but changed to root explorer and changed file name. Turned phone off and went into fast boot and then recovery and it worked.
To be clear, I was able to go into recovery before. I would have to open from manager, reflash cwm and boot into recovery.
I was just unable to power phone off and boot into recovery manually. Now I can.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Okay, so glad that you got it sorted out
Sent from my Galaxy Nexus using XDA App

this step by step process was incredibly easy. thank you!!!

reflekt2099 said:
this step by step process was incredibly easy. thank you!!!
Click to expand...
Click to collapse
Your welcome
Sent from my Galaxy Nexus using XDA App

Thanks for the reply. I did rename it the file to .bak following the script to the t! I don't know what happened either. Since then I deleted the file entirely this time and reflashed the cwm seems to work a little better than before an now I can do things in cwm recovery. Hope nothing else goes crazy.
Sent from my Galaxy Nexus using Tapatalk

Xirix12 said:
Thanks for the reply. I did rename it the file to .bak following the script to the t! I don't know what happened either. Since then I deleted the file entirely this time and reflashed the cwm seems to work a little better than before an now I can do things in cwm recovery. Hope nothing else goes crazy.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Yeah, that file can cause problems with CWM on LTE, although it's a quick fix, I'm sure it's being worked on for future editions. And since you've been able to flash things, when you use the volume keys to high light options, does it skip one or two every now and then? That's only problem I seem to be having.

theboo7 said:
when you use the volume keys to high light options, does it skip one or two every now and then? That's only problem I seem to be having.
Click to expand...
Click to collapse
Same here. You gotta go slow. I selected the wrong option many times.

Can't Access Storage, no Rom Installed.

Long story short, don't have any Rom's installed on my Nexus,none on the card, can only get to Fastboot and Clockwork recovery, and can't access sd card as I can't get into Android, what the hell do I do now ?
Cheers
Adam

Use fastboot
Sent from my Galaxy Nexus using xda premium

Ahk, as you can tell, I'm not the greatest with this, I know how to use fastboot, but which img should I flash with it?

Hey, this is because the phone is not fully rooted I think. Are you sure the bootloader is unlocked and you have successfully rooted? If you go into rom manager can you flash CWM?
---------- Post added at 05:57 PM ---------- Previous post was at 05:56 PM ----------
Foxhounnd said:
Ahk, as you can tell, I'm not the greatest with this, I know how to use fastboot, but which img should I flash with it?
Click to expand...
Click to collapse
If you are going down that road check this out. Should sort you out. Good luck.
http://forum.xda-developers.com/showthread.php?t=1366806

jd1001 said:
Hey, this is because the phone is not fully rooted I think. Are you sure the bootloader is unlocked and you have successfully rooted? If you go into rom manager can you flash CWM?
---------- Post added at 05:57 PM ---------- Previous post was at 05:56 PM ----------
If you are going down that road check this out. Should sort you out. Good luck.
http://forum.xda-developers.com/showthread.php?t=1366806
Click to expand...
Click to collapse
I actually did all that

Foxhounnd said:
I actually did all that
Click to expand...
Click to collapse
D'oh!
Can you try going through the rooting process again the way you first did it?
I had this recently and when I rooted again it worked fine but it was the exact same issue. Hope it works out for you.

There's no ROM on the phone at all so what would the OP be actually rooting??
To the OP, go into CWM and then mount the SD card so Windows can read it. Then transfer the ROM you wish to use and flash it as before
Or restore the backup you obviously took before flashing a new ROM

EddyOS said:
There's no ROM on the phone at all so what would the OP be actually rooting??
To the OP, go into CWM and then mount the SD card so Windows can read it. Then transfer the ROM you wish to use and flash it as before
Or restore the backup you obviously took before flashing a new ROM
Click to expand...
Click to collapse
Yeah, forgot too, fullretard.jpg. I tried mounting, doesn't work

EddyOS said:
There's no ROM on the phone at all so what would the OP be actually rooting??
To the OP, go into CWM and then mount the SD card so Windows can read it. Then transfer the ROM you wish to use and flash it as before
Or restore the backup you obviously took before flashing a new ROM
Click to expand...
Click to collapse
Good point! It's a Monday is my only defence!
Can you mount sd in CWM? Does your Nexus have an SD slot because mine doesn't. Mounting usb in CWM never worked for me either.
---------- Post added at 06:10 PM ---------- Previous post was at 06:09 PM ----------
Foxhounnd said:
Yeah, forgot too, fullretard.jpg. I tried mounting, doesn't work
Click to expand...
Click to collapse
Yeah as far as I am aware mounting usb in CWM won't work and never has. I also have never heard of or seen a GNex with an SD card.

You can try this: http://forum.xda-developers.com/showthread.php?t=1394051
Sent from my Galaxy Nexus using xda premium

LOL, I just answered this in another thread yesterday. You'll need to start all over by going back to stock Google images first.
Get the images here and be sure to pick the right GSM/LTE image:
http://code.google.com/android/nexus/images.html
Once you have the image, follow my steps in this thread:
http://forum.xda-developers.com/showthread.php?t=1447888
Finally, you need to install su again for root and flash CWM again.
EDIT: BTW, should warn you that doing so will wipe everything on your phone.

You could always download a ROM to your PC. Then boot your phone into CWM. Select Storages and Mounts. Then mount as a USB Mass Storage. Then copy the ROM to your phone.

kgeissler said:
You could always download a ROM to your PC. Then boot your phone into CWM. Select Storages and Mounts. Then mount as a USB Mass Storage. Then copy the ROM to your phone.
Click to expand...
Click to collapse
Has this worked for you? I've tried it before but CWM always fails to mount. I thought it's because GN doesn't have a dedicated SD card.

There is so much bad information here..
This phone WILL NOT MOUNT AS USB MASS STORAGE, therefore MOUNT USB in CWM does not work :/
If you are EVER stuck in this situation, you need to use fastboot to flash stock Google images as per three posts above me.
Not trying to be an ass, just get a point across.

joshnichols189 said:
There is so much bad information here..
This phone WILL NOT MOUNT AS USB MASS STORAGE, therefore MOUNT USB in CWM does not work :/
If you are EVER stuck in this situation, you need to use fastboot to flash stock Google images as per three posts above me.
Not trying to be an ass, just get a point across.
Click to expand...
Click to collapse
I totally agree! I knew usb couldn't bemounted in CWM!!!Thanks for clearing it up.

If you can boot into CWM you do not need to use fastboot. Boot into CWM and ADB push a ROM into /data/media (your "sdcard") and CWM flash the ROM.
Here's my advice for people who want to tinker with their Android phones.
Learn these fundamentals:
1.) Basic Linux/Windows command lines
2.) ADB
3.) Fastboot
4.) Odin or other flashing utilities respective to your phone.
Troubleshoot your phone in this order (as available to your situation):
1.) ClockworkMod Recovery
2.) Fastboot
3.) Odin/Download mode, RUU, other flashing utilities

joshnichols189 said:
There is so much bad information here..
This phone WILL NOT MOUNT AS USB MASS STORAGE, therefore MOUNT USB in CWM does not work :/
If you are EVER stuck in this situation, you need to use fastboot to flash stock Google images as per three posts above me.
Not trying to be an ass, just get a point across.
Click to expand...
Click to collapse
If that's the case then the mount options should be removed from CWM to stop confusion - I assumed it would connect as it does when booted
Sent from my Galaxy Nexus using xda premium

EddyOS said:
If that's the case then the mount options should be removed from CWM to stop confusion - I assumed it would connect as it does when booted
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
No SD caed either. Glad it's all cleared up.

NewMossie said:
Has this worked for you? I've tried it before but CWM always fails to mount. I thought it's because GN doesn't have a dedicated SD card.
Click to expand...
Click to collapse
Nexus S doesn't have a sdcard, and it works on the NS. The reason why this functionality doesn't work in CWR is because Galaxy Nexus uses MTP and not USB mass storage. Therefore, it doesn't work.

EddyOS said:
If that's the case then the mount options should be removed from CWM to stop confusion - I assumed it would connect as it does when booted
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
CWM is widely distributed across many devices. They're not going to remove it and give Galaxy Nexus owners their own recovery if they don't need to. There shouldn't be confusion because this phone does not support UMS, and that is very clear. So "mount USB storage" obviously wouldn't work.

Fastboot Status - FAILWrite Fail

Has anyone seen this? I can't flash anything at all via the toolkit or ADB or fastboot.
On my nexus's screen it keeps saying this at the bottom in blue:
Fastboot Status - FAILWrite Fail
Here's the background. My bootloader is unlocked. I have root or had (when i "upgraded" to 4.0.2 superuser is there but I can't seem to give anything root access anymore).
I decided to start fresh and just wipe the phone and use the factory images to install 4.0.4 onto the phone. But it seems no matter which drives I try, ADB just won't recognize my phone in bootloader mode.

You're doing it wrong.
iphone. helping computer illiteracy become popular since 2007.

@rbiter said:
You're doing it wrong.
iphone. helping computer illiteracy become popular since 2007.
Click to expand...
Click to collapse
Thank you for the extremely helpful response.
Does anyone else have any ideas?

ksc6000 said:
Thank you for the extremely helpful response.
Does anyone else have any ideas?
Click to expand...
Click to collapse
uhhhh did you even unlock your bootloader?
Sent from my Galaxy Nexus using xda premium

Diger36 said:
uhhhh did you even unlock your bootloader?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yes, it's unlocked.

Make sure you have the galaxy nexus files? I was a moron and had same issue when I accidentally downloaded nexus s
Sent from my Galaxy Nexus using xda premium

ksc6000 said:
Yes, it's unlocked.
Click to expand...
Click to collapse
Sorry, didn't read your OP right... My mistake.
Do you have a proper backup? If so: Maybe a lock and unlock bootloader might work. It's just a long shot but the message triggers me in that direction. Off course you will loose all your data, inclusing on /sdcard.

Diger36 said:
Sorry, didn't read your OP right... My mistake.
Do you have a proper backup? If so: Maybe a lock and unlock bootloader might work. It's just a long shot but the message triggers me in that direction. Off course you will loose all your data, inclusing on /sdcard.
Click to expand...
Click to collapse
Worth a try. I don't mind losing everything as I made a backup of the SD card on my computer before attempting.
EDIT: Nope, was able to re-lock and unlock the bootloader but still when trying to flash anything it says: FAILED <remote: Write Fail>

aimetti said:
Make sure you have the galaxy nexus files? I was a moron and had same issue when I accidentally downloaded nexus s
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
That is exactly what I did. SMH @ myself

adb wont recognize your phone in bootloader? Because ADB is when android is running. You need fastboot when you're in bootloader.

try another usb cable. and yes, either that or you're holding it wrong.

use fastboot: http://andwise.net/?attachment_id=270
and make sure you have the drivers for fastboot
do exactly as it says here http://andwise.net/?p=268

i got the same thing .. i flashed a kernel on my stock rom and then i was trying to flash the factory image and i had write fail thing

Ok. So we have a couple of symptoms, here.
1: You try to flash via fastboot, phone says: "Nuhu! Not with me, bro!"
2: The ADB/fastboot won't recognize the phone.
3: Some guys answering this thread, are just idiots...
Solutions:
1: Try erasing, before flashing. It helps
2: Reinstall the ADB/fastboot drivers (Check my signature, and do that (It works with every distribution of Windows form Vista+) This will reinstall the drivers, and the ADB/fastboot command/deamon will be able to communicate, with the deamon on the phone...
3: Ask a moderator, if he can delete some of those nasty n00b answers...
LG familyguy59
---------- Post added at 02:14 PM ---------- Previous post was at 02:10 PM ----------
M7amad90 said:
i got the same thing .. i flashed a kernel on my stock rom and then i was trying to flash the factory image and i had write fail thing
Click to expand...
Click to collapse
Again, read my sig.
TO ALL: Before creating a new thread, save memory (on the servers) and search function!!

Beatsleigher said:
Ok. So we have a couple of symptoms, here.
1: You try to flash via fastboot, phone says: "Nuhu! Not with me, bro!"
2: The ADB/fastboot won't recognize the phone.
3: Some guys answering this thread, are just idiots...
Solutions:
1: Try erasing, before flashing. It helps
2: Reinstall the ADB/fastboot drivers (Check my signature, and do that (It works with every distribution of Windows form Vista+) This will reinstall the drivers, and the ADB/fastboot command/deamon will be able to communicate, with the deamon on the phone...
3: Ask a moderator, if he can delete some of those nasty n00b answers...
LG familyguy59
---------- Post added at 02:14 PM ---------- Previous post was at 02:10 PM ----------
Again, read my sig.
TO ALL: Before creating a new thread, save memory (on the servers) and search function!!
Click to expand...
Click to collapse
I had the same problem, erasing userdata before flashing bootloader helps in solving,
actually i flashed the fact image via nexus toolkit and it asked to erase teh userdata first.

The Kuban Updater

How do you download from the kuban updater?
it doesnt work for me. please help me step by step

Read forum rules before posting
Questions go in Q&A
Thread moved
Thanks
FNM

Once you open the updater select a category, then select the mod or item you want to download, then at the bottom of the screen will be a download now button. Pressing the download now starts the download. Hope this helps.
Sent from my SPH-L710 using xda app-developers app

After downloading you may have to boot to recovery and flash the zip you downloaded.

zip files gone
COOKtheKILLA said:
After downloading you may have to boot to recovery and flash the zip you downloaded.
Click to expand...
Click to collapse
im having problems finding these files once in twrp ive even changed the directory to find them easier and once in recovery i cant find them. Using my files in the apps i find no problem but once in recovery they are gone. Any suggestions?
---------- Post added at 10:42 PM ---------- Previous post was at 10:22 PM ----------
msweber97 said:
im having problems finding these files once in twrp ive even changed the directory to find them easier and once in recovery i cant find them. Using my files in the apps i find no problem but once in recovery they are gone. Any suggestions?
Click to expand...
Click to collapse
im using wicked 3.1 also

msweber97 said:
im having problems finding these files once in twrp ive even changed the directory to find them easier and once in recovery i cant find them. Using my files in the apps i find no problem but once in recovery they are gone. Any suggestions?
---------- Post added at 10:42 PM ---------- Previous post was at 10:22 PM ----------
im using wicked 3.1 also
Click to expand...
Click to collapse
They should be in internal storage...while in recovery go to internal/kubandownloads and it should be there...

w8setter said:
They should be in internal storage...while in recovery go to internal/kubandownloads and it should be there...
Click to expand...
Click to collapse
yeah im on the internal storage, kubandownloads does not show up in recovery but it does in normal phone operation. any .zip files that i download from kuban updater they do not show up in recovery.

msweber97 said:
yeah im on the internal storage, kubandownloads does not show up in recovery but it does in normal phone operation. any .zip files that i download from kuban updater they do not show up in recovery.
Click to expand...
Click to collapse
I think I've tried everything I can to figure this out and no luck any suggestions?

msweber97 said:
I think I've tried everything I can to figure this out and no luck any suggestions?
Click to expand...
Click to collapse
Just copy and none the files somewhere else... I know this isn't the answer you're looking for, but at least recovery will see them then
SPRINT GS3 FAQ

Here's 2 options that you may or may not like, but how about open the kuban updater app and down at the bottom select the downloaded icon, it has an arrow pointing down, select the mod you want and select install mod....option 2 select the gears icon from the far left bottom and change the download folder to whatever you want and then download your mod and see if it shows in that folder....
Also if you have installed a aosp/cm10 like rom for some reason it creates a folder named 0....so try to open the 0 folder and see if you can access the kuban downloads folder from there in recovery....hope this helps...

w8setter said:
Here's 2 options that you may or may not like, but how about open the kuban updater app and down at the bottom select the downloaded icon, it has an arrow pointing down, select the mod you want and select install mod....option 2 select the gears icon from the far left bottom and change the download folder to whatever you want and then download your mod and see if it shows in that folder....
Also if you have installed a aosp/cm10 like rom for some reason it creates a folder named 0....so try to open the 0 folder and see if you can access the kuban downloads folder from there in recovery....hope this helps...
Click to expand...
Click to collapse
ive done exactly all of this before posting and still no luck copied and moved files like crazy and no luck and yes i have the "0" folder to and still not there!

msweber97 said:
ive done exactly all of this before posting and still no luck copied and moved files like crazy and no luck and yes i have the "0" folder to and still not there!
Click to expand...
Click to collapse
the only kuban file that shows up in recovery is kubancache.

msweber97 said:
the only kuban file that shows up in recovery is kubancache.
Click to expand...
Click to collapse
Well i finally got it to work. I had to wipe my foot unroot it go back to stock rom re-root phone reinstall wicked rom and finally it works!! thanks for all the suggestions!

msweber97 said:
Well i finally got it to work. I had to wipe my foot unroot it go back to stock rom re-root phone reinstall wicked rom and finally it works!! thanks for all the suggestions!
Click to expand...
Click to collapse
Well, at least your foot is clean now!
SPRINT GS3 FAQ

msweber97 said:
yeah im on the internal storage, kubandownloads does not show up in recovery but it does in normal phone operation. any .zip files that i download from kuban updater they do not show up in recovery.
Click to expand...
Click to collapse
Make sure you haven't actually hit the 0 folder. I did, and wouldn't see anything in kubandownloads folder. Once I backed up a level it was all there. Also if you would use TWRP 2.3.1 you shouldn't have go there. It will install it for you.
Sent from my SPH-L710 using xda app-developers app

[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.