Related
Okay, so I've been reading for a couple days now, and I know the exact process that I want to take to Permaroot my MT4G and get S=Off, and I understand very clearly what those terms mean and why I want them.
Once I started looking into what to do beyond that, I got really, really confused.
If someone could refer me to somewhere so I can read more, I would really appreciate it.
For starters, I don't understand what flashing is. I also don't know what pushing files via the adb is. I don't know what the difference between a ROM and a kernel is.
^^^^All of those would be helpful
I guess I'm just confused about what to do now. Should I now set up the SDK on my PC and configure the ADB? Or should I flash Clockworkmod and do a nandroid backup? Neither?
Once I've done that, should I find a kernel, a ROM, or both? I know I want Gingerbread, I want OC capability, and I it stripped down (missing bloat), but I also want stability and for things like WiFi to work. On top of all of those questions I posted above, does anyone have any recommendation for a ROM/kernel like that?
Sorry about all the questions, and thanks.
corruptsmurf said:
Okay, so I've been reading for a couple days now, and I know the exact process that I want to take to Permaroot my MT4G and get S=Off, and I understand very clearly what those terms mean and why I want them.
Click to expand...
Click to collapse
Well that i a good start. Good to see some reading before the jump in feet first.
corruptsmurf said:
Once I started looking into what to do beyond that, I got really, really confused.
If someone could refer me to somewhere so I can read more, I would really appreciate it.
Click to expand...
Click to collapse
That's why we're here.
corruptsmurf said:
For starters, I don't understand what flashing is. I also don't know what pushing files via the adb is. I don't know what the difference between a ROM and a kernel is.
^^^^All of those would be helpful
Click to expand...
Click to collapse
Edited: added Later
ADB is a commander center/protocol (if you will) that allows you to control your phone via a PC/Mac/Linux. You can push files which would be taking the file and "pushing" to the phone. Or "pulling" files from the phone and putting them on the computer. It's simply as it states, pushing and pulling the files.
To see what a Kernel is read This.
A ROM is the phones physical Operating system. Similar to what Window, Mac or Linux world be.
corruptsmurf said:
I guess I'm just confused about what to do now. Should I now set up the SDK on my PC and configure the ADB? Or should I flash Clockworkmod and do a nandroid backup? Neither?
Click to expand...
Click to collapse
Before you can flash Clockwork Mod you need to root your phone and turn s=off. For one of the methods, - before you can start you need to set up the ADB (Android Debug Bridge). See my signature for the quickest and most painless way to get that set up. You will also need VISIONary.apk. A quick Google Search will find it for you. Link
corruptsmurf said:
Once I've done that, should I find a kernel, a ROM, or both? I know I want Gingerbread, I want OC capability, and I it stripped down (missing bloat), but I also want stability and for things like WiFi to work. On top of all of those questions I posted above, does anyone have any recommendation for a ROM/kernel like that?
Sorry about all the questions, and thanks.
Click to expand...
Click to collapse
If you want a 2.3 based ROM you will need to flash Recovery image 3.0.0.6, link can be found in my signature, and hit up the development section to read reviews on different ROMs. I personally like the plain AOSP look so that leave Cyanogen(mod). But i know TeamRoyal has put together some newer ROMs that i haven't tampered with yet.
I do everything on my phone through CWM (clockworkmod) or terminal emulator, so there's no need for a PC, unless to download the files and transfer them to my SDcard, as I don't understand adb. Anyways, I'm gonna explain this very short and sweet cuz I was once in your shoes, and remember how much I had to read to understand something That could've been explained so simply.
Think of it this way. You're building the software version of a car. Now, if the whole car is the ROM, then the engine is what would be the kernel. And flashing would then be another word for installing , Now, a toyota with a ferrari engine, would be a custom ROM. While a toyota with a ferrari engine and BMW insignias all over it would then be a custom themed ROM.
**Remember, you can never install a car on something, but you can always install something in a car**
Ex. You can never flash a ROM on a kernel, but you can always flash a kernel on a ROM.
Anyways, first off, you will need CWM recovery to flash. Get it from the market. In the app itself, flash (this is the "flash" in the app) recovery 3.0.0.6. This will flash (this flash is not in the app) anything; any ROM, any kernel, etc. as long as its a FLASHABLE ZIP.
To boot into the recovery (the place you do flashing), hold both volume down and power buttons down as you either turn on or restart your phone. The screen you see is the bootloader. Choose recovery using the volume buttons, and use the power button to select it.
Going to flash a new ROM? Do a factory reset (in recovery), wipe cache (in recovery), and wipe delvik cache (this is in advance in recovery). Then install zip. Its pretty straight forward from there.
Going to flash an updated ROM, skip factory reset (as this deletes all data on your phone) and do the rest.
After you've flashed the ROM, you can now flash the kernel.
Note that, kernels are ROM specific. Read what kinds of ROM's the kernel is for before you flash it.
There, easy as pie, yeah? Hope that helped.
I recommend cyanogenmod 7 (Gingerbread based ROM) with faux's kernel (Gingerbread based kernel)
Sent from my HTC Glacier using XDA App
corruptsmurf said:
Okay, so I've been reading for a couple days now, and I know the exact process that I want to take to Permaroot my MT4G and get S=Off, and I understand very clearly what those terms mean and why I want them.
Once I started looking into what to do beyond that, I got really, really confused.
If someone could refer me to somewhere so I can read more, I would really appreciate it.
For starters, I don't understand what flashing is. I also don't know what pushing files via the adb is. I don't know what the difference between a ROM and a kernel is.
^^^^All of those would be helpful
I guess I'm just confused about what to do now. Should I now set up the SDK on my PC and configure the ADB? Or should I flash Clockworkmod and do a nandroid backup? Neither?
Once I've done that, should I find a kernel, a ROM, or both? I know I want Gingerbread, I want OC capability, and I it stripped down (missing bloat), but I also want stability and for things like WiFi to work. On top of all of those questions I posted above, does anyone have any recommendation for a ROM/kernel like that?
Sorry about all the questions, and thanks.
Click to expand...
Click to collapse
Neidlinger's got your back.
1. Glad you're reading before doing. What a welcome change of pace!
2. Flashing is the process of installing new software. We "flash" it to the phone's memory.
3. ADB is using a computer to control the phone via command-prompt from DOS. Push is a command which sends a file from your computer to your phone. Do a search, there are lots of good guides on ADB. TrueBlueDrew made one just recently that I highly recommend.
Here's Drew's thread. Don't forget to hit his thanks button! - http://forum.xda-developers.com/showthread.php?t=928370
4. Start with Clockwork Recovery and a nandroid backup. That's good practice. CWR2 is compatible with Froyo (2.2) ROMs. CWR3 is compatible with Gingerbread (2.3) ROMs. CWR 3.0.0.6 is compatible with BOTH. Very convenient.
5. I say start with CM7. It's extremely stable, even though it's still in development. A ROM is a complete OS replacement for the phone. ROMs contain kernels, which control the most basic hardware, such as processor. If you flash a custom kernel on your stock ROM, you can overclock it more. You can also flash custom kernels on top of custom ROMs for different battery life, clock speed, etc.
To be honest I don't even bother with custom kernels since this phone is so damn fast out of the box I really don't see the point.
QUICK TIPS FOR CM7 - On your first boot, let it sit for 5-10 mins before setting up. There are background processes running and interrupting can harm stability. BEFORE you sign into google for the first time, after it's finished sitting, reboot. This will clear out any wifi glitches and give you smooth sailing.
Have fun!
BTW, I think most ROM's have a kernel already built in. People install custom kernels because they can have fixes for bugs, help with battery life, overclocked frequencies, no lags, etc. Otherwise, you can just flash the ROM, and if you're satisfied with the kernel its running on, then obviously you'll have no need to flash a custom kernel.
Sent from my HTC Glacier using XDA App
Uchennadi said:
BTW, I think most ROM's have a kernel already built in. People install custom kernels because they can have fixes for bugs, help with battery life, overclocked frequencies, no lags, etc. Otherwise, you can just flash the ROM, and if you're satisfied with the kernel its running on, then obviously you'll have no need to flash a custom kernel.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
This is pretty much spot on. The developers have included kernels that they feel make the OS preform at it's peak. and most of them will allow for overclocking. However on some of them you may need to use a program called "setCPU" to adjust the frequencies. Cyanogen(mod) will have this built into the ROM natively. However most of the veterans will not promote running your phone in an over clocked status 100% of the time. most of us leave the phone at 1Ghz or slower. There are physical reasons, ie the constant expansion and contract of the chip isn't good for the mother board.
If i were you i'd stick with the Stock Kernel and leave it running as it. That way the developer can adjust their ROM, if you use an 3rd party kernel they aren't familiar with the coding so it's not going to act correct.
I'm not putting down what the kernel coders do, they do an awesome job. but for a n3wb i'd leave well enough alone.
I have a stock note3 and since the Kitkat update, lost ability to record calls - nothing works, just static noise from all of them.
Also Gmail app and K9 failed. Aquamail works a treat tho'.
I'm sure there are other bits n bobs (sd access, battery life etc) that are flaky but I haven't fully tested the phone.
A call recorder is essential in my line of work so guess I need to 'fiddle' with my OS, never done it before.
So can anyone tell me what I need to do, i.e; rooting, flashing, decent custom ROM or at least a quick and pain-free mod...i don't do command line stuff and I 'm not a programmer, so anything in plain English would be helpful.
I don't mind keeping Kitkat looking as it is. I've seen my mate's customised rom note2 purchased from ebay and looks like its designed by a 14 yr old gaming nerd.- yuk.
I am very time poor so won't be able to spend hours and hours tinkering.
Thanks in advance
bornatheist said:
I have a stock note3 and since the Kitkat update, lost ability to record calls - nothing works, just static noise from all of them.
Also Gmail app and K9 failed. Aquamail works a treat tho'.
I'm sure there are other bits n bobs (sd access, battery life etc) that are flaky but I haven't fully tested the phone.
A call recorder is essential in my line of work so guess I need to 'fiddle' with my OS, never done it before.
So can anyone tell me what I need to do, i.e; rooting, flashing, decent custom ROM or at least a quick and pain-free mod...i don't do command line stuff and I 'm not a programmer, so anything in plain English would be helpful.
I don't mind keeping Kitkat looking as it is. I've seen my mate's customised rom note2 purchased from ebay and looks like its designed by a 14 yr old gaming nerd.- yuk.
I am very time poor so won't be able to spend hours and hours tinkering.
Thanks in advance
Click to expand...
Click to collapse
call record is fine if you use custom rom, most of them have a modded call recorder and work fine.
To be frank, when I was still on stock 4.4.2 unrooted, I can use gmail with no problem.
rooting => find cf-autoroot at android original development note 3.
recovery => there's twrp, philz cwm, and chenglu cwm. I use chenglu cwm. twrp & philz u can find at android original development note 3. whereby chenglu cwm you can find at android development note 3. I personally use chenglu cwm.
custom ROM => you can pick anything u want, and try. no harm trying. If you got not much time, I suggest you just pick 2 or 3 then download all of them first, copy to your sdcard, and try one by one. so, you will no need to wait again next time to download another one. I have 4 custom ROM that I like inside my sdcard. anytime I want to change I just flash them, no need to wait to download again (because each rom is quite huge around 1.5gb+).
To flash rooting, recovery and custom ROM, you have to bear in mind :
do back up your efs (I personally use dr. ketan efs backup after I root my device. this tool need device to be rooted). You can find at android themes & apps note 3
when you want to flash custom rom, remember to do nandroid backup from recovery (in case anything bad happened). Touch wood, so far I don't need to use this backup.
please do a check on the MD5 hash, to be matched with the one provided on the download thread. If not match means you have a bad download, try to download again till the MD5 is matched. Sometimes, due to file size very huge, and if your internet link down, it might cause a bad download. Don't blame on the OP/devs.
The most important before you continue all those process (rooting, recovery and custom rom), READ the thread and FOLLOW the instructions carefully. Most of the time if you follow carefully, nothing harm will happen. And... all the thread are in simple english, no coding words on the OP thread.
cheers.
bornatheist said:
I have a stock note3 and since the Kitkat update, lost ability to record calls - nothing works, just static noise from all of them.
Also Gmail app and K9 failed. Aquamail works a treat tho'.
I'm sure there are other bits n bobs (sd access, battery life etc) that are flaky but I haven't fully tested the phone.
A call recorder is essential in my line of work so guess I need to 'fiddle' with my OS, never done it before.
So can anyone tell me what I need to do, i.e; rooting, flashing, decent custom ROM or at least a quick and pain-free mod...i don't do command line stuff and I 'm not a programmer, so anything in plain English would be helpful.
I don't mind keeping Kitkat looking as it is. I've seen my mate's customised rom note2 purchased from ebay and looks like its designed by a 14 yr old gaming nerd.- yuk.
I am very time poor so won't be able to spend hours and hours tinkering.
Thanks in advance
Click to expand...
Click to collapse
to get call recording to work, use NC2 FW/rom and use NB2 modem or higher..
try clearing gmail`s data in settings, i have had zero issues with gmail..
for root/recorvery check the guide that is linked in my sig, it has step by step instructions..
as for rom i personally recommend xnote and lean kenrel to everyone..
For the exact same main reason (call recording) I've requested to the seller to solve the problem (my seller was also the carrier provider: orange).
They've changed my phone with a new one with latest 4.3, after a long conversation between orange and samsung tech support, only because my complaints about 4.4.2 implementation on note 3.
Maybe this thread is of use for you:
http://forum.xda-developers.com/showthread.php?t=2709623
Good luck,
So straight talk offers an s5, the sm-s902l, which has no roms and no clockwork mod recovery. Twrp works on it. I would love to have miui 7. I've tried to flash the official s5 version from miui site but during setup screen went black. I'm pretty sure this phone is the same as a g900v. But any roms I flash don't recognize the stock Sim and are overall wonky. No cellular data or network. Is there anyone who would be willing to develop/port anything at all for this phone? It is sold at Walmart so I'm sure there are many people with this phone who would love to upgrade from kitkat. Also, straight talk hasn't upgraded this phone past 4.4.2. Thanks for listening or advising
DDJR
Bump
Did you try to "port" some files?
When someone with G900M try to use a G900T's they need a "signalfix" with "RIL's files from his stock rom".
Try that. Using your stock files.
https://drive.google.com/file/d/0B7EuVd0yZ8EremZsT0ROOEZhWjA/view?pli=1
Sorry my poor english.
I haven't tried to port anything, I'm afraid that is well beyond my tech saviness. I've looked at a few articles on " how to", but understood none of it.
And your English is fine
Hi, i'm not an owner of the SM -902L nor even hear about it before i saw this thread. However i try to make things clear for u
At another thread i saw u ported bisspop, but sim is not working? Thats exactly what he is talking about, the RIL path.
1. Take a look at the "signalfix" zip file structure. (^ by @npzinho )
2. Rebuild the system folder structure(from signalfix) with your files from the official SM -902L Rom (Ignore the META-INF folder, just keep it as it is)
3. Create a zip system+META-INF=signalfix.zip
4. Flash your ported blisspop zip, afterwards the signalfix.zip
5. Boot and hope your Sim will get reconized
Good luck
Traace, thanks for the reply. But I didn't port blisspop, I just downloaded it. And all the other instructions , way over my head. I'll look at it but I know I won't be able to understand it.
***DISCLAIMER***
If done incorrectly, this can soft brick your device. I take no responsibility for this, and if you're unfamiliar with rooting android I suggest reading up before attempting. There are threads to fix your tablet if this goes sideways, but if this doesn't work I personally can't promise I can help you.
I used this method two days ago, and would like to thank jerbear294 for providing me with the information. I didn't come up with this, I just want to help others looking for root.
Hello guys
First, apologies if this is a redundant thread. All the root methods I've seen in individual topics seem outdated, and I just wanted to make this quick guide to help people from having to scan through pages of information to learn how to root these things. This method works on firmware WW_V12.10.1.33_20150917, which is the current release as of this post.
Lets get to it!
Download
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
(Navigate to page 1, for some reason it links to the last page)
Place it on your computer and unzip.
And the latest supersu .zip 2.46
https://download.chainfire.eu/696/supersu/
Which will be on your tablet.
Install the temp recovery to your computer, connect the tablet, make sure you enable adb (USB Debugging) on it in developer mode (Settings → about → software version → tap build number 7 times for developer mode). Once connected, run the exe in the .zip from the temp recovery.
Choose: TWRP HDPI portrait, T4.
Your device will boot into twrp recovery. Now navigate to the supersu.zip on your tablet, and install, and you should be good to go . Good luck, and happy rooting!
Thanks to everyone who developed these tools (especially Social_Design_Concepts), and XDA for providing a medium to relate them.
To run Xposed, go to http://forum.xda-developers.com/showthread.php?t=3034811
Choose 'xposed-v80-sdk21-x86', this is currently the only version I've had success with. Happy hunting folks!
404 page not found on the first link?
ThunderThighs said:
404 page not found on the first link?
Click to expand...
Click to collapse
Link fixed, thanks and my apologies
thank you a lot! you saved me a lot of browsing! :good:
I updated my me176cx directly from v17 to v33. No matter what I do, the rooting method you outline here doesn't work for me anymore. On v17 it worked first time, now it's a fail every time. No superuser app, no su binary. Any suggestions? I've reinstalled the v33 firmware (it was actually a nandroid backup posted by jerbear on androidfilehost).
Anyway, when I installed temp TWRP this time it asked me did I want to keep system read only - I answered no. Was that a mistake? Also, I went straight from v17 to v33, bypassing the v24 update completely. Was that the wrong thing to do?
Your help would be hugely appreciated, a life with an unrooted device is not one I care to contemplate.
seamo123 said:
I updated my me176cx directly from v17 to v33. No matter what I do, the rooting method you outline here doesn't work for me anymore. On v17 it worked first time, now it's a fail every time. No superuser app, no su binary. Any suggestions? I've reinstalled the v33 firmware (it was actually a nandroid backup posted by jerbear on androidfilehost).
Anyway, when I installed temp TWRP this time it asked me did I want to keep system read only - I answered no. Was that a mistake? Also, I went straight from v17 to v33, bypassing the v24 update completely. Was that the wrong thing to do?
Your help would be hugely appreciated, a life with an unrooted device is not one I care to contemplate.
Click to expand...
Click to collapse
I hear you. I'll be honest - I didn't so much Pioneer this method so much as succeed with it and then repost it to save people some time going through the threads on here :/
That said, I would ask jerbear if he has had this problem reported via his nandroid backup. Answering "no" in twrp was fine, if you said yes it would have been gimped and probably useless, so I doubt that's the problem. I would say it's the nandroid, but I've read people using it and nobody I remember mentioned a problem. In the meantime, try re downloading the backup and flashing it again, and then trying temp twrp and see if it works. I personally haven't tried jerbear's nandroid, so I can't speak on it's behalf
Sorry I don't have something more concrete, let me know what jerbear says and how things play out, and good luck
Opensystem said:
I hear you. I'll be honest - I didn't so much Pioneer this method so much as succeed with it and then repost it to save people some time going through the threads on here :/
That said, I would ask jerbear if he has had this problem reported via his nandroid backup. Answering "no" in twrp was fine, if you said yes it would have been gimped and probably useless, so I doubt that's the problem. I would say it's the nandroid, but I've read people using it and nobody I remember mentioned a problem. In the meantime, try re downloading the backup and flashing it again, and then trying temp twrp and see if it works. I personally haven't tried jerbear's nandroid, so I can't speak on it's behalf
Sorry I don't have something more concrete, let me know what jerbear says and how things play out, and good luck
Click to expand...
Click to collapse
Hey, thanks for the reply. Just to clarify, is this the file you downloaded and restored? https://www.androidfilehost.com/?fid=24052804347832070
Here's what I had to do: I had to create a folder (this folder I named with my device's serial no) as well as creating a folder inside that folder that I named after a nandroid backup that I'd done earlier. Then I placed all the files from the nandroid zip inside that (second) folder. Only then did the TWRP 'see' the backup. I did the usual system/cache/dalvik cache wipe and restored the nandroid without any hitch. You did that or something similar to get TWRP to restore the nandroid, right?
I wonder should I have taken the recovery log from my own nandroid and replaced jerbear's recovery log with it? I'm starting to confuse myself at this point I think..
seamo123 said:
Hey, thanks for the reply. Just to clarify, is this the file you downloaded and restored? https://www.androidfilehost.com/?fid=24052804347832070
Here's what I had to do: I had to unzip the file into a folder (this folder I named with my device's serial no) as well as creating a folder inside that folder that I named after a nandroid backup that I'd done earlier. Only then did the TWRP 'see' the backup. I did the usual system/cache/dalvik cache wipe and restored the nandroid without any hitch. You did that or something similar to get TWRP to restore the nandroid, right?
Click to expand...
Click to collapse
No sorry you misread: I never had to use that nandroid (or any on this tablet yet, all my updates .33 were in order and via ota) - I'm aware of it though and I've only heard good things so I'm not sure where the process might have broken down, outside maybe a corrupted download. That's why I recommended asking jerbear if he's heard of that problem from anyone, because it's a stock backup and I know tons of people have used it and supposedly rooted successfully using temp twrp. From what I can tell, you shouldn't have any problems...it sounds like you know what you're doing and did everything properly.
Can you revert to a previous version, and manually download .33 from https://www.asus.com/support/Download/28/6/0/23/3HzHuNmdcAgeMhJ1/32/ ? I assume there are no backups readily available, but the major xda thread on the 176 might have a couple older ones you can try.
I haven't done as much as a lot of pioneers with my tab, just update, root and install xposed. As such I can't really answer myself what the problem you're having is, just offer general advice I would try. Jerbear hopefully knows about what might be causing the root to fail
Opensystem said:
No sorry you misread: I never had to use that nandroid (or any on this tablet yet, all my updates .33 were in order and via ota) - I'm aware of it though and I've only heard good things so I'm not sure where the process might have broken down, outside maybe a corrupted download. That's why I recommended asking jerbear if he's heard of that problem from anyone, because it's a stock backup and I know tons of people have used it and supposedly rooted successfully using temp twrp. From what I can tell, you shouldn't have any problems...it sounds like you know what you're doing and did everything properly.
Can you revert to a previous version, and manually download .33 from https://www.asus.com/support/Download/28/6/0/23/3HzHuNmdcAgeMhJ1/32/ ? I assume there are no backups readily available, but the major xda thread on the 176 might have a couple older ones you can try.
I haven't done as much as a lot of pioneers with my tab, just update, root and install xposed. As such I can't really answer myself what the problem you're having is, just offer general advice I would try. Jerbear hopefully knows about what might be causing the root to fail
Click to expand...
Click to collapse
Hope I haven't misunderstood you here, but I'd tried installing the v33 from that thread when I was running v17 and didn't get anywhere with it - jerbear told me that restoring a v33 android backup was the only way to go. So even if I can revert back to v17 I'm kind of back to square one, really. I wonder if skipping the v24 update (which I couldn't flash anyway) is the reason behind my current woes though..
P.S. You got Xposed framework running on v33? I'm impressed, I couldn't even get it installed on v17, how did you do it?
Just chiming in to say this method worked for me and thanks a lot!
I was on firmware WW_V12.10.1.33_20150917, followed the instructions, and used root checker to confirm. Yep, rooted!
I did tap the keep read only button, more so on accident. Not sure what that does/did but I did find the restore defaults button. I don't know if that "fixed" anything or what but I didn't want to accidentally break something. Anyway, after that, I flashed SuperSU and was rooted.
Thanks again! :good:
seamo123 said:
Hope I haven't misunderstood you here, but I'd tried installing the v33 from that thread when I was running v17 and didn't get anywhere with it - jerbear told me that restoring a v33 android backup was the only way to go. So even if I can revert back to v17 I'm kind of back to square one, really. I wonder if skipping the v24 update (which I couldn't flash anyway) is the reason behind my current woes though..
P.S. You got Xposed framework running on v33? I'm impressed, I couldn't even get it installed on v17, how did you do it?
Click to expand...
Click to collapse
Yes the general for the memo 176 has a special working xposed, make sure you use that one. I'm a bit busy, but I'll link when I can glad you got it rooted
Joe_Bangles said:
Just chiming in to say this method worked for me and thanks a lot!
I was on firmware WW_V12.10.1.33_20150917, followed the instructions, and used root checker to confirm. Yep, rooted!
I did tap the keep read only button, more so on accident. Not sure what that does/did but I did find the restore defaults button. I don't know if that "fixed" anything or what but I didn't want to accidentally break something. Anyway, after that, I flashed SuperSU and was rooted.
Thanks again! :good:
Click to expand...
Click to collapse
Glad to help, xda is where it's at for community
OMG!!!!!!!! Finally!!! I'm so glad to read this post.... thank you!!! I've been searching a good method for months!
And yes, it works!!! xD
Delichi said:
OMG!!!!!!!! Finally!!! I'm so glad to read this post.... thank you!!! I've been searching a good method for months!
And yes, it works!!! xD
Click to expand...
Click to collapse
Hurray! Glad it worked out for you
seamo123 said:
Hope I haven't misunderstood you here, but I'd tried installing the v33 from that thread when I was running v17 and didn't get anywhere with it - jerbear told me that restoring a v33 android backup was the only way to go. So even if I can revert back to v17 I'm kind of back to square one, really. I wonder if skipping the v24 update (which I couldn't flash anyway) is the reason behind my current woes though..
P.S. You got Xposed framework running on v33? I'm impressed, I couldn't even get it installed on v17, how did you do it?
Click to expand...
Click to collapse
Hey sorry for the late response, work got crazy on me. I edited the original post to now include how to set up Xposed, for you or anyone else interested. Confirmed working on both .33 and .36
Hey guys!
Sorry for the off-topic but how is the new .36 firmware compared to .33? For me .33 sucked,all memory leaks , crashing apps, slow as hell,fortunately I got motherboard replacement and now I'm on KK again. Should I update to .36? What do you think?
dareas said:
Hey guys!
Sorry for the off-topic but how is the new .36 firmware compared to .33? For me .33 sucked,all memory leaks , crashing apps, slow as hell,fortunately I got motherboard replacement and now I'm on KK again. Should I update to .36? What do you think?
Click to expand...
Click to collapse
It's got less battery drain here, performance seems better too but that could just be a placebo
Opensystem said:
It's got less battery drain here, performance seems better too but that could just be a placebo
Click to expand...
Click to collapse
Thank you. Does upgrading to LP unlock 64 bit capability of the processor (Z3745)? I'd really appreciate it if you could answer me.
dareas said:
Thank you. Does upgrading to LP unlock 64 bit capability of the processor (Z3745)? I'd really appreciate it if you could answer me.
Click to expand...
Click to collapse
I'm not sure, we should be because of art runtime but I feel like our version is bootlegged to a degree
unable to mount /data, internal storage 0MB. How can I load the zip file?
It's probably because FDE. I used a external SD card instead
N00b w/ "new SGH-I337 that is running original kernel & 4.2.2 & needs to be updated
I am going to apologize from the start. I've read through a lot of threads here and have ended up more confused (and somewhat scared lol). I am a tad more skilled than average when it comes to PCs but I'm a complete mess when it comes to phones!
For various reasons, I like my old ATT Samsung S4 SGH-I337 but am hard on them and need to replace them about every 2 years (I usually wear out the power port among other things). I buy a replacement, copy over my apps, etc, maybe run a minor update and I'm good to go. This time, I bought a "new" open box S4 on Ebay for a great price but when I went to install all my apps, discovered that it was STILL (since it was "brand new") running Android 4.2.2 and the original kernel from the release in 2013! Ok, no big I thought, I will just run the ATT update and I will be good. Nope. Too far out of date and no one at ATT or Samsung is willing to help. I did learn that if I can get 4.4.4 on the phone, then I should be able to update it via ATT to 5.0.1 but I can't even find those files (or at the least any links to them that are still any good!)
Due to life issues, it is critical that I get this phone updated ASAP. Please, can someone spell out step by step in N00b-speak where I can get the needed files and how I update this phone to 5.0.1 or better? I'd really rather not root it if I can avoid it but will do what is needed. I'll buy you a beer (or reasonable beverage of your choice! )
Samsung Galaxy S4 (ATT) SGH_I337
Android 4.2.2
Baseband ver: I337UCUAMDL
Kernel ver: 3.4.0-453947
[email protected]#1
Sat April 27 17:06:05 KST 2013
SilkRoadDog said:
I am going to apologize from the start. I've read through a lot of threads here and have ended up more confused (and somewhat scared lol). I am a tad more skilled than average when it comes to PCs but I'm a complete mess when it comes to phones!
For various reasons, I like my old ATT Samsung S4 SGH-I337 but am hard on them and need to replace them about every 2 years (I usually wear out the power port among other things). I buy a replacement, copy over my apps, etc, maybe run a minor update and I'm good to go. This time, I bought a "new" open box S4 on Ebay for a great price but when I went to install all my apps, discovered that it was STILL (since it was "brand new") running Android 4.2.2 and the original kernel from the release in 2013! Ok, no big I thought, I will just run the ATT update and I will be good. Nope. Too far out of date and no one at ATT or Samsung is willing to help. I did learn that if I can get 4.4.4 on the phone, then I should be able to update it via ATT to 5.0.1 but I can't even find those files (or at the least any links to them that are still any good!)
Due to life issues, it is critical that I get this phone updated ASAP. Please, can someone spell out step by step in N00b-speak where I can get the needed files and how I update this phone to 5.0.1 or better? I'd really rather not root it if I can avoid it but will do what is needed. I'll buy you a beer (or reasonable beverage of your choice! )
Samsung Galaxy S4 (ATT) SGH_I337
Android 4.2.2
Baseband ver: I337UCUAMDL
Kernel ver: 3.4.0-453947
[email protected]#1
Sat April 27 17:06:05 KST 2013
Click to expand...
Click to collapse
I too was lucky enough to snag a S4 off ebay with the original kernel still on it. So with that said....do NOT update your phone! You're on the very special Android 4.2.2 jelly bean MDL bootloader! If you update, you will lose the ability to boot AOSP ROMs and install a custom recovery like TWRP.
AOSP ROMs can take you past Android 5.0.x lollipop and give you Android 6.0.x marshmallow or 7.0.x nougat. You can also boot custom touchwiz ROMs that will take you to Android 5.0.x lollipop. Use the towel root app to root the phone and then freeze any OTA with the titanium backup app. You can also benefit from my guide here:
https://forum.xda-developers.com/galaxy-s4-att/general/how-to-one-guide-to-mdl-bootloader-t3584122
StoneyJSG said:
I too was lucky enough to snag a S4 off ebay with the original kernel still on it. So with that said....do NOT update your phone! You're on the very special Android 4.2.2 jelly bean MDL bootloader! If you update, you will lose the ability to boot AOSP ROMs and install a custom recovery like TWRP.
AOSP ROMs can take you past Android 5.0.x lollipop and give you Android 6.0.x marshmallow or 7.0.x nougat. You can also boot custom touchwiz ROMs that will take you to Android 5.0.x lollipop. Use the towel root app to root the phone and then freeze any OTA with the titanium backup app. You can also benefit from my guide here:
https://forum.xda-developers.com/galaxy-s4-att/general/how-to-one-guide-to-mdl-bootloader-t3584122
Click to expand...
Click to collapse
Thank you for your reply. So I root it, then where do I go from there? How do I know what ROM is what and which one will give me at the least what I had on the old phone (less bloatware would be nice but right now I am so up a creek that I would be ok with stock)? Also, do you have good links to the tools you recommend? One issue I have been having searching here is that the 3-4-year-old posts here have sketchy or dead links.
SilkRoadDog said:
Thank you for your reply. So I root it, then where do I go from there? How do I know what ROM is what and which one will give me at the least what I had on the old phone (less bloatware would be nice but right now I am so up a creek that I would be ok with stock)? Also, do you have good links to the tools you recommend? One issue I have been having searching here is that the 3-4-year-old posts here have sketchy or dead links.
Click to expand...
Click to collapse
No problem, I always try to help when possible. After rooting you can follow my guide to get Loki doki installed. Then you can install a custom recovery like TWRP or clock work mod. My guide gets you clock work mod recovery installed but it's an old version. I use it though and it works fine for me. If you want TWRP recovery, you will have to search the web on how to install it with loki doki.
After a custom recovery is installed you can choose to boot touchwiz based ROMs or AOSP based ROMs like cyanogen mod. Custom touchwiz ROMs will look just like stock only modified (deodex, debloated, etc.) and AOSP ROMs will look like bone stock Android only with added features.
You can find AOSP ROMs in the original Android development forum here in the s4 forums. You can find touchwiz ROMs in Android development which is right under original Android development forum. Sorry, but I don't have any links to tools handy except for the link to my guide which I posted above in my last post. I use golden eye ROM on my s4 which is a stock based touchwiz ROM on Android 5.0 lollipop.
When booting ROMs, be sure that they do not have a bootloader update or else it'll override everything and will patch the loki doki exploit and lock down everything for good.
StoneyJSG said:
No problem, I always try to help when possible. After rooting you can follow my guide to get Loki doki installed. Then you can install a custom recovery like TWRP or clock work mod. My guide gets you clock work mod recovery installed but it's an old version. I use it though and it works fine for me. If you want TWRP recovery, you will have to search the web on how to install it with loki doki.
After a custom recovery is installed you can choose to boot touchwiz based ROMs or AOSP based ROMs like cyanogen mod. Custom touchwiz ROMs will look just like stock only modified (deodex, debloated, etc.) and AOSP ROMs will look like bone stock Android only with added features.
You can find AOSP ROMs in the original Android development forum here in the s4 forums. You can find touchwiz ROMs in Android development which is right under original Android development forum. Sorry, but I don't have any links to tools handy except for the link to my guide which I posted above in my last post. I use golden eye ROM on my s4 which is a stock based touchwiz ROM on Android 5.0 lollipop.
When booting ROMs, be sure that they do not have a bootloader update or else it'll override everything and will patch the loki doki exploit and lock down everything for good.
Click to expand...
Click to collapse
Thank you so much for the reply. While I am very grateful, with all due respect, I understood only about half of it. Here is the deal. I'm an older guy N00b with chronic pain issues under an extreme amount of stress, and my cognitive abilities are not what they should be. There was a step by step guide posted back in 2015 that is what I need but most of the links are bad or sketchy. Like I said above, I really need something along the lines of "go here and here to get this software and put it in "X" place. Then press these keys and do "Y", then press those keys and do "Z". I'm really sorry to be so difficult but I am trying my best to get it.
SilkRoadDog said:
Thank you so much for the reply. While I am very grateful, with all due respect, I understood only about half of it. Here is the deal. I'm an older guy N00b with chronic pain issues under an extreme amount of stress, and my cognitive abilities are not what they should be. There was a step by step guide posted back in 2015 that is what I need but most of the links are bad or sketchy. Like I said above, I really need something along the lines of "go here and here to get this software and put it in "X" place. Then press these keys and do "Y", then press those keys and do "Z". I'm really sorry to be so difficult but I am trying my best to get it.
Click to expand...
Click to collapse
I gotcha, no problem. Okay so what's the status of your phone now? Rooted? Not rooted? To root, goto https://towelroot.com on your phone and click the big red thing in the middle of the page. Make sure you have a Wi-Fi or data connection to the internet, as this will root your phone. Then goto https://galaxys4root.com/galaxy-s4-...tt-or-verizon-galaxy-s4-sgh-i337sch-i545/amp/ to get loki doki installed and clockwork mod recovery. You can also install TWRP recovery instead of clockwork mod recovery, I THINK this is the link: https://galaxys4root.com/galaxy-s4-...rp-on-rooted-galaxy-s4-using-goo-manager/amp/
Galaxys4root.com is a reputable site ran by Mr. HIGH ON ANDROID himself, Xedomax aka Max Lee. The tools you need should be on his site for download and the links shouldn't be dead. He also has a YouTube channel with videos on how to do different things with your phone. My guide I wrote that I linked before, has step by step instructions on how to root and install a custom recovery and how to boot custom ROMs.
StoneyJSG said:
I gotcha, no problem. Okay so what's the status of your phone now? Rooted? Not rooted? To root, goto https://towelroot.com on your phone and click the big red thing in the middle of the page. Make sure you have a Wi-Fi or data connection to the internet, as this will root your phone. Then goto https://galaxys4root.com/galaxy-s4-...tt-or-verizon-galaxy-s4-sgh-i337sch-i545/amp/ to get loki doki installed and clockwork mod recovery. You can also install TWRP recovery instead of clockwork mod recovery, I THINK this is the link: https://galaxys4root.com/galaxy-s4-...rp-on-rooted-galaxy-s4-using-goo-manager/amp/
Galaxys4root.com is a reputable site ran by Mr. HIGH ON ANDROID himself, Xedomax aka Max Lee. The tools you need should be on his site for download and the links shouldn't be dead. He also has a YouTube channel with videos on how to do different things with your phone. My guide I wrote that I linked before, has step by step instructions on how to root and install a custom recovery and how to boot custom ROMs.
Click to expand...
Click to collapse
Ok, It's not rooted yet so I will start down the path laid out. What do you recommend as a source for Touchwiz (wth is that anyway? lol) ROMs? I don't know enough about Android 6.0.x marshmallow or 7.0.x nougat to make the call there but I do want to be able to access the Google apps and play store as before.
SilkRoadDog said:
Ok, It's not rooted yet so I will start down the path laid out. What do you recommend as a source for Touchwiz (wth is that anyway? lol) ROMs? I don't know enough about Android 6.0.x marshmallow or 7.0.x nougat to make the call there but I do want to be able to access the Google apps and play store as before.
Click to expand...
Click to collapse
Your instructions say " Next, you're going to want to freeze the OTA update so the phone won't update off the MDL bootloader (after installing SuperSU of course). You can do this via the Titanium Backup app or the MyBackup Root app (now called just MyBackup I think).
Let's recap...you will need a copy of the towel root app, then SuperSU, then TB or MyBackup Root app. SuperSU will kill the evil KNOX for you." Do I do that before "loki doki installed and clockwork mod recovery."? If so, where is a good source for them? If not, when do I do I install them?
".
StoneyJSG said:
I gotcha, no problem. Okay so what's the status of your phone now? Rooted? Not rooted? To root, goto https://towelroot.com on your phone and click the big red thing in the middle of the page. Make sure you have a Wi-Fi or data connection to the internet, as this will root your phone. Then goto https://galaxys4root.com/galaxy-s4-...tt-or-verizon-galaxy-s4-sgh-i337sch-i545/amp/ to get loki doki installed and clockwork mod recovery. You can also install TWRP recovery instead of clockwork mod recovery, I THINK this is the link: https://galaxys4root.com/galaxy-s4-...rp-on-rooted-galaxy-s4-using-goo-manager/amp/
Galaxys4root.com is a reputable site ran by Mr. HIGH ON ANDROID himself, Xedomax aka Max Lee. The tools you need should be on his site for download and the links shouldn't be dead. He also has a YouTube channel with videos on how to do different things with your phone. My guide I wrote that I linked before, has step by step instructions on how to root and install a custom recovery and how to boot custom ROMs.
Click to expand...
Click to collapse
Ok, forget anything I typed here in the last hour lol. Somehow there were two locals and I was in the wrong one. So far so good. So back to the other question above. " " Next, you're going to want to freeze the OTA update so the phone won't update off the MDL bootloader (after installing SuperSU of course). You can do this via the Titanium Backup app or the MyBackup Root app (now called just MyBackup I think).
Let's recap...you will need a copy of the towel root app, then SuperSU, then TB or MyBackup Root app. SuperSU will kill the evil KNOX for you."" I still need to do that, right? if so, where do I find those apps?
Thank you so much.
SilkRoadDog said:
Ok, It's not rooted yet so I will start down the path laid out. What do you recommend as a source for Touchwiz (wth is that anyway? lol) ROMs? I don't know enough about Android 6.0.x marshmallow or 7.0.x nougat to make the call there but I do want to be able to access the Google apps and play store as before.
Click to expand...
Click to collapse
Touchwiz is the "skin" user interface that Samsung puts on top of Android. It is the stock SAMSUNG rom. Just Google touchwiz then Google stock Android, you'll see a difference. I like touchwiz so I am running a custom ROM called "Golden eye". You can download it from the Android development forum here in the S4 section. Other people like stock Android. The magic of being on the MDL bootloader is that you can boot touchwiz and bone stock Android ROMs. Most custom ROMs both stock Android and touchwiz based will let you access Google apps and the play store.
---------- Post added at 10:36 PM ---------- Previous post was at 10:21 PM ----------
SilkRoadDog said:
Ok, forget anything I typed here in the last hour lol. Somehow there were two locals and I was in the wrong one. So far so good. So back to the other question above. " " Next, you're going to want to freeze the OTA update so the phone won't update off the MDL bootloader (after installing SuperSU of course). You can do this via the Titanium Backup app or the MyBackup Root app (now called just MyBackup I think).
Let's recap...you will need a copy of the towel root app, then SuperSU, then TB or MyBackup Root app. SuperSU will kill the evil KNOX for you."" I still need to do that, right? if so, where do I find those apps?
Thank you so much.
Click to expand...
Click to collapse
You can get all those app except towel root on the play store. Once installed you can use ES file explorer to back them up to apk files then use the my files app that's on ya phone to move them to your SD card for use with your new ROM or keep them where they are since my guide tells you how to keep your data in tact...well for touch wiz ROMs anyway.
StoneyJSG said:
Touchwiz is the "skin" user interface that Samsung puts on top of Android. It is the stock SAMSUNG rom. Just Google touchwiz then Google stock Android, you'll see a difference. I like touchwiz so I am running a custom ROM called "Golden eye". You can download it from the Android development forum here in the S4 section. Other people like stock Android. The magic of being on the MDL bootloader is that you can boot touchwiz and bone stock Android ROMs. Most custom ROMs both stock Android and touchwiz based will let you access Google apps and the play store.
---------- Post added at 10:36 PM ---------- Previous post was at 10:21 PM ----------
You can get all those app except towel root on the play store. Once installed you can use ES file explorer to back them up to apk files then use the my files app that's on ya phone to move them to your SD card for use with your new ROM or keep them where they are since my guide tells you how to keep your data in tact...well for touch wiz ROMs anyway.
Click to expand...
Click to collapse
Since this is a "new" phone and I have nothing to back up yet, do I need to run a backup or can I follow your guide from that point, clean things up and install the ROM of choice?
SilkRoadDog said:
Since this is a "new" phone and I have nothing to back up yet, do I need to run a backup or can I follow your guide from that point, clean things up and install the ROM of choice?
Click to expand...
Click to collapse
It's always good to make a backup in case anything goes wrong with your phone down the road you can get back to where you started without having to flash the MDL stock Rom in ODIN by connecting your phone to your computer. You should though keep a copy of ODIN and the MDL bootloader .tar ODIN file. However, it's entirely optional to make a back up so you could just follow the guide from that point and clean up for a ROM install if you don't want to make a backup.
You can also boot a ROM and then make a backup after you have everything set up. You can back up the stock Rom or any ROM you boot/install. That's the magic of having a custom recovery like TWRP or clock work mod.
StoneyJSG said:
It's always good to make a backup in case anything goes wrong with your phone down the road you can get back to where you started without having to flash the MDL stock Rom in ODIN by connecting your phone to your computer. You should though keep a copy of ODIN and the MDL bootloader .tar ODIN file. However, it's entirely optional to make a back up so you could just follow the guide from that point and clean up for a ROM install if you don't want to make a backup.
You can also boot a ROM and then make a backup after you have everything set up. You can back up the stock Rom or any ROM you boot/install. That's the magic of having a custom recovery like TWRP or clock work mod.
Click to expand...
Click to collapse
Unfortunately, since I already started the install before seeing this, I have no idea what I backed up or where it is. :crying:
First off, I want to thank you so much for the help. I owe you and would like to buy you a beer or the like. I have my phone back now! There were issues with the Golden Eye install (it froze at the Samsung logo for over an hour) and I had to wipe everything and start over then I was able to get it up and running. Is this the right one? https://forum.xda-developers.com/showthread.php?t=2313469
Quick question: Do you know if that ROM supports an external SD card larger than 32gig?
I am having some issues and so far am not thrilled with this ROM and am wondering if it's the right one or if I screwed up. It hasn't been worked on since 2015 and the dev is hasn't been responsive in years. On my phone, it's really buggy. It boots slow, apps hang when loading, a few don't work right, the screen can flash or freeze and TouchWiz keeps crashing like it was doing at the end on my old phone's life. Any ideas as to why?
SilkRoadDog said:
Unfortunately, since I already started the install before seeing this, I have no idea what I backed up or where it is. :crying:
First off, I want to thank you so much for the help. I owe you and would like to buy you a beer or the like. I have my phone back now! There were issues with the Golden Eye install (it froze at the Samsung logo for over an hour) and I had to wipe everything and start over then I was able to get it up and running. Is this the right one? https://forum.xda-developers.com/showthread.php?t=2313469
Quick question: Do you know if that ROM supports an external SD card larger than 32gig?
I am having some issues and so far am not thrilled with this ROM and am wondering if it's the right one or if I screwed up. It hasn't been worked on since 2015 and the dev is hasn't been responsive in years. On my phone, it's really buggy. It boots slow, apps hang when loading, a few don't work right, the screen can flash or freeze and TouchWiz keeps crashing like it was doing at the end on my old phone's life. Any ideas as to why?
Click to expand...
Click to collapse
If you made a nandroid backup with TWRP recovery or clockwork mod recovery, then the backup file will be on your phone SD card or internal memory. Use the my files app to find it. It should be under a folder called TWRP or clockwork mod.
Hey no problem man, I know how it is to goto a forum and have 87,000 people view your post yet nothing is said. Yes that link is the correct link to golden eye ROM. When booting a ROM for the first time it will get stuck at the Samsung logo for awhile, this is normal but it shouldn't be more than 20 minutes. I think the S4 can handle SD cards up to 128GB, it might only be 64GB though.
Very odd golden eye ROM is giving you issues, I have only had one problem with it and that was the text message app acting up every so often. When you booted golden eye did you use the Aroma installer so it just asks you questions and you pick what you want? If not wipe and start over using aroma, it's built into the ROM. Also be sure to tell Aroma you want to use the "imperium kernel". That's the kernel I am using. Golden eye ROM doesn't have a bootloader update in it, so you'll stay on MDL and not have to worry about your phone patching the loki exploit.
I think you can also use the hybrid max kernel, but I don't think it's in the Aroma installer so if you want it you will have to download it from the forums here and flash it separately.
Another thing you can try is just "nuking your phone" as explained in my guide that wipes everything and gives you a nice clean install. The only reason I included the "keep your data" method in my guide is because I just stumbled upon it by doing it on my phone.
If all else fails and as a last ditch effort, you could send the phone to me and I will see if I can get it up and running with golden eye ROM, then send it back. No guarantees though as I'm no developer or anything, just a guy that knows the basics of Android ROMs and root.
Final report. It turns out the problems I've been having were related to the SU Super App. There have been complaints about the recent version. I thought that it was a corrupt install of Golden Eye so got a clean DL from another mirror and was getting ready to start all over. This time I was going to follow the dev's install instructions step by step instead of yours and his. However, I couldn't install TWRP as he instructed. It hung at 100% and never completed. I thought that maybe Super SU was the issue there so I uninstalled it and all of my other problems went away! So happy. Thank you for everything. I do owe you a drink!
SilkRoadDog said:
Final report. It turns out the problems I've been having were related to the SU Super App. There have been complaints about the recent version. I thought that it was a corrupt install of Golden Eye so got a clean DL from another mirror and was getting ready to start all over. This time I was going to follow the dev's install instructions step by step instead of yours and his. However, I couldn't install TWRP as he instructed. It hung at 100% and never completed. I thought that maybe Super SU was the issue there so I uninstalled it and all of my other problems went away! So happy. Thank you for everything. I do owe you a drink!
Click to expand...
Click to collapse
Hey glad it finally worked out for you. You will need superSU though, try a different version of it and that might fix the issue you're having with the latest version. That is unless you have the kingroot super user app, then you can use that but it's not as good as superSU. I had problems with it authorizing my root apps so I got rid of it and installed superSU. No problem glad to help and no thanks needed but if you really wanna buy me a beer go for it lol.