Related
Hi guys I've been a root user on my Motorola Xoom for about a year now but I've jus landed myself a nexus 4 UK 16gb and after reading a lot on these nexus 4 forums i am still undecided as to what's the best/quickest/easyest way to root my new phone and what the best ROMs are so before I start the whole process in around an hour or so I wanna get your guys opinions please I'm quite tech savvy but still would like it nice and simple please
Will be starting the process at around 7pm GMT
So go crazy n let me have it lol
It really isn't that hard. There are three main steps: Unlock bootloader, flash custom recovery, flash supersu binaries via custom recovery.
Use this guide: http://forum.xda-developers.com/showthread.php?t=2266654
Oh, and dont use a toolkit.
Chromium_ said:
It really isn't that hard. There are three main steps: Unlock bootloader, flash custom recovery, flash supersu binaries via custom recovery.
Use this guide: http://forum.xda-developers.com/showthread.php?t=2266654
Oh, and dont use a toolkit.
Click to expand...
Click to collapse
Thanks I did it the old fashioned way anyway that's how I did my Xoom so I that's the way I know lol I was wondering what the best KitKat ROM is tbh my Xoom is getting a little behind due to partition size issues so I'm not up to date on ROMs ATM
I'd wait on kitkat until proper roms can be made. We will be getting the real deal very soon so I'd try kernels as stock 4.3 is great but I've noticed a great improvement changing the kernel and it let's you adjust as you know. Oh welcome BTW :thumbup:
Sent by mobile telephone.
I've got an Unlocked bootloader, status code 3, and when flashing Dhacker29's TWRP 2.7.0.0, I can no longer boot into recovery.
Anyone else noticing this?
Is there an updated version of TWRP compatible with official kitkat?
Leraeniesh said:
I've got an Unlocked bootloader, status code 3, and when flashing Dhacker29's TWRP 2.7.0.0, I can no longer boot into recovery.
Anyone else noticing this?
Is there an updated version of TWRP compatible with official kitkat?
Click to expand...
Click to collapse
Sadly not yet
http://forum.xda-developers.com/showthread.php?p=53183031#post53183031
But this should help get the ball rolling:
http://www.androidpolice.com/2014/0...and-4-4-2-kernels-for-the-razr-m-and-razr-hd/
And I'm checking here daily assuming Dhacker is going to be the one taking this on:
http://androidhosting.org/Devs/Dhacker29/msm8960/
There is a working clockwork, but if you're a TWRP user like myself that's not much help for restores.
Eclipse00 said:
Sadly not yet
http://forum.xda-developers.com/showthread.php?p=53183031#post53183031
But this should help get the ball rolling:
http://www.androidpolice.com/2014/0...and-4-4-2-kernels-for-the-razr-m-and-razr-hd/
And I'm checking here daily assuming Dhacker is going to be the one taking this on:
http://androidhosting.org/Devs/Dhacker29/msm8960/
There is a working clockwork, but if you're a TWRP user like myself that's not much help for restores.
Click to expand...
Click to collapse
is the CWM 100% operational ?
Last time I checked it was half baked still.
Give the Devs some time. =) atleast we got KK officially =) Loving it.
Seems like Dhaker29 just uploaded a new TWRP image for KitKat (2.7.1.0):
http://androidhosting.org/Devs/Dhacker29/msm8960/TWRP2710-RAZR-HD_M-KITKAT.img
j27h said:
Seems like Dhaker29 just uploaded a new TWRP image for KitKat (2.7.1.0):
http://androidhosting.org/Devs/Dhacker29/msm8960/TWRP2710-RAZR-HD_M-KITKAT.img
Click to expand...
Click to collapse
Saw that tweet.
Gonna have to stick to CWM till he updated TWRP for HDPI.
Its nearly unusable in XHDPI
Sent from my One using XDA Premium 4 mobile app
Leraeniesh said:
Saw that tweet.
Gonna have to stick to CWM till he updated TWRP for HDPI.
Its nearly unusable in XHDPI
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Here is the forum he was using to post that update. I sent him a PM letting him know about the resolution issue(XHDPI).
http://forum.xda-developers.com/showthread.php?p=53245960
It's here
http://androidhosting.org/Devs/Dhacker29/msm8960/TWRP2710-RAZR_M-KITKAT.img
Just used it this morning to install root on 4.4.2. Worked fine.
It doesn't seem to be working for me. I must not be doing something right. I am using these commands,
adb reboot bootloader
fastboot flash recovery TWRP2710-RAZR_M-KITKAT.img
it appears to work, it says successful but when I boot the phone into recovery it is still the stock. Any ideas on what I may be doing wrong?
Murph28 said:
It doesn't seem to be working for me. I must not be doing something right. I am using these commands,
adb reboot bootloader
fastboot flash recovery TWRP2710-RAZR_M-KITKAT.img
it appears to work, it says successful but when I boot the phone into recovery it is still the stock. Any ideas on what I may be doing wrong?
Click to expand...
Click to collapse
I'm assuming you have an unlocked bootloader. I had that same issue after the initial upgrade to the new OTA and bootloader. I ran through a few steps like unlocking the bootloader again (may have not done anything), I used a pre-rooted RSD flash of stock and I used the ADB method of installing the recovery instead of using fastboot.
To use the adb method I downloaded the batman 1.2 recovery tool, just renamed the version of TWRP (in this case TWRP2710-RAZR_M-KITKAT.img) to TWRP.IMG and placed it in the root of the batman folder, then I ran the flash TWRP recovery option. Note that the batman tool was designed for older firmware and you should probably not run any other functions on it if you are on the new firmware.
Batman 1.2
Murph28 said:
It doesn't seem to be working for me. I must not be doing something right. I am using these commands,
adb reboot bootloader
fastboot flash recovery TWRP2710-RAZR_M-KITKAT.img
it appears to work, it says successful but when I boot the phone into recovery it is still the stock. Any ideas on what I may be doing wrong?
Click to expand...
Click to collapse
You need to remove or rename,
Code:
/system/[COLOR="Red"][B][I]recovery-from-boot[/I][/B][/COLOR]
Thanks I will give this a try. I may hold off for now I read there was a possible update coming. I would guess you would need the stock recovery to get the update to work.
You could always flash the old recovery back. Since the soak test invites just came out it will probably be a month until it's released.
ezdi said:
You could always flash the old recovery back. Since the soak test invites just came out it will probably be a month until it's released.
Click to expand...
Click to collapse
Two weeks at best, considering it's the 4.4.3, which is probably the last update we'll get from Moto, unless a miracle occurs and we're given the 4.5 or 5.0, which shouldn't land until at least 5 months after it's release (if it does release next week).
I can't believe they're already planning another update. Sitting on jb we were all pretty sure that the kk update would be the last
Sent from my DROID RAZR M using Tapatalk
Either the KK build was just too buggy to ignore, or Verizon is making them close the bootloader exploit hole again.
GnatGoSplat said:
Either the KK build was just too buggy to ignore, or Verizon is making them close the bootloader exploit hole again.
Click to expand...
Click to collapse
It's a shame that they'd even bother closing that on a 2yr old phone but that's probably right. Too bad really. it's probably the only thing that would keep this device going for much longer. I know I was about to move on b4 towel root + bootloader unlock became available
Sent from my DROID RAZR M using Tapatalk
thewraith420 said:
It's a shame that they'd even bother closing that on a 2yr old phone but that's probably right. Too bad really. it's probably the only thing that would keep this device going for much longer. I know I was about to move on b4 towel root + bootloader unlock became available
Click to expand...
Click to collapse
Yeah, I'm hoping the update is because there were bugs that were too big to ignore, but Verizon forcing them to patch the exploit is probably more likely. Definitely a shame to close it on a 2yr old phone. IMO, we need some kind of consumer protection law that forces VZ and AT&T to allow BL unlocks once a device reaches EOL. It would even be better for the environment as it does keep devices relevant for much longer and less likely to end up in a toxic Chinese burn pile.
I feel like the reason we got the exploit back was a Moto dev saw the device is reaching EOL and decided it wouldn't hurt to help the community by putting the exploit back in, because it would almost have to have been deliberate.
Well it's actually lucky that 4.4.4 didn't patch towelroot, so root, I THINK, will stay, but for the bootloader unlock, it's better now than wait with Verizon.
I have tried many methods to bypass boot loader and install CWM or TWRP on i337 phones, all for which they failed, I am not sure whether because I have NC1 device
My phone is Rooted, NC1, My ultimate objective is to install T mobile Rom, so I can get Wifi-calling on my at&t, what do I need to do in order to that??? I am willing to downgrade or anything to reach my objective.
Here are some guides that I saw at
galaxys4root dot com
"How to Install GT-i9505/T-Mobile Custom ROMs on AT&T Galaxy S4!"
But i couldn't Install cwm or TWRP to proceed. Please Help.
you are post mdl build and can not run cwm or custom twrp only safestrap recovery. surprised you didn't run across that when you rooted and installed safestrap--
as far as wifi calling--don't know, but believe i have read not on an att phone
rugmankc said:
you are post mdl build and can not run cwm or custom twrp only safestrap recovery. surprised you didn't run across that when you rooted and installed safestrap--
as far as wifi calling--don't know, but believe i have read not on an att phone
Click to expand...
Click to collapse
OH right (I did this long time ago so forgot most of it), So if I wanted to install a tmobile s4 custom rom (DARTHSTALKER) on my i337 I could use safestrap, and then flash my kernel using odin for it to work? or that would break the phone?
not sure, i don't use SafeStrap and not familiar with rom
i would make sure it is safestrap compatible and see if any other att folks have flashed it
i do that by skimming last 30 pages and in-forum search for safestrap and att
or you can ask, but have found most times you get no answer on those type of questions. it has to be TW based--
You can get full root access on NC1
devil_2 said:
I have tried many methods to bypass boot loader and install CWM or TWRP on i337 phones, all for which they failed, I am not sure whether because I have NC1 device
My phone is Rooted, NC1, My ultimate objective is to install T mobile Rom, so I can get Wifi-calling on my at&t, what do I need to do in order to that??? I am willing to downgrade or anything to reach my objective.
Here are some guides that I saw at
galaxys4root dot com
"How to Install GT-i9505/T-Mobile Custom ROMs on AT&T Galaxy S4!"
But i couldn't Install cwm or TWRP to proceed. Please Help.
Click to expand...
Click to collapse
It's very hard to achieve what I did in these screen shots... sorta lol I just got the phone delivered yesterday at 2pm and hit Red Bull for 15 hours hacking it... I have full root access in system... knox is frozen by TiBu as you can see SELiniux is permissive, SuperSU Pro in control without a popup warning... I do have a new boot screen though with the unlocked lock lol. Bye bye warranty! I bought the 2 year replacement one and they don't care if it's rooted lol.
Check out the screen captures... I had to slug it out getting one app at a time til I finally figured out how to get TiBu su access... that was the key! I'd have to write a small novel explaining it, and I'm tired as heck lol. Some shots were too big. Point is... its stable I don't think you get this with safe strap do ya? Maybe ya do... but I hacked it lol. Still stock OS with a lot of freezes. If this is something different and ya wanna know reply to the message, but it takes a while and you need to really know your adb commands and be good with terminal emulator because it' s literally all you'll have for most of the 'fight' with Knox... and it really is. Lucky it didn't boot loop lol but I wanted full root access. I'll just deodex it and get rid of the bloatware later. I still wish I could flash CWM though lol. I like AOSP roms
Lt1streconbn said:
It's very hard to achieve what I did in these screen shots... sorta lol I just got the phone delivered yesterday at 2pm and hit Red Bull for 15 hours hacking it... I have full root access in system... knox is frozen by TiBu as you can see SELiniux is permissive, SuperSU Pro in control without a popup warning... I do have a new boot screen though with the unlocked lock lol. Bye bye warranty! I bought the 2 year replacement one and they don't care if it's rooted lol.
Check out the screen captures... I had to slug it out getting one app at a time til I finally figured out how to get TiBu su access... that was the key! I'd have to write a small novel explaining it, and I'm tired as heck lol. Some shots were too big. Point is... its stable I don't think you get this with safe strap do ya? Maybe ya do... but I hacked it lol. Still stock OS with a lot of freezes. If this is something different and ya wanna know reply to the message, but it takes a while and you need to really know your adb commands and be good with terminal emulator because it' s literally all you'll have for most of the 'fight' with Knox... and it really is. Lucky it didn't boot loop lol but I wanted full root access. I'll just deodex it and get rid of the bloatware later. I still wish I could flash CWM though lol. I like AOSP roms
Click to expand...
Click to collapse
Would have been easier on you to use TowelRoot which would give full root access and then use safestrap for its recovery. Could of avoided the 15 hours in about 1 minute with the TowelRoot app
I did try it. Several times. Didn't work at all... It was a lot of fun doing this honestly I haven't had a good challenge in a while lol. I managed to hack knox out of my device using nothing but the device itself and knowledge I have. I really don't want multiple Roms in my device. I just want one ROM like I have in all the others, and that's what I have now and I got CWM installed last night finally... A bit glitchy and not 100% stable yet... It has issues backing up to external SD for some reason. It'll backup to internal though. I used it to flash a small and meaningless update.zip I assembled to test it and it worked with it I'm not sure it would be successful using a backup yet either to restore the device... If I just used towel root I wouldn't have ever figured any of this out, and if I can get it a bit more simplified and figure out which particular steps or combinationof steps allowed me to exploit the system and get it in tthere and I can get it stable... I can tell everyone else how to do it. A friend on XDA is working on a tool now to simple install SuperSU into system... He done it on another device and got cwm installed on a device with a locked boot loader also. I used some of the code to get an idea how to do it on the sgh-i337. Its not impossible... Just hard to figure out I think that's one of the things XDA exist for... To learn and progress and help others... Right?
Lt1streconbn said:
I think that's one of the things XDA exist for... To learn and progress and help others... Right?
Click to expand...
Click to collapse
Sent from my Nexus 5 using XDA Free mobile app
Right, absolutely. Good job. We'll be curious how you do it once you get it figured out.
devil_2 said:
OH right (I did this long time ago so forgot most of it), So if I wanted to install a tmobile s4 custom rom (DARTHSTALKER) on my i337 I could use safestrap, and then flash my kernel using odin for it to work? or that would break the phone?
Click to expand...
Click to collapse
Why a T-Mobile rom on an AT&T phone. Why not use one for an AT&T phone?
tailgunner9 said:
Why a T-Mobile rom on an AT&T phone. Why not use one for an AT&T phone?
Click to expand...
Click to collapse
For t-mobile wifi-calling
Well Great Job then, I do applaud you for your work you done. Hopefully for those that are stuck using safestrap you can get it to the point they could use cwm. That would be awesome.
tailgunner9 said:
Why a T-Mobile rom on an AT&T phone. Why not use one for an AT&T phone?
Click to expand...
Click to collapse
I seriously would not try that using safe strap in i337 @ this point. The ROM would need to be ported as a multicarrier , which is pretty simple in and of itself... A lot of debugging I'd imagine though. You'll only get 2g speed using ATT device on TMO ya know. They have different 3g and 4g LTE bands. It just won't work. If you flash that ROM.. IIt's very likely you'll soft brick or hard brick the device. I have the ATT kernel decomped now working with it... I haven't downloaded any existing ROMS used with i337 yet, but I'll get one and check it out and see what has been done with Knox in it. Just very risky flashing a ROM not specific to your device...
I may have messed up, but I am not 100%, not use to Samsung Devices.
I have a developers edition S5.
I tried to run updates but it would not take any update OTA even though there were two, NCG was the current room.
I flashed the ni2 via odin.
Now on the screen, instead of Mode: Developer, it says Qualcomm Secureboot.
I am not sure if I relocked the bootloader, if it can be unlocked,
Or this just the need to go into a recovery and flash a different rom.
Did I relock the bootloader?
hill180 said:
I may have messed up, but I am not 100%, not use to Samsung Devices.
I have a developers edition S5.
I tried to run updates but it would not take any update OTA even though there were two, NCG was the current room.
I flashed the ni2 via odin.
Now on the screen, instead of Mode: Developer, it says Qualcomm Secureboot.
I am not sure if I relocked the bootloader, if it can be unlocked,
Or this just the need to go into a recovery and flash a different rom.
Did I relock the bootloader?
Click to expand...
Click to collapse
I believe you have. But first I need to ask you 1) were you rooted and 2) did you have a custom recovery (TWRP) on your phone before you ODIN'd NI2? If you had TWRP on your phone before ODIN can you get into TWRP recovery now? Just an FYI, Samsung does not send out, in any form (OTA or otherwise) updates to the Developer Edition phones. The explanation for why they don't is long and no one except for Samsung knows for sure and they are not commenting on the issue. Dev owners keep their phones up to date by flashing custom ROMs released by our Dev community for retail and dev edition phones.
hill180 said:
Did I relock the bootloader?
Click to expand...
Click to collapse
When you flashed the stock tar you locked the bootloader and unfortunately you will need to contact Samsung and explain what you did. Most likely you will need to send the phone in so they can unlock it again. Contact them first.
Misterxtc said:
When you flashed the stock tar you locked the bootloader and unfortunately you will need to contact Samsung and explain what you did. Most likely you will need to send the phone in so they can unlock it again. Contact them first.
Click to expand...
Click to collapse
I think you're right Misterxtc, unfortunately all Samsung is going to do is return him a retail version of the S5. According to 3 other Dev owners that locked their bootloaders all Samsung would do is return their phones to working order, but no unlocked bootloader.
jpcalhoun said:
I think you're right Misterxtc, unfortunately all Samsung is going to do is return him a retail version of the S5. According to 3 other Dev owners that locked their bootloaders all Samsung would do is return their phones to working order, but no unlocked bootloader.
Click to expand...
Click to collapse
That doesn't sound too promising. They really need to change their policy on that.
im not sure why you would have flashed a ne9 tar when instructions clearly say NOT to flash odin tars on a dev edition s5 because it will lock the bootloader
Sent from my SM-G900V using XDA Free mobile app
Thank you all.
Yes the phone has been locked. Obviously I blame myself for not researching and just assuming.
If there is a silver lining, it appears my phone has a bad microphone, when I called, Samsung wanted to do an warranty exchange. I told them it was a new item less than 5 days, so I am just going to return.
Still debating if I should wait a few month and get the S5 locked from VZW as I am not seeing a lot of dev (although it makes it easier to root), or if I should get another model of phone all together, or reorder the S5 Dev Edition.
hill180 said:
Thank you all.
Yes the phone has been locked. Obviously I blame myself for not researching and just assuming.
If there is a silver lining, it appears my phone has a bad microphone, when I called, Samsung wanted to do an warranty exchange. I told them it was a new item less than 5 days, so I am just going to return.
Still debating if I should wait a few month and get the S5 locked from VZW as I am not seeing a lot of dev (although it makes it easier to root), or if I should get another model of phone all together, or reorder the S5 Dev Edition.
Click to expand...
Click to collapse
I hope Samsung does right by you. Just my opinion, but I think the Developer Edition S5 is the best phone on the market right now. The only other phone, that I know of, that allows the user the flexibility and performance of a unlocked bootloader phone is the HTC M8. The M8 is a good phone no doubt, but I like the S5 better. True, there aren't that many ROMs rilght now, but more and more get added as time goes by. The ROMs that are available are good, staple ROMs and range anywhere from super customization available to the user to lean, debloated super fast with great battery life...and a couple in between. Your choice, but if Samsung will replace your Dev Edition with a new Dev Edition...I think that is your best bet right now. But that is just my opinion. Good luck.
jpcalhoun said:
I hope Samsung does right by you. Just my opinion, but I think the Developer Edition S5 is the best phone on the market right now. The only other phone, that I know of, that allows the user the flexibility and performance of a unlocked bootloader phone is the HTC M8. The M8 is a good phone no doubt, but I like the S5 better. True, there aren't that many ROMs rilght now, but more and more get added as time goes by. The ROMs that are available are good, staple ROMs and range anywhere from super customization available to the user to lean, debloated super fast with great battery life...and a couple in between. Your choice, but if Samsung will replace your Dev Edition with a new Dev Edition...I think that is your best bet right now. But that is just my opinion. Good luck.
Click to expand...
Click to collapse
Thanks, Samsung is def returning the Dev phone without a 15% restock (have rma). Not because of the locking, but because of the mic. I think you are correct.
I had to go to my standby which is the dev Moto X. Love this phone, but the photos are bad, and it is slow. When I confirm the credit has been giving for the Dev phone, I will reorder the Dev edition. This time I will have to figure out a way to make a backup for resell, and flash only using TWRP.
hill180 said:
Thanks, Samsung is def returning the Dev phone without a 15% restock (have rma). Not because of the locking, but because of the mic. I think you are correct.
I had to go to my standby which is the dev Moto X. Love this phone, but the photos are bad, and it is slow. When I confirm the credit has been giving for the Dev phone, I will reorder the Dev edition. This time I will have to figure out a way to make a backup for resell, and flash only using TWRP.
Click to expand...
Click to collapse
I've always been a Moto fan myself, but although they still make good phones, they're not great phones (camera, display etc). I just post a "Do's and Don'ts" for Dev owners. Give it a read and let me know if I should add something to the thread. I've seen six users brick their Dev S5s in the past couple of weeks, hopefully the thread will help the next guy from making a mistake: http://forum.xda-developers.com/verizon-galaxy-s5/general/developer-edition-s5-dos-donts-t2895563
jpcalhoun said:
I've always been a Moto fan myself, but although they still make good phones, they're not great phones (camera, display etc). I just post a "Do's and Don'ts" for Dev owners. Give it a read and let me know if I should add something to the thread. I've seen six users brick their Dev S5s in the past couple of weeks, hopefully the thread will help the next guy from making a mistake: http://forum.xda-developers.com/verizon-galaxy-s5/general/developer-edition-s5-dos-donts-t2895563
Click to expand...
Click to collapse
great read. (I my case I would have still been returning my phone, but the next S5 will be safe )
The only add, if even possible. It is possible to backup the stock recovery before installing TWRP. So when it is time to sell, you can return the TWRP original backup and flash the original stock recovery?
hill180 said:
great read. (I my case I would have still been returning my phone, but the next S5 will be safe )
The only add, if even possible. It is possible to backup the stock recovery before installing TWRP. So when it is time to sell, you can return the TWRP original backup and flash the original stock recovery?
Click to expand...
Click to collapse
That's a great question and one that I have been trying to figure how to do. I am not sure about this, but in order to backup a stock recovery you would have to use ADB and do a total backup of the phone that way. I have never tried that and I don't know for sure if it will even work using ADB. Here is how I look at it...who would want to pay $550 (or less) for a Developer Edition phone and never replace the stock recovery with a custom recovery? It doesn't make sense. In fact, the only way you can tell that a Developer Edition phone has not been inadvertently "locked" (not trying to stick a finger in your eye here) is to ask/see if a custom recovery is installed. If not, then there is no guarantee to the buyer that the bootloader is truly unlocked. SafeStrap does not count!
Very new to the Note 3 scene. I didn't see a post in the QnA recently of this. I'm on 4.4.2 with Root right now, but need to unlock my bootloader to load a custom rom. Any quick methods I can hit up? Thank you! Also, Do you need to unlock your bootloader to load a custom rom? What exactly is a Bootloader unlock all good for?
Please read the safestrap for booting custom roms
http://forum.xda-developers.com/showthread.php?t=2704992
Check out this thread for details on how to set yourself up.
http://forum.xda-developers.com/showthread.php?t=2528707
Hitmanthe3rd said:
Very new to the Note 3 scene. I didn't see a post in the QnA recently of this. I'm on 4.4.2 with Root right now, but need to unlock my bootloader to load a custom rom. Any quick methods I can hit up? Thank you! Also, Do you need to unlock your bootloader to load a custom rom? What exactly is a Bootloader unlock all good for?
Click to expand...
Click to collapse
You need to use a root method then install safe strap previous poster linked you.
there is currently not a method for unlocking the note 3 bootloader there may never be a way.
what this means to us we must use a workaround to load custom roms thus safestrap.
what a bootloader being unlocked gives is direct hardware access and the ability to run fully custom compiled code like cyanogenmod. It also allows for the use of custom kernels.
with the bootloader locked down as it is we are denied true asop builds of android and custom kernels. Instead we need to make due with ports from compatible builds of android galaxy s5, note 3 or 4 samsung firmware. Which means you are stuck with touchwiz and some bugs.
Holy cow!! Two replies that were helpful with no sarcasm or hate? Maybe there is still hope. Thanks for keeping it classy. OP, there's not as many roms as you may be used to from other devices, but the few that we have are all fantastic. Give a few a try, you won't be disappointed!
Sent from my SM-N900V using Tapatalk