First post here at XDA - before I start with my problem, I should say thanks to everyone who posts here. I've come across this site so often when looking for information and always found it to be very helpful.
I was taking a Photo Sphere photo a few weeks ago, and after the photo had been taken, and during the processing/rendering stage, I looked away from my phone while holding it to let it work. I looked down to see the finished result about 30 seconds later and saw the Google startup screen. It appears that somehow, taking a Photo Sphere photo may have soft bricked my 6P, but I have no idea how. The phone itself was working perfectly normally prior to that.
I kept manually restarting it, powering it off, booting to recovery and restarting to see if I could get it back to normal with no success. It would occasionally, maybe one in twenty times, get to the Android boot animation, but would freeze after around 5 seconds on that, then restart again. Eventually, I thought to clear the cache partition via TWRP, so I did so and it then booted and loaded Android as normal. However, one of the first things I did was go to Settings to reset the time as it was wrong, and, as soon as it displayed the Settings screen, the phone restarted again, and no amount of cache clearing has resolved the issue since.
It's a 64GB 6P running Marshmallow 6.0.1, unlocked and rooted via Heisenberg's excellent guide and running TWRP 3.0.2.0, which was the latest available when I rooted. Right now, upon starting, it shows the "Your device software can't be checked for corruption. Please lock the bootloader." message as normal, then the Google logo, then it restarts and does the same again. I can access recovery mode as normal.
Does anyone have any ideas what steps I need to take to get my 6P operable again? Given that it booted after I wiped the cache then rebooted when I went to settings, my relatively uneducated presumption is that the root has somehow gotten messed up, but I don't know enough about troubleshooting Android to resolve it myself. I'd obviously prefer to avoid wiping it and losing data if possible. Although I'm a computer geek, I'm not 100% sure about Android ADB/fastboot commands and what to run to resolve this issue, so I thought I should defer to the experts here. I was considering flashing the factory image (part 11 of Heisenberg's guide) to see if that helped, but wasn't sure if that's the best first step to try at this point so thought it best to seek some advice rather than turn a soft brick into a hard one.
Thanks for any and all assistance!
BL: angler-03.51
Baseband: angler-03.61
Product/Variant: ANGLER-ROW-VN1
Device is UNLOCKED.
Qfuse Status: ENABLED.
Well, maybe the above is a bit too much to read...my bad habit of being verbose. Here's a tl;dr version;
Unlocked and rooted 64GB 6P running Marshmallow is boot-looping at the bootloader unlocked screen
Wiping cache only temporarily resolved
Can access recovery and fastboot as normal
Any ideas?
Well, mine appears to have done the same exact thing, but I wasn't using photosphere. Before I continue, here's my story...
I'm on vacation from Sept 1st to Sept 5th, and on the 4th(yesterday), I was browsing using Chrome before it froze and shut off on me, which then turned into a bootloop with the Google screen. Next, I did what I normally do when I have a problem, I head to recovery(depending on what I was last doing, I'd delete a file that I know caused it), but instead, I couldn't get into recovery. I tried maybe about 10 times and got into recovery twice. I removed all overlays that had to do with Substratum and deleted my cache/dalvik cache, rebooted and I got to the Android updating screen. It went through the process, froze and rebooted again. Now, I'm at the point where it's just the Google screen. I can get into the Bootloader, but nothing else. I'm thinking I'm having hardware failure or something. I attempted to do a factory image restore twice now, doing the third one as I type this before I contact Google, but yeah... I can't get into recovery or past the Google screen. Only the bootloader is accessible.
Now... As for your situation, download Wugfresh Nexus Toolkit, or follow later on in Heisenberg's guide to restore the factory image without deleting the userdata partition. There may still be a chance for you to get your data back, but for me... nah. Good luck.
Hey Curiousn00b, thanks for sharing your story. It seems really weird that they're just dying so suddenly and so fatally with no hardware failures. I'm wondering if this is part of a larger issue.
I just tried flashing the factory images for MHC19I as per part 11 of Heisenberg's guide and, alas, no luck. The images flashed fine, but it's still doing the same thing as before.
Is there anything else I can do to get it to a usable state again without completely wiping it? Should I try another factory image, maybe an earlier one? And, if I do have to wipe it, can I re-flash TWRP recovery and take a backup first?
Here's my log output for confirmation. Thanks again, I appreciate your reply.
Code:
C:\SDK\platform-tools>fastboot flash bootloader C:\angler\images\bootloader-angler-angler-03.51.img
target reported max download size of 494927872 bytes
sending 'bootloader' (3526 KB)...
OKAY [ 0.105s]
writing 'bootloader'...
OKAY [ 0.237s]
finished. total time: 0.345s
C:\SDK\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time: 0.013s
C:\SDK\platform-tools>fastboot flash radio C:\angler\images\radio-angler-angler-03.61.img
target reported max download size of 494927872 bytes
sending 'radio' (48600 KB)...
OKAY [ 1.202s]
writing 'radio'...
OKAY [ 2.855s]
finished. total time: 4.060s
C:\SDK\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.014s]
finished. total time: 0.016s
C:\SDK\platform-tools>fastboot flash boot c:\angler\images\boot.img
target reported max download size of 494927872 bytes
sending 'boot' (12045 KB)...
OKAY [ 0.287s]
writing 'boot'...
OKAY [ 0.387s]
finished. total time: 0.676s
C:\SDK\platform-tools>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.036s]
finished. total time: 0.037s
C:\SDK\platform-tools>fastboot flash cache C:\angler\images\cache.img
target reported max download size of 494927872 bytes
erasing 'cache'...
OKAY [ 0.018s]
sending 'cache' (5752 KB)...
OKAY [ 0.161s]
writing 'cache'...
OKAY [ 0.226s]
finished. total time: 0.409s
C:\SDK\platform-tools>fastboot flash recovery C:\angler\images\recovery.img
target reported max download size of 494927872 bytes
sending 'recovery' (12977 KB)...
OKAY [ 0.337s]
writing 'recovery'...
OKAY [ 0.406s]
finished. total time: 0.747s
C:\SDK\platform-tools>fastboot flash system C:\angler\images\system.img
target reported max download size of 494927872 bytes
erasing 'system'...
OKAY [ 0.561s]
sending sparse 'system' (478066 KB)...
OKAY [ 12.529s]
writing 'system'...
OKAY [ 6.772s]
sending sparse 'system' (483054 KB)...
OKAY [ 12.458s]
writing 'system'...
OKAY [ 7.038s]
sending sparse 'system' (480089 KB)...
OKAY [ 12.603s]
writing 'system'...
OKAY [ 14.026s]
sending sparse 'system' (469850 KB)...
OKAY [ 12.264s]
writing 'system'...
OKAY [ 22.259s]
sending sparse 'system' (55828 KB)...
OKAY [ 1.530s]
writing 'system'...
OKAY [ 2.856s]
finished. total time: 104.912s
C:\SDK\platform-tools>fastboot flash vendor C:\angler\images\vendor.img
target reported max download size of 494927872 bytes
sending 'vendor' (185185 KB)...
OKAY [ 4.567s]
writing 'vendor'...
OKAY [ 15.101s]
finished. total time: 19.670s
C:\SDK\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.008s
C:\SDK\platform-tools>
Seems like it's possible for you to be in the same exact situation as me, unless you can boot into recovery. I can't do that.
If you can boot into recovery, just take your files off the device and go for a full wipe. I think my device hard bricked itself somehow... You may be soft-bricked, but in the worst case, hard bricked. :c
Yep, I can't boot into recovery either right now because I flashed the factory image. I'll try to re-flash the TWRP recovery and see how it goes.
I can't believe a software issue can get to the stage of hard-bricking your phone while doing nothing other than unlocking and rooting it, and even putting it back to factory and doing a full wipe doesn't resolve it. I really hope I don't get to that stage, although it's disappointing to hear that you've had that experience. Thanks again for your feedback, I'll update once I've attempted to re-flash.
So I finally got around to flashing the TWRP 3.0.2.0 recovery again and still no dice, so I made a start on the backup process.
One thing I wanted to check before I do the full wipe and reinstall stock, though - my partitions in TWRP showed this from the Backup screen;
Code:
Boot (32MB)
System (1850MB)
System Image (3072MB)
Vendor (173MB)
Vendor Image (200MB)
Data (0MB)
Cache (0MB)
Recovery (32MB)
EFS (8MB)
This may just be paranoia, but which of those is the user data (apps, files, photos etc.) stored in? I get that the Data partition is wiped when doing the stock image install, so that's fine, but I presume System would be the OS itself - and I'm pretty sure I have more than 2-3GBs of data on my 6P, but the largest there is 3GB.
Also, using Backup from the TWRP main menu, how do I restore the user data once I've got it back up and running again without killing the OS again? Can I selectively choose what to restore?
I've copied the TWRP backup folder to my laptop using adb pull, so that's safely stored there for now. Just wanted to check before I totally wipe everything and start clean.
Thanks.
MarkB16 said:
So I finally got around to flashing the TWRP 3.0.2.0 recovery again and still no dice, so I made a start on the backup process.
One thing I wanted to check before I do the full wipe and reinstall stock, though - my partitions in TWRP showed this from the Backup screen;
This may just be paranoia, but which of those is the user data (apps, files, photos etc.) stored in? I get that the Data partition is wiped when doing the stock image install, so that's fine, but I presume System would be the OS itself - and I'm pretty sure I have more than 2-3GBs of data on my 6P, but the largest there is 3GB.
Also, using Backup from the TWRP main menu, how do I restore the user data once I've got it back up and running again without killing the OS again? Can I selectively choose what to restore?
I've copied the TWRP backup folder to my laptop using adb pull, so that's safely stored there for now. Just wanted to check before I totally wipe everything and start clean.
Thanks.
Click to expand...
Click to collapse
Did you verify any contents in TWRP that you pulled to ur PC? . In TWRP go to advanced and then file explorer, you should see your data.
Edit: Data would be where the user data is stored (pictures, downloads, etc.)
I terms of restoring data, I've always gone with Titanium Backup but in this case not sure you'd be able to as it sound like u can't boot into the OS and see ur apps?
spunks3 said:
Did you verify any contents in TWRP that you pulled to ur PC? . In TWRP go to advanced and then file explorer, you should see your data.
Edit: Data would be where the user data is stored (pictures, downloads, etc.)
I terms of restoring data, I've always gone with Titanium Backup but in this case not sure you'd be able to as it sound like u can't boot into the OS and see ur apps?
Click to expand...
Click to collapse
Yep, if I go to TWRP, I can view the backups in the \sdcard\TWRP\backups\[serial number] folder, and now that I've done adb pull, they're on my hard drive, too.
Exactly, yeah, it's still boot-looping, so I can't get into the OS to run Titanium Backup or migrate any data. It's still looping at the "Device can't be checked for corruption" screen. I followed Heisenberg's guide to re-flash the stock images and didn't flash userdata. Why would the data partition show as being empty in TWRP unless the partition has been royally messed up when the phone had it's original heart attack?
And, if the data partition is where userdata is stored, I presume that means the data on the phone is already gone? Dumb question, I think I know the answer already, but don't understand how it could have happened when I didn't wipe it myself.
MarkB16 said:
Yep, if I go to TWRP, I can view the backups in the \sdcard\TWRP\backups[serial number] folder, and now that I've done adb pull, they're on my hard drive, too.
Exactly, yeah, it's still boot-looping, so I can't get into the OS to run Titanium Backup or migrate any data. It's still looping at the "Device can't be checked for corruption" screen. I followed Heisenberg's guide to re-flash the stock images and didn't flash userdata. Why would the data partition show as being empty in TWRP unless the partition has been royally messed up when the phone had it's original heart attack?
And, if the data partition is where userdata is stored, I presume that means the data on the phone is already gone? Dumb question, I think I know the answer already, but don't understand how it could have happened when I didn't wipe it myself.
Click to expand...
Click to collapse
You should be able to confirm if the data is really there or not by going into TWRP > Advanced > File Manager.
You should also check to see if data and cache are mounted in TWRP.
I haven't gone over Heisenberg's steps yet but, since you've already attempted to flash userdata, whatever you had is most likey gone.
Try the following via fastboot for erasing everything and starting from scratch.
NOTE: THE FOLLOWING COMMANDS WILL ERASE EVERYTHING ON YOUR PHONE.
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader [name of your file].img
fastboot reboot-bootloader
fastboot flash radio [name of your file].img
fastboot reboot-bootloader
fastboot flash recovery [name of recovery file].img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash vendor vendor.img
fastboot flash cache cache.img
fastboot format userdata
fastboot format cache
That's what I'm saying - at no point have I ever entered the command fastboot erase userdata - I specifically wanted to keep the data and do a backup, and the phrase userdata would be a big red flag to me, so I wouldn't enter it unless I knew for sure the data was already gone. I'm wary of even touching the data partition, so I've been sure to follow all of the commands very carefully. I've been in I.T. for a while, I know the danger of running the wrong command.
I can see that there are data files in the backups, however the data.ext4.win file is only 6KB, so I guess there's no data there.
I don't know how to mount the data and cache partitions in TWRP - I can see the option to do it, but have no idea what it does.
Thanks again.
Mine was the Camera app doing the HDR processing. For the first few times it happened, it was random - the crash and bootloop will happen after taking 2-3 photos. Today, it finally hung while processing HDR and it never recovered. Sigh, seems like I need to send my phone to Huawei. I have tried all sorts of flashing to no avail.
kurtisnet said:
Mine was the Camera app doing the HDR processing. For the first few times it happened, it was random - the crash and bootloop will happen after taking 2-3 photos. Today, it finally hung while processing HDR and it never recovered. Sigh, seems like I need to send my phone to Huawei. I have tried all sorts of flashing to no avail.
Click to expand...
Click to collapse
So my phone isn't the only one with an aversion to taking photos? I don't understand how just taking a photo could cause this unless there's a massive software bug somewhere that requires a very specific set of conditions to brick your device. Would you mind letting me know what Huawei say to your issue? I'm curious as to what they think could cause a failure of this degree.
MarkB16 said:
That's what I'm saying - at no point have I ever entered the command fastboot erase userdata - I specifically wanted to keep the data and do a backup, and the phrase userdata would be a big red flag to me, so I wouldn't enter it unless I knew for sure the data was already gone. I'm wary of even touching the data partition, so I've been sure to follow all of the commands very carefully. I've been in I.T. for a while, I know the danger of running the wrong command.
I can see that there are data files in the backups, however the data.ext4.win file is only 6KB, so I guess there's no data there.
I don't know how to mount the data and cache partitions in TWRP - I can see the option to do it, but have no idea what it does.
Thanks again.
Click to expand...
Click to collapse
If at anytime you did 'fastboot flash userdata userdata.img' you've overwritten the data partition and lost the data :-/ wish I could help more...
MarkB16 said:
So my phone isn't the only one with an aversion to taking photos? I don't understand how just taking a photo could cause this unless there's a massive software bug somewhere that requires a very specific set of conditions to brick your device. Would you mind letting me know what Huawei say to your issue? I'm curious as to what they think could cause a failure of this degree.
Click to expand...
Click to collapse
I've just collected my phone again from Huawei. They replaced the motherboard (new imei number). Sent in at 11.30am today and is ready by 4pm. Applaud Singapore Huawei service center for their super fast turnaround time. Totally was expecting at least a week of repair lol.
Mine was bricked completely - internal storage was accessible from twrp but that was about it. Flashing new roms with everything wiped didn't help. Flashing pure nexus also will sometimes hang and reboot. Sometimes it'll be successful.
spunks3 said:
If at anytime you did 'fastboot flash userdata userdata.img' you've overwritten the data partition and lost the data :-/ wish I could help more...
Click to expand...
Click to collapse
But I didn't, that's what I mean - it's like the data partition has been wiped for no reason at all, or it was part of the initial failure. I haven't run any commands which should touch that partition.
Am I right in thinking that, at this stage, the my data is unrecoverable, and the best bet is just to try to get the phone back up and running again? Are there any other checks I could try to confirm the data is already gone?
Thanks, I do appreciate your input.
kurtisnet said:
I've just collected my phone again from Huawei. They replaced the motherboard (new imei number). Sent in at 11.30am today and is ready by 4pm. Applaud Singapore Huawei service center for their super fast turnaround time. Totally was expecting at least a week of repair lol.
Mine was bricked completely - internal storage was accessible from twrp but that was about it. Flashing new roms with everything wiped didn't help. Flashing pure nexus also will sometimes hang and reboot. Sometimes it'll be successful.
Click to expand...
Click to collapse
Nice, glad they got it sorted so quickly for you. Hoping I can get mine running again, but I'll contact them if I can't.
MarkB16 said:
But I didn't, that's what I mean - it's like the data partition has been wiped for no reason at all, or it was part of the initial failure. I haven't run any commands which should touch that partition.
Am I right in thinking that, at this stage, the my data is unrecoverable, and the best bet is just to try to get the phone back up and running again? Are there any other checks I could try to confirm the data is already gone?
Thanks, I do appreciate your input.
Nice, glad they got it sorted so quickly for you. Hoping I can get mine running again, but I'll contact them if I can't.
Click to expand...
Click to collapse
Hmmmmm... The only other thing that comes to mind is trying something like a fastboot pull command
I've done a full adb pull for all the partitions already, and the data partition file was only 6KB.
One thing I clearly forgot about - I can use File Manager to confirm if the data is there. I've checked there, and all of the files and folders on my device still appear to be shown as normal - if I check /sdcard/DCIM/Camera, I can see my photos, if I check /sdcard/Downloads, I can see stuff I've downloaded, etc. However, when I go to the TWRP menu and choose Backup, the Data partition is 0MB. Tapping Refresh Sizes doesn't change anything.
So if the userdata is stored on the Data partition and I can confirm the files are still on the phone, how is the Data partition showing as 0MB in the Backup screen? What on earth is going on?
The data partition that you backed up isn't userdata, it's the installed apps partition. There is a separate partition for userdata. When installing a new rom, wiping /data in twrp is always a good idea but it won't touch your userdata.
You should be able to mount your phone to your PC while in twrp and copy all your data over, then proceed w a full factory flash to try and correct your problem. When you mount it, it will show up on PC just like a thumb drive.
Related
I think i may have bricked my nexus 10.. I was trying to install the chainfire3d application from the market, and when it rebooted, it wouldnt go past the X logo. waited for a long time, so i tried a hard reset, and still nothing. So i figured i would try using the toolkit to help fix. tried to relock, flash, and re-unlock, and it wouldnt work..after the step where you go into factory reset/wipe, it woudlnt go further. I cant get a custom recovery to install, it wont save the file. tried doing that step separately, and it seems to stick on sending the file over. this seems to be a common issue with anything i try.
The screen says:
"sending TWRP touch recovery..
sending 'recovery' (7246 KB) ...
and is just stuck there. this seems to happen in several places, with a few different things ive tried. When trying to flash the stock image, it will get stuck in similar places, perhaps not with the recovery step, but with a portion of the stock image. Been at this for a couple of hours... any help would be greatly appreciated!.
Also, as of now... it wont boot past the google logo. I can get it into fastboot by holding down the buttons, and I can get it into the stock recovery, but thats it. I don't even think adb is detecting the device. I have a feeling that may be a major roadblock to getting this thing fixed. Does anyone know how I can get the tablet to be detected by adb if i cant even get past the google logo screen at boot?
Update 1:
Still cant unbrick my device. any time i try to transfer or flash files to it... it stalls, and if i disconnect the device, i get this error:
FAILED (data transfer failure (too many links)).
Your Device will now boot into Android and detect ADB mode.
problem is, it doesnt reboot, and even if it did, it wouldnt be able to boot into android, since it wont go past the google logo when the device turns on. in fact, i cant even turn it off. only way to turn it off would be to wait for the battery to drain.
If this helps, here is what it says on the fastboot screen:
Device Information
Product Name: manta
Variant: wifi
H/W version : 8
Bootloader Version: MANTALJ12
Carrier Info: none
Serial Number: *********** (not going to publish that, lol)
LOCK STATE: Unlocked
Reboot Mode Flag: none.
anyone have any ideas at all how I can salvage this thing? Im kindof embarrassed honestly. Ive had 5 android devices prior to this one, and have rooted, flashed, and reflashed each of them countless times, and never, ever ran into this before. I could really use the help.
Quick note:
I just noticed that when i try to flash anything to the tablet, the following appears under the rest of the info i listed above.
FASTBOOT STATUS - DATA00713800 (this text is highlighted in light blue)
Update 2:
ok, so i tried to do the factory restore, and am running into the same wall as always. here is the text from the window, perhaps that may clue you into the problem:
7-Zip (A) 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-18
Processing archive: put_google_factory_image_here\mantaray-jop40c-factory-0d641789.tg
z
Extracting mantaray-jop40c-factory-0d641789.tar
Everything is Ok
Size: 329369600
Compressed: 326396069
Now extracting flashable Images
7-Zip (A) 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-18
Processing archive: put_google_factory_image_here\mantaray-jop40c-factory-0d641789.ta
r
Extracting mantaray-jop40c
Extracting mantaray-jop40c\image-mantaray-jop40c.zip
Extracting mantaray-jop40c\flash-base.sh
Extracting mantaray-jop40c\bootloader-manta-mantalj12.img
Extracting mantaray-jop40c\flash-all.sh
Extracting mantaray-jop40c\flash-all.bat
Everything is Ok
Folders: 1
Files: 5
Size: 329358105
Compressed: 329369600
Factory Images extracted. Starting Flash Process.
Now Flashing Bootloader Image..
sending 'bootloader' (1280 KB)... OKAY [ 0.232s]
writing 'bootloader'... OKAY [ 0.113s]
finished. total time: 0.345s
rebooting into bootloader... OKAY [ 0.001s]
finished. total time: 0.001s
Now Flashing Factory Image: Boot, Cache, Recovery, System and Userdata..
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: R32CB01KDWW
--------------------------------------------
checking product... OKAY [ 0.001s]
checking version-bootloader... OKAY [ 0.002s]
sending 'boot' (4606 KB)...
Its just stuck on that last part, sending 'boot' (4606 KB)...
and under all the info on the fastboot page, the following appeared while this was happening:
FASTBOOT STATUS - DATA0047f800 (this line is highlighted in light blue)
*Bump* That's really unfortunate. I managed to fixed my soft brick after unlocking and flashing TWRP with a factory image. There was no highlighted blue text, everything went smooth. I hope your issue get fixed
P.S. I did not use the toolkit. If you can boot to your bootloader (fastboot), try running the shell/batch scripts included with the factory image? (This is just following Google's instruction on the factory image download page)
cuguy said:
*Bump* That's really unfortunate. I managed to fixed my soft brick after unlocking and flashing TWRP with a factory image. There was no highlighted blue text, everything went smooth. I hope your issue get fixed
P.S. I did not use the toolkit. If you can boot to your bootloader (fastboot), try running the shell/batch scripts included with the factory image? (This is just following Google's instruction on the factory image download page)
Click to expand...
Click to collapse
can you link it?
cuguy said:
*Bump* That's really unfortunate. I managed to fixed my soft brick after unlocking and flashing TWRP with a factory image. There was no highlighted blue text, everything went smooth. I hope your issue get fixed
P.S. I did not use the toolkit. If you can boot to your bootloader (fastboot), try running the shell/batch scripts included with the factory image? (This is just following Google's instruction on the factory image download page)
Click to expand...
Click to collapse
trying that....
so far so good... dont want to get my hopes up though... below is what ive got so far in the cmd screen:
sending 'bootloader' (1280 KB)...
OKAY [ 0.162s]
writing 'bootloader'...
OKAY [ 0.125s]
finished. total time: 0.288s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: R32CB01KDWW
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.002s]
sending 'boot' (4606 KB)...
OKAY [ 32.528s]
writing 'boot'...
OKAY [ 0.116s]
sending 'recovery' (5106 KB)...
OKAY [ 56.840s]
writing 'recovery'...
OKAY [ 0.119s]
sending 'system' (528847 KB)...
Its been about 30 minutes now... and its still stuck on "sending 'system' (528847 KB)..." in the cmd window.... not sure what that means... it did take about a minute for the recovery to get sent over, and its about 100x larger in size, so i guess i will leave it connected like this for the next hour or so... and hope that it is just going REALLY slowly. Got my fingers crossed...
Battery died while waiting.... this is the complete text of the CMD screen while i was waiting.. forgot that it doesnt charge while in fastboot. got it plugged into an outlet for faster charging while its off.... hopefully when its charged up, i can try again and ill continue to progress
sending 'bootloader' (1280 KB)...
OKAY [ 0.162s]
writing 'bootloader'...
OKAY [ 0.125s]
finished. total time: 0.288s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: R32CB01KDWW
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.002s]
sending 'boot' (4606 KB)...
OKAY [ 32.528s]
writing 'boot'...
OKAY [ 0.116s]
sending 'recovery' (5106 KB)...
OKAY [ 56.840s]
writing 'recovery'...
OKAY [ 0.119s]
sending 'system' (528847 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 3941.094s
Press any key to exit...
Did you try to run e2fsck on all partitions (boot, system, userdata) and check whether there are any errors?
You can run it via adb once you boot into TWRP or CWM recovery. Here is more info:
http://forum.xda-developers.com/showthread.php?p=34923662
Ps.
I also bricked my nexus 10 while transferring files on it in windows. Nothing so far helped me. e2fsck doesn't see any partitions
I believe this is something to-do with a corrupted flash memory. Your case looks about the same.
jodvova said:
Did you try to run e2fsck on all partitions (boot, system, userdata) and check whether there are any errors?
You can run it via adb once you boot into TWRP or CWM recovery. Here is more info:
http://forum.xda-developers.com/showthread.php?p=34923662
Ps.
I also bricked my nexus 10 while transferring files on it in windows. Nothing so far helped me. e2fsck doesn't see any partitions
I believe this is something to-do with a corrupted flash memory. Your case looks about the same.
Click to expand...
Click to collapse
I cant get it to load a custom recovery! any advice on how to get that going?
ltracte said:
I cant get it to load a custom recovery! any advice on how to get that going?
Click to expand...
Click to collapse
So, if you run "fastboot boot twrp-image.img" under your current bootloader it doesn't boot it?
Also, If I remember it correctly, you can also boot in to a existing recovery and then run shell commands via adb.
ltracte said:
I cant get it to load a custom recovery! any advice on how to get that going?
Click to expand...
Click to collapse
Dumb question, if using a desktop PC are you using the front or rear USB ports? I had a similar issue where it would just get stuck on the "sending system" message. Switched the USB from front port to back port on my linux box and it solved my problem.
Sent from my Nexus 10 using Tapatalk 2
jodvova said:
So, if you run "fastboot boot twrp-image.img" under your current bootloader it doesn't boot it?
Also, If I remember it correctly, you can also boot in to a existing recovery and then run shell commands via adb.
Click to expand...
Click to collapse
i got twrp to load that way! thanks... what now? i cant get the device to mount so i can put the zip file of a rom on there.
ltracte said:
i got twrp to load that way! thanks... what now? i cant get the device to mount so i can put the zip file of a rom on there.
Click to expand...
Click to collapse
What I meant was, you can now run e2fsck and check all partitions for consistency. Refer to a thread that I posted a few comments back. You can run e2fsck either via a terminal session in TWRP or via adb shell.
jodvova said:
What I meant was, you can now run e2fsck and check all partitions for consistency. Refer to a thread that I posted a few comments back. You can run e2fsck either via a terminal session in TWRP or via adb shell.
Click to expand...
Click to collapse
couldnt get the command to work via adb, so i tried it using terminal inside TWRP, and this what it spit back at me:
/dev/block/platform/dw_mmc.0/by-name/system: clean. 11/51296 files. 6651/204800 blocks
i have no idea what that means, nor what else to do....
Fixed it!!!!
ltracte said:
Fixed it!!!!
Click to expand...
Click to collapse
Glad you fixed your problem. Please post any relevant information that may help people in the same situation.
Mark.
mskip said:
Glad you fixed your problem. Please post any relevant information that may help people in the same situation.
Mark.
Click to expand...
Click to collapse
well.. i loaded it into the bootloader, unzipped the factory image, and everything inside it into the platform-tools folder in my android sdk directory on my pc so i could use ADB
then i did the following via adb
fastboot flash bootloader bootloader-manta-mantalj12.img
fastboot reboot-bootloader
fastboot -w update image-mantaray-jop40c.zip.
the first time it got stuck pushing the system.img file, i let it run for almost an hour before giving up. then the battery on the tablet died. let it charge for about an hour, plugged it back in, reran the last command from above, and for some reason, the whole thing went through without a hitch. wish i could explain why it worked that time, but I cant. hope this helps someone else that encountered the issue.
thanks again to everyone that offered any input!
Whew! So glad you finally had success & thanks for sharing. I'm reading up, research, etc. I received my N10 yesterday. I'm getting ready to unlock/root today.
Sent from my Nexus 7 using Tapatalk 2
ltracte said:
well.. i loaded it into the bootloader, unzipped the factory image, and everything inside it into the platform-tools folder in my android sdk directory on my pc so i could use ADB
then i did the following via adb
fastboot flash bootloader bootloader-manta-mantalj12.img
fastboot reboot-bootloader
fastboot -w update image-mantaray-jop40c.zip.
the first time it got stuck pushing the system.img file, i let it run for almost an hour before giving up. then the battery on the tablet died. let it charge for about an hour, plugged it back in, reran the last command from above, and for some reason, the whole thing went through without a hitch. wish i could explain why it worked that time, but I cant. hope this helps someone else that encountered the issue.
thanks again to everyone that offered any input!
Click to expand...
Click to collapse
Hmm, did you try the flash-all.bat file that comes with the factory image? It does those 3 commands, + erases all partitions automatically.
ltracte said:
well.. i loaded it into the bootloader, unzipped the factory image, and everything inside it into the platform-tools folder in my android sdk directory on my pc so i could use ADB
then i did the following via adb
fastboot flash bootloader bootloader-manta-mantalj12.img
fastboot reboot-bootloader
fastboot -w update image-mantaray-jop40c.zip.
the first time it got stuck pushing the system.img file, i let it run for almost an hour before giving up. then the battery on the tablet died. let it charge for about an hour, plugged it back in, reran the last command from above, and for some reason, the whole thing went through without a hitch. wish i could explain why it worked that time, but I cant. hope this helps someone else that encountered the issue.
thanks again to everyone that offered any input!
Click to expand...
Click to collapse
That's exactly what I did. Just followed the factory image flashing instruction on google's page(where you download the image file for N10). Did you figure out why it wassnt able to transfer the first time?
Hey guys. Hoping to get some assistance here. My N10 seems to always freeze on the google (with the unlock icon) screen. I was coming from Mr Robinson's Buttered AOKP 4.2.2 to PAC MAN 4.3. I performed a factory reset and formated my data. Flashed the appropraite ROM and GAPPS after which I performed a reboot. This is when it decided to freeze up. Saw this and said to myself "no biggie" and repeated the aforementioned steps again just in case there was an error on my part. After performing this again it was a success. Started up the setup procedure and began downloading TBU to restore my apps. After downloading TBU I turned it off, took a break, and about 15 minutes later, powered it back on and to my surprise it was stuck on the Google screen again. I thought maybe the ROM file I flashed was corrupted so I tried flashing CM 10.2, and a few others. Every initial boot after installation I have no problems but any reboot afterwards brings me back to the frozen Google screen. At this point I'm stuck. Anyone have any ideas? Suggestions? Any help will be appreciated.
The Google screen represents the bootloader, and has nothing to do with the ROM. Two reasons I could think of.
1. Your bootloader's funky. I find that hard to believe, but it's possible. A full factory image flash(including manually erasing the bootloader) would fix this.
2. Your partitions are funky. You may have seen/heard about issues like this from the Kindle Fires I see in your signature. If even one partition is out of place(from a bad flash or otherwise) the system will refuse to boot. It sounds like it's either the userdata(media) or the cache partition, seeing as how the system boots fine once, but gets corrupted later(when these partitions get altered). Again, a full factory flash should fix this issue.
Or it could be something really simple, but that's all I've got. I've never heard of this issue before.
Just my luck to have an uncommon issue lol. I did notice now that when I boot into the bootloader on my way to recovery it always starts being stuck in download mode and only after holding down all of the buttons does it allow me to use the volume buttons to select starting up in recovery. The tablet also doesnt want to stay shut off and immediately reboots after powering off. What you said definitely makes sense especially with the two other issues I just mentioned. Definitely wont be the quickest fix and wqs hoping that there would be a quicker remedy but off course will do it if I have to. Are the root and unlock steps similar to the methods of the earlier versions of Jelly Bean? How does one go about manually deleting the bootloader?
Sent from my SGH-I317 using Tapatalk 4
Koopa777 said:
The Google screen represents the bootloader, and has nothing to do with the ROM. Two reasons I could think of.
1. Your bootloader's funky. I find that hard to believe, but it's possible. A full factory image flash(including manually erasing the bootloader) would fix this.
2. Your partitions are funky. You may have seen/heard about issues like this from the Kindle Fires I see in your signature. If even one partition is out of place(from a bad flash or otherwise) the system will refuse to boot. It sounds like it's either the userdata(media) or the cache partition, seeing as how the system boots fine once, but gets corrupted later(when these partitions get altered). Again, a full factory flash should fix this issue.
Or it could be something really simple, but that's all I've got. I've never heard of this issue before.
Click to expand...
Click to collapse
I think I have a similar problem myself. However, my device wont boot into bootloader. It won't turn on. How would you typically do a full factory image flash if that's the case?
I also got some message when I tried to flash my device saying that it failed to update the partition table, so that matches what you just said.
I'll update this post with a guide for both of you later tonight, as I'm out of town. IBalic, try to press and hold all 3 buttons to attempt to boot into fastboot. If that doesn't work, put it on the charger for awhile then try.
Sent from my MB855 using xda app-developers app
Koopa777 said:
I'll update this post with a guide for both of you later tonight, as I'm out of town. IBalic, try to press and hold all 3 buttons to attempt to boot into fastboot. If that doesn't work, put it on the charger for awhile then try.
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
That would be much appreciated. I was searching around xda earlier and came across a factory 4.3 image thread that also had a seperate bootloader zip file. I'm assuming it wouldn't be that easy but just in case I asked them if there was a way that I could just flash (recovery/fastboot) it to replace the corrupted one.
IBalic said:
I think I have a similar problem myself. However, my device wont boot into bootloader. It won't turn on. How would you typically do a full factory image flash if that's the case?
I also got some message when I tried to flash my device saying that it failed to update the partition table, so that matches what you just said.
Click to expand...
Click to collapse
Hey. I saw a similar issue somewhere else, the tablet simply wouldn't boot, the problem was solved leaving it charging for 1h, then unplugging, putting back while trying to power on and leaving overnight charging. Maybe you can try this .
Gameraddikted said:
That would be much appreciated. I was searching around xda earlier and came across a factory 4.3 image thread that also had a seperate bootloader zip file. I'm assuming it wouldn't be that easy but just in case I asked them if there was a way that I could just flash (recovery/fastboot) it to replace the corrupted one.
Click to expand...
Click to collapse
To factory reset follow this:
Download and get the factory image, I'd recommend you getting them from http://developers.google.com/android/nexus/images.
Extract it and later I'll update this post with a link to a fastboot/adb environment, that way it'll ease your life, if you want to do this now, extract the zip to your fastboot folder, plug your tablet on bootloader mode and type the following:
Code:
flash-all.bat
After that, if worked, you may got it flashed back to stock. If you're with partitions problem, then I'll think a little more and try to solve your problems for you .
Disclaimer: I'm not responsible for any damage!
Cheers,
~Lord
"We think so supersonic and we make our bombs atomic" - Eagle Fly Free (Helloween)
Sent from my Nexus 10 using Tapatalk HD
XxLordxX said:
Hey. I saw a similar issue somewhere else, the tablet simply wouldn't boot, the problem was solved leaving it charging for 1h, then unplugging, putting back while trying to power on and leaving overnight charging. Maybe you can try this .
To factory reset follow this:
Download and get the factory image, I'd recommend you getting them from http://developers.google.com/android/nexus/images.
Extract it and later I'll update this post with a link to a fastboot/adb environment, that way it'll ease your life, if you want to do this now, extract the zip to your fastboot folder, plug your tablet on bootloader mode and type the following:
Code:
flash-all.bat
After that, if worked, you may got it flashed back to stock. If you're with partitions problem, then I'll think a little more and try to solve your problems for you .
Disclaimer: I'm not responsible for any damage!
Cheers,
~Lord
"We think so supersonic and we make our bombs atomic" - Eagle Fly Free (Helloween)
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
I appreciate the help. I downloaded the factory image via the link you provided. When you say extracting the zip file to my fastboot folder do you mean my adroid-adb (aka. platform-tools) folder? Should I make a separate folder or just put everything in the root? Just to get the ball rolling I extracted the download to the root of the folder and ran the flash-all.bat command which started but kicked out some errors. I also noticed that the actual image is "zipped" inside the tgz file. Should I extract that as well or leave it be? Thanks
Gameraddikted said:
I appreciate the help. I downloaded the factory image via the link you provided. When you say extracting the zip file to my fastboot folder do you mean my adroid-adb (aka. platform-tools) folder? Should I make a separate folder or just put everything in the root? Just to get the ball rolling I extracted the download to the root of the folder and ran the flash-all.bat command which started but kicked out some errors. I also noticed that the actual image is "zipped" inside the tgz file. Should I extract that as well or leave it be? Thanks
Click to expand...
Click to collapse
As far as I remember the file you downloaded contains a folder with some files, if you feel more convenient copy all the files in the platform-tools to a new folder and copy also the files from the extracted download to this folder as well, then try again. If you don't get again, please send me the error report and the flash-all.bat file .
All the best,
~Lord
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my GT-I9505
XxLordxX said:
As far as I remember the file you downloaded contains a folder with some files, if you feel more convenient copy all the files in the platform-tools to a new folder and copy also the files from the extracted download to this folder as well, then try again. If you don't get again, please send me the error report and the flash-all.bat file .
All the best,
~Lord
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my GT-I9505
Click to expand...
Click to collapse
I tried both ways just in case. One with the embedded zip file extracted and the other "as is." This is the error I'm receiving although afterwards attempting it seems everything (bootloader, recovery, etc) has been deleted just as the command prompt states but for some reason they weren't replaced by the factory items:
C:\Users\Ben>flash-all.bat
erasing 'boot'...
OKAY [ 0.027s]
finished. total time: 0.027s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.094s]
finished. total time: 0.095s
erasing 'recovery'...
OKAY [ 0.025s]
finished. total time: 0.026s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.149s]
finished. total time: 0.150s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.456s]
finished. total time: 0.457s
error: cannot load 'bootloader-manta-mantamd03.img': Unknown error
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
< waiting for device >
error: failed to load 'image-mantaray-jwr66v.zip': No error
Press any key to exit...
Gameraddikted said:
I tried both ways just in case. One with the embedded zip file extracted and the other "as is." This is the error I'm receiving although afterwards attempting it seems everything (bootloader, recovery, etc) has been deleted just as the command prompt states but for some reason they weren't replaced by the factory items:
C:\Users\Ben>flash-all.bat
erasing 'boot'...
OKAY [ 0.027s]
finished. total time: 0.027s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.094s]
finished. total time: 0.095s
erasing 'recovery'...
OKAY [ 0.025s]
finished. total time: 0.026s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.149s]
finished. total time: 0.150s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.456s]
finished. total time: 0.457s
error: cannot load 'bootloader-manta-mantamd03.img': Unknown error
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
< waiting for device >
error: failed to load 'image-mantaray-jwr66v.zip': No error
Press any key to exit...
Click to expand...
Click to collapse
Hmm... Let's try doing it manually then. The partitions are already formated so it's all cool. Extract the zip, you'll get a few .img files, copy them all to your fastboot folder, plug you Nexus in bootloader mode then open a cmd there. Type:
Code:
fastboot flash bootloader bootloader-manta-mantamd3.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash cache cache.img
fastboot reboot
If this doesn't solve the issue I'll send you a reply later when I arrive home. Thanks for the patience
All the best,
~Lord
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my GT-I9505
XxLordxX said:
Hmm... Let's try doing it manually then. The partitions are already formated so it's all cool. Extract the zip, you'll get a few .img files, copy them all to your fastboot folder, plug you Nexus in bootloader mode then open a cmd there. Type:
Code:
fastboot flash bootloader bootloader-manta-mantamd3.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash cache cache.img
fastboot reboot
If this doesn't solve the issue I'll send you a reply later when I arrive home. Thanks for the patience
All the best,
~Lord
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my GT-I9505
Click to expand...
Click to collapse
Boom! This worked perfectly! Thanks so much for your help. I'm up and running again on PAC. Now if I can only figure out a way to restore my game backups for games that require extra downloads. Off to the forums again. Thanks again for your help :thumbup:
Sent from my SGH-I317 using Tapatalk 4
Due to my sensors being completely gone in 5.1 on my Nexus 4, I decided to flash the new 5.1.1 image. Did a backup in CWM (which is now lost, CWM recovery wipe/reset removes its own backups pffft ), flashed the factory image except userdata.img ... and boot loop. Did a backup of everything (CWM), repeated, still the boot loop. Tried CWM reset (which is supposed to leave backups), no joy. Tried restoring backup, GONE. Sigh. (Should've adb pulled /sdcard/ , I know. )
Okay, so flashed everything again incl. userdata.img. Still boot loop.
Flashed 4.4.4 on it and performed stock recovery reset. No joy. LOcked bootloader, then unlocked again, JOY. Booted up into 4.4.4, and lo and friggin' behold, sensors are all there.
So flashed 5.1.1 factory image completely (bootloader, radio, recovery, boot, cache, system, userdata images). And again the infinite boot animation. Tried locking and then unlocking bootloader. no joy.
Each time I'm giving the phone 5 minutes of the animation to continue to setup, more than enough.
The flash-all.bat file hasn't worked in the past (missing sig file warnings),[1] so I'm unpacking image-occam-lmy47v.zip and fastboot flashing each partition by hand.
[1] This time it's working, so ... patience wins.
sending 'bootloader' (2264 KB)...
OKAY [ 0.078s]
writing 'bootloader'...
OKAY [ 0.312s]
finished. total time: 0.391s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
sending 'radio' (45537 KB)...
OKAY [ 2.781s]
writing 'radio'...
OKAY [ 2.375s]
finished. total time: 5.188s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.062s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 14129561600
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3449600
Block groups: 106
Reserved block group size: 847
Created filesystem with 11/863264 inodes and 95427/3449600 blocks
Creating filesystem with parameters:
Size: 587202560
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 2240
Label:
Blocks: 143360
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35840 inodes and 4616/143360 blocks
--------------------------------------------
Bootloader Version...: MAKOZ30f
Baseband Version.....: M9615A-CEFWMAZM-2.0.1701.07
Serial Number........: 018ce19f988a6159
--------------------------------------------
checking product...
OKAY [ 0.000s]
checking version-bootloader...
OKAY [ 0.000s]
checking version-baseband...
OKAY [ 0.000s]
sending 'boot' (6398 KB)...
OKAY [ 4.125s]
writing 'boot'...
OKAY [ 0.328s]
sending 'recovery' (6960 KB)...
OKAY [ 1.281s]
writing 'recovery'...
OKAY [ 0.375s]
erasing 'system'...
OKAY [ 0.812s]
sending 'system' (834754 KB)...
OKAY [ 39.891s]
writing 'system'...
Click to expand...
Click to collapse
Anyone else encountering problems with the 5.1.1 factory image?
ChromeJob said:
Due to my sensors being completely gone in 5.1 on my Nexus 4, I decided to flash the new 5.1.1 image. Did a backup in CWM (which is now lost, CWM recovery wipe/reset removes its own backups pffft ), flashed the factory image except userdata.img ... and boot loop. Did a backup of everything (CWM), repeated, still the boot loop. Tried CWM reset (which is supposed to leave backups), no joy. Tried restoring backup, GONE. Sigh. (Should've adb pulled /sdcard/ , I know. )
Okay, so flashed everything again incl. userdata.img. Still boot loop.
Flashed 4.4.4 on it and performed stock recovery reset. No joy. LOcked bootloader, then unlocked again, JOY. Booted up into 4.4.4, and lo and friggin' behold, sensors are all there.
So flashed 5.1.1 factory image completely (bootloader, radio, recovery, boot, cache, system, userdata images). And again the infinite boot animation. Tried locking and then unlocking bootloader. no joy.
Each time I'm giving the phone 5 minutes of the animation to continue to setup, more than enough.
The flash-all.bat file hasn't worked in the past (missing sig file warnings),[1] so I'm unpacking image-occam-lmy47v.zip and fastboot flashing each partition by hand.
[1] This time it's working, so ... patience wins.
Anyone else encountering problems with the 5.1.1 factory image?
Click to expand...
Click to collapse
5 minutes? Takes at least 10 min to boot from flashing images on 5.0+. You likely are not looping, it just takes a very long time. You will see the screen dim at one point, and that signals like the last 25% or so of your wait, but if you do not see any errors, you are 99.99% likely just not waiting long enough.
Actually, my first flash of the 5.1.1 image files failed. Not sure if it was fastboot crashing on my laptop, or the fact my hyper kids were able to momentarily disconnect the USB while flashing, but I got an error sending system the first time.
ariesgodofwar said:
5 minutes? Takes at least 10 min to boot from flashing images on 5.0+. You likely are not looping, it just takes a very long time. You will see the screen dim at one point, and that signals like the last 25% or so of your wait, but if you do not see any errors, you are 99.99% likely just not waiting long enough.
Actually, my first flash of the 5.1.1 image files failed. Not sure if it was fastboot crashing on my laptop, or the fact my hyper kids were able to momentarily disconnect the USB while flashing, but I got an error sending system the first time.
Click to expand...
Click to collapse
Thanks, seems I have to go through this at least once a year ... not taking time to copy my CWM backup (adb pull /sdcard/ . ), etc. Not waiting for flash-all.bat to finish. Yada yada yada. I know that I'd set the N4 booting for more than 10 minutes (taking a shower and getting dressed, doing my 1-1/2 mile run -- 15 minutes -- etc).
Successfully installed and configured 4.4.4 again (good to clean out a system a bit. Will try again now that I've got a backup in hand, on a USB drive. Thanks for the feedback.
Having made and stored a successful backup, have been trying the 5.1 and 5.1.1 factory image install scripts with and without the -w userdata switch ... in all cases, the phone stays in a boot animation loop for longer than 15 minutes.
Is this Google's passive aggressive way of telling us the N4 is no longer supported? I.e. issue a broken factory image and leave us to stew in our juices?
I tried further tests last night and this morning with pure, straight factory image scripts, and the 5.1, 5.1.1 image just won't boot up on a Nexus 4. Pffft. I really wanted to see if the sensor problems were from an upgrade I did, or if it's a clear fault on a new vanilla install of stock 5.1.x. But it never worked. (I think I was running 5.0.1 until yesterday.)
This is infuriating.
Back to 4.4.4 because ... I need my phone, darn it!
I have the same problem. i tried everything, its now looping for a hour...
Maybe you might give installing 4.4.4 stock a try, and then upgrading via the OTAs instead of the images? The 5.1.1 images are not broken as I was able to flash without issue, so I am not thinking it is a problem with the images themselves.
If you are sure you are waiting long enough, I do know the was an issue with the 4.4.4->5.0 flash from the images where you literally had to flash and if you just left it, the dots would spin endlessly. This was remedied by then rebooting to bootloader, wiping the cache partition from bootloader, and rebooting. It would then boot just fine. It was just the N4 I found this to be the case on. I am pretty sure Wug even made an allowance for it in the NRT code (2.0.3 I think). Are you using 2.0.5 NRT to flash the images? If not, you might give it a try.
Adding- Are you trying to go from 4.4.4 to 5.1.1 directly? I can't recall if there were changes, but you might try flashing the 5.0 images from 4.4.4, and then going up to 5.1.1 just in case there is some issue with the version leap which is causing your issue.
Yes i tried have formated the partition and everything. I just go take a step backwards, i am currently installing 5.0.1, if thats not working i gonna flash 4.4.4. I wil give a update if i succeeded.
joostburg said:
Yes i tried have formated the partition and everything. I just go take a step backwards, i am currently installing 5.0.1, if thats not working i gonna flash 4.4.4. I wil give a update if i succeeded.
Click to expand...
Click to collapse
Just to be clear, when in bootloop, try rebooting to bootloader (hold Volume- and power) to get the android laying down with his chest open, and then I think it is hold Vol+ and tap pwr that will get you to the menu you are looking for.
Go in and just wipe the cache partition and reboot. Do not reformat it or anything. Just wipe cache, reboot, and then give it 10-15 minutes.
Still nothing works, damn tried now everything. How long should i see the 4 dots spinning approximately? 15, 30 or 60 minutes? Normally i just see it for about 5 minutes with a fresh installation.
edit: now its optimizing my apps, hope i am finally there now.
"The idea is simple. After you dirty flash the required images (boot, system and radio), install a custom recovery (CWM or TWRP) and clear "cache" AND "dalvik-cache". Bootloop avoided.You might think it's enough to just clear the cache. It's not. Trust me, I've tested this extensively." http://www.reddit.com/r/nexus4/comments/36r8s2/how_to_avoid_a_bootloop_when_flashing_the_511_or/
joostburg said:
Still nothing works, damn tried now everything. How long should i see the 4 dots spinning approximately? 15, 30 or 60 minutes? Normally i just see it for about 5 minutes with a fresh installation.
edit: now its optimizing my apps, hope i am finally there now.
"The idea is simple. After you dirty flash the required images (boot, system and radio), install a custom recovery (CWM or TWRP) and clear "cache" AND "dalvik-cache". Bootloop avoided.You might think it's enough to just clear the cache. It's not. Trust me, I've tested this extensively." http://www.reddit.com/r/nexus4/comments/36r8s2/how_to_avoid_a_bootloop_when_flashing_the_511_or/
Click to expand...
Click to collapse
I told you it takes an ungodly amount of time. I have more than a few times almost pulled the plug too early thinking it was taking too long.
Afters apps are optimized, i get a starting apps screen or something like that. After 8 hours its still showing that screen, pffff.
Edit: When i try to wipe data or internal storage i get:
e:Unable to mount /data
e:Unable to mount usb-otg
ariesgodofwar said:
Just to be clear, when in bootloop, try rebooting to bootloader (hold Volume- and power) to get the android laying down with his chest open, and then I think it is hold Vol+ and tap pwr that will get you to the menu you are looking for.
Go in and just wipe the cache partition and reboot. Do not reformat it or anything. Just wipe cache, reboot, and then give it 10-15 minutes.
Click to expand...
Click to collapse
Let's be clear about how to wipe cache, you can't do it in the bootloader.
Power off
Hold Power and VOL DOWN => bootloader
VOL to select Recovery
Power to enter Recovery.
In stock Recovery "fallen Android" icon, hold POWER and VOL UP => Recovery menu
Now use vol and power buttons to select Wipe cache partition.
My final attempt after doing factory reset/wipe data in stock recovery, using the factory image flash-all.bat and NOT removing the -w switch (so /userdata/ is overwritten as well), the N4 didn't boot after waiting > 30 minutes.
INteresting about clearing cache and Dalvik cache during factory flash ... Dalvik cache should be irrelevant with ART being default in Lollipop....
ChromeJob said:
Let's be clear about how to wipe cache, you can't do it in the bootloader.
Power off
Hold Power and VOL DOWN => bootloader
VOL to select Recovery
Power to enter Recovery.
In stock Recovery "fallen Android" icon, hold POWER and VOL UP => Recovery menu
Now use vol and power buttons to select Wipe cache partition.
My final attempt after doing factory reset/wipe data in stock recovery, using the factory image flash-all.bat and NOT removing the -w switch (so /userdata/ is overwritten as well), the N4 didn't boot after waiting > 30 minutes.
Click to expand...
Click to collapse
I did exact the some for the fifth time and after an hour still 4 dancing dots. OMG gonna throw my phone trough a wall! BTW if i wipe the dalvik cache the phone will boot then get a infinite loop after optimizing apps with android is starting apps.
Same. Tried the instructions on that reddit article, posted this:
... I cleared the cache with stock recovery, no joy. Powered off, flashed CWM recovery, cleared cache and Dalvik-cache with CWM, then reflashed stock recovery, then rebooted, endless "starting apps."
Now that I know this, I'm flashing 5.0.1 with existing apps, will either wait a day for OTA, or try flashing the factory image again over 5.0.1 with the caches clearing. Maybe some app is causing the problem. I know I was able to flash 5.0.1 previously over 4.4.4....
I just don't get how the 5.1.1 image is working for some people. It seems that as Android progresses, there are more and more little undocumented tricks and gimmicks that we have to use to update a factory image without wiping data....
And my kitchen In-Sink-Erator just bit the dust, so I've got that to deal with as well. (sigh)
I give up... Hope someone can post the solution. I gonna borrow a other phone, this is not gonna work.
Oh, I got caught up in several things ... 5.0.1 didn't work, though I previously installed it OVER 4.4.4. Pffft.
Frankly, I think 4.4.4 was a fine OS version running on the N4. ART, Material Design, etc....
5 has its enhancements, but I can't live without my sensors working properly.[1] They've got some bug fixin' to do....
[1] I didn't even know 5.1 or 5.1.1 was out, I was troubleshooting the sensors being gone in 5.0.1, searched online for similar reports, saw the new OTA announcements.
So ChromeJob and joostburg, were you guys at least able to manually flash back to 4.4.4?
Also, ChromeJob, on my post, you commented:
For your problem, download the factory image, then edit flash-all.bat/sh and remove the -w from the last flash command (-w rewrites /userdata partition). Whether you use 5.0.1 or 4.4.4 is up to you.
Click to expand...
Click to collapse
May you please explain this a little?
No i tried but the 4 dots won't disappear. I am phone less for more than 48 hours now lol, and all the stores are closed till Tuesday, fml.
About the -w flag, when you download the stock roms from google you have a file flash-all.bat, when you edit this file with notepad you will see -w, that stand for wiping your device (remove all data), when you remove the -w (backspace, backspace) save the file and execute your data will NOT be removed.
By the way, when i try to clear my sd card in custom recovery i get: e:mount -o bind '/data/media/0' '/sdcard' proces ended with error=255, is this the cause?
hmmzz, i did a last try with 4.4.4, did first factory reset and then a cache wipe and it booted again, finally.
Good day, this morning when the alarm woke me up I saw a huge amount of errors on my redmi 2, I tried to reboot it but during the miui loading screen it didn't go forward, then I started the phone in fastboot, started twrp but when I did something weird happened, it has lost every setting of twrp but more important the internal storage was 0mb, I tried to restore a backup, to flash a new rom but it obviously failed, the only partition it was able to flash was the system, all others: dalvik, cache, data etc. are 0mb.
I fear the internal memory is gone but is there something that I could try to restore it before give up and throw it into the trash?
Thank you.
Nemo1985 said:
Good day, this morning when the alarm woke me up I saw a huge amount of errors on my redmi 2, I tried to reboot it but during the miui loading screen it didn't go forward, then I started the phone in fastboot, started twrp but when I did something weird happened, it has lost every setting of twrp but more important the internal storage was 0mb, I tried to restore a backup, to flash a new rom but it obviously failed, the only partition it was able to flash was the system, all others: dalvik, cache, data etc. are 0mb.
I fear the internal memory is gone but is there something that I could try to restore it before give up and throw it into the trash?
Thank you.
Click to expand...
Click to collapse
Good evening, friend, do you have access to fastboot?
Fz3r0 said:
Good evening, friend, do you have access to fastboot?
Click to expand...
Click to collapse
Yes I do.
Nemo1985 said:
Yes I do.
Click to expand...
Click to collapse
Try https://forum.xda-developers.com/redmi-2/how-to/error-resolved-t3324791
Fz3r0 said:
Try https://forum.xda-developers.com/redmi-2/how-to/error-resolved-t3324791
Click to expand...
Click to collapse
Thank you, unlucky this isn't working:
>fastboot flash partition gpt_both0.bin
target reported max download size of 268435456 bytes
sending 'partition' (33 KB)...
OKAY [ 0.006s]
writing 'partition'...
FAILED (remote: failed to write partition)
finished. total time: 0.043s
Seems a common situation for people with redmi 2, a corrupted emmc
Nemo1985 said:
Thank you, unlucky this isn't working:
>fastboot flash partition gpt_both0.bin
target reported max download size of 268435456 bytes
sending 'partition' (33 KB)...
OKAY [ 0.006s]
writing 'partition'...
FAILED (remote: failed to write partition)
finished. total time: 0.043s
Seems a common situation for people with redmi 2, a corrupted emmc
Click to expand...
Click to collapse
Ooh
Try flash ROM via adb - fastboot
Boot to fastboot...open mi pc suite..it will show update option...select stable...it will wipe everything and install a clean miui stable rom
Hello,
I was trying to bring phone back to factory state and I messed things up. My options are very limited and I'd like to ask for help.
I have Revolution Recovery installed on my phone. I made backups of data, system, boot, oeminfo, cust. I flashed custom oeminfo from this thread. I hoped to download a rescue package via Huawei eRecovery. But it said that my data partition is corrupted and asked me to format it. So I did. My data is wiped and formatted. But it shows cannot download package after trying.
Right now, I can access fastboot, but I cannot flash anything:
Code:
$ fastboot flash recovery ~/Desktop/RevolutionRecovery_Nougat_P9Lite/TWRP.img
target reported max download size of 471859200 bytes
sending 'recovery' (27434 KB)...
OKAY [ 0.691s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.697s
When I try to start the phone (normal start, or volume up + power key) it goes straight to Huawei eRecovery. I cannot open recovery.
My phone is VNS-L31, before any changes I wrote down build number from system settings: VNS-L31C432B371. I bought it through an online store in Switzerland last summer, so I probably have some Europe edition. I don't have any backups from the initial state before I even had my custom rom installed.
Is there any chance to install recovery or whatever straight from SD card?
I'm happy to provide any additional data if I know what else is needed.
Thanks for help!
There is. That "FAILED (remote: Command not allowed)" just means you somehow locked your booloader again.
Mou must revert back to MM, which uses dload method.
It is quite easy, just follow https://forum.xda-developers.com/hu...torial-rollback-n-to-mm-c432-devices-t3563955