Database Users

I got an engineering machine, but it can't work

I got an engineering machine,
Interface is a native of Android. No,SN.The rest are all the same
Restore factory settings.it reboot, can't work.
Now,How I can get it to fastboot or working .

I think something like this happened with the cr48 Google Chrome netbooks last year someone got one by mistake and I think it helped out being able to flash an alternate bios.
Might want to hold on to this could be a important tool to help the developers out.

yes this is how the hp touchpad got android cyanhogen7mod can you do a full system dump with adb commands and post it here this is very crucial devs where are you.

kolboy said:
I got an engineering machine,
Interface is a native of Android. No,SN.The rest are all the same
Restore factory settings.it reboot, can't work.
Now,How I can get it to fastboot or working .
Click to expand...
Click to collapse
Contact @agrabren (twitter) he put TWRP on the KF and he apparently knows how to boot this thing into fastboot. Furthermore, if you can get into adb you might try pulling out a rom dump and other stuff for development purposes.
Sent from my SPH-D710 using xda premium

PM Sent
Hope you're willing to help us out!
---------- Post added at 02:05 PM ---------- Previous post was at 02:04 PM ----------
pyrostic said:
Contact @agrabren (twitter) he put TWRP on the KF and he apparently knows how to boot this thing into fastboot. Furthermore, if you can get into adb you might try pulling out a rom dump and other stuff for development purposes.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
We already knew how to boot into fastboot.
Code:
adb shell
su
idme bootmode 4002
reboot

death2all110 said:
PM Sent
Hope you're willing to help us out!
---------- Post added at 02:05 PM ---------- Previous post was at 02:04 PM ----------
We already knew how to boot into fastboot.
Code:
adb shell
su
idme bootmode 4002
reboot
Click to expand...
Click to collapse
Sorry this is using a special cable and would get you into fastboot even If you couldn't use adb.
Sent from my SPH-D710 using xda premium

Delete please.

pyrostic said:
Sorry this is using a special cable and would get you into fastboot even If you couldn't use adb.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Can you tell me about the special cable then?

pyrostic said:
Sorry this is using a special cable and would get you into fastboot even If you couldn't use adb.
Click to expand...
Click to collapse
Can you tell me about the special cable then?

kolboy said:
Can you tell me about the special cable then?
Click to expand...
Click to collapse
it's a Motorola "factory cable". I can't really lead you to a place that sells stuff, but I can LMGTFY the link .
http://lmgtfy.com/?q=http://shop.te...-programming-cable-for-Motorola-FactCable.htm

kolboy said:
I got an engineering machine,
Interface is a native of Android. No,SN.The rest are all the same
Restore factory settings.it reboot, can't work.
Now,How I can get it to fastboot or working .
Click to expand...
Click to collapse
same as me, if you know how to solve this problem, please pm me,thanks!

Now,I got zhe special cable into fastboot,
I try to enter a few commands
1. fastboot -i 0x1949 flash boot boot.img
2. fastboot -i 0x1949 flash recovery recovery.img
3. fastboot -i 0x1949 -w
4. fastboot -i 0x1949 boot boot.img
fire reboot, Next pic,i'm load to here,anyboby can help me ?
http://forum.xda-developers.com/atta...1&d=1322807775
Error effect:
MOUNT /CACHE Failure
http://forum.xda-developers.com/atta...1&d=1322807775
/backup/backup_userdata.zip Short of
http://forum.xda-developers.com/atta...1&d=1322807775

anyboby can help me ?

bricked kindle - unlike any other

Situation is this, replaced build.prop file with one from here...it bricked me I believe...
anyways, i get to boot past the logo, then a black screen
adb sees my device, but it doesnt seem to be rooted anymore
cant run adb root or push any files it seems
anyone think of a way to get around this and fix?
thanks

You don't have TWRP installed to mange/install/backup ROMS?

no I do not, I'm an idiot.

Same thing has happened to me. And others I have read on the site too.
No one seems to be able to do anything about it. I tried this http://forum.xda-developers.com/showthread.php?p=20852507.
But all it did was break the adb ability, and instead of a black screen after the splash screen, it changed to just having the splash screen on constantly.
Does anyone have any advice?
---------- Post added at 10:35 AM ---------- Previous post was at 09:59 AM ----------
okay okay. I got somewhere.
Do this: http://forum.xda-developers.com/showpost.php?p=20755810&postcount=1
Then once you have it stuck on splash screen do this:http://rootzwiki.com/topic/12363-ho...our-kindle-fire/page__pid__301703#entry301703
Although ignore the ADB part because I couldn't fastboot with adb and once I did the fbmode thing I couldn't adb but I could fastboot. I am stuck on the yellow triangle at the minute but hopefully I can go from here.
---------- Post added at 10:44 AM ---------- Previous post was at 10:35 AM ----------
taseedorf said:
Situation is this, replaced build.prop file with one from here...it bricked me I believe...
anyways, i get to boot past the logo, then a black screen
adb sees my device, but it doesnt seem to be rooted anymore
cant run adb root or push any files it seems
anyone think of a way to get around this and fix?
thanks
Click to expand...
Click to collapse
Don't give up. There is away around this and it is simple enough.
Read my above posts and try and get somewhere.
I literally just figured it out for myself and we had the exact same problem.
If you need help I just ask. I will keep checking back to see how you get on

Download the fbmode binary and TWRP installation image (twrp-blaze-2.0.0RC0.img).
Extract the stock build.prop from the Amazon update binary (update-kindle-6.2.1_D01E_XXXXXX.bin). Then run the following...
Code:
adb push fbmode /data/local/tmp/
adb shell /data/local/tmp/fbmode
adb reboot
You will then be stuck at the Kindle boot screen. Don't worry though, you are currently in fastboot mode. Now do the following...
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
Your device will reboot to install TWRP recovery. After installation is completed, tap on "Reboot". Once it reboots, you will need to boot into TWRP recovery.
From there, you go to "Mount" and mount the system partition. Then run the following...
Code:
adb push build.prop /system/build.prop
adb shell chown 0.0 /system/build.prop
adb shell chmod 644 /system/build.prop
Now just reboot and you should be set.
If you don't want TWRP and FireFireFire installed, you can install the Amazon update binary via TWRP.

i was figuring the fix was something like that...if it works, ill post my process....please post your donate link so if it does i can buy you some beers

I love you
Thank you so much. Worked like a charm. All I needed to do was chmod 777 to the tmp directory (don't know why...) Problem before, was I was trying to push that to my kindle without it being in fast boot mode, so it always said waiting for device... it was late, so I wonder what I was putting it into...
ANYWAYS, thank you.... and there is another person with this problem I discovered..so you will have helped them too. THANKS!

[Q] Kindle fire Bricked flashing with adb

I have read around and have not found anything, My kinidle is bricked and i want to flash a backup i made with twrp is it possible to do from my computer? Could i just flash the stock rom with adb somehow?

you have to unbrick it and reinstall twrp
what exactly is your problem - explain as close as you can
what have you done ?
fff / twrp installed ?
computer os/bit
status of kf ?

the kindle will just boot to the fff screen i had twrp installed but it wouldnt boot into it. Windows vista 32 bit. it just sits at the fff screen I tried to switch fastboot mode but it would not do anything.

how did you do the fastboot command - manually via command line or with kfu ?
ok - i think you have to wait 5min for next reply
if kfu select option 1 and bootmode normal
if manually do "fastboot -i 0x1949 oem idme bootmode 4000"
if it says <waiting for device> simply power the kf off by holding pwr button for ~20sec
then power on again - the command should resume and finish
restart again and you'r done

I tried it through kfu I tried it and it did nothing

open a elevated command prompt and cd to the tools directory of kfu (eg c:\kfu\tools) - then isue the command above and follow the procedure
---------- Post added at 02:02 AM ---------- Previous post was at 01:39 AM ----------
if that solved your issue
please mark at both of your threads the subject of the topic (edit first post) with [Solved]

Nexus 7 Stuck on Google Logo

Good day everyone,
My friend was updating her Nexus 7 and suddenly the connection went off and the update was stopped. When she booted her Nexus 7, it is stuck on the Google Logo and stays there.
If I press the Volume Down, I can get the Recovery, Bootloader or Shutdown. I tried the Recovery mode but still stuck there.
What to do? Is there anyone that can give me the right steps to get back the Nexus 7?
Thank you a lot.

Flash the stock boot.img using ADB
type “fastboot reboot-bootloader”
type “fastboot flash bootloader bootloader-grouper-3.34.img”
type “fastboot reboot-bootloader”
type “fastboot flash boot boot.img”
Hope this helps

sorry for my ignorance but how to flash the stock boot.img using ADB ?
Sorry again and thank you for your help

Aleksee said:
sorry for my ignorance but how to flash the stock boot.img using ADB ?
Sorry again and thank you for your help
Click to expand...
Click to collapse
Like I just told you, their the actual commands mate.
Open CMD by using Run -> CMD -> (NAVIGATE TO YOUR FOLDER)
E.g. cd c://mydocuments/adb/
Im guessing you have ADB installed, as you've already rooted and flashed.
When in the ADB directory, use
adb devices
With your tablet plugged in and USB Debugging enabled!!!
If this lists your device, then you're all good to go with flashing the boot.img
Hope this helps.
If you get stuck, google Flashing Boot.img with ADB on Android
Or something
---------- Post added at 02:35 PM ---------- Previous post was at 02:34 PM ----------
Or use the GUIDE that is on the first page, just above your post.
http://forum.xda-developers.com/showthread.php?t=1907796
^.-

createprocess failed when i try to fastboot -w

-official drivers installed
-usb debugging is on
-minimal adb/fastboot installed
-bootloader and critical are both unlocked
my phone also shows up in command prompt under both adb devices and fastboot devices. however when i was following the lineage install guide, when i try to do a fastboot -w to wipe userdata, i get "CreateProcess failed" and nothing really happens. what am i missing?

envizion58 said:
-official drivers installed
-usb debugging is on
-minimal adb/fastboot installed
-bootloader and critical are both unlocked
my phone also shows up in command prompt under both adb devices and fastboot devices. however when i was following the lineage install guide, when i try to do a fastboot -w to wipe userdata, i get "CreateProcess failed" and nothing really happens. what am i missing?
Click to expand...
Click to collapse
When you are in fastboot try fastboot reboot bootloader
and then try fastboot -w

i tried it. this is the exact error message i get.
PS C:\> fastboot -w
wiping userdata...
CreateProcess failed: The system cannot find the file specified. (2)
error: Cannot generate image for userdata
i'm using the latest minimal adb fastboot 1.4.3
edit: i figured out the issue. there is something wrong with minimal adb fastboot 1.4.3. Downgrading to 1.4.2 worked flawlessly.

envizion58 said:
i tried it. this is the exact error message i get.
PS C:\> fastboot -w
wiping userdata...
CreateProcess failed: The system cannot find the file specified. (2)
error: Cannot generate image for userdata
i'm using the latest minimal adb fastboot 1.4.3
edit: i figured out the issue. there is something wrong with minimal adb fastboot 1.4.3. Downgrading to 1.4.2 worked flawlessly.
Click to expand...
Click to collapse
the essential drivers install their own adb/fastboot get rid of minimal adb fastboot (uninstall in entirely) it sets a environment variable over top of the essential adb/fastboot environment. see pic

Downgrading worked for me.
envizion58 said:
i tried it. this is the exact error message i get.
PS C:\> fastboot -w
wiping userdata...
CreateProcess failed: The system cannot find the file specified. (2)
error: Cannot generate image for userdata
i'm using the latest minimal adb fastboot 1.4.3
edit: i figured out the issue. there is something wrong with minimal adb fastboot 1.4.3. Downgrading to 1.4.2 worked flawlessly.
Click to expand...
Click to collapse

aer0zer0 said:
the essential drivers install their own adb/fastboot get rid of minimal adb fastboot (uninstall in entirely) it sets a environment variable over top of the essential adb/fastboot environment. see pic
Click to expand...
Click to collapse
This! ^^

Thank you Envizion58!
Your diagnosis of Minimal ADB and Fastboot 1.4.3 being faulty with creating the "userdata" partition was a lifesaver. I've spent DAYS trying to figure out why I couldn't successfully flash an OS to both slots. Only 1 slot would boot, the other simply booted to the bootloader only, as if the boot image was corrupt or something. The only thing I could find was the userdata issue during an update IMG flashing. Anyway, thanks again!
---------- Post added at 04:18 PM ---------- Previous post was at 04:15 PM ----------
JakeSherlock said:
Downgrading worked for me.
Click to expand...
Click to collapse
Me too :good:
---------- Post added at 04:19 PM ---------- Previous post was at 04:18 PM ----------
JakeSherlock said:
Downgrading worked for me.
Click to expand...
Click to collapse
Me too :good:

rocketrazr1999 said:
Your diagnosis of Minimal ADB and Fastboot 1.4.3 being faulty with creating the "userdata" partition was a lifesaver. I've spent DAYS trying to figure out why I couldn't successfully flash an OS to both slots. Only 1 slot would boot, the other simply booted to the bootloader only, as if the boot image was corrupt or something. The only thing I could find was the userdata issue during an update IMG flashing. Anyway, thanks again!
---------- Post added at 04:18 PM ---------- Previous post was at 04:15 PM ----------
Me too :good:
---------- Post added at 04:19 PM ---------- Previous post was at 04:18 PM ----------
Me too :good:
Click to expand...
Click to collapse
WOW. I had the same issue with my Pixel XL trying to flash the stock rom, downgrading worked for me too!

envizion58 said:
i tried it. this is the exact error message i get.
PS C:\> fastboot -w
wiping userdata...
CreateProcess failed: The system cannot find the file specified. (2)
error: Cannot generate image for userdata
i'm using the latest minimal adb fastboot 1.4.3
edit: i figured out the issue. there is something wrong with minimal adb fastboot 1.4.3. Downgrading to 1.4.2 worked flawlessly.
Click to expand...
Click to collapse
Thank you so much. It worked so me too.

envizion58 said:
i tried it. this is the exact error message i get.
PS C:\> fastboot -w
wiping userdata...
CreateProcess failed: The system cannot find the file specified. (2)
error: Cannot generate image for userdata
i'm using the latest minimal adb fastboot 1.4.3
edit: i figured out the issue. there is something wrong with minimal adb fastboot 1.4.3. Downgrading to 1.4.2 worked flawlessly.
Click to expand...
Click to collapse
Thanks .. 1.4.2 worked

Just a word of advice - both from my own experience and from what I read in several threads... When flashing PH-1, always use the fastboot/adb binaries that come bundled with the Essential USB driver. Do NOT use Minimal ADB, Android Platform Tools or any other adb/fastboot package. That will save you from weird errors and failures.

envizion58 said:
-official drivers installed
-usb debugging is on
-minimal adb/fastboot installed
-bootloader and critical are both unlocked
my phone also shows up in command prompt under both adb devices and fastboot devices. however when i was following the lineage install guide, when i try to do a fastboot -w to wipe userdata, i get "CreateProcess failed" and nothing really happens. what am i missing?
Click to expand...
Click to collapse
AS OF 26 AUG 2022
the issue still persists with minimal adb 1.4.3
i tried wiping (fastboot -w)
IT DIDNT WORK
so i deleted that and installed 1.4.2
AND IT WORKED
so just downgrade your version and try, 1.4.3 still hasnt fixed that issue, hope i save yall from banging your heads

@LuK1337 Thanks for maintaining this ROM for OP6. I have a request. When phone is unlocked, status bar shows battery percentage plus 3 icons on right side. However, when screen is locked, it only shows battery percentage plus 1 icon. Can we have same number of icons in status bar when phone is locked?
Thanks!