Gnex boot loop after battery dies before cache is wiped - Samsung Galaxy Nexus

So last night my phone was acting up and i for some reason thought it would be a brilliant idea to wipe the cache in clockworkmod recovery, well the battery died midway when it was wiping the cache, and now I receive an infinite boot loop. Also when i go into fastboot on the phone i receive this message "e: can't mount /cache/recovery/log" I was reading on another thread and was thinking my partitions were deleted? I'm honestly not sure what's wrong or if i've bricked my phone beyond repair. Any help would be greatly appreciated!

cvrkickercomp said:
So last night my phone was acting up and i for some reason thought it would be a brilliant idea to wipe the cache in clockworkmod recovery, well the battery died midway when it was wiping the cache, and now I receive an infinite boot loop. Also when i go into fastboot on the phone i receive this message "e: can't mount /cache/recovery/log" I was reading on another thread and was thinking my partitions were deleted? I'm honestly not sure what's wrong or if i've bricked my phone beyond repair. Any help would be greatly appreciated!
Click to expand...
Click to collapse
you have flashing stock with pit via odin as an option...

samersh72 said:
you have flashing stock with pit via odin as an option...
Click to expand...
Click to collapse
Where are the stock files located? (not sure if i should specify that my nexus is verizon)
Thank,
Tyler

cvrkickercomp said:
Where are the stock files located? (not sure if i should specify that my nexus is verizon)
Thank,
Tyler
Click to expand...
Click to collapse
Look in verizon forum, you should find odin package
sent from my Galaxy

samersh72 said:
Look in verizon forum, you should find odin package
sent from my Galaxy
Click to expand...
Click to collapse
So I've tried two different things, I've used galaxy nexus toolkit to try and return to stock that way, and i've also tried downloading the odin pda file and phone file and flashing through odin and neither has gotten rid of the boot loop.

What is the error output of the fastboot commands, that's what I would like to know. "I've used a toolkit" means nothing to me.
a manta wrote this.

beekay201 said:
What is the error output of the fastboot commands, that's what I would like to know. "I've used a toolkit" means nothing to me.
a manta wrote this.
Click to expand...
Click to collapse
Pardon my ignorance but i'm not sure how to find/look for the error output.... I'm not educated at all on using the ADK/SDK which i believe might be a problem in me fixing this phone (if it's possible).
I'll elaborate on what i've tried to do to fix the problem. I've downloaded the stock toro 4.2.2 image from
HTML:
https://developers.google.com/android/nexus/images#mysid
I realized that didn't work so i tried to flash back to stock using odin from this tutorial
HTML:
http://www.galaxynexusforum.com/forum/rescue-squad/4707-how-return-stock-using-odin-vzw-lte-only.html
that didn't work so i thought maybe my partitions were messed up so i flashed the pit file from here
HTML:
http://www.usofttech.com/t51448.html
And that still hasn't helped so that is where i am at with trying to trouble shoot the problem.
Sorry i didn't answer your original question but i thought maybe if you knew what i have tried it might give you a better idea of what i'm doing wrong or right
Thanks,
Tyler :good:

cvrkickercomp said:
Pardon my ignorance but i'm not sure how to find/look for the error output.... I'm not educated at all on using the ADK/SDK which i believe might be a problem in me fixing this phone (if it's possible).
I'll elaborate on what i've tried to do to fix the problem. I've downloaded the stock toro 4.2.2 image from
HTML:
https://developers.google.com/android/nexus/images#mysid
I realized that didn't work so i tried to flash back to stock using odin from this tutorial
HTML:
http://www.galaxynexusforum.com/forum/rescue-squad/4707-how-return-stock-using-odin-vzw-lte-only.html
that didn't work so i thought maybe my partitions were messed up so i flashed the pit file from here
HTML:
http://www.usofttech.com/t51448.html
And that still hasn't helped so that is where i am at with trying to trouble shoot the problem.
Sorry i didn't answer your original question but i thought maybe if you knew what i have tried it might give you a better idea of what i'm doing wrong or right
Thanks,
Tyler :good:
Click to expand...
Click to collapse
Why didn't the factory images flash perfectly? What error? It's just that it's extremely difficult to troubleshoot when there's no output errors from commands, and this is why newbies using toolkits is never a good idea.
Please follow the procedure described here, first post. It will allow us to see which part of the flash is failing..and the corresponding error message.

beekay201 said:
Why didn't the factory images flash perfectly? What error? It's just that it's extremely difficult to troubleshoot when there's no output errors from commands, and this is why newbies using toolkits is never a good idea.
Please follow the procedure described here, first post. It will allow us to see which part of the flash is failing..and the corresponding error message.
Click to expand...
Click to collapse
So i followed the tutorial you said to and i still have a bootloop... nothing failed to flash correctly... I'm so lost

I just redownloaded the package and tried again, followed the tutorial exactly and still nothing. Everything flashed perfectly with no error messages whatsoever...

cvrkickercomp said:
I just redownloaded the package and tried again, followed the tutorial exactly and still nothing. Everything flashed perfectly with no error messages whatsoever...
Click to expand...
Click to collapse
paste the commands you used and their correspondent output please
erase and format partitions from fastboot, reflash
let it boot, it can take a few minutes

beekay201 said:
paste the commands you used and their correspondent output please
erase and format partitions from fastboot, reflash
let it boot, it can take a few minutes
Click to expand...
Click to collapse
Will do after work :good: Thanks for the help/guidance

so i'm trying to format all my partitions before i flash anything this time and this is what happened
C:\Users\Tyler\Desktop\adt\sdk\platform-tools>fastboot devices
0149CC3816013004 fastboot
C:\Users\Tyler\Desktop\adt\sdk\platform-tools>fastboot format bootloader
formatting 'bootloader' partition...
FAILED (remote: Invalid Argument)
FAILED (remote: Invalid Argument)
finished. total time: 0.016s
C:\Users\Tyler\Desktop\adt\sdk\platform-tools>fastboot format system
erasing 'system'...
OKAY [ 0.016s]
formatting 'system' partition...
Creating filesystem with parameters:
Size: 685768704
Block size: 4096
Blocks per group: 32768
Inodes per group: 6976
Inode size: 256
Journal blocks: 2616
Label:
Blocks: 167424
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/41856 inodes and 5443/167424 blocks
sending 'system' (12488 KB)...
writing 'system'...
OKAY [ 3.062s]
finished. total time: 3.078s
C:\Users\Tyler\Desktop\adt\sdk\platform-tools>fastboot format bootloader
formatting 'bootloader' partition...
FAILED (remote: Invalid Argument)
FAILED (remote: Invalid Argument)
finished. total time: 0.016s
C:\Users\Tyler\Desktop\adt\sdk\platform-tools>
Am i typing the right command to format the bootloader?

So I believe I have a problem with my internal memory. I just tried "fastboot oem lock" and it works, and the phone switches to "lock state - locked" but then when i select reboot bootloader, the phone says "lock state - unlocked" again. Is there any way to fix that?

Anyone? Please help!!

bump:good:

cvrkickercomp said:
bump:good:
Click to expand...
Click to collapse
There's no point locking your bootloader if it's all messed up. Leave it unlocked.
I don't think i can help you much but try this one
Make sure to follow this steps for a clean install. Hope it helps!
http://forum.xda-developers.com/showpost.php?p=44077732&postcount=5

Related

[Q] Galaxy Nexus Memory problem? can´t format

I have a stock firmware GSM version 4.04, and suddenly from one day to the other it doesn't boot anymore and I'm stuck in Goggle logo.
Trying to do a factory reset (from recovery) it gives:
--Wiping data...
Formatting /data...
Error mounting/data!
Skipping format.....
Formatting /cache...
E:format_volume: make_extf4fs failed on /dev/block/platform/omap/omap_hsmmc.0/by-name/cache
formatting /sd-ext...
formatting /sdcard/.android_secure...
Error mounting mounting /sdcard/.android_secure!
skipping format...
Data wipe complete...
E:Can't mount /cache/recovery/log
E:Can´t open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can´t open /cache/recovery/last_log
E:failed closing /dev/block/platform/omap/omap_hsmmc.0/by-names/misc
(I/O error)
Also trying to mount /system ->
Error mounting /system!
from fastboot if I try to reflash System and userdata ->
C:\galaxy>fastboot flash system system.img
sending 'system' (321251 KB)...
OKAY [ 29.667s]
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 47.294s
C:\galaxy>fastboot flash userdata userdata.img
sending 'userdata' (137554 KB)...
OKAY [ 12.642s]
writing 'userdata'...
FAILED (remote: Write Fail)
finished. total time: 20.180s
Is it a hardware problem?
Same problem
I have the same problem, cant erase, or flash data and cache. Can any help with this?
same boat here. except on a g3
Sounds like you need odin
Is your bootloader unlocked?
Have you flashed the latest bootloader, i.e., LC03, before trying to flash the system image?
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
Is your bootloader unlocked?
Have you flashed the latest bootloader, i.e., LC03, before trying to flash the system image?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
good call!
This fix your problem? Unlock boot loader
I have a Verizon CDMA (toro) of this phone. I am Having the same exact problem. So far i've tried flashing stock from the toolkit, I've tried manually pushing all files through fastboot. and i've also tried recovering through odin, all with proper files for my device(toro files). None have worked so far.
None of the partitions will mount at all or do anything. The bootloader is unlocked. I've even tried relocking the bootlocker, so that i can try to bring it back to the Verizon store, but it will not stick, as soon as i reset the bootloader it shows as being unlocked again. When accessing the recover the phone also shows right away all the mounting errors pertaining to the cache
E:Can't mount /cache/recovery/command
E:Failed closing /dev/block/platform/omap/omap_h
smmc. 0/by-name/misc
(I/O error)
E:Can't mount /cache/recovery/log
E:Can't open/cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open/cache/recovery/last_log
E:Failed closing /dev/block/platform/omap/omap_h
smmc. 0/by-name/misc
(I/O error)
I have something similar. Bootloader unlocked CWM flashed tried wiping in recovery, get "error mounting /data" and the rest of it. Get nowhere. Seems my sdcard is a bit screwed up. Tried Odin. Locks at userdata. Tried fastboot erase userdata. Have lastest bootloader LC03.
Could it be a hardware problem? or something else entirely?
extract userdata.img from stock rom, flash it over with fastboot.
sent from my i9250
bk201doesntexist said:
extract userdata.img from stock rom, flash it over with fastboot.
sent from my i9250
Click to expand...
Click to collapse
The same thing happened to me, but when I use the command "fastboot flash userdata userdata.img" the phone stucks on this moment: writing userdata.img and I can't solve my problem. Please help us.
whee1s said:
The same thing happened to me, but when I use the command "fastboot flash userdata userdata.img" the phone stucks on this moment: writing userdata.img and I can't solve my problem. Please help us.
Click to expand...
Click to collapse
This is exactly what happens to me too. Any solution would be greatly appriated.
Sounds like you all need to start studying up on Odin flashing.
DO NOT just jump in there and do it....read read read and read some more.
I'm certain that you can look up my old posts and find some specific directions and links to everything you'll need.
ODIN is the only thing that will recover your borked phones, every time.
Is ODIN equivalent to an sbf on Motorola?
Sent from my MB870 using xda app-developers app
ODIN would be comparable to RSD lite. It the Samsung software you run on the PC to flash.
Odin will run on a locked up phone.
Odin will restore all partitions and the file table.
It will also restore a borked boot image.
It will recover a bricked phone as long as there is no hardware problem causing the brick.
https://developers.google.com/android/nexus/images
You'll find every stock Gnex image there....all made to run on Odin.
http://forum.xda-developers.com/showthread.php?t=1671969
You can get a good idea of how it works here....be careful, some things are a bit different (as in we have no home key on a Gnex so ignore any calls to use it).
http://forum.xda-developers.com/showthread.php?t=1347899
You can get the mobile (on phone) version of Odin here (I do not know how this works as I have never used it myself).
http://www.google.com/url?sa=t&rct=...noHIBA&usg=AFQjCNF7sF0f2yJp0IxHp1ISlP2fzGKhtw
That should be a direct D/L of Odin 3 1.85 which I use
n2ishun said:
[snip]
https://developers.google.com/android/nexus/images
You'll find every stock Gnex image there....all made to run on Odin.
Click to expand...
Click to collapse
Those images are not in an odin-flashable format.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
Those images are not in an odin-flashable format.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Hehe, just to add, these are fastboot images.
Beamed from Maguro
efrant said:
Those images are not in an odin-flashable format.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Then I guess they didn't work when I used them either ???
If you KNOW how to use Odin you can use numerous different image types and some files need a .pit file and some do not.
There is a reason for everything.
Just because you cannot see the reason does not negate the fact that one exists.
n2ishun said:
Then I guess they didn't work when I used them either ???
If you KNOW how to use Odin you can use numerous different image types and some files need a .pit file and some do not.
There is a reason for everything.
Just because you cannot see the reason does not negate the fact that one exists.
Click to expand...
Click to collapse
Interesting. Please do share how you flashed those images from the link you posted in odin. I always re-packed them into an odin-flashable tar, but if you found a way to do it using the files in that link without repacking, I would really like to know.
Sent from my Galaxy Nexus using Tapatalk 2

[Q] Writing 'system' FAILED, any ideas?

This is my third Nexus to play with and this is the first time I encountered this problem on flashing.
Using fastboot commands seems to flash the other imgs, but specifically on the system.img and radio.img it says
writing 'system.img' . . . FAILED (remote: Write Fail)
I tried searching on different forums even Nexus One's and Nexus S', but still to no avail.
Any ideas? It will be greatly appreciated!
Mico
Corrupt system partitions? Bad cable? These are some possibilities does this process work on other Nexus's ?
Sent from my Galaxy Nexus using xda premium
I don't think a bad cable is the case, this is the original cable and I have used it to flash a yakju build a week earlier.
But on the corrupt partitions, how can I fix it?
Mickosis said:
I don't think a bad cable is the case, this is the original cable and I have used it to flash a yakju build a week earlier.
But on the corrupt partitions, how can I fix it?
Click to expand...
Click to collapse
You don't. And I could never trust Samsung stock cables... very thin and long. That's a lot of room for error. I'm just spitting out possibilities. In hope to narrow itndown
Sent from my Galaxy Nexus using xda premium
So if in case I got a corrupted partition problem, I should bring this to a Samsung repair store?
Damn Samsung corrupted already in a week @[email protected]
Update : I tried adb-ing in CWM a nandroid and restore, it didn't spit out an error, but it seems it goes on a boot loop when I boot it up.
Mickosis said:
So if in case I got a corrupted partition problem, I should bring this to a Samsung repair store?
Damn Samsung corrupted already in a week @[email protected]
Click to expand...
Click to collapse
Are you trying to flash Google's stock images? Have you tried redownloading them just incase the download was corrupt or something?
anton2009 said:
Are you trying to flash Google's stock images? Have you tried redownloading them just incase the download was corrupt or something?
Click to expand...
Click to collapse
Yes, I tried yakju and takju. The system.img always give that error. Everything else can be pushed and written.
Try 'fastboot erase system', then flash system.
Trying this on windows or Linux?
Which adb version are you using?
Sent from my i9250
I got it fixed, weird, I tried fastboot flashing on a different PC and it worked.
Thanks to all who replied, you may close this now
same problem! can´t format nor flash system.img
I have a stock firmware GSM version 4.04, and suddenly from one day to the other it doesn't boot anymore and I'm stuck in Goggle logo.
Trying to do a factory reset (from recovery) it gives:
--Wiping data...
Formatting /data...
Error mounting/data!
Skipping format.....
Formatting /cache...
E:format_volume: make_extf4fs failed on /dev/block/platform/omap/omap_hsmmc.0/by-name/cache
formatting /sd-ext...
formatting /sdcard/.android_secure...
Error mounting mounting /sdcard/.android_secure!
skipping format...
Data wipe complete...
E:Can't mount /cache/recovery/log
E:Can´t open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can´t open /cache/recovery/last_log
E:failed closing /dev/block/platform/omap/omap_hsmmc.0/by-names/misc
(I/O error)
Also trying to mount /system ->
Error mounting /system!
from fastboot if I try to reflash System and userdata ->
C:\galaxy>fastboot flash system system.img
sending 'system' (321251 KB)...
OKAY [ 29.667s]
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 47.294s
C:\galaxy>fastboot flash userdata userdata.img
sending 'userdata' (137554 KB)...
OKAY [ 12.642s]
writing 'userdata'...
FAILED (remote: Write Fail)
finished. total time: 20.180s
Is it a hardware problem?
Like the post above yours, have you tried another PC?
Sent from my i9250
bk201doesntexist said:
Like the post above yours, have you tried another PC?
Sent from my i9250
Click to expand...
Click to collapse
+1. This.
It is probably a driver or cable issue.
Writing 'system failed'
efrant said:
+1. This.
It is probably a driver or cable issue.
Click to expand...
Click to collapse
Yes, already tried in other pc without luck.
Also from recovery menu, using wipe data/reset to factory default fails, as it cannot format the respective partitions.
Any ideas?
nictew said:
Is it a hardware problem?
Click to expand...
Click to collapse
Per the I/O error, I would say yes, there's a hardware problem.
nictew said:
Yes, already tried in other pc without luck.
Also from recovery menu, using wipe data/reset to factory default fails, as it cannot format the respective partitions.
Any ideas?
Click to expand...
Click to collapse
have you tried erasing first, then flash? in fastboot?
Hi,
i have a similar problem, can't format/erase/write on userdata partition.
i tried with odin, several pda (all fails when trying to write userdata)
and
Code:
fastboot erase userdata
fails too (just hangs forever, when other partitions are erase in tenth of second), tried from windows and linux, with different cables...
so, hardware issue ? anything i can try to fix it (soft/hard)? replacing the motherboard would work ?
thanks in advance !
julienvt said:
Hi,
i have a similar problem, can't format/erase/write on userdata partition.
i tried with odin, several pda (all fails when trying to write userdata)
and
Code:
fastboot erase userdata
fails too (just hangs forever, when other partitions are erase in tenth of second), tried from windows and linux, with different cables...
I am having the same issue
Click to expand...
Click to collapse
Hi,
you can see the full discussion about my issue here:
http://forum.xda-developers.com/showthread.php?t=2309568
the phone's been sold for pieces...
let me know if you managed to solve this !

[Q] Frozen at Google Screen

(Repost after posting this in the wrong section)
Hello there. A few days ago I was able to update (finally) my Nexus 7 2013 WiFi version to KitKat. However, during some weird screen freezing issues, the tablet refuses to go past the Google screen. I am able to get into fastboot and recovery, but when I try to wipe the device, I get a lot of "failed to mount cache" messages.
The root toolkit also fails because of this, and even sideloading won't work. When I try to unlock the device, I get the blue text screen, but then it freezes at "erasing cache" or something to that effect. Any ideas on how I can fix this? Thanks!
Maybe your cache partition got corrupted. Have you tried fastboot flash cache cache.img? How about just a normal full factory reset from recovery? It could also be a problem with recovery, in which case you would do the above fastboot but replace cache with recovery.
prsterero said:
Maybe your cache partition got corrupted. Have you tried fastboot flash cache cache.img? How about just a normal full factory reset from recovery? It could also be a problem with recovery, in which case you would do the above fastboot but replace cache with recovery.
Click to expand...
Click to collapse
Thanks a lot for the reply!
I tried the cache.img, and it still said "erasing cache..." for 10 minutes without any sign of advancing. I tried the recovery.img, and it said this:
fastboot flash cache recovery.img
sending 'cache' (7424 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.001s
Which I don't understand since it is hooked up and appears under "fastboot devices"
Thanks again for the assistance!
ZReese23 said:
Thanks a lot for the reply!
I tried the cache.img, and it still said "erasing cache..." for 10 minutes without any sign of advancing. I tried the recovery.img, and it said this:
fastboot flash cache recovery.img
sending 'cache' (7424 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.001s
Which I don't understand since it is hooked up and appears under "fastboot devices"
Thanks again for the assistance!
Click to expand...
Click to collapse
That's because you made a typo. It's fastboot flash recovery recovery.img
prsterero said:
That's because you made a typo. It's fastboot flash recovery recovery.img
Click to expand...
Click to collapse
D'oh, how dumb of me. So I went to try that out, and it stopped me because it says the device was locked, and due to the aforementioned freezing at erasing userdata, I can't get further.
fastboot flash recovery recovery.img
sending 'recovery' (7424 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.006s
ZReese23 said:
D'oh, how dumb of me. So I went to try that out, and it stopped me because it says the device was locked, and due to the aforementioned freezing at erasing userdata, I can't get further.
fastboot flash recovery recovery.img
sending 'recovery' (7424 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.006s
Click to expand...
Click to collapse
What about "fastboot format cache"
prsterero said:
What about "fastboot format cache"
Click to expand...
Click to collapse
Just tried that for about 20 minutes. It's stuck on " erasing 'cache' ".
Thanks again for the help.
Have you tried re-entering bootloader? I think sometimes if you try doing everything in one session it can get stuck. Do fastboot reboot bootloader. Then try formatting cache again.
prshosting.org
prsterero said:
Have you tried re-entering bootloader? I think sometimes if you try doing everything in one session it can get stuck. Do fastboot reboot bootloader. Then try formatting cache again.
prshosting.org
Click to expand...
Click to collapse
Did the reboot and tried again. Waited about 20 minutes, and still stuck at "erasing 'cache ". I assume it doesn't take anywhere near this long. T_T
ZReese23 said:
Did the reboot and tried again. Waited about 20 minutes, and still stuck at "erasing 'cache ". I assume it doesn't take anywhere near this long. T_T
Click to expand...
Click to collapse
I think it should only be a few minutes or so. Are you using the factory cable and have you tried different USB ports? Maybe we can use team viewer and I can take a look if you have some time to kill lol
prshosting.org
prsterero said:
I think it should only be a few minutes or so. Are you using the factory cable and have you tried different USB ports? Maybe we can use team viewer and I can take a look if you have some time to kill lol
prshosting.org
Click to expand...
Click to collapse
I have tried two different cables and moved it around to different USB ports per past suggestions. It just seems to stop when I go to format the cache like it won't mount. Maybe the memory became corrupt.
And sorry, I'd prefer not to do the team viewer, but I am following your directions accordingly!
ZReese23 said:
I have tried two different cables and moved it around to different USB ports per past suggestions. It just seems to stop when I go to format the cache like it won't mount. Maybe the memory became corrupt.
And sorry, I'd prefer not to do the team viewer, but I am following your directions accordingly!
Click to expand...
Click to collapse
Is it just cache it can't format? Is it able to do anything else like data?
prsterero said:
Is it just cache it can't format? Is it able to do anything else like data?
Click to expand...
Click to collapse
I tried to format userdata and cache, and both hang at "erasing" without any indication of moving further.
ZReese23 said:
I tried to format userdata and cache, and both hang at "erasing" without any indication of moving further.
Click to expand...
Click to collapse
Maybe the computer is low on resources and can't complete the operation. Have you tried rebooting?
prshosting.org
lol, I don't think it's that. I have tried it out of a cold reboot do to messing around with the different tools that are available, and each time I tried it things hung there. =[
If everything else fails and you already wiped your data off it, you can try flashing the stock image from Google and use it as a fresh starting point.
Yeah, that's just the thing. There's no way for me to flash it, it seems. I can't unlock the bootloader, and when I go to flash it using Recovery, it just tells me it can't mount the cache. E: so on and so forth.

Really Bricked m9... Please Pro help required.

My M9 suddenly hang und went off... so ok i rebooted. but after boot animation off again.
i can boot into recovery and bootloader and download, but nothing else. ruu fails on pc and on sd. twrp shows system partition as 0Mb. i think something fckd up partition tables or so. i think i need a real pro to get this baby running again or at least to make it look like stock for return. if i try to flash stock recovery in download mode it says finished but still twrp on it. please please help me.
I was running Leedroid rom plus kernel.
device ist supercid and soff
nobody?? :'(
Sashtheflash said:
My M9 suddenly hang und went off... so ok i rebooted. but after boot animation off again.
i can boot into recovery and bootloader and download, but nothing else. ruu fails on pc and on sd. twrp shows system partition as 0Mb. i think something fckd up partition tables or so. i think i need a real pro to get this baby running again or at least to make it look like stock for return. if i try to flash stock recovery in download mode it says finished but still twrp on it. please please help me.
I was running Leedroid rom plus kernel.
device ist supercid and soff
Click to expand...
Click to collapse
Weird. Since you have TWRP, flashing a new ROM sounds like the best option. Maybe a full wipe beforehand? As long as you use a ROM that matches your firmware, it should work.... in theory, at least.
computerslayer said:
Weird. Since you have TWRP, flashing a new ROM sounds like the best option. Maybe a full wipe beforehand? As long as you use a ROM that matches your firmware, it should work.... in theory, at least.
Click to expand...
Click to collapse
since my phone cant find an internal memory i cant flash anything... i think partition tables are ****ed up or so. fastboot flash recovery ends in old state locking bootloader via fastboot results in bootloader still open.
Never had a problem like that and im here since the g1
Yikes. I'm afraid I don't have any further advice. Are there any threads around the M9 forums that talk about corrupted partitions?
Hello, please see my answer on pm regarding help.
Until then, please boot into TWRP and connect to adb and run cat /proc/emmc to get a listing of partitions and their sizes.
Then head over to my firmware thread, find the link to my partition table document and compare with yours. Output should be 100% identical, if not, you're right about your suspicion.
I rather assume you've got a permission / security issue which renders some partitions inaccessible. I doubt they're actually broken.
Please also make sure you always leave precise and concise info on what steps you tried and what the outcome was. This will help keep this short and helpful for others too.
Sneakyghost said:
Hello, please see my answer on pm regarding help.
Until then, please boot into TWRP and connect to adb and run cat /proc/emmc to get a listing of partitions and their sizes.
Then head over to my firmware thread, find the link to my partition table document and compare with yours. Output should be 100% identical, if not, you're right about your suspicion.
I rather assume you've got a permission / security issue which renders some partitions inaccessible. I doubt they're actually broken.
Please also make sure you always leave precise and concise info on what steps you tried and what the outcome was. This will help keep this short and helpful for others too.
Click to expand...
Click to collapse
unfortunately my device wont let me boot in recovery again... now it states: Failed to boot to recovery mode Press Volume up to back to menu.
seems my tries to flash single parts of firmware messed this up
Ok please keep it safe now. Don't do anything else to it for the time being. I can try to connect to it via team viewer tomorrow if you allow me into your machine.
What is your time zone? Will you be having time tomorrow afternoon/evening my time? I'm located in GMT +1 (Germany).
Sneakyghost said:
Ok please keep it safe now. Don't do anything else to it for the time being. I can try to connect to it via team viewer tomorrow if you allow me into your machine.
What is your time zone? Will you be having time tomorrow afternoon/evening my time? I'm located in GMT +1 (Germany).
Click to expand...
Click to collapse
Im from Germany, too ( Heilbronn) Ok i leave my fingers from it until tomorrow. Thank you a lot for trying !!!
im have also m9 dead after flash now my phone read on pc qload any one have idea to rework my phone again ?
logy122 said:
im have also m9 dead after flash now my phone read on pc qload any one have idea to rework my phone again ?
Click to expand...
Click to collapse
Yeah yours is a real brick while the OP's phone is more likely damaged NAND. Two very different things.
QHUSB on your PC when you connect it means you've managed to actually brick it.
For this, you'll need to open the phone and connect it to some special tool like the riff jtag box and rewrite the corrupted bootloader.
@Tecardo can do this for you in Germany. I'm not sure where you are but Tec has all the equipment and skills needed to fix that.
Sneakyghost said:
Yeah yours is a real brick while the OP's phone is more likely damaged NAND. Two very different things.
QHUSB on your PC when you connect it means you've managed to actually brick it.
For this, you'll need to open the phone and connect it to some special tool like the riff jtag box and rewrite the corrupted bootloader.
@Tecardo can do this for you in Germany. I'm not sure where you are but Tec has all the equipment and skills needed to fix that.
Click to expand...
Click to collapse
im also can open phone and replace emmc |> im only need boot file to write to phone and back to work
Yes you need to rewrite aboot. That's only possible with a jtag box and maybe, maybe, under Linux because the qhusb connection has no stable functioning driver on Windows. It's almost impossible to flash anything via qhusb on Windows. It could work in Linux though. I remember having had a half-stable connection to my HTC One S this way, back in 2012. I managed to rewrite the hboot back then. But afaik that never worked on the M7,8,9...
Gesendet von meinem HTC 10 mit Tapatalk
I don't want to start a new thread. I have a similar problem. I have an HTC one M9 S-OFF Unlocked. I returned my phone to stock after doing a nandrod backup. I realised I had a sms backup in the nandroid that I need so I thought I would install twrp and do a restore the nandroid. I installed twrp and afterward it bootlooped when I went to recovery mode. It goes from white HTC screen to black screen an back. I tried to go to download mode to do a fresh install but it bootloops there as well. It also bootloops if I try to turn it off with it connected to power. I have tried installing different version of twrp but I get the same problem. If I install a stock recovery it says failed to boot to recovery mode and stays on the white HTC screen. Does anyone know of a solution
Best way is to flash a RUU.
after, for your nandroid backup, flash twrp (same version you have made the backup) and don't accept supersu at the end if proposed...
bzhmobile said:
Best way is to flash a RUU.
after, for your nandroid backup, flash twrp (same version you have made the backup) and don't accept supersu at the end if proposed...
Click to expand...
Click to collapse
I get the following when I fastboot flash rom "fastboot flash rom /Users/.../Android/OPJAIMG.zip
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1013258477 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 474585325 is not a multiple of the block size 4096
sending sparse 'rom' (521267 KB)...
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
OKAY [ 15.122s]
writing 'rom'...
FAILED (remote: partition table doesn't exist)
finished. total time: 15.140s"
Sneakyghost said:
Yes you need to rewrite aboot. That's only possible with a jtag box and maybe, maybe, under Linux because the qhusb connection has no stable functioning driver on Windows. It's almost impossible to flash anything via qhusb on Windows. It could work in Linux though. I remember having had a half-stable connection to my HTC One S this way, back in 2012. I managed to rewrite the hboot back then. But afaik that never worked on the M7,8,9...
Click to expand...
Click to collapse
It was also possible w/Linux on the One XL. I too have never heard of it working on the M7 and later phones, though I've seen the odd post here claiming it is possible. No examples of anyone having done it, however.
copy the OPJAIMG.zip on the root of your Sdcard and reboot in the booloader and follow the instructions (vol +)...
or
with htc_fastboot
download Htc_fastboot.exe et copy it in your fastboot folder with the OPJAIMG.zip
fastboot oem lock , not needed if you're S-OFF
fastboot oem rebootRUU , to reboot
htc_fastboot flash zip OPJAIMG.zip
fastboot reboot
don't forget to unlock again youre device
djkfree said:
I get the following when I fastboot flash rom "fastboot flash rom /Users/.../Android/OPJAIMG.zip
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1013258477 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 474585325 is not a multiple of the block size 4096
sending sparse 'rom' (521267 KB)...
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
OKAY [ 15.122s]
writing 'rom'...
FAILED (remote: partition table doesn't exist)
finished. total time: 15.140s"
Click to expand...
Click to collapse
bzhmobile said:
copy the OPJAIMG.zip on the root of your Sdcard and reboot in the booloader and follow the instructions (vol +)...
or
with htc_fastboot
download Htc_fastboot.exe et copy it in your fastboot folder with the OPJAIMG.zip
fastboot oem lock , not needed if you're S-OFF
fastboot oem rebootRUU , to reboot
htc_fastboot flash zip OPJAIMG.zip
fastboot reboot
don't forget to unlock again youre device
Click to expand...
Click to collapse
I get bootloop when I fastboot oem rebootRUU
So,
go to download mod (option in the bootloader ) and apply the fastboot command
htc_fastboot flash zip OPJAIMG.zip

Pixel keeps bootlooping to TWRP

Hi Guys,
Pixel keeps bootlooping to TWRP. I unlocked bootloader, rooted with the boot-to-root, been using the phone for a few hours, then decided to install TWRP. I booted the img, then in TWRP flashed the zip file. (RC1) Did a wipe/factory reset and it just bootloops into TWRP.
Trying to figure out how to get back to stock. I only have a mac and can't seem to find any good instructions on how to do it. I downloaded the the stock image but I don't know how to flash the whole image through fastboot. Any help how to get out of this bootloop would be appreciated.
http://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478
I was reading through that thread, but I only have access to a mac, and I can't figure out to flash the whole image...
CZ Eddie said:
http://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478
Click to expand...
Click to collapse
flo7002 said:
I was reading through that thread, but I only have access to a mac, and I can't figure out to flash the whole image...
Click to expand...
Click to collapse
If you have a MAC then you'll probably want to learn how to create a Windows virtual machine.
Everyone with a MAC should know this.
Just like everyone with a Windows machine should know how to create a Linux virtual machine.
Sorry I can't help beyond giving annoying advice.
CZ Eddie said:
If you have a MAC then you'll probably want to learn how to create a Windows virtual machine.
Everyone with a MAC should know this.
Just like everyone with a Windows machine should know how to create a Linux virtual machine.
Sorry I can't help beyond giving annoying advice.
Click to expand...
Click to collapse
No worries... I guess I should try to install windows on my mac as well...
I tried this command: fastboot -w update image-marlin-nmf26q.zip (and I get this error)
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
fastboot(3918,0xa53391c0) malloc: *** mach_vm_map(size=1603837952) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 1602232032 bytes
error: update package missing system.img
flo7002 said:
No worries... I guess I should try to install windows on my mac as well...
I tried this command: fastboot -w update image-marlin-nmf26q.zip (and I get this error)
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
fastboot(3918,0xa53391c0) malloc: *** mach_vm_map(size=1603837952) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 1602232032 bytes
error: update package missing system.img
Click to expand...
Click to collapse
Most of that was normal, if you look at step #13 in my thread. I pasted the complete output of what the normal flash looks like for comparison.
The rest doesn't look familiar to me?
CZ Eddie said:
Most of that was normal, if you look at step #13 in my thread. I pasted the complete output of what the normal flash looks like for comparison.
The rest doesn't look familiar to me?
Click to expand...
Click to collapse
I got a little further. I noticed I had an older version of adb/fastboot.
Now it get all the way till the end and then this:
sending 'userdata' (145102 KB)...
OKAY [ 3.197s]
writing 'userdata'...
OKAY [ 2.444s]
erasing 'cache'...
(bootloader) Erasing active slot "_b"
FAILED (remote: Partition table doesn't exist
)
finished. total time: 117.266s
Any clue what's going on there? Should I flash boot.img on both A & B partitions? I haven't messed around with the partitions at all...
flo7002 said:
erasing 'cache'...
(bootloader) Erasing active slot "_b"
Any clue what's going on there? Should I flash boot.img on both A & B partitions? I haven't messed around with the partitions at all...
Click to expand...
Click to collapse
Not sure about those entries.
I do recommend flashing boot.img to both A & B as a cautionary/preventive measure.
flo7002 said:
I got a little further. I noticed I had an older version of adb/fastboot.
Now it get all the way till the end and then this:
sending 'userdata' (145102 KB)...
OKAY [ 3.197s]
writing 'userdata'...
OKAY [ 2.444s]
erasing 'cache'...
(bootloader) Erasing active slot "_b"
FAILED (remote: Partition table doesn't exist
)
finished. total time: 117.266s
Any clue what's going on there? Should I flash boot.img on both A & B partitions? I haven't messed around with the partitions at all...
Click to expand...
Click to collapse
This whole string of outputs is completely normal. Disregard the "erasing active slot" and "failed remote partition table" message.
You should now be able to boot the phone up and it will be completely restored to factory spec, if not, go-to your stock recovery, and delete cache and user data, and try again.
I wouldn't worry about flashing boot.img to the other partition unless your phone still refuses to boot to Android.

Categories

Resources