Hi,
I have a Samsung Galaxy S III (GT-19300 Intl), with Android 4.1.2. I recently rooted it and now I get this message with a 'dead Android' when I go into recovery:
# MANUAL MODE #
-- Applying Multi-CSC ...
Applied the CSC-code:BTU
Successfully applied multi-CSC.
Firstly, the device works fine, no problems. It's just when I go into recovery that I get this.
From a bit of research I understand the CSC is the country code. BTU = United Kingdom, where I live. My Android 'Build number' is I19300XXEMG4. XX I believe is the CSC, and so that no longer matches the built-in CSC, is that correct? Which, as a result, won't allow me to update the software... which is fine as I plan to flash a ROM update (no idea which yet)... but I'm new to this so I just wanted to check with you guys whether or not I need to do something about this before proceeding with a flash?
Many thanks.
Its normal. But you should flash a custom recovery like clockworkmod or TWRP before flash ROMs.
1) Download correct Clockworkmod (touch or regular as you wish) for your device from http://www.clockworkmod.com/rommanager
2) Place it at the root of your sdcard and rename it recovery.IMG
3) Download and install terminal emulator from the play store : https://play.google.com/store/apps/d...roidterm&hl=en
4) Run the terminal and
type: su (press enter)
Then type: dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 (press enter)
Don't mess up the command or you WILL brick your phone.
And you can now flash ROMs using a custom recovery
ipromeh said:
Its normal. But you should flash a custom recovery like clockworkmod or TWRP before flash ROMs.
1) Download correct Clockworkmod (touch or regular as you wish) for your device from http://www.clockworkmod.com/rommanager
2) Place it at the root of your sdcard and rename it recovery.IMG
3) Download and install terminal emulator from the play store : https://play.google.com/store/apps/d...roidterm&hl=en
4) Run the terminal and
type: su (press enter)
Then type: dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 (press enter)
Don't mess up the command or you WILL brick your phone.
And you can now flash ROMs using a custom recovery
Click to expand...
Click to collapse
Thanks. How about Recovery Tools or ROM Manager apps that do this automatically. Would you recommend I do that?
ChrisLozeau said:
Thanks. How about Recovery Tools or ROM Manager apps that do this automatically. Would you recommend I do that?
Click to expand...
Click to collapse
hmm.. I think there's recovery or kernel flash tool on playstore. But I'm not sure which as I don't own a s3, you can just follow the instruction properly by downloading the .img, flash it using terminal emulator and you're done
ipromeh said:
hmm.. I think there's recovery or kernel flash tool on playstore. But I'm not sure which as I don't own a s3, you can just follow the instruction properly by downloading the .img, flash it using terminal emulator and you're done
Click to expand...
Click to collapse
I used the Recovery Tools to flash CWM recovery. The S III also resets the recovery to default recovery upon restart, and the app had an option to ensure that doesn't happen. Easy as pie.
I then (for the first time) installed a ROM (S4 Revolution) using the recovery, and that was easy too.
Thanks.
Related
i have had problems with Rom manager not flashing recovery correct leaving me with no recovery. so i had to manually flash recovery following these steps exact. I have personally bricked 2 ERIS phones lucky me.The first i thoought it was just something i did, lucky i had another to replace it...(the second BRICK eris).
So here is a solution to keep from having a BRICK
USE Amon RA's Recovery PERIOD.
credit to northmendo @droidforums
1. download flash_image Here Updated Link 3/17/10
2. Open the terminal and copy and paste the following commands.
adb shell [hit enter]
su [hit enter]
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system [hit enter]
3. In a new terminal window (don't close the original one).
adb push flash_image /system/bin [hit enter]
exit [hit enter]
4. Now in the original terminal window
chmod 755 /system/bin/flash_image [hit enter]
5. Now exit all termainl windows and reboot your phone.
6. Download
Amon_RA's recovery Here.
7. Mount your phones sd card and drop recovery-RA-eris-v1.6.2.img on to it and eject
your phone.
8. Open the Terminal and copy and paste the following commands with the phone connected
to your computer.
8. adb shell [hit enter]
9. su [hit enter]
10. flash_image recovery /sdcard/recovery-RA-eris-v1.6.2.img
11. To get into recovery turn off you phone and hold the Volume Up + Power until it boots into recovery.
That's it.
ROM Manager and Clockwork recovery does not work for the Eris.
ROM Manager and Clockwork recovery does not work for the Eris (as far as I know).
Edit: Oops, sorry for the double post.
I currently have the clockwork recovery installed on my eris, can I just download amon's recovery image and install it to switch to it? Or do I have to uninstall clockwork recovery and then install amon's?
trishuhh said:
I currently have the clockwork recovery installed on my eris, can I just download amon's recovery image and install it to switch to it? Or do I have to uninstall clockwork recovery and then install amon's?
Click to expand...
Click to collapse
try to flash it from rom manager,(under other recoveries) if Rom manager has worked for you with no problems. if it doesnt work follow instructions as listed in 1st post
I wouldn't use clockwork recovery, it messed up my installation to the point i couldn't flash any rom or restore any nand. When i would try to flash anything it would fail, It failed when i tried to use the root rom....After I tried flashing root rom i had a nice looking brick on my desk....(I even changed back to RA but Clockwork had messed up my phone so bad that RA didn't even work either....
YOU HAVE BEEN WARNED!!!!!
Yeah, use Amon's. It does every job you need, and is 100% stable and reliable.
t2noob said:
I wouldn't use clockwork recovery, it messed up my installation to the point i couldn't flash any rom or restore any nand. When i would try to flash anything it would fail, It failed when i tried to use the root rom....After I tried flashing root rom i had a nice looking brick on my desk....(I even changed back to RA but Clockwork had messed up my phone so bad that RA didn't even work either....
YOU HAVE BEEN WARNED!!!!!
Click to expand...
Click to collapse
yea you beat me too it, , i only used it because i had it for my DROID and thought maybe devs would try to add it to the list on rom manager.
ok, obviously a bit of an amateur here, how do you know which recovery image you have, i installed amon's, but i'm not sure if clockwork made it to my phone somehow, thinking about unrooting soon, that's why i ask, thanks.
jrhoades858 said:
ok, obviously a bit of an amateur here, how do you know which recovery image you have, i installed amon's, but i'm not sure if clockwork made it to my phone somehow, thinking about unrooting soon, that's why i ask, thanks.
Click to expand...
Click to collapse
reboot into recovery and read the bottom
Ok Please help a newbie out here im losing my mind. I downloaded flash, plugged phone into mac and set phone to debugging and mounted. Opened terminal from utilities on Mac. When I enter adb shell it says "command not found" if I try using ./ before adb as suggested on another forum for macs when i enter su it asks for password? Any how please help a brother out. Thanks
I flashed amons ras recovery from my phone it was easier for me I didn't use rom manger or terminal emulater
Sent from my FroyoEris using XDA App
Can someone help me get rid of clockwork recovery it showed up after I flashed a rom. How do you flash Amons recovery?
tkryan said:
Can someone help me get rid of clockwork recovery it showed up after I flashed a rom. How do you flash Amons recovery?
Click to expand...
Click to collapse
You do exactly what the first post says
Sent from my Eris
ufccowboyfan said:
Ok Please help a newbie out here im losing my mind. I downloaded flash, plugged phone into mac and set phone to debugging and mounted. Opened terminal from utilities on Mac. When I enter adb shell it says "command not found" if I try using ./ before adb as suggested on another forum for macs when i enter su it asks for password? Any how please help a brother out. Thanks
Click to expand...
Click to collapse
When you are doing this, are you in the correct directory? For example, my SDK is installed in /android , so first I would:
cd /android/tools
then
./adb shell
could someone help me with this. i really need to get the stock recovery image on my eris and im alittle noobie at this stuff. if any one could help id be sooooo happy
I'm not sure how to flash amons on a mac. I know for windows you put the recovery.img in the sdk tools folder, boot into fastboot and type
Fastboot flash recovery recovery.img
To get stock recovery (I assume you want your phone back to stock) then flash the official ruu. Will return your phone to 100% stock. You can find it on a sticky in the Eris general forums I believe.
Sent from my Eris using XDA App
I'm not sure on a mac, but on Windows you put the img in the tools folder of your sdk, boot into fastboot and type in adb:
Fastboot flash recovery recovery.img
To get stock recovery back, simply flash the official ruu found on a sticky in the Eris general forums I believe. Flashing the ruu will unroot your phone.
Sent from my Eris using XDA App
I installed Amon Ra as part of the root for leakers instructions some time ago. -- Is there a new version out? (Search was surprisingly not helpful) And what is the best way to update recovery?
Slugdoc said:
I installed Amon Ra as part of the root for leakers instructions some time ago. -- Is there a new version out? (Search was surprisingly not helpful) And what is the best way to update recovery?
Click to expand...
Click to collapse
There is no new version out; the first version (v1.6.2) is the only one that Amon_RA published.
IF there was a new version, you could flash it by using adb with the existing Amon_RA. You don't even need to push a version of "flash_image" to the phone, because it is already in /sbin in Amon_RA recovery. Just get the recovery image to your SD card, start an interactive shell (adb shell), and then
flash_image recovery /sdcard/<wherever-you-put-it>/recovery-RA-eris-v1.6.2.img
Yes, you can "flash a recovery partition by using the recovery" - because when you are interacting with it (the recovery boot), it lives entirely in a ramdisk.
The second easiest way is to have the engineering bootloader (1.49.2000 S-OFF) installed on your phone, and flash it with fastboot from the PC, as in
fastboot flash recovery recovery-RA-eris-v1.6.2.img
Note that neither of these two methods perform any integrity checks on the recovery image file that the normal "Flash .zip from sdcard" ROM installation method does. Therefore, it is imperative that someone using these methods is extremely diligent in cross-checking image MD5 signatures after it has been transferred to the SD card. Amon_RA also has the "md5sum" utility built into it's shell, BTW.
I mention this last point as a warning to newbs - they seem to routinely corrupt files when they transfer them to the SD card. (I suppose they are not using the "safely remove hardware" controls correctly, or they are getting truncated downloads).
bftb0
Hi geniuses.
From
http://forum.xda-developers.com/showthread.php?t=1034145
G. Flash Custom Recovery:
1) Push recovery-clockwork-5.0.2.6-galaxyace.img to your device using "adb push recovery-clockwork-5.0.2.3-galaxyace.img /tmp/" command
2) Turn off your phone
3) Press POWER+HOME BUTTON
4) Login to your device over "adb shell"
5) Mount /system using "mount /dev/block/stl12 /system" command
6) Flash CWM recovery using "flash_image recoveryonly /tmp/recovery-clockwork-5.0.2.3-galaxyace.img" command
7) Umount /system using "umount /system" command
8) Reboot your device using "reboot recovery" command to test your new CWM recovery
9) Reboot your device
QUESTIONS:
1. Is this the manual way of flashing a custom recovery? Because I think ROM Manager can accomplish the same thing, but I'm a bit wary of it, no offense to the developer.
2. How is 1, 4, 5, and 6 done? Or number 1 at least. How do I "Push recovery-clockwork-5.0.2.6-galaxyace.img to your device" ? Is it done via Odin?
3. I think I've read in The Myth's thread that he suggests cwm4 for his TheMythICS, but why? I have the cwm5.
4. If I back up using nandroid, will it really return EVERYTHING to the way it was? It better, because samfirmware.com does not have DXKPD !
5. Is using nandroid sort of a shortcut to downloading the appropriate firmware in samfirmware.com? If I use nandroid, I don't need to download from samfirmware.com to return to my original stock ROM, correct??
Thanks guys.
thats for cwm 5.0.2.6 which i dont know if can install directly from stock recovery.
i think u better off with cwm 4.0.0.6 which is straighforward for installation. just download, copy zip to root of sdcard, reboot into stock recovery, flash earlier zip and ur done.
http://forum.xda-developers.com/showthread.php?t=1168417&highlight=recovery
1- yes it does displays sga as compatible and u can flash cwm from it, but u had 99% chance of bricking if flashing cwm via rom manager.
3- because 4.0.0.6 is easier to install.
You know,you could just flash cwm the normal way instead of using adb push and cmd..
1.Theres nothing like Manual and Automatic in Android You use what you want..Flash with rom manager and you could get a new phone tomorrow by going to the service centre,that is,if you are under warranty
2.No,its done with cmd..You dont need to do all that,you just need to do a normal flash...Which is,reboot into stock recovery,select install zip from sd card,select the cwm file and then flash
3.Nothing much there..You can flash it via cwm5 too...You are not going to face any probs..I flashed with cwm5,the author himself flashed with cwm5
4.I have got to sixp) words for you,Hell yeah man..Nandroid is awesome
5.WTH???Nandroid is a feature that comes with cwm...How is it related to Odin?
Prawesome said:
2.No,its done with cmd
Click to expand...
Click to collapse
Correction pp I think it is done by adb not cmd.
Sent from my GT-S5830 using xda premium
My son has Samsung Europa. He has locked his phone and cannot remember his password. I have tried to get into recovery to hard reset it but I cannot. I can get into download mode only? I've tried volume up, power, home. Ect. Nothing works.
Can someone tell me the correct procedure please
numbnutsuk said:
My son has Samsung Europa. He has locked his phone and cannot remember his password. I have tried to get into recovery to hard reset it but I cannot. I can get into download mode only? I've tried volume up, power, home. Ect. Nothing works.
Can someone tell me the correct procedure please
Click to expand...
Click to collapse
The europa doesn't have a hardware key combination to get into recovery.
You can use adb to get into recovery.
If you have android sdk installed. Open the command prompt and type "adb reboot recovery" without quotes.
Or you can download any other custom recovery like cwm and flash it in Odin.
Sent from my GT-I9300
Got it, I flashed firmware using Odin working well now. Thanks for pointing me in the right direction
cwm recovery
123shree said:
The europa doesn't have a hardware key combination to get into recovery.
You can use adb to get into recovery.
If you have android sdk installed. Open the command prompt and type "adb reboot recovery" without quotes.
Or you can download any other custom recovery like cwm and flash it in Odin.
Sent from my GT-I9300
Click to expand...
Click to collapse
hello. I flashed CWM recovery with odin..bu how can get now in cwm recovery to install updates or Roms from zip ? Thanks.
lossovidiu said:
hello. I flashed CWM recovery with odin..bu how can get now in cwm recovery to install updates or Roms from zip ? Thanks.
Click to expand...
Click to collapse
If you flash cwm recovery us using odin it automatically boots into recovery.
If your on cyanogenmod or any other cm derived rom it'll have an option to reboot into recovery in the power menu.
Sent from my GT-I9300 using xda app-developers app
cwm
10x for replying. but everytime when i want to go to recovery i must flash with odin ??
lossovidiu said:
10x for replying. but everytime when i want to go to recovery i must flash with odin ??
Click to expand...
Click to collapse
If you want to reboot recovery from a stock rom or any rom with no recovery reboot option just root the phone and install the terminal app. Then open the terminal and type the following:
su (then hit enter/return on keyboard to get superuser)
reboot recovery (type that and hit enter/return again and the phone will reboot into recovery)
thanks
10x a bunch. you saved me thanks again everyone.
Well im writing this tutorial because I myself ran into this problem.... I download the latest TWRP 2.5.0.0 and it broke while using aroma. Never happen on 2.4.4.0.. But anyways I flashed a test kernel through recovery and it kept freezing my phone and so I tryed flashing my pizzuto Rom and it broke. And I have no computer at the moment, So this tutorial is for people who are on the go and have no computer access. Or backup.
LIKE I SAID THIS IS FOR PEOPLE ON THE GO THAT DON'T HAVE COMPUTER ACCESS AND DON'T HAVE NANDROID BACKUPS. AND FOR PEOPLE WHO FLASHED TWRP 2.5.0.0 ON THE GO.
Requirements:
1. A Rom that doesn't use aroma to install.
2. Android terminal
3. TWRP 2.3.3.0 image
HOW TO DO IT:
1. Download or Install Android Terminal, And Open It
Code:
su
2.
Code:
flash_image recovery /path/to/recovery.img
^^^ And I Believe Same Can Apply Boot.img ^^^
But only like this:
Code:
flash_image boot /path/to/boot.img
24ky said:
Code:
Type " su "
Click to expand...
Click to collapse
When you encapsulate text in [ CODE ] tags, do not write Type or include quotation marks if they aren't meant to be included in the terminal command. This should simply say:
Code:
su
Adjust your other code encapsulations as well.
24ky said:
Code:
Type " flash_image recovery /path/to/were/recovery.img/is
Click to expand...
Click to collapse
/path/to/were/recovery.img/is is a terrible path example. Either use /path/to/recovery.img or give a legitimate example /sdcard/recovery.img.
Maze has finally published the Alpha Stock-Rom.
Download Link: https://goo.gl/9kCJiv :fingers-crossed:
The system.img file is incorrectly downloaded as a system 002.img file. It must be renamed. And then copy it to the folder "3. Maze_Alpha_V05_20170816 Official ROM".
Thanks!
Hope anyone can root this phone.
Hi!
I am in need of a new phone, and this one looks quite good at the price.. But what do you think can i expect from custom ROM scene here for it? I am a Xiaomi Fan, and my Mi4 was and is one of the best supported phones still. Do you think there will be a subforum for this device, custom ROMs (preferreable Lineage OS, or other close to AOSP ROMs? OFC nobody can know now, i understand, but what tells your experience of other new phones from new companys? It has created quite a buzz, so i think there will be a demand for sure..
Just am 2 afraid to get a phone without good custom ROM. Never had an Android in last 5 years with stock ROM. Total nightmare for me now to have to go back.
Root + TWRP 3.2.1
3 Methods to root MAZE Alpha
Note: Method II is the most universal and must works with almost any official ROM
I- Method 1 : flashing modified Magisk boot.img
1. make sure to have already installed the version 20170816
2. reboot the phone in fastboot mode (phone off -> Vol Up + Power or "adb reboot bootloader")
3. unlock the bootloader if not already done : fastboot flashing unlock (if not works, in android development setting set the unlock bootloader and then retry)
4. unzip and then flash the attached boot image : fastboot flash boot new-boot.img
5. reboot your phone: fastboot reboot
6. install the MagiskManager apk v14
7. Voila
I have used this Magisk guide to create it
I used old manual guide :
Code:
adb shell "rm -rf /data/local/tmp/*"
adb push META-INF/com/google/android/update-binary common magisk_inject boot.img /data/local/tmp
adb shell "cd /data/local/tmp/magisk_inject; mv ../common/* .; chmod 755 *; sh ../update-binary indep boot_patch.sh ../boot.img; mv ../bin/busybox busybox"
adb pull /data/local/tmp/magisk_inject/new-boot.img
adb shell "rm -rf /data/local/tmp/*"
II- Method 2 : using TWRP and Magisk.zip (External SDCARD or USB OTG cable needed)
1. reboot int bootloader mode : adb reboot bootloader
2. unzip and flash the the attached TWRP recovery : fastboot flash recovery recovery_maze_alpha_4G_twrp-321.img
3. In TWRP choose first "change language" then press the "cancel" button while asking you for decryption password for data
4. In your PC download the Magisk-v15.3.zip and put it in a USB key, or an SDCARD
5. Use an usb otg cable to connect the USB key to your phone running TWRP and install the Magisk-v14.zip from Usb-otg (or SDCARD)
6. bonus: do a complete backup of your phone : all partitions except cache and data to your Usb-otg (or SDCARD)
7. reboot and install the MagiskManager apk v14
III- Method 3 : using the phhusson modified boot image
1- flash the attached boot image, using fasboot (fastboot flash boot boot-super-bootimg-output-su-eng-r318.img) or SPFlashTools using the attached scatter, if you do not want to unlock your bootloader
2- reboot to Android then install from google play the phhsusson superuser
3- Voila
Important Notes:
1- In all case you can use SPFlashTools to flash boot image without unlocking bootloader.
2- windows SPFlashTools users : phone off, press VOL+ and connect it to your PC (running SPFlashTool and waiting for phone connetion)
3- linux SPFlashTools users : phone off and connected to PC , press VOL+ and POWER while your PC is running SPFlashTool (with sudo) and waiting for phone connetion.
Some useful tips
1- manual install of busybox :
a- root you phone with method II if not already done
b- stay in TWRP (or boot TWRP as in method II) then in advance->sideload slide the slider to confirm and after cancel that (we will not sideloading any thing, just to activate adb)
c- unzip and copy the attached busybox : adb push busybox /external_sd/
d- mount the system partition with the TWRP mount button
e- copy the busybox binary to /system/xbin : adb shell --> cp /external_sd/busybox /system/xbin/
f- make executable busybox and create links (the point at the end is a part of the command) : cd /system/xbin/; chmod 755 busybox; ./busybox --install -s .
g- umount the system partition in TWRP and reboot
2- manually install the OTA update.zip :
a- Google and download those 3 tools BlockImageUpdate, simg2img and img2simg.
b- In a terminal of your Linux PC do :
Code:
simg2img system.img system.raw.img # convert the sparse image to a normal raw (ext4) image
BlockImageUpdate system.raw.img system.transfer.list system.new.dat system.patch.dat # patch the newly created raw image
img2simg system.raw.img system.img # convert the patched raw image to a flashable sparse image
- system.img: you old system image (from 20170816 official rom)
- system.transfer.list, system.new.dat and system.patch.dat : inside the OTA update.zip
c- After that the original system.img will be patched and you will have an updated system.img.
d- Flash this patched system.img and also all .bin and .img files inside the update.zip (just replace old ones in the original 20170816 rom by those) and you will have the new official rom
3- Using supersu as root manager :
The last update at this time of supersu zip (2.82 SR5) works well, even it cannot update the su binary.
Credits to Magisk Devs, Phhusson and Jemmini
dreambo said:
Here how to root this phone.
1. make sure to have already installed the version 20170816
2. reboot the phone in fastboot mode (phone off -> Vol Up + Power or "adb reboot bootloader")
3. unlock the bootloader if not already done : fastboot flashing unlock (if not works, in android development setting set the unlock bootloader and then retry)
4. unzip and then flash the attached boot image : fastboot flash boot new-boot.img
5. reboot your phone: fastboot reboot
6. install the MagiskManager apk v13.6
7. Voila
I have used this Magisk guide to create it
Credits to Magisk Devs.
Click to expand...
Click to collapse
If I root my phone with this method, will I get further OTA Updates from Maze?
Following to see where this goes.
Cheers
CrashCrash123 said:
If I root my phone with this method, will I get further OTA Updates from Maze?
Click to expand...
Click to collapse
Yes.
You will only lost the root.
If the new update have the same kernel, the same methode with the same boot image can be used to root it again, othewise, we can follow the Magisk guide to create a new one.
I have tried this method. But it only works until the reboot. Then the root access is gone again.
SomeOneX said:
I have tried this method. But it only works until the reboot. Then the root access is gone again.
Click to expand...
Click to collapse
The root is permanent.
If you lost it, perhaps the first time we unlock the bootloader, the phone do a reset, and we lost the root (I suppose).
Just re-flash the new boot again, and it will be permanent : fastboot flash boot new-boot.img
Hi . I have locked the OEM lock but I can not install it through fastboot (remote: not allowed in lock state)
can we expect VOLTE on this device ?
and is there any chance of custom rom development for this device?
alfymon22 said:
can we expect VOLTE on this device ?
and is there any chance of custom rom development for this device?
Click to expand...
Click to collapse
It seems (take with a pinch of salt) that VoLTE is supported, but then most sites that announce that also make mistakes on other specs, so...)
As for custom ROMs, so far the square root of bugger all, but the consumer phones are just filtering in, so give it time.
dreambo said:
Here how to root this phone.
1. make sure to have already installed the version 20170816
2. reboot the phone in fastboot mode (phone off -> Vol Up + Power or "adb reboot bootloader")
3. unlock the bootloader if not already done : fastboot flashing unlock (if not works, in android development setting set the unlock bootloader and then retry)
4. unzip and then flash the attached boot image : fastboot flash boot new-boot.img
5. reboot your phone: fastboot reboot
6. install the MagiskManager apk v13.6
7. Voila
I have used this Magisk guide to create it
Credits to Magisk Devs.
Click to expand...
Click to collapse
it worked, but i have cts fail on safetynet check. how you fixed this?
PrimateaEu said:
it worked, but i have cts fail on safetynet check. how you fixed this?
Click to expand...
Click to collapse
install the universal safety net fix
Hey guys, does this root method wipe the data partition?
KilljoyTDA said:
Hey guys, does this root method wipe the data partition?
Click to expand...
Click to collapse
The flash of the boot image does not wipe the data, but unlocking the bootloader reset the phone and wipe the data.
If you phone is already unlocked, you will not loss the data, otherwise do a backup before.
Well, I don't remember unlocking it, unless Kingo's windows app does it without telling even when rooting fails, so I guess I'd better back up.
Thanks for the info
KilljoyTDA said:
Well, I don't remember unlocking it, unless Kingo's windows app does it without telling even when rooting fails, so I guess I'd better back up.
Thanks for the info
Click to expand...
Click to collapse
It is easy to know if your phone is locked or not : enter fastboot mode and then do : "fastboot getvar all".
Read the last lines of the output and you will know.
Thank you @dreambo for this method, but for me "fastboot flashing unlock" not work, "fastboot oem unlock" working for me, all ok
ps:excusez moi pour mon anglais
dreambo said:
It is easy to know if your phone is locked or not : enter fastboot mode and then do : "fastboot getvar all".
Read the last lines of the output and you will know.
Click to expand...
Click to collapse
Well I failed to back up for some reason anyways, so since I had almost nothing vital on the internal memory, I rooted (sucessfully) and now I'm reinstalling/reconfiguring my apps. Thanks anyways