Let me first say I've looked through the forums and can't find a direct answer to this, so I hope this doesn't bother you guys.
I just bought the noteII yesterday and so far it looks like I'm selling the iPhone5 (why'd it take me so long?)
I do want to root my noteII so I can use the secure setting and other plugins with Tasker mostly. Plus just having full control.
Seems I have Android 4.1.1 with Baseband version I605VRALL4 and Build JR003C.I605VRALL4 (kernel 3.0.31-414933)
Now I'm a mac user so one question is - is there a way to do this through mac? if it possible...second is if it's not how long until it looks like it might be? gives me time to find a windows PC.
snickn said:
Let me first say I've looked through the forums and can't find a direct answer to this, so I hope this doesn't bother you guys.
I just bought the noteII yesterday and so far it looks like I'm selling the iPhone5 (why'd it take me so long?)
I do want to root my noteII so I can use the secure setting and other plugins with Tasker mostly. Plus just having full control.
Seems I have Android 4.1.1 with Baseband version I605VRALL4 and Build JR003C.I605VRALL4 (kernel 3.0.31-414933)
Now I'm a mac user so one question is - is there a way to do this through mac? if it possible...second is if it's not how long until it looks like it might be? gives me time to find a windows PC.
Click to expand...
Click to collapse
You will need a windows PC with the samsung drivers installed as well as ODIN.
Yes you can still root, but you cannot unlock the bootloader at this time because your phone has accepted the OTA - so flashing custom ROM's, kernel's, etc. is out. All the info you need is in this thread to root (if you have a VERIZON Note2):
http://forum.xda-developers.com/showthread.php?t=2024207
Use the route66 image (there are three listed to choose from, be sure to pick route66) - there is lots of information on what you want to do in the latter 15 pages of that thread.
stop after section 1a.
Honestly though out of the box the phone is outstanding, and without an unlock method for the bootloader, I'd recommend doing nothing. Too many people have already borked their phones due to lack of experience, knowledge, reading the steps correctly...you get the idea. I'm not commenting on your knowledge, just saying what I would do after reading as much as I could find here on this phone. The terrific devs will come up with a way to unlock and root the post OTA version soon enough.
Honestly the two things that is causing me to want to unlock it is I can't seem to get Tasker to control lockscreen properly. I have it setup to detect what cell towers I'm on and not lock in the house - and yet...it continually locks. Shows I'm on that cell tower, just seems like it can't properly control the lockscreen.
Secondly, I'd like to make GPS only come on when certain apps are open - and that seems to be a root only feature.
Reason enough for me :thumbup:
courtesy of my unlocked Note2
after these steps, will I get OTA for current security fixed updated?
alu1008 said:
after these steps, will I get OTA for current security fixed updated?
Click to expand...
Click to collapse
You know I'm going to forgive you this time for not reading the OP and then the other giant thread on it but come on man, seriously.
If you have a brand new phone and you took the OTA, you can still root. Just do NOT try to install a custom recovery, kernel, rom, etc.
If you are rooted and you took the OTA, you should still be rooted OR you will already have root installed. Again, you CANNOT install a custom recovery, kernel, or rom, etc.
alu1008 said:
after these steps, will I get OTA for current security fixed updated?
Click to expand...
Click to collapse
You will get prompted. Defer the OTA then freeze or uninstall SDM 1.0 using Titanium Backup from the Play Store.
You can get the OTA applied using a safe zip made by Adryn...its a thread in the General section I think.
The threads are full of questions and answers on this topic.
courtesy of my unlocked Note2
ILMF said:
Too many people have already borked their phones due to lack of experience, knowledge, reading the steps correctly...you get the idea. I'm not commenting on your knowledge, just saying what I would do after reading as much as I could find here on this phone. The terrific devs will come up with a way to unlock and root the post OTA version soon enough.
Click to expand...
Click to collapse
People bork their phones all the time. Samsung phones are the easiest to "fix". It amazes me that even with step by step videos people still get things wrong. Life is about living and learning. If you screw it up 9 times out 10 it can be fixed.
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
you can lead a horse to water but you cant make him drink.
Alright, I've searched high and low with no results, so here it goes. I hope I'm posting in the correct forum. My apologies if not.
I've got a rooted note 3 on pretty much stock MJ4, hardware version N900P.12. I vaguely recall when I first got this phone (about a year ago) that there was an issue with unlocking the bootloader that broke 4G. I cannot find anything on this anymore. I'd really like to try some custom ROMs. I've been holding off on the OTAs, as I don't really want to limit my options.
Questions:
1) Can I now unlock the bootloader and run custom ROMs without breaking 4g LTE?
2) If so, what is my best path for upgrading and either keeping root, or re-rooting my phone?
Thanks in advance...
xpingjockey said:
Alright, I've searched high and low with no results, so here it goes. I hope I'm posting in the correct forum. My apologies if not.
I've got a rooted note 3 on pretty much stock MJ4, hardware version N900P.12. I vaguely recall when I first got this phone (about a year ago) that there was an issue with unlocking the bootloader that broke 4G. I cannot find anything on this anymore. I'd really like to try some custom ROMs. I've been holding off on the OTAs, as I don't really want to limit my options.
Questions:
1) Can I now unlock the bootloader and run custom ROMs without breaking 4g LTE?
2) If so, what is my best path for upgrading and either keeping root, or re-rooting my phone?
Thanks in advance...
Click to expand...
Click to collapse
I never had to unlock my boot loader and ive got perfect 4g you should do as you please verizon and att has locked bootloaders so yeah odin flash update odin flash modem to odin flash cwm or twrp cf auto root read instructions and reread them then flash the rom you want me personally I run sacs s5 moar port I hope this helps ps make sure you have the sprint note 3 n900p
xpingjockey said:
Alright, I've searched high and low with no results, so here it goes. I hope I'm posting in the correct forum. My apologies if not.
I've got a rooted note 3 on pretty much stock MJ4, hardware version N900P.12. I vaguely recall when I first got this phone (about a year ago) that there was an issue with unlocking the bootloader that broke 4G. I cannot find anything on this anymore. I'd really like to try some custom ROMs. I've been holding off on the OTAs, as I don't really want to limit my options.
Questions:
1) Can I now unlock the bootloader and run custom ROMs without breaking 4g LTE?
2) If so, what is my best path for upgrading and either keeping root, or re-rooting my phone?
Thanks in advance...
Click to expand...
Click to collapse
If the device was sprint issued the boot loader is/was unlocked. Running custom roms will not break 4g LTE, that is part of your baseband/modem.
If you upgrade to NAB,NC5, or NH7 it won't make any difference because your device is out of warranty. I would upgrade to NC5 check out this link http://forum.xda-developers.com/showthread.php?t=2770729&page=3 read post #25. Enjoy !!!
So I just got handed an S4 from a co-worker, I just spent an hour looking up info on root and stuff to load custom roms (looking mainly for CM11). My main problem seems to be all the shortened terms and everything associated with this phone, root vs unlocked bootloader vs etc, MK2?? NC5??. I can't seem to find any "newb" friendly breakdown of all of this. This isn't my first hacked device by far (I got an old DiNC and a ReZound for my last 2), but definitely the most confusing one. So here's the info I got on my phone: Galaxy S4, Verizon, SCH-I545, Android 4.4.2, VRUFNC5, hardware version: I545.06.
Can anyone point me in the right directions to understand better, and get me to my final destination of Custom rom? Or at least get me to understand this better?
I did search the first 5 pages of every section to see if there was a "newb-friendly" sticky but didn't seem to go anywhere fast, just made me more confused.
tong6998 said:
So I just got handed an S4 from a co-worker, I just spent an hour looking up info on root and stuff to load custom roms (looking mainly for CM11). My main problem seems to be all the shortened terms and everything associated with this phone, root vs unlocked bootloader vs etc, MK2?? NC5??. I can't seem to find any "newb" friendly breakdown of all of this. This isn't my first hacked device by far (I got an old DiNC and a ReZound for my last 2), but definitely the most confusing one. So here's the info I got on my phone: Galaxy S4, Verizon, SCH-I545, Android 4.4.2, VRUFNC5, hardware version: I545.06.
Can anyone point me in the right directions to understand better, and get me to my final destination of Custom rom? Or at least get me to understand this better?
I did search the first 5 pages of every section to see if there was a "newb-friendly" sticky but didn't seem to go anywhere fast, just made me more confused.
Click to expand...
Click to collapse
The problem with a simple "newb friendly" page is that every update to the phone changes what you need to do to root and what you can run.
For your NC5 phone, you need to use Towelroot to root it. That gets you root, but you're stuck with the stock bootloader. That means that you can't directly run a custom ROM. You can use Safestrap to allocate space for an alternative ROM, which is almost the same as a fully unlocked phone. The big thing you lose is that you can't run arbitrary ROMs, just what's compatible with the stock kernel. No CM, no AOSP.
So, read up on Towelroot and Safestrap. Once you have those down, you should be n the way.
Yeah, I got towel root already installed, supersu running and added to system and Knox disabled. Where should I be looking at roms that I can run under safestrap? Or should I say which section of the forums? Thank you for your response btw.
tong6998 said:
Yeah, I got towel root already installed, supersu running and added to system and Knox disabled. Where should I be looking at roms that I can run under safestrap? Or should I say which section of the forums? Thank you for your response btw.
Click to expand...
Click to collapse
Usually, roms that are compatible with safestrap are labeled as such. Since nc5 doesn't allow custom kernels, you will stuck with touchwiz kernels, so usually the roms will look like the stock samsung experience or a themed version. If you want an aosp themed safestrap rom, get eclipse rom. If you want a 99% gpe s4 rom download the gpe edition safestrap rom( it has some bugs though).
Usually roms are located at the "Android development" section of the forum. The gpe rom thread is in the general section.
tong6998 said:
Yeah, I got towel root already installed, supersu running and added to system and Knox disabled. Where should I be looking at roms that I can run under safestrap? Or should I say which section of the forums? Thank you for your response btw.
Click to expand...
Click to collapse
The thing to keep in mind, is that safestrap loads too late to be able to replace the kernel. This is the limiting factor, your stuck on the stock kernel... Different versions of android and different versions of kernels may have slightly different functions/parameters coded into the kernel, so calling a newer function or calling a function with parameters that no longer match the new style will fail.... so if the rom wasn't directly designed for the stock kernel of the same version your using it likely won't work.
In practice that means you need a rom based on TW, that is the same version (NC5) as you are currently using. Not sure but there are likely a few changes the Rom make needs to add for safe strap compatibility... Basically when you look at the Rom's thread it will list a baseband (NC5) and say its safestrap compatible.
Thanks to all of you, that clears up a lot of confusion I had. Now where do I find out (or how do I decifer) if I'm MJ7/MK2/ME7/MI1? Or am I correct in assuming I'm NOT (all the builds I see for safestrap mention those only no NC5.
Hi,
so I am having issues with the Wifi on my, recently acquired, LG V30.
I have got a strange model, L-01K, from Japanese provider DOCOMO.
I have unrooted / flashed .. currently running Havoc 3.11 on Android 10.
The wifi often loses connection/signal and in order to restore requires a complete device reboot.
Looking for some help.
Regards,
H.
haevaristo said:
Hi,
so I am having issues with the Wifi on my, recently acquired, LG V30.
I have got a strange model, L-01K, from Japanese provider DOCOMO.
I have unrooted / flashed .. currently running Havoc 3.11 on Android 10.
The wifi often loses connection/signal and in order to restore requires a complete device reboot.
Looking for some help.
Regards,
H.
Click to expand...
Click to collapse
Check your network stability? Don't use Havoc?
ldeveraux said:
Check your network stability? Don't use Havoc?
Click to expand...
Click to collapse
Is this a joke ?
Not really a joke... did the phone work fine on a stock ROM? You never told us what you came from.
How did you get to Havoc 10? As far as I've seen, Pie ROMs often have issues after install... I can't imagine 10-roms to be any better. Did you try any of the fixes mentioned in the ROM threads instead of just asking here? Sounds like it's probably ROM specific...
Well, is it my first custom, so I have no past experience and I don't know if this is specific to the ROM or the firmware drivers, or etc... hence I am asking around here for some support.
I assumed it was clear where I cam from, I came from stock. I only had the phone stock for a short period so I do not know if it was better or not before flashing. The phone was trully horrible with all the Japanese software crap on it.
I think I saw somewhere that this phone is known to have crappy drivers from LG.
haevaristo said:
Well, is it my first custom, so I have no past experience and I don't know if this is specific to the ROM or the firmware drivers, or etc... hence I am asking around here for some support.
I assumed it was clear where I cam from, I came from stock. I only had the phone stock for a short period so I do not know if it was better or not before flashing. The phone was trully horrible with all the Japanese software crap on it.
I think I saw somewhere that this phone is known to have crappy drivers from LG.
Click to expand...
Click to collapse
You also don't have a model number I've ever seen before, nor is it mentioned in the WTF thread. We have no clue what you installed here or how you did it, so I would suggest flashing one of the stock ROMs through TWRP if that's your bag. The Havoc ROM used in this forum is v3.9, again don't know how you got 3.11
Perhaps its not 3.11 ... I got it from the V30 Telegram group ... the zip file is "Havoc-OS-v3.11-20201128-joan-Unofficial.zip", I cannot seem to find the running software version, so I dont know how to check ... I am also trying to get some help there but I thought it wouldn't hurt to ask here as well.
are you rooted and or unlocked bootloader?
Also I've never heard of there being an issue with WIFI on this device.
Yes. TWRP installed as well
You say you came from stock, but WHAT stock? Oreo? Pie? US998? Something else? All this matters. You can't just slap a ROM on without having the rest of the stuff prepared on this phone.
As others mentioned, the model number doesn't make sense to us, so it could be some weird stock ROM that is not compatible with Havoc (or other custom ROMs). Even for many of these, you need to start with a known stock ROM, so that the proper blobs (binaries) are present as well as the partition layout in the phone. As you don't seem to know what it was (eg US998 is preferred) then I'd recommend you start there and then move forward. This means Frankensteining to US998, then moving forward.
Of course, given your weird model number, this may not be advised either... but if you want to try that's where I'd start.
OK.
So, phone came with stock Docomo android 8. Dont know too many details as I didnt kept it long.
Then I had some discussions on telegram group, where people advised me to unroot the phone, and install TWRP. It was mostly same as described in the thread for the LGv30 here in the forums.
I had to install a pre 2018 ROM version, using samsungs tools.
I don't recall anymore all the details order i did things from this on, I followed the steps as advised ... but I had to flash a V300 to H930 ROM. I also remember that an important step in the flashing process was not to flash modem, xbl and xbl2. So I did skip those.
Then initially I rooted Revolution Remix android 9.0, from stock android 10.0 ... by mistake, then I reverted back and I installed Havox android 10.0 instead.
The stock filename was "H93020d_00_OPEN_EU_OP_0326.kdz" and "V300_to_H93031a_converter.zip".
Edit: perhaps it wasnt Android 8 but rather 9 as someone corrected, this phone did not shipped with android 8. As mentioned, I did not keep the phone stock for long as it was literally unsuable with all the Japanese software, so I have not paid too much attention.
haevaristo said:
OK.
So, phone came with stock Docomo android 8. Dont know too many details as I didnt kept it long.
Then I had some discussions on telegram group, where people advised me to unroot the phone, and install TWRP. It was mostly same as described in the thread for the LGv30 here in the forums.
I had to install a pre 2018 ROM version, using samsungs tools.
I don't recall anymore all the details order i did things from this on, I followed the steps as advised ... but I had to flash a V300 to H930 ROM. I also remember that an important step in the flashing process was not to flash modem, xbl and xbl2. So I did skip those.
Then initially I rooted Revolution Remix android 9.0, from stock android 10.0 ... by mistake, then I reverted back and I installed Havox android 10.0 instead.
The stock filename was "H93020d_00_OPEN_EU_OP_0326.kdz" and "V300_to_H93031a_converter.zip".
Click to expand...
Click to collapse
You're ostensibly trying to combine 2 tutorials and forums to fix your problem. My guess is that flashing all those random ROMs, unrooting to install TWRP (?!?!), and using a Samsung tool definitely were not the right move. I'd advise against doing anything else unless @ChazzMatt gives his blessing, but he's away for a bit. Either that or ask for your Telegram friends to fix what they broke.
Also, wtf is docomo? The V30 did not come stock with Android 8.
ldeveraux said:
You're ostensibly trying to combine 2 tutorials and forums to fix your problem. My guess is that flashing all those random ROMs, unrooting to install TWRP (?!?!), and using a Samsung tool definitely were not the right move. I'd advise against doing anything else unless @ChazzMatt gives his blessing, but he's away for a bit. Either that or ask for your Telegram friends to fix what they broke.
Also, wtf is docomo? The V30 did not come stock with Android 8.
Click to expand...
Click to collapse
If you had read my earlier posts, I explain who is docomo and why I have such a weird model.
They are not my 'Telegram friends' but a community of people who use the LG V30. From what I gather it seems several of them are very active in ROMs, fixes and also part of the XDA forums here. They continue trying to help me however I though it would not hurt to also ask here in parallel ... it is also far easier for someone who later may face the same issues, to benefit from the solution if they can find this thread. Perhaps it was a mistake, this reminds me why I dont really miss much using forums ...
Using the LG tool was definitely the right move as written everywhere in the forums here and advised by anyone you ask to directly. As a first step, you need to break the encryption/security on the phone and you can only do that by reverting to an older version, preJuly 2018, where a known exploit exists. And guess what, until you root the phone, you can only do that by using a tool developed by LG.
And yes, I am definitely trying to combine several tutorials as there simply is no single tutorial or source of information.There are also no instructions, or even knowledge, for my model on the forums, and since the information is vague, outdated or incomplete on the different threads, you simply have no choice other than combining it. I followed the instructions as advised by my 'Telegram friends' considering it was clear I had to Frankenstein to something anyhow and the information they gave me, It all made sense, when compared to the forums information and according to the rationalle that they gave. So I took the risk. It worked without me bricking my phone, so I consider that a success.
It was definitely not 'random ROMs', if you go into the XDA section on LGv30 it is clearly explained why you need each of those and how. Its only the specifics, and versions, for my case that is not clear.
Seriously dude, you obviously have not enough knowledge nor interest in helping, .. so why don't you do me a favor, ignore this thread and go spend your time somewhere else and let others who can actually help reply... thanks, seriously!
Oh OK, no problem. Hope you and the other user who bothered replying twice can fix your cockup. With the 0 Likes and 2 weeks on XDA, I'm sure you'll solve it immediately.
... another really helpfull post, you really never disappoint ...
You really need to be far more clear in what you are doing or did. Don't blame the other users for your mistakes, nor should you complain to them when they're trying to help you with limited info. If you want help, you need to give a LOT more info. And you did, indeed, flash multiple different custom ROMs, which is a recipe for trouble.
Your terminology is also confusing, as you keep saying "unroot" and then install TWRP. You need to unlock the bootloader to install TWRP, maybe that's what you mean. Unrooting is a very different operation. You need to be precise in what you are asking for help with, otherwise you'll get bad info from anyone. Know the terms and use them properly, otherwise we can't help you... bad info will always lead to trouble.
Bottom line, as far as I know, there's only one way to do this right on the V30, which we can only assume you have. If you want to proceed, then you need to focus on one process and not try to mix with every other person's idea of what's right. Chazz has been great on this, and has provided detailed info... follow that.
Again, I won't tell you to do this because I don't want you to blame me if you brick the phone. So, if you want to proceed, you do so at your own risk. That said, I would start by getting to US998 stock ROM via KDZ. Follow the Frankenstein thread hereon XDA to see how to get there first. Once there, check to see that the phone operates properly - it should. If it doesn't then stop jumping around and fix that first.
Once all is good on that stock ROM, follow the WTF thread to install TWRP again (KDZ will remove it), with the version mentioned there (there may be newer versions, but you need to stick to what's detailed there to prevent problems, as those are the ones that are tested and known to work). Once you get that done, again, make sure the phone is working properly... then you can consider going to a custom ROM.
If you decide to move ahead, then you need to read the requirements of the custom ROM carefully. Most PIE ROMs, for example, require the PIE blobs, so you need to get to a stock PIE ROM as prescribed before going to a custom ROM. I don't know what the specifics are for 10-ROMs, so you'll have to see what's possible and how it's done based on that ROM's thread.
Well, I am not blaming anyone for my mistakes nor am I complaining to anyone trying to help me, you've been really helpful so far, not only giving ideas on what could be done but as well trying to teach and correct me, and I haven't complained about it.
However, the other guy is literally just patronizing.
Even for me who is new to this, I can clearly see by his comments that he doesn't know what he is talking about, this device in particular, and he even didn't bother to read Chad's thread to try and understand the typical, normal, process.
Just feel free to read again everything that I posted and everything that he posted, 'helping' me, its all registered above.
As for your points you are right, I am trying my best to understand all the details, but as you can notice I have literally just registered here in the forums and this is in fact my first attempt at customizing an android phone ROM.
I have initially, wrongly assumed, that the information I provided was enough and I expected this to be a more common issue that someone with experience could quickly point me to the problem or what I did wrong. And yes, my terminology is wrong, nothing I can do about that at the moment. The posts and information are literally full of jargon, abreviations, code names and sometimes spread over multiple replies or even different threads, this is not for the faint of heart and anyone new will always struggle to understand it all, no matter how smart they are, ... I am literally doing my best to try and catch up as quickly as possible.
So, wherever you read 'unroot' earlier, just replace with "unlock bootloader". As far as I understood it, and as I recall all the things that I have done, I have literally followed the process outlined in Chad's post here in XDA ... I have however frankensteined using the V300 to H930 patch, also according to instructions outlined here (I'm not sure at this moment, if that is also a post by Chad) as per the advice I received in the Telegram group. BTW, I have looked into the telegram group and Chad is also part of it, though he has not been active in the past days, so its not just a random group of people as pointed out earlier.
Anyway .. as far as I was explained, this device requires you to first flash A9 before going straight to A10, otherwise there are some 'blobs' issues with it, i dont really understand the details. During the process of discussion in the chat group, there was some miss understanding and I ended up going straight to A10 and then I installed LineageOS. Later when we noticed this, I tried to correct this by then going back again to A9 and then A10 and then finally I installed Havoc instead of going back to LOS.
So there was some mix up there, and I mentioned this not to blame anyone but just because I thought this could potentially be a source of the problems I am facing and a hint at the potential solution.
Thank you for your suggestion, I am literally half way in the process of sort of doing what you suggest. I am now back to stock A9 and see if the WiFi behaves better. I did flashed stock via TWRP, not KDZ. So I did not went all the back as you suggest. If this proves unsuccessful I might do that.
Not that he/she/they needs my defense, but ldeveraux is a senior member (more-so than me) and has tons of knowledge on this device, in my experience. That's all I want to say about that.
So it sounds like the problem was jumping to A10 from A9. Also, using instructions from one ROM to end up jumping to another. Each ROM has its needs/requirements, so you can't really do that. Also, at least on this phone, going between Android levels is somewhat tricky, so you can't just jump around from what I've read.
Yes, there can be some jargon and such. Chazz's thread (post 193) explains most, if not all, of that, but if you're missing something I strongly recommend reading MUCH more, rather than just moving forward. It is a very long thread, but it's very important you read through ALL of it, and understand it before moving forward. Then read it again. Don't read it on a phone/device - use a computer because browsers and apps have a bad habit of truncating the message. These are Chazz's recommendations as well, for good reason (and also at the top of this thread). I did a TON of reading before I did my phone unlocking/rooting, and with that thread alone, so I have read it MANY times myself (well, at least the older revision when I did my hacking) and I didn't have to ask questions... so I know the answers can be found.
US998 is the best "foundation" to start with for various reasons. Fact is, US998 should work on pretty much any carrier to start with, so it's a great foundation for that reason too. That's why I suggest starting there to be sure you have a good, working basis.
I have read that if you go to A9 or A10, going to another version may require going all the way back to Nougat first. You may need to do that now, if you want to get back to a stable US998 to begin with. The Pie/10 threads probably have info on this... I haven't read them up myself as I don't want to bother. I have stuck with Oreo because it does everything you need anyway... I see no advantage to Pie or 10. I believe Chazz has also stayed on Oreo for this reason.
Senior or no senior, he should just not patronize people. He has clearly the option to ignore if he doesn't feel like helping .. I have even politely asked him to do so ... but instead he decided to come back and patronize further ...
I rest my case...
OK. So, I am still in the process of finalizing everything, but I think it is safe to say that for the L-01K models, the US998 is the safe way to go.
Make a backup of your modem partition, then do the Frankenstein to US998 then once you are done, you can restore you original modem partition and everything should work fine!!