Related
Hello
I got a new XperiaZ, because i dont like Apple anymore (too Flat).
Well.
I have root the Device, install the Recovery.
That all work perfekt on my unlocked Bootloader.
I wipe all, factory reset,.....
I trie to flash this Miui-Rom, but averytime i flash with the Recovery (no Errors), the Device, dont boot anymore.
So i must flash the stock-Rom again and make the procedure from beginning.
What im doing wrong?
-
Edit:
Dont boot whit the stock-kernel and also "Z-DooMKernel-v08.zip" - averytime the same.
At the and from flashing the Recovery tells me 2 Questions, i click yes.
Than it shot down, and dont reboot.
Can someone help me please?
Tne instructions for installing Miui on locked bootloaders is fairly intricate. You should try flashingna different rom if you havent yet, (like Rom Aur, or basic deodexed stock) and see if you can get those to work. If those fail on you as well then the issue is most likely that you need a different recovery version (or possibly arent wiping right in recovery?) then move on to the roms with multistep install processes.
aethervagrant said:
Tne instructions for installing Miui on locked bootloaders is fairly intricate. You should try flashingna different rom if you havent yet, (like Rom Aur, or basic deodexed stock) and see if you can get those to work. If those fail on you as well then the issue is most likely that you need a different recovery version (or possibly arent wiping right in recovery?) then move on to the roms with multistep install processes.
Click to expand...
Click to collapse
THX
After flash my phone again, and again, i think i now the problem:
In some device it can be open, in others not, right? (*#*#7378423#*#* - yes/no).
But by default the Bootloader is closed, rigtht?
I think i understand.
(But with a unlocked bootloader my problems are in the beginning).
NoFlat said:
THX
After flash my phone again, and again, i think i now the problem:
In some device it can be open, in others not, right? (*#*#7378423#*#* - yes/no).
But by default the Bootloader is closed, rigtht?
I think i understand.
(But with a unlocked bootloader my problems are in the beginning).
Click to expand...
Click to collapse
Yeah the hidden menu should show the bootloader as locked, and whether it is unlockable. However its simpler than that even: if its tmobile brand or device number 6606 than its locked and not unlockable. Other brands, 6602s and 6603s should all be capable of unlocking.
aethervagrant said:
Yeah the hidden menu should show the bootloader as locked, and whether it is unlockable. However its simpler than that even: if its tmobile brand or device number 6606 than its locked and not unlockable. Other brands, 6602s and 6603s should all be capable of unlocking.
Click to expand...
Click to collapse
Yes,its a 6603, and it show me: unlockable.
Now i been tried to flash in "Bootloader-locked-mode", but after point 7.) Boot into CWM & flash the MIUI 3.9.7 ROM .zip:
it stops at 95% (permissions) and go to bootloop.
I dont wanna unlock my Bootloader at the moment.
Damn
Code:
For Locked Bootloaders follow this guide from @kevev
1.) Read through all of these instructions before proceeding!
*****All .FTF files are flashed using Flashtool.*****
*****These .FTF files will NOT flash a baseband because we need to keep the stock radio bands.*****
*****If you flash an incorrect BASEBAND you may loose LTE or all radio functions!****
*****I have included the .166 T-Mobile US C6606 Baseband .FTF in case someone needs it.*****
2.) Place All MIUI ROMs zip files on the external SD card.
(This is important as later on you may have issues placing files here after flashing the first ROM.)
3.) Flash this rom:
C6603_10.3.1.A.2.67_Generic ES_NO_BASEBAND.ftf
4.) Root the device:
Instructions: http://forum.xda-developers.com/showthread.php?t=2386405
Notes:
When you boot after flashing the NL .FTF kernel file go into settings --> About
Tap on "Build number" a bunch of times till you see this on the screen "You are now a developer".
This will allow you to enable "USB Debugging" in the "Developer Options" settings menu.
Also enable "Unknown Sources" in "Security" in settings menu.*****
Ignore the fact that your SD card will not mount. That will be fixed after MIUI is installed.
5.) Install dual recovery:
http://forum.xda-developers.com/showthread.php?t=2261606
Notes:
When running the .bat file enter "1" for SuperSU.
When you see this message "Look at your device and grant supersu access" you may not see
the supersu window on your device if you previously allowed access.
6.) set "vanilla" cwm as default instead of Philz recovery:
Do this by going to sdcard1/XZDualRecovery/XZDR.prop and change the line "dr.vanilla.cwm=false" to true
7.) Boot into CWM & flash the MIUI 3.9.7 ROM .zip:
a.) Shut down the device.
b.) Power on the device.
c.) Press Volume Up when you see the Green LED.
c.) "wipe data/factory reset"
d.) "advanced" --> "wipe dalvik cache"
e.) "install zip" --> "choose zip from /storage/sdcard" --> "miui_l36h_lockbl_3.9.27_498ecdaeac_4.1.zip
f.) Reboot.
g.) Select "Yes" on the "Disable Recovery Flash" screen. The device will reboot.
*****You will have only a blank screen after the black "Sony" screen. This is OK. Continue to next steps.*****
8.) Boot into flash mode and flash .253 kernel:
a.) Keep USB plugged in and open Flash Tool.
b.) Hold Power + Volume Up until the device reboots(Screen goes blank) and release buttons.
c.) Quickly Hold Volume Down until you see "Device connected in flash mode" in the Flash Tool window.
*****If you do not press Volume Down quick enough the device will bootloop again.*****
d.) Flash C6603_10.1.1.A.1.253_Generic DE_KERNEL_ONLY.ftf (Do this quickly as the device may reboot randomly!)
e.) Reboot.
f.) After booting up and moving through the initial MIUI setup menus, wait 5 minutes before proceeding to the next
steps.
9.) Boot into CWM & flash the latest MIUI-Z ROM .zip just like you did the 3.9.27 version:
a.) Flash the .zip
*****Make sure to select "Locked Bootloader" in the Aroma Installer which starts after begining flash!*****
(You can install the "Beats Audio" mod if you wish.)
*****You will have only a blank screen after the black "Sony" screen. This is OK. Continue to next steps.*****
b.) Reboot.
c.) Select "Yes" on the "Disable Recovery Flash" screen. The device will reboot.
10.) Boot into flash mode and flash .67 kernel just like you did the .253 kernel:
a.) After flashing the kernel Reboot.
b.) After booting up and moving through the initial MIUI setup menus, wait 5 minutes before rebooting again.
c.) Enjoy MIUI!
MIUI Update Instructions:
1.) Boot CWM & Flash the latest MIUI-Z ROM .zip:
a.) Wipe Cache & Dalvik Cache.
b.) Flash .zip .
c.) Reboot.
*****No need to flash the .67 kernel*****
Here is all you need thx again @kevev
I got it
But dont ask how exactly: eek:
Had the meantime it the Chinese version, with pre-flashed 253er kernel.
Then again, dual recovery (unchanged XZDR.prop), wipe, Flash the Rom, kernel 2.67 afterwards (ALL WITH TWRP - not CVM).
In any case, she is now running, uff.
Have I kept to about half of the manual.
In between, was nothing more thought .... over and done with.
and ... all without BLunlock.
A beautiful ROM.
Ciao
So I was following this guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684 and when it came to the step to allow modification in twrp I had already goofed up and kept it read only. How do I change this. I cannot find the setting anywhere in twrp???
CombustLemonz said:
So I was following this guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684 and when it came to the step to allow modification in twrp I had already goofed up and kept it read only. How do I change this. I cannot find the setting anywhere in twrp???
Click to expand...
Click to collapse
Reflash TWRP.
Sent from my Droid Turbo.
Resurrection Remix.
Straight Talk/Verizon.
Tapatalk.
Reflashing did not work at first so I went to reboot and selected bootloader. It loaded up TWRP again and gave me the option! We are good! Thanks!
CombustLemonz said:
Reflashing did not work at first so I went to reboot and selected bootloader. It loaded up TWRP again and gave me the option! We are good! Thanks!
Click to expand...
Click to collapse
No problem señor!
Sent from my Droid Turbo.
Resurrection Remix.
Straight Talk/Verizon.
Tapatalk.
CombustLemonz said:
Reflashing did not work at first so I went to reboot and selected bootloader. It loaded up TWRP again and gave me the option! We are good! Thanks!
Click to expand...
Click to collapse
Could you please be more specific about how you got the option to reappear. I have the exact same issue. Thanks
Not sure if this will fix it or not... but I did the same thing when I first loaded twrp, I didnt allow system mods (or whatever it said) but in recovery if you go to Mount... theres a selection "Mount system partition read-only" that had a check and I unchecked it.
I am only assuming this corrects that issue... hopefully someone can come along and confirm.
jlang11 said:
Not sure if this will fix it or not... but I did the same thing when I first loaded twrp, I didnt allow system mods (or whatever it said) but in recovery if you go to Mount... theres a selection "Mount system partition read-only" that had a check and I unchecked it.
I am only assuming this corrects that issue... hopefully someone can come along and confirm.
Click to expand...
Click to collapse
I can confirm that unchecking that option solves this. I tried to flash a ROM update once and it gave me an error saying my system partition was read only, and after unchecking that option it flashed correctly.
The reason for having to run adb flash recovery.img (the TWRP custom recovery) is because you chose the read-only mode introduced in v2.8.7.0 of TWRP. It means that the stock recovery will overwrite it if you reboot without selecting keep modifications on that first screen. Tapping on the Keep Read Only button will keep it temporary, but swiping the blue arrows to the right (like I did in the video), will install TWRP permanently. Reference: http://www.androidexplained.com/oneplus-3-install-twrp/
Latiken said:
I can confirm that unchecking that option solves this. I tried to flash a ROM update once and it gave me an error saying my system partition was read only, and after unchecking that option it flashed correctly.
Click to expand...
Click to collapse
omg thank you so much, that was driving me mental.
can anyone confirm if this works? also, if i flash a new nightly via TWRP is CM going to overwrite the TWRP recovery? or I just have to wipe the cache and the update is done?
i91004ever said:
can anyone confirm if this works? also, if i flash a new nightly via TWRP is CM going to overwrite the TWRP recovery? or I just have to wipe the cache and the update is done?
Click to expand...
Click to collapse
It will overwrite TWRP if you have the developer option checkmark to use CM Recovery. Go into Settings/Developer Options and UNcheck that box.
Hi guys i have the twrp but i flashed a rom called cm13 on my galaxy s5 sm-g900p and i want to go back to touch wiz but the restore says at the twrp
"Cannot restore Modem -- mounted read only. What should i do also the "Mount system partition read-only" box was already unchecked
Wazup20 said:
Hi guys i have the twrp but i flashed a rom called cm13 on my galaxy s5 sm-g900p and i want to go back to touch wiz but the restore says at the twrp
"Cannot restore Modem -- mounted read only. What should i do also the "Mount system partition read-only" box was already unchecked
Click to expand...
Click to collapse
You should probably ask in the Galaxy S5 help section. That SM-G900p model is for Sprint.
Sprint Galaxy S 5 Q&A, Help & Troubleshooting
http://forum.xda-developers.com/sprint-galaxy-s5/help
Latiken said:
I can confirm that unchecking that option solves this. I tried to flash a ROM update once and it gave me an error saying my system partition was read only, and after unchecking that option it flashed correctly.
Click to expand...
Click to collapse
Confirmed ! :highfive:
zefir738 said:
Reflash TWRP.
Sent from my Droid Turbo.
Resurrection Remix.
Straight Talk/Verizon.
Tapatalk.
Click to expand...
Click to collapse
how can i reflash it again? i am having trouble with swipe to modification. swipe is not working i wiped data cache dalvik and system and the backup which i created is not restoring it says system--mounted read only. now i can neither boot to old OS nor the new OS is installing in my phone. im in great trouble please could you help me.
sizzlingsuraj said:
how can i reflash it again? i am having trouble with swipe to modification. swipe is not working i wiped data cache dalvik and system and the backup which i created is not restoring it says system--mounted read only. now i can neither boot to old OS nor the new OS is installing in my phone. im in great trouble please could you help me.
Click to expand...
Click to collapse
Either
how you flashed in the first place, probably fastboot via PC?
or if it's still in your download folder, go to TWRP "install" and check install "image". Flash it TWRP (reinstall) from there, boot to bootloader and then go back to "recovery".
I use the 2nd method all the time to update to newer versions of TWRP.
ChazzMatt said:
Either
how you flashed in the first place, probably fastboot via PC?
or if it's still in your download folder, go to TWRP "install" and check install "image". Flash it TWRP (reinstall) from there, boot to bootloader and then go back to "recovery".
I use the 2nd method all the time to update to newer versions of TWRP.
Click to expand...
Click to collapse
very important to do int hese order
fastboot flash recovery twrp-3.0.3-0-hammerhead.img
fastboot reboot-bootloader
enter the twrp
:good:
ironia. said:
very important to do int hese order
fastboot flash recovery twrp-3.0.3-0-hammerhead.img
fastboot reboot-bootloader
enter the twrp
:good:
Click to expand...
Click to collapse
That's basically what I said. But for this phone, you would want QUARK TWRP recovery – not hammerhead.
Latest QUARK TWRP:
https://www.androidfilehost.com/?w=files&flid=39562
(Use most recent date.)
yes, sorry for the wrong model
Ran into the same problem.
Made my device read only at the start up of TWRP by mistake.
Then I followed the advice by unticking the "mount system partition read only" option.
That's when the menu with the question came up again.
I swiped to the right to allow system modifications.
Rebooted into my phone.
Everything working fine phonewise.
Rebooted into bootloader.
Selected recovery.
Stock Recovery appears. :/
Any idea why stock recovery is returning despite having swiped right for allowing modifications on TWRP?
Hello,
I have Oneplus 3 A3000 running on OOS 4.0.1 (Android 7.0). I also have official OP3 twrp recovery version 3.0.3-0 installed and root was done using supersu free v2.82.. It also has dm verity prompt which comes up during boot time because it is oem unlocked.
I want to know exact procedure to go to complete stock rom + stock recovery along with links to download stock recovery and rom. I saw different versions of stock recovery for different OOS. I don't care about device data as everything is on cloud and nothing on is on device. App list also I can get from google account history. Only thing I care is not to corrupt any system partitions. I also saw few posts that go into boot loop if incorrectly unrooted. I would not want that either.
Your help is greatly appreciated. Virtual beer for you ???. I am software engineer so even though I am noob in terms of hacking my android, I can follow the instructions properly.
Thanks again.
You can flash official OOS Rom and just use TWRP, you can try using the current recovery you have. Allow it to boot after if it allows you then do not go back to TWRP, allow it to boot to its system and then normally it will just override TWRP with OOS stock recovery.
reyscott said:
You can flash official OOS Rom and just use TWRP, you can try using the current recovery you have. Allow it to boot after if it allows you then do not go back to TWRP, allow it to boot to its system and then normally it will just override TWRP with OOS stock recovery.
Click to expand...
Click to collapse
What about unroot and oem lock and dm verity? do I need to do all that before doing OOS update? I am getting OOS 4.1.6 in system update.
mit2nil said:
What about unroot and oem lock and dm verity? do I need to do all that before doing OOS update? I am getting OOS 4.1.6 in system update.
Click to expand...
Click to collapse
you sure you want to be locked again ? i doubt..
dm verity is not a big deal for me.. i allowed it.. im ok with but if you want to remove it siankatbg has a guide on how to remove it..
reyscott said:
you sure you want to be locked again ? i doubt..
dm verity is not a big deal for me.. i allowed it.. im ok with but if you want to remove it siankatbg has a guide on how to remove it..
Click to expand...
Click to collapse
I actually want to go to systemless su + magisk + xposed later on. This one didn't work well with some apps that can detect root. But before I do that I want to start fresh because things tend to go messy and i do not have a backup device right now
mit2nil said:
I actually want to go to systemless su + magisk + xposed later on. This one didn't work well with some apps that can detect root. But before I do that I want to start fresh because things tend to go messy and i do not have a backup device right now
Click to expand...
Click to collapse
flash stock oos thats it.. you may leave the bootloader unlocked. better that way..
Sorry but I am still not sure about exact process. Here are my noob queries:
1. Should I update twrp to latest version before proceding? If so which one? currently it is 3.0.3-0. I remember running into encryption issue due to unsupported twrp when I did this last time.
2. Should I use wipe option to wipe anything before I update OOS? I want to do clean install. If so, what should I be wiping out of dalvik/system/data/internal storage/cache/usb otg?
3. To update, I should copy full ota zip on internal memory -> go to recovery -> install -> select zip file -> swipe to flash. Is that correct?
4. After that if I boot into recovery -> I will keep twrp and if I let it boot, it will replace twrp with stock recovery right?
5. Let say, I let it boot n install stock recovery, will I have dm-verity during next boot?
6. Will my superSU root be gone or still be there? If it is still there should I do complete unroot before starting this process?
7. If it is not gone, is it ok to do complete unroot after stock oos + recovery is installed?
8. I saw a dm-verity patch zip which can be used to patch dm-verity in bootloader mode if I do "fastboot oem disable_dm_verity and fastboot oem enable_dm_verity". Does it suppress the issue or it resolves it gracefully?
Thanks for the patience and help in answering the queries advance.
mit2nil said:
Sorry but I am still not sure about exact process. Here are my noob queries:
1. Should I update twrp to latest version before proceding? If so which one? currently it is 3.0.3-0. I remember running into encryption issue due to unsupported twrp when I did this last time.
2. Should I use wipe option to wipe anything before I update OOS? I want to do clean install. If so, what should I be wiping out of dalvik/system/data/internal storage/cache/usb otg?
3. To update, I should copy full ota zip on internal memory -> go to recovery -> install -> select zip file -> swipe to flash. Is that correct?
4. After that if I boot into recovery -> I will keep twrp and if I let it boot, it will replace twrp with stock recovery right?
5. Let say, I let it boot n install stock recovery, will I have dm-verity during next boot?
6. Will my superSU root be gone or still be there? If it is still there should I do complete unroot before starting this process?
7. If it is not gone, is it ok to do complete unroot after stock oos + recovery is installed?
8. I saw a dm-verity patch zip which can be used to patch dm-verity in bootloader mode if I do "fastboot oem disable_dm_verity and fastboot oem enable_dm_verity". Does it suppress the issue or it resolves it gracefully?
Thanks for the patience and help in answering the queries advance.
Click to expand...
Click to collapse
1. Try the first the current TWRP that you have. If it work, then just reboot it on to the system and TWRP will be overwritten by Stock OOS recovery.
2. Wipe dalvik/system/data/cache ..
3. YES , if im not mistaken.
4. answered on question 1.
5. most probably. Try flashing a certain firmware (not sure which one would work) . This is what I did before. But cant be sure.
6. It will be gone.
7. gone.
8. You can try.
reyscott said:
1. Try the first the current TWRP that you have. If it work, then just reboot it on to the system and TWRP will be overwritten by Stock OOS recovery.
2. Wipe dalvik/system/data/cache ..
3. YES , if im not mistaken.
4. answered on question 1.
5. most probably. Try flashing a certain firmware (not sure which one would work) . This is what I did before. But cant be sure.
6. It will be gone.
7. gone.
8. You can try.
Click to expand...
Click to collapse
Thank you so much.
mit2nil said:
Thank you so much.
Click to expand...
Click to collapse
I will tell you what I do.
Flash the latest official TWRP which is 3.1.1-2
If you want a totally clean install, boot into recovery and wipe system data including internal storage, dalvik and cache.
Then without rebooting, push the ROM downloaded from the OnePlus site to the phone. Select the ROM in recovery and swipe to flash.
Otherwise you can copy the ROM to the phone, boot into recovery, wipe system, data, dalvik and cache and then in recovery, flash the ROM.
Wipe dalvik and cache and reboot into system.
Your root will be gone and along with it TWRP. You will be on stock ROM with stock recovery.
Leave the bootloader unlocked. If necessary, it can be locked at any time.
Most likely you will not get the dm verity error. If you do, simply flash the zip given in post #215 in siankatabg's thread on dm verity. It will merely remove the message as all such methods do.
Enjoy
tnsmani said:
I will tell you what I do.
Flash the latest official TWRP which is 3.1.1-2
If you want a totally clean install, boot into recovery and wipe system data including internal storage, dalvik and cache.
Then without rebooting, push the ROM downloaded from the OnePlus site to the phone. Select the ROM in recovery and swipe to flash.
Otherwise you can copy the ROM to the phone, boot into recovery, wipe system, data, dalvik and cache and then in recovery, flash the ROM.
Wipe dalvik and cache and reboot into system.
Your root will be gone and along with it TWRP. You will be on stock ROM with stock recovery.
Leave the bootloader unlocked. If necessary, it can be locked at any time.
Most likely you will not get the dm verity error. If you do, simply flash the zip given in post #215 in siankatabg's thread on dm verity. It will merely remove the message as all such methods do.
Enjoy
Click to expand...
Click to collapse
Hi sorry I was afk for couple of weeks. So I started following this procedure. Very strangely, after I did a reboot post stock OOS (1.4gb zip) flash, twrp said no os installed, you are sure you want to reboot? I wasn't sure so I just said yes. Then I also so dm-verity coming back which was not the case when I started as I had disabled it using "fastboot enable_dm_verity" command.
Now, its been more than five minutes and my phone is stuck on the boot animation forever. (red dot in middle and two while dots rotating).
I am not sure what happened. Can someone please help me ?
mit2nil said:
Hi sorry I was afk for couple of weeks. So I started following this procedure. Very strangely, after I did a reboot post stock OOS (1.4gb zip) flash, twrp said no os installed, you are sure you want to reboot? I wasn't sure so I just said yes. Then I also so dm-verity coming back which was not the case when I started as I had disabled it using "fastboot enable_dm_verity" command.
Now, its been more than five minutes and my phone is stuck on the boot animation forever. (red dot in middle and two while dots rotating).
I am not sure what happened. Can someone please help me ?
Click to expand...
Click to collapse
Never mind. It booted to setup screen after few minutes. I guess I was in too much hurry.
i just went to stock yesterday, i flash stock recovery followed by sideloading the Oxygen OS and after that relock the bootloader.. i kinda feel the battery is much better now compare to when it was rooted with OOS
danxtian said:
i just went to stock yesterday, i flash stock recovery followed by sideloading the Oxygen OS and after that relock the bootloader.. i kinda feel the battery is much better now compare to when it was rooted with OOS
Click to expand...
Click to collapse
Awesome. I am still getting safety net failure even after locking bootloader lock. Any ideas? It fails on CTS profile match. I even did factory reset. Only thing I can think of is the "dm verity" which is back for some reason even though I am on complete stock rom+recovery with no root or unlocked bootloader.
Any way to remove it from stock recovery?
mit2nil said:
Awesome. I am still getting safety net failure even after locking bootloader lock. Any ideas? It fails on CTS profile match. I even did factory reset. Only thing I can think of is the "dm verity" which is back for some reason even though I am on complete stock rom+recovery with no root or unlocked bootloader.
Any way to remove it from stock recovery?
Click to expand...
Click to collapse
There is a zip floating around XDA which I am not able to locate immediately. It may be on siankatabg's thread on dm verity. Simply flash it.
There is also another method I read about where you flash the 4.0.2 firmware, use the enable verity command on adb, boot the phone and then flash the current firmware.
Both methods are mentioned here in XDA. Search for it.
EDIT: One of them here: https://forum.xda-developers.com/showpost.php?p=72273041&postcount=215
See also the OP of the same thread for the other method.
mit2nil said:
Awesome. I am still getting safety net failure even after locking bootloader lock. Any ideas? It fails on CTS profile match. I even did factory reset. Only thing I can think of is the "dm verity" which is back for some reason even though I am on complete stock rom+recovery with no root or unlocked bootloader.
Any way to remove it from stock recovery?
Click to expand...
Click to collapse
i remember having the dm verity but i forgot what i did to make it disappear.. after that time ive been running OOS rooted with twrp until i decided to go back to stock locked
So, I stopped doing anything as I got busy with my life. Here comes the 4.1.7 OTA and my DM verity was gone. So, it seems like if you go to stock and if still dm verity exists, try to do ota update or go to one ota back for flashing.
Here we have root for stock rom Thanks to the Chainfire Team.
Everything done by them so all thanks and credits are for them
Download
https://download.chainfire.eu/1036/CF-Root/CF-Auto-Root/CF-Auto-Root-on7xelte-on7xeltedd-smg610f.zip
Installation
-Enable USB debugging and OEM unlocking in the settings
- Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a button to continue
-Flash the CF-Auto-Root package as AP in ODIN(Comes within the zip file), and your device should reboot into a modified recovery (signified by a large red Android logo) and it will install SuperSU for you and restore the stock recovery, and reboot back into Android.
I tested it on my device and it worked normally
I will not be responsible for any damage to your device, but following the steps will normally work normally
I just tested with ROM stock 6.0.1 with security patch from 1 July 2017
.
Hayleyw2 said:
Here we have root for stock rom Thanks to the Chainfire Team.
Everything done by them so all thanks and credits are for them
Download
https://download.chainfire.eu/1036/CF-Root/CF-Auto-Root/CF-Auto-Root-on7xelte-on7xeltedd-smg610f.zip
Installation
-Enable USB debugging and OEM unlocking in the settings
- Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a button to continue
-Flash the CF-Auto-Root package as AP in ODIN(Comes within the zip file), and your device should reboot into a modified recovery (signified by a large red Android logo) and it will install SuperSU for you and restore the stock recovery, and reboot back into Android.
I tested it on my device and it worked normally
I will not be responsible for any damage to your device, but following the steps will normally work normally
I just tested with ROM stock 6.0.1 with security patch from 1 July 2017
.
Click to expand...
Click to collapse
Hi will it work for version 7.0 also
it's working fine for me
i have "G610FDDU1BRF2" with android version 7.0 and it gets installed successfully
thanks
How to change Supersu with Magisk?
Razortm said:
it's working fine for me
i have "G610FDDU1BRF2" with android version 7.0 and it gets installed successfully
thanks
Click to expand...
Click to collapse
How to restore stock recovery
Ryan.XM said:
How to restore stock recovery
Click to expand...
Click to collapse
Flash the cf auto root and it will automatically change your recovery into stock.
bjpp21 said:
Flash the cf auto root and it will automatically change your recovery into stock.
Click to expand...
Click to collapse
Ok thanks
I have J7 prime [SM-G610F] with stock andriod 8.1, samsung experience 9.5 and 1 November 2018 security patch will it still work?
I don't think so. I think the J7 with 8.1 is impossible to root? I can't seem to find an answer on this.
lordbaal19 said:
i don't think so. I think the j7 with 8.1 is impossible to root? I can't seem to find an answer on this.
Click to expand...
Click to collapse
its not impossible to root j7 on oreo..just search here in xda and you will find the impossible is really possible.
Well the TWRP thread has no real answers and this method doesn't work either.
I have done it
LordBaal19 said:
Well the TWRP thread has no real answers and this method doesn't work either.
Click to expand...
Click to collapse
yes, I have made root in my SM-G610m with Android 8.1 and it was with TWRP, and I have learned it from YouTube and in Spanish language.
For now I do not have available Super User. I think this post will work for me
ernestoi said:
yes, I have made root in my SM-G610m with Android 8.1 and it was with TWRP, and I have learned it from YouTube and in Spanish language.
For now I do not have available Super User. I think this post will work for me
Click to expand...
Click to collapse
Found a way:
LordBaal19 said:
Which one do you recommend? At which point do I have to install it and then I don't need to install no-verity-opt-encrypt-6.0?
EDIT: I think I finally got it. I did it like this:
1. Ok, so the phone as a fresh 8.1.0 system (just flashed the 7.0 and then it updated OTA in a matter of minutes). I enter the phone, enable the developer mode, enable OEM Unlocking and USB Debug.
2. Then I put the phone on download mode, flash the TWRP recovery disabling the auto-reboot on Odin so it doesn't boot to system automatically. This seem important since otherwise the recovery goes back to stock.
3. Then, to get out of download mode I press vol. down and power keys at the same time and the phone turn off. Then I turn on the phone into recovery mode, once in there I swipe into write mode and go to Wipe and select Format Data, type down yes and it says it's done. I go back to TWRP main menu.
4. I connect the cellphone to the PC and in storage I select Mount USB. Then drag the Magisk-v18.0.zip file into the storage that pops up on Windows. Then I saftely remove the device in Windows and go back to the main TWRP menu on the phone. I select Install and install the .zip file without selecting Signature verification or Reboot after is complete. It says is done installing and no errors seems to occur. I employ the button to wipe Cache and Dalvik.
5. I go back again o Wipe and select Format Data, type down yes and it says it's done, again.
5. Then I try to reboot to System, and choose to Do Not Install the TWRP app, and... SUCCESS!! The phone starts again, I config everything and then Magisk is there in the apps. I tried with an app that requires SU and it works!
Thanks for the help.
Click to expand...
Click to collapse
For the files and details check the OP on that thread.
LordBaal19 said:
Found a way:
For the files and details check the OP on that thread.
Click to expand...
Click to collapse
That's the way I have done it. But if you go on Z3X, select the device (SM-G610M), and you perform some activity like repair IMEI, Z3X detects the root, but it does not detect the Super User.
Hello ... Any ideas on recovering IMEI after successful root of Note9 ?
IMEI currently unknown (both), TWRP shows empty EFS folder (should i see these files?), Software Baseband is UNKNOWN too.
Software factory wipe done with no effect, OEM unlock is unlocked (and not greyed out).
Thanks
Just wondering if anyone has recovered from this ?
did you read all of dr ketans thread on root?
go to general discussion section / dr ketan oem fix and root and simply do a search in that thread for imei
edit
https://forum.xda-developers.com/galaxy-note-9/how-to/root-note-9-n960f-fd-experimental-t3832143
basicaly you flash back stock firmware and try again.
bober10113 said:
did you read all of dr ketans thread on root?
Click to expand...
Click to collapse
do let us know the tread link
bober10113 said:
did you read all of dr ketans thread on root?
go to general discussion section / dr ketan oem fix and root and simply do a search in that thread for imei
edit
https://forum.xda-developers.com/galaxy-note-9/how-to/root-note-9-n960f-fd-experimental-t3832143
basicaly you flash back stock firmware and try again.
Click to expand...
Click to collapse
nrah said:
do let us know the tread link
Click to expand...
Click to collapse
added link
Thanks for the link
I have been plowing through - i still can't work out how to backup the EFS before TWRP is installed.
Should the backup take place after TWRP is installed, before the first reboot (and before running the Dr's script) ??
nrah said:
Thanks for the link
I have been plowing through - i still can't work out how to backup the EFS before TWRP is installed.
Should the backup take place after TWRP is installed, before the first reboot (and before running the Dr's script) ??
Click to expand...
Click to collapse
restore back to stock and be sure everything works.
then flash twrp with odin and dont let phone reboot.
manualy reboot to recovery. using an external sd card backup EFS partition.
go to wipe menu and format data.
go to reboot menu and reboot back to recovery.
go to wipe menu and do a factory wipe, the default swipe right option.
now you have 2 choices:
either flash dr ketan method 1 root oem fix zip and stay on stock firmware.
or
flash dr ketan method 1 zip and then flash a custom rom.
then reboot. if no signal restore the backup of efs you made earlier.
bober10113 said:
restore back to stock and be sure everything works.
then flash twrp with odin and dont let phone reboot.
manualy reboot to recovery. using an external sd card backup EFS partition.
go to wipe menu and format data.
go to reboot menu and reboot back to recovery.
go to wipe menu and do a factory wipe, the default swipe right option.
now you have 2 choices:
either flash dr ketan method 1 root oem fix zip and stay on stock firmware.
or
flash dr ketan method 1 zip and then flash a custom rom.
then reboot. if no signal restore the backup of efs you made earlier.
Click to expand...
Click to collapse
I have been doing this, except for the additional step on the factory wipe that you pointed out - thanks.
But after three full rounds of rooting and trying to restore the EFS, i still have "unkown" and no Baseband information when i get to the end. When i return to the stock image, both Baseband & IMEI's are present.
I have backed up EFS/Baseband/Carrier configs/carrier images successfully and restored all 4 partitions. But IMEI does not return.
nrah said:
I have been doing this, except for the additional step on the factory wipe that you pointed out - thanks.
But after three full rounds of rooting and trying to restore the EFS, i still have "unkown" and no Baseband information when i get to the end. When i return to the stock image, both Baseband & IMEI's are present.
I have backed up EFS/Baseband/Carrier configs/carrier images successfully and restored all 4 partitions. But IMEI does not return.
Click to expand...
Click to collapse
are you on pie or oreo?
bober10113 said:
are you on pie or oreo?
Click to expand...
Click to collapse
8.1, Oreo .. was thinking of grabbing a ver9 image and giving it a go
nrah said:
8.1, Oreo .. was thinking of grabbing a ver9 image and giving it a go
Click to expand...
Click to collapse
did you try method 2 in dr ketans oem fix root hread?
also maybe try flashing a custom rom instead of being on stock and see if that works out for you.
but to think of it, believe your issue is kernel related. i think i remember reading something about it.
so after twrp and data format , reboot back to twrp and oem fix, dont reboot to OS yet. try flashing endurance kernel or tgp kernel. just be sure to take the appropriate oreo or pie version depending on what android os version you go on.
bober10113 said:
did you try method 2 in dr ketans oem fix root hread?
also maybe try flashing a custom rom instead of being on stock and see if that works out for you.
but to think of it, believe your issue is kernel related. i think i remember reading something about it.
so after twrp and data format , reboot back to twrp and oem fix, dont reboot to OS yet. try flashing endurance kernel or tgp kernel. just be sure to take the appropriate oreo or pie version depending on what android os version you go on.
Click to expand...
Click to collapse
:good:
I have not tried method 2 yet .. I did flash OREO and when i tried to run to flash TWRP, the console echoed "Only official released binaries are allowed to be flashed(Recovery)". So i will need to roll back to an earlier image on 8.1
Forgive my lack of knowledge - where would i find the endurance kernel ? Thanks.
nrah said:
:good:
I have not tried method 2 yet .. I did flash OREO and when i tried to run to flash TWRP, the console echoed "Only official released binaries are allowed to be flashed(Recovery)". So i will need to roll back to an earlier image on 8.1
Forgive my lack of knowledge - where would i find the endurance kernel ? Thanks.
Click to expand...
Click to collapse
that binaries issue you had should have been fixed by ketans oem fix root.( method 1)
when you flash back stock to correct the issue. go to system settings and go down to software update and make if manualy find updates. it will then pop up "device registered". then to go to software and tap "build" a few times to make developer options appear.
then go check in dev options oem unlock should say already unlocked."
if i dont do the manual software update check thing after a binaries issue, i would get stuck.
also unrelated:
when you flash stock, you flash all 5 files right?( in odin csc slot you put csc.md5 and not the home csc.md5 and all the other slots only have 1 appropriate file so you cant go wrong there)
endurance:
https://forum.xda-developers.com/galaxy-note-9/development/kernel-endurance-kernel-v1-1-7-t3883862/
v2.xxxx is pie
v1.xxxx is oreo
after flashing kernel.zip you MUST flash magisk or you wont have anyways to manage root and give permissions.
so also flash right after kernel:
https://github.com/topjohnwu/Magisk/releases/download/v19.3/Magisk-v19.3.zip will eventualy be not the latest( check last link below dor mire up to date)
then if and when phone boots up you can install the magisk manager app:
https://github.com/topjohnwu/Magisk/releases/download/manager-v7.1.2/MagiskManager-v7.1.2.apk
both can be found here are up to date :
https://github.com/topjohnwu/Magisk/releases
bober10113 said:
that binaries issue you had should have been fixed by ketans oem fix root.( method 1)
when you flash back stock to correct the issue. go to system settings and go down to software update and make if manualy find updates. it will then pop up "device registered". then to go to software and tap "build" a few times to make developer options appear.
then go check in dev options oem unlock should say already unlocked."
Click to expand...
Click to collapse
In developer mode, it was set for USB debug correctly. The OEM lock option was not present on this OREO version.
Currently bumping back to 8.1
And yes, I select all 4 files in Odin.
nrah said:
In developer mode, it was set for USB debug correctly. The OEM lock option was not present on this OREO version.
Currently bumping back to 8.1
And yes, I select all 4 files in Odin.
Click to expand...
Click to collapse
well thats one of your problems. if oem unlock has not appeared you either need to wait for 7 days or try the method i described by visiting system/software update/manual update and wait for a pop up message that says device registered. then go back to dev options to see of OEM unlock has appeard and says that it is unlocked
Waititng 7 days sure....
That doesn't work imho. Just download an older 8.1 stock rom and flash . u will find OEM to be unlocked there.
The fix in the end was to use the Root_for_OEM_issue_devices_v5 script. I had been using the v3 script. I had followed Max's vid from high on Android, where he's got the earlier script version on his site.
Issue also, once rooted, was that Magisk was out of sync - Magisk was ahead of the manager, so i down graded the manager (once I worked out the release pairs), and magisk was stable again. I did note that the Magisk did not always maintain root for some reason, when the version were out of sync. Possible connection, not sure.
Must admit you learn a lot about these phones when you have a root problem - a lot more compared to someone just following someone else's good work and wanting the %100 it will work path !
Thanks bober10113 for chipping in along the way.