Realme devices are nice because bootloader unlocks are officially allowed by the company. Unfortunately, they usually also have to be explicitly released, in the form of a DeepTesting/In-Depth Test app from OPPO/Realme. You usually can't take the DeepTesting APK from another device and install it, and if you do, Realme still has to whitelist the device model on the server backend. It turns out that at least the X3 SuperZoom is actually whitelisted for bootloader unlocking by Realme. Now all we need is a DeepTesting APK that'll install, which we do. The Realme 6 Pro's version installs just fine on the X3 SuperZoom.
Since this isn't official yet, I figured I'd share a "guide" (my process) for unlocking the bootloader on the Realme X3 SuperZoom (it should also work on the normal X3, but I don't have one to confirm). Let's get started.
NOTE: I think this goes without saying, but unlocking the bootloader WILL wipe your data, and it WILL void any warranty you may have. While you can relock the bootloader, you shouldn't do this in the first place if you aren't sure.
First up, enable Developer Options. Go to Settings >> About Phone >> Baseband & Kernel and tap the Build Number field 7 times.
Next, go to Settings >> Additional Settings >> Developer Options and enable OEM Unlocking.
Now, download the Realme 6 Pro DeepTesting APK (in the attachments here).
Open it up (launcher shortcut is called In-Depth Test) and start the application process. Agree to the disclaimers and whatnot, and send in the application. (NOTE: If you get an error about your device being carrier-customized, you can work around this. I'll write up another guide for that later.)
After a few minutes, check your application status (the tiny green link at the top right of the home page of the app). It should say "Approved" with another tiny green link to "Start In-Depth Test."
Tapping that link will cause your phone to reboot into fastboot mode. If you don't have fastboot installed on your computer, follow these instructions.
Plug your phone into your computer and execute "fastboot flashing unlock". (NOTE: I had to unplug and replug my phone for every command. Otherwise, fastboot would sit there with "< waiting for any device >".)
Your phone should now show a bootloader unlock prompt. Use the volume buttons to choose the option to continue with the unlock, and use the power button to confirm.
The phone will wipe all data and restart into the setup wizard.
That's it! If you want to root with Magisk, follow this guide: https://forum.xda-developers.com/x3-superzoom/how-to/guide-root-realme-x3-superzoom-magisk-t4136333.
This is great info, thanks @Zacharee1!
Will be unlocking as soon as there is a good recovery software that I can use, which will make rooting process easier.
How long point 5 "After a few minutes, check your application status (the tiny green link at the top right of the home page of the app). It should say "Approved" with another tiny green link to "Start In-Depth Test."
should take, is more than one hour that stay on status "application submitted"
Anyone tried GSI images after unlocking bootloader?
ch3mn3y said:
Anyone tried GSI images after unlocking bootloader?
Click to expand...
Click to collapse
I wouldn't recommend it. My unit is hardware defective and I'm returning it to Realme soon anyway, so I tried an LOS 17.1 GSI. So far, I've only managed to get it stuck at the bootloader splash screen. It just doesn't get past that state. And it's a pain to restore to a functional system. I had to use a leaked OFP and the fastboot that comes with the Realme Flash Tool to reflash the super.img. Stock fastboot breaks things further when flashing it. I have one more combination of weirdness to try, but it doesn't seem like GSIs really work.
I'm not a ROM or bootloader expert, so it's possible I'm just doing something wrong, but if I am, it's certainly not easy to flash a GSI right now. I think the best thing to do is wait for the official bootloader unlock and kernel source, and then someone should be able to build TWRP.
How long can it take for an application to be approved? I'm waiting for 15-20 minutes already
EDIT: OK, I'm just to lazy to check it.
Thanks for the guide, at least I have root now.
Just bumping this thread - any recoveries available for X3 Super Zoom yet?
Though root is possible now, I am waiting for a bit more easy process of flashing through a recovery.
phonedroid said:
Just bumping this thread - any recoveries available for X3 Super Zoom yet?
Though root is possible now, I am waiting for a bit more easy process of flashing through a recovery.
Click to expand...
Click to collapse
PBRP RECOVERY IS Available on Telegram Channel
What telegram channel?
SolankiDS064 said:
PBRP RECOVERY IS Available on Telegram Channel
Click to expand...
Click to collapse
When I checked the PBRP website, there are recoveries available only for Realme X, X2, XT etc, but not for X3 Super Zoom. Can you please give the details about the telegram channel?
EDIT: I got the Telegram channel info from their website. Thanks. (Still to check for X3 SS recovery availability)
phonedroid said:
When I checked the PBRP website, there are recoveries available only for Realme X, X2, XT etc, but not for X3 Super Zoom. Can you please give the details about the telegram channel?
EDIT: I got the Telegram channel info from their website. Thanks. (Still to check for X3 SS recovery availability)
Click to expand...
Click to collapse
https://t.me/RealmeX3Updates join this Group
And Development has been Stopped for Realme X3& SuperZoom because of Developers have No Realme X3 Device
---------- Post added at 08:04 AM ---------- Previous post was at 07:08 AM ----------
phonedroid said:
When I checked the PBRP website, there are recoveries available only for Realme X, X2, XT etc, but not for X3 Super Zoom. Can you please give the details about the telegram channel?
EDIT: I got the Telegram channel info from their website. Thanks. (Still to check for X3 SS recovery availability)
Click to expand...
Click to collapse
https://t.me/RealmeX3Updates
Is there any information after unlocking the bootloader, that it is unlocked when the phone boots up?
For example, in Nexus 7/4 there is an unlocked padlock icon after each reset.
@Zacharee1
Official tutorial for Android 10 is released at https://c.realme.com/in/post-details/1365223130418737152
Thanks
After running a dedicated unlock "in-depth test" app, phone reboots, enters fastboot mode for a second (screen with fastboot and some chinese chars), then reboots to system. When my phone is plugged to PC I try to type "fastboot devices" in platform tools and my phone is not visible there, however it is visible when I type "adb devices" I can not boot into fastboot mode manually either - after pressing VOL UP + POWER for a few seconds, it boots up to fastboot and then immediately restarts to system. How can I possibly unlock the bootloader?
I'm gonna note that the same thing happens when I try to execute "adb reboot bootloader" - boot to fastboot mode for few seconds, then restart to system immediately
Any idea what to do?
M1ch0k0 said:
After running a dedicated unlock "in-depth test" app, phone reboots, enters fastboot mode for a second (screen with fastboot and some chinese chars), then reboots to system. When my phone is plugged to PC I try to type "fastboot devices" in platform tools and my phone is not visible there, however it is visible when I type "adb devices" I can not boot into fastboot mode manually either - after pressing VOL UP + POWER for a few seconds, it boots up to fastboot and then immediately restarts to system. How can I possibly unlock the bootloader?
I'm gonna note that the same thing happens when I try to execute "adb reboot bootloader" - boot to fastboot mode for few seconds, then restart to system immediately
Any idea what to do?
Click to expand...
Click to collapse
Are you sure the unlock application succeeded? This means bootloader unlocking isn't allowed.
Not quite sure it succeeded, I was able to start in-depth test, phone rebooted to fastboot mode (white fastboot logo with chinese chars) for a second and immediately went to system after, I don't know if it was a proper behaviour.
M1ch0k0 said:
Not quite sure it succeeded, I was able to start in-depth test, phone rebooted to fastboot mode (white fastboot logo with chinese chars) for a second and immediately went to system after, I don't know if it was a proper behaviour.
Click to expand...
Click to collapse
Did you enable the OEM Unlocking switch in Developer Options?
Yes, I enabled it.
Zacharee1 said:
Are you sure the unlock application succeeded? This means bootloader unlocking isn't allowed.
Click to expand...
Click to collapse
Is there any way to get around this? it's weird because I bought the phone online and not in any telecommunication services provider. why would they block it?
M1ch0k0 said:
Is there any way to get around this? it's weird because I bought the phone online and not in any telecommunication services provider. why would they block it?
Click to expand...
Click to collapse
I don't know why it's happening, sorry.
Related
I know there is few hundered threads with "unbrick" in title but I read them all and nothing seems to work.
Friend brings me kenzo that he gets since his cousin brick it while trying OTA.
When I power phone its start to load system and it has 3 stages:
1. Show screen with "powered by Android" and 3 dots in the bottom, usualy about 4 min and restart
2. After restart just get black screen with Mi logo in the middle, for about 30 sec and restart
3. Instead of Android with dots bottom have white line progres bar, it takes 4 to 5 min and restart again.
After that stage 2 and 3 repeat for long as you have nervs to wait .
Phone can get in recovery and fastboot mode. And when I put him in test mode just show test screen and cant do anything.
In fastboot mode MiFlash recognize phone but report "device is locked" (try with 20160401 and 20160830).
After that i put him in EDL mode (fastboot reboot-edl) and MiFlash report successful flash. But nothing changes.
I try flashing global stable v8.0.5.0, china stable v8.0.4.0, global dev v6.10.13 and at the end global stable v7.2.5.0.
Any idea welcome. Thx
Have you tried to unlock bootloader? Perhaps install TWRP and do a system/dalvik/cache wipe and install MIUI through that?
banana_bender said:
Have you tried to unlock bootloader? Perhaps install TWRP and do a system/dalvik/cache wipe and install MIUI through that?
Click to expand...
Click to collapse
Cant do that. Even unofficial unlock need phone to be working to enable USB debbuging and accept RSA kay from PC.
Edit: Right now looking for ways to edit boot.img to unlock bootloader in attempt to get any useful recovery.
you can try this guide to flash twrp altogether with rom. after flashing, directly boot to twrp and move to custom rom
abihary said:
you can try this guide to flash twrp altogether with rom. after flashing, directly boot to twrp and move to custom rom
Click to expand...
Click to collapse
I will try... but dont think it will do the job. Will post result little later.
EDIT
It dose not work, just as I think.
All that kind of method/advice need 2 things:
1. Enabled USB debbuging - You cant do that on bricked phone even if you edit boot.img ( ro.debuggable=1 ) because fastboot will not execute command since you will not have option to accept RSA kay from PC on your phone and complete that action.
2. Dev ROM - since you have to enable OEM unlock and that option you have only in dev ROMs. Even Xiaomi official unlock requires that you must do it on dev ROM and that is a reason for "stuck on 50% in unlocking".
I try all that I can think: edit boot.img file, use patch emmc_appsboot.mbn, use edited flash_all.bat and rawprogram0.xml, insert sTWRP and ZCX TWRP in fastboot ROM... and all combination of that. Did it on 7.2.5.0 and 8.0.5.0 stable and 6.8.18 dev (since its last 5.1 ROM that I have).
Most of this attempts ends with "3 stages" explained in the first post. Some just show Mi logo for few sec and restart, once even power off phone. And once I even get phone to go directly to sideload/recovery state showing picture of the phone and usb cable.
Only thing left now is to find info is there difference in accessing to EDL mode between software (reboot-edl), deep flash cable and testpoint. IMHO there is none or little difference. Since software and deep flash can be troubled with bad USB cable or connector or USB board in phone.
IMPORTANT: It appearance that Huawei is no longer going to provide bootloader unlocking services for their devices. Because of this, this guide is of no use unless you can find a way to get a code or you just held onto the code.
Hello, this is a guide for unlocking the bootloader and rooting the Huawei Ascend XT. I am writing this because the current guide is not very well written and does not contain bootloader unlock instructions. This will be split into two parts: Part 1, unlocking the bootloader, and Part 2, rooting the phone.
PLEASE NOTE THAT FOLLOWING THESE INSTRUCTIONS WILL WIPE YOUR DEVICE. I AM NOT RESPONSIBLE FOR AND DAMAGE DONE TO YOUR PHONE!
THINGS YOU WILL NEED:
1. A Huawei Ascend XT with at least 60% of battery left
2. A computer with adb drivers, fastboot drivers, and the Huawei USB drivers
3. A Micro-SD card for your backups (THIS IS VERY IMPORTANT! PLEASE MAKE BACKUPS!)
4. TWRP for this phone. This can be found here: https://forum.xda-developers.com/android/general/huawei-ascend-xt-h1611-t3507933 (credits to enigma2446)
5. The ZIP containing SuperSU. This can be found here: https://forum.xda-developers.com/android/general/huawei-ascend-xt-h1611-t3507933
6. The SDK Platform Tools. These can be found on the android studio website.
PART 1: UNLOCKING THE BOOTLOADER1. Geting the Bootloader Unlock Code: You need to get your bootloader unlock code. You can get this by going to https://emui.huawei.com/en/plugin.php?id=unlock
(EDIT: It appears that this website is down. I have read that if you PM Huawei on Twitter or call them and provide all the details of your phone, they will give you a code. I have not tested this method, bit people have said it worked with the mate 10.) and signing into your Huawei ID. If you dont have one, create one. Then, follow the instructions given to you by Huawei to get the code.
2. Enabling the Enable OEM Unlock Option: To enable this option, you must enable developer options. To do this, go to Settings>About Phone and tap the Build number until it says "You are now a Developer". back out of About Phone, and go to Developer options. turn on "Enable OEM unlock" and press Enable.
3. Enable USB Debugging: While you are still in Developer options, enable the option 'USB debugging" and press OK.
4. Booting Into the Bootloader: once you have completed the first three steps, you can now boot into the bootloader. Connect your phone to your computer, and open the Platform Tools folder you should have downloaded and extracted. Shift-Right click, and press "Open Command Window Here" or "Open Powershell Window Here", depending on your version of windows. Once it is open, make sure your device is detected by typing "adb devices". If it displays your device, you are good to continue. If not, something is not set up right on your computer or phone. Once you verified that your phone is detected, type "adb reboot bootloader".
5. Unlocking the Bootloader: Once your phone has booted into the bootloader, you can now unlock the bootloader. YOUR PHONE WILL BE WIPED ONCE YOU TYPED THIS COMMAND. You can unlock it by typing "fastboot oem unlock <your bootloader unlock code>". Once it has finished, you can reboot your phone, and just run through the setup fast, because you will still have to wipe it again.
PART 2: ROOTING YOUR PHONE1. Move the TWRP image you downloaded (called
Xtrecovery) to your Platform Tools folder and rename it to "TWRP.img"
2. Insert Your Micro-SD Card
3. Move the SuperSU Zip you downloaded to the SD card
4. Re-Enable USB Debugging: Enable Developer options by going to Settings>About Phone and taping the Build number until it says "You are now a Developer". Back out of About Phone, and go to Developer options, and enable USB debugging, and press OK.
5. Boot Into the Bootloader: Type "adb reboot bootloader" into your open CMD window or Powershell window.
6. Verify That your Phone says that the Bootloader is unlocked
7. Type "fastboot boot TWRP.img"
8. TWRP should boot. Tap "Keep Read Only"
9. You should now be in TWRP. Go to Backup>Select Storage and choose your Micro-SD card and tap OK. Uncheck everything and check "Recovery". Then, Swipe the slider to back up your stock recovery partition.
10. Once it has finished backing up, reboot your phone to the bootloader.
11. Once it is in the bootloader, type "fastboot flash recovery TWRP.img" to flash TWRP as your recovery. (I believe this is the point where your warrenty will be invalidated by Huawei, so be careful.)
12. When it finishes flashing TWRP, reboot your phone to TWRP by holding down the power button and volume up
13. It should boot to TWRP. Tap "Keep Read Only", then go to (YOU ARE ABOUT TO WIPE IT AGAIN)Wipe>Format Data and type yes, and hit the enter button.
14. Once it finishes, go to Backup>Select Storage, select your SD card and hit OK, then check every box to backup all six partitions, and swipe to back them up. (At the end, it may seem to get stuck at 98-99%, DO NOT STOP IT! It is generating an MD5 checksum)
15. When it finishes backing everything up, go back to the home screen of TWRP, then go to Install, navigate to where you stored the SuperSU ZIP, select it, then swipe to flash it.
16. When it finishes flashing the SuperSU ZIP, tap "Clear Cache/Dalvik" and swipe to clear them.
17. Reboot your phone. IT WILL REBOOT MULTIBLE TIMES AND APPEAR TO BE STUCK SOMETIMES, BUT DONT TOUCH IT! This is normal and it will eventually boot like normal.
That's it!
Your phone should now be rooted and have SuperSU installed. Please note that this is a Systemless root, and will be removed if you factory reset your phone.Thanks to divineBliss for creating the original instructions.
What do we do after we get root to install custom ROMS? please advise
nedfred0 said:
What do we do after we get root to install custom ROMS? please advise
Click to expand...
Click to collapse
To install a custom ROM, you need the ROM you want to install, gapps depending on the ROM, and the proper firmware. The firmware you are on can be found under about phone and is the last 4 digets of the build number (in the format of B1xx). Once you are on the proper firmware, have your ROM and other things it may require, (every ROM is different), and a backup (just in case), you can flash the ROM from TWRP. Follow the instructions provided by the creator of the ROM to properly flash it.
Where do you get the USB driver at because I am not seeing it at http://consumer.huawei.com/us/support/phones/ascend-xt/
BTJustice said:
Where do you get the USB driver at because I am not seeing it at
Click to expand...
Click to collapse
The drivers come with HiSuite. Download it and you should be good to go.
randomness725 said:
The drivers come with HiSuite. Download it and you should be good to go.
Click to expand...
Click to collapse
Thanks. I tried that but couldn't get it to go so I downloaded these instead which did the job:
https://www.androidfilehost.com/?fid=817550096634745788
does this work on the new h1711 huawei assend xt2
xaneth201 said:
does this work on the new h1711 huawei assend xt2
Click to expand...
Click to collapse
It will not. The TWRP recovery image is device specific and might brick your device if you flash it to your phone.
bricked 1711
randomness725 said:
It will not. The TWRP recovery image is device specific and might brick your device if you flash it to your phone.
Click to expand...
Click to collapse
Well I did not see that, so yeah, I have bricked it. IT comes up and says it is unlocked, it used to sit there then boot into the system.
So I downloaded the TWRP, tried to reboot to recovery and nothing.
Now, it just gets to the yellow warning screen, then goes black. Just bought this today on a black friday sale for 49.00
But did it for a reason. Now I would like to be able to recover it....
I was able to run adb and fastboot, so know that the drivers work, but it looks like it won't even get there now.
And it won't even go to the recovery, so I guess this phone is a real brick.
Can't seem to get the back cover off to remove the battery either.
You need a copy of the stock H1711 recovery image to use
"fastboot flash recovery H1711-stock-recovery.img" to restore the stock recovery. Until someone creates a working H1711 TWRP, I don't know where you'll find a stock H1711 recovery image file.
scrungydoolittle said:
Well I did not see that, so yeah, I have bricked it. IT comes up and says it is unlocked, it used to sit there then boot into the system.
So I downloaded the TWRP, tried to reboot to recovery and nothing.
Now, it just gets to the yellow warning screen, then goes black. Just bought this today on a black friday sale for 49.00
But did it for a reason. Now I would like to be able to recover it....
I was able to run adb and fastboot, so know that the drivers work, but it looks like it won't even get there now.
And it won't even go to the recovery, so I guess this phone is a real brick.
Can't seem to get the back cover off to remove the battery either.
Click to expand...
Click to collapse
download hisuite, enable oem unlocking and usb debbuginig, you gotta also get tha password or the unlocking, denn u run cmd and type:
adb devices
i hope i helped
there is easy way to get unlock bootloader pass for all huawei
just by IMEI search on google "hardreset24 unlock bootloader" there is full info how to do it
BTJustice said:
Where do you get the USB driver at because I am not seeing it at http://consumer.huawei.com/us/support/phones/ascend-xt/
Click to expand...
Click to collapse
Here is the site for USB drivers for all Huawei models:
http://huaweiadvices.com/download-huawei-usb-drivers/
Good luck....
Does the phone even have a fastboot mode?
RomLord14495 said:
Does the phone even have a fastboot mode?
Click to expand...
Click to collapse
Sure it does
Notes on booting up the phone (from power off)
Bootloader (fastboot) = power + volume down + USB hooked to pc
eRecovery = power + volume up + USB hooked to PC
TWRP = power + volume up
Click to expand...
Click to collapse
Optionally you put phone into bootloader/fastboot or recovery modes by typing from an adb prompt "reboot bootloader" or "reboot recovery"
Hi there. The website link for submitting your imei to get the unlock code doesn't work. Does anyone know how to get this code now?
dominoes20 said:
Hi there. The website link for submitting your imei to get the unlock code doesn't work. Does anyone know how to get this code now?
Click to expand...
Click to collapse
You'll have to use DC Unlocker and pay to unlock until the page returns
Since unlocking the bootloader is no longer supported, I have a suggestion but am afraid to try myself.
So, download stock version of rom (aka fastboot rom). Extract, replace recovery.img with twrp (renamed to recovery.img). Restart phone in EDL mode, flash. In theory, edl is working fastboot mode so it shouldn't matter if bootloader is unlocked, correct?
ezopantyd said:
there is easy way to get unlock bootloader pass for all huawei
just by IMEI search on google "hardreset24 unlock bootloader" there is full info how to do it
Click to expand...
Click to collapse
Imma try this out, I’m stuck in a weird situation where my sd card slot broke. When I sent it in for service, they said it was rooted and refused to fix it. I specifically did not root it so that I could send it in for warranty service. So it’s mission to try and root, unlock boot loader etc so that I can have more storage space
---------- Post added at 11:50 AM ---------- Previous post was at 11:36 AM ----------
ezopantyd said:
there is easy way to get unlock bootloader pass for all huawei
just by IMEI search on google "hardreset24 unlock bootloader" there is full info how to do it
Click to expand...
Click to collapse
Can you be a little more specific? I didn’t get that info on google
So, i installed Xposed, and like many people, i got stuck in the logo... No big deal there... Went to look for some help, and it said to go to fastboot, so I went, but it got stuck in the fastboot logo. Then I connected it to the computer and when I try to list the ADB devices I Ialways get an error saying the server is outdated...
I really need some help! I can't find anything online to help me!
Thanks in advance!
Edit: I submitted a bootloader unlock request to Xiaomi earlier today, but I can't see if its approved or not because phone doesn't work
well,
if you are in fastboot mode then the command is "Fastboot Devices", Not "adb Devices"
_____________________________________________
and about boot loop problem try to flash miui fastboot rom.
_____________________________________________
And about bootloader request problem you can go to edl mode and flash miui without any permissions
Thanks:good::good:
nishant2222 said:
well,
if you are in fastboot mode then the command is "Fastboot Devices", Not "adb Devices"
_____________________________________________
and about boot loop problem try to flash miui fastboot rom.
_____________________________________________
And about bootloader request problem you can go to edl mode and flash miui without any permissions
Thanks:good::good:
Click to expand...
Click to collapse
I tried, but i cant seem to go to edl mode through fastboot, any tips? and because of bootloader lock i cant flash fastboot rom with MI Flash
Edl mode needs a specific fastboot version.
For the Redmi Note 3 Pro / Special Edition
Download and extract this package on your PC.
Enter fastboot mode by holding Power and Vol- at the same time. Wait until the Mi Bunny appears, then connect the phone to the PC.
Run reboot.bat in the extracted package. A command prompt will appear. Press a key to reboot the phone to EDL mode.
Upon entering EDL mode, the screen should turn blank. The notification LED might be blinking red. Done.
To get out of EDL mode, hold the Power button for about 10 seconds.
Click to expand...
Click to collapse
Above quote taken from xiaomi reddit wiki.
If the above doesn't work, see the link for deep flash cable, shouldn't be need for kenzo/kate.
How you flashed/installed xposed on locked bootloader is another question?
You may need to update your adb/fastboot version + device drivers(adb)
corkiejp said:
Above quote taken from xiaomi reddit wiki.
If the above doesn't work, see the link for deep flash cable, shouldn't be need for kenzo/kate.
How you flashed/installed xposed on locked bootloader is another question?
You may need to update your adb/fastboot version + device drivers(adb)
Click to expand...
Click to collapse
Ok, so when i try to reboot in edl, it just reboots as normal after screen goes blank...
I installed Xposed with an APK
Sorry if i'm being annoying, but I just want this fixed
KaiZix said:
Ok, so when i try to reboot in edl, it just reboots as normal after screen goes blank...
I installed Xposed with an APK
Sorry if i'm being annoying, but I just want this fixed
Click to expand...
Click to collapse
Mate, watch any video on YouTube. You're not understanding from text instructions.
AtomR said:
Mate, watch any video on YouTube. You're not understanding from text instructions.
Click to expand...
Click to collapse
Can't find any... Recommendations?
EDL Mode: - https://www.youtube.com/watch?v=LDGViyDYPbU
If you can't get into EDL mode, you may need to use the deep flash cable method.
corkiejp said:
EDL Mode: - https://www.youtube.com/watch?v=LDGViyDYPbU
If you can't get into EDL mode, you may need to use the deep flash cable method.
Click to expand...
Click to collapse
I can't get into EDL mode, and I can't make/buy a deep flash cable... I'm getting really scared now...
About ADB, how can I fix it?
KaiZix said:
I can't get into EDL mode, and I can't make/buy a deep flash cable... I'm getting really scared now...
About ADB, how can I fix it?
Click to expand...
Click to collapse
Installing Mi Flash should have put the correct drivers on your PC.
But can be got from here: - https://xiaomifirmware.com/downloads/download-pc-drivers-xiaomi-redmi-note-3/
And I already linked adb/fastboot tools.
IF your comfortable opening your device, there is also a test point method you could try.
http://en.miui.com/thread-244814-1-1.html
Could not find a English video, so maybe try googling more and you might find one.
If not, you could ask at local repair shop, if they would fix it for you. Using Cable/ TP method.
Note for other readers:- MIUI roms need a special version of xposed, for it to work. And installing from an app would more than likely would have use the wrong version. Should never be done on a locked bootloader, only asking for trouble. (Rovo89 is currently trying to bring MIUI support to the official version for nougat roms)
1-step
in order to root these qilive devices you will need...
magisk manager apk v5.6.4
stock boot.img file
working ADB to unlock oem and flash
2-step
lets get to it
place the magisk.apk and the stock boot.img
in the internal memory of your phone (downloads)
if you like to keep stuff organized :good:
3-step
follow the vídeo tutorial and use magisk manager
to patch your stock boot.img it will output a new
boot.img that includes magisk Root (patched_boot.img)
https://www.youtube.com/watch?v=BF4_hnKgjFA
ps: major ty to hovatek team for this great tutorial
step-4 use Google drive or usb OTG to get the patched_
boot.img to your PC and place it in the ADB folder
once you have oem(bootloader) unlocked just
rename the patched_boot.img to boot.img
step-5
unlock oem, these qilive devices wont unlock
the bootloader even if you enable it in DEV options
enable USB debug in dev options
you will need to use ADB commands
command- adb devices
serial appears
command- adb reboot bootloader
phone reboots to fastboot mode
command- fastboot devices
serial appears
command- fastboot oem unlock
(MAJOR WARNING the fastboot
oem unlock will wipe/reset/factoryreset/delete your data)
after you give the command small letters will appear
on the phone screen(yes or no) hard to read dont be hasty plz
use VOLUME+ to select and VOLUME - to confirm
note: when my phone ended the unlock it whent back to
that black screen where you choose fastboot-recovery-restart
and was stuck there, side keys did nothing if this happens
just long press the power key for 10 sec it will shutdown
then press power again to turn on
first boot after unlock will take longer then normal dont freakout
after you unlock small letters will appear during boot up saying the device
is not safe unlocked ,you can later use ( fastboot oem lock )
step-6
flash the patched boot.img with ADB
command- adb devices
serial appears
command- adb reboot bootloader
phone reboots to fastboot mode
command- fastboot devices
serial appears
command- fastboot flash boot boot.img
finished/ok
command- fastboot reboot
and voila you should now have magisk
installed in the app drawer, open it!!
step-7 run the install one final time from the
magisk manager and install magisk V16 using
recomended option it will verify/patch the boot image
Do NOT select the AVB 2.0 BOX it will bootloop the phone
and your done, enjoy your qilive rooted phone.
from this point on you can use the fastboot
command- fastboot oem lock
to remove the letters in boot up about the
device not safe unlocked
WARNING oem lock
will WIPE/FACTORY RESET again (god damn it!!)
ps: i had to install twice in a row,major pain in the ....
Repeat step 7 after Wipe/Reset
here is the stock boot for 2 qilive models
you can get the stock firmware for any qilive
at this site www.doc-doapi.com/EM/qilive/smartph...te_3m-fdd-cs_mul_20170818-110645_songlixin_PC
and get the recovery or boot from the unpacked firmware file
ps:my phone is the Q8SIN4GP AND ITS WORKING FINE
A VERY SPECIAL TY to topjohnwu (magisk creator), this man is nothing
short of a God damn genius!! , and if you can donate to him.
hope this helps other qilive users to root:highfive:
quick note on the qilive models, they have two model names
the cliente name in my case Q8SIN4GP
and the factory name in my model its 882912
in order to download the right firmware for your model
you need the factory model witch is what appears in the qilive
site above, it will be in the back of the phone or the original
box on a sticker just bellow the bar code, full model exempl
:Q8SIN4GP/882912 my firmware serves several models,
these Q8 models all start with 88xxxx WARNING
dont try this using the wrong firmware/boot file or you will DAMAGE your phone
Help with BOOTLOOP problems, if you find your self stuck in a bootloop
the phone wont go past the qilive logo and just stays there, dont freak out
you will loose your data but there is a way out
just keep pressing power + Volume up until a black screen with 3 options appears
when it does let go, use Volume + to select option and Volume - to confirm
select Fastboot or alternative select recovery and then select reboot to bootloader
both option will place your phone in Fastboot mode, once in fastboot mode
connect your phone to PC and use ADB commands to fix/bootloop
command- fastboot devices
serial appears
command- fastboot oem unlock (skip this if you use phone unlocked)
a confirm action option appears on the phones screen
use Volume up to say YES / or Volume Down to say NO
Warning oem unlock will WIPE/Factory reset your phone
once it finishes the phone will be stuck on the
Recovery/fastboot/restart screen just long press the power key
until the phone shuts down
start the phone again using Power + Volume up when the black
screen with the 3 options come up, let go and use Volume up to
select Fastboot mode and confirm using Volume Down
Once in fastboot connect your phone to PC and use ADB commands
command- fastboot devices
serial apears
Here you will flash the magisk patched_boot.img
the same image you used to root your phone
command- fastboot flash boot boot.img
it will say finished-ok (or similar)
command- fastboot reboot
the boot up time will be longer than normal
but the phone should now complete the boot
and present the inicial setup screen, select language
enter your mail, the usual bla bla...
any way at this point just repeat step 7
to get root running again
sp flash tools v5.1716.
phonedriller said:
1-step
in order to root these qilive devices you will need...
magisk manager apk v5.6.4
stock boot.img file
working ADB to unlock oem and flash
2-step....
Click to expand...
Click to collapse
Hi phonedriller,
phew, I did it! (Q8S55IN4G2), thanks.
Next step: Have you found a compatible custom recovery? (especially for nandroid backups and for xposed installation)
Would be very thankful for your help!
thanks
xdatheresianum
xdacktheresianum said:
Hi phonedriller,
phew, I did it! (Q8S55IN4G2), thanks.
Next step: Have you found a compatible custom recovery? (especially for nandroid backups and for xposed installation)
Would be very thankful for your help!
thanks
xdatheresianum
Click to expand...
Click to collapse
Awsome work congrats, as for the recovery so far no luck so try not to go 2 crazy until a working recovery is up and working , install stericsons busy box this is always the first root app i install
If possible buy sterics busybox pro and titaniumbackup pro if you want to install apps to sd card apps2sd pro all of these can be tested in free
Version,again nice work congrats enjoy you rooted phone :highfive:
xdacktheresianum said:
Hi phonedriller,
phew, I did it! (Q8S55IN4G2), thanks.
Next step: Have you found a compatible custom recovery? (especially for nandroid backups and for xposed installation)
Would be very thankful for your help!
thanks
xdatheresianum
Click to expand...
Click to collapse
give a hungry man fish and you solve his problem for a day or two
teach him how to fish and you solve his problem for life
phonedriller said:
give a hungry man fish and you solve his problem for a day or two
teach him how to fish and you solve his problem for life
Click to expand...
Click to collapse
hi phonedriller,
...well, i must have been an unlucky fisherman
an app i installed ended up giving me a soft brick (bootloop between qilive icon opening screen - btw still with the "warning" of "device is unsafe etc", i.e. oem still open - and black screen, qilive opening screen etcetcetc)
have cleaned cache; went for factory reset; etc
BUT: am presently stuck when trying to go via ADB (which used to work perfectly before) that somehow the usb drivers don't want to get installed properly. as a consequence, desktop cannot see devices.
and i cannot, for the sake of me, remember how i had succeeded before installing usb drivers.
could you please help?
thx
cktheresianum
xdacktheresianum said:
hi phonedriller,
...well, i must have been an unlucky fisherman
an app i installed ended up giving me a soft brick (bootloop between qilive icon opening screen - btw still with the "warning" of "device is unsafe etc", i.e. oem still open - and black screen, qilive opening screen etcetcetc)
have cleaned cache; went for factory reset; etc
BUT: am presently stuck when trying to go via ADB (which used to work perfectly before) that somehow the usb drivers don't want to get installed properly. as a consequence, desktop cannot see devices.
and i cannot, for the sake of me, remember how i had succeeded before installing usb drivers.
could you please help?
thx
cktheresianum
Click to expand...
Click to collapse
PS: adb will not work if the phone is not booting to the OS
it will work if you manualy place the phone in fastboot AKA bootloader
MODE ,you see if it does not boot to OS then usb service is not working
use power + Volume up to enter the black menu
use the Volume up to select fastboot(bootloader) volume - to confirm
connect the phone to your PC
flash the boot.img, the same boot.img used to root (patched by magisk)
to see is adb is ok just run - fastboot devices
if a serial is presented then all other stuff should work
step 1 - reflash the boot img
step 2 - after the flash finishes - fastboot oem lock
message on the phone screen, confirm yes to lock
OEM
step 3- press power until it turns off
it should now complete the start up (boot)
if not working this method let me now
you can still flash the full factory firmware
using SP Flash Tool v5.17xx
phonedriller said:
PS: adb will not work if the phone is not booting to the OS
it will work if you manualy place the phone in fastboot AKA bootloader
MODE ,you see if it does not boot to OS then usb service is not working
use power + Volume up to enter the black menu
use the Volume up to select fastboot(bootloader) volume - to confirm
connect the phone to your PC
flash the boot.img, the same boot.img used to root (patched by magisk)
to see is adb is ok just run - fastboot devices
if a serial is presented then all other stuff should work
step 1 - reflash the boot img
step 2 - after the flash finishes - fastboot oem lock
message on the phone screen, confirm yes to lock
OEM
step 3- press power until it turns off
it should now complete the start up (boot)
if not working this method let me now
you can still flash the full factory firmware
using SP Flash Tool v5.17xx
Click to expand...
Click to collapse
dearphonedriller,
thank you so much for your speedy help.
followed the steps given by you. all is well, as you predicted, until step 3.
however:
phone (now without the "orange state" message, i.e. oem locked) still bootloops and short of ADB "fastboot devices" the desktop doesn't see the phone (and driver installation continues to fail), as per your PS (thanks!) i guess flashing the full factory firmware ("RC-mt6737...zip" quoted by you in your very first post) is next.
would you please point me to a basic-for-noobs tutorial or instruct me on the step-by-step commands/procedures using this zip file?!
HUGE thanks
ckth
xdacktheresianum said:
dearphonedriller,
thank you so much for your speedy help.
followed the steps given by you. all is well, as you predicted, until step 3.
however:
phone (now without the "orange state" message, i.e. oem locked) still bootloops and short of ADB "fastboot devices" the desktop doesn't see the phone (and driver installation continues to fail), as per your PS (thanks!) i guess flashing the full factory firmware ("RC-mt6737...zip" quoted by you in your very first post) is next.
would you please point me to a basic-for-noobs tutorial or instruct me on the step-by-step commands/procedures using this zip file?!
HUGE thanks
ckth
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=-zaEmj3-prU
turn the phone off, follow the video
flashing the full firmware is actualy easy
https://forum.hovatek.com/thread-13970.html
or searh sp flash tool here on xda
https://www.youtube.com/watch?v=LzyYXAflmOk&t=125s
phonedriller said:
https://www.youtube.com/watch?v=-zaEmj3-prU
turn the phone off, follow the video
flashing the full firmware is actualy easy
https://forum.hovatek.com/thread-13970.html
or searh sp flash tool here on xda
https://www.youtube.com/watch?v=LzyYXAflmOk&t=125s
Click to expand...
Click to collapse
thank you, phonedriller
everything worked perfectly via SPFlash Tool.
and, referring back to our above questions re the possibility of getting TWRP onto the phones, a developer friend of mine writes me this:
>try to flash TWRP:
>Download following files from this link:
>https://mega.nz/#F!qZIgnJRK!5apBfYo1je0ytg-wmA6JMQ
>- Odin3 v3.12.3 (Complete folder)
>- twrp-3.2.1-0-Q8S55IN4G2-20180318.tar
>1. Start your Phone into download mode
>2. Start Odin (Odin3 v3.12.3\Odin3.exe)
>3. Click on Options and unmark Auto Reboot
>4. Click AP and select twrp-3.2.1-0-Q8S55IN4G2-20180318.tar
>5. Press Start and wait until finished (Reset or OK!)
>6. Restart your phone immediatly to recovery mode
>7. In TWRP Recovery click on mount
>8. Set the checkbox checked at system (that system is mounted)
>9. go back and click on advanced
>10. Open file manager
>11. navigate to system/build.prop and click on build.prop
>12. Click on chmod
>13. type: 0644 and hit the accept button on screen or at the virtual
>keyboard on your phone
>14. restart your phone
i haven't tried this, but am wondering whether it might seem "reasonably possible" when reading through it.
thanks
ckth
Do you perhaps have link to Q8S5IN4GP stock rorm? Mine came with malware installed on it. I want to see if those were chinese who preinstalled or or was it decided by Auchan.
tommo1982 said:
Do you perhaps have link to Q8S5IN4GP stock rorm? Mine came with malware installed on it. I want to see if those were chinese who preinstalled or or was it decided by Auchan.
Click to expand...
Click to collapse
On my phone it came from factory and on the firmware file on 2 models , however only kasperky complains about malware on an system app called Helper bla bla bla i think its a false positive(i think) as no other antivirus or playstore ever found anything,but hey better investigate and be safe then sry right :good: maybe a ported cyanogen rom, ive look at a few rom port tutorials but my knowhow is limited + dont even have a working twrp yet, avg/avast/malwarebytes and a few others ,only kaspersky detects malware.
phonedriller said:
On my phone it came from factory and on the firmware file on 2 models , however only kasperky complains about malware on an system app called Helper bla bla bla i think its a false positive(i think) as no other antivirus or playstore ever found anything,but hey better investigate and be safe then sry right :good: maybe a ported cyanogen rom, ive look at a few rom port tutorials but my knowhow is limited + dont even have a working twrp yet, avg/avast/malwarebytes and a few others ,only kaspersky detects malware.
Click to expand...
Click to collapse
I had issues with adds being displayed at home screen and I was not able to close them. I had to use NetGuard to find that FOTA talks to 'adsup' and it is a known malware provider. I learned that some of the system apps try to talk with Alibaba servers and AdOppo (whatever it's called). Kaspersky might not be wrong, actually.
I'm trying to download stock firmware, but I don't know the file name. The website with it is locked, so unless I know exactly what I need, I cannot download it.
phonedriller said:
On my phone it came from factory and on the firmware file on 2 models , however only kasperky complains about malware on an system app called Helper bla bla bla i think its a false positive(i think) as no other antivirus or playstore ever found anything,but hey better investigate and be safe then sry right :good: maybe a ported cyanogen rom, ive look at a few rom port tutorials but my knowhow is limited + dont even have a working twrp yet, avg/avast/malwarebytes and a few others ,only kaspersky detects malware.
Click to expand...
Click to collapse
Yes i noticed the site now asks for a login that i dont have,but it was open to all until recently i have the firmware file in my pc,a few days ago i went to check for firware updates and the site was diferent and closed , in the site the download link was 882912/****** this firmware services at least 3 similar models
phonedriller said:
Yes i noticed the site now asks for a login that i dont have,but it was open to all until recently i have the firmware file in my pc,a few days ago i went to check for firware updates and the site was diferent and closed , in the site the download link was 882912/****** this firmware services at least 3 similar models
Click to expand...
Click to collapse
I guess the best thing would be a lineage or cyanogen ported rom(clean),ps i flashed the phone 2 times because of popups/adds and battery drain,however im aware that having root and installing tones of crasy stuff can fu.. Up any phone cheap or flagship,thus the firmware flashes,i discovered that having malwarebytes(premium)free for 30days keeps the phone clean and working fine,it seems that one is forced to buy from a main stream brand or risk this kind of thing,little to no support,no updates at all,bad security,the problem is certain apps if removed resoult in boot loop like this Helper app
phonedriller said:
I guess the best thing would be a lineage or cyanogen ported rom(clean),ps i flashed the phone 2 times because of popups/adds and battery drain,however im aware that having root and installing tones of crasy stuff can fu.. Up any phone cheap or flagship,thus the firmware flashes,i discovered that having malwarebytes(premium)free for 30days keeps the phone clean and working fine,it seems that one is forced to buy from a main stream brand or risk this kind of thing,little to no support,no updates at all,bad security,the problem is certain apps if removed resoult in boot loop like this Helper app
Click to expand...
Click to collapse
Ps use root + apps2sd or titaniumbackup to stop/disable the bad apps and replace them with playS app,not possible on all apps of course
phonedriller said:
I guess the best thing would be a lineage or cyanogen ported rom(clean),ps i flashed the phone 2 times because of popups/adds and battery drain,however im aware that having root and installing tones of crasy stuff can fu.. Up any phone cheap or flagship,thus the firmware flashes,i discovered that having malwarebytes(premium)free for 30days keeps the phone clean and working fine,it seems that one is forced to buy from a main stream brand or risk this kind of thing,little to no support,no updates at all,bad security,the problem is certain apps if removed resoult in boot loop like this Helper app
Click to expand...
Click to collapse
I'm thinking about Android 8.1 with it's Treble project. I might not be knowledgable enought to compile and flash it, though.
tommo1982 said:
I'm thinking about Android 8.1 with it's Treble project. I might not be knowledgable enought to compile and flash it, though.
Click to expand...
Click to collapse
Flashing is super easy use spflashtools or. Odin compiling a Rom is not , were you able to get the original firmware? You will need the original firware to get the boot and partition info from what i read so far
Unfortunately not. I will ask at the shop where I bought it how to contact tech. It should be freely available. I don't understand why Qilive restricted access to firmware.
I'll post when I learn anything.
Well, you can download the firmware if you know the file name. The bad news is, it seems the stock firmware has malware preinstalled. If there is anyone who could help confirm it. I have the ROM, and I can upload it to Google Drive if needed.
Hi all,
I'm coming back to a question lingering since the very first post here and mentioned again in post #9:
Is there a successful way to install TWRP on this Qilive model?
Re this topic:
- has anybody tried/has anybody been successful with the procedure described in post #9?
and
- has anybody seen the following TWRP builders' version (do an in-page search on Q8S55IN4G2)
https://twrpbuilder.github.io/fr/downloads/twrp/
with the download belonging to it
https://androidfilehost.com/?fid=890129502657591798
???
any successful installations to report???
Wouldn't THAT be great!!??
thanks
xdack
the idea is to simply deggogle my a10. i found a few videos on how to do it. however i took the liberty of making a note of the base build number and after searching the internet, i found a firmware farchive that contained several md5 files. i figured i may need this in case anything went wrong.
so i went into settings and developer mode, turned on unlocking oem and usb debugging and attempted to flash the phone by booting into rescue mode (power off phone then power on while holding the volume up button) then selecting boot into bootlader from the menu before using a toll called odin on my pc, which given the threads i've seen on here, most of you are aware odin. i tried to flash the tar file reccomended on the site. odin reported failure. so without rebooting i flashed the firmware that matched my phone my selcting the respective md5 files and telling odin to do it. it reported neither success nor failure but gave a message of something like cs select. i have no idea what that means. however on rebooting the phone it booted fine. no errors or anything, just a completely reset phone. I like to add that this is not may main phone as i am a newbie on this area and wouldn't be so reckless as to experiment on my main phone. hower there is an app on there now called lazade which i beleiv is a shopping app based in the asian continent which isn't where i'm from. i unlocked developer mode once again as it had reset and found that the unlock oem option is missing. is it becasuse of the firmware i burned on it and to i need to reburn another? or is ther another way to get it back?
the baseband version is a105gdxu8cvg2
android 11
one ui 3.1
Your post isn't very clear....have you been able to unlock your bootloader?
The OEM Unlock toggle often disappears if 1) the bootloader is already unlocked, or 2) the system has not yet verified whether OEM unlocking is allowed. This is most likely not a firmware issue.
V0latyle said:
Your post isn't very clear....have you been able to unlock your bootloader?
The OEM Unlock toggle often disappears if 1) the bootloader is already unlocked, or 2) the system has not yet verified whether OEM unlocking is allowed. This is most likely not a firmware issue.
Click to expand...
Click to collapse
it's an old phone. i've had it for a number of years, but i got a new phone recently so i took the oppounity to attempt to degoogle my old one. apparently there's more than one way to do this One is to replace android with other operating system. if youtube is to be beleived. i doubt the phone needs veryfying as it's an old phone although the firmware is fresh. perhaps it is unlocked. in tairness i don't know how to determine that.
fjb59 said:
it's an old phone. i've had it for a number of years, but i got a new phone recently so i took the oppounity to attempt to degoogle my old one. apparently there's more than one way to do this One is to replace android with other operating system. if youtube is to be beleived. i doubt the phone needs veryfying as it's an old phone although the firmware is fresh. perhaps it is unlocked. in tairness i don't know how to determine that.
Click to expand...
Click to collapse
The best I can suggest is to flash a LineageOS GSI without Gapps. There are other custom ROMs available that are sanitized of all Google services.
V0latyle said:
The best I can suggest is to flash a LineageOS GSI without Gapps. There are other custom ROMs available that are sanitized of all Google services.
Click to expand...
Click to collapse
are they available here?
fjb59 said:
are they available here?
Click to expand...
Click to collapse
Just Google LineageOS, they have a website. You should be able to flash a GSI image via TWRP.
V0latyle said:
Just Google LineageOS, they have a website. You should be able to flash a GSI image via TWRP.
Click to expand...
Click to collapse
that's my next goal. i haven't got twirp on there. none of the methods i saw on youtube worked.
fjb59 said:
that's my next goal. i haven't got twirp on there. none of the methods i saw on youtube worked.
Click to expand...
Click to collapse
i found the site for it but the a10 is not listed on thier choice of phones
Assuming your bootloader is already unlocked, here is the TWRP thread for your device., which you probably could have found by searching. Instructions for flashing are in that thread. And here is the LineageOS 19.x GSI thread.
If you haven't unlocked your bootloader yet, that's your first step. Some devices are not bootloader unlockable.
V0latyle said:
Assuming your bootloader is already unlocked, here is the TWRP thread for your device., which you probably could have found by searching. Instructions for flashing are in that thread. And here is the LineageOS 19.x GSI thread.
If you haven't unlocked your bootloader yet, that's your first step. Some devices are not bootloader unlockable.
Click to expand...
Click to collapse
i don't know if i have yet. i went though a process and now the oem unlocking option disappeared ffrom the developer menu. i can boot into the bootload from the rescue menu. I assume that's what you mean.
fjb59 said:
i don't know if i have yet. i went though a process and now the oem unlocking option disappeared ffrom the developer menu. i can boot into the bootload from the rescue menu. I assume that's what you mean.
Click to expand...
Click to collapse
When you're in download mode, you should see OEM LOCK among the text in the upper right of the screen. If this says ON, your bootloader is locked.
V0latyle said:
When you're in download mode, you should see OEM LOCK among the text in the upper right of the screen. If this says ON, your bootloader is locked.
Click to expand...
Click to collapse
oem lock onu1)
looks like it's on. how do i disable it for this phone?
Turn the phone completely off, and leave it off for a few minutes. Then, while holding both Volume buttons together, plug in the USB cable. The device should start in Download mode. Hold Volume + until the bootloader unlock screen appears, then follow the prompt to unlock your bootloader. This will wipe data.
V0latyle said:
Turn the phone completely off, and leave it off for a few minutes. Then, while holding both Volume buttons together, plug in the USB cable. The device should start in Download mode. Hold Volume + until the bootloader unlock screen appears, then follow the prompt to unlock your bootloader. This will wipe data.
Click to expand...
Click to collapse
never shows up. i get to the download screen but pressing the vol up keys doesn't do anything. not even adb can see the device. use debugging is turned on. and usb mode is set to file transfer mode. it weorked finde before i reflashed it. perhaps i need another version of the firmware
development, i noticed the wifi wasn't turned on. i turned it on the went into the development mode. unlock oem was there and ticked
so i did what you said again, this time the option for unlocking oem in download was present. i followed the instructions. it booted and came telling me the oem is unlocked and won't be able to verify the intergrty of the os. now it's doing a reset. i think we got here. what next? you you said twrp?
fjb59 said:
never shows up. i get to the download screen but pressing the vol up keys doesn't do anything. not even adb can see the device. use debugging is turned on. and usb mode is set to file transfer mode. it weorked finde before i reflashed it. perhaps i need another version of the firmware
Click to expand...
Click to collapse
ADB only works in Android or in recovery mode. Samsung devices don't have a fastboot mode.
fjb59 said:
development, i noticed the wifi wasn't turned on. i turned it on the went into the development mode. unlock oem was there and ticked
so i did what you said again, this time the option for unlocking oem in download was present. i followed the instructions. it booted and came telling me the oem is unlocked and won't be able to verify the intergrty of the os. now it's doing a reset. i think we got here. what next? you you said twrp?
Click to expand...
Click to collapse
Yep. Since you don't already have TWRP installed, follow "Method 2" in the thread I linked.
V0latyle said:
ADB only works in Android or in recovery mode. Samsung devices don't have a fastboot mode.
Yep. Since you don't already have TWRP installed, follow "Method 2" in the thread I linked.
Click to expand...
Click to collapse
yep it does. i had a little bit of trouble between installing the first and second file. it kept reporting a corrupt operating system but i noteiced it cycled a reboot wo i held hte power and volume up buttons together when it cycled. this allowed me into rescue mode. from there i was able to power down the phone so i could reboot it back into download mode then upload the rescue file contained in the zip file mentioned. after that it booted ok but keeps claiming that the operating system isn''t offician but then boots into android ok. i expect installing the disable_drm_very app wil fix that. then i can try installign a new os.
but that's for tomorrow
Jjflick said:
I noticed this thread and would like to keep looking
Click to expand...
Click to collapse
i hope it helps you. i've detailed the steps i took as best as i could.