I have SGN3 N900a build # n900aucubnb4 how can I flash recovery (twrp/cwm) ? Can't find ANYTHING about it anywhere.
Sent from my SAMSUNG-SM-N900A using Tapatalk
JunkheadINC said:
I have SGN3 N900a build # n900aucubnb4 how can I flash recovery (twrp/cwm) ? Can't find ANYTHING about it anywhere.
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
You can't flash any custom recoveries because the bootloader is locked. The only thing we have close to it is Safestrap. Look at the Safestrap thread in the development section. It will tell you all you need to know.
And for the record, there is a TON of stuff out there about the locked bootloader preventing custom recoveries, kernels, AOSP ROMs, etc.
Do I need to update to KK And I'll be able to use regular recovery?
- junkheadINC
{[/Galaxy Note 3, N900A/]}
I did not want to update due to the fact I could send apps to the SD anymore.
- junkheadINC
{[/Galaxy Note 3, N900A/]}
The bootloader is locked on KitKat as well. "Upgrading" to KitKat would be even worse because there is no root for it yet and once you install the official update you cannot go back to 4.3.
There is absolutely NO way to use custom recoveries, custom kernels, or AOSP ROMs on the N900A because the bootloader is locked in all firmware versions for the N900A. There is no way to unlock it and probably never will be unless AT&T releases an update that unlocks it, which is very unlikely.
If you want TWRP, CM11, and custom kernels, sell your AT&T Note 3 and buy the T-Mobile version. It has an unlocked bootloader so you can do whatever you want to it. It is fully compatible with AT&T's network. There are guides around here somewhere that go more in depth and explain how too do it.
Thanks man. I got safestrap installed now. What r the down sides to using that? I'm on the ATT next program. I return my phones every 18months for new ones so I can't trade or sell it.
- junkheadINC
{[/Galaxy Note 3, N900A/]}
The only major downsides in my opinion are if you try to do the hold volume up+home+power button to get to recovery (or is it volume down? I forget...), you go straight to the stock recovery instead of Safestrap. Also, if you don't hit the button to boot into Safestrap in time you have to wait for the phone to finish booting, turn it off, and try again. You can't flash kernels with it either, but that's not Safestrap's fault.
It has its upsides as well. You get several slots for flashing ROMs and mods so you can run several different ROMs at the same time without having to wipe out your phone to try a new ROM. Each ROM you flash has to be based off the same version of android, though. That means no Fire Note in the stock slot, Dynamic KitKat in the first, S5 experience in the second, etc. There's more discussion about that in the Safestrap thread.
Related
Ok guys, i figured i've refrained from customizing my phone long enough.
I'm well aware of how to flash things onto the phone. I am currently running 4.2.2 on my C6606.
I have dualboot recovery flashed onto it, phone is rooted, and the only mod i have is pure audio.
I know i have to unlock my bootloader to be able to flash roms that require a custom kernel.
My question is, is there anything i should lookout for before flashing onto my phone?
I just want to know if these roms will also work on the t-mobile network. Haven't seen too much activity from C6606 users on here, so i'm a bit curious on that.
I don't believe you can unlock the bootloader on a C6606. If you could, you would need to back up your AT? partition; the one that has all your DRM keys and stuff. But you can still flash custom roms that are made for locked bootloaders, with stock kernels... I have flashed the stock roms from other regions and never had a problem with my C6606 working on the T-Mobile network.
Good luck!
i flashed NUT's 4.3 rom from 4.2 and running that, we have a locked bootloader which means we cant use a custom kernel. sony's ramdisk layout is bit different then im used to, im used to standard boot.img format on many devices. anyways the dual recovery script allows for booting custom ramdisks, if i can get a cm one setup and going then we could have cm booting on locked bootloaders. this is no easy task and something i have never done before, not to mention there may be issues that isnt there with a custom kernel.
shabbypenguin said:
i flashed NUT's 4.3 rom from 4.2 and running that, we have a locked bootloader which means we cant use a custom kernel. sony's ramdisk layout is bit different then im used to, im used to standard boot.img format on many devices. anyways the dual recovery script allows for booting custom ramdisks, if i can get a cm one setup and going then we could have cm booting on locked bootloaders. this is no easy task and something i have never done before, not to mention there may be issues that isnt there with a custom kernel.
Click to expand...
Click to collapse
Being able to get CM on the Z without unlocking the bootloader would be awesome.
iDroid8 said:
Being able to get CM on the Z without unlocking the bootloader would be awesome.
Click to expand...
Click to collapse
well i dont want peopel to get their hopes up about myself, its no easy feat and i applied for motorola financing last week, as i might end up going with a moto x. the bill with tmobile is a bit more than expected and going with a moto x would mean unlocked bootloader as well as lower monthly payments. you guys have some very talent people working on this device, it may end up happening on the z1 first and then get backported.
shabbypenguin said:
well i dont want peopel to get their hopes up about myself, its no easy feat and i applied for motorola financing last week, as i might end up going with a moto x. the bill with tmobile is a bit more than expected and going with a moto x would mean unlocked bootloader as well as lower monthly payments. you guys have some very talent people working on this device, it may end up happening on the z1 first and then get backported.
Click to expand...
Click to collapse
I'm just finding the process quite confusing. I haven't found any good videos detailing the entire process for a retard (myself).
iDroid8 said:
I'm just finding the process quite confusing. I haven't found any good videos detailing the entire process for a retard (myself).
Click to expand...
Click to collapse
videos on what?
shabbypenguin said:
videos on what?
Click to expand...
Click to collapse
Of flashing CM11. Most people aren't helpful and say if I can't unlock a bootloader then I shouldn't flash ROM's.
iDroid8 said:
Of flashing CM11.
Click to expand...
Click to collapse
its not possible with a locked bootloader at this time.
sbackus said:
I don't believe you can unlock the bootloader on a C6606. If you could, you would need to back up your AT? partition; the one that has all your DRM keys and stuff. But you can still flash custom roms that are made for locked bootloaders, with stock kernels... I have flashed the stock roms from other regions and never had a problem with my C6606 working on the T-Mobile network.
Good luck!
Click to expand...
Click to collapse
shabbypenguin said:
i flashed NUT's 4.3 rom from 4.2 and running that, we have a locked bootloader which means we cant use a custom kernel. sony's ramdisk layout is bit different then im used to, im used to standard boot.img format on many devices. anyways the dual recovery script allows for booting custom ramdisks, if i can get a cm one setup and going then we could have cm booting on locked bootloaders. this is no easy task and something i have never done before, not to mention there may be issues that isnt there with a custom kernel.
Click to expand...
Click to collapse
So say i tried to flash XperiaBlueLights, its a 4.2.2 rom, and it says its for a locked bootloader, it should work fine right?
Or the CriskeloRom, its 4.3 but it says it works on both locked and unlocked bootloaders. There shouldn't be an issue installing this on a C6606 should there?
Don't mean to ask so many questions, im usually the type to go and find out myself, but so far customizing my first sony phone isn't as fun, or easy as my past phones.
xDC23 said:
So say i tried to flash XperiaBlueLights, its a 4.2.2 rom, and it says its for a locked bootloader, it should work fine right?
Or the CriskeloRom, its 4.3 but it says it works on both locked and unlocked bootloaders. There shouldn't be an issue installing this on a C6606 should there?
Don't mean to ask so many questions, im usually the type to go and find out myself, but so far customizing my first sony phone isn't as fun, or easy as my past phones.
Click to expand...
Click to collapse
I think you would need to flash the C6606 kernel to be able to boot. I have written a C6606 tutorial for MIUI if you are interested in the Chinese version of Android. It is in the first post.
http://forum.xda-developers.com/showthread.php?p=46120012
C6606 user here. Currently running @niaboc79 4.3 Black Edition, and couldn't be happier.
I got my Z shortly after it became available, and have had a custom stock based ROM on it since day 1. I will admit there was a slight learning curve, but I knew I was switching to T-mobile and started reading up on the whole rooting/flashtool before I purchased and have stayed out of trouble (for the most part). Once you flash a ROM or two you will get the gist of it and it will become less confusing. The beauty of it is that we don't have to wait for T-Mobile to push out new Android versions. Once the Z gets it, so can we and no T-Mobile bloat. You will not have wifi calling if you haven't figured that out already.
Look for the "LB" (lockedbootloader) tag in the ROM title, and they should be good to go for us C6606 users.
Just follow the OP's instructions for installing and you will be fine. I haven't touched anything directly related to the C6606, other than APN's. I haven't had any luck doing the "download settings for internet and MMS" under wireless & networks settings.
I use these APN's every time I do a clean install and all network modes (3G, 4G, LTE) work just fine - http://forum.xda-developers.com/showthread.php?t=2236735
xDC23 said:
Ok guys, i figured i've refrained from customizing my phone long enough.
I'm well aware of how to flash things onto the phone. I am currently running 4.2.2 on my C6606.
I have dualboot recovery flashed onto it, phone is rooted, and the only mod i have is pure audio.
I know i have to unlock my bootloader to be able to flash roms that require a custom kernel.
My question is, is there anything i should lookout for before flashing onto my phone?
I just want to know if these roms will also work on the t-mobile network. Haven't seen too much activity from C6606 users on here, so i'm a bit curious on that.
Click to expand...
Click to collapse
yeah made sure you back your entire phone completely up! that way if something happens you can always go bck to the orginal state!
So I used to have a Galaxy S3 and the charging port was jacked up so I was not able to hold a USB connection long enough to be able to root. But now I have an HTC One. I know I can't root yet because I have a Verizon One with 4.4.2. But I have a few questions before I'm even able to root.
Anyway, what is a recovery?
nikalsaki said:
So I used to have a Galaxy S3 and the charging port was jacked up so I was not able to hold a USB connection long enough to be able to root. But now I have an HTC One. I know I can't root yet because I have a Verizon One with 4.4.2. But I have a few questions before I'm even able to root.
Anyway, what is a recovery?
Click to expand...
Click to collapse
Look, a custom recovery like TWRP or Clockworkmod allows you to root, flash a custom rom, make a backup, restore the system image or wipe the phone. Every single phone has a stock recovery, but this doesn't allow you to do the features of a custom recovery as I mentioned above. The stock recovery only allows you to flash the official firmwares, provided that you have a matching model ID and carrier ID.
So, in basic terms, rooting requires a custom recovery. TWRP is the recommended recovery for HTC One
I can't seem to find a recovery that will flash a rom for MY phone. I have the MetroPCS version/variant of the sgh-t599n and I really want to be able to flash a custom rom to my phone, but I can't seem to find anyone with (codinMetroPCS) files for it. The only reason I say that is because when I finally got CWM 6.0.3.2 downloaded and working, tried to flash beanstalk rom and it told me "THIS ROM IS FOR CODINALTE PHONES NOT CODINMETROPCS PHONES" Is there a different rom for the Metro phones? Or am I doing something wrong....Im rooted through cydiaimpactor, well, i guess technically through the pre-rooted stock rom I had to flash through Odin...BTW-Over the last two weeks I've learned that flashing a rom on a samsung (at least mine) takes a custom recovery, which needs to be flashed via Odin (something I didn't know how to do at the time)...I almost feel like Im starting to get confused with all these different programs needed to run or flash or download this or that....I'm not sure if the info is even in the correct order in my head......could someone please walk me through this? or call me! lmao...this is giving me a headache. lol....but I REALLY REALLY want to know what Im doing.....ANYONE? PLEASE??
Cdbarron727 said:
I can't seem to find a recovery that will flash a rom for MY phone. I have the MetroPCS version/variant of the sgh-t599n and I really want to be able to flash a custom rom to my phone, but I can't seem to find anyone with (codinMetroPCS) files for it. The only reason I say that is because when I finally got CWM 6.0.3.2 downloaded and working, tried to flash beanstalk rom and it told me "THIS ROM IS FOR CODINALTE PHONES NOT CODINMETROPCS PHONES" Is there a different rom for the Metro phones? Or am I doing something wrong....Im rooted through cydiaimpactor, well, i guess technically through the pre-rooted stock rom I had to flash through Odin...BTW-Over the last two weeks I've learned that flashing a rom on a samsung (at least mine) takes a custom recovery, which needs to be flashed via Odin (something I didn't know how to do at the time)...I almost feel like Im starting to get confused with all these different programs needed to run or flash or download this or that....I'm not sure if the info is even in the correct order in my head......could someone please walk me through this? or call me! lmao...this is giving me a headache. lol....but I REALLY REALLY want to know what Im doing.....ANYONE? PLEASE??
Click to expand...
Click to collapse
Just flash the recovery listed in the BeanStalk thread.
There's 3 variants of the phone; T599, T599N, T599V (codinatmo, codinametropcs/codinanewcotmo, codinavid) they're pretty much the same exact phone, there's just slight differences in proprietary files - so the developers decided to unify the all of them into one (codinalte), as it's easier to build for one phone then three seperate times. The recovery's responsible for the phone; which is why the recovery plays a key-role, basically the recovery you have right now can only accept roms that are specifically 'titled' as codinametropcs, and by flashing that recovery, you'll be able to flash any of the 4.4.x roms (BeanStalk, Vanir, OmniROM, CM, AOKP, and soon pure-vanialla AOSP).
ok so....
Exothermic said:
Just flash the recovery listed in the BeanStalk thread.
There's 3 variants of the phone; T599, T599N, T599V (codinatmo, codinametropcs/codinanewcotmo, codinavid) they're pretty much the same exact phone, there's just slight differences in proprietary files - so the developers decided to unify the all of them into one (codinalte), as it's easier to build for one phone then three seperate times. The recovery's responsible for the phone; which is why the recovery plays a key-role, basically the recovery you have right now can only accept roms that are specifically 'titled' as codinametropcs, and by flashing that recovery, you'll be able to flash any of the 4.4.x roms (BeanStalk, Vanir, OmniROM, CM, AOKP, and soon pure-vanialla AOSP).
Click to expand...
Click to collapse
?
When you say flash....you mean through Android System Recovery (stock recovery)? right? ....sry man...back when i was rooting my droid x, I never ran into any issues and it seemed a little easier to flash roms
Cdbarron727 said:
?
When you say flash....you mean through Android System Recovery (stock recovery)? right? ....sry man...back when i was rooting my droid x, I never ran into any issues and it seemed a little easier to flash roms
Click to expand...
Click to collapse
flash it through odin.
Thank you....now....I think I've actually gotten this far already.....had cwm installed...then tried to flash beanstalk with cwm and I got the codin error saying "this is not for codinmetropcs" ...if I get that problem again...is there something conflicting with it in some way? Or where did I go wrong? do i have to have twrp?
sorry to bug bro
Exothermic said:
Just flash the recovery listed in the BeanStalk thread.
There's 3 variants of the phone; T599, T599N, T599V (codinatmo, codinametropcs/codinanewcotmo, codinavid) they're pretty much the same exact phone, there's just slight differences in proprietary files - so the developers decided to unify the all of them into one (codinalte), as it's easier to build for one phone then three seperate times. The recovery's responsible for the phone; which is why the recovery plays a key-role, basically the recovery you have right now can only accept roms that are specifically 'titled' as codinametropcs, and by flashing that recovery, you'll be able to flash any of the 4.4.x roms (BeanStalk, Vanir, OmniROM, CM, AOKP, and soon pure-vanialla AOSP).
Click to expand...
Click to collapse
I just flashed cwm through odin and it passed....I havn't rebooted just yet, but I know it was working before.... But just saw that the cwm I downloaded from the beanstalk thread says its for kitkat builds only. My phone is running 4.1.2..does that matter? or does that mean I just need a 4.4 rom to be flashed with it? Sorry if these are dumb questions
Cdbarron727 said:
I just flashed cwm through odin and it passed....I havn't rebooted just yet, but I know it was working before.... But just saw that the cwm I downloaded from the beanstalk thread says its for kitkat builds only. My phone is running 4.1.2..does that matter? or does that mean I just need a 4.4 rom to be flashed with it? Sorry if these are dumb questions
Click to expand...
Click to collapse
It's cool; it just means you can only flash 4.4 roms, so you cannot flash cm10.1, cm10.2, and pac. It doesn't matter that your phone's running 4.1.2.
As content as I am with my tweaked stock rom on my Note 3 (AT&T variant...) curiosity has me looking at custom ROMs. However, when I look for information on the AT&T Note 3, most sites say locked bootloader. Which would tell me that I can't install ClockworkMod/TWRP recovery to install an AOSP ROM (probably CyanogenMod since most others seem based off that anyways). Correct me if I'm wrong, but that would mean I'm (we're?) stuck with factory-based ROMs.
However...the instructions here: http://wiki.cyanogenmod.org/w/Install_CM_for_hlte mention nothing about the AT&T variant not working.
And I found this: http://www.teamandroid.com/2014/09/...-att-galaxy-note-3-n900a-kitkat-custom-rom/2/ where they have the ClockworkMod installed. However, in this case, search engines have been unhelpful in finding more information about the "Internazionale" ROM. The only thing I've seen is that it's based on official N9005XXUENC2.
Will the hlte instructions work on an AT&T Note 3? I don't have a warranty on the phone anyways, so voiding it really isn't an issue; I'm simply not interested in bricking the thing.
QuimaxW said:
As content as I am with my tweaked stock rom on my Note 3 (AT&T variant...) curiosity has me looking at custom ROMs. However, when I look for information on the AT&T Note 3, most sites say locked bootloader. Which would tell me that I can't install ClockworkMod/TWRP recovery to install an AOSP ROM (probably CyanogenMod since most others seem based off that anyways). Correct me if I'm wrong, but that would mean I'm (we're?) stuck with factory-based ROMs.
However...the instructions here: http://wiki.cyanogenmod.org/w/Install_CM_for_hlte mention nothing about the AT&T variant not working.
And I found this: http://www.teamandroid.com/2014/09/...-att-galaxy-note-3-n900a-kitkat-custom-rom/2/ where they have the ClockworkMod installed. However, in this case, search engines have been unhelpful in finding more information about the "Internazionale" ROM. The only thing I've seen is that it's based on official N9005XXUENC2.
Will the hlte instructions work on an AT&T Note 3? I don't have a warranty on the phone anyways, so voiding it really isn't an issue; I'm simply not interested in bricking the thing.
Click to expand...
Click to collapse
Take the time to click on just about any thread and you'll find the answer to your question. The bootloader is locked on only the AT&T and Verizon variants so only stock kernels will work. Only ROMs based on the stock ROM will work.
I have been reading threads here for the last week. I know how people who ask seemingly dumb questions get attacked here. I almost didn't even post the questions to begin with cause I knew the repricussions of asking questions.
So...only factory firmware with the locked boot loader. Next question...can we run a non-odin recovery? In the one page I posted it looked like they were running CWM recovery, but everything I've read here says to use the safeboot strap.
Safestrap 3.75 is the ONLY option available to us on the AT&T variant. It does use a modded version of TWRP, but as previously stated, only roms that use the stock TW kernel will work. So far the best rom I've tried is DynamicKat.
Hey guys!
I'm new to the Nexus phones and also new to unlocked bootloaders, but I will be getting the Verizon Nexus 6 within the next couple of weeks. Very excited. The first thing I'll be doing is unlocking the bootloader and obtaining root.
I am coming from the Verizon Note 3 (of course it's locked). I'm very familiar with rooting, flashing, and custom recoveries on locked devices. So, I guess I was hoping you guys could give me some tips and things to watch out for so I don't hard brick this phone. I've never bricked a phone before and I don't want this to be my first.
A few questions I already have..
Can any Nexus 6 ROM be flashed onto the Verizon Nexus 6?
What are some "NO's" I need to know about to avoid a hard brick?
How different are the custom recoveries (TWERP and Safestrap)?
If I make a backup of the factory image, can I just reflash it at any point?
Thanks for taking your time to read this and help me out.
ForeverZ3RO said:
Hey guys!
I'm new to the Nexus phones and also new to unlocked bootloaders, but I will be getting the Verizon Nexus 6 within the next couple of weeks. Very excited. The first thing I'll be doing is unlocking the bootloader and obtaining root.
I am coming from the Verizon Note 3 (of course it's locked). I'm very familiar with rooting, flashing, and custom recoveries on locked devices. So, I guess I was hoping you guys could give me some tips and things to watch out for so I don't hard brick this phone. I've never bricked a phone before and I don't want this to be my first.
A few questions I already have..
Can any Nexus 6 ROM be flashed onto the Verizon Nexus 6?
What are some "NO's" I need to know about to avoid a hard brick?
How different are the custom recoveries (TWERP and Safestrap)?
If I make a backup of the factory image, can I just reflash it at any point?
Thanks for taking your time to read this and help me out.
Click to expand...
Click to collapse
1. yes. all nexus 6 are the same, regardless where you bought it.
2. nos, just educate yourself by reading.
3. its twrp, and its the only custom recovery for a nexus 6. wtf is safestrap?
3. if you make a nandroid backup in your recovery, you can restore it at any time.
ForeverZ3RO said:
Can any Nexus 6 ROM be flashed onto the Verizon Nexus 6? Yes.
What are some "NO's" I need to know about to avoid a hard brick? Don't do any modifications until you thoroughly understand what you are doing.
How different are the custom recoveries (TWERP and Safestrap)? There is only one custom recovery (TWRP) available.
If I make a backup of the factory image, can I just reflash it at any point? If you make a backup of your stock ROM, you can reflash it at any time. And you can also fastboot flash the factory image at any time.
Click to expand...
Click to collapse
Replies above in RED.
Thanks for the quick reply and some great answers simms22 & Cam30era!
I definitely do a LOT of reading before trying anything i'm unsure about.
simms22 - Safestrap is a custom recovery for locked devices (like the Verizon Note 3) that allows flashing ROMs onto "ROM-slots", keeping the stock ROM-slot safe. As long as you can boot into Safestrap, you can always load your stock-ROM. You can have up to 4 different custom ROMs along side the stock ROM.
Thanks for the help!
ForeverZ3RO said:
Thanks for the quick reply and some great answers simms22 & Cam30era!
I definitely do a LOT of reading before trying anything i'm unsure about.
simms22 - Safestrap is a custom recovery for locked devices (like the Verizon Note 3) that allows flashing ROMs onto "ROM-slots", keeping the stock ROM-slot safe. As long as you can boot into Safestrap, you can always load your stock-ROM. You can have up to 4 different custom ROMs along side the stock ROM.
Thanks for the help!
Click to expand...
Click to collapse
I was a note 4 user on verizon also the latest for the note 3 safestrap was based off twrp. So if u know safestrap you should be good. But what i would recommend is going onto youtube and watching a couple videos on twrp
There a some good ones on there.
Here is one for the s3
https://www.youtube.com/watch?v=05ReQbru9s0