Database Users

not able to flash factory image!

hey guys,
after a long day og non-success i really need your help here.
i tried to do a factory image restore as described here: http://forum.xda-developers.com/showthread.php?t=1907796
Everything worked fine until it came to the point of flashing the image (fastboot -w update image-nakasi-jop40c.zip). as you can see on screenshot1 it stops working at step "sending system" (i´ve been waiting for 2 hours, nothing happened).
also tried the same procedure with nexus 7 toolkit and nexus root toolkit, but here the same problem mentioned above occurs when "sending bootloader" (see screenshot2).
all in all here is what i´ve got:
working unlocked bootloader (4.13), stock recovery and fastboot - but no system
i hope there´s all the information you need right now and anyone can help me out of this misery.
thanks!

Take a look at this video; it describes everything you need to learn how to use the Nexus 7 Root Toolkit: http://www.youtube.com/watch?v=sK9avekmA1c
Once you figure it out you will also be able to flash the stock ROM to your tablet.
boerni2k said:
hey guys,
after a long day og non-success i really need your help here.
i tried to do a factory image restore as described here: http://forum.xda-developers.com/showthread.php?t=1907796
Everything worked fine until it came to the point of flashing the image (fastboot -w update image-nakasi-jop40c.zip). as you can see on screenshot1 it stops working at step "sending system" (i´ve been waiting for 2 hours, nothing happened).
also tried the same procedure with nexus 7 toolkit and nexus root toolkit, but here the same problem mentioned above occurs when "sending bootloader" (see screenshot2).
all in all here is what i´ve got:
working unlocked bootloader (4.13), stock recovery and fastboot - but no system
i hope there´s all the information you need right now and anyone can help me out of this misery.
thanks!
Click to expand...
Click to collapse

thanks for your answer but this is not helpful. the problem is not that i dont know how to use the tools but somehow the flashing process stops at the points mentioned above and i cant explain why

Maybe your downloaded factory image is corrupted somehow? You could try re-downloading and/or flashing the system.img separately:
fastboot flash system system.img

i already tried that and also let the toolkits download the images themselves but still no success.
when flashing the system.img seperately it still just says sending system.img but nothing happens
trying to flash an older bootloader also failed due to the same problem

Try different cable/USB port/PC. Sounds unlikely but you'd be surprised.

Looks like the 4.13 bootloader has a serious issue with receiving and then flashing data, I keep reading about this....

dave_uk said:
Try different cable/USB port/PC. Sounds unlikely but you'd be surprised.
Click to expand...
Click to collapse
holy cow. it´s always the simple things in life that really matter right? although i already tried different usb ports, there were still others to try and finally it worked!
thanks man! problem solved

boerni2k said:
holy cow. it´s always the simple things in life that really matter right? although i already tried different usb ports, there were still others to try and finally it worked!
thanks man! problem solved
Click to expand...
Click to collapse
Had a very similar situation myself a couple of days where I thought I'd completely murdered by days-old Nexus 7 3G and switching flaming USB ports sorted it. Annoyance and relief in equal measure! Glad it worked for you.
D

Razr M XT 907 - Multiple Problems after flashing with RSD Light

Hey guys so I am facing weird problems. I have searched through the forums either I cant find anything or I am too scared to do any more experiments I really dont want to loose my Razr M XT 907.
Problems
Laggy performance at times
Camera gets stuck when I take pictures at times then I have to restart.
when I reboot my phone it shows AP Fast boot screen, then I have to access boot menu and select the second last option (Console something). It always shows Null:Null and when I change it back the phone reboots normally
Phone hangs sometimes and then responds with everthing I have clicked all at once.
The screen on off button responds a second late
I think you guys can help me better if I tell you what I did to this phone exactly since I got this phone.
What I did
I initially bought this phone with defaul OS 4.0.1 in Pakistan.
I then installed a Verizon system update of 250 MB that got my phone stuck on a boot loop (and made me cry almost)
I restored my phone to the settings it came in using this procedure
http://www.andromods.com/tips-trick/how-to-restore-unroot-droid-razr-m-xt907-stock-original-firmware.html
The phone worked fine for 2 days but then I got that update prompt again and it got annoying so I though maybe If i upgrade it to JB using the same RSD Lite method but a different ROM that may solve it.
So I applied the above Procedure using this ROM
http://forum.xda-developers.com/showthread.php?t=2250155
The method showed as Passed on RSD Lite but the phone got stuck on bootloop again so I paniced and tried restoring my phone abck to ICS using the method mention in the first link provided.
Then the phone got stuck on AP Boot Menu
Then I used DROID_RAZR_M_Utility_1.20 and used both methods 1 and two but it didnt work
Then out of the blue I went to the boot menu and I saw an option Switch Console (Null:null) I pressed up key on and null null changed to default:tty something it and the phone booted up just fine back to ICS
Now everytime I power off the phone it goes to AP Boot menu showing FASTBOOT REASON: Sticky bit factory_fastboot and I have to do the above to restart the phone.
What I need
Please help me restore my phone I dont want to brick it, I am a simple user I will need step by step guide
Anyone ?

Bump
Bump still looking for a solution

I have CM10 on mine and the camera is completely broken

Enter fastboot oem fb_mode_clear and problem gone.

v0ltage112 said:
Hey guys so I am facing weird problems. I have searched through the forums either I cant find anything or I am too scared to do any more experiments I really dont want to loose my Razr M XT 907.
Problems
Laggy performance at times
Camera gets stuck when I take pictures at times then I have to restart.
when I reboot my phone it shows AP Fast boot screen, then I have to access boot menu and select the second last option (Console something). It always shows Null:Null and when I change it back the phone reboots normally
Phone hangs sometimes and then responds with everthing I have clicked all at once.
The screen on off button responds a second late
I think you guys can help me better if I tell you what I did to this phone exactly since I got this phone.
What I did
I initially bought this phone with defaul OS 4.0.1 in Pakistan.
I then installed a Verizon system update of 250 MB that got my phone stuck on a boot loop (and made me cry almost)
I restored my phone to the settings it came in using this procedure
http://www.andromods.com/tips-trick/how-to-restore-unroot-droid-razr-m-xt907-stock-original-firmware.html
The phone worked fine for 2 days but then I got that update prompt again and it got annoying so I though maybe If i upgrade it to JB using the same RSD Lite method but a different ROM that may solve it.
So I applied the above Procedure using this ROM
http://forum.xda-developers.com/showthread.php?t=2250155
The method showed as Passed on RSD Lite but the phone got stuck on bootloop again so I paniced and tried restoring my phone abck to ICS using the method mention in the first link provided.
Then the phone got stuck on AP Boot Menu
Then I used DROID_RAZR_M_Utility_1.20 and used both methods 1 and two but it didnt work
Then out of the blue I went to the boot menu and I saw an option Switch Console (Null:null) I pressed up key on and null null changed to default:tty something it and the phone booted up just fine back to ICS
Now everytime I power off the phone it goes to AP Boot menu showing FASTBOOT REASON: Sticky bit factory_fastboot and I have to do the above to restart the phone.
What I need
Please help me restore my phone I dont want to brick it, I am a simple user I will need step by step guide
Anyone ?
Click to expand...
Click to collapse
I have solution but the android you will flash is android kitkat i don know if do u want reply me if u want to unbrick note: kitkat not supported root

lulz
Adriantech said:
I have solution but the android you will flash is android kitkat i don know if do u want reply me if u want to unbrick note: kitkat not supported root
Click to expand...
Click to collapse
Dude.. you know that you're responding to a thread that is literally a year old right?

cliMAKtic said:
Dude.. you know that you're responding to a thread that is literally a year old right?
Click to expand...
Click to collapse
And wath is the problem i cant help?

Adriantech said:
I have solution but the android you will flash is android kitkat i don know if do u want reply me if u want to unbrick note: kitkat not supported root
Click to expand...
Click to collapse
I also have a solution, but you would need another phone...
But as cliMAKtic said, it's most likely way too late now. Same goes for your replies in other threads.
Adriantech said:
And wath is the problem i cant help?
Click to expand...
Click to collapse
You can, but I'm afraid you won't. You'll rather achieve the opposite by bringing obsoleted threads back to the top.

lem22 said:
I also have a solution, but you would need another phone...
But as cliMAKtic said, it's most likely way too late now. Same goes for your replies in other threads.
You can, but I'm afraid you won't. You'll rather achieve the opposite by bringing obsoleted threads back to the top.
Click to expand...
Click to collapse
ok

PROBLEM Initializing the device

Hi everyone...
I have an awkward issue here with my Nexus 4...
It is in an eternal loop in bootlogo 5.1.1
I already did anything I found in Google search
Flashed ALL firmwares stock, tried some Cyanogenmod and nothing!
I already used simple .bat/.sh in stock folder, used Nexus Toolkit with bricked/bootloop ticked, SkipSoft Tookit and even a tutorial saying to use LGNPST to flash a developer version... this last one worked... but like said in tutorial, the rom is encrypted and the user can do nothing! After that, flashed stock rom and still got stucked in logo!
I did not say, but yes.. I always run ALL wipes
I do not know what else I can do! The phone seems to work normally. I can entry,
download mode, fastboot, recovery but system..
Any ideas?
Thanks for now and sorry about english!

Are you flashing the userdata.img file?

yes and no!
The same result... =/

After flashing userdata.img in fastboot, are you going into recovery using the power and volume buttons to perform a factory wipe?

yes... I already did that too!
Today in the morning, I installed a developer version 4.2 through LGNPST... The phone worked, but it is a old version, I want the last one 5.1.1 and I got the problem that internal memory shows 8GB instead of 16GB...
And I could not resolv this, even reading tutorials from xda forum
If anyone could give me a BIN file of 5.1.1 to use in LGNPST...

no one???

I'm facing the exact same issue, here my post
http://forum.xda-developers.com/nexus-4/help/nexus-4-stuck-animation-android-t3419997
Did u solved it?

No man...
unfortunately I ditched the device!

I've installed Android 4.2.2 and block OTA updates rooting the device, the problem is internally in the device, maybe is a hardware problem, I already made a test of the sensors and none works, for know I'm gonna use it just for phone calls and wapp...
thanks for answer....

Help!! my Angler is dead (bootloop)

I need help, my phone went into a Bootloop. I have tried to flash the factory image (7.0 and 6.0.1) using NRT and manually and still does not pass the Google logo. It does not let me enter the recovery, it only restarts continuously. When flashing the factory image did not give me any error, even the computer detects it in fastboot mode.
All this happened when I was about to open an application and suddenly I shut down and began to restart continuously. I had using android 7.0 stock.

Exact thing happened to me and I flashed both 7 and 6.0.1 and wiped data and caches multiple times.. nothing seems to work.. any ideas?

Tried everything but still bootloops.

Same thing here, although I was on a 7.1 build. There must be a flaw that can cause this to happen in recent build(s), I was trying to share a picture and it froze and bricked like this suddenly. I tried every combination of formatting and flashing stock images and whatnot but no luck.

Seanmiz said:
Same thing here, although I was on a 7.1 build. There must be a flaw that can cause this to happen in recent build(s), I was trying to share a picture and it froze and bricked like this suddenly. I tried every combination of formatting and flashing stock images and whatnot but no luck.
Click to expand...
Click to collapse
Your Nexus 6P uses Samsung eMMC doesn't?

I've seen countless threads here and on reddit about this.
My phone hard bricked last week and I suspect the Samsung emmc is to blame, too many people are having the exact same issue without a solution in sight. I am absolutely unable to access the recovery or anything on the emmc for that matter.
See if you're still covered under warranty (mine was 5 days past its warranty, and Google refused to help), otherwise you're SOL. I think we need to make some noise about it and have AP or another site pick up on this.

darksmartz said:
Your Nexus 6P uses Samsung eMMC doesn't?
Click to expand...
Click to collapse
I believe it was Samsung, yes. I RMA'd it right away after exhausting all flashing efforts.

darksmartz said:
Your Nexus 6P uses Samsung eMMC doesn't?
Click to expand...
Click to collapse
How do I know if my 6p uses Samsung eMMC? What is this, btw?
Edit
Nevermind. I just figured out. Mine is Toshiba, btw.

Rafsxd said:
How do I know if my 6p uses Samsung eMMC? What is this, btw?
Edit
Nevermind. I just figured out. Mine is Toshiba, btw.
Click to expand...
Click to collapse
how did you find this out ? would be nice to tell people so they can check to find out if they will be at risk

brichardson1991 said:
how did you find this out ? would be nice to tell people so they can check to find out if they will be at risk
Click to expand...
Click to collapse
You can find this information on the Bootloader screen listed under eMMC about halfway down the list.

Same problem, samsung memory here

Same for me too,i send my phone back to amazon
Envoyé de mon HUAWEI VNS-L31 en utilisant Tapatalk

Mine uses a Toshiba eMMC and bootloops nevertheless. Not sure if this is actually what's causing it. At this point my only thought is that there was a bad batch of devices as so far no one could find a pattern on what exactly causes the bootloops.

seco2004 said:
Mine uses a Toshiba eMMC and bootloops nevertheless. Not sure if this is actually what's causing it. At this point my only thought is that there was a bad batch of devices as so far no one could find a pattern on what exactly causes the bootloops.
Click to expand...
Click to collapse
Yeah, it doesn't actually seem to be related to eMMC brand. It was very strange, because after it happened, I was able to flash 7.0 stock and regain OS use on a very touchy level. I couldn't access USB connectivity, the home button didn't work most of the time, and if I tried to do too much with it, it would go right back into infinite bootloops. After accomplishing this 2 or 3 times, I could never again get back into the OS.
I could wipe and flash all of the partitions with no errors, I could always get into stock recovery, but TWRP never worked.
Was anyone *not* on the November patch level of v7.0+?

Seanmiz said:
Yeah, it doesn't actually seem to be related to eMMC brand. It was very strange, because after it happened, I was able to flash 7.0 stock and regain OS use on a very touchy level. I couldn't access USB connectivity, the home button didn't work most of the time, and if I tried to do too much with it, it would go right back into infinite bootloops. After accomplishing this 2 or 3 times, I could never again get back into the OS.
I could wipe and flash all of the partitions with no errors, I could always get into stock recovery, but TWRP never worked.
Was anyone *not* on the November patch level of v7.0+?
Click to expand...
Click to collapse
When this first started for me I was on the latest beta build, October security patch.

Same issue here - 64MB Samsung memory.
Google support are aware of the issue, they sent out a replacement no questions asked. For some reason, the guy suggested (but he said unofficially) tapping on the power button. Anybody have any clue why this would be relevant?
Regardless, I'm in a position where I can access fastboot, but nothing else. Can anyone think of any data recovery options at this point?
---------- Post added at 12:26 PM ---------- Previous post was at 12:20 PM ----------
To follow up on my previous post - just before I hit a reboot that threw me into the bootloop, I encountered a hard freeze. I received a bug report after the hard freeze and this is now sitting in my gmail drafts. Would this bug report have any pertinent information here?

thisisgil said:
For some reason, the guy suggested (but he said unofficially) tapping on the power button. Anybody have any clue why this would be relevant?
Click to expand...
Click to collapse
I know exactly why it's relevant!
He's trying to make sure it's not a shoddy power button. My Galaxy SII back in the day had a common power button failure where it would think that you are just constantly hitting/holding the power button if you even breathed on it. My phone would bootloop or suddenly reboot constantly because it was getting power button commands from the poor quality button. Better quality buttons along with other methods of locking/unlocking the phone to reduce power presses have mostly prevented this sort of thing these days.

wifi not working on android p

I've upgraded to Android p and a few minutes ago I've rooted my phone
Since then my wifi won't work, what can I do?
Ok the root did not work

TheZadok42 said:
I've upgraded to Android p and a few minutes ago I've rooted my phone
Since then my wifi won't work, what can I do?
Ok the root did not work
Click to expand...
Click to collapse
Kernel or firmware mismatch
Sent from my PH-1 using Tapatalk

Reflash it
TheZadok42 said:
I've upgraded to Android p and a few minutes ago I've rooted my phone
Since then my wifi won't work, what can I do?
Ok the root did not work
Click to expand...
Click to collapse
Rooting a Beta Rom is usually a bad thing. My only suggestion is reflash following Essential's steps...

Wolfhawke said:
Rooting a Beta Rom is usually a bad thing. My only suggestion is reflash following Essential's steps...
Click to expand...
Click to collapse
Why? Root works fine with it, this has nothing to do with that.

crixley said:
Why? Root works fine with it, this has nothing to do with that.
Click to expand...
Click to collapse
Root works fine with what? A dev preview OS.
If someone is having issues then it must not be working ok.

jmill75 said:
Root works fine with what? A dev preview OS.
If someone is having issues then it must not be working ok.
Click to expand...
Click to collapse
Yes it works fine and the issue has nothing to do with root. Probably half of us using it are rooted without issue

Bit of a thread-dig here, but I just got a PH1 and went straight to P (not rooted yet) and saw no WiFi. Wouldn't even turn on.
The phone came with 7.1.1 and I flashed P via fastboot. Tried rebooting and monkeying with it, but never saw any progress, no list of networks, etc.
7.1.1 did see WiFi for the 5 minutes I ran it.
Flashed latest stable 8.1 and it WiFi worked again immediately.
Then flashed 9 a second time and now WiFi works fine.
My best guess is the 7.1.1->9 transition has some kind of issue (doesn't quite make sense to me, given that I think EVERYTHING is being flashed by the 9 update, but this did fix it).

tliebeck said:
Bit of a thread-dig here, but I just got a PH1 and went straight to P (not rooted yet) and saw no WiFi. Wouldn't even turn on.
The phone came with 7.1.1 and I flashed P via fastboot. Tried rebooting and monkeying with it, but never saw any progress, no list of networks, etc.
7.1.1 did see WiFi for the 5 minutes I ran it.
Flashed latest stable 8.1 and it WiFi worked again immediately.
Then flashed 9 a second time and now WiFi works fine.
My best guess is the 7.1.1->9 transition has some kind of issue (doesn't quite make sense to me, given that I think EVERYTHING is being flashed by the 9 update, but this did fix it).
Click to expand...
Click to collapse
Just got my Essential Phone today as well and did the exact same thing, flashed straight from 7.1.1 to P. I thought I was seriously going to have to send the phone back due to a broken Wi-Fi chip or something. You are seriously a lifesaver!

rignfool said:
Kernel or firmware mismatch
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
What can be done about this? I am having the same issue, but I have flashed the whole "Back to Stock" set for P beta 2 from the other thread.

Saundersmtt said:
What can be done about this? I am having the same issue, but I have flashed the whole "Back to Stock" set for P beta 2 from the other thread.
Click to expand...
Click to collapse
If I take your post at face value... You have a bad flash and need to try again... Or blame your cable... And go buy a new one...
Otherwise... You have a bad download... Or there is something wrong wrong with your zip or batch/script... Or you're not completely unlocked

Listen guys, the issue is bc the ota zip for p doesnt flash both slots and the fastboot images zip doesnt either. If u look at the script (flashall. Bat) with a text editor it specifically shows only flashing one slot. To fix the wifi issue, u need the july oreo images file and that flashall. Bat flashes both slots and will fix the lost wifi and or Bluetooth. Once u do that, it reboots twice and go back to dev options and renable usb debugging. Now u reboot bootloader and flash p. Now it should all work. Also, in doing this, you will have to lose your data.

Same here but can't roll back to Oreo
See.issue here but I seem.to not be able.to resolve wifi issue or roll back to Oreo. When I try to reflash it just says it expects a newer version of is. Any ideas?

1jason said:
See.issue here but I seem.to not be able.to resolve wifi issue or roll back to Oreo. When I try to reflash it just says it expects a newer version of is. Any ideas?
Click to expand...
Click to collapse
Yes flash the july oreo flashall. Bat

Saundersmtt said:
What can be done about this? I am having the same issue, but I have flashed the whole "Back to Stock" set for P beta 2 from the other thread.
Click to expand...
Click to collapse
I had the same problem. went back to stock on July's build (was on January's stock build previously) and reflashed P. Been smooth sailing ever since

jacksummers said:
Listen guys, the issue is bc the ota zip for p doesnt flash both slots and the fastboot images zip doesnt either. If u look at the script (flashall. Bat) with a text editor it specifically shows only flashing one slot. To fix the wifi issue, u need the july oreo images file and that flashall. Bat flashes both slots and will fix the lost wifi and or Bluetooth. Once u do that, it reboots twice and go back to dev options and renable usb debugging. Now u reboot bootloader and flash p. Now it should all work. Also, in doing this, you will have to lose your data.
Click to expand...
Click to collapse
The reason is because one of the OTAs did not have the partition you're looking for... And it created a mismatch somewhere...
You DO NOT need to have the same software on A and B... It just makes troubleshooting easier from our perspective... And... It forces you to reflash and probably fix the problem...
As intended... There should ALWAYS be a mismatch between A and B... At least a monthly security update... If not an Android versioning difference

Edited. We are all just trying to help others. Lets keep it that way.

so, uhmmm like yea...... there is this thread here, called the stock images thread (link for posterity https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681 ) this is firmware images, directly from essential. I have added the remaining images that you dont get from essential, so that way you can reflash, and get the same version of software on both sides. there are wipe and no wipe bat files in there, twrp11 (the working twrp we have), and the fix red boot (in case you broke verity), and a stockboot.img (coincidentally the same file as called boot in the zip, but renamed for your twrp/rooting pleasure).
These images work great, many many many people have used them to go back and forth between O and P, OTA, or recover from catastrophe. As usual, beware of dragons, make SURE SURE SURE SURE you have a working adb/fastboot environment (use the version that comes with essentials drivers) (you can always do ADB VERSION or FASTBOOT --VERSION ) to check your version and where its working out of. It is 1 stop shopping. I also know the guy that makes the zips

jacksummers said:
Edited. We are all just trying to help others. Lets keep it that way.
Click to expand...
Click to collapse
Sorry if my post came off as harsh... I'll edit it... But this forum is literally littered with VAST amounts of guessing and misinformation...

rignfool said:
Sorry if my post came off as harsh... I'll edit it... But this forum is literally littered with VAST amounts of guessing and misinformation...
Click to expand...
Click to collapse
No prob, i understand the frustration.i assure you i was not guessing. I only post what i know is for sure. When faced with the exact same issue as OP i was forced to flash both slots to fix it. Yes, they could boot up with slightly different partitions, but the wifi was broken still. I believe the whole phone needed both slots flashed with each corresponding img simultaneously in order to resolve said issue. For whatever reason, i had both a and b screwed up. At the time i was trying to fix the ril and camera issues on the pixel 2 system image after flashing it on my essential. I want to get that working fully to release as a port.

jacksummers said:
No prob, i understand the frustration.i assure you i was not guessing. I only post what i know is for sure. When faced with the exact same issue as OP i was forced to flash both slots to fix it. Yes, they could boot up with slightly different partitions, but the wifi was broken still. I believe the whole phone needed both slots flashed with each corresponding img simultaneously in order to resolve said issue. For whatever reason, i had both a and b screwed up. At the time i was trying to fix the ril and camera issues on the pixel 2 system image after flashing it on my essential. I want to get that working fully to release as a port.
Click to expand...
Click to collapse
Wouldn't it be easier to attempt to port the 2 or 3 features we don't have as a separate systemui.apk or framework-res.apk?
And use Magisk?
Since we don't have that fancy hardware photo rendering thingymabob