Database Users

Hong Kong 1.29.708.16

Does anyone have a backup, recovery or RUU of 1.29.708.16? I flashed the wrong RUU and now it's stuck in bootloader.

justinw1997 said:
Does anyone have a backup, recovery or RUU of 1.29.708.16? I flashed the wrong RUU and now it's stuck in bootloader.
Click to expand...
Click to collapse
I don't think any exist yet and your best bet would to push the stock 1.29.401.16 from the development thread using adb push and flash the zip with cwm or trwp to get you back up and running.

daleski75 said:
I don't think any exist yet and your best bet would to push the stock 1.29.401.16 from the development thread using adb push and flash the zip with cwm or trwp to get you back up and running.
Click to expand...
Click to collapse
okay thank you

justinw1997 said:
i didn't back up my phone
Click to expand...
Click to collapse
Can you get into recovery?
When you plug your phone into your pc can you browse storage?
If yes to both of the above, download and flash the zip from the link below.
http://forum.xda-developers.com/showthread.php?t=2224752

daleski75 said:
Can you get into recovery?
When you plug your phone into your pc can you browse storage?
If yes to both of the above, download and flash the zip from the link below.
http://forum.xda-developers.com/showthread.php?t=2224752
Click to expand...
Click to collapse
no, i can't. when i enter recovery the phone reboots and it goes to the bootloader screen. is it possible to flash a custom ROM to get my phone working? i don't mind what rom i use now as long as i get out of this..

justinw1997 said:
no, i can't. when i enter recovery the phone reboots and it goes to the bootloader screen. is it possible to flash a custom ROM to get my phone working? i don't mind what rom i use now as long as i get out of this..
Click to expand...
Click to collapse
If you can get into fastboot then download cwm recovery as a .img file, then make sure it says fastboot usb on the white screen and type.
fastboot-windows flash recovery name_of_file.img then power off the phone and power it back on and see if you can then get into recovery if that works you can then use adb push to push a zip to the phone and flash using the newly written recovery.

daleski75 said:
If you can get into fastboot then download cwm recovery as a .img file, then make sure it says fastboot usb on the white screen and type.
fastboot-windows flash recovery name_of_file.img then power off the phone and power it back on and see if you can then get into recovery if that works you can then use adb push to push a zip to the phone and flash using the newly written recovery.
Click to expand...
Click to collapse
Thanks for the reply.
I downloaded recovery-clockwork-6.0.3.1-m7.img so do I open up command prompt and type:
"fastboot-windows flash recovery recovery-clockwork-6.0.3.1-m7.img" in a single line?

justinw1997 said:
Thanks for the reply.
I downloaded recovery-clockwork-6.0.3.1-m7.img so do I open up command prompt and type:
"fastboot-windows flash recovery recovery-clockwork-6.0.3.1-m7.img" in a single line?
Click to expand...
Click to collapse
Yup

daleski75 said:
Yup
Click to expand...
Click to collapse
Strange I just use -> fastboot flash recovery CWM.img
where does the fastboot-windows come from ?

daleski75 said:
Yup
Click to expand...
Click to collapse
Thanks for the reply. I placed the file recovery.img file into my desktop and i opened command prompt to the desktop and typed what you told me to. It gave the message "'fastboot' is not recognized as an internal or external command". I'm pretty sure i plugged in my phone correctly as it says fastboot usb on the screen.

justinw1997 said:
Thanks for the reply. I placed the file recovery.img file into my desktop and i opened command prompt to the desktop and typed what you told me to. It gave the message "'fastboot' is not recognized as an internal or external command". I'm pretty sure i plugged in my phone correctly as it says fastboot usb on the screen.
Click to expand...
Click to collapse
is fastboot on the desktop along with the recovery.img?
if so the command is -> fastboot flash recovery recovery.img
point is all the files have to be in one place togather

daleski75 said:
Yup
Click to expand...
Click to collapse
btw, i'm using a windows PC as i used a mac before which is the reason i got into this mess in the first place

clsA said:
is fastboot on the desktop along with the recovery.img?
if so the command is -> fastboot flash recovery recovery.img
point is all the files have to be in one place togather
Click to expand...
Click to collapse
I extracted the fastboot file folder that i got from (http://theunlockr.com/2013/03/19/how-to-install-clockworkmod-recovery-on-the-htc-one-m7/) and i put the files onto my desktop.
it gave me the message: FAILED <remote: signature verify fail>

justinw1997 said:
btw, i'm using a windows PC as i used a mac before which is the reason i got into this mess in the first place
Click to expand...
Click to collapse
Yeah. I put parallels on mine the instance I got it so I don't have to worry about things like that and have the benefit of both OSs
Sent from the one and only HTC One

bb

justinw1997 said:
Thanks for the reply. I placed the file recovery.img file into my desktop and i opened command prompt to the desktop and typed what you told me to. It gave the message "'fastboot' is not recognized as an internal or external command". I'm pretty sure i plugged in my phone correctly as it says fastboot usb on the screen.
Click to expand...
Click to collapse
I assume you have fastboot binaries for windows?

daleski75 said:
I assume you have fastboot binaries for windows?
Click to expand...
Click to collapse
nope, didn't install it on this windows pc. i'm downloading the adt bundle from android developers now.

justinw1997 said:
nope, didn't install it on this windows pc. i'm downloading the adt bundle from android developers now.
Click to expand...
Click to collapse
the instructions on the link you got fastboot from above are spot on
if you did what's their I can't imagine where the problem would be.
you don't need the full SDK just to fastboot a recovery to your phone
---------- Post added at 09:50 AM ---------- Previous post was at 09:47 AM ----------
daleski75 said:
I assume you have fastboot binaries for windows?
Click to expand...
Click to collapse
his link above has full instructions for a windows install

clsA said:
the instructions on the link you got fastboot from above are spot on
if you did what's their I can't imagine where the problem would be.
you don't need the full SDK just to fastboot a recovery to your phone
---------- Post added at 09:50 AM ---------- Previous post was at 09:47 AM ----------
his link above has full instructions for a windows install
Click to expand...
Click to collapse
has my problem got anything to do with the fact that i'm using a new windows pc?
on my phone it says:
TAMPERED
RELOCKED
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.13
....
FAST BOOT USB
....
...
..
BOOTLOADER (highlighted)
REBOOT
....
...
My error message from CMD is attached

justinw1997 said:
has my problem got anything to do with the fact that i'm using a new windows pc?
on my phone it says:
TAMPERED
RELOCKED
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.13
....
FAST BOOT USB
....
...
..
BOOTLOADER (highlighted)
REBOOT
....
...
My error message from CMD is attached
Click to expand...
Click to collapse
You have to unlock your bootloader again.

Nexus 7 2012 (GSM) Booting Failed/No OS

i have access to ADB and fastboot mode.
i also try google factory image(see the attach picture for the result)

niceguy01 said:
i have access to ADB and fastboot mode.
i also try google factory image(see the attach picture for the result)
Click to expand...
Click to collapse
Yes, me too. I can't load anything except ADB & Fastboot. I used the Nexus 7 Toolkit to try to update to Kit Kat and now I have a soft bricked device. HELP!!!:crying:

Have you tried using adb shell command prompt to push the files to your device instead of a root toolkit?

cr0wnest said:
Have you tried using adb shell command prompt to push the files to your device instead of a root toolkit?
Click to expand...
Click to collapse
what file do i need to push in my device??

Effing toolkits again. When will they be banned for once and for all?
Oh that's right. They bring in ad revenue from lazy people.
Sent from my Nexus 5

niceguy01 said:
what file do i need to push in my device??
Click to expand...
Click to collapse
Check out this sticky here, it gives instructions on how to do it and what files are required. Its quite a lengthy guide, but its the safest method. http://forum.xda-developers.com/showthread.php?t=1907796

Pirateghost said:
Effing toolkits again. When will they be banned for once and for all?
Oh that's right. They bring in ad revenue from lazy people.
Sent from my Nexus 5
Click to expand...
Click to collapse
sorry im just a newbie:angel:

UPDATE: booting failed already gone by flashing cyanogen rom
the problem now is stuck in booting.see the attach picture
what is the meaning of
archive does not contain boot.sig
archive does not contain recovery.sig
archive does not contain system.sig

Got the same problem...I used RTK to flash 4.4 and ended up with a soft bricked N7.
Well initially I haven't been able to update any newer versions of CM. I was stuck on 10.2 nightly. I got a notification that there's an update so I downloaded it and tried installing. I get stuck when my N7 will go into recovery, I'll always get the droid with the red exclamation point and I have to stop the update. But I will always be able to do a system reboot and use the N7. After flashing using the RTK, all I can do is boot into the Bootloader mode. Choice at that point it Recovery, Reboot Recovert, Reboot Bootloader and Power Off. If I choose Recovery nothing happens. So the real choice is only to power off or reboot the bootloader.
I tried using fast boot but the guide I got was asking me to put the tablet in debugging mode (which I can't really do). And I get an error when doing the steps in CMD. I think I wasn't able to properly load the drivers because I am not seeing my device listed with serial number when I run >dab devices.
Kindda stuck and waiting where this thread will lead to as well so I can fix my N7.
Also, when I get the factory image (JWR66V) and run 7-zip on it, I don't see these files: bootloader-grouper-4.23.img, image-nakasi-jwr66y.zip, flash-all.sh, flash-base.sh. I only see 1 file.

As mentioned in about 5 billion threads, USB debugging has nothing to do outside of a booted OS.
Fix your drivers.
Unzip the factory image archive.
Sent from my Nexus 5

^Fixed my drivers (via SDK). PC recognised the device via fast boot devices. Ran a set of commands fast boot erase boot, cache, recovery, system, and user data. Flashed boot loader and reboot boot loader. Flashed 4.3 factory image (extracted via 7zip). Flashing/Update FAILED (I think the error was 'too mani links') and it went back to a blinking cursor.
@niceguy01 - just wait for CMD to process the entire thing. I was worried as well when I saw the system does not contain boot.sig etc error. Waited for it and started getting some scripts after. Wasn't able to complete the flash though but little steps getting there.

where should i flash radio.img?
boot,bootloader,recovery.system or userdata??see the picture
thanks

None of the above
Sent from my Nexus 5

Pirateghost said:
None of the above
Sent from my Nexus 5
Click to expand...
Click to collapse
thanks:good:

finally i got manage to fix my N7,thanks anyone who help me:good:
-----------thread close------------
i use google nexus toolkit v4 and install sdk drivers

[GUIDE] How to Unlock the Bootloader, Flash a Factory Image, and Return to Stock

This guide will help you unlock your bootloader, flash a factory image, and return you to a stock device. It is wriiten assuming you have a windows PC (MAC users, see post 2). This can be helpful if you need to RMA your device or if you are getting erratic behavior or messed something up.
Tools and Files You’ll Need
If you don’t have adb and fastboot installed on your PC go here for a quick install of the necessary files, thanks to @Snoop05, http://forum.xda-developers.com/showthread.php?t=2588979
For MAC users go here. http://forum.xda-developers.com/showthread.php?p=32305619
For Linux users, http://forum.xda-developers.com/showthread.php?p=10746225
For the factory image go here, https://developers.google.com/android/nexus/images You’ll download a .tgz file. Use winrar or 7-zip to extract the file to its own directory and remember where that directory is. Inside is another zip file, extract that too. You’ll need those image files if you use the long method to install the factory image. It’s also good to know where they are as they come in handy as you get more familiar with fastboot and what you can do with it.
How To Unlock the Bootloader
If you don’t have developer options enabled on your device go to settings, about device and tap on the build number 7 times.
In settings, developer options enable oem unlock
Now you get to use fastboot! Boot you device into the bootloader, vol up + power with your device shut off. Once booted into the bootloader connect it to your PC with the usb cable and open a command window on your PC. Once connected type the following command in the cmd window:
fastboot devices (Your device serial number should show up and this will ensure fastboot is working properly)
​Then type:
​fastboot oem unlock (This will unlock the bootloader and you’re now good to go)​
NOTE, UNLOCKING THE BOOTLOADER DOES WIPE YOUR DEVICE SO BACKUP OFF YOUR DEVICE FIRST
How To Flash the Factory Image, SHORT METHOD
Open a command window on your PC in the same directory as you extracted the factory image. In that directory shift, right click in an open area and use “Open a command window here”
Boot your device into the bootloader and connect it to your PC. Then simply double click on the flash-all batch file. Note that there are batch files in there that will work for Windows as well as Linux machines
Let the batch file run and when it’s done you’ll be back to stock.
NOTE THAT FLASHING BY THIS METHOD DOES WIPE YOUR DEVICE SO MAKE SURE YOU BACKUP OFF YOUR DEVICE FIRST.
How To Flash the Factory Image, LONG METHOD
In this method each factory image is flashed separately. This should be used if you have problems with the short method and as you get more familiar with fastboot you’ll be able to flash only the images that you need for your specific requirement. For instance, you might want to only flash the stock recovery if you’re trying to take an ota and you’ve installed a custom recovery. The order that you flash the images is not important.
In the folder you extracted the factory image it’s easiest if you re-name the bootloader image file to simply bootloader and radio. Then open a Windows command window in that folder and use the fastboot commands:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot –w (NOTE, this command does wipe your device. It’s possible to flash the factory image without this command but if you’re going from different revision numbers of android it’s highly recommend to wipe the device)
Now open a Windows command window in the same folder that you extracted the zip file in, the one where you find recovery, system, etc. Then run the fastboot commands:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img [Note, flashing system takes a long time, so let it do it's thing]
fastboot flash vendor vendor.img
Congratulations, you’ve now flashed a factory image and learned how to use fastboot!

For MAC users, proceed each fastboot command with a ./ e.g. ./fastboot flash boot boot.img

This should be made a 'sticky'...
An excellent well written tutorial... succinct, clear and to the point.
Far better to use fastboot instead of a toolkit... Everything is more transparent, and you actually gain a better understanding of your device as a result.
Rgrds,
Ged.

GedBlake said:
This should be made a 'sticky'...
An excellent well written tutorial... succinct, clear and to the point.
Far better to use fastboot instead of a toolkit... Everything is more transparent, and you actually gain a better understanding of your device as a result.
Rgrds,
Ged.
Click to expand...
Click to collapse
Thanks @GedBlake. I would have responded sooner but I had to get home and check my tablet. Actually both work, vol up + power and vol down + power.
Sent from my Nexus 9 using XDA Free mobile app

But.... Toolkit so easy?
(agreed... Toolkits not the best choice)
Thread stuck. Great guide @jd1639!
If we get enough guides, tutorials, how to's and other great info threads.... I would suggest a "sticky roll up" thread, so too many stickies aren't created.
Food for thought.
Edit : That ^^^^ was a hint to other members to get your guides, tutorials, info threads, FAQ... Etc... Going..... This is a Nexus section after all. :silly:

Darth said:
But.... Toolkit so easy? ?
(agreed... Toolkits not the best choice)
Thread stuck. Great guide @jd1639! ?
If we get enough guides, tutorials, how to's and other great info threads.... I would suggest a "sticky roll up" thread, so too many stickies aren't created.
Food for thought. ?
Click to expand...
Click to collapse
I'll keep an eye it and do a roll up when the need arises
Sent from my Nexus 9 using XDA Free mobile app

cant flash system.img
I Xubuntu 14.04 I can't seem to flash the system.img I get the following error
sending 'system' (1108544 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.032s

nyasha1935 said:
I Xubuntu 14.04 I can't seem to flash the system.img I get the following error
sending 'system' (1108544 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.032s
Click to expand...
Click to collapse
It's possible that you need to update your Android SDK to the latest. There was a recent change (within last 6 months) to fastboot to allow flashing these large .img files.

cam30era said:
It's possible that you need to update your Android SDK to the latest. There was a recent change (within last 6 months) to fastboot to allow flashing these large .img files.
Click to expand...
Click to collapse
Ok thanks gonna try on windows, im a noob on linux

nyasha1935 said:
Ok thanks gonna try on windows, im a noob on linux
Click to expand...
Click to collapse
You'll be sorry.....

cam30era said:
You'll be sorry.....
Click to expand...
Click to collapse
Ok back to linux, how do I update android SDK

nyasha1935 said:
Ok back to linux, how do I update android SDK
Click to expand...
Click to collapse
http://rootzwiki.com/topic/20770-gu...-adb-and-fastboot-in-linux-ubuntu-and-mint12/

Is it possible to flash a factory image using a custom recovery like TWRP?
Sent from my Nexus 9 using Tapatalk

iamroddo said:
Is it possible to flash a factory image using a custom recovery like TWRP?
Click to expand...
Click to collapse
Is it possible to extract the .img from the volantis-lmy47x-factory-3efdc8d4.tgz from https://developers.google.com/android/nexus/images and flash them individually with TWRP (with the exception of recovery.img, which I guess would over-write TWRP)? Can it this be done directly from 5.0.1 or would I need to first upgrade to 5.02?

Hi, I'm Italian so i'm sorry if my english is bad xD what happens if i flash a different kernel? Will i lose my warranty?
If yes, if i flash the factory image, will i have my warranty again?
And, again, sorry for my bad english

Leoncino said:
Hi, I'm Italian so i'm sorry if my english is bad xD what happens if i flash a different kernel? Will i lose my warranty?
If yes, if i flash the factory image, will i have my warranty again?
And, again, sorry for my bad english
Click to expand...
Click to collapse
No need top apologize. You're English if fine.
There's a lot of discussion and lack of agreement about what affects the warranty on the Nexus 9. HTC says that even unlocking the bootloader "may void the warranty".
My advice would be to do what you want to it, but make sure you understand what you are doing. Ask a lot of questions before you do something you're unsure of.
Unlock your bootloader (if you haven't already). Do not relock bootloader if something goes wrong (this does not solve anything). With an unlocked bootloader, you can recover from almost any problem.
And you can flash the Google factory images anytime you want to return to stock.
I'm sorry there's not a clear answer to your question.

cam30era said:
No need top apologize. You're English if fine.
Click to expand...
Click to collapse
Thanks
So it's like Samsung knox, we don't know what happens to our device.
An other little question? Is the same if i root my device? Need to unlock bootloader?

Leoncino said:
Thanks
So it's like Samsung knox, we don't know what happens to our device.
An other little question? Is the same if i root my device? Need to unlock bootloader?
Click to expand...
Click to collapse
Bootloader has to be unlocked to root, install custom recovery (TWRP). And note that when you unlock bootloader, it will wipe the contents of your SDcard. If you have anything important there, back it up on your PC.

cam30era said:
Bootloader has to be unlocked to root, install custom recovery (TWRP). And note that when you unlock bootloader, it will wipe the contents of your SDcard. If you have anything important there, back it up on your PC.
Click to expand...
Click to collapse
And what happens if i lock again my bootloader, will i restore the warranty?

Leoncino said:
And what happens if i lock again my bootloader, will i restore the warranty?
Click to expand...
Click to collapse
That's a good question, without a clear answer (unfortunately).

Need some help with flashing Oreo B3

Hi.
I was having trouble when I try to follow the method on essential's site.
Here's what adb told me:
"opening 'ota_file.zip'...
connecting...
falling back to older sideload method...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information."
Did some research on google. But sadly still don't know how this happened. Plz, help me, if you know what to do. thx

I suggest trying to flash the stock dump OB3 from here:
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
I assume you already unlocked the bootloader.
You will need to unlock critical as well, but if you got ADB up and running already, should be easy.
Download and unzip the OB3 dump.
Unzip and place all files where fasboot is placed, should be platform-tools.
fastboot flashing unlock_critical (will wipe entire phone)
Then run the flash-all.bat in terminal (you can just drag and drop the flash-all file into terminal)
If successful, run fastboot -w to format data just for good measure.
If unsuccessful, open the flash-all in a text editor and copy paste the commands one at a time in terminal, enter after each one.
If not able to get either to work, DO NOT REBOOT. ask for more help.

q13017 said:
Hi.
I was having trouble when I try to follow the method on essential's site.
Here's what adb told me:
"opening 'ota_file.zip'...
connecting...
falling back to older sideload method...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information."
Did some research on google. But sadly still don't know how this happened. Plz, help me, if you know what to do. thx
Click to expand...
Click to collapse
Normally you should be able to adb sideload with a locked bootloader and the original recovery.
Try another computer or USB-C cable, and yes USB-C cable quality does make a big difference.
Double check these
1. Bad drivers (i.e dont use Leca driver, but Google usb driver)
2. Bad USB Cable
3. Too outdated adb version
4. Bad flashable zip download

jamesst20 said:
Normally you should be able to adb sideload with a locked bootloader and the original recovery.
Try another computer or USB-C cable, and yes USB-C cable quality does make a big difference.
Double check these
1. Bad drivers (i.e dont use Leca driver, but Google usb driver)
2. Bad USB Cable
3. Too outdated adb version
4. Bad flashable zip download
Click to expand...
Click to collapse
I just wait until the bts is available. I've had bad luck sideload in.
Sent from my PH-1 using XDA Labs

avd said:
I just wait until the bts is available. I've had bad luck sideload in.
Click to expand...
Click to collapse
I have gotten the essential today and the first thing I did is flash Android O and everything seems flawless

avd said:
I just wait until the bts is available. I've had bad luck sideload ing.
Click to expand...
Click to collapse
And if your bootloader is locked you can't fallback to other methods of your system goes wonky even if we have an a/b system.
Sent from my PH-1 using XDA Labs

Airwolf79 said:
I suggest trying to flash the stock dump OB3 from here:
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
I assume you already unlocked the bootloader.
You will need to unlock critical as well, but if you got ADB up and running already, should be easy.
Download and unzip the OB3 dump.
Unzip and place all files where fasboot is placed, should be platform-tools.
fastboot flashing unlock_critical (will wipe entire phone)
Then run the flash-all.bat in terminal (you can just drag and drop the flash-all file into terminal)
If successful, run fastboot -w to format data just for good measure.
If unsuccessful, open the flash-all in a text editor and copy paste the commands one at a time in terminal, enter after each one.
If not able to get either to work, DO NOT REBOOT. ask for more help.
Click to expand...
Click to collapse
Just wondering if I can delete -w to save user data? LIke the old day nexus devices.

jamesst20 said:
Normally you should be able to adb sideload with a locked bootloader and the original recovery.
Try another computer or USB-C cable, and yes USB-C cable quality does make a big difference.
Double check these
1. Bad drivers (i.e dont use Leca driver, but Google usb driver)
2. Bad USB Cable
3. Too outdated adb version
4. Bad flashable zip download
Click to expand...
Click to collapse
Thx for the help,
1. I used the one provided on the official website.
2. The one comes with the phone. (My motherboard do support Type-c Male to Male )
3. I'm pretty sure it is the newest version.
4. Maybe...

q13017 said:
Just wondering if I can delete -w to save user data? LIke the old day nexus devices.
Click to expand...
Click to collapse
It only works with fastboot factory images. These are recovery flashable zip as far as I know.
Also, you need unlocked bootloader to flash factory images and in case you are already unlocked, you could just push the zip into your phone and use twrp to flash it.
q13017 said:
Thx for the help,
1. I used the one provided on the official website.
2. The one comes with the phone. (My motherboard do support Type-c Male to Male )
3. I'm pretty sure it is the newest version.
4. Maybe...
Click to expand...
Click to collapse
You could try booting your phone with usb debugging enabled and see if the command "adb push file.zip /sdcard/Download"
If this command fail aswell, it's probably driver related or cable. I don't think an invalid zip would make it fail

q13017 said:
Thx for the help,
1. I used the one provided on the official website.
2. The one comes with the phone. (My motherboard do support Type-c Male to Male )
3. I'm pretty sure it is the newest version.
4. Maybe...
Click to expand...
Click to collapse
The one that change with the phone is not for flashing
Sent from my PH-1 using XDA Labs

avd said:
The one that change with the phone is not for flashing
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
Yeah, don't use the charging cable for flashing. Essential has confirmed that some phones have been bricked using their included cable.
Sent from my PH-1 using Tapatalk

jamesst20 said:
It only works with fastboot factory images. These are recovery flashable zip as far as I know.
Also, you need unlocked bootloader to flash factory images and in case you are already unlocked, you could just push the zip into your phone and use twrp to flash it.
You could try booting your phone with usb debugging enabled and see if the command "adb push file.zip /sdcard/Download"
If this command fail aswell, it's probably driver related or cable. I don't think an invalid zip would make it fail
Click to expand...
Click to collapse
Anyway, fastboot flash method works for me. There's a guy post the dumped image files above. Thx for your help!

q13017 said:
Anyway, fastboot flash method works for me. There's a guy post the dumped image files above. Thx for your help!
Click to expand...
Click to collapse
No problem! Then you had an unlocked bootloader

q13017 said:
Just wondering if I can delete -w to save user data? LIke the old day nexus devices.
Click to expand...
Click to collapse
Doesn't matter. If you use the fastboot method, you need to unlock the bootloader AND unlock critical, which will wipe user data anyway, unless you had already done that previously. You can try the sideload method with stock recovery, but if you're not able to get that to work, you don't have a choice but to unlock and try the fastboot method.

I'm trying to install Beta 3 (I'm coming from stock NMJ51B), but the sideload will end at 94% and I get the Message:
Unable to open sysfs usb node (no such file or directory) Trying configfs failed to set driver control: No such device
Install from ADB complete
The PH-1 will then boot just fine and everything seems to work.
Any ideas?

power-on+volume-up ..bootloader running?
Was problem solved?,I wanted looking for solved of same things.Just I found it's lost my process of running fastboot.

Lenovo TB-X306F and TWRP

Hi
I have been unable to find a TWRP build for my Android device (a Lenovo TB-X306F) anywhere online. I'd like to get into custom romming, which is pretty much impossible without TWRP. Does anyone know if there's a stable, reliable build of TWRP that has been tested to work with this device that carries the smallest risk of bricking my hardware or getting caught in a boot loop, and will allow me to interface with TWRP via ADB shell?
Thanks in advance!

SeedyTeevee said:
Hi
I have been unable to find a TWRP build for my Android device (a Lenovo TB-X306F) anywhere online. I'd like to get into custom romming, which is pretty much impossible without TWRP. Does anyone know if there's a stable, reliable build of TWRP that has been tested to work with this device that carries the smallest risk of bricking my hardware or getting caught in a boot loop, and will allow me to interface with TWRP via ADB shell?
Thanks in advance!
Click to expand...
Click to collapse
me too! did you have any luck?

tkalfaoglu said:
me too! did you have any luck?
Click to expand...
Click to collapse
I'm trying to root my device do you have any suggestions?

Hello231 said:
I'm trying to root my device do you have any suggestions?
Click to expand...
Click to collapse
yeah it was very easy -- download the current firmware for your tablet, extract the boot.img
install the magisk app, then run it..
copy the boot.img to the tablet, tell the app to patch it, download the patch BACK to your pc..
then put the device into fastboot, and run
fastboot flash boot boot_patched.img

BTW, I could not find a TWRP that worked with our device.. it was not necessary anyway.. flashing the boot partition was enough

tkalfaoglu said:
yeah it was very easy -- download the current firmware for your tablet, extract the boot.img
install the magisk app, then run it..
copy the boot.img to the tablet, tell the app to patch it, download the patch BACK to your pc..
then put the device into fastboot, and run
fastboot flash boot boot_patched.img
Click to expand...
Click to collapse
Ok a bit more information for what I tried like 3 months ago
- I downloaded adb and fastboot
-adb was working fastboot was not
-i read about mtk drivers and that they are the problem I did download them but still my tablet doesn't show up in the pc (fastboot devices)
I can't get past that step

when you say that fastboot is not running, why is that?
what error do you get? you know you need to put the tablet into fastboot mode before fastboot will be useful,, right?

tkalfaoglu said:
when you say that fastboot is not running, why is that?
what error do you get? you know you need to put the tablet into fastboot mode before fastboot will be useful,, right?
Click to expand...
Click to collapse
I do exactly this
I open my tablet connect to PC run adb devices it finds my device good
I run adb reboot bootloader it goes on fastboot good
I run fastboot devices it gets stuck at waiting for devices
That is my problem

Hello231 said:
I do exactly this
I open my tablet connect to PC run adb devices it finds my device good
I run adb reboot bootloader it goes on fastboot good
I run fastboot devices it gets stuck at waiting for devices
That is my problem
Click to expand...
Click to collapse
Try different cables (or drivers if you are using windows).. they make a big difference.

tkalfaoglu said:
Try different cables (or drivers if you are using windows).. they make a big difference.
Click to expand...
Click to collapse
Do you have any suggestions on drivers?

Hello231 said:
Do you have any suggestions on drivers?
Click to expand...
Click to collapse
No sorry - I use Linux which doesn't need drivers.