Develop Bugs

TWRP update

So it looks they initiated a feature freeze and will focus on ironing out bugs, so I don't think we're too far from a release.
Got boost?

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Nice! I have been waiting for TWRP. I rooted but refuse to put on CWM with all the issues. Plus my battery life is so much better with the stock kernel right now.

stangdriverdoug said:
So it looks they initiated a feature freeze and will focus on ironing out bugs, so I don't think we're too far from a release.
Got boost?
Click to expand...
Click to collapse
Not yet, but I'm looking to be pushing about 12 lbs in the coming year.
sent from my Epic 4g Touch

Could someone please explain to me what TWRP is.
Sent from my SPH-D710 using xda premium

amwworks said:
Could someone please explain to me what TWRP is.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
It the recovery that teamwin were building for our phone, its a touch base recovery. search for it from android central or google.

jedwardmiller said:
Nice! I have been waiting for TWRP. I rooted but refuse to put on CWM with all the issues. Plus my battery life is so much better with the stock kernel right now.
Click to expand...
Click to collapse
haven't rooted this device yet, but will soon. I have never had issues with cwm on my tab or my original epic. I haven't read any complaints yet with cwm on this device. Can you share some links or specifics you know about?
Sent from my SPH-D710 using XDA App

TWRP is touch screen capable. Also they figured out how to keep it from changing when you flash other kernels.
Got boost?

tpike said:
haven't rooted this device yet, but will soon. I have never had issues with cwm on my tab or my original epic. I haven't read any complaints yet with cwm on this device. Can you share some links or specifics you know about?
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
A lot of people are afraid of CWM because on the OG EVO 4G early builds were wiping out people's RSA keys which are needed to connect to 4G. It was fixed shortly after, but for some it was too late. Once you restored from a nandroid, your 4g abilities were gone. That is really the only issue I have ever heard of with CWM. I have heard of issues with Rom Manager, but not CWM itself. I prefer TWRP, but if the only custom recovery is CWM, then that is what I'll use. There are no issues with CWM on our phone.

housry23 said:
A lot of people are afraid of CWM because on the OG EVO 4G early builds were wiping out people's RSA keys which are needed to connect to 4G. It was fixed shortly after, but for some it was too late. Once you restored from a nandroid, your 4g abilities were gone. That is really the only issue I have ever heard of with CWM. I have heard of issues with Rom Manager, but not CWM itself. I prefer TWRP, but if the only custom recovery is CWM, then that is what I'll use. There are no issues with CWM on our phone.
Click to expand...
Click to collapse
The good thing us we don't have to worry about 4g keys.
Sent from my PC36100 using xda premium

Hit a bump in the road!
From Twitter...
This, folks, is why #TWRP 2 isn't released yet. It just magically s-on'ed my EVO 4G! Stupid phone. >_<

cordell12 said:
Hit a bump in the road!
From Twitter...
This, folks, is why #TWRP 2 isn't released yet. It just magically s-on'ed my EVO 4G! Stupid phone. >_<
Click to expand...
Click to collapse
I saw that! I was like wtf? S-on really?
Got boost?

stangdriverdoug said:
I saw that! I was like wtf? S-on really?
Got boost?
Click to expand...
Click to collapse
Lol he bricked his evo4g on the newest tweet
Sent from my SPH-D710 using xda premium

tpike said:
haven't rooted this device yet, but will soon. I have never had issues with cwm on my tab or my original epic. I haven't read any complaints yet with cwm on this device. Can you share some links or specifics you know about?
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
No links or anything. Going on personal opinions onlyy. I actually used and liked CWM in the past. I have also used and liked AmonRA. I did put stock with cwm on a while ago and battery dropped from going to bed with over 50% to going through the entire battery in a day.
I know it most likely had nothing to do with CWM, so no need to correct me. This is only personal. Plus after seeing TWRP in action I can't wait to try it.

housry23 said:
A lot of people are afraid of CWM because on the OG EVO 4G early builds were wiping out people's RSA keys which are needed to connect to 4G. It was fixed shortly after, but for some it was too late. Once you restored from a nandroid, your 4g abilities were gone. That is really the only issue I have ever heard of with CWM. I have heard of issues with Rom Manager, but not CWM itself. I prefer TWRP, but if the only custom recovery is CWM, then that is what I'll use. There are no issues with CWM on our phone.
Click to expand...
Click to collapse
There was also another issue of CWM not wiping properly so when people would wipe and then install a ROM, it made the ROM appear to not be functioning properly, ie force closes and such. That and the RSA keys issues were the only ones I was aware of.
The solution to that was to just switch to AmonRa recovery, which was a lot better anyway.

I never was a fan of CWM, its too buggy. If teamwin comes through in separating the kernel and recovery partition I will be very happy, this is much needed.
@spencer88 I also had a feeling that CWM does not wile properly, I'd install a ROM and get boot loops. Usually that only happens with a ROM when you don't wipe and flash.

true but with Calk's "format all" that SHOULD put you at ease
spencer88 said:
There was also another issue of CWM not wiping properly so when people would wipe and then install a ROM, it made the ROM appear to not be functioning properly, ie force closes and such. That and the RSA keys issues were the only ones I was aware of.
The solution to that was to just switch to AmonRa recovery, which was a lot better anyway.
Click to expand...
Click to collapse
phatmanxxl said:
I never was a fan of CWM, its too buggy. If teamwin comes through in separating the kernel and recovery partition I will be very happy, this is much needed.
@spencer88 I also had a feeling that CWM does not wile properly, I'd install a ROM and get boot loops. Usually that only happens with a ROM when you don't wipe and flash.
Click to expand...
Click to collapse

phatmanxxl said:
I never was a fan of CWM, its too buggy. If teamwin comes through in separating the kernel and recovery partition I will be very happy, this is much needed.
@spencer88 I also had a feeling that CWM does not wile properly, I'd install a ROM and get boot loops. Usually that only happens with a ROM when you don't wipe and flash.
Click to expand...
Click to collapse
Agree. That happen to me just recently. I can't wait for a new recovery, I'm looking at you twrp
Sent from my SPH-D710 using xda premium

xlGmanlx said:
true but with Calk's "format all" that SHOULD put you at ease
Click to expand...
Click to collapse
It does, thanks Calk.

xlGmanlx said:
true but with Calk's "format all" that SHOULD put you at ease
Click to expand...
Click to collapse
I only used his format all on the EVO and had issues with getting loops and force closes. I haven't used it since then. It sounds like all are loving it though, which is good to hear.

What's wrong with my phone

Ok I'm really irritated right about now. I am unable to flash any custom ROMS on my phone. Actually let me rephrase, I can flash them but many things do not work. I have tried Wicked, FreeGS3 and CapROM. They all have the same issues. Let me explain.
Once the ROM is booted I get odd string of numbers and TXT in the status bar, (goes away, think nothing of it)
Root not avail/accessible by root apps.
Home button does not work
Play store missing
standard Google login prompt at first boot is missing, it never asks me to login
Using CWM 5.8.4.5 Touch Recovery
TMO GS3 Rooted with Odin no trip method
I don't get it. I am i just stuck using stock ROM? If anyone can help I would love you forever.

are you clearing /cache and dalvik-cache before you reboot to the custom rom?

mrmako777 said:
are you clearing /cache and dalvik-cache before you reboot to the custom rom?
Click to expand...
Click to collapse
If you mean clearing those after the install (in recovery completes) then no. Basically after the install I just reboot. Obviously clear and reset everything before I install though.

hd2Raz said:
Ok I'm really irritated right about now. I am unable to flash any custom ROMS on my phone. Actually let me rephrase, I can flash them but many things do not work. I have tried Wicked, FreeGS3 and CapROM. They all have the same issues. Let me explain.
Once the ROM is booted I get odd string of numbers and TXT in the status bar, (goes away, think nothing of it)
Root not avail/accessible by root apps.
Home button does not work
Play store missing
standard Google login prompt at first boot is missing, it never asks me to login
Using CWM 5.8.4.5 Touch Recovery
TMO GS3 Rooted with Odin no trip method
I don't get it. I am i just stuck using stock ROM? If anyone can help I would love you forever.
Click to expand...
Click to collapse
Touch recovery might be your problem
Sent from my SGH-T999 using Tapatalk 2

horr1blek1tten said:
Touch recovery might be your problem
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Really? A recovery can cause these kinds of issues. Haven't heard of that before. Any other thoughts? What recovery are you using?

Try TWRP 2.2.1.1

hd2Raz said:
Really? A recovery can cause these kinds of issues. Haven't heard of that before. Any other thoughts? What recovery are you using?
Click to expand...
Click to collapse
Yeah I've heard touch recovery has its problems so I don't use it. Try using the recovery rom manager gives you.
Sent from my SGH-T999 using Tapatalk 2

horr1blek1tten said:
Yeah I've heard touch recovery has its problems so I don't use it. Try using the recovery rom manager gives you.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I use TWRP and have no problems.
Do a Factory reset, wipe cache, wipe dalvik cache, fix permissions.
If that doesn't work, flash stock and reroot and try again.

I use touch recovery 5.8.4.7 and flashed it with adb. I've flashed almost everything. Cyanogenmod and every other ROM. NEVER had a problem with an instalation. Or even lost IMEI. I think people specifically aren't reading over OP's and figuring out what's safest for their devices and end up with these kind of results. Just my input.
Sent from my SGH-T999 using xda premium

Use mskips tool for our phones. It does everything you can image and then some. I have been using his tools since the HD2 and no issues to date.

The odd string of numbers that flashes upon boot in the status bar sounds like it's just identifying your external sd card. Totally normal.

OK so nothing worked. TWRP did the same thing. Tried diff ROM, same thing. I flashed back to 100% stock, unrooted ROM. Wiped the phone in the standard Android recovery. Then I rooted again, installed TWRP and flashed my ROM of choice and voila. Everything works. Problem solved. Thanks all for the inputs.

Bootloader loop on all roms?

Hey guys.
I am using a 4.0.4 paranoid android rom with franco kernal. it works okay, my battery is draining fast now and I want to upgrade to jellybean.
No matter which rom I install and follow the instructions I get stuck on the bootloader. I am following all instructions properly I think.
Can anyone help me out here?
thanks

Flash back to stock first and then try.
Sent from my Galaxy Nexus using xda premium

Mackie011 said:
Hey guys.
I am using a 4.0.4 paranoid android rom with franco kernal. it works okay, my battery is draining fast now and I want to upgrade to jellybean.
No matter which rom I install and follow the instructions I get stuck on the bootloader. I am following all instructions properly I think.
Can anyone help me out here?
thanks
Click to expand...
Click to collapse
what recovery are you using?

bk201doesntexist said:
what recovery are you using?
Click to expand...
Click to collapse
I go into CWM to try all this.

Mackie011 said:
I go into CWM to try all this.
Click to expand...
Click to collapse
Are you doing a "dirty" flash? Make sure to make a backup, then wipe data, system, factory reset, dalvik cache, cache and then finally install the .zip file.
Sent from my Galaxy Nexus using xda app-developers app

Mackie011 said:
I go into CWM to try all this.
Click to expand...
Click to collapse
What cwm version are you using? Try twrp.
AlexWekell said:
Are you doing a "dirty" flash? Make sure to make a backup, then wipe data, system, factory reset, dalvik cache, cache and then finally install the .zip file.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
This.

AlexWekell said:
Are you doing a "dirty" flash? Make sure to make a backup, then wipe data, system, factory reset, dalvik cache, cache and then finally install the .zip file.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Hi! thanks for responding!
that's what I do. make a backup, factory reset, wipe cache, dalvik cache. and then install the zips. the only thing I can think is that when I wipe the dalvik cache it says failed and there's no dalvik cache there? that's the only thing I can think of?

What about system and data?
Sent from my Galaxy Nexus using xda app-developers app

AlexWekell said:
What about system and data?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I factory reset, and wipe cache partition and then dalvik cache. I'm not sure how to do any others? How do you do them?!
I flashed back to stock to try it and it still gets stuck at bootloader.

In cwm (if I recall, I've switched to twrp, which is a lot better) its either in mounts or advanced or something like that, it should say format system/data. Do both of those before you flash along with the factory reset and so on.
Edit:
Here is where you want to be:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Galaxy Nexus using xda app-developers app

What version of CWM recovery are you using? Make sure you are running the latest version.
Sent from my Galaxy Nexus using xda premium

AlexWekell said:
In cwm (if I recall, I've switched to twrp, which is a lot better) its either in mounts or advanced or something like that, it should say format system/data. Do both of those before you flash along with the factory reset and so on.
Edit:
Here is where you want to be:
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Alright.
Format System, format data, factory reset, wipe cache partition, wipe dalvik. install zips. wipe cache partition, wipe dalvik. still getting stuck there.

Mackie011 said:
Alright.
Format System, format data, factory reset, wipe cache partition, wipe dalvik. install zips. wipe cache partition, wipe dalvik. still getting stuck there.
Click to expand...
Click to collapse
Try TWRP:
http://www.youtube.com/watch?v=VnBA-Y_hqaY&feature=youtube_gdata_player
Sent from my Galaxy Nexus using xda app-developers app

Have you tried returning to stock, then re-rooting gnex then flashing? Might be corrupted data on your phone. Also make sure that your running latest version of clockworkmod
Sent from my Galaxy Nexus using xda app-developers app

kyokeun1234 said:
Have you tried returning to stock, then re-rooting gnex then flashing? Might be corrupted data on your phone. Also make sure that your running latest version of clockworkmod
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Hi!
and I formatted SD card. went back to stock on everything. unlocked and rooted it. I tried to get the OTA update of JB but it still freezes.
I tried using a rom again and same result, not sure what's causing it now.
also I am now using TWRP.

AlexWekell said:
Try TWRP:
http://www.youtube.com/watch?v=VnBA-Y_hqaY&feature=youtube_gdata_player
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I switched to TWRP. is there any instructions that could maybe help me here?!

I had that problem once on my verizon nexus. Try flashing everything back to stock with odin. I did that and had to start from scratch, but it did fix my problem. I don't know if there are images for the gsm version, if thats what you are using, but the verizon ones fixed my problem. You can also try fastbooting the factory images from google too.

Mackie011 said:
Hi!
and I formatted SD card. went back to stock on everything. unlocked and rooted it. I tried to get the OTA update of JB but it still freezes.
I tried using a rom again and same result, not sure what's causing it now.
also I am now using TWRP.
Click to expand...
Click to collapse
ota will not flash if you have a custom recovery.
flashing other roms should be fine though.
i notice you say that you flash zips... what zips are you flashing? give us a specific example.

You might also want to give the JB bootloader a try and see if that will help yo!

Download the following: Superwipe zip, and Jelly Bean Bootloader zip
http://d-h.st/jcO Bootloader
http://www.mediafire.com/?lxpw84fwtm5cj6w Superwipe Script
Use clockworkmod and flash the superwipe choosing install zip from sd first the the same for the bootloader then flash your rom. Let it boot up which can take a couple minutes at the boot screen

[Q] backup question - TWRP, CWM, and RA

ok, maybe this is stupid but i don't know. i recently was able to get my evo hboot back down to 0.76.2000 and i'm like all excited and stuff. it works and i'm happy.
here's the potentially stupid question... when creating a backup in the mentioned recoveries, they create a backup of BOOT. does BOOT mean HBOOT?
Second question... in the backup recovery is listed. is that the recovery such as twrp, ra. cwm?
the reason i ask is i'm planning on restoring a backup and i don't want to lose my hboot. the recovery was done on hboot 2.16
i have three oreo cookies for the first person who know, answers, and doesn't call me a dumb-ass.

That's your boot image, not your hboot. And yes that backs up your recovery.Now where's my oreos
Sent from my IdeaTab A2107A-F using Tapatalk HD

CRIME INC. said:
That's your boot image, not your hboot. And yes that backs up your recovery.Now where's my oreos
Sent from my IdeaTab A2107A-F using Tapatalk HD
Click to expand...
Click to collapse
ok. so if i make a back up with CWM and then install RA and use RA to restore the CWM backup, it will put CWM back on my device?
and here's your three Oreo's. real deal, not some of those cheap ass wal-mart fake crap cookies! :good:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

jsp254 said:
ok. so if i make a back up with CWM and then install RA and use RA to restore the CWM backup, it will put CWM back on my device?
and here's your three Oreo's. real deal, not some of those cheap ass wal-mart fake crap cookies! :good:
View attachment 1625464
Click to expand...
Click to collapse
I do believe that's what would happen, I've never used that option when making a nandroid though.
Sent from my IdeaTab A2107A-F using Xparent ICS Tapatalk 2

well since i know now it wont screw up my hboot... i think i'm about to give it a shot and test it.
enjoy those cookies, they were my last ones.

jsp254 said:
well since i know now it wont screw up my hboot... i think i'm about to give it a shot and test it.
enjoy those cookies, they were my last ones.
Click to expand...
Click to collapse
Good luck, post back and let us know how it turns out.
Sent from my IdeaTab A2107A-F using Tapatalk HD

It won't revert recovery but you need to use a special setting to restore a CWM backup from ra or twrp.
Edit: at least not from my experience..
Sent from my SPH-L710 using xda premium

i never even tried it. i had been running the latest TWRP, but went back to RA. i like the keyboard ability in TWRP and being able to name my backups as i create them. but, i like the 3x wipe option in RA. if i knew how to mash them together to get a touch responsive, keyboard equipped, triple wiping recovery... i would just be someone else people could ***** at for bricking their ****.
i may go back later.
i'm like a ***** with shoes.
"what to wear today...pumps, heels, or jungle boots..."

I believe you will have to reflash whatever Rom or kernel you had after you recover your backup, since you changed Hboots. Usually it will not boot into the operating system, but will go directly to Hboot instead.
Sent from my SAMSUNG-SGH-I747 using xda premium

shortydoggg said:
I believe you will have to reflash whatever Rom or kernel you had after you recover your backup, since you changed Hboots. Usually it will not boot into the operating system, but will go directly to Hboot instead.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Not the case. Hboot has nothing to do with it. I ran a ROM on 2.18 then downgraded to 2.10 and the ROM still worked.
Sent from my SPH-L710 using xda premium

ROMs have nothing to do with hboot, they are contained in the /system and /data partitions while hboot is located somewhere esle. The only interaction between the two is that hboot is what tells the how to start up and that is what then loads up the actual ROM on the Android VM
Sent from my PG06100 using xda premium

death-by-soap said:
Not the case. Hboot has nothing to do with it. I ran a ROM on 2.18 then downgraded to 2.10 and the ROM still worked.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
2.10 yes, but I've had Hboot 0.76 after downgrading from 2.10, 2.16, and 2.18 and that was the case. I always had to reflash the kernel to get it to boot into the operating system, or else it would go directly to Hboot. It's an old engineering bootloader unlike 2.10.

I use a zip called superwipe. i'll have to get back to you on where i found it, but i think it would be a good solution to your TWRP/RA dilema lol. all you do is flash in recovery the superwipe.zip, and it automatically deletes cache/dalvik cache/data, three times, then sends you back to the recovery menu, where you can just simply flash your desired rom zip. sorry if this was already mentioned... i didn't read all of the reply pages
its called ZZZVR_SUPERWIPE.ZIP, im sure google will point you to the download location
also, im running MIUI ROM and RA 2.3 recovery

jsp254 said:
i never even tried it. i had been running the latest TWRP, but went back to RA. i like the keyboard ability in TWRP and being able to name my backups as i create them. but, i like the 3x wipe option in RA. if i knew how to mash them together to get a touch responsive, keyboard equipped, triple wiping recovery... i would just be someone else people could ***** at for bricking their ****.
i may go back later.
i'm like a ***** with shoes.
"what to wear today...pumps, heels, or jungle boots..."
Click to expand...
Click to collapse
Twrp factory reset/data wipe wipes 2x in one click everything except dalvik which its wipe option wipes 2x as well as a matter of fact I think every single wipe option in twrp automagically runs 2x it jist formats the partition and then reformats it again everytime you swipe the slide
Sent from my SPH-L900 using Xparent ICS Tapatalk 2

No Recovery?

So, I'm having this strange issue where I can't boot into Recovery Mode.
I've been a flashaholic for a little over a year now, but I've never had this problem.
I wanted to get off of Philz because it wasn't wiping my phone correctly while flashing new roms, so I decided to go back to good 'ol TWRP.
I downloaded Goomamager and tried to install, no luck.
So I hopped on my laptop to flash via ODIN, still a no go.
Only after that, it doesn't boot into Recovery at all.
I tried to use ROM Manager to install CWM, because at this point I'm willing to use anything, still a no go.
Anyone got any ideas?
I can get into Download Mode, but no Recovery is sticking.
I try to boot into Recovery, but the device just reboots itself.
Any help is appreciated, thanks.
Sent from my SM-N900T using XDA Premium 4 mobile app

devynbf said:
So, I'm having this strange issue where I can't boot into Recovery Mode.
I've been a flashaholic for a little over a year now, but I've never had this problem.
I wanted to get off of Philz because it wasn't wiping my phone correctly while flashing new roms, so I decided to go back to good 'ol TWRP.
I downloaded Goomamager and tried to install, no luck.
So I hopped on my laptop to flash via ODIN, still a no go.
Only after that, it doesn't boot into Recovery at all.
I tried to use ROM Manager to install CWM, because at this point I'm willing to use anything, still a no go.
Anyone got any ideas?
I can get into Download Mode, but no Recovery is sticking.
I try to boot into Recovery, but the device just reboots itself.
Any help is appreciated, thanks.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Depends on the android version. Also go back to stock with Odin and start all over. Make sure you using right recovery ? As far as philz cwm not wiping properly. Not to sure about that one. A wipe is a generic thing. What do you mean not wiping the right way?
TWEAKED 2.0 ELEMENT V3.0 NOTE 3

BACARDILIMON said:
Depends on the android version. Also go back to stock with Odin and start all over. Make sure you using right recovery ? As far as philz cwm not wiping properly. Not to sure about that one. A wipe is a generic thing. What do you mean not wiping the right way?
TWEAKED 2.0 ELEMENT V3.0 NOTE 3
Click to expand...
Click to collapse
Alright, I was gonna do that tomorrow on my day off, since the device seems to function properly mostly.
With Philz, I mean that I would Factory Reset, Wipe Data and "Wipe for new ROM", but when I would flash the new ROM, it would still have everything I had before on the device's SD memory, (which to me, is not a clean flash).
I am on Temasek's 4.4 CM11 v50.
I've been using this ROM for a long time and I've never had this problem in the past.
Sent from my SM-N900T using XDA Premium 4 mobile app

devynbf said:
Alright, I was gonna do that tomorrow on my day off, since the device seems to function properly mostly.
With Philz, I mean that I would Factory Reset, Wipe Data and "Wipe for new ROM", but when I would flash the new ROM, it would still have everything I had before on the device's SD memory, (which to me, is not a clean flash).
I am on Temasek's 4.4 CM11 v50.
I've been using this ROM for a long time and I've never had this problem in the past.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
OK I am not familiar with asop so I don't know what to say. But best bet is Odin back then flash twrp as you would like
TWEAKED 2.0 ELEMENT V3.0 NOTE 3

just connect fastboot
fastboot flash recovery (recoveryname).img

Hi man,i also have a sm n900t and im having this problem to,tried with every kind of recovery but no1 made it possible to boot into recovery,did you find an answer?