Hi everyone. I am on rooted stock 4.2.2 MDK and want to install a new 4.4.2 ROM. I haven't done any flashing in about a year (since my GNEX) and wanted to know if it's smart to go from 4.2.2 MDK right to the latest Hyperdrive ROM (which seems like one of the best). Any thoughts?
mryank9 said:
Hi everyone. I am on rooted stock 4.2.2 MDK and want to install a new 4.4.2 ROM. I haven't done any flashing in about a year (since my GNEX) and wanted to know if it's smart to go from 4.2.2 MDK right to the latest Hyperdrive ROM (which seems like one of the best). Any thoughts?
Click to expand...
Click to collapse
I did. Hyperdrive 16.1. No regrets. Just be sure you "Loki" & install a custom recovery such as TWRP or Philz Touch.
wtherrell said:
I did. Hyperdrive 16.1. No regrets. Just be sure you "Loki" & install a custom recovery such as TWRP or Philz Touch.
Click to expand...
Click to collapse
Sorry for all the questions but what do you mean by Loki? Also once I install Hyperdrive (or any Kitkat ROM) do I still have the MDK bootloader?
mryank9 said:
Sorry for all the questions but what do you mean by Loki? Also once I install Hyperdrive (or any Kitkat ROM) do I still have the MDK bootloader?
Click to expand...
Click to collapse
Well if your phone is already rooted and has a custom recovery on it you're good to go.
I don't run TW ROMs really but from my experience just flash the TW KToonsez kernel after flashing the ROM and you'd be all set. Not sure what kernel comes with HD ... Just read the HD post as I'm sure SBreen has most your questions covered.
And yes you'd still have your MDK bootloader. Only way you'd lose that is by using Odin and any other firmware other than MDK... so don't do that!!
Or by taking an OTA update from Verizon. Don't do that either!!
Sent from my SCH-I545 using Tapatalk
Use flashify to install latest twrp. Flash hyperdrive normally and yes you will still have the mdk bootloader
Sent from my SCH-I545 using Tapatalk
And by the way... Here's exactly what Loki is if you feel like reading a bit
http://forum.xda-developers.com/showthread.php?p=41751943
Sent from my SCH-I545 using Tapatalk
Awesome, thanks guys. Currently have TWRP recovery installed, not sure if its the most recent though. Currently making a nandroid backup with it right now. Good to know things can be as easy as the GNEX days lol, appreciate the help
joshm.1219 said:
Use flashify to install latest twrp. Flash hyperdrive normally and yes you will still have the mdk bootloader
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Would I need to upgrade to a new baseband?
mryank9 said:
Would I need to upgrade to a new baseband?
Click to expand...
Click to collapse
You don't need to but I would recommend trying any modem newer than mj7, because they take advantage of the new lte bands.
Sent from my SCH-I545 using Tapatalk
joshm.1219 said:
You don't need to but I would recommend trying any modem newer than mj7, because they take advantage of the new lte bands.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Any chance you have a link? Trying to take advantage of the new LTE bands was the main reason I am updating to 4.4.x
mryank9 said:
Any chance you have a link? Trying to take advantage of the new LTE bands was the main reason I am updating to 4.4.x
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2487298
Flash the modem only versions. You can use retail or dev edition modems but I prefer retail if you're going to stay on touchwiz. Use mj7, mk2, nc2, or nc5 modems. Try them all out to see what works best for you.
If all you're trying to do is access the new aws lte (rebranded as xlte) then the modem is all you need to update.
Sent from my SCH-I545 using Tapatalk
mryank9 said:
Hi everyone. I am on rooted stock 4.2.2 MDK and want to install a new 4.4.2 ROM. I haven't done any flashing in about a year (since my GNEX) and wanted to know if it's smart to go from 4.2.2 MDK right to the latest Hyperdrive ROM (which seems like one of the best). Any thoughts?
Click to expand...
Click to collapse
Are you sure you are mdk?
sent by bajarom v2.2 kitkat
decaturbob said:
Are you sure you are mdk?
sent by bajarom v2.2 kitkat
Click to expand...
Click to collapse
I'm assuming so? check out the screenshot
{
"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 SCH-I545 using Tapatalk
mryank9 said:
I'm assuming so? check out the screenshotView attachment 2803652
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I was just asking as it seems you aren't familiar with loki.
sent by bajarom v2.2 kitkat
If you don't like the laggy TW roms go try the Google Play Edition ROM.
http://forum.xda-developers.com/showthread.php?t=2643031
Sent from my Nexus 7 using Tapatalk
Related
To start off, I love you @Hashcode for being the talented developer you are; making safestrap for our beauty.
Moving on...
Requirements
Safestrap
Atleast 4 gigs of free memory.
A rom.
Battery be at least 50%
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Once you have met the pre-requisites above you may continue.
Procedure to install any rom on the stock partition over stock
Step 1.) Reboot and select recovery
{
"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"
}
Step 2.) Select boot options. Create a rom slot on rom slot 1. Keep the default memory values because the slot is only temporary.
In the meantime while its loading, go ahead and hit that thank you button :good:
Step 3.) After the virtual partition is made go back to /boot options/rom-slot-1 and activate the slot.
Step 4.) Go to the safestrap main menu and click install, then find the rom you want and flash.
Step 5.) Now that you have a rom installed on your virtual partition...
Go back to the main menu and back it up, you only need to
Note: backup both "DATA" & "SYSTEM" (This is a crucial part of the process and can not be skipped)
Step 5.) Go to /boot options/stock rom and activate it, then go to the rom-slot-1 and delete the partition.
Step 6.) Restore your baked up rom-slot-1 to your stock partition. Make sure to restore date and system.
Step 7.) Enjoy :good::good:
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I am new to ss so please excuse my noobness. Why cant you just flash the new rom to the stock slot? Wouldnt this only be using one slot as well?
Will following this process trip the Knox e-fuse?
njfoses said:
I am new to ss so please excuse my noobness. Why cant you just flash the new rom to the stock slot? Wouldnt this only be using one slot as well?
Click to expand...
Click to collapse
That's what I did. No problems here...
Running HD on the Stock Slot
Sent from my SM-N900V using XDA Premium HD app
njfoses said:
I am new to ss so please excuse my noobness. Why cant you just flash the new rom to the stock slot? Wouldnt this only be using one slot as well?
Click to expand...
Click to collapse
That's what I did (Didn't know it was taboo!) and everything's fine. Knox is still 0x0 and everything. I can't get Custom status to go away, but I think that's just how MJ7 has been for everyone.
Pfhortune said:
That's what I did (Didn't know it was taboo!) and everything's fine. Knox is still 0x0 and everything. I can't get Custom status to go away, but I think that's just how MJ7 has been for everyone.
Click to expand...
Click to collapse
Install xposed framework and use the Wanam xposed app to fix that.
Sent from my SM-N900V using XDA Premium HD app
Pfhortune said:
That's what I did (Didn't know it was taboo!) and everything's fine. Knox is still 0x0 and everything. I can't get Custom status to go away, but I think that's just how MJ7 has been for everyone.
Click to expand...
Click to collapse
I look at it as a cool thing that mine is custom.... I keep it.
Sent from my SM-N900V using xda app-developers app
njfoses said:
I am new to ss so please excuse my noobness. Why cant you just flash the new rom to the stock slot? Wouldnt this only be using one slot as well?
Click to expand...
Click to collapse
mchief298 said:
That's what I did. No problems here...
Running HD on the Stock Slot
Sent from my SM-N900V using XDA Premium HD app
Click to expand...
Click to collapse
Pfhortune said:
That's what I did (Didn't know it was taboo!) and everything's fine. Knox is still 0x0 and everything. I can't get Custom status to go away, but I think that's just how MJ7 has been for everyone.
Click to expand...
Click to collapse
The reason I created this tutorial is because just flashing would never work for me, it's weird. When I try to just flash, it never gets wiped properly. And I think, even if that method works, it's safer.
Sent from my SM-N900V using Tapatalk
mchief298 said:
Install xposed framework and use the Wanam xposed app to fix that.
Sent from my SM-N900V using XDA Premium HD app
Click to expand...
Click to collapse
Doesn't work since I came to MJ7. Neither does the SysScope normalizer Xposed module.
Brandonrz said:
The reason I created this tutorial is because just flashing would never work for me, it's weird. When I try to just flash, it never gets wiped properly. And I think, even if that method works, it's safer.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Oh, I wholeheartedly agree that your method is safer. I was reckless when I flashed mine.
Pfhortune said:
Doesn't work since I came to MJ7. Neither does the SysScope normalizer Xposed module.
Oh, I wholeheartedly agree that your method is safer. I was reckless when I flashed mine.
Click to expand...
Click to collapse
And you always have a backup. If anything goes wrong while flashing in the virtual slot it doesn't affect your main system and brick your phone...
Sent from my SM-N900V using Tapatalk
Ok again I apologize for being a noob with ss, never had to use it with my previous htc devices. If I backup my stock ROM in ss, then wipe the stock slot and install a new ROM, wouldn't I be able to then wipe stock slot again and restore stock backup if needed? I don't have a need to have multiple roms loaded. Thanks.
Sent from my vzw note 3
@njfoses Correct, but I would recommend using mymethod of installing a new rom to your stock partition. You have less chances of screwing up your phone by flashing. And it's cleaner
Sent from my SM-N900V using Tapatalk
Will it be an issue if I'm on MI9 and flash a ROM that is an MJ7 build? I read somewhere that it would be a good idea to Odin the MJ7 kernel/modem but I can't find those files anywhere.
Worked great for me. I must admit I was quite hesitant but with beans rom being out I took the plunge. So far so good!!
Sent from my SM-N900V using Tapatalk 2
Never used SS before. I think I am going to take the plunge using this tut. Thanks. Wish me luck lol.
haza12d said:
Will it be an issue if I'm on MI9 and flash a ROM that is an MJ7 build? I read somewhere that it would be a good idea to Odin the MJ7 kernel/modem but I can't find those files anywhere.
Click to expand...
Click to collapse
It will be an issue I think I read somewhere. Just flash the whole build via odin.
repsol_23 said:
Worked great for me. I must admit I was quite hesitant but with beans rom being out I took the plunge. So far so good!!
Sent from my SM-N900V using Tapatalk 2
Click to expand...
Click to collapse
Glad to hear
dukins said:
Never used SS before. I think I am going to take the plunge using this tut. Thanks. Wish me luck lol.
Click to expand...
Click to collapse
Have fun
Sent from my SM-N900V using Tapatalk
Trying to make sure I understand the backup part of this process. I see that the backup I make is the ROM I just installed in the virtual disk. Is it assumed that I've backed up my "stock ROM" prior to restoring the ROM I just installed in the other slot?
My goal is to have a copy of my rooted stock ROM before I do anything on the phone.
Thanks
bossei said:
Trying to make sure I understand the backup part of this process. I see that the backup I make is the ROM I just installed in the virtual disk. Is it assumed that I've backed up my "stock ROM" prior to restoring the ROM I just installed in the other slot?
My goal is to have a copy of my rooted stock ROM before I do anything on the phone.
Thanks
Click to expand...
Click to collapse
Yes than by all means, if you want a backup of your stock rooted ROM, Back it up too! These instructions have you erase the STOCK rom slot, so if you do not back it up, the only way to get it back would be to ODIN back, or find a flashable stock ROM -- in other words, the best option is to backup your stock ROM so that you can easily put it back into the STOCK slot, than simply go back into Android, and uninstall the safestrap, and its as if you never did anything.
I too am a n00b with safestrap...
Sent from my SM-N900V using XDA Premium 4 mobile app
n00b1269 said:
I too am a n00b with safestrap...
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That's why I wrote up a tutorial with pictures, it made the tutorial take like 1 & half to make up. I done mind because it's nothing compared to what @Hashcode & @beanstown106 do for us and sacrifice.
Sent from my SM-N900V using Tapatalk
Looks like the credible SamMobile has 4.4.2 kitkat in their palms. We could expect a leak to be soon, in the past they have been really good about leaking firmware like how they already have for the s4 by contacting thier "elite friends."The picture below is a screenshot of the kitkat easteregg and wrote note 3 on it. Some of the things im most looking forwards to is Google wallet and the ability to hide apps from the app drawer. FUNFUNFUN
http://www.youtube.com/watch?v=8E4dspICPJE
Basicly saying we'll leak it when it become more stable. It doesn't surprise me considering the s4 got it leaked already, but what does surprise me is that they got a kitkat leak first, considering we have the newer/premium device.
SamMobile on twitter posted "#NEXTUPDATE (Too buggy atm)"
{
"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"
}
Excited.
Sent from my SM-N900V using Tapatalk
@Brandonrz
"...what does surprise me is that they got it first."
Tell me a bout it. Maybe Samsung's working harder on ours?
theROMinator said:
@Brandonrz
"...what does surprise me is that they got it first."
Tell me a bout it. Maybe Samsung's working harder on ours?
Click to expand...
Click to collapse
I was surprised that the s4 got the first leak.
Sent from my SM-N900V using Tapatalk
OK just a thought but if we do get the release.... the leaked one could there be a chance that there is some way we could unlock the bootloader.. being that it is a leak not fully locked down like the officials would be.
johnminator said:
OK just a thought but if we do get the release.... the leaked one could there be a chance that there is some way we could unlock the bootloader.. being that it is a leak not fully locked down like the officials would be.
Click to expand...
Click to collapse
They leak will be as locked down if it's for our variant... And either way, chances are It will be for the international version so either way it's irrelevant. But it shouldn't be too hard to port it hopefully.
Sent from my SM-N900V using Tapatalk
Tmobile ppl are running this now.... so we shall see
Sent from my SM-N900V using XDA Premium 4 mobile app
Just released.
Sent from my SM-N900V using xda app-developers app
staywide8 said:
Just released.
Sent from my SM-N900V using xda app-developers app
Click to expand...
Click to collapse
Yep, for international version, you can get it here http://www.sammobile.com/2014/01/12...-galaxy-note-3-sm-n9005/#.UtMGEIhqC48.twitter Hopefully some of the dev's can get this working for us. DO NOT TRY INSTALLING ON THE VZW VERSION, YOU WILL ALMOST CERTAINLY BRICK!
This wont work with the verizon N3 will it.
EDIT: Anyone have a mirror that isnt slow as sin
---------- Post added at 03:10 PM ---------- Previous post was at 02:56 PM ----------
njfoses said:
Yep, for international version, you can get it here http://www.sammobile.com/2014/01/12...-galaxy-note-3-sm-n9005/#.UtMGEIhqC48.twitter Hopefully some of the dev's can get this working for us. DO NOT TRY INSTALLING ON THE VZW VERSION, YOU WILL ALMOST CERTAINLY BRICK!
Click to expand...
Click to collapse
well poop
njfoses said:
Yep, for international version, you can get it here http://www.sammobile.com/2014/01/12...-galaxy-note-3-sm-n9005/#.UtMGEIhqC48.twitterDO NOT TRY INSTALLING ON THE VZW VERSION, YOU WILL ALMOST CERTAINLY BRICK!
Click to expand...
Click to collapse
Can this be installed on a Dev edition? Since it probably has the aboot partition included, will it lock the Dev edition phone? Once a dev makes this rom suitable for the retail version, is there a way to extract and repack the files without the aboot portion? How does one make an Odin-flashable file anyway if one has the partitions like boot.img, modem.bin etc? I've always been wanting to learn to make my own Odin .tar files in case I want to flash and don't have recovery installed.
Thanks
Isn't anyone concerned about this update, I mean look at the SE Android Status from N9005 from the test build it is currently showing as Enforcing. For those of us with the Retail SM-N900V doesn't this mean no more Safestrap Recovery? Also, if you go back and read about the Test Firmware it does a complete wipe of Data, so shouldn't we be worried about Root too? I certainly understand the excitement over 4.4.2 but isn't anyone paying attention to what the test build has done?
Hard to be excited about losing Root and Safestrap to get KitKat...
KachowPow said:
Isn't anyone concerned about this update, I mean look at the SE Android Status from N9005 from the test build it is currently showing as Enforcing. For those of us with the Retail SM-N900V doesn't this mean no more Safestrap Recovery? Also, if you go back and read about the Test Firmware it does a complete wipe of Data, so shouldn't we be worried about Root too? I certainly understand the excitement over 4.4.2 but isn't anyone paying attention to what the test build has done?
Hard to be excited about losing Root and Safestrap to get KitKat...
Click to expand...
Click to collapse
There is already root for the international version from chainfire but safestrap idk.
jparasita said:
There is already root for the international version from chainfire but safestrap idk.
Click to expand...
Click to collapse
You mean Root has been restored already on the international version, which this is mainly due to the Unlocked Bootloader, which it is simpler to restore Root on a device that has an Unlocked Bootloader as you just install/flash the SU.zip in custom Recovery and Root is restored, works for Unlocked devices. There lies the problem, for those of us with the retail SM-N900V if the KitKat update does a complete wipe on install deleting the internal storage all is lost, if SE is set to Enforcing it could be a cold winter.
KachowPow said:
There lies the problem, for those of us with the retail SM-N900V if the KitKat update does a complete wipe on install deleting the internal storage all is lost, if SE is set to Enforcing it could be a cold winter.
Click to expand...
Click to collapse
I'm pretty sure the Kingo folks might get us root again on Kit Kat in no time.
AngryManMLS said:
I'm pretty sure the Kingo folks might get us root again on Kit Kat in no time.
Click to expand...
Click to collapse
Idk...kitkat really doesnt seem to be a big deal. I have it running on another device, and its a minor update. I could live with 4.3 and a rooted device with safe strap
+1. Did nothing but mess up bluetooth on nexus 10.
Sent from my SM-N900V using XDA Premium 4 mobile app
AngryManMLS said:
I'm pretty sure the Kingo folks might get us root again on Kit Kat in no time.
Click to expand...
Click to collapse
It's not really Root I'm worried about, I'm more concerned with Recovery. If the SE status changes from "Permissive" to "Enforcing" there goes our ability to flash new custom 4.4.2 ROMs that I'm sure will come out. It will be like owning a SM-N900A.
KachowPow said:
Isn't anyone concerned about this update, I mean look at the SE Android Status from N9005 from the test build it is currently showing as Enforcing. For those of us with the Retail SM-N900V doesn't this mean no more Safestrap Recovery? Also, if you go back and read about the Test Firmware it does a complete wipe of Data, so shouldn't we be worried about Root too? I certainly understand the excitement over 4.4.2 but isn't anyone paying attention to what the test build has done?
Hard to be excited about losing Root and Safestrap to get KitKat... .
Click to expand...
Click to collapse
I was under the impression that the only data wipe was when people are Odin-ing the update, rather than accepting an OTA. On the past androids i had (incredible, thunderbolt, galaxy nexus, s3, note 10.1, nexus 7) i haven't had an update that wiped data from an OTA.
KachowPow said:
It's not really Root I'm worried about, I'm more concerned with Recovery. If the SE status changes from "Permissive" to "Enforcing" there goes our ability to flash new custom 4.4.2 ROMs that I'm sure will come out. It will be like owning a SM-N900A.
Click to expand...
Click to collapse
For some reason I don't think they are going to set it to enforcing. Because they haven't for the past 3 updates. Even if they did. Hash would be able to easily cook up ss because on the at&t note 3 and Verizon s4 and s3 are enforcing and he was able to do it... Never underestimate @Hashcode
Sent from my SM-N900V using Tapatalk
There are tons of exploits out there maybe ONE of them will work.
Report findings in this thread so we can keep track of what's been tried, and what failed.
Poot Failed
Motochopper Failed
IO Root Failed
Kingoroot Failed
VRoot Failed
Framaroot Failed
Vroot failed. I wrote kingo and they said they cant root KK.
IO root failed
Gesendet von meinem LG-D802 mit Tapatalk
mav744 said:
IO root failed
Gesendet von meinem LG-D802 mit Tapatalk
Click to expand...
Click to collapse
It's already listed
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Are there devs that is working on bringing root to kitkat? Just asking...apologize if there are
Root worked for me but I did it the long way. Reverted to D80010o using LG FLash Tools then used ioroot22 to root. Had AT&T push the q update. Stayed rooted. Got the KitKat D80020c update and updated. Root stuck.
So I am running KitKat rooted.
So if you do it this way, ioroot22 works.
However I suspect that you are looking for a solution once the KitKat update is installed, then to root. Of all the threads that I have read on the subject (all of them), there is no way that I am aware of to root KitKat once it is already installed.
NevetsDrassel said:
Root worked for me but I did it the long way. Reverted to D80010o using LG FLash Tools then used ioroot22 to root. Had AT&T push the q update. Stayed rooted. Got the KitKat D80020c update and updated. Root stuck.
So I am running KitKat rooted.
So if you do it this way, ioroot22 works.
However I suspect that you are looking for a solution once the KitKat update is installed, then to root. Of all the threads that I have read on the subject (all of them), there is no way that I am aware of to root KitKat once it is already installed.
Click to expand...
Click to collapse
Eventually phones shipped from LG will have KitKat pre-installed. So, yes I'm talking about rooting Kitkat, not keeping Root after Kitkat.
Let's set up a bounty!
robogo1982 said:
Let's set up a bounty!
Click to expand...
Click to collapse
Go on. Ill wait till bounty is set then ill upload
Originally Posted by robogo1982
Let's set up a bounty!
Click to expand...
Click to collapse
Go on. Ill wait till bounty is set then ill upload
Click to expand...
Click to collapse
Link or it didn't happen lol
Sent from my LG-D800 using xda app-developers app
muppetmaster916 said:
Link or it didn't happen lol
Sent from my LG-D800 using xda app-developers app
Click to expand...
Click to collapse
Haha no no, what is the point of the bounty. Ill attach a screenie then
{
"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"
}
Root Inc
DesertHawk said:
Haha no no, what is the point of the bounty. Ill attach a screenie then
Root Inc
Click to expand...
Click to collapse
Asking for money to release a root exploit... Typical XDA
Sent from my LG-D800 using XDA Premium 4 mobile app
Markyzz said:
Asking for money to release a root exploit... Typical XDA
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yep. No i really dont give but its uploading now and itll take ages as im uploading 2 ROM's first for D802. Both which are 2GB. And I need two D802 testers :/
Keep this crap out of my thread please.
Want to start a bounty? Do it on your own thread.
DesertHawk said:
Yep. No i really dont give but its uploading now and itll take ages as im uploading 2 ROM's first for D802. Both which are 2GB. And I need two D802 testers :/
Click to expand...
Click to collapse
I have D802, still need testers? Let me know!
MrDarkKV said:
I have D802, still need testers? Let me know!
Click to expand...
Click to collapse
KitKat Roms?
LG D802(Beast), Nexus 5, Galaxy S4, Note 10.1 2014, TF3OOT?
john0699 said:
KitKat Roms?
LG D802(Beast), Nexus 5, Galaxy S4, Note 10.1 2014, TF3OOT?
Click to expand...
Click to collapse
all this talk about kitkat is giving me the munchies lol
MrDarkKV said:
I have D802, still need testers? Let me know!
Click to expand...
Click to collapse
I also have a D802 , and it´s ready for testing ! :good:
NevetsDrassel said:
Root worked for me but I did it the long way. Reverted to D80010o using LG FLash Tools then used ioroot22 to root. Had AT&T push the q update. Stayed rooted. Got the KitKat D80020c update and updated. Root stuck.
So I am running KitKat rooted.
So if you do it this way, ioroot22 works.
However I suspect that you are looking for a solution once the KitKat update is installed, then to root. Of all the threads that I have read on the subject (all of them), there is no way that I am aware of to root KitKat once it is already installed.
Click to expand...
Click to collapse
What did u use to "retain" root?
He probably just updated via OTA. You can keep root permission like that. If he flashed KitKat .kdz and then rooted it, well, then it's a whole different story.
I'm hoping to find hotspot mod for note 3 on kit kat stock rom.
Sent from my SM-N900P using Tapatalk
shadricksimms said:
I'm hoping to find hotspot mod for note 3 on kit kat stock rom.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Here: droidforums.net/forum/android-news/255802-free-wifi-tether-galaxy-note-3-using-native-tether-app-no-root-no-hacks.html
Leave links plz
Sent from my SM-N900P using Tapatalk
DarkGrey said:
Here: droidforums.net/forum/android-news/255802-free-wifi-tether-galaxy-note-3-using-native-tether-app-no-root-no-hacks.html
Click to expand...
Click to collapse
This one is for Verizon tried it on our phone and does not work.
JSnively said:
This one is for Verizon tried it on our phone and does not work.
Click to expand...
Click to collapse
Try this way than:
http://www.youtube.com/watch?v=wLSWPaZI3rg
DarkGrey said:
Try this way than:
http://www.youtube.com/watch?v=wLSWPaZI3rg
Click to expand...
Click to collapse
That one will work if you are rooted not sure if OP is rooted sounded like he is not.
I'm going to try this right now..This is my setup on my note3
{
"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 SM-N900P using Tapatalk
Like I said I'm on kit kat
Sent from my SM-N900P using Tapatalk
This only puts your phone in a bootloop and have to take steps to fix your phone. If on kit kat update wait for new mods
Sent from my SM-N900P using Tapatalk
This is to show I am rooted as well I know what I'm talking about.you don't cause your not on kit kat
Sent from my SM-N900P using Tapatalk
JSnively said:
That one will work if you are rooted not sure if OP is rooted sounded like he is not.
Click to expand...
Click to collapse
Yes he's rooted, he's been messaging me about his issue. Still can't find a fix.
Wireless tethering for root users should work, but off the top of my head I don't remember the settings.
I always had luck with beta 2 of the app: https://code.google.com/p/android-w...tail?name=wifi_tether_v3_2-beta2.apk&can=2&q=
Check routing fix
Leave network open.
DarkGrey said:
Yes he's rooted, he's been messaging me about his issue. Still can't find a fix.
Wireless tethering for root users should work, but off the top of my head I don't remember the settings.
I always had luck with beta 2 of the app: https://code.google.com/p/android-w...tail?name=wifi_tether_v3_2-beta2.apk&can=2&q=
Check routing fix
Leave network open.
Click to expand...
Click to collapse
Well I'm in the same boat as him. I've tried what you told me to use and it doesn't work with either of the settings. I used hotspot so much before with 4.3.
I tried the Beta 2 with NAB and it doesn't work this time around...
DarkGrey said:
Yes he's rooted, he's been messaging me about his issue. Still can't find a fix.
Wireless tethering for root users should work, but off the top of my head I don't remember the settings.
I always had luck with beta 2 of the app: https://code.google.com/p/android-w...tail?name=wifi_tether_v3_2-beta2.apk&can=2&q=
Check routing fix
Leave network open.
Click to expand...
Click to collapse
shadricksimms said:
I'm going to try this right now..This is my setup on my note3
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
hmm How are you on KK 4.4.2 and still using MI3 baseband?
slow_one said:
hmm How are you on KK 4.4.2 and still using MI3 baseband?
Click to expand...
Click to collapse
Good catch, lol wow!!!
For my sake I'm correctly on nab running sac's kk rom. 4.4.2
Nickitt said:
Good catch, lol wow!!!
For my sake I'm correctly on nab running sac's kk rom. 4.4.2
Click to expand...
Click to collapse
That's the original baseband for when the phone was first released.
But still the thought recurs...let us just post, "it's not working..."
Sent from my SM-N900P using Xparent BlueTapatalk 2
Actually, I did what @rlmiller said to do, was simple and got my wifi tether producing a signal again. You need to do a clean install if flashing the Rom you are on dirty doesn't fix the hotspot.
Rlmiller said:
When I do a CLEAN install...the process is as follows:
in TWRP.....
WIPE>advanced Wipe> selectdalvik cache, system, data, INTERNAL STORAGE, cache then swipe to wipe.... I do this twice
them go back and select FORMAT DATA....type yes and press go.... I do this twice...
then go back to main menu. and select reboot> RECOVERY....wait for recovery to restart.
Now install rom
tried service.jar from MJ4 days and it just made the phone hang...:laugh: Knew that it was gonna happen but what the heck, tried anyway... Guess wait for the updated service.jar..
Just wait for developers to come up with a solution.all old mods do not work on kit kat
Sent from my SM-N900P using Tapatalk
Nickitt said:
Actually, I did what @rlmiller said to do, was simple and got my wifi tether producing a signal again. You need to do a clean install if flashing the Rom you are on dirty doesn't fix the hotspot.
Rlmiller said:
When I do a CLEAN install...the process is as follows:
in TWRP.....
WIPE>advanced Wipe> selectdalvik cache, system, data, INTERNAL STORAGE, cache then swipe to wipe.... I do this twice
them go back and select FORMAT DATA....type yes and press go.... I do this twice...
then go back to main menu. and select reboot> RECOVERY....wait for recovery to restart.
Now install rom
Click to expand...
Click to collapse
Those are rom-specific instructions that are absolutely unnecessary for many on these forums.
I'm glad they worked for you, but there are TouchWiz KitKat roms on the grid now and in the pipeline for this phone where such guidance is both unnecessary and most certainly unwarranted.
Sent from my SM-N900P using Xparent BlueTapatalk 2
I think I am screwed. What is this?
{
"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 SCH-I605 using Tapatalk
No idea on every you possibly did but was bored at work and nowhere does it recognize your version. Sorry man.
Sent from my SCH-I605 using Tapatalk
Dang. Im screwed
Sent from my SCH-I605 using Tapatalk
Hey just seen this and remembered about you but in case you haven't figured it out here you go. http://www.droid-life.com/2014/05/0...-gets-minor-update-includes-roaming-on-telus/
Sent from my SCH-I605 using Tapatalk
Thanks. Saw that too.
Sent from my SCH-I605 using Tapatalk
Download link???
Quick note to anyone coming from MJ9, this update can remove your root, and the MJ9 saferoot method will not work on it.
Happy updating to those out there!
I've lost root too..does anyone know of a root process for the build? I haven't tried the process listed in the Development section as it doesn't say anything about the VRUAND3 build...
Thanks!!
Saferoot is not working with the new update VRUAND3 so don't waste your time.
Sent from my SCH-I605 using Tapatalk
Latindude001 said:
Saferoot is not working with the new update VRUAND3 so don't waste your time.
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
Forever or is there plans to include it soon in the next safeboot build?
gee1000 said:
Forever or is there plans to include it soon in the next safeboot build?
Click to expand...
Click to collapse
At the moment we don't know yet. But I was told today that you can go back to 4.1.1 with a great risk of bricking your device.
Sent from my SCH-I605 using Tapatalk
how?
Latindude001 said:
At the moment we don't know yet. But I was told today that you can go back to 4.1.1 with a great risk of bricking your device.
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
If you updated to 4.3 you cannot go back to 4.1.1
Also going to 4.1.1 is touchy. If you were to go back you need to go to 4.1.2
Basically if you have the official 4.3 update and beyond you cannot unlock the bootloader or in some instances root.
I am using the Skynote Rc2.5 ROM but I am technically coming from 4.1.2. There is no official 4.2.x update for this version of the Note 2.
bvzxa3 said:
If you updated to 4.3 you cannot go back to 4.1.1
Also going to 4.1.1 is touchy. If you were to go back you need to go to 4.1.2
Basically if you have the official 4.3 update and beyond you cannot unlock the bootloader or in some instances root.
I am using the Skynote Rc2.5 ROM but I am technically coming from 4.1.2. There is no official 4.2.x update for this version of the Note 2.
Click to expand...
Click to collapse
Right, I was asking because the ND3 update doesn't appear to be any different than MJ9 firmware wise except for what I assume are mostly changes in the baseband to accomodate the Telus bands. I would think that safeboot will be updated easily for this minor build but I am not any expert by any means.
I also saw people talking about for the same Telus update for the S3 to just Odin backflash VRUCNC1 4.3 to VRUCML1 4.3 with success (http://forum.xda-developers.com/showthread.php?t=2575661&page=153). Anyone tried that? I might actually try it myself to get root back. I don't this new "update". I think VZ did this more to take away root than add some really necessary Canadian roaming anyway.
gee1000 said:
Right, I was asking because the ND3 update doesn't appear to be any different than MJ9 firmware wise except for what I assume are mostly changes in the baseband to accomodate the Telus bands. I would think that safeboot will be updated easily for this minor build but I am not any expert by any means.
I also saw people talking about for the same Telus update for the S3 to just Odin backflash VRUCNC1 4.3 to VRUCML1 4.3 with success (http://forum.xda-developers.com/showthread.php?t=2575661&page=153). Anyone tried that? I might actually try it myself to get root back. I don't this new "update". I think VZ did this more to take away root than add some really necessary Canadian roaming anyway.
Click to expand...
Click to collapse
Curious to see what your results are if you do try this. I also feel that VZW did this update more to take root away, especially considering that the base band could have been incorporated into the (hopefully) upcoming 4.4 update.
Yup, this annoyed me enough that I finally got an account!
this update was just to steal root. they had already tried using the my verizon app to take it. telus uses gsm and the same lte frequency verizon uses. all vzw note 2's could already "roam" on telus. this was just vzw being f**ktards trying to control us.
Has anyone been able to revert or re root their phone after this?
mwinschel said:
Has anyone been able to revert or re root their phone after this?
Click to expand...
Click to collapse
Other users are reporting that you can Odin back to MJ9 and then root with saferoot. See this thread for details... http://forum.xda-developers.com/showthread.php?p=52792973
Sent from my SCH-I605 using XDA Premium 4 mobile app
I was forced the vruand3 update at about 4 am while I was sleeping. I woke up to no root and some issues tied to the freedom app not being uninstalled. I flashed back to mj9 with odin. I rerooted with saferoot. I was still having the connection issues with everything google related. I took the ota update again to try to fix the issue. The google issue fixed itself after the ota, but my root wasn't taken away this time. So now I'm on build vruand3 and have full root access. Maybe someone can shed some light on this , or it will help someone