Hey, I'm french so if I do mistake, it's normal, sorry
Here is a way to root this Wiko, finally!
Before doing this, i want to say that me, XDA or nobody exept you is responsible of what you can do on your phone, this method work for me, surely for you, but this operation will delete all your data, so remember to backup your data.
Now, you Have to go to Developper options, enable "OEM Unlocking", "USB Debugging" and disable "Verify apps over USB"
After, set "Select USB Configuration" to MTP. After That, download file (https://mega.nz/#!ioBQDZra!z6ntj85aM-mjg4dnscPaPBjvd-qpSY9HQiDkKuYbxcU) and extract it
Connect your phone to your Computer, Copy and Paste the SuperSU zip file in your SD card, and reboot your phone in fastboot mode (shutdown, and boot it by pressing Power and Vol+, then, when you have a choice between recovery and fastboot, select fastboot by clicking Vol-)
Open a command prompt in the extracted file, and type: fastboot oem unlock
Here, all your data will be lost by a factory reset.
When the phone restart, in the command prompt, type:
adb root
adb shell
cat /proc/partitions
ls -l /dev/block/platform/soc/7825900.sdhci/by-name/ (7825900.sdhci may be different, so use tab to find the correct file)
in the list, you will have a file with "recovery -> /dev/block/XXX" (XXX may be like mmcblk0p22)
cat /dev/block/XXX > /data/local/tmp/recovery.img
exit
adb pull /data/local/tmp/recovery.img
adb reboot-bootloader
fastboot flash recovery "CUSTOM recovery.img"
fastboot reboot
if there is no problems, you phone restart normally, so stop it, and boot to the recovery (Power and Vol+ and whene the choice appear, Select recovery with Vol+)
if your phone don't want to boot to the TWRP recovery, try to flash the stock recovery, reboot and flash again the custom one. if the problem persist, leave a comment.
In TWRP, swipe the button, and go to Install, Up a level, select external_sd and then, select the SuperSU file, select "Reboot after installation is complete, and swipe to flash.
When it's done, install or not the TWRP app, and reboot. The device can start twice before finally boot, and can be longer than usual, but don't do anything, it's normal.
When the phone finally boot, SuperSU may be installed, so go check if it's true, and if it is, go to the play store and install BusyBox (by Stephen (Stericson))
After the installation is complete, open it, and click install.
If there is no problem, the root acces will be request, so accept it and all is done.
If you have a problem, or any question, ask me.
Anyone a idea how to root a Wiko View 3 Lite?
give me the link, pls
greenverdy said:
give me the link, pls
Click to expand...
Click to collapse
Ok
Root Wiko View
Hi,
Can you send the link for rooting Wiko view.
Thanks in advance.
give me the link Please.
can you send me the link as well?
Please if someone has the package already, kindly posted it on the forum.
zerking said:
can you send me the link as well?
Please if someone has the package already, kindly posted it on the forum.
Click to expand...
Click to collapse
Ok, no problem
thank you for the link. I got both TWRP and SU installed but the device is not rooted? How can it be?
zerking said:
thank you for the link. I got both TWRP and SU installed but the device is not rooted? How can it be?
Click to expand...
Click to collapse
Do you have an error message ? Or something else ?
Oh, well, it figured my way out! First SU installation, the phone isn't rooted (I don't know why, either). But I factory reset the phone, set the phone up, then go to TWRP and re-install SU and it worked. Now the phone is rooted!
Thank you very much for your guide and files.
By the way, I guess most people will get stuck at "adb root" command.
Simply dial *#*#84666364#*#* (this launches TinnoEngineerMode)
- go to "Tinno Debug Feature"
- tap on "persist.tinno.debug" and choose 1
Then you can go on with "adb root" command
Hope this helps!
zerking said:
Oh, well, it figured my way out! First SU installation, the phone isn't rooted (I don't know why, either). But I factory reset the phone, set the phone up, then go to TWRP and re-install SU and it worked. Now the phone is rooted!
Thank you very much for your guide and files.
By the way, I guess most people will get stuck at "adb root" command.
Simply dial *#*#84666364#*#* (this launches TinnoEngineerMode)
- go to "Tinno Debug Feature"
- tap on "persist.tinno.debug" and choose 1
Then you can go on with "adb root" command
Hope this helps!
Click to expand...
Click to collapse
It's a good think to say it, because it don't work without dialing this number. Thanks
zerking said:
Oh, well, it figured my way out! First SU installation, the phone isn't rooted (I don't know why, either). But I factory reset the phone, set the phone up, then go to TWRP and re-install SU and it worked. Now the phone is rooted!
Thank you very much for your guide and files.
By the way, I guess most people will get stuck at "adb root" command.
Simply dial *#*#84666364#*#* (this launches TinnoEngineerMode)
- go to "Tinno Debug Feature"
- tap on "persist.tinno.debug" and choose 1
Then you can go on with "adb root" command
Hope this helps!
Click to expand...
Click to collapse
On latest wiko view update, tinoo debug feature was gone, we can't use adb root again after update
guys where i can download official rom for the wiko view 2 and extract?
ola and in french plz ?
don´t work on my wiko view 32GB
please help me to root my wiko view 32gb+3gb. i place fastboot oem unlock in pront comand i see waiting for device, and nothing. please creat a apk our anything for root
Would it work on k-Kool ?
We'll this sounds horrifying, just to get root permission, you have to accept to get rid of all your data and parms ? It must be another way.
I'll explain my real need for rooting my Wiko k-Kool. I bought a 64GB SD card, to be used normally as external storage, not for apps install. However I want to be able to backup my phone onto that card, just in case. I use Helium to backup my data without needing root (uses internally adb) ! However non-rooted Helium as a 3d party application has no permission to write to the SD card ! The reason I want to root is just to give Helium the permission to wirte into a backup directory.
Therefore I dont want to put my data at risk just to get root permission, but found no other way to change heliums permissions.
Thanks for any help.
This can work for the Wiko view 2 ? I can't find anything for my phone [emoji24]
Envoyé de mon W_C800 en utilisant Tapatalk
Can this work for view 2?
This work forse Wiko view max?
nothing for wiko view go?
Hello
Is there anyone who did root the wiko view go hier please?
Related
Hello. This is my 2nd post after here. I hope this will not bother anybody.
I have a situation. I did root my TF201 using CWM and virtuous_prime_s_9.4.2.21_v1 a month ago. Just now, I plan to sell my TF201. So, I go to the tablet setting and click at the reset data or something like that. I think it's just a normal data deletion process which is not effecting the rooted system. Unfortunately, after I reset / delete the data, the tablet is not going to boot. It just keep showing the CWM Recovery page with options to reboot the system, install zip from sdcard, wipe data, and so on. I selects to reboot the system, but nothing is happening. The tablet is turned off and turned back on with same display (CWM Recovery page).
What should i do?
titanbullet said:
Hello. This is my 2nd post after here. I hope this will not bother anybody.
I have a situation. I did root my TF201 using CWM and virtuous_prime_s_9.4.2.21_v1 a month ago. Just now, I plan to sell my TF201. So, I go to the tablet setting and click at the reset data or something like that. I think it's just a normal data deletion process which is not effecting the rooted system. Unfortunately, after I reset / delete the data, the tablet is not going to boot. It just keep showing the CWM Recovery page with options to reboot the system, install zip from sdcard, wipe data, and so on. I selects to reboot the system, but nothing is happening. The tablet is turned off and turned back on with same display (CWM Recovery page).
What should i do?
Click to expand...
Click to collapse
If you still have the virtuous prime file on there just.go to install zip and select it then reflash and youl be good to go. If not then you need to search on here for a program called knives and forks which is the easy way to install adb android debug bridge once installed download virtuous prime zip and place it in the same Rwhere you just installed adb then make sure you are in the cmw main screen and type adb push (filename) this will send the to tablet it may take up to 10 minutes and will just show a flashing cursor . Then flash.as normal. Sorry for spelling mistakes typing.g this on my phone and its being stupid
Uberjim said:
If you still have the virtuous prime file on there just.go to install zip and select it then reflash and youl be good to go. If not then you need to search on here for a program called knives and forks which is the easy way to install adb android debug bridge once installed download virtuous prime zip and place it in the same Rwhere you just installed adb then make sure you are in the cmw main screen and type adb push (filename) this will send the to tablet it may take up to 10 minutes and will just show a flashing cursor . Then flash.as normal. Sorry for spelling mistakes typing.g this on my phone and its being stupid
Click to expand...
Click to collapse
Thanks for the reply. I appreciate the info given. Will try to use the tool now since the rom file is no longer saved in the tablet.
Will update soon.
Thanks.
I'm just done installing the Knivesandforks on my win7. After that, the system automatically install the phyton. I dont know what its function, but as i follow this steps, i get error with cmd which shown as below:
Code:
c:\users\pc>adb reboot
error: device not found
i think i didn't miss any steps. Anybody here could help me with this?
Thanks in advance.
* my tablet is still in cmw main page and not showing anything even has been connected to the PC. i think that's the reason why the error occurs - device not found. anybody who could give some ideas on this will much appreciated.
You may need the fast boot drivers I wasn't sure if you would with being in cmw download those and extract them to the same folder as adb then load it up by using shift right mouse click run command and type and type adb devices if it shows up your good to go try the above steps again
titanbullet said:
Hello. This is my 2nd post after here. I hope this will not bother anybody.
I have a situation. I did root my TF201 using CWM and virtuous_prime_s_9.4.2.21_v1 a month ago. Just now, I plan to sell my TF201. So, I go to the tablet setting and click at the reset data or something like that. I think it's just a normal data deletion process which is not effecting the rooted system. Unfortunately, after I reset / delete the data, the tablet is not going to boot. It just keep showing the CWM Recovery page with options to reboot the system, install zip from sdcard, wipe data, and so on. I selects to reboot the system, but nothing is happening. The tablet is turned off and turned back on with same display (CWM Recovery page).
What should i do?
Click to expand...
Click to collapse
Recovery bootloop, see here, option 1a: http://forum.xda-developers.com/showthread.php?t=1514088
Use only Universal Naked Drivers (see related thread).
Sometimes even with proper drivers adb is a mess, then uninstall adb and search the net for a ready to use adb, there are some easy to find.
Uberjim said:
You may need the fast boot drivers I wasn't sure if you would with being in cmw download those and extract them to the same folder as adb then load it up by using shift right mouse click run command and type and type adb devices if it shows up your good to go try the above steps again
Click to expand...
Click to collapse
i did those steps again, but it seems like not helping. the script is only rebooting the tablet instead of giving me the option to flash the rom. i don't know if i did wrong. but as i know, i did as posted here.
* frust to see the cmw recovery for the whole day
Striatum_bdr said:
Recovery bootloop, see here, option 1a: http://forum.xda-developers.com/showthread.php?t=1514088
Use only Universal Naked Drivers (see related thread).
Sometimes even with proper drivers adb is a mess, then uninstall adb and search the net for a ready to use adb, there are some easy to find.
Click to expand...
Click to collapse
i did follow this tutorial
at first, install universal naked drivers - done
Now do the following:
Make sure your Prime is in Recovery mode (CWM) - YES
Open a cmd line on your pc - DONE
Type: "adb shell" - DONE
You should see a "#" now - YES
Once you have that "#", please type: dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1 and press [Enter] - Ok. This part was very difficult. I see the "#" but to type all those command, I can't. Why? Because the line in cmd instantly extended to a new line of command. I mean it just like I press the ENTER button. So, the line move to below and i can't finish typing all those command.
Now type: dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1 and press [Enter]
Exit the shell and reboot your Prime via CWM
It should not reboot to CWM automatically now. It either boots your ROM or is stuck at the splash screen. If it is stuck, boot to recovery and install any ROM you want.
Click to expand...
Click to collapse
titanbullet said:
i did follow this tutorial
at first, install universal naked drivers - done
Click to expand...
Click to collapse
Very strange, try to expand your command line window first. It doesn't matter if the text goes on following line, as long as you don't press Enter it's considerd as the same line. Try copy/paste instead ot typing.
Striatum_bdr said:
Very strange, try to expand your command line window first. It doesn't matter if the text goes on following line, as long as you don't press Enter it's considerd as the same line. Try copy/paste instead ot typing.
Click to expand...
Click to collapse
this is my first time, so i don't know if that was strange. ha ha. well, it's not about the command line which is extended or not. but the line itself creating a new line, as i said - just like i press the ENTER button.
i try to use copy-paste function (ctrl + c and ctrl + v). but i don't think it functions in cmd.
please help..
[Solved]
What i do?
I follow this step again
Installing the ADB again
And the most important thing is, pushing ROM into /sdcard should be like this:
Code:
adb push rom.zip /sdcard/rom.zip
And right-click copy paste function solving my strange cmd
Then i just follow the steps by installing the zipped rom thru cwm when my screen did not stuck at splash screens
Thanks for your kindness
My TF is now back to normal
THANKS!
Hello, how to root Op3n Dott P4502 ?
I tested some programs on google play and on my pc, and it can't root my mobile
Can someone help me with root ?
Thanks.
@refresh
I too need this, pls answer.
1. Download and install apk from google play "MTK Engineering Mode"
2. In this apk "MTK Settings->Log and Debugging->User2Root" push "Root" button and exit apk.
3. Switch on "Debugging Mode" in phone:
-open up Settings, then scroll all the way down to About phone. Once there, tap Software information, then tap Build number seven times. You'll see a toast notification alerting you that you are now a developer.
- go back to the main Settings page and you'll see a new entry for Developer options. In this menu check USB debugging
4. Download and install this program iRoot, (download with IE beacuse firefox see dangerous file)
5. Run iRoot and connect phone to PC
6. Choose "Connect" and then "Root"
7. Unistall 2 chineese aplication, and install "Supersu" from google play (after restart update "supersu")
8. You have root.
I use chineese supersu beacuse this from google play have problem with permission to sdcard.
-----
Recovery Instalation:
1. Download recovery and copy it to /data/local/temp (change filename to recovery.img)
2. Installanr run Terminal emulator.
3. type:
su
dd if=/data/local/tmp/recovery.img of=/dev/recovery
4. Now reboot to recovery and make backup.
-----
Link to hungary forum Link
Thank you very much!
Rom for Medion p4502
I do the same but the phone is block in a boot loop.
When i start with the button "on" and "volume Up", i have a special screen with "No command" writed.
Then using the buttons under the screen i have a menu seems to a cm recovery.
Is there a rom for this phone ? the Medion p4502 ?
What you do , Root or CWM? I have Op3n Dott but this the same phone like medion p4502.
Dromadore said:
I do the same but the phone is block in a boot loop.
When i start with the button "on" and "volume Up", i have a special screen with "No command" writed.
Then using the buttons under the screen i have a menu seems to a cm recovery.
Is there a rom for this phone ? the Medion p4502 ?
Click to expand...
Click to collapse
-- i finaly passed the capchat so i'll edit this post with the right username --
shanti77 said:
What you do , Root or CWM? I have Op3n Dott but this the same phone like medion p4502.
Click to expand...
Click to collapse
Good morning,
I think i just need a ROM or a Backup.
I installed the systel recivert TWRP with flash tool, it works but missing the OS.
With flash tool:
I used those files: logo.bin, lk.bin, MBR, preloader.bin, secro.img, MT6582_Android_scatter.txt, boot.img, recovery.img, system.img
But i didn't have any files for: ebr1, ebr2, cache, usrdata
A the TWRP seems to work, i think i can simply flash a zip file on the SD-card.
Thank you four your interest !
ps: I was invited to type the captcha and it was very very very very difficult to read (i tried more than 20x).
Firmware ver213 link
shanti77 said:
1. Download and install apk from google play "MTK Engineering Mode"
2. In this apk "MTK Settings->Log and Debugging->User2Root" push "Root" button and exit apk.
3. Switch on "Debugging Mode" in phone:
-open up Settings, then scroll all the way down to About phone. Once there, tap Software information, then tap Build number seven times. You'll see a toast notification alerting you that you are now a developer.
- go back to the main Settings page and you'll see a new entry for Developer options. In this menu check USB debugging
4. Download and install this program iRoot, (download with IE beacuse firefox see dangerous file)
5. Run iRoot and connect phone to PC
6. Choose "Connect" and then "Root"
7. Unistall 2 chineese aplication, and install "Supersu" from google play (after restart update "supersu")
8. You have root.
I use chineese supersu beacuse this from google play have problem with permission to sdcard.
Click to expand...
Click to collapse
Thank you for excellent post! I managed to root my Medion P4502 using your instructions but substituted iRoot with Kingo Root. Here is the link with necessary steps.
shanti77 said:
Firmware ver213
Click to expand...
Click to collapse
*removed link because not passed limit yet*
Hey shanti, I too have been stupid and managed to remove my system. I was trying to navigate TWRP (so much more used to CWM with previous devices) and accidentally erased the system instead of backing it up. Is it possible to flash this with fastboot? I did managed to back up the boot files, just not the system, and I don't have a external SD card (I might be able to swap the one off my mums phone though at some point).
Thanks
Will
PS. If it helps, I use Arch Linux (32 bit) because my laptop chargers broken I'm using my spare PC, and also the phone is the Medion variant (LIFE P4502 from Aldi)
EDIT: Buying SD Card today
Can somebody help me to make cm11 port? Thanks
Were can i find chinese supersu? I instaled from google but really have problemy with SD, lost settings after reboot, and other problems
shanti77 said:
Firmware ver213 link
Click to expand...
Click to collapse
Hello,
Is this Original firmware, and how to do it?
Thanks for helping me.
Still need original ROM for Medion P4502
Can someone tell me where and how to recover my phone?
It doesn't connect to my network provider (I tested 3 differents Sim cards), and he also change his MAC address at WIFI connection.
I need original ROM and how to put it back (how to do).
Please help me as I don't want to send it back to Medion service (3th time), as they didn't do anything.
A friend has the same phone.
Is it possible to make a copy of his ROM (and how) to put it back on mine?
Thanks for helping me.
No answer, so phone send back to Medion repair service.
Hope this time it will return in good conditions ...
Please help!
Dromadore said:
I do the same but the phone is block in a boot loop.
When i start with the button "on" and "volume Up", i have a special screen with "No command" writed.
Then using the buttons under the screen i have a menu seems to a cm recovery.
Is there a rom for this phone ? the Medion p4502 ?
Click to expand...
Click to collapse
Hi Dromadore,
Did you end up to fix you bootloop issue? Can you please share your findings with me as I am desperately looking for a solution?
Cheers,
So I recently pulled my G Watch back out and installed the most recent OTA 6.0.1, installed TWRP, the custom kernel, and rooted it. Obviously all of that required ADB to function correctly. It did perfectly. I installed ADB using the 15 Second ADB Installer, and used WinDroid Toolkit to flash TWRP and get into recovery and do the rest, that by default installed the ClockworkMod ADB drivers, all of this on my Windows 10 PC.
Those drivers worked perfectly. Until today.
I did a fresh install of CM13 on my Nexus 5 phone, which my watch was paired to at the time. I wiped everything and started over, so I then went into my watches settings and did the Factory Reset so I could start fresh and resync up with my new rom install on my phone.
But when I try to connect via ADB or even try to list the devices it always states "Unauthorized"...
For whatever reason, no matter what I try it wont bring up the prompt on my phone to authorize this computer.
I revoked Debug permissions on both my watch and my phone, tried different usb ports, turned off and on debugging in all its forms on both my watch and phone, plus restarted all my devices and my PC. I have tried google's adb drivers as well.
Not sure what else there is to possibly try, seems I have covered all my bases here. Just doesn't make sense that it worked and now all the sudden it doesn't...
Glad I'm not the only one having this problem! I've tried same exact methods you mentioned with no luck. Hopefully someone knows what's going on here and provide a solution
Maybe deleting the keys in the computer will fix it. If it works with another computer, then it's the solution. On Mac, they are stored in a folder called .android in the home folder, if I recall correctly. Anyway it should be easy to find online how to delete the keys in the OS you're using.
What I did was first authorise my phone to my pc's adb then I copied adb_keys from /data/misc/adb/ on my phone to my pc. I then copied that while in TWRP on my LG G watch to the same directory /data/misc/adb/ and rebooted to system and voila adb access restored!
Thanks for your suggestions guys, but I officially give up figuring this out. Tried other computers and it still says "unauthorized." Tried both Windows 10 and Ubuntu and still the same error. Some thing's definitely happened since Wear 6.0 update or maybe invisible kernel for 6.0?
@Xmaster24 I would try your TWRP way, but I never installed it as I didn't see the need for it. I don't think there's a way to install it now without ADB, is there?
xymic said:
Thanks for your suggestions guys, but I officially give up figuring this out. Tried other computers and it still says "unauthorized." Tried both Windows 10 and Ubuntu and still the same error. Some thing's definitely happened since Wear 6.0 update or maybe invisible kernel for 6.0?
@Xmaster24 I would try your TWRP way, but I never installed it as I didn't see the need for it. I don't think there's a way to install it now without ADB, is there?
Click to expand...
Click to collapse
adb is absolutely not required. seeing as you are running 6.0.1 get the custom TWRP from my root guide here and follow the instructions on flashing the recovery. Seeing as you don't have adb you will just have to power off your watch and boot it up and swipe top left to bottom right as soon as you see something
Xmaster24 said:
adb is absolutely not required. seeing as you are running 6.0.1 get the custom TWRP from my root guide here and follow the instructions on flashing the recovery. Seeing as you don't have adb you will just have to power off your watch and boot it up and swipe top left to bottom right as soon as you see something
Click to expand...
Click to collapse
Aaaaaand we're back, Houston! Thanks a lot man. Works great now.
Hello
I have the same problem as author of this thread. How can I get authorize adb? I need it to push some files to internal memory.
I suffer the same problem.
Ok, I found solove for this problem. Just what you need is back to stock for example by this method: http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863 or manually("fastboot flash" command): http://forum.xda-developers.com/g-watch/development/how-to-to-stock-rooted-6-0-t3339875 If you will have bootloop, you need to factory reset in twrp and reboot. To boot into twrp when you have bootloop you must enter to bootloader mode and write in cmd "fastboot boot YourTwrpName.img" command. I used twrp from this topic: http://forum.xda-developers.com/g-watch/development/guide-how-to-root-lg-g-watch-6-0-1-t3320512 After all you can update your watch to actual android wear version and again root/ change kernel.
Sorry for my bad english. I am not native speaker.
koszanty said:
Ok, I found solove for this problem. Just what you need is back to stock for example by this method: http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863 or manually("fastboot flash" command): http://forum.xda-developers.com/g-watch/development/how-to-to-stock-rooted-6-0-t3339875 If you will have bootloop, you need to factory reset in twrp and reboot. To boot into twrp when you have bootloop you must enter to bootloader mode and write in cmd "fastboot boot YourTwrpName.img" command. I used twrp from this topic: http://forum.xda-developers.com/g-watch/development/guide-how-to-root-lg-g-watch-6-0-1-t3320512 After all you can update your watch to actual android wear version and again root/ change kernel.
Sorry for my bad english. I am not native speaker.
Click to expand...
Click to collapse
Sorry, but, with ADB in "unauthorized" state it can't be done.
Guys, read Xmaster24's posts in first page. That's how I fixed it.
turbomann said:
Sorry, but, with ADB in "unauthorized" state it can't be done.
Click to expand...
Click to collapse
Why? Fastboot is diffrent thing than adb and it should work without 'adb authorization'. I used this method and it worked for me.
xymic said:
Guys, read Xmaster24's posts in first page. That's how I fixed it.
Click to expand...
Click to collapse
If you don't have copy of adb keys on watch sdcard, probably you cant use his fix(or am I wrong?). By the way, how can I mange files in TWRP mode without working adb? In TWRP is special option/ command for mange files by PC or something like that? If I connect watch to PC I can't see it as mass storage.
koszanty said:
Why? Fastboot is diffrent thing than adb and it should work without 'adb authorization'. I used this method and it worked for me.
If you don't have copy of adb keys on watch sdcard, probably you cant use his fix(or am I wrong?). By the way, how can I mange files in TWRP mode without working adb? In TWRP is special option/ command for mange files by PC or something like that? If I connect watch to PC I can't see it as mass storage.
Click to expand...
Click to collapse
You had flash 5.1.1 and then upgrade to 6.0.1? Are there bootloader compatible?
koszanty said:
If you don't have copy of adb keys on watch sdcard, probably you cant use his fix(or am I wrong?). By the way, how can I mange files in TWRP mode without working adb? In TWRP is special option/ command for mange files by PC or something like that? If I connect watch to PC I can't see it as mass storage.
Click to expand...
Click to collapse
You only need to have adb_keys file on the phone not the watch. In my case, I was able to use adb perfectly fine while I was in TWRP. Basically here's what I did:
1. Copy adb_keys file from your phone to computer. It is located in /data/misc/adb. If you can't see the file, you probably have to authorize your phone first with your computer.
2. Flash TWRP recovery from XMaster24's link using fastboot on your watch.
3. Boot into recovery. You don't need go into any options. While on the recovery homescreen, Just use this command to transfer adb_keys file into your watch:
Code:
adb push adb_keys /data/misc/adb
You can check using "Files" option in recovery to see if the file is transferred into the watch.
4. Reboot your watch and you should be able to access adb now.
You can do it your way as well, but using xmaster24's method saves time, I think
xymic said:
You only need to have adb_keys file on the phone not the watch. In my case, I was able to use adb perfectly fine while I was in TWRP. Basically here's what I did:
1. Copy adb_keys file from your phone to computer. It is located in /data/misc/adb. If you can't see the file, you probably have to authorize your phone first with your computer.
2. Flash TWRP recovery from XMaster24's link using fastboot on your watch.
3. Boot into recovery. You don't need go into any options. While on the recovery homescreen, Just use this command to transfer adb_keys file into your watch:
Code:
adb push adb_keys /data/misc/adb
You can check using "Files" option in recovery to see if the file is transferred into the watch.
4. Reboot your watch and you should be able to access adb now.
You can do it your way as well, but using xmaster24's method saves time, I think
Click to expand...
Click to collapse
In my case adb doesn't worked at all
turbomann said:
You had flash 5.1.1 and then upgrade to 6.0.1? Are there bootloader compatible?
Click to expand...
Click to collapse
It's compatibile but can occur bootloop. If you will have bootloop, you must do that what I write some posts earlier.
I'm realised that my phone with MM do the same bug, unauthorized, I look for adb_keys file but folder ADB is empty, then only remains flash and update on the watch.
When I try to uppgrade with cm12.1 and others, I always
get "signature can't veryfy....", and then reboots.
What iis wrong? I'm new at this so I need some
guide please.
vespa70 said:
When I try to uppgrade with cm12.1 and others, I always
get "signature can't veryfy....", and then reboots.
What iis wrong? I'm new at this so I need some
guide please.
Click to expand...
Click to collapse
Welcome to the Android comuntiy!
I will try to guide you step by step on how to get your phone rocking cyanogenmod 11 (cm11 is kitkat but it is the same procedure for any other ROM, just replace the cm11 file cm12)
What you'll need;
The CyanogenMod ROM
A custom recovery, otherwise you'll get the signiture verification error
ROOT!
Adb and fastboot
adb drivers
Google Apps
-------------------------
We are going to use The custom recovery I provided in this post and not the one provided in the description of the video. The steps below is assuming that you have succesfully rooted your device and have enabled usb debugging and authorized your pc.
-------------------------
1. Connect your phone to your pc, wait for the drivers to install and once they have installed continue on.
2. Click start and open devices and printers, you should see your device, right-click it and hit properties and then you should see different "devices", choose the one who has a type from SAMSUNG and then up next to the corners you should see 2 options, general and one more, hit the second one and hit properties at the bottom right.
3. It should open a new window, in that window there is and option to change setting, click it then select drivers at the top and hit update.
4. Click choose an update already availible on the computer, then click let me pick and wait.
5. Then there is an option to choose compatible drivers or something like that and make sure it is not ticked! Find a driver from ClockworkMod and to the right you should see android adb interface, click it and hit install after that is complete you should have the adb drivers.
6. Open minimal adb and fastboot that you downloaded and type "adb devices" and wait, it should show your device and you might get a popup window on your phone saying to authorize the pc, hit always trust and hit allow and your device should be seen in adb and it should say device next to the serial number.
7 Turn off your phone.
8. Boot into recovery by pressing power + volume up + home button.
9. Click advanced
10. Click adb sideload and make sure that when you type adb devices in minimal adb and fastboot you should see your device and it should say sideload next to the serial number. If you don't, repeat the steps for installing the drivers just this time do it in adb sideload mode.
11. Once you got the driver working in adb sideload you should press the home button and click wipe, then select advanced wipe and select, dalvik, system, data, internal storage, cache and preload. This will wipe your data!
12. Once that is done go to adb sideload and connect your phone to the pc.
13. Move the downloaded ROM to the minimal adb and fastboot folder adn then in the command line type adb sideload <filename>. DON'T REBOOT!!!
14. Once flash is done it is time to move the google apps to the minimal adb and fastboot, remember, DON'T REBOOT!!
15. Type adb sideload <googelappsfilename>. Wait till it is done and now you can finally reboot.
--------------------
It should boot perfectly, remember, the first time boot might take a lot of time and the device might overheat but just leave it there for a couple of mnutes until it boots.
All credits to the cyangenmod development team and that guy from youtube!
If I helped you, hit thanks!
If you encounter any problems (ROM Not booting or device won't show up in adb), please post them here!
RAZERZDAHACKER said:
Welcome to the Android comuntiy!
I will try to guide you step by step on how to get your phone rocking cyanogenmod 11 (cm11 is kitkat but it is the same procedure for any other ROM, just replace the cm11 file cm12)
What you'll need;
The CyanogenMod ROM
A custom recovery, otherwise you'll get the signiture verification error
ROOT!
Adb and fastboot
adb drivers
Google Apps
-------------------------
We are going to use The custom recovery I provided in this post and not the one provided in the description of the video. The steps below is assuming that you have succesfully rooted your device and have enabled usb debugging and authorized your pc.
-------------------------
1. Connect your phone to your pc, wait for the drivers to install and once they have installed continue on.
2. Click start and open devices and printers, you should see your device, right-click it and hit properties and then you should see different "devices", choose the one who has a type from SAMSUNG and then up next to the corners you should see 2 options, general and one more, hit the second one and hit properties at the bottom right.
3. It should open a new window, in that window there is and option to change setting, click it then select drivers at the top and hit update.
4. Click choose an update already availible on the computer, then click let me pick and wait.
5. Then there is an option to choose compatible drivers or something like that and make sure it is not ticked! Find a driver from ClockworkMod and to the right you should see android adb interface, click it and hit install after that is complete you should have the adb drivers.
6. Open minimal adb and fastboot that you downloaded and type "adb devices" and wait, it should show your device and you might get a popup window on your phone saying to authorize the pc, hit always trust and hit allow and your device should be seen in adb and it should say device next to the serial number.
7 Turn off your phone.
8. Boot into recovery by pressing power + volume up + home button.
9. Click advanced
10. Click adb sideload and make sure that when you type adb devices in minimal adb and fastboot you should see your device and it should say sideload next to the serial number. If you don't, repeat the steps for installing the drivers just this time do it in adb sideload mode.
11. Once you got the driver working in adb sideload you should press the home button and click wipe, then select advanced wipe and select, dalvik, system, data, internal storage, cache and preload. This will wipe your data!
12. Once that is done go to adb sideload and connect your phone to the pc.
13. Move the downloaded ROM to the minimal adb and fastboot folder adn then in the command line type adb sideload <filename>. DON'T REBOOT!!!
14. Once flash is done it is time to move the google apps to the minimal adb and fastboot, remember, DON'T REBOOT!!
15. Type adb sideload <googelappsfilename>. Wait till it is done and now you can finally reboot.
--------------------
It should boot perfectly, remember, the first time boot might take a lot of time and the device might overheat but just leave it there for a couple of mnutes until it boots.
All credits to the cyangenmod development team and that guy from youtube!
If I helped you, hit thanks!
If you encounter any problems (ROM Not booting or device won't show up in adb), please post them here!
Click to expand...
Click to collapse
Hello! Thank's for your help! But I'm stuck at item nbr 9. There is no "advanced" .
Right now I can't go anny further.
vespa70 said:
Hello! Thank's for your help! But I'm stuck at item nbr 9. There is no "advanced" .
Right now I can't go anny further.
Click to expand...
Click to collapse
I wrote that we are not going to use the recovery the guy in the video used, replace it with the recovery I provided, remember to read the whole post.
RAZERZDAHACKER said:
I wrote that we are not going to use the recovery the guy in the video used, replace it with the recovery I provided, remember to read the whole post.
Click to expand...
Click to collapse
Hi! Shall I first install "TWRP...md5" with Odin?
The phone is rooted, I used Kingroot.
Item 5, can't find "ClockworkMod".
vespa70 said:
Hi! Shall I first install "TWRP...md5" with Odin?
The phone is rooted, I used Kingroot.
Item 5, can't find "ClockworkMod".
Click to expand...
Click to collapse
Yea, twrp and you should see the clockworkmod in the list, make sure the box is not ticked if you downloaded and installed the .exe driver file that I provided.
RAZERZDAHACKER said:
Yea, twrp and you should see the clockworkmod in the list, make sure the box is not ticked if you downloaded and installed the .exe driver file that I provided.
Click to expand...
Click to collapse
yes, ther is 5 in the list and i looked at all of them.
There is a lot of manufacturers but not Clockwork.
vespa70 said:
yes, ther is 5 in the list and i looked at all of them.
There is a lot of manufacturers but not Clockwork.
Click to expand...
Click to collapse
If you have an sdcard you can put the files on there and flash via sdcard.
RAZERZDAHACKER said:
If you have an sdcard you can put the files on there and flash via sdcard.
Click to expand...
Click to collapse
Yes I have a sdcard. If I copy all the files from you to
the card, how do I procid from there?
The cam is rooted so how do I go on?
vespa70 said:
Yes I have a sdcard. If I copy all the files from you to
the card, how do I procid from there?
The cam is rooted so how do I go on?
Click to expand...
Click to collapse
Put the cyanogenmod rom on the sdcard and the google apps. Assuming you have the recovery I provided here boot into it. Hit install then select storage then select your sdcard. Make sure the files are there and exit out and wipe as I said in the instructions. Make sure not to wipe the micro sdcard. Then install the rom then the google apps.
RAZERZDAHACKER said:
Put the cyanogenmod rom on the sdcard and the google apps. Assuming you have the recovery I provided here boot into it. Hit install then select storage then select your sdcard. Make sure the files are there and exit out and wipe as I said in the instructions. Make sure not to wipe the micro sdcard. Then install the rom then the google apps.
Click to expand...
Click to collapse
I am a little confused about this. This is what I have on the sdcard:
cm-11-20160603-UNOFFICIAL-kylepro.zip, TWRP.S7580.tar.md5, HDPI_gapps-kk-20160526-signed.zip.
I have done TWRP.. with Odin, is that what you mean "boot into it"??
"Hit install", where?? Wipe: Shall I "wipe cache partition"??
There is "wipe data/factory reset", but then everything is gone.
Please, can you show me point by point what to do, so I don't brick it all.
You know what, I stumbled across this video and it is basically a full tutorial! Lycka till med ditt flashande!
vespa70 said:
Hi!!!! It''s working now 4.4.4 kitkat is up
and running!! I don't belive it, but it's true.
I had to,in Odin, untick "autoreboot and F.Reset time". That maked the the damn thing not to reboot.
After that it worked.
Anyway, Many thank's for your hep!!
Bye
Click to expand...
Click to collapse
vespa70 said:
Hi!!!! It''s working now 4.4.4 kitkat is up
and running!! I don't belive it, but it's true.
I had to,in Odin, untick "autoreboot and F.Reset time". That maked the the damn thing not to reboot.
After that it worked.
Anyway, Many thank's for your hep!!
Bye
Click to expand...
Click to collapse
Ha, jag visste det från alla utropstecken , hoppas att allt funkar bra och om du får några bugg eller så rapportera det här.
Hi guys, my redmi 5 plus is stuck on logo loading screen and i can only go for fastboot. Cannot neither turn off phone.
I tried with Mi Flash tool but program fail with "Can not find flash_all.bat". I tried different version of roms and Mitool, but still have this error. How can i repair my device? Thnak you all for the future responsed
Ps: sorry for my really bad english
I dont´know what you tried to do before to get this status or if you have an unlocked bootloader to perform some operation in fastboot mode. If you are in stock rom you can try enter to recovery and use MiAssistant feature is a kind of adb sideload in-built that you can use to reinstall again the rom onto your device. Here you will find some guide lines about this behind the concept http://www.xiaomitool.com/adb
SubwayChamp said:
I dont´know what you tried to do before to get this status or if you have an unlocked bootloader to perform some operation in fastboot mode. If you are in stock rom you can try enter to recovery and use MiAssistant feature is a kind of adb sideload in-built that you can use to reinstall again the rom onto your device. Here you will find some guide lines about this behind the concept http://www.xiaomitool.com/adb
Click to expand...
Click to collapse
You right sorry. I have Bootloader unlocked. My brick come becose of me trying to root the phone with "1clickrooter" for redmi5 plus. When phone rebooted on recovery he ask me for a password. No pin works on this pass requesto so i try to wipe cash, phone automatically reboot and stuck in logo screen. Cannot turn of or go to recovery, only action i can make is to go on fastboot mode.
So, i have news, i can go on recovery mode (recovery i have is called "Team Win Recovery Project 3.2.1.0"), but in order to make write action (now i can only read) request me a password, obviously neither 1 of my pass (sim pin/screen unlock) work.
Jackevolution said:
So, i have news, i can go on recovery mode (recovery i have is called "Team Win Recovery Project 3.2.1.0"), but in order to make write action (now i can only read) request me a password, obviously neither 1 of my pass (sim pin/screen unlock) work.
Click to expand...
Click to collapse
If you can reboot now to recovery twrp then just cancel when it prompts for a password and you have to format data in order to can reboot to system again
Jackevolution said:
You right sorry. I have Bootloader unlocked. My brick come becose of me trying to root the phone with "1clickrooter" for redmi5 plus. When phone rebooted on recovery he ask me for a password. No pin works on this pass requesto so i try to wipe cash, phone automatically reboot and stuck in logo screen. Cannot turn of or go to recovery, only action i can make is to go on fastboot mode.
Click to expand...
Click to collapse
SubwayChamp said:
If you can reboot now to recovery twrp then just cancel when it prompts for a password and you have to format data in order to can reboot to system again
Click to expand...
Click to collapse
Already done, now semms to be stuck on the same loading screen, baibe he installing apps? It taking sooo long...
i think this isn't working. It's just 20 minute that phone is stuck on "Mi" screen...
Nope, definetly not worked. There is a way to put filesin the phone from recovery?
Jackevolution said:
Nope, definetly not worked. There is a way to put filesin the phone from recovery?
Click to expand...
Click to collapse
Yes, you can reflash again the rom, put the rom zip in your adb folder and short the name as you can, and flash it using adb sideload, to do this tap on "advanced option" and then "adb sideload" in recovery menu and in adb terminal in your pc type adb sideload nameofrom.zip where nameofrom is te name of the rom, don´t forget the extension .zip as I wrote. TWRP will load the zip and flash it again and then you can flash Magisk to root device.
If you can´t see storage of device in your pc is cause it´s encrypted but you can perform adb sideload anyway
Jackevolution said:
Hi guys, my redmi 5 plus is stuck on logo loading screen and i can only go for fastboot. Cannot neither turn off phone.
I tried with Mi Flash tool but program fail with "Can not find flash_all.bat". I tried different version of roms and Mitool, but still have this error. How can i repair my device? Thnak you all for the future responsed
Ps: sorry for my really bad english
Click to expand...
Click to collapse
Look at the error you got every time "Can not find flash_all.bat" its mean that you are selecting invalid path, okay so here is correct method to flash via fast-boot method:
Download the latest fast boot rom zip one option is http://bigota.d.miui.com/V9.5.12.0....FA_20180525.0000.00_7.1_global_343bc5aaef.tgz
Unzip .tgz using winrar and the zip will be extracted in folder named as vince_global_images_V9.5.12.0.NEGMIFA_20180525.0000.00_7 inside this folder there will be another folder named same.
Open Mi Flash tool and click to select direct to folder vince_global_images_V9.5.12.0.NEGMIFA_20180525.0000.00_7 open the folder and then open the other folder click Ok (don't open the the images folder)
Connect your redmi 5 plus in fast boot mode and click refresh, then choose clean all and click Flash