Develop Bugs

[Q][help] bricked badly after failed encrypt - fastboot and ODIN can't write to flash

hi all,
i've managed to get my g-nex (vz lte) pretty badly bricked and am hoping that someone here will be able to help. here's what i did initially on the phone:
1. ran 4.0.2 update from carrier
2. installed adb sdk etc on win 7, verified connectivity and function
3. oem unlock
4. rooted phone
5. installed apps, etc.
6. used phone for a few days, rebooted at will, all working as expected, no issues
7. fully charged phone and in the settings kicked off the encryption process, entered PIN, everything looked good.
8. this morning i woke up to a failed encryption (unfortunately i didn't catch the error message) which needed to be rebooted to move on.
9. after choosing reboot, the screen went very strange - it had grainy horizontal lines that shifted in color somewhat and got dim
10. after waiting for a bit without anything happening, pulled the power and battery
11. the phone rebooted into fastboot, couldn't get into recovery to restore cwm backup, couldn't really do anything
phone shows the following:
fastboot mode - no boot or recovery img
product name - tuna
variant - toro
hw version - 9
bootloader version - primekkk15
baseband version - i515.ek02 cdma - i515.ek05
carrier info - none
serial number - XX_redacted_XX
signing - production
lock state - unlocked
here's what i've tried:
adb commands - doesn't show as there from adb devices
fastboot commands - shows up with fastboot devices, flash commands seem to start but never stop
ODIN mode - connects but writes fail to complete
different usb ports/cables, doesn't seem to make a difference
what i've found to somewhat work - but not really do much - is to oem lock and unlock the phone, once there i can fastboot flash boot boot.img, etc. but if i do a recovery and try and boot into it, it just hangs at the google screen (with the lock unlocked).
i would like maybe reformat the phone completely and reinstall, i've tried the fastboot -w and erase boot / recovery thinking that i could write a clean image to them once they had been cleared, no dice.
if anyone has some suggestions, i'd really appreciate it.
take care,
philo

Have you tried a clean install of the factory image found here? http://code.google.com/android/nexus/images.html#mysidicl53f

i have tried going back to factory, unfortunately that set of images didn't work either. i was able (after an oem lock/unlock) to flash the img files, but it errored on the fastboot reboot-bootloader command with the oddly lined screen. i've attached a picture of the screen for reference.

philo_enyce said:
i have tried going back to factory, unfortunately that set of images didn't work either. i was able (after an oem lock/unlock) to flash the img files, but it errored on the fastboot reboot-bootloader command with the oddly lined screen. i've attached a picture of the screen for reference.
Click to expand...
Click to collapse
I hope you flashed the LTE version and not the GSM
You need this one https://dl.google.com/dl/android/aosp/mysid-icl53f-factory-65895fa8.tgz and you must first flash bootloader then radio and then the update img

i have been using the lte, same as your link. i can get the bootloader on, but a reboot-bootloader gives that weird screen, if i try and flash the radio without rebooting i get:
unknown partition 'radio'

philo_enyce said:
i have been using the lte, same as your link. i can get the bootloader on, but a reboot-bootloader gives that weird screen, if i try and flash the radio without rebooting i get:
unknown partition 'radio'
Click to expand...
Click to collapse
Check here http://forum.xda-developers.com/showthread.php?t=1392336
Its the cwm for cdma edition.Check if you can flash it and in this way have access to cwm recovery

i've tried that as well, same lines even if i use the menu to go to recovery after flashing rather than reboot to bootloader first.

So long as it's back to stock, and you've locked the bootloader, it's off for a replacement you go if it was me

EddyOS said:
So long as it's back to stock, and you've locked the bootloader, it's off for a replacement you go if it was me
Click to expand...
Click to collapse
+1 to this

interestingly, i can't get the fastboot oem lock to take either. it reverts back to unlocked after the reboot fails and i have to pop the battery.
does anyone know how to straight up repartition/reformat the flash? i'm assuming that the failed encryption of the flash has put it into an unusable state and would be happy enough just wiping the damn thing clean...

It looks the encryption screwed up because of the different recovery partition which might of also messed up the partition table.
Best bet is to plead ignorance and get a replacement phone.

problem "solved"
i called samsung and pleaded for the pit + factory image with no luck, so i went over to my local vzw and had them replace the phone for me.
i'm not going to try and encrypt this one, hopefully this was just a fluke and won't affect anyone else...

nice work... let them try to fix that shiz!

Darn, I was hoping for a solution...
I am having a similar issue with a Nexus 5. Phone was working fine, started the encryption process and went to bed and woke up with a bricked phone. I can get into the Bootloader and had figured no problem, I'll just do a factory wipe. Whether trying to boot the phone or get it to do the factory restore it sits there and bootloops with the Google logo. Wish programmers would put in status messages the way we did in the 'old days.'
I was able to get a little further was able to reflash, format the partitions etc. but no luck. I am wondering if perhaps the user data may have an indicator or flag that states it is encrypted even though it isnt at this point encrypted. Figured the factory restore would have been more than enough. WUG makes a nice Root Toolkit that automates a lot of the process but even letting do what I already didnt help.
philo_enyce said:
i called samsung and pleaded for the pit + factory image with no luck, so i went over to my local vzw and had them replace the phone for me.
i'm not going to try and encrypt this one, hopefully this was just a fluke and won't affect anyone else...
Click to expand...
Click to collapse

philo_enyce said:
interestingly, i can't get the fastboot oem lock to take either. it reverts back to unlocked after the reboot fails and i have to pop the battery.
does anyone know how to straight up repartition/reformat the flash? i'm assuming that the failed encryption of the flash has put it into an unusable state and would be happy enough just wiping the damn thing clean...
Click to expand...
Click to collapse
Yep , if you can get into recovery , you can adb shell , then list the partitions with "cat proc/mounts" , from there you'll have a list of your partitions and you can use the ext4 tools to manually repartition . I believe the command is makefs_ext4 <whatever partition you wanna do > I'll try to find the exact command but you can do it .
Also if you simply type "fastboot " when at the bootloader it'll give you the help text and it should tell you how to wipe partitions from fastboot
Hack The Tuna

The same issue here ! memory locked
I ve got the same scenario on a phone i just got , brand new but with the same issue , this one boots up but its impossible to factory reset it , odin , cyanogenmod , fastboot adb flashes .... everything fails somehow .... once you reboot the phone everything comes back ! stock software with the applications and old data .... theres no way to erase it ... it seems the previous owner of the phone encrypted it and then used clockworkmod or something like that ..... the nand on the device is like hardlocked .... doesnt let you do anything !

Unfixable Google Loop - So frustrated

I bought my Nexus 7 2013 shortly after they were available and it was a good device until the release of KitKat. After the KitKat OTA it's been a piece of junk.
After the KitKat OTA it developed a problem where the tablet was on but the touchscreen was unresponsive. The only way to fix it was to shut it down by holding the power button. Eventually it started being stubborn and I'd have to power cycle it several times before it would clear the Google screen. That gradually progressed to having to do a system reset before it would come back to life.
On December 15th it finally refused to go past the Google splash. Attempting to boot into recovery also left you stuck at the Google logo. At the time I tried the WUGFresh tools to do a stock recovery and while I was successful in unlocking no amount of flashing / formatting / erasing would give you a normal boot or a recovery screen.
I sent it off to ASUS on 12/17 and got it back this past Monday (1/13). It worked fine until Tuesday night when once again the screen was unresponsive and I had to shut it down by holding the power button. It's now stuck at the Google screen and no amount of flashing / formatting / erasing using FreshWug or fastboot directly via command line has brought it back.
Here's what I've done so far:
Spammed flash-all at least 6 times
fastboot format of /boot /system /userdata /cache multiple times
Multiple runs of WUGFresh
Flashed 4.4.2 and 4.3 images
What else is there I can do aside from sending it back to ASUS?

Does it boot to bootloader?
Sent from my Nexus 7 using Tapatalk

As Micheal said, can you get to the bootloader? Do all of these commands go successfully?
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
I don't use Wug's tool, preferring to do things from the command line so I know exactly what's being done and to see error messages.

Pandae said:
As Micheal said, can you get to the bootloader? Do all of these commands go successfully?
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
I don't use Wug's tool, preferring to do things from the command line so I know exactly what's being done and to see error messages.
Click to expand...
Click to collapse
This
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app

Pandae said:
As Micheal said, can you get to the bootloader? Do all of these commands go successfully?
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
I don't use Wug's tool, preferring to do things from the command line so I know exactly what's being done and to see error messages.
Click to expand...
Click to collapse
Yes to all of those, I just did them again to verify. FYI WUG opens a command shell as it runs fastboot so you can see what it's up to.
Anywhoo I reflashed kot49h (manually) and got the same result, stuck at Google. If this thing wasn't still under warranty I'd snap it in half and light the two halves on fire.
Any other ideas?

What if you tried a custom recovery and custom ROM?

So I ran through the procedure once more last night and it worked! After about 20 minutes the tablet rebooted on it's own, displayed the working android and then booted up. I guess you just need to reflash 22 times?

buelldozer said:
So I ran through the procedure once more last night and it worked! After about 20 minutes the tablet rebooted on it's own, displayed the working android and then booted up. I guess you just need to reflash 22 times?
Click to expand...
Click to collapse
any updates? is it working fine now? any random reboots? god i hated that on my 1st nex7fhd, im on my 2nd one, its and perfect aside from the 'low speaker volume' stock

Might be an hardware issue, don't get stuck with software too much, send it again until they replace it.

I'd be interested in what ASUS did to it.
Did they include a list of parts replaced, etc?

I'm also curious.
As long as the flashes are done correctly it should boot fine.
However, I had a similar issue flashing stock.
The fix was to flash stock. Boot.
If it boot looped restart and wipe dalivik cache and cache and reboot. It should start then. just an FYI...
Sent from my Galaxy Nexus using xda app-developers app

If u get boot loops = lemon, it will develop those anno ying reboots
Via my NeXus™ 7 FHD on Tapatalk⁴ Pro

So it did it again but following the previous directions I was able to unloop it immediately the big story though is WHY it was looping.
I have a minisuit BT keyboard / case ( http://www.amazon.com/Minisuit-Blue...=UTF8&qid=1390433882&sr=8-3&keywords=minisuit ). The thing is dynamite and I love it and it worked great! The keyboard has a low power battery saver state so after you don't use it for a few minutes it basically goes to sleep until you tap a few buttons and wake it up.
I went a week with no issues but I wasn't using the keyboard. When I did finally use the keyboard I would stop typing and let it go to sleep as I always do. When I tapped a few keys it would wake up and then wake up the N7 and it's screen but the screen would -not- accept touch input. I had to hold the power button down and force the N7 to shut off. When I powered it back up...BAM...LOOPED.
It didn't do this before the Kit Kat upgrade. It's obvious that something is wrong with the BT stack in 4.4.2 and when a HID goes into a low power state it hoses the touch input. Since the touch input is hosed you can't shut it down correctly and the file system corrupts, likely the /system partition.
If I use the N7 without the keyboard it's perfectly fine.
userdelroot I couldn't clear dalvik on mine because I couldn't boot to recovery. All boot options lead to a Google Loop.

I have had exactly the same experience, basically. Just got mine back from ASUS, worked for about a day, and then BAM, back to the same DAMN thing! I think you may be on to something about the BT stack. If there is any common thread to both my breakdowns, its that my Nexus got screwed not long after i paired a BT headset with it. Its late and I'm frustrated as all hell so please forgive my short rant. So what to do? Do I send it back to ASUS and hope they actually replace it this time? (The invoice I got back from them was very strange incidentally. I couldn't tell what they did, except among four parts listed, they seemed to replace a "cracked, broken screen" which was not the way it was when I sent it to them???!) Or should I just keep reflashing and hope it takes, as it seemed to do for you? But then can I risk pairing my BT headset again?! This sux.
Update: Woke up this morning, turned it on, and it booted up! WTF? Not complaining I guess. Taking it easy this time, unlocked bootloader still of course, but holding off rooting, and not going to pair any BT with it for awhile. Although its kinda BS I should have to try it this way...

It's at it again but this time time I wasn't using my keyboard (I quit using it thinking that was the problem).I'm attempting to unloop it again using the same procedure as before. Use of the BT may aggravate the problem (it certainly took longer to glitch out this time) but it's not the whole problem.
I didn't have these problems before the 4.4 update so I'm rolling back to 4.3 for some testing.

buelldozer said:
It's at it again but this time time I wasn't using my keyboard (I quit using it thinking that was the problem).I'm attempting to unloop it again using the same procedure as before. Use of the BT may aggravate the problem (it certainly took longer to glitch out this time) but it's not the whole problem.
I didn't have these problems before the 4.4 update so I'm rolling back to 4.3 for some testing.
Click to expand...
Click to collapse
I have the same problem. Described it right here: http://forum.xda-developers.com/showthread.php?t=2653430
Nothing helps me =( Please, write down any solution, you are able to find.
You wrote, you was able to boot it normally. What did you do for that?

Demian87 said:
I have the same problem. Described it right here: http://forum.xda-developers.com/showthread.php?t=2653430
Nothing helps me =( Please, write down any solution, you are able to find.
You wrote, you was able to boot it normally. What did you do for that?
Click to expand...
Click to collapse
Perform these steps in this order:
fastboot format userdata
fastboot format cache
fastboot format system
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash-all.bat
Then wait at least a full hour before deciding it didn't work. Mine takes a very long time to 'recover' and boot up after that procedure. I'm beginning to suspect that the problem is actually in the /cache partition as it's one of the things that isn't addressed in the flash-all script and it appears to retain information between reboots. The next time this happens I'm going to format and erase just cache and see what happens.
I'm serious on waiting a full hour, and it may take two. I just started it on mine and am timing it now to see what it actually takes.

buelldozer said:
Perform these steps in this order:
fastboot format userdata
fastboot format cache
fastboot format system
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash-all.bat
Then wait at least a full hour before deciding it didn't work. Mine takes a very long time to 'recover' and boot up after that procedure. I'm beginning to suspect that the problem is actually in the /cache partition as it's one of the things that isn't addressed in the flash-all script and it appears to retain information between reboots. The next time this happens I'm going to format and erase just cache and see what happens.
I'm serious on waiting a full hour, and it may take two. I just started it on mine and am timing it now to see what it actually takes.
Click to expand...
Click to collapse
Thank you a lot! I'll try to leave it turned on for the whole night. I left it only for 45 minutes before that. Probably, that was not enough.

My tablet is now at 3.5 hours and still hasn't left the "Google" screen. "All Night" might be the correct time frame. I'll give it another 4 hours and see what that does.

buelldozer said:
My tablet is now at 3.5 hours and still hasn't left the "Google" screen. "All Night" might be the correct time frame. I'll give it another 4 hours and see what that does.
Click to expand...
Click to collapse
My tablet is now at 9:15 hours and still at Google logo. I'm guessing that the time is not the only matter for normal boot up.
---
Now after 11 hours I gave up. =(

Boot-Looped device. I'm willing to try anything at this point.

So before I get linked to a bunch of solutions, here's what I've tried so far as I do have fastboot access:
I've tried flashing the latest factory image from Google. Both manually from fastboot and with NRT, all to no avail. It shows the Google logo then reboots repeatedly. I've tried entering recovery to factory reset there after flashing, but the device won't get into recovery.
I've also tried this method, but I can't get the device to enter download mode. It shows that it's entering it for a moment when I plug it into my computer while holding volume up, but then reboots into the bootloop again.
There's one weird thing that should be noted that makes me think this is some weird software issue, and not a hardware failure. I let the device bootloop all night last night until the battery died. When I powered it on this morning it went all the way to the Android setup page where you select wifi, etc and go from there. However, when I plugged it in and kept going through setup, it rebooted and has been looping since. I've contacted Google and they're supposed to conference call me with LG to see what we can do. Do I have any options other than that? Thanks for any help.

From bootloader
fastboot erase cache
fastboot format cache
fastboot erase user
fastboot format user
BTW what exactly is happening when you say it doesn't enter recovery?

addisontodd said:
So before I get linked to a bunch of solutions, here's what I've tried so far as I do have fastboot access:
I've tried flashing the latest factory image from Google. Both manually from fastboot and with NRT, all to no avail. It shows the Google logo then reboots repeatedly. I've tried entering recovery to factory reset there after flashing, but the device won't get into recovery.
I've also tried this method, but I can't get the device to enter download mode. It shows that it's entering it for a moment when I plug it into my computer while holding volume up, but then reboots into the bootloop again.
There's one weird thing that should be noted that makes me think this is some weird software issue, and not a hardware failure. I let the device bootloop all night last night until the battery died. When I powered it on this morning it went all the way to the Android setup page where you select wifi, etc and go from there. However, when I plugged it in and kept going through setup, it rebooted and has been looping since. I've contacted Google and they're supposed to conference call me with LG to see what we can do. Do I have any options other than that? Thanks for any help.
Click to expand...
Click to collapse
it's seems like me , it's been a month i can't boot it up .

sfhub said:
From bootloader
fastboot erase cache
fastboot format cache
fastboot erase user
fastboot format user
BTW what exactly is happening when you say it doesn't enter recovery?
Click to expand...
Click to collapse
I choose reboot recovery from the fastboot menu and it just boot loops. It won't enter recovery.

addisontodd said:
I choose reboot recovery from the fastboot menu and it just boot loops. It won't enter recovery.
Click to expand...
Click to collapse
what if you try
fastboot boot twrp.img

I've bootlooped so many times I don't know where to start.
So you flashed the factory IMG from your bootloader correct.
Fastboot -w will wipe without wiping system.
Then reflash your whole system. I would redownload from the Google site through Skipsoft...the easiest way. When it asks to keep or flash new recovery you want to flash the stock recovery.
http://forum.xda-developers.com/nex...olkit-skipsoft-android-toolkit-nexus-t3230444
You'll have to reroot afterwards which you can also do through skipsoft.
Profit... Thank me if I helped.

It's a Hardware issue. Installing system again will not fix it. Send it to LG for a repair. My phone had the same issue.

Recovery lost after cache wipe

I updated to Oreo by signing up to the beta program and installed the full upgrade (~1GB) earlier today. It worked flawlessly for several hours and then the phone froze; I was unable to boot it up after that. I booted into recovery, performed a cache wipe, but since that, it still won't boot and now I can't go to recovery either (just get a blank screen after the Google logo). My device is locked, so I can't do a fastboot flashing unlock
Do you have any ideas what to do next? I can still go to fastboot and issue fastboot commands and the phone charges if I connect a charger in a powered-off state, but that's it.

refurbed and still bootlooping

LG refurb updated the ROM to 20x, and (supposedly) replaced MB & RF.
Now I can't get into bootloader, with either ADB or power/vol down combo. Bootloops instead and takes 15 mins to become a working phone again.
I've factory reset 2x today.
Perhaps factory reset and don't restore from Google?
Perhaps 20x is corrupt?
I have no idea what to do next other than deal with the apparent idiots at LG Texas. This is the 2nd "refurb" in a month and 3rd since I've had the G4.
HTC M7 is saving my sanity as backup.

finally got out of bootloop. OEM unlock was the issue in Developer options.
But now having problem getting it to boot into twrp.
fastboot flash recovery twrp.img - went ok, as per past experience.
but - fastboot boot twrp.img - is a no go.
I get this back - cannot load 'twrp.img': No such file or directory.
Can't power down with power button held for 10secs.
Only fastboot reboot works.

What happens if you try to boot into recovery with the key combo (power and vol down until lg logo appears, then release power briefly whilst still holding vol down and then press power again whilst still holding vol down - should bring you to "factory reset page" but once factory reset is confirmed should go to TWRP)

nope, goes to factory reset. tried that twice.

Ok so even after you have flashed twrp, when you enter that factory reset page and click yes twice, it actually factory resets it (that screen is there for everyone but it normally goes to twrp afterwards). Did you boot into your phones OS inbetween flashing twrp and booting to it? LG software replaces twrp with stock recovery if you don't patch the os.
The way to permanently install twrp is:
1) reboot to bootloader and perform "fastboot flash recovery twrp.img"
2) fastboot reboot
3) AS SOON AS IT REBOOTS (<-- that is important) - use key combo and click yes twice - do NOT let it boot back into the main android system inbetween, or you will need to start again

k, I'll give that a go tonite after work. Don't recall the issue with the earlier OS, 20v (before "refurb"), but I'll do oit.

What model of phone is it?
In terms of flashing twrp, that has always been the process (I have a G4 on v20g firmware and it took me a while to work out why twrp kept being wiped)

it's a G40 w/20x. Never had this issue before 20x.
still actually having an issue on reboot. Takes about 7 mins now as it optimizes 1 unknown app.

used this method from fastboot:
fastboot boot twrp.img and pointed (d&d) to twrp on my drive.
then installed twrp from memory as described on twrp page/Fastboot Installation Method.
Ding Ding Ding!
thanks.