Related
Hello there users. I'm currently a dev for Nokia X but I would love to help you guys out.
So, I'll be giving out ways on how you can try to get Root on your device. This is a discussion thread.
As I don't have the device myself, I'm counting on people who have purchased it.
So lets start. In order to get development for your device, you need to get a system dump of your whole/entire device.
But for that, you need Root. Heres an app that I think might root the device. http://www.cydiaimpactor.com/
Goto the link, download it and test it out. Give feedback.
And nothing happens. Maybe I`ve done somthing wrong...
So, in a dev options i`ve point usb debuging.
On my pc i got two new devices - Nokia composite adb interface and nokia 2 with yellow mark.
Then run cidia from admin name - usb - driver scan - no device found.
I tried with rooted nokia xl - just to see what happens - error - no such device.
stutofa aregercisr are
Thanks for your help, I tried it out and got this error all the time
Altivex said:
And nothing happens. Maybe I`ve done somthing wrong...
So, in a dev options i`ve point usb debuging.
On my pc i got two new devices - Nokia composite adb interface and nokia 2 with yellow mark.
Then run cidia from admin name - usb - driver scan - no device found.
I tried with rooted nokia xl - just to see what happens - error - no such device.
Click to expand...
Click to collapse
tdiddy.2 said:
Thanks for your help, I tried it out and got this error all the time
Click to expand...
Click to collapse
Okay, so that didnt work.
Now, goto this link and download the adb and fastboot drivers for Nokia X and install them.
After that, go HERE and flash CWM Recovery for Nokia X using the instructions given in the thread.
DONT DO THE ABOVE METHOD! As there is no backup, if something goes wrong, you'll lose the device. For now, wait and let me find more exploits. Till then, do install the adb and fastboot divers.
After that, goto ADB folder and Open command prompt from there (Shift + Right mouse button). Then type this:
Code:
adb reboot bootloader
fastboot -i 0x0421 devices
And see if the device gets recognized.
Then type:
Code:
fastboot -i 0x0421 reboot
You can try this method too: http://forum.xda-developers.com/showthread.php?t=803682
Okay will try. For the recovery, I tried both Nokia X's CWM and TWRP already, none of them worked However it's not going to brick my device haha
On fastboot - nothing. I coudn`t install adb from this tread
http://forum.xda-developers.com/showthread.php?t=2744191
Installer told me-unsupported language and close)
I used cmd.exe ,and path to android tools - on fastboot i got nothing. No list of devices. But.
On reboot or others command - answer is - Waiting for device
Super one click - runs adb server around 3 times, then program freez on - Waiting for device =)
If i click on button driver chek - no issues found.
Maybe i`ve got some trouble with drivers ?
I got them from here
http://developer.nokia.com/resources/library/nokia-x/getting-started/device-setup.html
But i haven`t adb_usb.ini where it should be...
Altivex said:
On fastboot - nothing. I coudn`t install adb from this tread
http://forum.xda-developers.com/showthread.php?t=2744191
Installer told me-unsupported language and close)
I used cmd.exe ,and path to android tools - on fastboot i got nothing. No list of devices. But.
On reboot or others command - answer is - Waiting for device
Super one click - runs adb server around 3 times, then program freez on - Waiting for device =)
If i click on button driver chek - no issues found.
Maybe i`ve got some trouble with drivers ?
I got them from here
http://developer.nokia.com/resources/library/nokia-x/getting-started/device-setup.html
But i haven`t adb_usb.ini where it should be...
Click to expand...
Click to collapse
adb_usb.ini is important as it is the key that recognizes the adb device to the computer.
Do all the above steps in the guide fully including the adb_usb.ini step.
mmmm, Nokia XL got connected without this file...
I tried all instructions on 3 different pc - this file is missed....
So,i just created this file.
on ADB devices i got answer - 188bde4a device
on command fastboot -i 0x0421 devices-
188bde4a fastboot
then i reboot device.
i`ve try out some comands - i lost recovery....
fastboot -i 0x0421 oem unlock
unlocked
fastboot -i 0x0421 flash recovery recovery img.
7seconds flash - and i coud not boot recovery....
i tyed this one
http://forum.xda-developers.com/showthread.php?t=2704379
but - phone boots up in normal mode...
ok,good news - got stock firmware from navifirm!
Just need stock recovery)
Okay, i tried superoneclick, not work :crying:
---------- Post added at 11:02 AM ---------- Previous post was at 10:58 AM ----------
And for the Fastboot...
Code:
Tungs-MacBook-Air:~ md232llaoption$ fastboot -i 0x0421 devices
f901c863 fastboot
Tungs-MacBook-Air:~ md232llaoption$
I think i goot rooted my device....
with root_backup
or towelroot.
So, if I`ll install gaps- that would be great. But i really need custom recovery)
http://forum.xda-developers.com/showthread.php?t=2783157
or in attach.
Copy all data to phone, then go to folder "1" install tr.apk
Make shure you`ve got internet connection.
in folder "2" is SUpersu apk.
In folder"3" - root explorer.
Also you`ll find apk for backup phone.
Altivex said:
mmmm, Nokia XL got connected without this file...
I tried all instructions on 3 different pc - this file is missed....
So,i just created this file.
on ADB devices i got answer - 188bde4a device
on command fastboot -i 0x0421 devices-
188bde4a fastboot
then i reboot device.
i`ve try out some comands - i lost recovery....
fastboot -i 0x0421 oem unlock
unlocked
fastboot -i 0x0421 flash recovery recovery img.
7seconds flash - and i coud not boot recovery....
i tyed this one
http://forum.xda-developers.com/showthread.php?t=2704379
but - phone boots up in normal mode...
ok,good news - got stock firmware from navifirm!
Just need stock recovery)
Click to expand...
Click to collapse
Thats it. You got the fastboot recognized. Now try Bin4ry Root Method and see if it'll work.
tdiddy.2 said:
Okay, i tried superoneclick, not work :crying:
---------- Post added at 11:02 AM ---------- Previous post was at 10:58 AM ----------
And for the Fastboot...
Code:
Tungs-MacBook-Air:~ md232llaoption$ fastboot -i 0x0421 devices
f901c863 fastboot
Tungs-MacBook-Air:~ md232llaoption$
Click to expand...
Click to collapse
You also got fastboot recognized. f901c863 is your fastboot device number.
Try Bin4ry root method.
Altivex said:
I think i goot rooted my device....
with root_backup
or towelroot.
So, if I`ll install gaps- that would be great. But i really need custom recovery)
Click to expand...
Click to collapse
Wait. Did you get Root? HOWWW?! Share if you did. Cause this is what the thread is about.
Dom3616 said:
Wait. Did you get Root? HOWWW?! Share if you did. Cause this is what the thread is about.
Click to expand...
Click to collapse
Towelroot in attach. Idk will it work on clear device,or you need to unlock bootloader. Cos on oem unlock- unlocked something=)
Altivex said:
Towelroot in attach. Idk will it work on clear device,or you need to unlock bootloader. Cos on oem unlock- unlocked something=)
Click to expand...
Click to collapse
Very good. I'll be updating this thread soon.
Now, next step is to goto this thread and make a full dump of your device: http://forum.xda-developers.com/showthread.php?t=2450045
Dom3616 said:
Very good. I'll be updating this thread soon.
Now, next step is to goto this thread and make a full dump of your device: http://forum.xda-developers.com/showthread.php?t=2450045
Click to expand...
Click to collapse
Yes yes!!
Hmmm, and online nandroid backup can do this procedure? Or dump and backup- defferent things?
Altivex said:
Hmmm, and online nandroid backup can do this procedure? Or dump and backup- defferent things?
Click to expand...
Click to collapse
Yes, you can use this also: http://forum.xda-developers.com/showthread.php?t=1620255
After creating the backup, upload it to Google Drive or any other server.
Altivex said:
Hmmm, and online nandroid backup can do this procedure? Or dump and backup- defferent things?
Click to expand...
Click to collapse
I tried to pull and got the recovery img for ya hope this work
Native recovery or custom?)
native I`ve restored yesterday from navifirm. And custom will make our life a bit easyer)
I`ve made a twrp backup, with nandroid . Backup have files with .win extension....
Hello all, I have a Lenovo a6000 smartphone. It was owned by my friend. She had a problem with the android os, so she went to a local store and the there it got hard bricked. Now if I turn it on it only vibrates once. no backlight or any picture. If I press and hold vol- and power buttons together LCD backlight turns on but no display. then it goes off and then again turns on. PC does not detect it. Can anyone help me getting it out from this state?
arnab8820 said:
Hello all, I have a Lenovo a6000 smartphone. It was owned by my friend. She had a problem with the android os, so she went to a local store and the there it got hard bricked. Now if I turn it on it only vibrates once. no backlight or any picture. If I press and hold vol- and power buttons together LCD backlight turns on but no display. then it goes off and then again turns on. PC does not detect it. Can anyone help me getting it out from this state?
Click to expand...
Click to collapse
Try qfil method
JovanSijacki said:
Try qfil method
Click to expand...
Click to collapse
Can you give the link please..... please note the phone is no longer detected in pc
arnab8820 said:
Can you give the link please..... please note the phone is no longer detected in pc
Click to expand...
Click to collapse
You need to have adb and fastboot drivers for your phone to correctly get detected.
Here's the LINK FOR QFIL TUTORIAL. You'll need another set of drivers called as the QCOM drivers which are mentioned in the tutorial from the above link.
Hope this helps.
I already have installed the drivers. Still not detected. Even the device manager does not show a device is connected
sasukay said:
You need to have adb and fastboot drivers for your phone to correctly get detected.
Here's the LINK FOR QFIL TUTORIAL. You'll need another set of drivers called as the QCOM drivers which are mentioned in the tutorial from the above link.
Hope this helps.
Click to expand...
Click to collapse
Here the phone connects in Qualcomm hs-USB...... mode. But in case of mine, it does not even show up in the device manager.
arnab8820 said:
Here the phone connects in Qualcomm hs-USB...... mode. But in case of mine, it does not even show up in the device manager.
Click to expand...
Click to collapse
You should try changing the usb cable you are using. Or maybe that guy in the local repair shop didn't put the sub PCB board back correctly.
sasukay said:
You should try changing the usb cable you are using. Or maybe that guy in the local repair shop didn't put the sub PCB board back correctly.
Click to expand...
Click to collapse
There is only one pcb in it. Changing the cable does not make a difference
One update. I can get into the fastboot mode. But the bootloader is locked. What to do?
arnab8820 said:
One update. I can get into the fastboot mode. But the bootloader is locked. What to do?
Click to expand...
Click to collapse
Lenovo A6000 doesn't come with a locked bootloader B-l
If you can boot into fastboot then you should flash twrp from it depending on the current android version of the device. If it had been on kitkat flash this TWRP v2.8.6.0 or if it has been updated to lollipop then flash the latest TWRP v3.1.0.
For this you need to first have the fastboot drivers installed and also the minimal adb and fastboot tool. Then place the required TWRP in that folder, better rename the file to 'recovery.img' and then in the CMD window which you open by Shift + Right Click first type
Code:
fastboot devices
To check whether your device is detected by the tool and haa got drivers installed correctly.
Later, if successful, type in
Code:
fastboot flash recovery recovery.img
Then you'll have TWRP recovery installed.
Then flash any ROM on the device using it.
sasukay said:
Lenovo A6000 doesn't come with a locked bootloader B-l
If you can boot into fastboot then you should flash twrp from it depending on the current android version of the device. If it had been on kitkat flash this TWRP v2.8.6.0 or if it has been updated to lollipop then flash the latest TWRP v3.1.0.
For this you need to first have the fastboot drivers installed and also the minimal adb and fastboot tool. Then place the required TWRP in that folder, better rename the file to 'recovery.img' and then in the CMD window which you open by Shift + Right Click first type
To check whether your device is detected by the tool and haa got drivers installed correctly.
Later, if successful, type in
Then you'll have TWRP recovery installed.
Then flash any ROM on the device using it.
Click to expand...
Click to collapse
Thanks! I will try it and post the results.
Btw are you sure it does not come with a locked bootloader? I tried to flash the stock recovery and got an error saying "unknown command or device is lock"
arnab8820 said:
Thanks! I will try it and post the results.
Btw are you sure it does not come with a locked bootloader? I tried to flash the stock recovery and got an error saying "unknown command or device is lock"
Click to expand...
Click to collapse
Yeah bro I'm 100% positive. I think unknown command is displayed when you flash the wrong version of recovery.
You can also try
Code:
fastboot boot recovery.img
Sometimes only this works which temporarily boots into the custom recovery.
sasukay said:
Yeah bro I'm 100% positive. I think unknown command is displayed when you flash the wrong version of recovery.
You can also try
Sometimes only this works which temporarily boots into the custom recovery.
Click to expand...
Click to collapse
Ok friend i will post the results tonight
sasukay said:
Lenovo A6000 doesn't come with a locked bootloader B-l
If you can boot into fastboot then you should flash twrp from it depending on the current android version of the device. If it had been on kitkat flash this TWRP v2.8.6.0 or if it has been updated to lollipop then flash the latest TWRP v3.1.0.
For this you need to first have the fastboot drivers installed and also the minimal adb and fastboot tool. Then place the required TWRP in that folder, better rename the file to 'recovery.img' and then in the CMD window which you open by Shift + Right Click first type
Code:
fastboot devices
To check whether your device is detected by the tool and haa got drivers installed correctly.
Later, if successful, type in
Code:
fastboot flash recovery recovery.img
Then you'll have TWRP recovery installed.
Then flash any ROM on the device using it.
Click to expand...
Click to collapse
Tried the above method but no luck it gives an error: "unknown command or device is lock".
arnab8820 said:
Tried the above method but no luck it gives an error: "unknown command or device is lock".
Click to expand...
Click to collapse
Try this with the CWM recovery too.
BTW does your device gets detected by fastboot devices command? Also, have you tried the QPST method?
sasukay said:
Try this with the CWM recovery too.
BTW does your device gets detected by fastboot devices command? Also, have you tried the QPST method?
Click to expand...
Click to collapse
Device gets detected by fastboot devices command. I cant try qpst because the device is not detected in any other mode except fastboot. I hv all the drivers installed
arnab8820 said:
Device gets detected by fastboot devices command. I cant try qpst because the device is not detected in any other mode except fastboot. I hv all the drivers installed
Click to expand...
Click to collapse
You've tried booting into Download mode? It requires you to press the VOL UP + POWER KEY, then you need to select the Download mode in it to perform flashing through QPST.
Also, you never mentioned what android version was the device on, earlier.
sasukay said:
You've tried booting into Download mode? It requires you to press the VOL UP + POWER KEY, then you need to select the Download mode in it to perform flashing through QPST.
Also, you never mentioned what android version was the device on, earlier.
Click to expand...
Click to collapse
If i press and hold vol up and power key together the phone only vibrates once and shows nothing. And i think my friend applied the lollipop update on it. She is not sure.
arnab8820 said:
If i press and hold vol up and power key together the phone only vibrates once and shows nothing. And i think my friend applied the lollipop update on it. She is not sure.
Click to expand...
Click to collapse
Try fastboot oem unlock
arnab8820 said:
Tried the above method but no luck it gives an error: "unknown command or device is lock".
Click to expand...
Click to collapse
I think you are missing something (maybe).
The command is "fastboot flash recovery recovery.img"
If the recovery files name is twrp.img then command will be "fastboot flash recovery twrp.img".
Hi, I've my new essential.
I can't flash a factory image, my device is dectected in fastboot, I have unlocked the bootloader, but when I click on flash-all in the image files, I have "waiting for device". I can't understand why because ALL OTHER COMMANDS have worked : fasboot flashing unlock, USB debugging, fastboot devices...
What can I do ? (In the control panel, device is detected without a yellow mark or something else. Everything should be fine.
basongwe said:
Hi, I've my new essential.
I can't flash a factory image, my device is dectected in fastboot, I have unlocked the bootloader, but when I click on flash-all in the image files, I have "waiting for device". I can't understand why because ALL OTHER COMMANDS have worked : fasboot flashing unlock, USB debugging, fastboot devices...
What can I do ? (In the control panel, device is detected without a yellow mark or something else. Everything should be fine.
Click to expand...
Click to collapse
Still seems like a driver issue. While in bootloader, you could confirm this by trying the command "fastboot devices". If nothing shows then check your device manager. If you are seeing Mata, it's your issue. For some reason every few times I plug in, it'll default back to that and have to manually update the driver to the bootloader driver. Just choose from list of installed drivers as the update method.
Also, if you have USB 2 ports, try one of those. I couldn't get anything to flash when I had it plugged in one of my USB 3 ports.
Could be cable issue, USB port issue, driver issue or you can try updating your adb setup etc... I used the Minimal ADB and Fastboot. Mine was out of date and wouldn't recognize device in fastboot after the Oreo sideload.
Works perfectly with the Essential official drivers in Win8.1Pro now.
The cable is brand new by anker, and works perfectly. Drivers and adb are updated.
mrcooter said:
Still seems like a driver issue. While in bootloader, you could confirm this by trying the command "fastboot devices". If nothing shows then check your device manager. If you are seeing Mata, it's your issue. For some reason every few times I plug in, it'll default back to that and have to manually update the driver to the bootloader driver. Just choose from list of installed drivers as the update method.
Click to expand...
Click to collapse
and fastboot devices works properly. But i've noticed that I wanna flash the same build that I had, maybe that ?
basongwe said:
and fastboot devices works properly. But i've noticed that I wanna flash the same build that I had, maybe that ?
Click to expand...
Click to collapse
Something that was odd that may help (assumed it was just my environment setup). I had adb installed to C:\adb and only way fastboot will work consistently for me is to run commands from that directory. Could be unrelated but thought I would mention it.
basongwe said:
Hi, I've my new essential.
I can't flash a factory image, my device is dectected in fastboot, I have unlocked the bootloader, but when I click on flash-all in the image files, I have "waiting for device". I can't understand why because ALL OTHER COMMANDS have worked : fasboot flashing unlock, USB debugging, fastboot devices...
What can I do ? (In the control panel, device is detected without a yellow mark or something else. Everything should be fine.
Click to expand...
Click to collapse
Try copying fastboot to the folder that has the flash all.bat
What operating system?
Where did you get your driver's?
Reason I ask is at first I had driver's auto install from a Samsung device that I used previously. Caused an issue where it wouldn't start the fastboot process and device got stuck at first step.
Take the system driver of your operating system from essential homepage... Was the trick for me
Link: https://www.essential.com/developer/current-builds
vergilbt said:
Take the system driver of your operating system from essential homepage... Was the trick for me
Link: https://www.essential.com/developer/current-builds
Click to expand...
Click to collapse
This also did the trick for me
You're welcome...
Edit : I have it(drivers from essential website)
Try "fastboot -i 0x2e17 <whatever command here>" it worked for me I wasn't able to unlock my bootloader until I found that command in a random website.
723i said:
Try "fastboot -i 0x2e17 <whatever command here>" it worked for me I wasn't able to unlock my bootloader until I found that command in a random website.
Click to expand...
Click to collapse
That did the trick.
723i said:
Try "fastboot -i 0x2e17 <whatever command here>" it worked for me I wasn't able to unlock my bootloader until I found that command in a random website.
Click to expand...
Click to collapse
command result: "fastboot: unknown option -- i"
not worked for me
mine is on the latest pie update
un1ocked said:
command result: "fastboot: unknown option -- i"
not worked for me
mine is on the latest pie update
Click to expand...
Click to collapse
It's always recommended to use the adb/fastboot provided by Essential (gets installed along with the Windows driver). From the error message, it looks like you are using a different fastboot executable. If you have more than one adb/fastboot package installed on your PC, make sure to use the one from Essential. You can see the path to the executable by running "fastboot --version".
kt-Froggy said:
It's always recommended to use the adb/fastboot provided by Essential (gets installed along with the Windows driver). From the error message, it looks like you are using a different fastboot executable. If you have more than one adb/fastboot package installed on your PC, make sure to use the one from Essential. You can see the path to the executable by running "fastboot --version".
Click to expand...
Click to collapse
fastboot version 28.0.3-5475833
Installed as C:\Program Files (x86)\Essential\ADB\fastboot.exe
EDIT:
problem solved by switching to an old PC with a pure usb 2.0 port
un1ocked said:
problem solved by switching to an old PC with a pure usb 2.0 port
Click to expand...
Click to collapse
Ahh... Yeah, that's often the issue. Still doesn't make a lot of sense to me, because your error msg was "unsupported option". Well, good that it worked for you.
Hi.
Recently I decided to flash lineage os 15.1 on my MiA1
For that I have downgrade to Android nougat.
After downgrading I booted my device.
After setting up device I booted device in fastboot mode to follow further steps like flashing TWRP and all but the problem is my device goes in fastboot mode and it is not identified by abd and after that it is automatically getting restarted and is not holding in fastboot mode.
Please help??
Odd issue. What are you using to flash? If you are using XiaoMiFlash.exe, you'll want to try the (THIS WILL REMOVE ALL YOUR DATA) "clean all" option. Please note that this removes all your data.
I have used MiFlash tool for this and now My device automatically reboot from fastboot mode so I am not able to use adb as well to flash rom or twrp also Now MiFlash tool is not recognising the device.
MrUsamahh said:
I have used MiFlash tool for this and now My device automatically reboot from fastboot mode so I am not able to use adb as well to flash rom or twrp also Now MiFlash tool is not recognising the device.
Click to expand...
Click to collapse
Hmm. What ROM version are you trying to flash on this? If your device isn't recognized by your PC when in fastboot mode, I'm not sure how you'd flash it.
oreo27 said:
Hmm. What ROM version are you trying to flash on this? If your device isn't recognized by your PC when in fastboot mode, I'm not sure how you'd flash it.
Click to expand...
Click to collapse
I flashed Android N Fastboot rom by selecting Clean and lock option.
After that the problem started
MrUsamahh said:
I flashed Android N Fastboot rom by selecting Clean and lock option.
After that the problem started
Click to expand...
Click to collapse
It should boot if you've fully flashed it and cleaned the user data partition. If it still isn't, you'll want to wait for other members with more experience in bricks to chime in.
oreo27 said:
It should boot if you've fully flashed it and cleaned the user data partition. If it still isn't, you'll want to wait for other members with more experience in bricks to chime in.
Click to expand...
Click to collapse
My device is booting up without any problems.
But the problem is bootloader is still unlocked. So i am not able to update via OTA.
And as the device does not holds in fastboot mode so I am not able to do other flash work.
Is there any way I can share a video of my problem with you?
MrUsamahh said:
My device is booting up without any problems.
But the problem is bootloader is still unlocked. So i am not able to update via OTA.
And as the device does not holds in fastboot mode so I am not able to do other flash work.
Is there any way I can share a video of my problem with you?
Click to expand...
Click to collapse
Oh. If it's booting up fine, then you shouldn't be worried too much.
If it keeps restarting in Fastboot mode, it could be a driver issue which is preventing your PC from recognizing your device and vice versa. I'm on Windows 10 which installs drivers automatically so I've never had experience with it.
oreo27 said:
Oh. If it's booting up fine, then you shouldn't be worried too much.
If it keeps restarting in Fastboot mode, it could be a driver issue which is preventing your PC from recognizing your device and vice versa. I'm on Windows 10 which installs drivers automatically so I've never had experience with it.
Click to expand...
Click to collapse
https://photos.app.goo.gl/TyLendNH7XaY74bs1
Please see this video.
If i boot in fastboot mode the device should be in fastboot mode till power button is not pressed for at least 10 seconds.
But in this case it gets switched off.
I have not connected the USB to pc and nothing else.
MrUsamahh said:
https://photos.app.goo.gl/TyLendNH7XaY74bs1
Please see this video.
If i boot in fastboot mode the device should be in fastboot mode till power button is not pressed for at least 10 seconds.
But in this case it gets switched off.
I have not connected the USB to pc and nothing else.
Click to expand...
Click to collapse
I think that's expected behavior? If it doesn't recognize itself being connected to a device, it'll exit fastboot mode.
I think you need to connect it to the USB cable and into your PC for it to not restart/power off.
oreo27 said:
I think that's expected behavior? If it doesn't recognize itself being connected to a device, it'll exit fastboot mode.
I think you need to connect it to the USB cable and into your PC for it to not restart/power off.
Click to expand...
Click to collapse
No when I connect it to pc at that time also same happens.
Previously when booted in fastboot mode it will stay ther by the time juice is out.
MrUsamahh said:
No when I connect it to pc at that time also same happens.
Previously when booted in fastboot mode it will stay ther by the time juice is out.
Click to expand...
Click to collapse
Yup. I just tested it out. It looks like you're right.
oreo27 said:
Yup. I just tested it out. It looks like you're right.
Click to expand...
Click to collapse
So do you know how can I help myself out?
wait.. what exacly did you do when you booted into fastboot? did you type "adb devices" or "fastboot devices"? also, try rebooting into fastboot mode by typing "adb reboot bootloader" in cmd, with your phone plugged into your pc, and with the proper platform-tools installed. it shouldn't really go away from fastboot mode like that.
Mizuru said:
wait.. what exacly did you do when you booted into fastboot? did you type "adb devices" or "fastboot devices"? also, try rebooting into fastboot mode by typing "adb reboot bootloader" in cmd, with your phone plugged into your pc, and with the proper platform-tools installed. it shouldn't really go away from fastboot mode like that.
Click to expand...
Click to collapse
Hy man, I know basic of adb and I use cmd "adb devices"
My device is recognised when it is on.
I can also give various cmd like boot in recovery or fastboot mode or reboot and the device follow the instructions.
Please see the video that I've shared.
Once fastboot mode is on the device is automatically restarted in about 10 to 15 sec and within this time MiFlash tool or adb cmd prompt bot does not recognise my device.
I have tried to flash OTA via adb side load but it is showing error.
Help me with your input!
MrUsamahh said:
Hy man, I know basic of adb and I use cmd "adb devices"
My device is recognised when it is on.
I can also give various cmd like boot in recovery or fastboot mode or reboot and the device follow the instructions.
Please see the video that I've shared.
Once fastboot mode is on the device is automatically restarted in about 10 to 15 sec and within this time MiFlash tool or adb cmd prompt bot does not recognise my device.
I have tried to flash OTA via adb side load but it is showing error.
Help me with your input!
Click to expand...
Click to collapse
Your device doesn't get detected in your CMD prompt when it's in fastboot AND you type "fastboot devices"?
If it doesnt then you might have flashed something incorrectly.
Also, make sure to have your android drivers up to date in your pc. It's very, very likely that you don't have them installed on your PC, or they are outdated. See this: https://developer.android.com/studio/run/oem-usb.html
And this: https://developer.android.com/studio/releases/platform-tools.html
I have faced this issue. Yesterday i dirty flashed a custom rom. but i forgot how to dirty flash. i just simply flashed the rom and restarted the phone. it was mandatory to flash custom recovery and gapps after flashing a rom dirtily or normally. but i didn't. After the reboot completed, i remembered that i didn't flashed the twrp and gapps. So, i go back recovery mod, guessed i could flash twrp now. But i didn't see any custom recovery on my phone. But the phone boots, and i can use the phone. Still, i'm on that phone, while i'm typing this comment. i didn't lost my data cause i flashed dirtily. But the problem is, as i didn't flashed gapps or magisk (for root access), now i can't use google apps like, play store, and more. As i don't have root access on my phone so, i can't run flasify, to flash custom recovery. neither i can run other apps that need root. As i didn't flash custom recovery, now i can't flash gapps, magisk and whatever that needs a custom recovery.
I told some rom porter about the matter. They told me to flash stock rom. So, i was trying to flash stock rom. but flashing stock rom requires a fastboot mode. But my fastboot logo doesn't appear and it's blank. I told this to a rom porter. But he said, He doesn't know about that and he can't help.
I'm trying to install TWRP recovery on my essential phone. this is the guide i am using, though pretty much every guide i found follows the same commands:
https://android.gadgethacks.com/how-to/install-twrp-recovery-essential-ph-1-0187660/
The command to determine my current slot returned that i am on slot_b, and when i try to flash the twrp img to slot_a, it sits trying to write. it never crashes but doesn't get anywhere. nothing is happening either in the command prompt window or on the phone screen.
I'm not sure what the issue is. I've updated the android sdk to the newest version and confirmed that I'm using that version of fastboot. I've also updated essential's windows drivers for the device, and rebooted the bootloader several times.
EDIT: I have noticed that on the phone screen when in the bootloader, it says "SECURE BOOT - yes". i don't know if this is important, but when i ran "fastboot oem device-info" it said true for unlocked and unlocked-critical.
Ricx94 said:
I'm trying to install TWRP recovery on my essential phone. this is the guide i am using, though pretty much every guide i found follows the same commands:
https://android.gadgethacks.com/how-to/install-twrp-recovery-essential-ph-1-0187660/
The command to determine my current slot returned that i am on slot_b, and when i try to flash the twrp img to slot_a, it sits trying to write. it never crashes but doesn't get anywhere. nothing is happening either in the command prompt window or on the phone screen.
I'm not sure what the issue is. I've updated the android sdk to the newest version and confirmed that I'm using that version of fastboot. I've also updated essential's windows drivers for the device, and rebooted the bootloader several times.
EDIT: I have noticed that on the phone screen when in the bootloader, it says "SECURE BOOT - yes". i don't know if this is important, but when i ran "fastboot oem device-info" it said true for unlocked and unlocked-critical.
Click to expand...
Click to collapse
Have you the latest twrp.img from the twrp.me site?
Do you have a type c to USB connector thing? Bluetooth keyboard?
If yes, fastboot flash boot twrp.img.
You might need the Bluetooth keyboard in case of not having touch response.
dirtyreturn said:
Have you the latest twrp.img from the twrp.me site?
Do you have a type c to USB connector thing? Bluetooth keyboard?
If yes, fastboot flash boot twrp.img.
You might need the Bluetooth keyboard in case of not having touch response.
Click to expand...
Click to collapse
i do have the newest file. i even tried redownloading it thinking the file might have been corrupted.
i haven't gotten to the part where i would need a usb otg keyboard yet, though i have one for when i make it that far.
I would check out the PH1 Development Telegram Channel as if your on stock they have boot images with TWRP and root already added and then all you have to do is fastboot flash the patched image and you will have TWRP with working touch and root as well. Here is the link to the channel if your interested https://t.me/EssentialPH1DEV
dirtyreturn said:
Have you the latest twrp.img from the twrp.me site?
Do you have a type c to USB connector thing? Bluetooth keyboard?
If yes, fastboot flash boot twrp.img.
You might need the Bluetooth keyboard in case of not having touch response.
Click to expand...
Click to collapse
robertbarber said:
I would check out the PH1 Development Telegram Channel as if your on stock they have boot images with TWRP and root already added and then all you have to do is fastboot flash the patched image and you will have TWRP with working touch and root as well. Here is the link to the channel if your interested https://t.me/EssentialPH1DEV
Click to expand...
Click to collapse
I'm not having issues with touch yet. haven't even made it far enough to know if I'm having an issue with touch in twrp...
I can't flash anything for some reason.
I'm stuck at "Sending 'boot_b' (48712 KB)" and nothing happens. every post I've seen says this should take less than 2 seconds but I've waited up to 10 minutes some tries and nothing happens. i need to restart the bootloader after trying this each time before it will let me try again.
Ricx94 said:
I'm not having issues with touch yet. haven't even made it far enough to know if I'm having an issue with touch in twrp...
I can't flash anything for some reason.
I'm stuck at "Sending 'boot_b' (48712 KB)" and nothing happens. every post I've seen says this should take less than 2 seconds but I've waited up to 10 minutes some tries and nothing happens. i need to restart the bootloader after trying this each time before it will let me try again.
Click to expand...
Click to collapse
Did you do the two unlock commands via fastboot? Firstly.?(not intending to dumb you down or anything)
Did you try with just - fastboot flash boot twrp.img ?
P.S. !! Definitely check out the posted telegram channel! Super helpful group of people.
dirtyreturn said:
Did you do the two unlock commands via fastboot? Firstly.?(not intending to dumb you down or anything)
Did you try with just - fastboot flash boot twrp.img ?
P.S. !! Definitely check out the posted telegram channel! Super helpful group of people.
Click to expand...
Click to collapse
I did fastboot flashing unlock and unlock_critical. Those seemed to work it shows up as being unlocked and factory reset.
To try to flash twrp I ran fastboot flash boot_a (also tried boot_b and boot) twrp.img and it tried to send but just sits trying and isn't getting anywhere.
Ricx94 said:
I did fastboot flashing unlock and unlock_critical. Those seemed to work it shows up as being unlocked and factory reset.
To try to flash twrp I ran fastboot flash boot_a (also tried boot_b and boot) twrp.img and it tried to send but just sits trying and isn't getting anywhere.
Click to expand...
Click to collapse
https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
Ricx94 said:
I did fastboot flashing unlock and unlock_critical. Those seemed to work it shows up as being unlocked and factory reset.
To try to flash twrp I ran fastboot flash boot_a (also tried boot_b and boot) twrp.img and it tried to send but just sits trying and isn't getting anywhere.
Click to expand...
Click to collapse
Are you using cmd or power shell for Windows. What ports are you using,2.0 or 3.0 and which type of cord. A-c or c-c
Sent from my PH-1 using Tapatalk
dazeone said:
Are you using cmd or power shell for Windows. What ports are you using,2.0 or 3.0 and which type of cord. A-c or c-c
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
I've tried both CMD and Powershell
my computer only has USB 3.0 and 3.1 ports, all type A, so I'm using USB A-C cables. the cables are both only USB 2.0.
so I'm not sure why i tried this but it seemed to work...
I sent the flash command and when it got to the part it normally freezes at, i restarted the bootloader using volume and power keys on the phone. then while it was restarting i sent the command again, and as soon as it got to the bootloader the command activated and worked instantly. now I'm toying around with this newfound knowledge and i think i have twrp working. just wiped phone again and installed AOSIP so here we go
Ricx94 said:
so I'm not sure why i tried this but it seemed to work...
I sent the flash command and when it got to the part it normally freezes at, i restarted the bootloader using volume and power keys on the phone. then while it was restarting i sent the command again, and as soon as it got to the bootloader the command activated and worked instantly. now I'm toying around with this newfound knowledge and i think i have twrp working. just wiped phone again and installed AOSIP so here we go
Click to expand...
Click to collapse
Sorry... I didn't read...
When you are stuck at waiting for device .. if you unplug... Run the command... And then plug in... It will sometimes take...
Why... I don't know
Sent from my PH-1 using Tapatalk
Ricx94 said:
so I'm not sure why i tried this but it seemed to work...
I sent the flash command and when it got to the part it normally freezes at, i restarted the bootloader using volume and power keys on the phone. then while it was restarting i sent the command again, and as soon as it got to the bootloader the command activated and worked instantly. now I'm toying around with this newfound knowledge and i think i have twrp working. just wiped phone again and installed AOSIP so here we go
Click to expand...
Click to collapse
Nice to hear! Be sure to have the twrpinstaller.zip handy to flash after the ROM!! This preserves twrp.
rignfool said:
Sorry... I didn't read...
When you are stuck at waiting for device .. if you unplug... Run the command... And then plug in... It will sometimes take...
Why... I don't know
Click to expand...
Click to collapse
I need to send the command while the bootloader is restarting. It works consistently for me. Unplugging and repluging won't do it; only restarting bootloader. I honestly can't explain it but it's working great.
Ricx94 said:
I need to send the command while the bootloader is restarting. It works consistently for me. Unplugging and repluging won't do it; only restarting bootloader. I honestly can't explain it but it's working great.
Click to expand...
Click to collapse
HOLY CRAP THANK YOU
I've been going insane and this worked for whatever reason. You are awesome!
Zach Alt said:
HOLY CRAP THANK YOU
I've been going insane and this worked for whatever reason. You are awesome!
Click to expand...
Click to collapse
Glad i could be of service