Related
I went stock DI01 by Odin, and tried re-rooting by Superoneclick 1.7, but it doesn't respond at "Waiting for device". it freezes.
I tried the other way from terminal, and it keeps on saying that the device isn't connected.
******************************************************************************
* *
* Dirrk's EZ Root v0.2 (Sebastien Krahmers Exploit) *
* *
******************************************************************************
*
* Testing if your device is connected
*
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
*
* If you are NOT connected please follow these directions
* Install the correct drivers
* Turn On Debugging
* Check usb port, cable and phone
* Then rerun this application
*
Press any key to continue . . .
*
* Pushing the files to your phone
* rage.bin, busybox, Superuser.apk, su, com.sh
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
* Restarting your phone to ensure the exploit will work
* When your phone comes back on please unlock it if it is locked and then
* wait
error: device not found
I can access the SD card, but rooters are not working when I turn on usb debugging.
I have Samsung driver installed, android sdk installed, and tried turning on and off while connected to computer. still no root.
how can I get it working?
With the number of pre-rooted roms we have why even root? After odin restore boot but don't sign in and power down. Pull battery/Flash CWM_recovery.tar/ insert battery 3 finger salute to recovery flash desired (rooted) rom. Depending upon what package you used you might have to flash a current modem in odin. Continue to restore set up.
good day.
One Click doesn't work anymore. I did this yesterday, after going back to stock and doing an OTA update, works wonderfully and it's really easy, very low possibility of bricking your phone and having to go through the hassle of fixing that. Go to this thread and follow along. http://forum.xda-developers.com/showthread.php?t=913470 I recommend using the Clockwork Packages from here though they are the most recent and everything seems to be fixed on them. http://forum.xda-developers.com/showthread.php?t=1017817 Easiest way I have ever seen to root a phone.
Team Win Recovery Project 3.0.2
https://postimage.org/
Code:
*** Disclamer
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
WARNING: The stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Flash a root such as SuperSU or phh-superuser. You can also flash no-verity-opt-encrypt.zip.
- Prerequisites :
• YOUR BOOTLOADER MUST BE UNLOCKED
-Check this post for details on how to unlock your stylo 2 plus bootloader
http://forum.xda-developers.com/showpost.php?p=68919557&postcount=15
-If you have problems with the device drivers installed , you will need to install lg bridge app by lg that contains the device driver
http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=PWZO7A26B9UW
• Enable OEM Unlocking and ADB in developer options!
- Download :
https://www.mediafire.com/download/ofyf0vdc8t4349c
[Please do not repost this information or mirror the downloads. Feel free to post a link to this thread anywhere you like.]
- How to install twrp :
Notice:
this install guide was originally written for the stylo 2 plus I'm not sure it will work on the stylo 2..
• BOOT INTO FASTBOOT MODE:
With your phone off, connect your usb cable to your phone while holding VOLUME DOWN to boot into fastboot mode or just type [adb reboot bootloader] in the adb terminal
• ONCE YOU ARE IN FASTBOOT MODE:
Open a command prompt and type "fastboot flash recovery <path_to_recovery.img>” without the quotation marks.
Example: fastboot flash recovery C:/Users/John/Desktop/recovery.img
[don't forget to extract the downloaded recovery zip to get the recovery.img]
• WHEN THE FLASH COMPLETES: (Takes about 2 seconds)
On your phone, unplug the usb cable and power it off by taking out the battery and putting it back in.
• BOOT INTO RECOVERY MODE FOR THE FIRST TIME
HOLD VOLUME DOWN + POWER until you see the LG logo and then temporarily release the POWER button, immediately pressing and holding it back down until you see the white prompt screen. You will NEVER release the volume down button in this process!
Use the hard keys to select "YES" and then "YES" again to boot into
TWRP recovery!
After the TWRP splash screen you will see the option to type in the password to decrypt the filesystem. Due to the password prompt and the touchscreen driver, you will not have any touchscreen functionality until your phone locks for inactivity. After it locks (ON ITS OWN) and the screen dims, you can unlock it normally and TWRP is fully functional.
Warning: use the [volume down + power] buttons combo only to boot into twrp for the first time after flash ! don't use it after that as it will wipe your device every time you try to use the buttons combo again to boot into twrp after the first time .
u have 2 methods to boot into twrp after the first boot:
1- u can use this app [root is required] :
https://play.google.com/store/apps/details?id=com.stephansmolek.reboot&hl=en
2- or u can use adb command type [ adb reboot recovery ] in adb terminal to boot into twrp
DISABLE FORCED ENCRYPTION & ROOT IT!
1. In TWRP, go to Wipe > Format Data. Enter the keyword ‘yes‘, in the provided space and enter. This will wipe the automatically encrypted filesystem, and decrypt it.
2. Once the wiping is done, reboot back into recovery. Go to Reboot > Recovery.
3. When the recovery boots again, connect your phone to the PC and Enable MTP under the Mount section.
4. Transfer the downloaded ‘no-verity-opt-encrypt-2.1.zip’ and ‘SR1-SuperSU-v2.78-SR1-20160915123031.zip to your internal storage or EXTSD
5. Disconnect the device now.
6. Tap on Install. Now, navigate your phone’s storage and select ‘no-verity-opt-encrypt-2.1.zip’. Finally swipe the ‘Swipe to confirm Flash’ button on the bottom of the screen.
7. The flashing process will merely take a few seconds. And when it’s done, follow the same method to flash the root package – SR1-SuperSU-v2.78-SR1-20160915123031.zip
Click to expand...
Click to collapse
Wait 1 or 2 minutes after the zip files are done flashing then reboot system and PROFIT! Your phone may take 3-5 minutes to boot the first time and it might boot-loop once or twice at the Metro PCS splash screen but don’t worry this is expected.
All required files [supersu+dm-verify disable] can be found in this thread :
http://forum.xda-developers.com/lg-g5/development/recovery-team-win-recovery-project-lg-g5-t3363047
Like my work?
consider donating. TY
Nice :good:
Now...who's gonna be first to try this on a LS775 (not Stylo Plus xx550)?
Andromeda_Station said:
Nice :good:
Now...who's gonna be first to try this on a LS775 (not Stylo Plus xx550)?
Click to expand...
Click to collapse
Thx xD it should be safe to test if u are not doing anything wrong , are u able to enter fastboot mode ?
messi2050 said:
Thx xD it should be safe to test if u are not doing anything wrong , are u able to enter fastboot mode ?
Click to expand...
Click to collapse
Not yet...I need to make a proper back up before I do any messing around with this thing. I've got four phones here but the Stylo 2 is the only one I can't afford to brick right now
I thought the Stylo 2 Plus stuff had already been tried and didn't work on this?
Andromeda_Station said:
Not yet...I need to make a proper back up before I do any messing around with this thing. I've got four phones here but the Stylo 2 is the only one I can't afford to brick right now
I thought the Stylo 2 Plus stuff had already been tried and didn't work on this?
Click to expand...
Click to collapse
This is not a stylo 2 plus recovery that's twrp port for the stylo 2 ls775 model....
messi2050 said:
This is not a stylo 2 plus recovery that's twrp port for the stylo 2 ls775 model....
Click to expand...
Click to collapse
Ah, I see that now...just downloaded it.
No luck so far though...have USB debugging and 'enable OEM unlock' checked, 'adb reboot bootloader' and 'reboot to bootloader' from recovery both just boot as normal and power off/volume down+plug in USB just gives the battery charging screen.
Edit: Just went back and read some old threads over again...looks like no one has been able to get to fastboot post ZV3
Is anyone actively trying to get this to work? This is my last hope for this phone. If I cant get it rooted I'm switching phones.
Would this method work for LG VS835 (Stylo 2 V)
Araltd said:
Would this method work for LG VS835 (Stylo 2 V)
Click to expand...
Click to collapse
No
I have the VM version of the stylo 2. I got temp root at one point and tried to get full root via the terminal method but it didn't work and I have king root installed in the system but no root, Ive been trying this method but when I push the adb reboot boot loader command it reboots into the boot loader but I can't get any command to work after that. I launched the adb devices command and no device is listed, the only time the device is listed is when the phone is booted to the stock ROM. I'm currently downloading the lg bridge app in hopes it fixes this issue. I'm willing to do this because I have 3 VM variants of this phone all running zv3. Also my google apps are broke after attempting to achieve permanent root....I feel a Lil bummed about that lol
I spent a fair amount of time yesterday and today trying everything I could imagine to get to fastboot...nothing. Tried everything I could find for other LG models in case one worked...nope. Read every thread on every forum I could find that was posted to within the last 60 days. Pulled out the stylus and tried it all again (lol)...all the while being mocked by the cursed "Boost Zone" app icon.
Now I'm just trying to decide if I should pull my hair out, or punch myself in the nuts.
---------- Post added at 05:35 PM ---------- Previous post was at 05:32 PM ----------
bakerd62 said:
I'm willing to do this because I have 3 VM variants of this phone all running zv3. Also my google apps are broke after attempting to achieve permanent root....I feel a Lil bummed about that lol
Click to expand...
Click to collapse
AFAIK @DirtyPISTOLA is the only one who's pulled this off...everyone else got ZV4'd
You've probably already read these, but if not:
http://forum.xda-developers.com/android/help/lg-stylo-2-ls775-root-t3387009
http://forum.xda-developers.com/android/development/boost-varient-permanent-root-t3435543
I don't even know what I did?
So I tried this. First when I tried to Unlock the bootloader but no matter what I tried it wouldn't work. It would always return with the error saying the command is unrecognized (I tried the old and new command to unlock the bootloader). So then I figured I might as well try and flash the recovery anyways. I tried flashing TWRP and it worked. It comes up with a screen that asking if I want to keep my system partition unmodified. Whether I choose to or not it has a bunch of error messages when I try to factory reset. I'm completely confused. I have TWRP but it seems I can't do anything with it. My phone isn't bricked either. I can still boot into android just fine.
Slayer1822 Jr said:
So I tried this. First when I tried to Unlock the bootloader but no matter what I tried it wouldn't work. It would always return with the error saying the command is unrecognized (I tried the old and new command to unlock the bootloader). So then I figured I might as well try and flash the recovery anyways. I tried flashing TWRP and it worked. It comes up with a screen that asking if I want to keep my system partition unmodified. Whether I choose to or not it has a bunch of error messages when I try to factory reset. I'm completely confused. I have TWRP but it seems I can't do anything with it. My phone isn't bricked either. I can still boot into android just fine.
Click to expand...
Click to collapse
Huh...flashed it with fastboot? If so, what mode was your phone in when you did it?
Andromeda_Station said:
Huh...flashed it with fastboot? If so, what mode was your phone in when you did it?
Click to expand...
Click to collapse
It was in fastboot mode
Slayer1822 Jr said:
It was in fastboot mode
Click to expand...
Click to collapse
Ah...right, I see from the other thread you're on ZV3. I can't get to fastboot
Slayer1822 Jr said:
It was in fastboot mode
Click to expand...
Click to collapse
what's the output of [adb reboot recovery] ?
messi2050 said:
what's the output of [adb reboot recovery] ?
Click to expand...
Click to collapse
It reboots the phone into TWRP with the same message as the first time I booted to it (can see that in my post above)
I'm on zv6 how can I help
Sent from my LGLS775 using Tapatalk
So I figured out after many days of trying to flash a recovery through fastboot and didn't work, I found a way. This may work for zv4, zv5, and zv6 for I'm on zv3. Anywho I'll get started on what I did.
1) get some type of root (temp or perm)
2) download flashify from play store or Google
3) allow root access
4) open up flashify and choose recovery image
5) press choose image
6) locate where you downloaded your recovery
7) press on your image it will pop up a box click yup 8) it will flash, after the flash choose reboot now
9) for any reason you don't want to reboot right then but you want to later, go to flashify and click the 3 dots in the top right corner and press reboot recovery.
How do I get even temp root? I'm on zv6 if it matters.
Sent from my LGLS775 using Tapatalk
I'm just going to leave this here in case anyone of you encounters this problem after modifying files in the system or after flashing custom ROMs. Do note that this fix does not remove the error, but instead bypasses it (for those without EFS backup) and enables the system to boot up normally (installs SuperSU as well). Also, as this requires the use of Odin, devices running MacOS or OSX are not supported.
An alternative (and easier) method has been discovered (refer to post #4 for more details)
Prerequisites:
1) TWRP recovery (https://drive.google.com/open?id=0B6QXDUz9wzc9YWcyZklybmZLc0k)
2) dm-verity bypass (https://drive.google.com/open?id=0B6QXDUz9wzc9Wk1ra0hKYVJtT1k)
3) Odin (https://drive.google.com/open?id=0B6QXDUz9wzc9c3BxYzdBNXhvbnc)
Steps (please follow the steps accordingly in order):
1) Place your phone in D/L mode
- Ensure device is fully turned off by pressing the volume down and power button
- Hold the volume down, home, and power button until a blue warning screen appears
- Press once on the volume up button
- Connect your device to your computer
2) Flash TWRP onto your device
- Open Odin and click on the "AP" tab, and then directing to the location of the TWRP recovery (TWRP_3.0.2.tar)
- Click on the "Options" tab and untick the option "Auto Reboot" [DO NOT TICK ANYTHING ELSE]
- Click on "Start" until Odin says "PASS!"
3) Reboot device into TWRP and flash the bypass zip
- Hold the volume down and power down button until the screen turns off
- Then, hold the volume up, home, and power button until "Set Warranty Bit : recovery" appears at the top of the screen
- Click on "Advanced", followed by "ADB Sideload" and ensure that "Wipe Dalvik Cache" and "Wipe Cache" is ticked, then swipe the bar at the bottom to start sideload
- Using the command prompt, type "adb sideload dm-verity bypass.zip" and wait till it completes
- Click on "Reboot System" after it completes, and your system should be able to boot
Possible errors which you may have encountered:
1) Odin does not detect my device
-- [You will need to install the device driver]
> Download the driver at https://drive.google.com/open?id=0B6QXDUz9wzc9LU9FclQ5WjNWRFk and install it.
2) My device does not boot into recovery after flashing via Odin
-- [System was trying to boot instead of recovery and had ignored the custom recovery after that]
> Go back to step 1) and repeat again
What is ADB and where can I get it?
> The installer is available for download at https://drive.google.com/open?id=0B0MKgCbUM0itNVB1elljU2NPR0k
> Run the installer and type "Y" for every prompt
> Open the command prompt (On your keyboard, press the windows key followed by the "R" key, then type "cmd" in the window and press enter
> Type "cd C:\adb" and you may continue with the steps (do note that C: is the mounted letter of your root drive which may be different from yours)
"* cannot read 'dm-verity bypass.zip *" appears after I entered the command
-- [ADB cannot read the file as the file cannot be found]
> Copy the dm-verity bypass.zip into your ADB folder, or after typing "adb sideload ", drag the dm-verity bypass.zip into your command prompt window and then pressing enter.
Do notify me immediately if there are any errors. Thank you and good luck!
Thanks to @KingWilliams for the dm-verity bypass zip which was present in one of your ROMs.
Q&A
Will OTA updates still work?
> No, the phone will detect that files has been modified and thus OTA updates are stopped. Updates will have to be carried out manually.
NIce Info Thanks, btw is it work on Marshmallow or Lollipop j500f ?
NIce Info Thanks, btw is it work on Marshmallow or Lollipop j500f
Click to expand...
Click to collapse
Should work on both versions but would you mind trying out a simpler and better method instead? It works fine on my device but I am unsure if it works on other models/variants. This method keeps the system status official and even enables OTA updates.
The guide below encompasses the updated method. Do note that as the guide is still being tested and is not an official method, I am assuming that all necessary drivers are installed correctly on your computer and that you have the knowledge and experience to work through the steps as these prerequisites are not included in this guide.
1) Download SamFirm (https://forum.xda-developers.com/attachment.php?attachmentid=3803841&d=1467715462), extract and then run the application.
2) After checking the "Auto" and "Binary Nature" box, type in your model (in your case, SM-J500F) and your region (refer to http://samsung-updates.com/device/?id=SM-J500F if you need help identifying your region) before clicking on "Check Update".
2.1) The application should now be able to detect a firmware saying (for example)
Code:
SamFirm v0.3.6.0
Checking firmware for SM-J500F/TGY/J500FZHU1API2/J500FZZH1API2/J500FZHU1API2/J500FZHU1API2
Model: SM-J500F
Version: J500FZHU1API2/J500FZZH1API2/J500FZHU1API2/J500FZHU1API2
OS: Lollipop(Android 5.1.1)
Filename: SM-J500F_1_20161018133014_hz4nve666g_fac.zip.enc4
Size: 1060126192 bytes
LogicValue: 0us57tdgetwzs2jy
3) Before clicking on "Download", ensure that the option "Decrypt automatically" is checked. The "Check CRC32" option is optional.
4) Once the application is done downloading and decrypting the firmware image, extract it.
5) Using Odin, flash BL, AP, CP, CSC and once it reboots and the error pops up, boot the phone back to the Download Mode.
6) Using Odin, flash AP only (untick BL, CP and CSC checkboxes).
The phone should now boot up normally into the system. Do report the results here for further analysis. Thank you!
Thanks mate, i'll try it :highfive:
Rizzed said:
Should work on both versions but would you mind trying out a simpler and better method instead? It works fine on my device but I am unsure if it works on other models/variants. This method keeps the system status official and even enables OTA updates.
The guide below encompasses the updated method. Do note that as the guide is still being tested and is not an official method, I am assuming that all necessary drivers are installed correctly on your computer and that you have the knowledge and experience to work through the steps as these prerequisites are not included in this guide.
1) Download SamFirm (https://forum.xda-developers.com/attachment.php?attachmentid=3803841&d=1467715462), extract and then run the application.
2) After checking the "Auto" and "Binary Nature" box, type in your model (in your case, SM-J500F) and your region (refer to http://samsung-updates.com/device/?id=SM-J500F if you need help identifying your region) before clicking on "Check Update".
2.1) The application should now be able to detect a firmware saying (for example)
Code:
SamFirm v0.3.6.0
Checking firmware for SM-J500F/TGY/J500FZHU1API2/J500FZZH1API2/J500FZHU1API2/J500FZHU1API2
Model: SM-J500F
Version: J500FZHU1API2/J500FZZH1API2/J500FZHU1API2/J500FZHU1API2
OS: Lollipop(Android 5.1.1)
Filename: SM-J500F_1_20161018133014_hz4nve666g_fac.zip.enc4
Size: 1060126192 bytes
LogicValue: 0us57tdgetwzs2jy
3) Before clicking on "Download", ensure that the option "Decrypt automatically" is checked. The "Check CRC32" option is optional.
4) Once the application is done downloading and decrypting the firmware image, extract it.
5) Using Odin, flash BL, AP, CP, CSC and once it reboots and the error pops up, boot the phone back to the Download Mode.
6) Using Odin, flash AP only (untick BL, CP and CSC checkboxes).
The phone should now boot up normally into the system. Do report the results here for further analysis. Thank you!
Click to expand...
Click to collapse
excuse me, i've tried this method but when i boot the phone to the recovery mode, an error message still show (Device does nit have DRK (Device Root Key), contact to SW PL please flash ENG binary then install DRK), any suggestion ?
dv6661 said:
excuse me, i've tried this method but when i boot the phone to the recovery mode, an error message still show (Device does nit have DRK (Device Root Key), contact to SW PL please flash ENG binary then install DRK), any suggestion ?
Click to expand...
Click to collapse
Sorry about that and for wasting your time. In my original thread, I stated that this method does not eradicate the problem completely but simply bypasses it. The guide that I had requested you to try had two differences - sets the system status to official and enables OTA updates. Now that I think of it, this method is only useful for devices that does not have a workable TWRP/CWM recovery yet, or to give people a peace of mind that their system is official and unmodified. Since entering the recovery mode resurfaces this problem , this method is more or less useless as OTA updates are installed in recovery mode. All updates would need to be done manually via Odin/Smart Switch.
You got to admit this method is simpler and easier though! Could I ask does this method work? Did your phone boot up normally? Thank you.
Rizzed said:
Sorry about that and for wasting your time. In my original thread, I stated that this method does not eradicate the problem completely but simply bypasses it. The guide that I had requested you to try had two differences - sets the system status to official and enables OTA updates. Now that I think of it, this method is only useful for devices that does not have a workable TWRP/CWM recovery yet, or to give people a peace of mind that their system is official and unmodified. Since entering the recovery mode resurfaces this problem , this method is more or less useless as OTA updates are installed in recovery mode. All updates would need to be done manually via Odin/Smart Switch.
You got to admit this method is simpler and easier though! Could I ask does this method work? Did your phone boot up normally? Thank you.
Click to expand...
Click to collapse
yes my phone just boot up normally, the only problem is when i entering recovery mode there's a message "dm-verity need to check verification failed drk first"
i fixed it by mount /system and it worked on j500f .
s10gopal said:
i fixed it by mount /system and it worked on j500f .
Click to expand...
Click to collapse
Are you sure about that? This error only appears when the /efs partition is corrupted.
100%
https://source.android.com/security/verifiedboot/
s10gopal said:
100%
https://source.android.com/security/verifiedboot/
Click to expand...
Click to collapse
Will test it out later on my device.
I have a question. Can I take a DRK backup from one phone and repair another? I have a working Galaxy S6 64gb, and a Galaxy S6128GB that has DRK issue.
Can't Flash TWRP, FRP lock :/
Hi, I have the dm-verification failed problem, but I can't flash twrp because of the FRP lock. Any solution? thanks
_ale33_ said:
Hi, I have the dm-verification failed problem, but I can't flash twrp because of the FRP lock. Any solution? thanks
Click to expand...
Click to collapse
Got to developer settings and tap oem lock on and it should fix your problem.
Hello.
My phone is a Samsung Note 5. 64gb, SM-N9208 ( Taiwan ).
Many many thanks for this post! I have trawled the net for weeks and weeks to find a solution for this ridiculous dm-verity, DRK missing fiasco. I have managed to fix it thanks to your instructions. I understand that this is a work around, don't mind that one bit! But should anyone have a solution to get rid of the problem permanently, you will be an even bigger hero. Let me know if anyone does. Best Regards. Ian.
JaanZZ said:
Got to developer settings and tap oem lock on and it should fix your problem.
Click to expand...
Click to collapse
there's a problem, a mobile go backup sent the device in bootloop, can't boot, only stock recovery or download mode available and i need to backup sensible data.
witty2309 said:
Hello.
My phone is a Samsung Note 5. 64gb, SM-N9208 ( Taiwan ).
Many many thanks for this post! I have trawled the net for weeks and weeks to find a solution for this ridiculous dm-verity, DRK missing fiasco. I have managed to fix it thanks to your instructions. I understand that this is a work around, don't mind that one bit! But should anyone have a solution to get rid of the problem permanently, you will be an even bigger hero. Let me know if anyone does. Best Regards. Ian.
Click to expand...
Click to collapse
Glad that I could help. I suppose you used the TWRP method to recover your device?
_ale33_ said:
there's a problem, a mobile go backup sent the device in bootloop, can't boot, only stock recovery or download mode available and i need to backup sensible data.
Click to expand...
Click to collapse
Perhaps the system files are corrupted. Try flashing the AP file (not HOME file) in Odin and you should be good to go.
Jamessr79 said:
I have a question. Can I take a DRK backup from one phone and repair another? I have a working Galaxy S6 64gb, and a Galaxy S6128GB that has DRK issue.
Click to expand...
Click to collapse
Really sorry for the late reply but in case you have not found an answer yet, no it's not possible (even if it is possible it would be considered illegal - duplicate IMEI).
Hi,
So currently i am staying in a country where Google services aren't possible to access without a VPN which makes it impossible to setup the device for the first time or after flashing a new Rom where you are required to connect to a network to enter your account. Especially after Nougat 7.1.2 and Android O beta the option to setup the device without network has disappeared for me. I have searched online to no avail of how to bypass the setup screen but luckily i found some hints and eventually it worked out. Here is what you need:
Requirements:
* ADB and Fastboot installed on PC or Mac.
* Unlocked Bootloader
* The Latest device TWRP.
* Notepad++
The Process:
* Whether you'r booting your device for the first time or you have flashed a new rom you need to boot to the bootloader by typing "Fastboot reboot bootloader" in Cmd or using the physical keys " Power button + Vol down" or by holding the Vol down and connecting the usb from your device to the PC.
* Launch CMD from Fastboot.exe location folder by clicking Shift + right click and choosing "Open Command window here"
* Enter the Bootloader screen on your device to flash TWRP. Put the TWRP.img you downloaded in the location of fastboot.exe then in CMD Type the following code without quotations: "fastboot flash recovery <filename>.img"
* After flashing TWRP use the hardware keys on your device and select to reboot to the bootloader again, then after booting back select to reboot to recovery. You will enter TWRP after that.
* Mount System in the "mount" section, you will see your device connected to you PC now. Put the SuperSu zip file you downloaded into your device. After that navigate to the install section in TWRP and install SuperSu.
* Now you need to navigate to System/build.prop by using the File browser in TWRP, copy the file to the Sdcard then on your PC using Notepad++ open the build.prop and edit it by adding the following Line without quotations: "ro.setupwizard.mode=DISABLED".
* The next step is to copy back the build.prop edited and replace it with the original one(leave a copy just in case if you want to) in your device, after you do that click the build.prop file make sure to select the left button to set the permissions to default "755".
* That's it reboot your device, you should be able to bypass the wizard and go to the homescreen.
Credits to @organophosphate
https://forum.xda-developers.com/showthread.php?t=1909602
P.S:
* Sorry for making the guide not noob friendly. Noobs you can find tutorials on how to do all the things required here if you google a bit!.
* Regarding the build.prop you can restore the default one you saved(if you did as suggested) using any file browser with root and don't forget to change the permissions to default before you restart the device. Another way is to do it in TWRP as we did earlier.
* I have tested this on Nougat 7.1.2 and Android O DP3 and it worked in both.
* Finally the reason you can't pass the Wifi setup page is because of "Factory Reset Protection", the reason it is enabled is because the device was factory reset before the Google account linked with it was signed out from. Next time you perform a factory reset do yourself a favour and sign out your Google account then do a factory reset, what happens is that next time you start up your device you can set it up without a Google account or wifi like you remember it.
Good Luck :good:
if i need to go through the setup wizard but only have few pages like language selection and owner name for e.g., is it possible?
josephpatrick said:
if i need to go through the setup wizard but only have few pages like language selection and owner name for e.g., is it possible?
Click to expand...
Click to collapse
Basically what this method does is it takes you directly to the home screen bypassing all the setup screens including the ones you mentioned.
Thats alot of work.
Rashad83 said:
Hi,
So currently i am staying in a country where Google services aren't possible to access without a VPN which makes it impossible to setup the device for the first time or after flashing a new Rom where you are required to connect to a network to enter your account. Especially after Nougat 7.1.2 and Android O beta the option to setup the device without network has disappeared for me. I have searched online to no avail of how to bypass the setup screen but luckily i found some hints and eventually it worked out. Here is what you need:
Requirements:
* ADB and Fastboot installed on PC or Mac.
* Unlocked Bootloader
* The Latest TWRP.
* The Latest SuperSu.
* Notepad++
The Process:
* Whether you'r booting your device for the first time or you have flashed a new rom you need to boot to the bootloader by typing "Fastboot reboot bootloader" in Cmd or using the physical keys " Power button + Vol down" or by holding the Vol down and connecting the usb from your device to the PC.
* Launch CMD from Fastboot.exe location folder by clicking Shift + right click and choosing "Open Command window here"
* Enter the Bootloader screen on your device to flash TWRP. Put the TWRP.img you downloaded in the location of fastboot.exe then in CMD Type the following code without quotations: "fastboot flash recovery <filename>.img"
* After flashing TWRP use the hardware keys on your device and select to reboot to the bootloader again, then after booting back select to reboot to recovery. You will enter TWRP after that.
* Mount System in the "mount" section, you will see your device connected to you PC now. Put the SuperSu zip file you downloaded into your device. After that navigate to the install section in TWRP and install SuperSu.
* Now you need to navigate to System/build.prop by using the File browser in TWRP, copy the file to the Sdcard then on your PC using Notepad++ open the build.prop and edit it by adding the following Line without quotations: "ro.setupwizard.mode=DISABLED".
* The next step is to copy back the build.prop edited and replace it with the original one(leave a copy just in case if you want to) in your device, after you do that click the build.prop file make sure to select the left button to set the permissions to default "755".
* That's it reboot your device, you should be able to bypass the wizard and go to the homescreen.
Credits to @organophosphate
https://forum.xda-developers.com/showthread.php?t=1909602
P.S:
* Sorry for making the guide not noob friendly. Noobs you can find tutorials on how to do all the things required here if you google a bit!.
* Regarding the build.prop you can restore the default one you saved(if you did as suggested) using any file browser with root and don't forget to change the permissions to default before you restart the device. Another way is to do it in TWRP as we did earlier.
Good Luck :good:
Click to expand...
Click to collapse
Why wouldnt u just tap the four corners of your screen counter clockwise starting from bottom right?.
pacods61 said:
Why wouldnt u just tap the four corners of your screen counter clockwise starting from bottom right?.
Click to expand...
Click to collapse
That doesn't work on Nougat 7.1.2 and later, or atleast when i tried it. Anyway this method is a last resort for people who have tried every other method.
Thats weird
Rashad83 said:
That doesn't work on Nougat 7.1.2 and later, or atleast when i tried it. Anyway this method is a last resort for people who have tried every other method.
Click to expand...
Click to collapse
Works for me anyways nice write up.
Would this also apply to a device that is frp? And if I get pass the setup screen, will I be able to add a new google account?
Att.Fan1982 said:
Would this also apply to a device that is frp? And if I get pass the setup screen, will I be able to add a new google account?
Click to expand...
Click to collapse
Not possible because do you haven´t unlock bootloader
I need help with this because I have tried everything else and none worked but I do not seem to understand what you would have said above
NattyDread2412 said:
I need help with this because I have tried everything else and none worked but I do not seem to understand what you would have said above
Click to expand...
Click to collapse
Which part you don't get?, Please be specific!. I know the tutorial isn't beginners friendly but it's intended that way, you need to have some experience with the tools or flashing process before attempting this. So please before trying this read up on the parts you don't get by googling them or searching XDA.
Rashad83 said:
Which part you don't get?, Please be specific!. I know the tutorial isn't beginners friendly but it's intended that way, you need to have some experience with the tools or flashing process before attempting this. So please before trying this read up on the parts you don't get by googling them or searching XDA.
Click to expand...
Click to collapse
I really do not understand anything mostly the beginning
NattyDread2412 said:
I really do not understand anything mostly the beginning
Click to expand...
Click to collapse
Sorry to hear that, but if you can't I am sorry to say that the tutorial isn't for you and you will need to read about the terminology used in the guide to better understand.
Unbrick your ASUS ROG Phone 3 for free!!
Don't pay for this stuff anywhere, it's your device and you deserve the right to fix it yourself.
I noticed some people in the community charging upto 50$ for the firmware which should've been free from the start.
Code:
#include <std_disclaimer.h>
/*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* I'm not gonna tell you how to install drivers and other things and only[COLOR="RoyalBlue"][/COLOR]
* proceed with this if you know what you're doing and please do some
* research first. YOU are choosing to make these modifications, and if you
* point the finger at me for messing up your device, I will laugh at you.
*/
NOTE - In case it's a Hard / Soft Brick
• For Hard Brick - Hard brick is when your device can only enter EDL mode and shows up as Qualcomm HS-USB QDLoader 9008 in device manager.
- Just follow from Step 1 to 3 to fix your device.
• For Soft Brick - Soft brick is when the system fails to boot but you can access fastboot mode.
- Just follow Step 3 to fix your device.
Prerequisites ►
• Windows PC
• Device fastboot drivers
• Qualcomm EDL drivers
• a bricked ROG 3 duh
Downloads ►
• EDL Unbrick tool - ROG_PHONE_3_ZS661KS_UNBRICK_EDL.7z
• RAW ROG 3 Firmware - Check the second post below
Instructions ►
Make sure you have device manager opened up to see if the device is connected.
1] Extract the EDL firmware
- Use the side port and connect device to PC
- Then run the file named 1ROG3_VFLASH_EDL.cmd
2] After you get an EDL SUCCESS message let the device boot within a minute or two into bootloader, use the device manager to
check if it's in EDL and if it's still there after a minute, press Power key + Volume down for about 12-13 seconds until
you don't see it in Device Manager, keep it plugged in and let it boot or try to power it on so it gets into the bootloader.
3] Once it's in bootloader flash any of the RAW firmware linked above depending on the device that you have, if its Tencent then flash CN, for global it's WW.
- Extract the RAW firmware and run the file zs661ks_raw_flashall.bat , have some patience and do not disconnect the device as this will take some time.
• That's all folks.
ROG 2/3 Telegram Groups & Channels ►
Global Discussion Group
Updates Channel
GCam Discussion
List of RAW firmware (latest at the top)
— Android 11 RAWs —
18.0410.2108.158 : WW
18.0410.2106.138 : WW
18.0410.2105.133 : WW
— Android 10 RAWs —
17.0823.2104.147 : WW
17.0823.2102.143 : WW
17.0823.2012.131 : WW
17.0823.2012.122 : WW
17.0823.2009.99/100 : WW | CN
17.0823.2009.98 : WW | CN
17.0823.2008.78 : WW | CN
17.0823.2007.58 : WW | CN
17.0823.2007.47/48 : WW | CN
17.0823.2007.32 : WW | CN
does it work for imei repair
tolgahan33 said:
does it work for imei repair
Click to expand...
Click to collapse
NO
deadlyindian said:
Unbrick your ASUS ROG Phone 3 for free!!
Don't pay for this stuff anywhere, it's your device and you deserve the right to fix it yourself.
I noticed some people in the community charging upto 50$ for the firmware which should've been free from the start.
NOTE
If your device can only enter EDL mode and shows up as Qualcomm HS-USB QDLoader 9008 in device manager then this is for you.
I'm not gonna tell you how to install drivers and other things, you should only proceed with this if you know what you're doing.
Prerequisites ►
• Windows PC
• Device fastboot drivers
• Qualcomm EDL drivers
• a bricked ROG 3 duh
Downloads ►
• EDL Firmware - ROG_PHONE_3_ZS661KS_UNBRICK_EDL.7z
• RAW ROG 3 Firmware - WW RAW | CN RAW | Mirror [17.0823.2007.32]
Instructions ►
Make sure you have device manager opened up to see if the device is connected.
• Extract the EDL firmware
- Use the side port and connect device to PC
- Then run the file named 1ROG3_VFLASH_EDL.cmd
• After you get an EDL SUCCESS message let the device boot within a minute or two into bootloader, use the device manager to
check if it's in EDL and if it's still there after a minute, press Power key + Volume down for about 12-13 seconds until
you don't see it in Device Manager, keep it plugged in and let it boot or try to power it on so it gets into the bootloader.
• Once it's in bootloader flash any of the RAW firmware linked above depending on the device that you have, if its Tencent then flash CN, for global it's WW.
- Extract the RAW firmware and run the file zs661ks_raw_flashall.bat , have some patience and do not disconnect the device as this will take some time.
• That's all folks.
Click to expand...
Click to collapse
what cable did you use?
takoyaki17 said:
what cable did you use?
Click to expand...
Click to collapse
You can use the deep flash cable if you can't get your device into EDL mode
Also don't quote the whole thing, just tag the user next time.
sorry,first time using this XDA lab app.thanks btw
Is it possible to unlock bootloader via EDL ?
Reserved Thanks
Do we need to keep PC in Test Mode?
Sorry I used Unbrick Toll of Oneplus earlier in that we need to put PC in test mode, that's why I'm asking.
sendme2pop said:
Do we need to keep PC in Test Mode?
Sorry I used Unbrick Toll of Oneplus earlier in that we need to put PC in test mode, that's why I'm asking.
Click to expand...
Click to collapse
When drivers lack a valid driver signature Windows prevents them from being installed and that's where test mode and disabling Driver Signature Enforcement comes in, if you have driver's with valid signature then you don't need to do this
Moha1155 said:
Is it possible to unlock bootloader via EDL ?
Click to expand...
Click to collapse
If you find a solution to this problem, please write. I also cannot unlock the bootloader on my Tencent version
Thanks for making this thread. This is my 1st Asus device and I confirmed that this tool is working 100%. I got my bricked device back with this tool. Now waiting for other development for Dirty Flash.
Warning Guys please dont use this tool
Unless the issue been rectified
This unbrick tool damage system partition
And persist as well
Need to fixed as early as possible
It also boot in asus rog 2 boot animation
Asus ROG Phone 3 (I003D)
можете помочь пытался прошить с китайской на глобальную Asus ROG Phone 3 ни чего не получается может есть человек мне нужна помощь
Please update the RAW files man thanks
Qtr1st said:
Warning Guys please dont use this tool
Unless the issue been rectified
This unbrick tool damage system partition
And persist as well
Need to fixed as early as possible
It also boot in asus rog 2 boot animation
Click to expand...
Click to collapse
Can you please explore more how its damaging the partition?
Have you tried it or its your guess?
I wouldnt say if i didnt try .. i flashed when i forced my phone to edl
And then tried edl mode .. the phone could not boot anymore .. system partition was damaged and couldnt be flashed using fastboot even when i re unlocked my phone by a help of chinese guy .. and then got system partition solved and also persist was fixed
deadlyindian said:
Latest at the top
17.0823.2007.58 : WW | CN
17.0823.2007.47/48 : WW | CN
17.0823.2007.32 : WW | CN
Click to expand...
Click to collapse
update
sendme2pop said:
update
Click to expand...
Click to collapse
How about you do it yourself? Ever hear of google? Geez.