I had a perfectly working rooted Nexus 6 with twrp recovery. There was, a screen defect, and I was about to send it to Motorola under warranty., and needed to reset to factory. I guess I did this in the wrong order.
First, I did a "fastboot oem lock" which worked (too well)
Then I went into recovery (twrp) and used factory reset, which failed.
When I try and reboot the system, I get into a blinking teamwin screen.
The USB connection still works, andI can get to fastboot bootloader, , but can no longer oem unlock , "Check 'Allow OEM Unlock' in Developer Options.".
All the bootloader options, recovery, factory, bp tools all go to the flashing teamwin.
Is there any way to recover from this? Help!
kmandel said:
I had a perfectly working rooted Nexus 6 with twrp recovery. There was, a screen defect, and I was about to send it to Motorola under warranty., and needed to reset to factory. I guess I did this in the wrong order.
First, I did a "fastboot oem lock" which worked (too well)
Then I went into recovery (twrp) and used factory reset, which failed.
When I try and reboot the system, I get into a blinking teamwin screen.
The USB connection still works, andI can get to fastboot bootloader, , but can no longer oem unlock , "Check 'Allow OEM Unlock' in Developer Options.".
All the bootloader options, recovery, factory, bp tools all go to the flashing teamwin.
Is there any way to recover from this? Help!
Click to expand...
Click to collapse
since you still have twrp installed, you might have a chance. but your one and only option would be to fastboot format userdata and cache.
>since you still have twrp installed, you might have a chance. but your one and only option would be to fastboot format userdata and cache.
I suppose twrp is still installed, if thats what gives the teamwin loop. I can't actually get into twrp.
Would I be issuing two separate fastboot formats, or can I specify both userdata and cache on the same fastboot format.
If this actually worked, is the expectation that I could boot the system?
kmandel said:
>since you still have twrp installed, you might have a chance. but your one and only option would be to fastboot format userdata and cache.
I suppose twrp is still installed, if thats what gives the teamwin loop. I can't actually get into twrp.
Would I be issuing two separate fastboot formats, or can I specify both userdata and cache on the same fastboot format.
If this actually worked, is the expectation that I could boot the system?
Click to expand...
Click to collapse
yes. if you didnt have twrp installed, then id say you have a 0% chance. with twrp being installed, your chances went up dramatically, like a 50-50 chance.
Hint...
TeamWinRecoveryProject TWRP
Formats should fix that
Then youncan flash.a.rom.and.enable oem.unlock
Protip. Never lock the bootloader until you are back to complete stock. Basically, you don't start with it. You end with it.
graydiggy said:
Protip. Never lock the bootloader until you are back to complete stock. Basically, you don't start with it. You end with it.
Click to expand...
Click to collapse
Protip #2: Never lock the bootloader unless you intend to return it for repair.
cam30era said:
Protip #2: Never lock the bootloader unless you intend to return it for repair.
Click to expand...
Click to collapse
You didn't read the OP, did you?
graydiggy said:
You didn't read the OP, did you?
Click to expand...
Click to collapse
Yes, but it was long enough that I forgot.
cam30era said:
Yes, but it was long enough that I forgot.
Click to expand...
Click to collapse
some of us must be older than others :angel:
simms22 said:
some of us must be older than others :angel:
Click to expand...
Click to collapse
You bet!
Ok, I hate to act needy but I'm afraid of screwing this up beyond hope.
I assume that I first do
fastboot format userdata
fastboot format cache
Then what? Reboot?
If so what would I expect to see, Lolipop or twrp, or something else?
If its not Lollipop I guess I need to load a rom. Until now the only rom's I've loaded
are the factory firmware with "flash-all". But that needs oem unlock which I can't do.
kmandel said:
Ok, I hate to act needy but I'm afraid of screwing this up beyond hope.
I assume that I first do
fastboot format userdata
fastboot format cache
Then what? Reboot?
If so what would I expect to see, Lolipop or twrp, or something else?
If its not Lollipop I guess I need to load a rom. Until now the only rom's I've loaded
are the factory firmware with "flash-all". But that needs oem unlock which I can't do.
Click to expand...
Click to collapse
after, try booting up or try booting into twrp and see if you can load a rom, gapps, and supersu. if you dont have gapps or supersu, youll be fine this time. most importantly would be booting up and enabling oem unlocking in dev options.
Well I did the formats, and then a reboot. This time it boots into rotating colored balls
which seemed hopeful However, its been a half an hour now and they are still rotating.
I know this can go for a while, and am hesitant to interrupt it. but this seems ominous.
As far as the formats, here is the output
# fastboot format userdata
erasing 'userdata'...
OKAY [ 0.188s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 59751923712
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14587872
Block groups: 446
Reserved block group size: 1024
Created filesystem with 11/3653632 inodes and 275392/14587872 blocks
sending 'userdata' (141067 KB)...
writing 'userdata'...
(bootloader) Unlock before flashing
FAILED (remote failure)
finished. total time: 5.065s
# fastboot format cache
erasing 'cache'...
OKAY [ 0.030s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
sending 'cache' (6248 KB)...
writing 'cache'...
(bootloader) Unlock before flashing
FAILED (remote failure)
finished. total time: 0.241s
kmandel said:
Well I did the formats, and then a reboot. This time it boots into rotating colored balls
which seemed hopeful However, its been a half an hour now and they are still rotating.
I know this can go for a while, and am hesitant to interrupt it. but this seems ominous.
As far as the formats, here is the output
# fastboot format userdata
erasing 'userdata'...
OKAY [ 0.188s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 59751923712
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14587872
Block groups: 446
Reserved block group size: 1024
Created filesystem with 11/3653632 inodes and 275392/14587872 blocks
sending 'userdata' (141067 KB)...
writing 'userdata'...
(bootloader) Unlock before flashing
FAILED (remote failure)
finished. total time: 5.065s
# fastboot format cache
erasing 'cache'...
OKAY [ 0.030s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
sending 'cache' (6248 KB)...
writing 'cache'...
(bootloader) Unlock before flashing
FAILED (remote failure)
finished. total time: 0.241s
Click to expand...
Click to collapse
kmandel said:
Well I did the formats, and then a reboot. This time it boots into rotating colored balls
which seemed hopeful However, its been a half an hour now and they are still rotating.
I know this can go for a while, and am hesitant to interrupt it. but this seems ominous.
As far as the formats, here is the output
# fastboot format userdata
erasing 'userdata'...
OKAY [ 0.188s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 59751923712
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14587872
Block groups: 446
Reserved block group size: 1024
Created filesystem with 11/3653632 inodes and 275392/14587872 blocks
sending 'userdata' (141067 KB)...
writing 'userdata'...
(bootloader) Unlock before flashing
FAILED (remote failure)
finished. total time: 5.065s
# fastboot format cache
erasing 'cache'...
OKAY [ 0.030s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
sending 'cache' (6248 KB)...
writing 'cache'...
(bootloader) Unlock before flashing
FAILED (remote failure)
finished. total time: 0.241s
Click to expand...
Click to collapse
Boot to TWRP. Download a ROM from development forums to your PC. Connect your nexus to PC while it's booted to TWRP. You should see the nexus internal storage show up on your PC. Drag and drop or copy and paste the ROM from PC to internal storage. Flash ROM with TWRP. Boot up, skip all set up, enable developer options and then boot to bootloader and fastboot OEM unlock.
To make a long story short: SUCCESS!
The longer story was that there were complications.
-- Filemanager came up with an empty "SHAMU' that it couldn't write to
- I used adb push to get a rom image over to the rootfs
- the install had trouble with the data partition. I had to format
- turned out the rootfs partition was a bad place for the rom image, had to move it to /data
- install of rom from twrp finally worked
- using the new rom to enable oem unlocking worked
- flash-all of factory image failed. Had to individually flashboot flash piece by piece for some reason.
Finally: SUCCESS. Thanks for all you help!!
kmandel said:
To make a long story short: SUCCESS!
The longer story was that there were complications.
-- Filemanager came up with an empty "SHAMU' that it couldn't write to
- I used adb push to get a rom image over to the rootfs
- the install had trouble with the data partition. I had to format
- turned out the rootfs partition was a bad place for the rom image, had to move it to /data
- install of rom from twrp finally worked
- using the new rom to enable oem unlocking worked
- flash-all of factory image failed. Had to individually flashboot flash piece by piece for some reason.
Finally: SUCCESS. Thanks for all you help!!
Click to expand...
Click to collapse
I had the same problem can you have me please advise what did you do
kmandel said:
To make a long story short: SUCCESS!
The longer story was that there were complications.
-- Filemanager came up with an empty "SHAMU' that it couldn't write to
- I used adb push to get a rom image over to the rootfs
- the install had trouble with the data partition. I had to format
- turned out the rootfs partition was a bad place for the rom image, had to move it to /data
- install of rom from twrp finally worked
- using the new rom to enable oem unlocking worked
- flash-all of factory image failed. Had to individually flashboot flash piece by piece for some reason.
Finally: SUCCESS. Thanks for all you help!!
Click to expand...
Click to collapse
You certainly made a mountain out of a mole hill here.
fastboot format cache
fastboot format userdata - this should fix TWRP like I said on page 1.
Boot into TWRP and tick the box "enable mtp" then copy a rom to from your computer using windows explorer like you would if it was booted to android.
Why would you put data on rootfs?
Important lesson, if you're going to be rooted, know your phone
Related
I messed up my tab after I rooted it and used an app that lowers the DPI setting. Now I can't see anything after I restart my tablet. It's just a black screen. I can hold down power and the down button to get to the screen where the android is showing it's guts and can choose between Recovery and Power off.... but not clock work recovery. I tried pressing the up button as it powers on but nothing. It was rooted using the on click root option which was also supposed to install CWR but it's not working. Can anyone explain how to flash the original rom back to the device without using CWR just using the PC?
Thanks.
i'm very noob at this but i thought there was somehing with ADB?
download & install the android SDK from google, developer.android.com/sdk/index.html, & follow their instructions to configure it
download the stock ROM from google, developers.google.com/android/nexus/images, and follow the instructions
pretty straight forward, done it twice already
Come on. Please use the search, this is what it's there for.
http://forum.xda-developers.com/showthread.php?t=
Sent from my Nexus 7 using xda premium
tehSmoogs said:
download & install the android SDK from google, developer.android.com/sdk/index.html, & follow their instructions to configure it
download the stock ROM from google, developers.google.com/android/nexus/images, and follow the instructions
pretty straight forward, done it twice already
Click to expand...
Click to collapse
Thanks! I will follow the steps.
kind3rgarten said:
Come on. Please use the search, this is what it's there for.
http://forum.xda-developers.com/showthread.php?t=
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I apologize. I tried to do a search but what came up was confusing me more.
tehSmoogs said:
download & install the android SDK from google, developer.android.com/sdk/index.html, & follow their instructions to configure it
download the stock ROM from google, developers.google.com/android/nexus/images, and follow the instructions
pretty straight forward, done it twice already
Click to expand...
Click to collapse
I've downloaded the SDK and the rom file and have extracted it.
It says to run the ./flash-all.sh script. But it's not associated with any programs. I assume that I load this file into the SDK?
I think flashing the entire image might be overkill. You (or the app, I guess) presumably only messed with the build.prop, right? If so, should only have to find and reflash a working build.prop.
Warning: the above is noob advice. I'm just guessing here.
thebobp said:
I think flashing the entire image might be overkill. You (or the app, I guess) presumably only messed with the build.prop, right? If so, should only have to find and reflash a working build.prop.
Warning: the above is noob advice. I'm just guessing here.
Click to expand...
Click to collapse
Thanks. But I think my problem is bigger than that. I can't see the tablet on my computer anymore. After the Google logo with the unlocked sign on the bottom goes away, I assume this is the point where I'm supposed to see the Nexus logo. It doesn't get that far. When I tried to connect it to the USB on the computer, I hear a connection signal but the tablet never pops up in Windows. I was only able to get to the CWR screen once. Don't know how I did it but when I tried to select Wipe Data/Factory Reset, it just shows me an icon of a top hat and a circle underneath it. Pressing the power button just brought me back to the CWR screen and any other choice will give me the top hat screen. I haven't been able to get back to CWR screen again. I can get to the main screen where I can select start/restart bootloader/recovery but selecting recovery doesn't get me back into the CWR screen.
thebobp said:
I think flashing the entire image might be overkill. You (or the app, I guess) presumably only messed with the build.prop, right? If so, should only have to find and reflash a working build.prop.
Warning: the above is noob advice. I'm just guessing here.
Click to expand...
Click to collapse
Yeah.
Protip: Backup Build.prop before messing with it.
If you would have just backed it up you could have done a simple adb push.
Sent from my Nexus 7 using xda premium
I didn't do that. That's probably why I get the top hat when I tried to do a factory wipe from CWR
At this point I think it's not going to be able to connect to the computer. I'll exchange it for another one and not use that app!
If you're willing, give this a go.....
You'll need to copy flash-all.sh, bootloader-grouper-3.34.img and image-nakasi-jrn84d.zip files to the "C:\Program Files (x86)\Android\android-sdk\platform-tools\" folder - thats if the sdk installed to the same place as mine.
Start a command prompt and change directory to the platform-tools folder.
Check that the tablet is accessible by doing a "fastboot devices" - it should display a hex string - if you don't get this then you'll be beyond my help......
The flash-all.sh file is the unix equivalent of a ".bat" file, all you need to do is rename it to "flash-all.bat" and then run it from the commnd prompt.
When you run it you should see something like this:-
erasing 'boot'...
OKAY [ 0.104s]
finished. total time: 0.104s
erasing 'cache'...
OKAY [ 0.130s]
finished. total time: 0.130s
erasing 'recovery'...
OKAY [ 0.105s]
finished. total time: 0.105s
erasing 'system'...
OKAY [ 0.176s]
finished. total time: 0.176s
erasing 'userdata'...
OKAY [ 1.251s]
finished. total time: 1.251s
sending 'bootloader' (2072 KB)...
OKAY [ 0.284s]
writing 'bootloader'...
OKAY [ 1.168s]
finished. total time: 1.452s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 3.34
Baseband Version.....: N/A
Serial Number........: xxxxxxxxxxxxxxx
--------------------------------------------
checking product...
OKAY [ 0.020s]
checking version-bootloader...
OKAY [ 0.020s]
sending 'boot' (4884 KB)...
OKAY [ 0.663s]
writing 'boot'...
OKAY [ 0.328s]
sending 'recovery' (5228 KB)...
OKAY [ 0.689s]
writing 'recovery'...
OKAY [ 0.268s]
sending 'system' (432360 KB)...
OKAY [ 52.602s]
writing 'system'...
OKAY [ 21.431s]
erasing 'userdata'...
OKAY [ 1.041s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 14442037248
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3525888
Block groups: 108
Reserved block group size: 863
Created filesystem with 11/883008 inodes and 96825/3525888 blocks
sending 'userdata' (137526 KB)...
writing 'userdata'...
OKAY [ 24.636s]
erasing 'cache'...
OKAY [ 0.115s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 464519168
Block size: 4096
Blocks per group: 32768
Inodes per group: 7088
Inode size: 256
Journal blocks: 1772
Label:
Blocks: 113408
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/28352 inodes and 3654/113408 blocks
sending 'cache' (9052 KB)...
writing 'cache'...
OKAY [ 1.808s]
rebooting...
finished. total time: 103.718s
At that point you should be booting back to stock.
Good luck!
CyberChulo said:
I didn't do that. That's probably why I get the top hat when I tried to do a factory wipe from CWR
Click to expand...
Click to collapse
i just messed mine up the exact same way, but hopefully we'll figure it out instead of returning a product that we specifically killed
tehSmoogs said:
If you're willing, give this a go.....
At that point you should be booting back to stock.
Good luck!
Click to expand...
Click to collapse
Thanks for all your help but the computer does not recognize any usb device connected. I've returned it and waiting on another one to come in. I sure as hell won't be messing around with dpi settings anymore!
CyberChulo said:
Thanks for all your help but the computer does not recognize any usb device connected. I've returned it and waiting on another one to come in. I sure as hell won't be messing around with dpi settings anymore!
Click to expand...
Click to collapse
Okay, for one, LCD modder has been known not to work with the N7, use ROM toolbox or manually edit the prop yourself.
Two, do you possibly have the phone plugged into a USB 3.0 port? ADB and the drivers do not like USB 3.0 ports. Is there also possibly a driver or something that is not installed? Look at the link I posted on the first page.
Sent from my Galaxy Nexus using xda premium
kind3rgarten said:
Okay, for one, LCD modder has been known not to work with the N7, use ROM toolbox or manually edit the prop yourself.
Two, do you possibly have the phone plugged into a USB 3.0 port? ADB and the drivers do not like USB 3.0 ports. Is there also possibly a driver or something that is not installed? Look at the link I posted on the first page.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
All drivers were installed initially when I ran the One click Root procedure. I did have it plugged into a USB 3.0 port at home but at work I only have 2.0 ports. None of them recognized the device other than showing that a USB device was connected. It has trouble finding the MTP driver.... after I had modded the dpi setting.
Hi,
I tried to update to Android 4.2 (from 4.1.2) today, but it failed at the stock recovery saying:
[..]
assert failed: apply_patch_check("/system/app/Books.apk", ........
Installation aborted.
Screenshot: https://www.dropbox.com/s/b8lk0n147cbcfuv/20121114_121646_4_bestshot.jpg
Using Titanium Backup I used to make Google Books a Userland application and uninstalled it a while ago, because I wanted to remove some bloatware. I installed the backup I had and made it a system-application again, but its still giving me that error. Even factory reset didnt help.
What options do I have? How can I flash the full image?
Kind regards
Alex
Nevermind, I found the factory image at
https://developers.google.com/android/nexus/images#nakasijop40c
Downloaded it, did a titanium backup, flashed image via flash-all.bat, restored root, restored backup and 4.2 with root is all up and running now.
Same problem with apply_patch_check error bij update.
Also try to flash full factory image 4.2 by fastboot.
After install and reboot, Google icon in screen, doesn't startup.
That 5x but no success.
Same install with factory image 4.1.2 and no problem.
Help!
---------- Post added at 01:10 PM ---------- Previous post was at 01:02 PM ----------
Hello Alex,
You said, flashed bij Flash-all.bat.
How does that work? You may have a brief description of how you do it?
Thank you!
In the .zip you downloaded, there is a file called flash-all.bat. For example it does this for the WiFi version:
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.13.img
fastboot reboot-bootloader
ping -n 10 127.0.0.1 >nul
fastboot -w update image-nakasi-jop40c.zip
echo Press any key to exit...
pause >nul
exit
Check your version an run it in platform-tools with all content beeing there of course. Its quite easy
You sense about PATH I do not understand.
The rest I have indeed done in cmd
I have indeed PlatformTools and I have all five files in that folder.
Same folder where adb.exe also capable.
I've done in cmd in the platformtools path:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.13.img
fastboot reboot-bootloader
fastboot -w update image-nakasi-jop40c.zip
Then start the nexus7 but remains on the startup screen on the google logo.
Am I forgetting something?
whats the output of the fastboot commands from above?
I have the same problem but with GooglePinyinime.apk.
Have just worked out how to sideload using adb and am getting stuck on this error.
I did freeze this app using titanium pro, then unfroze it when I upgraded to 4.1.2 ota successfully, so can't understand why its pulling up an error now?
Am a bit of a noob with these commands so would be very grateful for any help.
Am on stock rom, rooted and no custom recovery.
Thanks.
Sent from my Nexus 7 using Tapatalk 2
simacca said:
I have the same problem but with GooglePinyinime.apk.
Have just worked out how to sideload using adb and am getting stuck on this error.
I did freeze this app using titanium pro, then unfroze it when I upgraded to 4.1.2 ota successfully, so can't understand why its pulling up an error now?
Am a bit of a noob with these commands so would be very grateful for any help.
Am on stock rom, rooted and no custom recovery.
Thanks.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Do you have fastboot installed on your computer? I am not in front of my development computer so I can't give you specific details but I had a several modifications to /system so I didn't bother trying to reverse them and instead flashed the original 4.1.2 system.img.
The (rough) procedure for this is:
1. Backup your current 4.1.2 rom in case you can't live with 4.2
2. Plug the nexus into your computer and boot into the bootloader (up vol + down vol + power)
3. On your computer, download the 4.1.2 factory image from https://dl.google.com/dl/android/aosp/nakasi-jzo54k-factory-973f190e.tgz
4. Unzip the image and then unzip the zip file that was inside the image (I can't remember the name but I believe there is only one)
5. If you unzipped everything correctly you should have a system.img file, open a command window and navigate to the directory that contains the system.img file and type:
Code:
fastboot flash system system.img
Sorry I don't have the specific details. If no one else has filled in the missing file names by the time I get home and you are comfortable with this procedure I will update this with the proper names.
C:\android-sdk-windows\platform-tools>fastboot flash bootloader bootloader-group
er-4.13.img
sending 'bootloader' (2096 KB)...
OKAY [ 0.290s]
writing 'bootloader'...
OKAY [ 1.252s]
finished. total time: 1.548s
C:\android-sdk-windows\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.022s
C:\android-sdk-windows\platform-tools>fastboot -w update image-nakasi-jop40c.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.13
Baseband Version.....: N/A
Serial Number........: 015d2578a3140811
--------------------------------------------
checking product...
OKAY [ 0.030s]
checking version-bootloader...
OKAY [ 0.018s]
sending 'boot' (4942 KB)...
OKAY [ 0.599s]
writing 'boot'...
OKAY [ 0.405s]
sending 'recovery' (5444 KB)...
OKAY [ 0.660s]
writing 'recovery'...
OKAY [ 0.348s]
erasing 'system'...
OKAY [ 0.155s]
sending 'system' (477136 KB)...
OKAY [ 60.010s]
writing 'system'...
OKAY [ 23.794s]
erasing 'userdata'...
OKAY [ 1.092s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 14442037248
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3525888
Block groups: 108
Reserved block group size: 863
Created filesystem with 11/883008 inodes and 96825/3525888 blocks
sending 'userdata' (137526 KB)...
writing 'userdata'...
OKAY [ 27.895s]
erasing 'cache'...
OKAY [ 0.119s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 464519168
Block size: 4096
Blocks per group: 32768
Inodes per group: 7088
Inode size: 256
Journal blocks: 1772
Label:
Blocks: 113408
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/28352 inodes and 3654/113408 blocks
sending 'cache' (9052 KB)...
writing 'cache'...
OKAY [ 1.940s]
rebooting...
finished. total time: 117.197s
C:\android-sdk-windows\platform-tools>
Nexus root toolkit works
Nexus root toolkit works like a champ for restoring stock if you need it.
Works flawlessly in windows 7 for me.
http://www.wugfresh.com/nrt/
The real issue with the the assert errors is that you changed something you should not have. The 4.2 update hash checks the original system apps for consistency. If you changed any of the System apps outside of an official update you get the assert errors when trying to flash the new update.
Have the same problem...
[..]
assert failed: apply_patch_check("/system/app/Books.apk", ........
Installation aborted.
Anyone manage ti fix it without restoring original rom would be nice....
alex2308 said:
Nevermind, I found the factory image at
https://developers.google.com/android/nexus/images#nakasijop40c
Downloaded it, did a titanium backup, flashed image via flash-all.bat, restored root, restored backup and 4.2 with root is all up and running now.
Click to expand...
Click to collapse
Hi Alex,
Did flashed factory image returned our Nexus like a new phone or just restoring system files? I want to flash factory image but afraid if it's like a factory reset
everyday_ said:
Hi Alex,
Did flashed factory image returned our Nexus like a new phone or just restoring system files? I want to flash factory image but afraid if it's like a factory reset
Click to expand...
Click to collapse
Its like a full factory reset, everything is gone (also the /sdcard folder with the downloads and stuff). Restoring was pretty easy, I copied the /sdcard stuff via USB to my computer and used titanium backup to backup the apps with settings (and copied that too to my computer). The only thing I had to setup again was WiFi, Homescreen and Email (although you can backup them via Titanium, which I didnt).
Mathijs17 said:
C:\android-sdk-windows\platform-tools>fastboot flash bootloader bootloader-group
er-4.13.img
sending 'bootloader' (2096 KB)...
OKAY [ 0.290s]
writing 'bootloader'...
OKAY [ 1.252s]
finished. total time: 1.548s
C:\android-sdk-windows\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.022s
C:\android-sdk-windows\platform-tools>fastboot -w update image-nakasi-jop40c.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.13
Baseband Version.....: N/A
Serial Number........: 015d2578a3140811
--------------------------------------------
checking product...
OKAY [ 0.030s]
checking version-bootloader...
OKAY [ 0.018s]
sending 'boot' (4942 KB)...
OKAY [ 0.599s]
writing 'boot'...
OKAY [ 0.405s]
sending 'recovery' (5444 KB)...
OKAY [ 0.660s]
writing 'recovery'...
OKAY [ 0.348s]
erasing 'system'...
OKAY [ 0.155s]
sending 'system' (477136 KB)...
OKAY [ 60.010s]
writing 'system'...
OKAY [ 23.794s]
erasing 'userdata'...
OKAY [ 1.092s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 14442037248
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3525888
Block groups: 108
Reserved block group size: 863
Created filesystem with 11/883008 inodes and 96825/3525888 blocks
sending 'userdata' (137526 KB)...
writing 'userdata'...
OKAY [ 27.895s]
erasing 'cache'...
OKAY [ 0.119s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 464519168
Block size: 4096
Blocks per group: 32768
Inodes per group: 7088
Inode size: 256
Journal blocks: 1772
Label:
Blocks: 113408
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/28352 inodes and 3654/113408 blocks
sending 'cache' (9052 KB)...
writing 'cache'...
OKAY [ 1.940s]
rebooting...
finished. total time: 117.197s
C:\android-sdk-windows\platform-tools>
Click to expand...
Click to collapse
Did you do a erase or just flash over them?
Phone is staing in bootloader- i cant boot any other function like at normal boot, recovery, qcom, bp tools...nothing. Device is LOCKED!!!'Allow OEM Unlock' in developer options is UNCHEKED!!!
BL: moto-apq8084-71.08 (sha-32g8854, 2014-12-09 14:00:26)
Baseband: D4.0-9625-02.95
Product/Variant: shamu XT1100 64GB P3AO
Code:
c:\adb>Fastboot oem lock begin
...
(bootloader) fastboot oem lock currently disabled!
OKAY [ 0.002s]
finished. total time: 0.002s
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.016s
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.012s
downloading 'boot.img'...
OKAY [ 0.469s]
booting...
FAILED (remote failure)
finished. total time: 0.479s
c:\adb>fastboot format cache
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.026s]
sending 'cache' (6248 KB)...
OKAY [ 0.249s]
writing 'cache'...
OKAY [ 0.141s]
finished. total time: 0.426s
c:\adb>fastboot format userdata
Creating filesystem with parameters:
Size: 59743535104
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14585824
Block groups: 446
Reserved block group size: 1024
Created filesystem with 11/3646496 inodes and 274946/14585824 blocks
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 1.700s]
sending 'userdata' (141063 KB)...
OKAY [ 5.993s]
writing 'userdata'...
OKAY [ 3.731s]
finished. total time: 11.434s
c:\adb>
c:\adb>fastboot flash system system.img
target reported max download size of 536870912 bytes
sending sparse 'system' (522112 KB)...
OKAY [ 24.621s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 24.648s
c:\adb>fastboot flash boot boot.img
target reported max download size of 536870912 bytessending 'boot' (7681 KB)...
OKAY [ 0.299s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.315s
Seriously, do you guys not search ANYWHERE? There are tons of threads regarding bricked Nexus 6s, there's even an unbricking thread about this in this very section! http://forum.xda-developers.com/showthread.php?t=3059518
brando56894 said:
Seriously, do you guys not search ANYWHERE? There are tons of threads regarding bricked Nexus 6s, there's even an unbricking thread about this in this very section! http://forum.xda-developers.com/showthread.php?t=3059518
Click to expand...
Click to collapse
read carefully- my phone not detect like HS-USB QDLoader it is like adb bootloader interface. This happened after rewrite files into /dev/block/. Backups all those files i have. Question- how to write them back?
Duumon said:
read carefully- my phone not detect like HS-USB QDLoader it is like adb bootloader interface. This happened after rewrite files into /dev/block/. Backups all those files i have. Question- how to write them back?
Click to expand...
Click to collapse
Cannot.
rootSU said:
Cannot.
Click to expand...
Click to collapse
I found the way to connect phone as HS-USB QDloader device. All filles of blank-flash.bat flashed, but phone stil dont turn on
Duumon said:
I found the way to connect phone as HS-USB QDloader device
Click to expand...
Click to collapse
How?
rootSU said:
How?
Click to expand...
Click to collapse
testpoint
Duumon said:
testpoint
Click to expand...
Click to collapse
You created a "testpoint" cable?
That's interesting - @efrant
@Duumon - are you still following this thread? http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
@Duumon - are you still following this thread? http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
Click to expand...
Click to collapse
yes-all those steps passed, but phone stil in locked bootloader. I think need flash boot and sysstem by qualkomm tool but.....how?
Duumon said:
yes-all those steps passed, but phone stil in locked bootloader. I think need flash boot and sysstem by qualkomm tool but.....how?
Click to expand...
Click to collapse
Did you also read post 94 (and related posts) of that thread?
@randy6644 got it to work.
http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518/post59650346
What is a testpoint cable?
Doesn't helped. Phone have cid-dead and status unlock-not supported. In photo at attach not full the last log- system and boot .img flashed with error Preflash validation failed
still dead...any ideas?
Duumon said:
I found the way to connect phone as HS-USB QDloader device. All filles of blank-flash.bat flashed, but phone stil dont turn on
Click to expand...
Click to collapse
Same Problem. Can you explain how you create the testpoint cable?
Gesendet von meinem LG-D855 mit Tapatalk
[Q] Managed to delete everything, "could not detect filesystem" so can't flash anythi
Hi there!
So, being an idiot, I managed to wipe my phone completely whilst attempting to upgrade my firmware.
Now, I can't flash anything, as when I try to do so I get the following text...
Code:
Flashing AICP System files...
could not detect filesystem for /dev/block/platform/msm_sdcc.
1/by-name/system, assuming ext4 mount: failed to mount /dev/
block/platform/msm_sdcc. 1/by-name/system at system:
no such volume
script succeeded: result was [0.200000]
Updating partition details...
Can't check permissions
after Factory Reset
Please boot rom and try
again after you reboot into
recovery.
Done
Unfortunately, when I then reboot, I don't have an OS so it just sits at the HTC logo.
After a lot of effort, I did manage to get a rom onto my internal memory, but as shown above, it just won't let me flash it
Any ideas what is wrong and how it can be fixed?
EDIT1: Additional information:
Code:
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.21.3263.04
OpenDSP-v32.120.274.0909
OS-
eMMC-boot 2048Mb
EDIT2: Tried sideloading, this didn't work either
EDIT3: Using CWM recovery instead of TWRP seems to have worked
?
How did you manage to erase it like that? 0_o
Tried
fastboot format system
?
After format, try flashing a ROM.
Lavanoid said:
How did you manage to erase it like that? 0_o
Tried
fastboot format system
?
After format, try flashing a ROM.
Click to expand...
Click to collapse
I'm not entirely sure how I managed this.
When trying fastboot format system I got the following
Code:
Creating filesystem with parameters:
Size: 1946152960
Block size: 4096
Blocks per group: 32768
Inodes per group: 7920
Inode size: 256
Journal blocks: 7423
Label:
Blocks: 475135
Block groups: 15
Reserved block group size: 119
Created filesystem with 11/118800 inodes and 15607/475135 blocks
target reported max download size of 1526722560 bytes
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: 0.016s
Hhm
I think I read another post with a similar problem, earlier today in this forum. If you look around the Q&A forum, you should be able to find it.
Saidinsaidar said:
Code:
Flashing AICP System files...
[COLOR="Red"]could not detect filesystem for /dev/block/platform/msm_sdcc.
1/by-name/system[/COLOR], assuming ext4 mount: failed to mount /dev/
block/platform/msm_sdcc. 1/by-name/system at system:
no such volume
Click to expand...
Click to collapse
Looks like you are simply not using the right recovery version for the rom you want to flash. Roms that need "by-name" partitions mounting (lie all Cyanogenmod based roms) requires twrp 2.7.1.1+ or CWM 6.0.4.8+.
alray said:
Looks like you are simply not using the right recovery version for the rom you want to flash. Roms that need "by-name" partitions mounting (lie all Cyanogenmod based roms) requires twrp 2.7.1.1+ or CWM 6.0.4.8+.
Click to expand...
Click to collapse
That's odd, I'm using the most up to date version of TWRP, downloaded and flashed with fastboot this evening :/
EDIT: Changed to CWM recovery and tried flashing, seems to have been successful. Hooray!
Sorry, my English very bad. I have Mi A2 with bootloop. Bootloader locked. I tried to flash three different firmwares using MiFlash, but was getting one error. it 1st image.
Later it seems I changed my MiFlash version and got another error, this is the second image. What do these errors mean?
Me_gusta_98 said:
Sorry, my English very bad. I have Mi A2 with bootloop. Bootloader locked. I tried to flash three different firmwares using MiFlash, but was getting one error. it 1st image.
Later it seems I changed my MiFlash version and got another error, this is the second image. What do these errors mean?
Click to expand...
Click to collapse
Don't know what that means but 'ack' should refer to "android common kernels".
I found a few videos searching for "Android Ack count don't match". Maybe you could try their solutions / methods.
User699 said:
Don't know what that means but 'ack' should refer to "android common kernels".
I found a few videos searching for "Android Ack count don't match". Maybe you could try their solutions / methods.
Click to expand...
Click to collapse
I saw it, there Indians install the beta version of MiFlash and everything is fine. But the beta version does not work for me, it does not see the file "flash_all.bat"
Me_gusta_98 said:
I saw it, there Indians install the beta version of MiFlash and everything is fine. But the beta version does not work for me, it does not see the file "flash_all.bat"
Click to expand...
Click to collapse
Maybe try an older (beta) version. It could be a problem in the current release which didn't occur in prior releases.
I have the same problem with a brand new Mi A2
Stuck at the androidone bootlogo.
Entering fastboot works without problems.
Flashing results in this error: FAILED (remote: 'Error flashing partition : Write Protected')
No matter which slot is used.
Unlocking via fastboot tells me that everything is already unlocked.
Booting the twrp image from fastboot gets stuck at the twrp logo.
This also happens with the patched twrp_4pda version.
This [GUIDE] Flashing ROMs with TWRP black screen post seemed helpful and adb shell works.
But sending commands like twrp wipe cache results in:
TWRP does not appear to be running. Waiting for TWRP to start . . .
Code:
fastboot --set-active=b
fastboot flash boot_b twrp.img
fastboot --set-active=a
fastboot flash boot_a twrp.img
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot oem unlock
fastboot boot twrp.img
adb shell
twrp wipe cache
Entering EDL mode via fastboot works without problems.
I installed the qualcomm 9008 drivers (windows 10 driver signature verification had to be disabled) and the phone in edl mode appears.
Downloaded the Mi A2 global fastboot rom
I tried all miflash versions (2015 to 2018 and beta) ... they had various bugs
XiaoMiFlash.Config --> rename to XiaoMiFlash.exe.Config
generate "Log" folder
place rom files inside miflash folder ... avoid any long/special path names
In the end they all start flashing and fail with "no Binary dump" or "ACK count don't match".
I also tried a different PC, different USB cable and fastboot on linux.
Is there anything else that could be done or is time to consider a hardware failure (broken emmc ...?) ?
#### update ###
fastboot format userdata
.... works and writes something without error
fastboot format cache / fastboot erase cache
... FAILED (remote: 'Error flashing partition : Write Protected')
I was able to get into stock recovery (hold VolUp+Power --> "no command" --> hold again).
wipe data / factory reset --> getting stuck forever on "wiping data..." screen
Apply Update from ADB --> adb sideload miui.zip also gets stuck forever
calling fastboot -w results in:
Spoiler: error code
Erasing 'userdata' OKAY [ 0.081s]
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 4652023 4k blocks and 1163264 inodes
Filesystem UUID: 969bf7be-a1e1-11ec-9ff1-f15f995f2a7c
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'userdata' (180 KB) OKAY [ 0.011s]
Writing 'userdata' OKAY [ 0.000s]
Erasing 'cache' OKAY [ 0.002s]
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 65536 4k blocks and 65536 inodes
Filesystem UUID: 96ab61ae-a1e1-11ec-aed9-d92ea3a1e9cc
Superblock backups stored on blocks:
32768
Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'cache' (56 KB) FAILED (remote: 'Error: Last flash failed : Write Protected')
fastboot: error: Command failed