Related
ROOT WITHOUT UNLOCKING BOOTLOADER
NOTE: *AM NOT RESPONSIBLE FOR ANY DAMAGE CAUSED TO YOUR PHONE
* IF U POINT FINGERS AT ME , I WILL LAUGH AT YOU
PRECONDITIONS :
DOWNLOAD ADB AND FASTBOOT DRIVERS FROM HERE OR HERE
EXTRACT THE DOWNLOADED FILE
DOWNLOAD RECOVERY FROM HERE AND PUT INTO EXTRACTED FOLDER WHERE ADB AND FASTBOOT ARE PRESENT
DOWNLOAD SUPERUSER FROM HERE AND COPY TO PHONE'S SD CARD OR EXT CARD
STEPS:
GO TO THE EXTRACTED FOLDER AND OPEN COMMAND PROMPT BY PRESSING CTRL+SHIFT
connect your phone in switch on mode
TYPE THIS COMMAND
PHP:
adb reboot bootloader
wait for the device to boot into bootloader mode/fastboot , and then Type the following
PHP:
fastboot -i 0x1ebf boot recovery-yu.img
NOW CONNECT YOUR PHONE
note : RECOVERY STAYS ONLY FOR ONE TIME SINCE BL IS NOT UNLOCKED
ROOT
ONCE THE RECOVERY SHOWS UP , DO THE FOLLOWING
SECLECT INSTALL ZIP
CHOOSE ZIP FROM SD CARD
NOW SELECT THE DOWNLOADED SUPERUSER ZIP
CONFIRM AND REBOOT
NOW SUCCESSFULLY ROOTED WITHOUT UNLOCKING BOOTLOADER
After running fastboot -i 0x1ebf boot recovery-yu.img I am getting below error.
any idea please?
downloading 'boot.img'...
OKAY [ 0.297s]
booting...
FAILED (remote: bootimage: incomplete or not signed)
finished. total time: 0.297s
change of WiFi Mac address
Faiyaz5yaz said:
ROOT WITHOUT UNLOCKING BOOTLOADER
NOTE: *AM NOT RESPONSIBLE FOR ANY DAMAGE CAUSED TO YOUR PHONE
* IF U POINT FINGERS AT ME , I WILL LAUGH AT YOU
PRECONDITIONS :
DOWNLOAD ADB AND FASTBOOT DRIVERS FROM HERE OR HERE
EXTRACT THE DOWNLOADED FILE
DOWNLOAD RECOVERY FROM HERE AND PUT INTO EXTRACTED FOLDER WHERE ADB AND FASTBOOT ARE PRESENT
DOWNLOAD SUPERUSER FROM HERE AND COPY TO PHONE'S SD CARD OR EXT CARD
STEPS:
GO TO THE EXTRACTED FOLDER AND OPEN COMMAND PROMPT BY PRESSING CTRL+SHIFT
connect your phone in switch on mode
TYPE THIS COMMAND
PHP:
adb reboot bootloader
wait for the device to boot into bootloader mode/fastboot , and then Type the following
PHP:
fastboot -i 0x1ebf boot recovery-yu.img
NOW CONNECT YOUR PHONE
note : RECOVERY STAYS ONLY FOR ONE TIME SINCE BL IS NOT UNLOCKED
ROOT
ONCE THE RECOVERY SHOWS UP , DO THE FOLLOWING
SECLECT INSTALL ZIP
CHOOSE ZIP FROM SD CARD
NOW SELECT THE DOWNLOADED SUPERUSER ZIP
CONFIRM AND REBOOT
NOW SUCCESSFULLY ROOTED WITHOUT UNLOCKING BOOTLOADER
Click to expand...
Click to collapse
This method changeed the WiFi Mac address of my YU
Any idea why?
Harsh_24 said:
This method changeed the WiFi Mac address of my YU
Any idea why?
Click to expand...
Click to collapse
I don't think the method caused it , since it only installs superuser app in system folder
I doubt the YU recovery which u suggested and developed by Vishal I guess
Faiyaz5yaz said:
I don't think the method caused it , since it only installs superuser app in system folder
Click to expand...
Click to collapse
I doubt d recovery file developed by Vishal
is it truly change the MAC address?
Harsh_24 said:
I doubt d recovery file developed by Vishal
Click to expand...
Click to collapse
Dear @vishal_android freak
is it truly cbange something MAC address? when we flash your recovery image?
regard
androidgalaxyman
Faiyaz5yaz said:
ROOT WITHOUT UNLOCKING BOOTLOADER
NOTE: *AM NOT RESPONSIBLE FOR ANY DAMAGE CAUSED TO YOUR PHONE
* IF U POINT FINGERS AT ME , I WILL LAUGH AT YOU
PRECONDITIONS :
DOWNLOAD ADB AND FASTBOOT DRIVERS FROM HERE OR HERE
EXTRACT THE DOWNLOADED FILE
DOWNLOAD RECOVERY FROM HERE AND PUT INTO EXTRACTED FOLDER WHERE ADB AND FASTBOOT ARE PRESENT
DOWNLOAD SUPERUSER FROM HERE AND COPY TO PHONE'S SD CARD OR EXT CARD
STEPS:
GO TO THE EXTRACTED FOLDER AND OPEN COMMAND PROMPT BY PRESSING CTRL+SHIFT
connect your phone in switch on mode
TYPE THIS COMMAND
PHP:
adb reboot bootloader
wait for the device to boot into bootloader mode/fastboot , and then Type the following
PHP:
fastboot -i 0x1ebf boot recovery-yu.img
NOW CONNECT YOUR PHONE
note : RECOVERY STAYS ONLY FOR ONE TIME SINCE BL IS NOT UNLOCKED
ROOT
ONCE THE RECOVERY SHOWS UP , DO THE FOLLOWING
SECLECT INSTALL ZIP
CHOOSE ZIP FROM SD CARD
NOW SELECT THE DOWNLOADED SUPERUSER ZIP
CONFIRM AND REBOOT
NOW SUCCESSFULLY ROOTED WITHOUT UNLOCKING BOOTLOADER
Click to expand...
Click to collapse
There is surely something in the recovery img by vishal.
I flashed the twrp recovery img and my wifi Mac address recovered its initial values.
Harsh_24 said:
There is surely something in the recovery img by vishal.
I flashed the twrp recovery img and my wifi Mac address recovered its initial values.
Click to expand...
Click to collapse
I never found this issue and it's pretty weird as MAC address has nothing to do with recovery afaik. Still I'll have a look
Unlocking boot loader and rooting vs without unlocking rooting
vishal_android freak said:
I never found this issue and it's pretty weird as MAC address has nothing to do with recovery afaik. Still I'll have a look
Click to expand...
Click to collapse
Dears,
Which one is actually void the yu youreka warranty. as we know , Manufactures allows us to root the device. But which mode is right one? I am aware , if we don't do unlock the boot loader ,we can't flash the custom roms. is it safe without unlocking the bootloader to flash the custom recovery image like TWRP or CWW?
Regards
androidgalaxyman
androidgalaxyman said:
Dears,
Which one is actually void the yu youreka warranty. as we know , Manufactures allows us to root the device. But which mode is right one? I am aware , if we don't do unlock the boot loader ,we can't flash the custom roms. is it safe without unlocking the bootloader to flash the custom recovery image like TWRP or CWW?
Regards
androidgalaxyman
Click to expand...
Click to collapse
You cannot flash recovery without unlocking bootloader. And yureka's warranty isn't getting void if we unlock it
@Faiyaz5yaz
Have you actually tested the method on an actual YU Yureka which has unlock & tamper bits marked as 'false'?? My tests show same thing as @tarunongo's; the image can't be boot if unlock bit is set false.
:cyclops:
Titokhan said:
@Faiyaz5yaz
Have you actually tested the method on an actual YU Yureka which has unlock & tamper bits marked as 'false'?? My tests show same thing as @tarunongo's; the image can't be boot if unlock bit is set false.
:cyclops:
Click to expand...
Click to collapse
I did try as mentioned by @vishal_android freak for unlocked bootloaders .. I didn't try this though .. But Logically it should work , since I have tried this method on nexus devices , one plus one & android one devices which have similar bootloaders .. Never had this issue..
and @Harsh_24 , did u successfully flash recovery ?
And can anyone try this command instead
fastboot boot recovery-name.img ..
if someone confirms that both methods fail.. I ll lock the thread ..
@Faiyaz5yaz
Without ' -i 0x1ebf', fastboot can't recognize or access the device. I have tested all possible methods; even you can't flash or boot official images under locked bootloader - please see the conversation here.
I have Nexus 4, Nexus 7 (2012) & OnePlus One & thus accustomed with temp recovery booting., but it seems a noticeable exception.
I'm still waiting for confirmation from other member(s).
mayhack said:
I have used the method for rooting Yureka without unlocking Boot loader with boot -i 0x1ebf command which worked fine on Kitkat but not on Yureka running Lollipop after Upgrading to Lollipop. Can anyone confirm that this method can work on lollipop ??
Click to expand...
Click to collapse
It doesn't work for me either. I had rooted my CM11 earlier but nothing is working on CM12. Custom recovery gets flashed through fastboot but phone always loads stock recovery. Where does Custom recovery go after it gets successfully flashed.
I recently updated Yureka to 5.0.2 and out of curiosity I was searching for Root access in developer tools, and unable to see it. But I believe it was there in KitKat. Even search option in settings gives result ROOT ACCESS in same option, but I'm unable to get.
I believe there should be a way out than losing all internal memory data to flash SuperSU. It is possible to enable that HIDDEN TOGGLE by some ADB command since USB debugging is available?
@Faiyaz5yaz
Hot booting will cause brick of device ! I didn't tried though
I am working on a tool which can be used to root yureka and yuphoria without unlocking bootloader and without any custom recovery. I will be sharing it soon (already posted but beta tester said that it is not installing su binaries. )
Didnt work for me. It boots into a dark screen.
Lollipop
mayhack said:
I have used the method for rooting Yureka without unlocking Boot loader with boot -i 0x1ebf command which worked fine on Kitkat but not on Yureka running Lollipop after Upgrading to Lollipop. Can anyone confirm that this method can work on lollipop ??
Click to expand...
Click to collapse
I would not recommend trying it on lollipop as it doesn't work and it boots to fastboot/bootloader constantly with the error "Reason for Fastboot: UTAG "flashfail" etc.
I luckily fixed it as I have no other android phone, I had to go on BP Tools press Vol+ to select it, it overrided it and then when I rebooted it was fine thank God I almost ended up having to hard reset and reinstall Stock ROM
Phew.
Plus it was good think I had backup though one problem at the time I couldn't restore it due to not being able to use adb.
:fingers-crossed: it should be fixed, Hopefully
tarunongo said:
After running fastboot -i 0x1ebf boot recovery-yu.img I am getting below error.
any idea please?
downloading 'boot.img'...
OKAY [ 0.297s]
booting...
FAILED (remote: bootimage: incomplete or not signed)
finished. total time: 0.297s
Click to expand...
Click to collapse
same thing was happening to me.
To install CMW recovery or any other you have to unlock bootloader if not then you may brick your phone. As normally you can't enter in a house before open the main door. And yu provide permission for all type rooting
Hello Yu Yureka fans!!!
This for the Yu Yureka fans who want to root the phone but don't want to miss OTA update by flashing custom recovery
In this thread i will tell you how to ROOT your Yu Yureka without flashing custom recovery.
This method will not flash custom recovery over stock recovery, this will just boot the custom recovery once just to flash the superuser.zip. so you will be back to stock recovery after flashing superuser.zip.
So lets get started...
Your Bootloader should be UNLOCKED
Files you need:
1. adb and fastboot drivers
2. A CWM recovery link (don't worry we wont flash it, it is just needed to install superuser.zip)
3. Superuser.zip link (save this in your sd card or internal memory)
Note: Keep recovery.img file in the same folder where adb and Fastboot drivers are placed and always open command window from that folder.
Connect your phone to pc via data cable
Steps:
1. Open command window (cntl+shift+right click)
2. Type
Code:
adb devices
if your device is connected you will get it in connected devices
3. Type
Code:
adb reboot-bootloader
4. Type
Code:
fastboot -i 0x1ebf boot recovery-yu.img
now your device will boot into recovery mode
5. Select install zip from sd and navigate where you have downloaded the superuser.zip and select install.
6. Done!!! Your device is rooted and you are still in stock recovery :good: you wont miss the OTA
To check if you are in stock recovery just reboot into recovery :good:
Hit thanks if this helped :good:
This isn't yours, You copied it from YuPlayGodForums, from DoomLord's post...
N'ayam Amarsh'e said:
This isn't yours, You copied it from YuPlayGodForums, from DoomLord's post...
Click to expand...
Click to collapse
First i am not a user of yuplaygod forums,
Second its not copied
Third you have no right to point at someone without any valid reason
Lastly stop spamming my post (read xda forum rules first you visit it here --> http://forum.xda-developers.com/announcement.php?f=3861)
@aashking
You can't boot the recovery image on locked bootloader; we have covered this fact already.
http://forum.xda-developers.com/showpost.php?p=58628082&postcount=12
Titokhan said:
@aashking
You can't boot the recovery image on locked bootloader; we have covered this fact already.
http://forum.xda-developers.com/showpost.php?p=58628082&postcount=12
Click to expand...
Click to collapse
@Titokhan yeah dude thanks for reminding i will update the OP :good:
Unable to get the 3rd command working. It keeps waiting for the device and the device reboots in normal mode. What am I doing wrong?
jitendragarg said:
Unable to get the 3rd command working. It keeps waiting for the device and the device reboots in normal mode. What am I doing wrong?
Click to expand...
Click to collapse
Reinstall ADB Drivers
adbdriver.com
N'ayam Amarsh'e said:
Reinstall ADB Drivers
adbdriver.com
Click to expand...
Click to collapse
Thanks, will check. Although I downloaded the drivers just today, so not sure, how it is not up to date. Anyway, will check it once I am home in 3 hours.
tried resintalling the drivers. didn't help. command prompt still keeps on waiting for device forever, while phone is in fastboot mode.
Edit:
If I cancel the third command, and check the list again, phone is not listed. Somehow, after rebooting into bootloader, phone stops the adb connection.
i am on twrp recovery can i flash this recovery on that and update the new ota?
please help
[RECOVERIES & ROOT] Yureka custom recoveries & Root without Changing Stock Recovery
Note : This tutorial is for YU Yureka based on CM11 (KK 4.4.4) 32bit architecture
and
do it on your own risk, I will not be responsible if you brick your phone
Here is the detailed guide and collection of stock and all custom recoveries for YU Yureka and detailed guide to Root YU Yureka without changing Stock Recovery
Requirements
1. YU Yureka (obviously) with USB Data cable
2. PC / Laptop (Having Windows installed at least Windows 7 or above)
3. Drivers (Windows Automatically detect and install the required drivers)
4. ADB & Fastboot binary package that can be downloaded from XDA 15 seconds ADB Installer v1.4.2']http://forum.xda-developers.com/showthread.php?t=2588979
5. Custom Recovery (Anyone in which you are interested CWM, PhiZ, TWRP)
6. Latest SuperSU.zip file to root your phone
Warning: This process may delete all data stored in internal storage so better backup all the files stored in internal storage.
Step One
Enable USB Debugging on your device you can just follow these steps:
Go to Settings> About phone and keep taping on build number at least 7 times or till it appears "You are a developer now",
Now again go to settings>developer option (only after the previous step it will be enabled)> check/select USB debugging.
Step Two
Unlock your bootloader to flash custom recovery and root.
Here is the process
1. Download the adb & fastboot binary package and install it.
2. Put your phone into FASTBOOT mode by following anyone from below methods :
Method 1 (easiest)
-------------------
a. Power down phone
b. Plug USB cable to your PC
c. Press and hold Vol Up button and plug other end of USB to your device, soon you will see the fastboot screen.
(or without plugging USB Cable, Press and Hold Power and Vol Up buttons simultaneously, until you see the screen
"FASTBOOT MODE"
Method 2
---------
a. While your phone is Power On, plug USB Data Cable with PC and Phone (USB Debuging must be Enable)
b. Open Command Prompt on your PC (with Administartor rights) and type the following command
adb -s 0x1ebf devices
You will get results something like that :
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
3a289c2 device
*Note : If you get "authorization message" then look on your mobile screen and authorize your PC and run the command again.
c. Now note down the device no. (for e.g. in above "3a289c2") and type the following command
adb -s 3a289c2 reboot bootloader
[*Note replace the device id with your id (here 3a289c2), that you got in last command]
Now your phone must be booted into fastboot mode. A screen with "Fastboot Mode" should be appear on your phone.
3. Device drivers will get installed by windows (please wait for the driver installation to complete)
4. After driver installation is done go to the folder where you have extracted the package
5. Now open elevated DOS command prompt (terminal) on your PC and go into the same folder where you saved the recovery file
(*Note : to start command prompt directly from desired folder, while holding the Shift Key Right Click on folder and select start "open command window here")
6. Type the following command to check if the device was detected in fastboot mode
fastboot -i 0x1ebf devices
you should get output like : 2a25d00 fastboot
if you don't get similar output it means that the drivers weren't correctly installed or the device wasn't connected properly
7. If the output is similar to above then run the following command:
fastboot -i 0x1ebf oem unlock
you should get output something like :
.....
OKAY [ 0.003s]
finished. total time: 0.004s
8. Now your bootloader is now unlocked.
*Note : if you want to re-lock your bootloader again (for warranty on any other reason), again boot into fastboot mode and this time type the following command and enter
fastboot -i 0x1ebf oem lock
Step Three
Boot your phone into recovery (temporarily or permanently) and root your phone
1. Download SuperSU.zip and put it on root of your internal or external SD card
2. To load custom recovery (CWM / TWRP / PhiZ) temporarily, now type this command in terminal :
fastboot -i 0x1ebf boot CWM_6.0.5.1_recovery-yu.img
*Note 1 : if you want to flash the custom recovery permanently then us the following command
fastboot -i 0x1ebf flash CWM_6.0.5.1_recovery-yu.img
*Note 2 : if your download custom recovery is named differently (here CWM_6.0.5.1_recovery-yu.img) then while writing the above commands you need to put the name of the recovery same as as your saved file name (anyone CWM / Phiz / TWRP)
3. Done ! You loaded custom recovery temporarily, if command used with "boot" hence to root your phone, proceed to next section (step 5).
or
If you flashed recovery permanently, using command with "flash" then boot your phone into recovery. To do so, you have Two options
i) type the following command and press enter : adb -s 3a289c2 reboot recovery
or
ii) power off your phone, after then press and hold "Vol up+ Vol down + Power" buttons simultaneously to boot into custom recovery.
Now to root your phone proceed with next section (step 5).
Root your phone
5. To gain root access, flash SuperSu.zip that is stored on your internal or external SD card (in step 1)
6. Choose reboot phone and enjoy rooted phone with stock or custom recovery !
Special Note 1
I didn't tested, but came to know that root doesn't effect OTA update on Yureka.
You can get OTA updates with root but after the OTA update is flashed you will loose root access. To keep it or to avoid this please go to System Settings -> Developer Options -> UNTICK -"Update CM Recovery" (update recovery while installing system updates)
Even though if someone want to go back to Stock recovery, then download the official stock recovery (link no. 6 above) and flash it using command in fastboot mode (second command in step 2 under head "STEP THREE")
Downloads
1. 15 seconds ADB Installer v1.4.2 http://forum.xda-developers.com/showthread.php?t=2588979
2. Super SU latest v2.46 http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
3. CWM 6.0.5.1 https://s.basketbuild.com/devs/vishal_android_freak/yu/yureka
OR http://d-h.st/ElAe
4. PhilZTouch 6.59 based on CWM v6.0.5.1 http://www.androiddevs.net/downloads/
OR http://d-h.st/UqWK
5. TWRP 2.8.5.0 http://techerrata.com/browse/twrp2/tomato
OR https://www.androidfilehost.com/?fid=95916177934528156
OR http://d-h.st/5wDD
6. YU Yureka Official Stock Recovery http://d-h.st/tQ1k
Special Note 2
Without the vendor id, phone will not get detected in fastboot mode.
Like if you want to check fastboot type this :
fastboot -i 0x1ebf devices
therefore, always add "i -0x1ebf" after fastboot and then write your command
aabidhashmi said:
Here is is collection of all custom recoveries for YU Yureka and detailed guide to Root YU Yureka without changing Stock Recovery
Requirements
1. YU Yureka (obviously) with USB Data cable
2. PC / Laptop (Having Windows installed at least Windows 7 or above)
3. Drivers (Windows Automatically detect and install the required drivers)
4. ADB & Fastboot binary package that can be downloaded from XDA 15 seconds ADB Installer v1.4.2']http://forum.xda-developers.com/showthread.php?t=2588979
5. Custom Recovery (Anyone in which you are interested CWM, PhiZ, TWRP)
6. Latest SuperSU.zip file to root your phone
Warning: This process may delete all data stored in internal storage so better backup all the files stored in internal storage.
Step One
Enable USB Debugging on your device you can just follow these steps:
Go to Settings> About phone and keep taping on build number at least 7 times or till it appears "You are a developer now",
Now again go to settings>developer option (only after the previous step it will be enabled)> check/select USB debugging.
Step Two
Unlock your bootloader to flash custom recovery and root.
Here is the process
1. Download the adb & fastboot binary package and install it.
2. Power down phone
3. Plug USB cable to your PC
4. Press and hold Vol Up button and plug other end of USB to your device, soon you will see the fastboot screen.
(or without plugging USB Cable, Press and Hold Power and Vol Up buttons simultaneously, until you see the screen
"FASTBOOT MODE"
5. Device drivers will get installed by windows (please wait for the driver installation to complete)
6. After driver installation is done go to the folder where you have extracted the package
7. Now open elevated DOS command prompt (terminal) on your PC and go into the same folder where you saved the recovery file
* to start command prompt directly from desired folder, while holding the Shift Key Right Click on folder and select start "open command window here"
8. Type the following command to check if the device was detected in fastboot mode
fastboot -i 0x1ebf devices
you should get output like : 2a25d00 fastboot
if you don't get similar output it means that the drivers weren't correctly installed or the device wasn't connected properly
9. If the output is similar to above then run the following command:
fastboot -i 0x1ebf oem unlock
you should get output something like :
.....
OKAY [ 0.003s]
finished. total time: 0.004s
10. Now your bootloader is now unlocked.
Step Three
Root your phone without changing your stock recovery
1. Download SuperSU.zip and put it on root of your internal or external SD card
2. To load custom recovery (CWM / TWRP / PhiZ) temporarily, now type this command in terminal :
fastboot -i 0x1ebf boot recovery CWM_6.0.5.1_recovery-yu.img
*Note : if your download custom recovery is named differently (here CWM_6.0.5.1_recovery-yu.img) then while writing the above command you need to put the name of the recovery same as as your saved file name (anyone CWM / Phiz / TWRP)
Done ! You flashed custom recovery temporarily.
3. Now press and hold "Vol up+ Vol down + Power" buttons simultaneously to boot into custom recovery.
4. To gain root access flash SuperSu.zip that is stored on your internal or external SD card (in step 1)
5. Choose reboot phone and enjoy rooted phone without changing stock recovery !
Downloads
1. 15 seconds ADB Installer v1.4.2 http://forum.xda-developers.com/showthread.php?t=2588979
2. Super SU latest v2.46 http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
3. CWM 6.0.5.1 https://s.basketbuild.com/devs/vishal_android_freak/yu/yureka
OR http://d-h.st/ElAe
4. PhilZTouch 6.59 based on CWM v6.0.5.1 http://www.androiddevs.net/downloads/
OR http://d-h.st/UqWK
5. TWRP 2.8.5.0 http://techerrata.com/browse/twrp2/tomato
OR https://www.androidfilehost.com/?fid=95916177934528156
OR http://d-h.st/5wDD
Special Note
Without the vendor id, phone will not get detected in fastboot mode.
Like if you want to check fastboot type this :
fastboot -i 0x1ebf devices
therefore, always add "i -0x1ebf" after fastboot and then write your command
Click to expand...
Click to collapse
Few errors noted:
1. You can't say flashing recovery when you are booting it.
2. In step 3 point 3 is not valid because when your command is to boot it will automatically boot into recovery you need not use combination keys.
3. Last point vender id is wrong !!!
Few suggestions:
1. It feels like you have not tested this by yourself
2. There is already a guide for "rooting without flashing recovery". Search before posting.
Regards
aashking
aashking said:
Few errors noted:
1. You can't say flashing recovery when you are booting it.
2. In step 3 point 3 is not valid because when your command is to boot it will automatically boot into recovery you need not use combination keys.
3. Last point vender id is wrong !!!
Few suggestions:
1. It feels like you have not tested this by yourself
2. There is already a guide for "rooting without flashing recovery". Search before posting.
Regards
aashking
Click to expand...
Click to collapse
Dear aaskking
Thanks to inform. Here is the corrections
1 & 2 - Tutorial updated with "boot" and "flash" commands separately.
3 + Vendor ID is correct nothing wrong in it.
4 - I already tested all those procedures and commands. I never post anything without testing.
5 - Yes, I also seen that available guide, but that is not so much detailed and also required files links are not provided.
Anyway, thanks for your suggestions.
aabidhashmi said:
Dear aaskking
Thanks to inform. Here is the corrections
1 & 2 - Tutorial updated with "boot" and "flash" commands separately.
3 + Vendor ID is correct nothing wrong in it.
4 - I already tested all those procedures and commands. I never post anything without testing.
5 - Yes, I also seen that available guide, but that is not so much detailed and also required files links are not provided.
Anyway, thanks for your suggestions.
Click to expand...
Click to collapse
EDIT : You can get OTA updates with root..
After the update is flashed you will loose root access ..
To keep it or to avoid this please write the following step
STEP) In Developer Option UNTICK -"Update CM Recovery".
That's it.. Cheers mate wonderful thread.. @aabidhashmi @aashking
arjunsingh1000 said:
EDIT : You can get OTA updates with root..
After the update is flashed you will loose root access ..
To keep it or to avoid this please write the following step
STEP) In Developer Option UNTICK -"Update CM Recovery".
That's it.. Cheers mate wonderful thread.. @aabidhashmi @aashking
Click to expand...
Click to collapse
Thanks Arjun Singh @arjunsingh1000 for suggestion and appreciation
Post updated ...
aabidhashmi said:
Thanks Arjun Singh @arjunsingh1000 for suggestion and appreciation
Post updated ...
Click to expand...
Click to collapse
Great mate cheers just checked and tried that ota updates are available and work.. On stock recovery... Locked bootloader and with root..
Achieved this by downgrading to the very first cm11 firmware and got then rooted it and locked the bootloader then I just booted it and got the incremental update .. Downloaded and flashed .. Works perfectly.. Root not lost due to the untick in dev options..
Thanks again Arjun Singh, for confirming OTA updates are working.
I am already on Stock ROM & recovery {rooted} and tried the same procedure {locked the bootloader}, but no updates for me.
Is updates are really there, or something wrong with me ?
Sent from my AO5510 using Tapatalk
I am simply unable to get the device listed in command prompt after fastboot mode is enabled. my phone has option to boot into fastboot mode in power options. i tried that option, i tried using command to boot into fastboot. But somehow, when phone is in fastboot mode, it does not get detected by fastboot application (even though windows installs drivers successfully).
I have tried 3 different laptops. All had same problem. No idea how to solve this.
aabidhashmi said:
Thanks again Arjun Singh, for confirming OTA updates are working.
I am already on Stock ROM & recovery {rooted} and tried the same procedure {locked the bootloader}, but no updates for me.
Is updates are really there, or something wrong with me ?
Sent from my AO5510 using Tapatalk
Click to expand...
Click to collapse
Well I guess you are on the latest build XN0PHQ I guess? Another beta update was made but not rolled out it is um XNPH08P I know its a little late but just in case you don't know..
---------- Post added at 05:30 PM ---------- Previous post was at 05:28 PM ----------
jitendragarg said:
I am simply unable to get the device listed in command prompt after fastboot mode is enabled. my phone has option to boot into fastboot mode in power options. i tried that option, i tried using command to boot into fastboot. But somehow, when phone is in fastboot mode, it does not get detected by fastboot application (even though windows installs drivers successfully).
I have tried 3 different laptops. All had same problem. No idea how to solve this.
Click to expand...
Click to collapse
Ahahahaah... I know just the way... Do not reboot via adb ...
Switch off your phone remove your battery and put it back in do not turn it on.. But connect your USB cable and at the same time hold the power up or maybe down button .. Voila your in fastboot which will get detected .. Don't forget to use the vendor id.
arjunsingh1000 said:
Ahahahaah... I know just the way... Do not reboot via adb ...
Switch off your phone remove your battery and put it back in do not turn it on.. But connect your USB cable and at the same time hold the power up or maybe down button .. Voila your in fastboot which will get detected .. Don't forget to use the vendor id.
Click to expand...
Click to collapse
I tried this method but phone does not get detected in fastboot mode at all. I have drivers installed for all different modes I connect my phone as. No luck at all.
Also, weird thing is, I have an option to directly go to fastboot mode from the power menu.
Jitendra Garg
Your driver's are not installed
As there is no special drivers setup, so connect your PC with Internet then plug your phone and let Windows install drivers automatically.
Sent from my AO5510 using Tapatalk
Working TWRP custom recovery for infocus m430 bingo 21.
To do this, you would require:
data cable if not rooted phone
stock marshmallow running infocus m430 bingo 21
if not rooted, you need adb and fastboot installed on your computer-> google this if never heard of.
download attachments of this post(twrp_recoveryimg)
Problems:
Before you do this, you need to know the temporary problems you would encounter and their solutions
TWRP is in other language but you can use this link to bring it back to english, 1 time thing
http://www.teamandroid.com/2017/04/30/change-twrp-recovery-language-english/
if the above link does not work out, there are lot of youtube videos to enable english in twrp. google out.
once mobile boots into recovery, it will not come back to normal. There is a bit being set by infocus on some partition to reboot to recovery always. Until i find it, you would have to use following the process below to come back to normal boot.
Steps to come back to normal boot
1. in recovery, select option advanced
2. select adb sideload option
3. swipe to start sideload(this will start adb in recovery mode)
4. cancel
5. in your computer type
Code:
adb reboot bootloader
6. After mobile shows fastboot mode: in top of the screen with infocus logo type the below command
Code:
fastboot continue
7. This should boot your device back to normal android boot.
8. You have to do this every time you boot to recovery.
Now follow the below procedures to get a custom recovery on your mobile.
Procedure 1 : (does not require root)
unlock developer options -> google this if you never knew this until now.
unlock oem. Do this by going to developer options -> oem unlocking(enable).
unzip the recovery image attachment
enter fastboot by typing following command.
Code:
adb reboot bootloader.
flash twrp_recovery.img in the attachement. Do this by using following commands.(place your twrp_recovery.img in the current directory of terminal / cmd)
Code:
fastboot erase recovery
fastboot flash recovery twrp_recovery.img
Procedure 2 : (requires root) I have not tried this but it would work. Try it on your own risk.
Download the attachments
send them to your mobile sdcard
install mobile uncle tools or similar app from play store which would flash recovery images
select install recovery and point to the twrp_recovery.img in your sdcard.
Message me in case of questions or reply this thread.
Sir,where to type the code 'adb reboot bootloader' and other codes?
Want your contact number, for the purpose of custom recovery.
I tried that steps many times on my phone via pc. So help me for the custom recovery. I want your contact number to do this process correctly without worrying any problem occurs on my phone.
You should be able to find youtube video on how to install adb and fastboot online. After that, you should type those commands in command prompt in windows computer if you have or in terminal if you have linux or mac.
[email protected] said:
Sir,where to type the code 'adb reboot bootloader' and other codes?
Click to expand...
Click to collapse
Gimme your whatsapp or telegram number, i should be able to reach you out.
iyyappan001 said:
I tried that steps many times on my phone via pc. So help me for the custom recovery. I want your contact number to do this process correctly without worrying any problem occurs on my phone.
Click to expand...
Click to collapse
Problem while using adb fastboot method in In focus M425
What about infocus M425 phone ????
Some informations at first:
XT1676 Moto G5, Fine Gold, 16GB
(TYPE M2675/ FCC ID: <known>/ SEQ#: <known>)
2017-10-30
Problem: Stuck in unlocked Bootloader
Hi all,
i am stuck on bootloader and cant get out.
On my PC I have "Minimal ADB and Fastboot"(v. 1.4.2.) installed and after i open a command prompt(admin) and type
- "fastboot devices" my phone is listed as <NR> fastboot
so that works as the only positive thing i can say
- "adb reboot", *daemon not running. starting it now on port 5037*
*daemon started successfully*
error: no devices/ emulators found
- "adb reconnect", error: no devices/ emulators found
i am not into the adb commands at all, i am a dummy and i would be so glad if someone could lead me out of my problem.
Maybe a word how i got into there:
1) i installed the minimal adb and fastboot(v1.4.2.)
2) i unlocked the bootloader by doing that over the Motorola UNLOCK Bootloader site
3) then i rooted & Flash Twrp Recovery (twrp-3.1.1-0-cedric)
with "fastboot flash recovery twrp-3.1.1-0-cedric.img"
4) first time entered into twrp recovery and i did the following:
A) a factory wipe-> reboot back to recovery mode->
B) install no-verity-opt-encrypt-5.1-> reboot and let system start before i turn off phone and enter bootloader(vol down+start) again
C) after entering recovery mode again, i install Magisk-v11.6 -> reboot->
D) now everything seemed to work, the system started properly rooted.
E) but then i decided to flash once again the Magisk-v11.6 followed by wipe data/ factory reset cause i wanted to completly do the flashing all over.
(dont ask me why i did it.. i could explain and tell you my intention but well it happened anyway and brought me to where i am stuck now)
but that was on this move not all yet: i also wipe dalvik cache
so after wipedalvik/ cache , since that moment i couldnt access to my SD Card anymore as it simply didnt show up anymore.
after a restart i was my first time in an endless bootloop of that Screen with "Erasing"(, the letters sourrounded by a spectral colored circle)
i had to disconnect the phone from power . also i tried to remove the battery for a day. but it would only get me back into that bootloop and only get me out by removing the battery...
i dont know anymore what happened then when the phone now got stuck in the bootloader instead of the bootloop. But yea, now i am stuck here, appreciating any help :highfive:
more infromation from my bootloader screen:
AP Fastboot Flash Mode(secure)
BLB8.12 (<known>, 2017-04-19 11:00:47)
Baseband <known>
Product/ Variant: cedric XT1676 16GB P5
Serial Number: <known>
CPU: MSM8937
eMMC: <known>
DRAM: <known>
Console [NULL]: null
Tools Mode Config: DISABLED
Battery OK
flashing_unlocked
Software status: Official
Connect USB Data Cable
- When pressing <Start>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone drops back to Bootloader
when pressing <RESTART BOOTLOADER>
it restarts to BOOTLOADER
- When pressing <Start Recovery>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
after 10 seconds another screen poops up:
"Erasing", the letters sourrounded by a spectral colored circle for 3 seconds,
bevor the Phone just drops back to Bootloader
(talking about Erasing ..)
- When pressing <POWER OFF>
Power Off works
- When pressing <FACTORY RESET>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone just drops back to Bootloader
- When pressing <BARCODES>
Barcodes are shown
- When pressing <BP TOOLS>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone just drops back to Bootloader
- When pressing <QCOM>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone just drops back to Bootloader
- When pressing <BOOTLOADER LOGS>
Display shows:
AP Fastboot Flash Mode(secure)
Fastboot Reason: UTAG "bootmode" configured as fastboot
When connecting an USC- cable
Transfer Mode: USB Connected
...shows up but i cant get any adb commands to work tho ofc i am a dummy at it...
oh my, i just helped myself by reading my first poste here on the forum from 2016.
i made it now to start twrp by downloading the twrp_cedric_3.1.1-0 once again putting the recovery in my adb folder and type
<fastboot flash recovery twrp.img>
followed by <fastboot reboot-bootloader>
i am curious if i can get going now and if my SD card will be read and if i can get a new flash going...
now back in twrp i go first again to wipe/ factory reset.
now going to reboot, and reboot back into recovery. only gets me back to bootloader from where i can enter twrp manually now(but there is already an indication of the problem i have?)
also before the reboot, it doesnt ask me to install the twrp app anymore where i usually choose "do not install".
now i go to install the <no-verity-opt-encrypt-5.1>, flashing it successfully as it says at the end of the process but there is also some error message in the log before the ...done:
Failed to mount '/data' (invalid argument)
now i thought i should be able to boot the system again but i only get back into the bootloader...
can someone help me how to proceed correctly?
did i miss something to flash?
Techcri said:
now back in twrp i go first again to wipe/ factory reset.
now going to reboot, and reboot back into recovery. only gets me back to bootloader from where i can enter twrp manually now(but there is already an indication of the problem i have?)
also before the reboot, it doesnt ask me to install the twrp app anymore where i usually choose "do not install".
now i go to install the <no-verity-opt-encrypt-5.1>, flashing it successfully as it says at the end of the process but there is also some error message in the log before the ...done:
Failed to mount '/data' (invalid argument)
now i thought i should be able to boot the system again but i only get back into the bootloader...
can someone help me how to proceed correctly?
did i miss something to flash?
Click to expand...
Click to collapse
For failed mount data goto wipe & select format data (option on the right)
Reboot to recovery
For always going into recovery either you don't have a rom installed or read the faq section on my twrp thread as the answer is there
First of all thanks TheFixItMan, that you are behind it and your thread looks really cool and i will immediatly read and try to understand it!
For now i am stuck in the following:
TheFixItMan said:
For failed mount data goto wipe & select format data (option on the right)
Reboot to recoverye
Click to expand...
Click to collapse
i went to "wipe" & "select format data"
the process shows successfully and "...done" but in the log there is a line of red letter:
<Red Letter>"Failed to unmount '/data' ( Device or resource busy)"
<White Letter> You may need to reboot recovery to be able to use / data again.
i went back and to reboot and recovery.
but recovery wouldnt be booted but i get back to the bootloader(maybe that is still an indication of the problem i have here?)
manually entered recovery i did the select format data again but <red letter> line remains.
TheFixItMan said:
For always going into recovery either you don't have a rom installed or read the faq section on my twrp thread as the answer is there
Click to expand...
Click to collapse
i will parallel read your thread now, thx for being behind it solving the questions! :good:
Techcri said:
First of all thanks TheFixItMan, that you are behind it and your thread looks really cool and i will immediatly read and try to understand it!
For now i am stuck in the following:
i went to "wipe" & "select format data"
the process shows successfully and "...done" but in the log there is a line of red letter:
<Red Letter>"Failed to unmount '/data' ( Device or resource busy)"
<White Letter> You may need to reboot recovery to be able to use / data again.
i went back and to reboot and recovery.
but recovery wouldnt be booted but i get back to the bootloader(maybe that is still an indication of the problem i have here?)
manually entered recovery i did the select format data again but <red letter> line remains.
i will parallel read your thread now, thx for being behind it solving the questions! :good:
Click to expand...
Click to collapse
You have to select recovery from the bootloader menu to enter recovery
You can also type in a terminal window whilst phone connected to pc in fastboot
fastboot erase userdata
This will erase all internal data (the same as format data in twrp)
Important Notes For Stock Rom Users
When you first start TWRP it will ask you to swipe to allow modifications - If you do this your stock rom will no longer boot unless you disable dm-verity.
This can be done either by flashing a disable dm-verity zip or by flashing SuperSu zip which will disable it for you
Click to expand...
Click to collapse
ok, stock rom didnt boot so i flashed the "no-verity-opt-encrypt-5.1" .zip
and voila, i could boot the stock again finally! yipie!
but three things i noticed:
1) the boot progress is suspicous / wrong/ stuck at a moment:
"hello" and "moto" i still see and before the letters of moto start spinning around, the screen freezes for like 2-3 seconds and the next ting i see is the red mouth and cameleon and so on
2) i tried to test camera real quick and it says camera is busy
camera unable to start. if this repeats please power off your phone and restart.
(i did already 5 restarts now and still same problem)
anyway, i wanted to install a ROM now, something like Cyanogenmod.
in this context i wonder what the Magisk-v11.6 does? Does it just give superuser permission and is it always required?
3) system only gives me option to Power Off System(no reboot possible)
and that power off and turn on always gets me first into bootloader tho i dont press vol down+start
Edit:
ok, i have here 3 issues still but it goes offtopic already. i throw a thanks first of all at TheFixItMan and then i think thread cna be closed.
I will soon try to install a ROM, like LineageOS 15.1 , and hope that my previous 3 issues will be solved in the process. . .
Techcri said:
ok, stock rom didnt boot so i flashed the "no-verity-opt-encrypt-5.1" .zip
and voila, i could boot the stock again finally! yipie!
anyway, i wanted to install a ROM now, something like Cyanogenmod.
in this context i wonder what the Magisk-v11.6 does? Does it just give superuser permission and is it always required?
Click to expand...
Click to collapse
Cyanogenmod is now lineageos
Use the latest version of magisk to root (see official magisk thread on xda)
You can run modules to mod phone without tripping integrity or dm-verity which if false will stop apps that check if you are rooted from working
Magisk hide can hide apps from detecting you are rooted on a per app selected basis
3) system only gives me option to Power Off System(no reboot possible)
and that power off and turn on always gets me first into bootloader tho i dont press vol down+start
Click to expand...
Click to collapse
Phone should power off normally
If it can't be started normally without going in bootloader and selecting normal startup see my faqs in twrp thread & follow guide to wiping the misc partition
Note if flashing lineageos 15.1 you will require the 64bit version of TWRP available on the lineageos thread - I did not compile this & don't support it
It also doesn't support encryption as far as I know so if you are encrypted you will need to format data & remove it else the rom will get stuck at the decryption screen
TheFixItMan said:
Phone should power off normally
Click to expand...
Click to collapse
it can be powered off normally as long as its not connected per usb (power or pc)
If it can't be started normally without going in bootloader and selecting normal startup see my faqs in twrp thread & follow guide to wiping the misc partition
Click to expand...
Click to collapse
that was not exactly the problem. my problem is that either i press restart system from system or from recovery, i first get a stop at the bootloader. from there i can just toggle to START and confirm. then my system boots. its just that i first need to confirm in bootloader the Start, always!
at this point i tried now anyways from your Official TWRP For Moto G5 Cedric- Thread |||||| your solution from your faq. But yea, it obviously doesnt fit my problem cause putting the lines in cmd prompt gave me that result and boot still does a stop at bootloader.. before i can start system or recovery..
So yea, after the first codeline didnt trigger for an unknown reason for me...
i hadnt the courage to even try the second more relevant codeline!
Note if flashing lineageos 15.1 you will require the 64bit version of TWRP available on the lineageos thread - I did not compile this & don't support it
It also doesn't support encryption as far as I know so if you are encrypted you will need to format data & remove it else the rom will get stuck at the decryption screen
Click to expand...
Click to collapse
btw, Thx a lot for the information, i appreciate it! i choose LineageOs 15.1 and it runs now. atm i am reading myself into magisk. Also big thanks for your tipp looking up the official thread.
Techcri said:
it can be powered off normally as long as its not connected per usb (power or pc)
that was not exactly the problem. my problem is that either i press restart system from system or from recovery, i first get a stop at the bootloader. from there i can just toggle to START and confirm. then my system boots. its just that i first need to confirm in bootloader the Start, always!
at this point i tried now anyways from your Official TWRP For Moto G5 Cedric- Thread |||||| your solution from your faq. But yea, it obviously doesnt fit my problem cause putting the lines in cmd prompt gave me that result and boot still does a stop at bootloader.. before i can start system or recovery..
So yea, after the first codeline didnt trigger for an unknown reason for me...
i hadnt the courage to even try the second more relevant codeline!
btw, Thx a lot for the information, i appreciate it! i choose LineageOs 15.1 and it runs now. atm i am reading myself into magisk. Also big thanks for your tipp looking up the official thread.
Click to expand...
Click to collapse
That error means your phone is not connected to your pc
Make sure you have enabled adb debugging in phones dev settings before booting into recovery
If you type
adb devices
It will list all devices attached
Once your device is listed the commands will work
TheFixItMan said:
That error means your phone is not connected to your pc
Make sure you have enabled adb debugging in phones dev settings before booting into recovery
If you type
adb devices
It will list all devices attached
Once your device is listed the commands will work
Click to expand...
Click to collapse
and you think that your commands fromyour solution here helps me with my issue that i can start straight to everywhere i want? Cause atm I just always have to go over the bootloader -"stop". From there i have then to manually "START" in order to start system (now: LineageOS 15.1:victory or where i have to manually toggle down to "RECOVERY MODE" and start TWRP.
Well, i would give it a try, but yea dunno what i am doing wrong here atm. i just realized that the command "adb devices" never worked for me yet, cause i got in conflict with the command fastboot adb devices which effectivly works for me. Cause before i installed lineageOS 15.1 i had to flash the twrp cedric 3.2.1-0 x64. i did that over the adb command prompt:
Code:
fastboot flash recovery twrp.img
and in that process i even let my phone restart to bootloader with
Code:
fastboot reboot bootloader
.
now i went to tab build nummer 7 times-> dev options "on" -> android debugging enabled.
when i go to bootloader now or to recovery, and connect my device, for a strange reason in command prompt "adb devices" shows that:
... i dont know why the cmd "adb devices" doesnt show my device. maybe there is a twrp setting i need to change?
Techcri said:
and you think that your commands fromyour solution here helps me with my issue that i can start straight to everywhere i want? Cause atm I just always have to go over the bootloader -"stop". From there i have then to manually "START" in order to start system (now: LineageOS 15.1:victory or where i have to manually toggle down to "RECOVERY MODE" and start TWRP.
Well, i would give it a try, but yea dunno what i am doing wrong here atm. i just realized that the command "adb devices" never worked for me yet, cause i got in conflict with the command fastboot adb devices which effectivly works for me. Cause before i installed lineageOS 15.1 i had to flash the twrp cedric 3.2.1-0 x64. i did that over the adb command prompt:
Code:
fastboot flash recovery twrp.img
and in that process i even let my phone restart to bootloader with
Code:
fastboot reboot bootloader
.
now i went to tab build nummer 7 times-> dev options "on" -> android debugging enabled.
when i go to bootloader now or to recovery, and connect my device, for a strange reason in command prompt "adb devices" shows that:
... i dont know why the cmd "adb devices" doesnt show my device. maybe there is a twrp setting i need to change?
Click to expand...
Click to collapse
Does it display a device when the phone is fully booted
If yes than the recovery you are using doesn't support adb (my official recovery does)
If no I recommend downloading the full android sdk and using the adb that comes with that (you will find it in the platform tools folder where you installed it)
Hello, thx for your support.
I linked the wrong picture. This Screeny shows the related cmd (when dev enabled, booted to recovery, connected via usb to pc and typed adb devices).
Does it display a device when the phone is fully booted. If yes than the recovery you are using doesn't support adb (my official recovery does)
Click to expand...
Click to collapse
it shows the same like linked above and when in recovery mode
so no , the 64bit version of twrp cedric 3.2.1-0 prolly isnt the problem.
If no I recommend downloading the full android sdk and using the adb that comes with that (you will find it in the platform tools folder where you installed it)
Click to expand...
Click to collapse
ok i will try that. and the command prompt i have to open from the directoryy<platform tools folder> then right?
would you deinstall minimal ADB and fastboot before installing full android sdk?
TheFixItMan said:
If no I recommend downloading the full android sdk and using the adb that comes with that (you will find it in the platform tools folder where you installed it)
Click to expand...
Click to collapse
still my phone isnt found
- sdk tools installed
- dev enabled
- adb debugging enabled
- command prompt opened at "...\android-sdk\platform-tools"
either in recovery nor in booted system nor in bootloader "adb devices" finds my phone
so the problem with the "bootstop" (have always to manually press "START" at bootloader) persists..
oh wait... i am not connected as admin! is it possible to open an admin command promp:silly:t?
so i am am reading here atm how to open command prompt in specific folder(platform-tools)
but wife is waiting for dinner so i better do that first..
Techcri said:
still my phone isnt found
- sdk tools installed
- dev enabled
- adb debugging enabled
- command prompt opened at "...\android-sdk\platform-tools"
either in recovery nor in booted system nor in bootloader "adb devices" finds my phone
so the problem with the "bootstop" (have always to manually press "START" at bootloader) persists..
oh wait... i am not connected as admin! is it possible to open an admin command promp:silly:t?
so i am am reading here atm how to open command prompt in specific folder(platform-tools)
but wife is waiting for dinner so i better do that first..
Click to expand...
Click to collapse
On windows 7 - hold shift then right click a white empty space of the window where adb is & select open command prompt here
Windows 7 or 10 - search for cmd then right click on cmd and select run as administrator then navigate using cd commands to adb location or copy & paste location (if any spaces in path then put the entire path in quotation marks)
On windows 7 - hold shift then right click a white empty space of the window where adb is & select open command prompt here
Click to expand...
Click to collapse
yes i did that before as non admin
Windows 7 or 10 - search for cmd then right click on cmd and select run as administrator then navigate using cd commands to adb location or copy & paste location (if any spaces in path then put the entire path in quotation marks)
Click to expand...
Click to collapse
i use win7 and cd'ing to the path was almost getting annoying
as screenshot shows, it still doesnt work
in my desperation i deinstalled now all adb drivers(minimal+ sdk)
ran a ccleaner and cleaned registry and reinstalled minimal adb again (btw, there was a new version by now out, 1.4.3)
so the episodes still goes on and i could figure out some new details
because i bought the same phone again for a relative who needed a phone..
in the process of setting it up correctly( thankfully xda is around ) i enabled dev options and the adb debugging
here is the result for the new phone
that shows now that executing as admin or standard user wasnt the problem. i just did it as standard user..
then i thought "hey cool, wait, i connect now my own G5 and see if i can get the phones' Nr displayed there and make sure my phone can communicate with my pc over adb( dunno if the sentence just made sense- greetz from a dummy)"
what happened is shown in this screenshot .. same picture as before! :crying:
(dont get irritated by the screeny because i used the same command prompt for
first, the new phone and
second, my "old" phone which doesnt boot properly, if you look at the command and the result
i am lost!
is it possible to reinstall a bootloader? or how come my phone doesnt communicate with the pc anymore?
and how come that effects the booting process so that i always get this "stop" at the bootloader although i pressed for a restart?
can i do any more tests that indicates what problem i have here?