Related
Hi all-so I decided to flash back to stock since my 32GB Nexus was down to about 14GB from flashing ROMS and such.Everything seems to have gone smoothly however when I try the oem unlock command I am told that the device is already unlocked.I proceeded to root and then I tried to flash TWRP but I get permission denied.
Also,my Play Store just crashed when I try and type in an app to search for.
The question is-how do I know which factory image is right for my device?
There are a number of 5.1.1 images,I selected the one marked for all carriers except T-Mobile.Could I have selected the wrong image to be causing some of these problems?
Or should I just go ahead and jump up to 6.0.1-there is only 1 image for that release.
I would't think the image mattered that much but something is wrong here.
I got the phone last week from the Amazon sale and I activated it no problem on Verizon and flashed several ROMS no issue.
Advice is much appreciated.
I really don't understand why anyone would flash to an old version of a ROM. I appreciate that people have different tastes (e.g. don't like material design) or perceive different characteristics (e.g. better battery life) but in general each new ROM brings advantages, stability, security, improvements, so why stick with an old one when you can have new?
Me, I'd definitely go for a full clean install of MMB29K.
And if you insist on root, be aware of the issues with Marshmallow - you need a different kernel (Elementalx is popular) or alternatively flash TWRP and install Chainfire's SuperSU 2.62. I say 2.62 rather than 2.65 because there are numbers of people reporting that root doesn't work with 2.65, which isn't the case with 2.62, and from personal experience 2.62 works absolutely fine on my 6.0.1 N6.
dahawthorne said:
I really don't understand why anyone would flash to an old version of a ROM. I appreciate that people have different tastes (e.g. don't like material design) or perceive different characteristics (e.g. better battery life) but in general each new ROM brings advantages, stability, security, improvements, so why stick with an old one when you can have new?
Me, I'd definitely go for a full clean install of MMB29K.
And if you insist on root, be aware of the issues with Marshmallow - you need a different kernel (Elementalx is popular) or alternatively flash TWRP and install Chainfire's SuperSU 2.62. I say 2.62 rather than 2.65 because there are numbers of people reporting that root doesn't work with 2.65, which isn't the case with 2.62, and from personal experience 2.62 works absolutely fine on my 6.0.1 N6.
Click to expand...
Click to collapse
Thanks for the detailed response. I was running 5.1 initially because that is what the phone booted with and I like full-featured ROMS like BlissPop. I guess I'll give 6.0.1 a whirl.It just seemed like it was too new to be rock solid. I had as many features on my old S3 running 4.4.2 as I have seen since then if not more actually. I am curious about Google Now On Tap however.
Hopefully this gets me fixed up.Cheers.
chiadrum said:
Hi all-so I decided to flash back to stock since my 32GB Nexus was down to about .......
Click to expand...
Click to collapse
It is possible that the issue is caused because you downgraded the bootloader by flashing 5.1.1.
Flash the complete latest stock 6.0.1 images.
Flashing 6.0.1 now. Both times the CMD window has showed me archive does not contain boot.sig and recovery.sig. I am guessing that is normal?
The 5.1.1 started working fine after an update all but I still couldn't install TWRP fyi.
Let's see how Marshmallow tastes!
The "does not contain boot.sig and recovery.sig" is standard. I have no idea why it continues to appear version after version, but it has no effect on the installation.
chiadrum said:
Flashing 6.0.1 now. Both times the CMD window has showed me archive does not contain boot.sig and recovery.sig.
Click to expand...
Click to collapse
Same on my N6 when flashing 6.0.1. When 6.0.1 is running, you can flash TWRP recovery in fastboot mode.
NLBeev said:
Same on my N6 when flashing 6.0.1. When 6.0.1 is running, you can flash TWRP recovery in fastboot mode.
Click to expand...
Click to collapse
Thanks guys.
chiadrum said:
Thanks guys.
Click to expand...
Click to collapse
Ok more strangeness.pPhone is working fine,no issues.However I am unable to unlock bootloader using the fastboot OEM unlock command.
The message is "Not supported command in current status".
Yes,OEM unlock is allowed in Dev Options.I tried turning that off in case the indicator was faulty and then I couldn't even attempt to unlock,immediate failure.
Tried this several times after reboots as well.
Build MMB29K.
Any ideas?
Would it be too simple an answer to say that it's because the phone is already unlocked? You couldn't install a new ROM with a locked bootloader.
I myself have been a bit surprised by the peremptory & derogatory comments of some of the very senior members in these forums when people ask what seem to be questions with obvious answers, and I'm beginning to see their point...
Still, I also recognise that an "easy" question is one that you know the answer to, and I don't want to put people off asking questions. Being knocked back myself several times hasn't stopped me asking.
That's actually a very good point.Perhaps the image came boitloader unlocked.I'll see if I can flash TWRP and install something. I haven't loaded any roms since the initial flash,I was following protocol to unlock,root and then flash.Appreciate the help.Sometimes obvious seems too easy.
chiadrum said:
That's actually a very good point.Perhaps the image came boitloader unlocked.I'll see if I can flash TWRP and install something. I haven't loaded any roms since the initial flash,I was following protocol to unlock,root and then flash.Appreciate the help.Sometimes obvious seems too easy.
Click to expand...
Click to collapse
Confirmed I am an idiot.Device is unlocked already. Wasn't expecting that.The people way smarter than me who prepared that image took care of it for me.
Not an idiot at all. Like I said, an easy question is one that you know the answer to. Experience counts...
It's not the image that is unlocked - it's the device. Once unlocked, you have to specifically lock it again, but it's neither simple nor a good idea. An unlocked device gives you a far better chance to recover from errors.
This will be for the SM-G935D/SC-02H Japanese variant of the s7 edge.
Stock ODIN firmware: https://www.androidfilehost.com/?fid=457095661767130814 (Marshmallow)
TWRP 3.0.3-0: https://www.androidfilehost.com/?fid=817550096634747128
Rooted Rom: https://www.androidfilehost.com/?fid=385035244224413763
HKernel for hero2qltedcm:https://www.androidfilehost.com/?fid=745425885120706416
Kernel includes:
CVE updated
Permissive
F2FS support
Ramdisk changes the same as hero2qltechn variant. (All changes are the same)
Kernel Change-log:
https://github.com/travismills82/android_kernel_samsung_msm8996/commits/tw-6.0
TWRP Unofficial:
F2FS Support
More partitions supported for backup and restore compared to official version
How to root this device: https://forum.xda-developers.com/s7-edge/how-to/guide-sm-g9350-s7-edge-qualcomm-sd820-t3410969
Reserved
travis82 said:
This will be for the Japanese variant of the s7 edge this is an unlocked model also.
Stock ODIN firmware: https://www.androidfilehost.com/?fid=457095661767130814 (SC02HOMU1APL2)
TWRP: Coming soon
Debloated Rom: Coming soon
Kernel: Coming soon
Click to expand...
Click to collapse
Can this be used for sm g9350 hongkong?
Sent from my SM-G9350 using Tapatalk
Please use common sense and read ITS FOR THE JAPANESE VARIANT.. READ THE MODEL #. Good gosh stop posting stupid questions dude.
Thanks I'll try this when I get to work.
I can't seem to unlock my bootloader, I'm unable to flash TWRP and enter the recovery. It just says Recovery mode -> Warranty bit set: Recovery and enters into a normal boot after trying it a few times.
Edit:
used the official TWRP and recovery now works. Now trying to install the rom
Edit2:
When trying to install it keeps giving me the following error:
This package is for "SC-02h,hero2qledcm" devices; this is a "hero2qltedcm"
Update process ended with ERROR: 7
Error installing zip file '/sdcard/TWRP/SC-02H_Debloated.zip'
Edit3:
I edited the update-script and removed the assert.
However I don't notice any changes in the rom itself. It still has some bloatware (docomo stuff)
ahh ok i thought it would use sco2h not dcm I can fix that sorry, and I assume twrp is doing the same. I will use a dcm kernel in twrp, let me know if that kernel boots please I dont have the device in hand so I am relying on you all to let me know.
USE crom.apk to unlock bootloader you should find it in galaxy apps store. I'm pretty sure others have unlocked their bootloader doing the same thing. I also used to have someone install my hkroms and kernels on the jap variant so I know you can unlock the bootloader.
CROM: https://www.androidfilehost.com/?fid=385035244224394932
can you unlock the bootloader with that, its a link to what we used to unlock ours.
I need you to unlock your bootloader first please. Sounds like that is the issue.
If I run that app it just exits with Crom Service has stopped working.
Your rom works fine, it has root which is what I needed the most.
Just wish there was a way to remove the sim lock from the device without having to beg Docomo.
I bet I have my asserts all messed up here man I'm sorry. I see SC-02H than hero2qltedcm, than SM-G935D soo I need to get this in the correct order. Would you mind shooting me a pm so I can hangouts you so we can knocks this out quickly?
updated op with twrp recovery and kernel.
This works, root and most of the bloated software is gone
Off topic question (need some insight)
You have started to make a working TWRP for the Docomo variant - thank you for your work (hopefully people in JP using the Docomo version find success).
I know this is off topic but I thought you could provide me with a better understanding.
I am currently using the au KDDI variant (SCV33-Snapdragon) and have successfully installed TWRP (3.0.2-0) with ability to mount /data following xda, youtube, and a Vietnamese forum using google translate; BUT I am unable to keep TWRP ability to mount /data after flashing re-engineered boot file via odin to apply root (Snapdragon Variant Root). TWRP can still be used to go into recovery, mount /ext sdcard, and reboot. I've tried many different styles of rooting after and before installing TWRP, in addition to flashing in different ways - but I still failed. It's either have full working TWRP that can mount /data but without root; or, have root but TWRP that can't mount /data (basically useless as it cannot install anything nor, make backups).
I apologize for such long response, any insight or somewhere you can point me to where I can do more research, as this is how far I have come so far, but still fail to acquire both (Yes I have watched numerous YT vids and read countless post stating devs have not yet found a way on the US-Snapdragon variants, which I understand this may apply to the JP variant too) . Thank you.
With the development of ROMs for the Exynos variants (SG935F/FD) moving along apace... I'm wondering if it is feasible to use one of those ROMs with this kernel.
I did something similar to get a custom ROM made for an AT&T S4 onto my DoCoMo S4 (SC-04E) without issues.
Is that a stupid question?
SCV33 looks exactly the same as SC-02H. What's the difference? single sim dual sim? Can you use sc-02h roms for it? I need more information unless you guys want to start donating me devices.
bu06034 said:
With the development of ROMs for the Exynos variants (SG935F/FD) moving along apace... I'm wondering if it is feasible to use one of those ROMs with this kernel.
I did something similar to get a custom ROM made for an AT&T S4 onto my DoCoMo S4 (SC-04E) without issues.
Is that a stupid question?
Click to expand...
Click to collapse
You guys should never flash an engineering kernel anymore. There is no need since you have a custom kernel and ramdisk and twrp now since I made them. Also those are exynos not qualcomm you can port it but it will be a major task to do.
travis82 said:
You guys should never flash an engineering kernel anymore. There is no need since you have a custom kernel and ramdisk and twrp now since I made them. Also those are exynos not qualcomm you can port it but it will be a major task to do.
Click to expand...
Click to collapse
First, I really apprecate the work you have put in on bringing ROOT and TWRP to users in Japan. If I can help by doing some testing for you with my DoCoMo model, I'd be happy to do so!
Regarding my original question, I was not talking about an engineering kernel. I was thinking that if I flashed a custom ROM for the SG-935F Hong Kong (Exynos) model, and then flashed your kernel over it, would it work?
As I understand it, the kernel is the interface between the OS and the hardware. Maybe that is ignorant? The reason I ask is because this process was quite common for Japanese S4 users to employ custom ROMs for US S4s; i.e. Flash the US custom ROM (e.g. Mokee or Albee95) and then flash the Japanese S4 kernel onto it.
I understand the question might seem silly to you, but I don't have the hundreds of hours required to reach your level of expertise. I have invested sufficient time to understand much of the jargon; and the tools and methods employed to get root and flash ROMs. More than that, I rely on asking the experts, like you. :good:
you would have to port firmware framework and a bit of other things, secondly hong kong does not self exynos versions here. It's all Qualcomm.
SCV33 waiting for someone to flash this kernel on it to let me know if its compatible or not.
Anyways updated main thread with BETA 2.
Enjoy,
Travis82
SCV33 test 1
travis82 said:
SCV33 waiting for someone to flash this kernel on it to let me know if its compatible or not.
Anyways updated main thread with BETA 2.
Enjoy,
Travis82
Click to expand...
Click to collapse
Travis,
TESTED (Semi-working)
I've done some testing on my SCV33 variant using what you've made for the SC-02H.
[Kernel]
I flashed the HKernal Beta 2, using the SC-02H FW, and TWRP Unofficial you've provided onto my SCV33 Galaxy S7e and it is really snappy and fast. Very nice kernel. Any DoCoMo users out there should flash this - though still beta it does the job. I had no problems flashing this in TWRP.
[TWRP Unofficial]
I was able to mount all partitions - works. I had no problem flashing this using Odin.
[Problems I've Encountered]
* After rebooting into TWRP Unofficial many times. My log reads "Unable to mount /steady." I have no idea what this is or what partition it belongs too; but, TWRP is still able to do everything else such as mount /data, wipe /system, etc. - I don't think its a big issue to be honest. Just wanted to let you know.
* After installing everything and everything working fine. I do not/cannot communicate with networks (cannot connect to wifi, cannot call, and no data). I had check SIM status = not available, IMEI = Unknown, SN = Unknown. I had made an EFS back up of my KDDI rom with working network communication and restored with with TWRP Unofficial. Installation via TWRP log has stated successful, but upon reboot problem has not been fixed. Any ideas I should try? I also believe the software from the SC-02H OS handles how im about to connect to data towers and catch frequencies. Putting in my own APN does not work.
* Crom Service.apk you've provided at an earlier comment to unlock bootloader, which I've installed, does not work. All it does is FC when trying to open the app - installation is fine. I had also tried getting one from the internet, and looking for it at the Samsung Galaxy App Store - the internet one does the same, FC. Samsung Galaxy App Store does not have Crom Service available. I am assuming SCV33 wont ever be able to unlock bootloader.
* Debloated Rom Zip does not work, after doing a clean install to Stock Odin, installing TWRP Unofficial, system ext4 format, wiping /system /data /internal storage /dalvikArt /cache, and flashing Debloated Rom Zip with TWRP - states installed successful and boots up. Though upon booting I still have all the bloat there. In addition, many FCs from many different apps, even after reboot (e.g. tap and play, google play store, google services). The rom still functions after a couple more reboots after a /dalvikART cache wipe, but it just doesn't seem as fast as the stock one though. I believe this maybe a conflict due to my device, and myself as well.
----
Oh BTW the SCV33 is:
*SM-G935J
*OS 6.0.1
*Single SIM only
I will try my best do to other methods on trying to get this to fully work, but the Network Communication thing always halts my progress. I really dig this kernel man.
Again, thank you for your hard work and dedication to the Snapdragon Variant its very much appreciated :highfive:. Looking at the Exynos sub-forum I get so jelly at times.
OK is yours has a different modem then the rest. Also your partitions might be a bit different, I really need that device in my hands to look at the partition layout. If you can find SCV33 kernel source I will be more than happy to make a kernel for this variant also. I call my kernels beta because it's just how I do it.
Ok found your source for the kernel I'll check out the configs and maybe make a kernel later on this week.
SM-G935J (SCV33)
Here is a test kernel: https://www.androidfilehost.com/?fid=529152257862698452
Rooted rom: https://www.androidfilehost.com/?fid=529152257862698453
Let me know if there is any issues.
Hello all.,,
I checked and read many thread slowly and steadily ,but couldn't find a good solution to root this phone 3T.
I just bought this Beautiful Device runing so smooth but with Hands tied too hard unable to run many apps and many ads and Bloatwares..
Thought to Root this device ,but all are mostly either Oxygen 3 or Marshmallow or 7.0. Version of ANdroid..and DW Error,is also a major concern to look out..
So Please help me to root this device running O2 4.1.1 (I literally dont want to change the stock,as of now) and Android 7.1.1 ,some simple steps...
Thanks and Regards
Awaiting for replies!!
I'm about to get this phone so I've been doing a lot of research myself. It looks like you can follow the steps in this thread and you can flash supersu through TWRP once you've unlocked the bootloader.
Unlock bootloader.
Flash TWRP.
Flash your preferred root zip in TWRP (SuperSU or Magisk are two good choices, I prefer Magisk).
That's about it...
i too tried the above method,,But I got struck with Logo of TWRP and got enabled only after 6 Hours.. But to my fate,,i'm still running on Stock recovery.. Not on TWRP !!
Use the latest official TWRP (currently 3.1.0-1). Works just fine.
i can relate to your question.
however, i discovered how to root the 3t and flash the usual zips files the finally the freedom rom, on my own.
it was a thrill.
i advise you to just take the blue pill.
I installed Blusparks Version of TWRP ,,but still no use,,SuperSU or Magisk both says My phone is not rooted!!!!
I want to live the Stock ROM and just to root the device,,But the steps are not futile for me!
What I would do if i was you.
Unlock bootloader
Flash TWRP
Flash latest Magisk 13.2 zip
Hey,
Is this method still valid for rooting the 3T?
https://forums.oneplus.net/threads/...wrp-root-nandroid-efs-backup-and-more.475142/
Yes, that is still valid, more or less. Might be a more current version of blue_spark's TWRP (official TWRP is on 3.1.1.2) although the link only says 3.1.1-x, so I don't know what that means. But probably won't make a huge difference.
Can't see what version Magisk is linked (my office network is blocking the link). If you choose Magisk, flash latest version 13.3, especially if you want to hide root (from Snapchat, banking apps, etc.). Older versions of Magisk will fail to hide, due to recent changes Google made to SafetyNet.
And what if we want to flash this beta to a brand new device?
http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_openbeta_12/
Should we first unlock the device, then install the TWRP recovery, then flash this beta rom and then root?
Hello, first time here but I need some help.
So I wanted to root my P10 (mainly for Viper) and I started digging around here and there (mostly in XDA). I followed few guides (on how to unlock the bootloader, how to flash TWRP, how to root...) but I still can't pull this off. Anyway, straight to the problem:
So as you can see I'm using P10 on Oreo (B360) and EMUI 8.0. I unlocked the bootloader using ADB & fastboot. Then I flashed this TWRP: link
So far everything went smooth and without any errors. I am able to boot into TWRP. So here I'm stuck trying to flash the root.zip (this one). Whenever I try I get the Error: 1 (as mentioned in the thread), however, I read here in XDA that on Oreo flashing boot.img bricks the phone? I saw several threads of people with bricked phones due to flashing boot.img. My question is - what do I do here?
I looked for other solutions like Magisk but from what I understood Viper4Android doesn't work on it.
Anyone... anything? I'd really appreciate any help.
If it's not possible (even though I've seen people with rooted P10s on Oreo...) is there a way I can revert back the changes I did so I can remove the warning message on bootup and possibly have my warranty back?
you Cant root it yet beacose there is no twrp for emui 8, so look and try some methodes root without TWRP
and why you wanna rooot emui 8, there is nothing for it, yet.
What do you mean? I already said I have TWRP and I'm able to boot into it without problems. I even linked the unofficial TWRP I flashed in my first post. Plus I saw few people here that have rooted P10s on Oreo. And finally all I want to install is Viper.
There is this TWRP by @espaciosalter20 : https://forum.xda-developers.com/p10/development/recovery-twrp-3-2-1-0-emui-8-0-4-04-2018-t3773449
should work, support for data decrpytion...
I used MAGISK 16 to root my OREO EMUI 8.0 P10
-done....
about super root and supersu working on OREO EMUI 8.0 you have to ask in the ROOT thread.
about viper4android i don´t know..i don´t use it.
Firstly, I apologize if this is posted in the wrong place and topic has been covered before, but I really need your help!
I got the A6 brand spanking new 4 days ago, and have managed to flash TWRP (TWRP-3.2.3-TwrpBuilder-a6ltexx-2018-11-26_20-43.tar) successfully and get RMM-State_Bypass_Mesa_v2.zip, Magisk-v18.0.zip & no-verity-opt-encrypt-6.0.zip (in that exact order) and I thought was all good.... BUT here lies the problem, after I have flashed the above files, I need to update Magisk to the latest version to be able to use the Magisk Hide & Superuser functions.. Whenever I have updated Magisk, either by direct install or download only then install in TWRP, it makes the phone reboot at random intervals..
it can be hours between reboots or it can be minutes, it goes blank and restarts from the android boot animation, where I have to enter my pins to be able to use it again.. WHY is Magisk causing this random reboot and how can I fix it??
Ive re-flashed the A600FNXXU3ARL1_A600FNOBE3ARL1_EVR (Android 8.0.0) a good few times now, but this random reboot bug Isn't present since I flashed it back to stock..
Also, a separate question; WHY are certain android apps refusing to run due to phone being rooted?? I thought once you re flash official stock firmware the phone appears "warranty intact"?
I used to be up-to-date with android rooting & modifying back in the day, but I have been out of the loop for a long time.
Thanks for your patience reading this and thanks in advance for any help/answers/time taken by me.
Arty.
Magisk on Oreo doesn't work well if you don't have the one with anti defex version as the kernel keeps avoiding you to use superuser commands as part of security feature even after rooting.
About the stock apps refusing to work after flashing the stock rom, you already tripped knox while flashing twrp which once gone you won't be able to turn back. But flashing a custom kernel would fix such problems most of the time.
henok.gk said:
Magisk on Oreo doesn't work well if you don't have the one with anti defex version as the kernel keeps avoiding you to use superuser commands as part of security feature even after rooting.
About the stock apps refusing to work after flashing the stock rom, you already tripped knox while flashing twrp which once gone you won't be able to turn back. But flashing a custom kernel would fix such problems most of the time.
Click to expand...
Click to collapse
Thank you for your reply!
How do I get said anti defex version? Ive tried googling it but only found unrelated results, could you please point me in the right direction in how to proceed please? thanks
Arty.
I can't point you a direct link with a magisk version you need to flash to get rid of defex. If you're lucky you may get a custom kernel built including it. Try one of the oxygen/phoenix kernels through this A6 thread.
The kernels will also help you byass all knox security related stuff which in turn will help most stock apps get back to working state expect for samsung pay and secure folder.