Related
Stuck at "Data.img" thru odin. Possible EMMC brick fix! Thanks to Jaymoon pg.#44
So here's the deal. I just couldn't help myself and I flashed shabbys ICS test build this morning. Well the more I started reading in the thread about guys having issues restoring there backups I tried it. Flashed the cwm touch recovery....did a full wipe and then went to restore my nand of Blend. Booted up and gets stuck at the Samsung boot screen. I let it sit there for about 10 minutes. Then from there I pressed volume up and power to see if i could get back into cwm. I was able to and had rogue recovery. I then went to do a full wipe again. The data wipe took about 2 minutes....which was strange...then wiped cache and dalvik. Then went to flash Blend(not the nand backup) and again stuck at the samsung boot screen.
So I then went into odin mode and attempted to odin back to stock using the D710USEL29_20120105.stock from qb777's you tube vid. All went good....got the pass and once again stuck at the Samsung boot screen. Then from there I went back into odin download mode and attempted to odin the stock rooted file(not the file to keep your data file) and it got stuck at "Data.img" in odin.
So now I sit with the battery out of my phone and have no idea what I can try from here. I think I remember reading that as long as you can get into odin download mode there should be a fix. As alot of you can probably tell from reading this I am new to odin. I should have never flashed this test build if I was not a hundred percent sure that I could get back and also should have been WAY more familiar with odin before flashing.
I'm off to hit the sack....have a fat headache from this screw up of mine. I'll be up at 6am to check in here. If anyone can help I would really appreciate it......and whatever suggestions you may offer please take into account that I just learned about odin last week, so maybe a "odin for dummies" could help me out the most.
A little freaked out about this and really hope someone knows a way they can help.
THANKS in advance
[EDIT] Looks like we may have a fix. Refer to Page numbers 44,45. Thanks to Jaymoon and everyone else involved.
nevermind 10 char
try this homie...
odin this recovery.... http://goo-inside.me/kernels/TeamRo.../rogue_ET-recoveryonly-1.1.4-rc0-odin.tar.md5
it finally allowed me to wide data which i couldnt do all this time...
im just gonna stick with this for now and try a few things
caspersfi said:
So I then went into odin mode and attempted to odin back to stock using the D710USEL29_20120105.stock from qb777's you tube vid. All went good....got the pass and once again stuck at the Samsung boot screen. Then from there I went back into odin download mode and attempted to odin the stock rooted file(not the file to keep your data file) and it got stuck at "Data.img" in odin.
Click to expand...
Click to collapse
It is possible somehow your partitions got messed up.
If you look at section A2 of the EL29 ODIN One-Click, you will find the regular ODIN tar.md5
You can use that with regular ODIN. The file you download is a self-extractor so you need to double-click and select where to unpack. That will give you a tar.md5 file. Use the *PDA* slot in ODIN to select that file. Double-check you used the *PDA* slot. Then the only option you should select in ODIN (that isn't already selected for you) is Re-Partition (so you should have Re-Partition and Auto-Reboot checked)
so sfhub,
after doing the wipe in the stock recovery.... i did a reboot system
THe "samsung Galaxy sII" screen just flashes on and off every couple of minutes.
dadoc04 said:
so sfhub,
after doing the wipe in the stock recovery.... i did a reboot system
THe "samsung Galaxy sII" screen just flashes on and off every couple of minutes.
Click to expand...
Click to collapse
So this is different that what it was doing before? Perhaps you are making progress.
Try ODIN flashing just the rooted ROM (section #B4)
Sorry it is taking so long. I'm kind of using you to debug the actual issue.
sfhub said:
So this is different that what it was doing before? Perhaps you are making progress.
Try ODIN flashing just the rooted ROM (section #B4)
Sorry it is taking so long. I'm kind of using you to debug the actual issue.
Click to expand...
Click to collapse
no problem... your help is appreciated... gimme a minute download #B4 and ODIN... ill post results
---------- Post added at 02:40 AM ---------- Previous post was at 02:38 AM ----------
I dont see a B4... maybe im looking in the wrong thread... u mind linking me?
---------- Post added at 02:42 AM ---------- Previous post was at 02:40 AM ----------
NEVERMIND>.. i was using the wrong link.. i found it
---------- Post added at 02:46 AM ---------- Previous post was at 02:42 AM ----------
do you want me to select anything in odin? or just the auto reboot?
It is a self-extractor so remember to double-click on it to extract the tar.md5 before using in ODIN.
Just auto-reboot is fine.
You've already flashed the kernel and reformated /data. The only thing needed to boot that might not be correct is the ROM, so hopefully this works.
alright... ill let you know in a few minutes what happens
It will probably take a little bit of time. The ROM is the largest image.
^ yea...
its going now... currently in FACTORYFS...
---------- Post added at 02:59 AM ---------- Previous post was at 02:55 AM ----------
it says PAss..... not sure where it did data though....
factoryfs
NAND Write Start
RQT CLose
RES OK
REmoved
Completed
All threads completed (succeed 1/ failed 0)
It didn't do /data (data.img). You already formatted that using stock recovery, so it shouldn't be necessary to flash it.
Factoryfs.img is the ROM.
You previously already flash the kernel and verified it was working because you were able to boot into stock recovery.
So that takes care of kernel, ROM, and /data. I doubt anything is wrong with the modem. So everything that is needed to boot should be in place.
its just flashing the "samsung galaxy s II" screen again
it goes to a grey battery image screen
That is usually what it does when you power down your phone. What happens when you press and hold power until something happens?
press and hold power = gray battery screen....
edit... the battery went away and "samsung galaxy s2" is back
If it is looping again, try booting into recovery and wipe data/factory reset one more time.
I wonder if you can run adb logcat as the phone goes from off state to stuck on samsung logo. You might be able to see whats going on if adb picks it up.
^ That's a good idea ^ Might provide some clues.
sfhub said:
If it is looping again, try booting into recovery and wipe data/factory reset one more time.
Click to expand...
Click to collapse
wiping data/factory reset now... ill let ya know how it goes. It took a while last time as i think it was hung up
---------- Post added at 03:17 AM ---------- Previous post was at 03:14 AM ----------
im comfortable with ADB...
tell me how/when to do it and ill give it a shot....
---------- Post added at 03:18 AM ---------- Previous post was at 03:17 AM ----------
wipe is complete...
still shows the E:file is written: not updated
in command prompt, type
adb logcat
it will more than likely say "waiting for device" . thats fine, just plug in your phone to the pc and boot up the phone as usual. if the phone is booting far enough, adb should pick up the device and start displaying the logcat.
I just finished rooting successfully, internet pass through works fine but i can't turon wifi on, it just syas error under wifi in settings? help!?
Edit: Explained by below post.
Twner said:
I just finished rooting successfully, internet pass through works fine but i can't turon wifi on, it just syas error under wifi in settings? help!?
Click to expand...
Click to collapse
How do you root ?
There are difference between fastboot flash boot boot.img and fastboot boot boot.img
Thanks guys, i just had to clear my cache and reset everything and got it working again.
ckpv5 said:
How do you root ?
There are difference between fastboot flash boot boot.img and fastboot boot boot.img
Click to expand...
Click to collapse
Since he got that working anyway,how about telling me what's the difference??
Sent from my One V using xda app-developers app
Twner said:
Thanks guys, i just had to clear my cache and reset everything and got it working again.
Click to expand...
Click to collapse
Right, a fastboot erase cache after flashing a boot.img is always a wise move. Glad you solved your problem.
---------- Post added at 09:21 PM ---------- Previous post was at 09:16 PM ----------
soham_sss said:
Since he got that working anyway,how about telling me what's the difference??
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
fastboot flash boot boot.img - boot.img will be permanently in your device until you flash another one.
fastboot boot boot.img - boot.img is temporarily installed, once reboot, the old boot.img is effective. The same can be applied to a recovery.img. You can test a recovery whether it works correctly without installing it permanently. Let say yours is CWM recovery and you want to try TWRP, just fastboot boot TWRP.img, device will boot to recovery with TWRP, once reboot, your old CWM still there, no need reflashing.
ckpv5 said:
Right, a fastboot erase cache after flashing a boot.img is always a wise move. Glad you solved your problem.
---------- Post added at 09:21 PM ---------- Previous post was at 09:16 PM ----------
fastboot flash boot boot.img - boot.img will be permanently in your device until you flash another one.
fastboot boot boot.img - boot.img is temporarily installed, once reboot, the old boot.img is effective. The same can be applied to a recovery.img. You can test a recovery whether it works correctly without installing it permanently. Let say yours is CWM recovery and you want to try TWRP, just fastboot boot TWRP.img, device will boot to recovery with TWRP, once reboot, your old CWM still there, no need reflashing.
Click to expand...
Click to collapse
Cool, thanks!!
Sent from my One V using xda app-developers app
When in fastboot i can clear the cache and it is sucessfull, in twrp i cant mount it, my phone is in a constant boot loop that shows the notice in red indicating the constant bootloop is trying to load twrp.
after this i have to reflash twrp then clear the cache and reboot before i can get into twrp again.
i have viper 2.6.0 downloaded and cannot install it
i have a twrp backup of my origonal rom that wont work due to the previous.
i have tried flashing clockworkmod and it failed.
i had an error mounting the sd card but i managed to fix it
when i try to restore the boot in twrp it has errors mounting the cache
What should i do?
Why would you want to mount the cache? just format the cache and flash the correct boot.img in fastboot-USB mode and your phone will have no problems.
When i tried that nothing happend, and i dont know why when trying to flash the boot.img in twrp it wants to access the cache but it fails.
I think part of my problem with the fastboot boot.img copy was that i do not have the boot.img from my origonal O.S. in a .img format so i had to download somebody elses nand to try that. when i backed up my O.S. with twrp it saved my boot info as boot.emmc.win
t3ckfr3ak1 said:
When i tried that nothing happend, and i dont know why when trying to flash the boot.img in twrp it wants to access the cache but it fails.
I think part of my problem with the fastboot boot.img copy was that i do not have the boot.img from my origonal O.S. in a .img format so i had to download somebody elses nand to try that. when i backed up my O.S. with twrp it saved my boot info as boot.emmc.win
Click to expand...
Click to collapse
Yes and you can flash that like all other boot.img files
Fastboot flash boot boot.emmc.win
You cant flash a boot.img in recovery ! I.dont really get the picture what you are trying to do ? Cache is just temp....you can wipe it and it builds up again. You can't flash cache or anything like that ....
I ran ruu and rooted but when I try to install a rom Twrp fails on me and says it can't mount the cache
Sent from my HTC One X using xda app-developers app
t3ckfr3ak1 said:
I ran ruu and rooted but when I try to install a rom Twrp fails on me and says it can't mount the cache
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Bringing this back. I'm having the same problem and wanted to see if you found a fix for it...?
---------- Post added at 09:48 PM ---------- Previous post was at 08:55 PM ----------
t3ckfr3ak1 said:
I ran ruu and rooted but when I try to install a rom Twrp fails on me and says it can't mount the cache
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
integramodder said:
Bringing this back. I'm having the same problem and wanted to see if you found a fix for it...?
Click to expand...
Click to collapse
Never mind. I ended up changing recoveries from TWRP 2.5.0.0 to CWM 6.0.2.8 and it was able to mount and wipe the cache.
FIX ANDROID BOOT LOOP ISSUES ON STOCK ANDROID
Step 1. Remove the battery from the device and wait for 30 seconds and then put the battery again on your device. If your phone doesn’t has the remove bale battery like Nexus 4, then power down the phone and keep it powered off for 5 minutes. This will turn off your device permanently.
Step 2. After that Boot your device in to Recovey Mode. Samsung Users use Volume Up+ Home + Power keys. If you have the other Android device then do a Google search how to enter in recovery mode.
Step 3. Once your android device is in Recovery Mode, Go to the “wipe cache partition” option and select it.
Step 4. After that go back to the recovery main menu and reboot the device by “reboot system now” option.
Step 5. If the device again stuck on Android Boot Loop pull out the battery again and repeat the above steps. This time also “wipe data/factory reset” and then reboot device.
Now your device will come out of the Android Boot Loop and at the first time the device will take some time to reboot.
FIX ANDROID BOOT LOOP ISSUES ON ROOTED WITH CWM RECOVERY ANDROID
Step 1. Follow the Above guide (Fix Android Boot loop issues on Stock Android) Step 1 and Step 2 on your device.
Step 2. Once your Rooted device on recovery mode, go to the Go to “Advanced” and Choose “Wipe dalvik-cache”. After that go to “Mounts & Storage” and choose “Wipe /cache”. In the end go to the main menu of recovery and Reboot your phone.
Now the Android Boot Loop should be gone now. If it still persists, do the following on your device. Go to “Mounts & Storage” and Choose “Wipe /data” after that Choose “Wipe /cache” and now reboot your phone.
Now the phone should reboot normally. And the Android loop problem is solved on your device.
Please comment if any queries.
Black Brain
:good:
My Micromax android one marshmallow, april security updated, has given way to bootloop, with marshmallow boot screen continuing. Factory reset and cache wiping through stock recovery didn't helped as well.
[email protected] said:
My Micromax android one marshmallow, april security updated, has given way to bootloop, with marshmallow boot screen continuing. Factory reset and cache wiping through stock recovery didn't helped as well.
Click to expand...
Click to collapse
Saksham try to factory data reset your mobile this may help if not then PM me. I will see to this issue.
Black Brain said:
Saksham try to factory data reset your mobile this may help if not then PM me. I will see to this issue.
Click to expand...
Click to collapse
Sir i have tried that and even tried wiping cache partition, but it is still stuck on the boot animation.
Please tellme what to do next.
[email protected] said:
Sir i have tried that and even tried wiping cache partition, but it is still stuck on the boot animation.
Please tellme what to do next.
Click to expand...
Click to collapse
Have you considered rooting your phone?
See you have to do it step by step
First format dalvik-cache
Then wipe cache partition
Then factory data reset and then boot it normally
If it takes more than 15 min then tell me
And see to it if your mobiles try to read the app I mean optimize them.
Black Brain said:
Have you considered rooting your phone?
See you have to do it step by step
First format dalvik-cache
Then wipe cache partition
Then factory data reset and then boot it normally
If it takes more than 15 min then tell me
And see to it if your mobiles try to read the app I mean optimize them.
Click to expand...
Click to collapse
How will I wipe the dalvik cache, when my android is on stock recovery and not with usb debugging, other recoveries?
Hey do me a favor and post screen shots showing all the options in Stock Android.
Sent from my SM-T815Y using XDA-Developers mobile app
same issue (stuck on animation screen)
Tried all the steps mentioned here - wipe data/cache , factory data reset, reboot. Stuck on animation screen for more than 15 mins.
Black Brain said:
Hey do me a favor and post screen shots showing all the options in Stock Android.
Sent from my SM-T815Y using XDA-Developers mobile app
Click to expand...
Click to collapse
Done
It's seems [email protected] you have unmounted the system
Mount system
Wipe cache portion
Date factory reset
And reboot
Black Brain said:
It's seems [email protected] you have unmounted the system
Mount system
Wipe cache portion
Date factory reset
And reboot
Click to expand...
Click to collapse
Even after that it remains the same...... as the pic I uploaded.
---------- Post added at 04:34 PM ---------- Previous post was at 04:06 PM ----------
Black Brain said:
It's seems [email protected] you have unmounted the system
Mount system
Wipe cache portion
Date factory reset
And reboot
Click to expand...
Click to collapse
Still stuck
[email protected] said:
Even after that it remains the same...... as the pic I uploaded.
---------- Post added at 04:34 PM ---------- Previous post was at 04:06 PM ----------
Still stuck
Click to expand...
Click to collapse
Ok then you gotta reset your whole device
Fully delete the system
Or consider rooting it
Black Brain said:
Ok then you gotta reset your whole device
Fully delete the system
Or consider rooting it
Click to expand...
Click to collapse
ok show me the whole way of deleting the system or rooting it now!!!
i had the same problem. I downloaded and ran android one tool kit (google it) Then brought phone on fastboot by press power and volume up button and selecting fastboot mode and connected to pc. clicked on root on android one tool kit. it took me to custom recovery on phone. then tap format option-tap clean for installing new rom-copy rom file on sd card and select install from sd and let the procedure run. after it let the phone boot for 15 minutes. may it help you. it solved my problem
https://www.youtube.com/watch?v=SHIYKDfseaY
See this video and Please see my new thread.
boot loop without recovery
what's about if you have boot loop and recovery is not available? any idea how to fix it?
tuscan72 said:
what's about if you have boot loop and recovery is not available? any idea how to fix it?
Click to expand...
Click to collapse
No it isn't possible. Every phone has a recovery either a stock once or a custom. Without recovery the photo isn't possible to be operated even.
tuscan72 said:
what's about if you have boot loop and recovery is not available? any idea how to fix it?
Click to expand...
Click to collapse
True, it can't be fixed.
sachinxda09 said:
i had the same problem. I downloaded and ran android one tool kit (google it) Then brought phone on fastboot by press power and volume up button and selecting fastboot mode and connected to pc. clicked on root on android one tool kit. it took me to custom recovery on phone. then tap format option-tap clean for installing new rom-copy rom file on sd card and select install from sd and let the procedure run. after it let the phone boot for 15 minutes. may it help you. it solved my problem
Click to expand...
Click to collapse
Hey sachinxda09 Can u give the link for the rom copy, which u installed. thanks
aman04 said:
Hey sachinxda09 Can u give the link for the rom copy, which u installed. thanks
Click to expand...
Click to collapse
it was the same problem for me.... at last it sent it to customer service, who returned the phone in 1 hour after repariring it. Try it.
Secure boot enabled.
Device state - unlocked.
I tried to follow the Heisenberg tutorial to flash a custom Rom.
Finished the root. Decided I installed the wrong version of GApps. Went back to stock to redo the process.
Accidentally installed a 6p stock image instead of 5x. Then my troubles began.
I've tried a lot of different things. I don't have a full log of steps taken.
Have tried reflashing different 5x stock images. They flash fine but problem persists.
Problems:
1. Booting to Android bootloops
2. TWRP recovery GUI is non-responsive.
Fastboot works great.
Reflashing TWRP from fastboot doesn't help.
ADB access to recovery seems responsive, but I'm not sure whether commands are actually executing. For example running twrp factoryreset just hangs. All twrp commands do that.
I would like to perform a factory reset. I have TWRP backups that I could restore. I don't know how to do that from fastboot.
First download the full Nexus 5x stock rom from here: https://developers.google.com/android/nexus/images then boot your Nexus 5x into its bootloader then on your computer (I am assuming it's Windows) download 7zip from here: http://www.7-zip.org then right click the .tgz stock rom file you just downloaded on your computer then extract it with 7zip. Inside that you will find a .tar file. Extract that then you will find a zip file before extracting the zip file run the .bat file while your Nexus 5x is connected to your computer then hold down your shift key, right click and click open command window here (while you are in the folder where you extracted the zip) in the command window, terminal, CMD, whatever you like to call it then type fastboot -w (that does a factory reset) then type fastboot flash system system.img then fastboot flash recovery recovery.img than fastboot flash boot boot.img than fastboot flash cache cache.img then fastboot flash userdata userdata.img then fastboot flash vendor vendor.img then fastboot flash recovery recovery.img. You should be able to boot back into Android now but you will need to reflash twrp. Also download the any file for 6.0.1 not 7.0 because you will have to do some extra steps for that.
P.S. this MIGHT erase your twrp backups.
Thank You,
Sincerely VibraniumDroid
---------- Post added at 08:06 AM ---------- Previous post was at 08:05 AM ----------
leolittlebook said:
Secure boot enabled.
Device state - unlocked.
I tried to follow the Heisenberg tutorial to flash a custom Rom.
Finished the root. Decided I installed the wrong version of GApps. Went back to stock to redo the process.
Accidentally installed a 6p stock image instead of 5x. Then my troubles began.
I've tried a lot of different things. I don't have a full log of steps taken.
Have tried reflashing different 5x stock images. They flash fine but problem persists.
Problems:
1. Booting to Android bootloops
2. TWRP recovery GUI is non-responsive.
Fastboot works great.
Reflashing TWRP from fastboot doesn't help.
ADB access to recovery seems responsive, but I'm not sure whether commands are actually executing. For example running twrp factoryreset just hangs. All twrp commands do that.
I would like to perform a factory reset. I have TWRP backups that I could restore. I don't know how to do that from fastboot.
Click to expand...
Click to collapse
Tell me if this works
---------- Post added at 08:08 AM ---------- Previous post was at 08:06 AM ----------
Also after your done type fastboot -w again
vibraniumdroid said:
Tell me if this works
Click to expand...
Click to collapse
android stock version: MTC20F
flash-all.bat OKAY
fastboot -w OKAY
fastboot flash system system.img OKAY
fastboot flash recovery recovery.img OKAY
fastboot flash boot boot.img OKAY
fastboot flash cache cache.img OKAY
fastboot flash userdata userdata.img OKAY
fastboot flash vendor vendor.img OKAY
fastboot flash recovery recovery.img OKAY
fastboot reboot
RESULT: bootloop continues. fails to boot to android.
fastboot flash recovery twrp-3.0.2-1-bullhead.img OKAY
reboot to recovery mode
RESULT: GUI still unresponsive. No change.
Can only lock screen with power button.
vibraniumdroid said:
download the any file for 6.0.1 not 7.0 because you will have to do some extra steps for that.
Click to expand...
Click to collapse
I don't understand this line.
EDIT:
fastboot -w again
OKAY
No improvement.
Sorry typo
---------- Post added at 09:57 AM ---------- Previous post was at 09:57 AM ----------
Try reflashing the radio
---------- Post added at 09:58 AM ---------- Previous post was at 09:57 AM ----------
vibraniumdroid said:
Sorry typo
---------- Post added at 09:57 AM ---------- Previous post was at 09:57 AM ----------
Try reflashing the radio
Click to expand...
Click to collapse
Try cyanogen recovery
vibraniumdroid said:
try...
Click to expand...
Click to collapse
Flashed radio, no change.
Cyanogen recovery interface functional.
Ran full factory reset. Wiped cache.
Able to navigate with physical buttons. Screen buttons still not working. Cannot use back button. Cannot exit menu.
Cannot reboot from adb due to loss of authorization when switching recoveries.
Rebooted with long power button press.
Wiped system.
Rebooted normally. Stuck on Google screen. I assume because I deleted the /system OS.
Reflashed stock using flash-all.bat. Still bootloops.
Reflashed CM recovery.
A CHANGE! Screen buttons now work.
Flashed TWRP recovery. Buttons work.
Copied TWRP backups to phone. They are for prior Android version, however.
Testing whether current version will boot. Nope; bootloops.
Restored backup. Attempted boot. Stuck on Google screen.
leolittlebook said:
Flashed radio, no change.
Cyanogen recovery interface functional.
Ran full factory reset. Wiped cache.
Able to navigate with physical buttons. Screen buttons still not working. Cannot use back button. Cannot exit menu.
Cannot reboot from adb due to loss of authorization when switching recoveries.
Rebooted with long power button press.
Wiped system.
Rebooted normally. Stuck on Google screen. I assume because I deleted the /system OS.
Reflashed stock using flash-all.bat. Still bootloops.
Click to expand...
Click to collapse
try to reflash really all manually (bootloader and so on) also try to format your userdata and then reflash it (will wipe internal storage)
Thargorsson said:
try to reflash really all manually (bootloader and so on) also try to format your userdata and then reflash it (will wipe internal storage)
Click to expand...
Click to collapse
New after you posted:
Reflashed CM recovery.
A CHANGE! Screen buttons now work.
Flashed TWRP recovery. Buttons work.
Copied TWRP backups to phone. They are for prior Android version, however.
Testing whether current version will boot. Nope; bootloops.
Restored backup. Attempted boot. Stuck on Google screen.
I will try what you suggest.
how do I make these lines:
---------- Post added at 09:58 AM ---------- Previous post was at 09:57 AM ----------
instead of adding a second post?
Thargorsson said:
try to reflash really all manually (bootloader and so on) also try to format your userdata and then reflash it (will wipe internal storage)
Click to expand...
Click to collapse
wiped all from twrp. said no OS.
rebooted to fastboot. ran flash-all.bat for bullhead-mtc20f
Rebooted into android bootloop.
flashed all manually.
failed midway through on system transfer. switched to different usb cable. worked.
result: bootloop.
redoing with new wire.
flash-all.bat result - bootloop.
manually flashed all. result: bootloop.
leolittlebook said:
how do I make these lines:
---------- Post added at 09:58 AM ---------- Previous post was at 09:57 AM ----------
instead of adding a second post?
wiped all from twrp. said no OS.
rebooted to fastboot. ran flash-all.bat for bullhead-mtc20f
Rebooted into android bootloop.
flashed all manually.
failed midway through on system transfer. switched to different usb cable. worked.
result: bootloop.
redoing with new wire.
flash-all.bat result - bootloop.
manually flashed all. result: bootloop.
Click to expand...
Click to collapse
did you really ran "fastboot earease userdata"? and then "fastboot flash userdata userdata.img"
Thargorsson said:
did you really ran "fastboot earease userdata"? and then "fastboot flash userdata userdata.img"
Click to expand...
Click to collapse
I'm not sure whether I specifically ran the erase command manually on this iteration. I ran those exact two commands just now. It's bootlooping still.
leolittlebook said:
I'm not sure whether I specifically ran the erase command manually on this iteration. I ran those exact two commands just now. It's bootlooping still.
Click to expand...
Click to collapse
Hanging on what? google logo or bootanimation.
Youve tried LG download mode? (power + volume up, then plug usb into phone).
See https://www.youtube.com/watch?v=_47Y-yOTF8k
By the way try a full restore and after lock the bootloader.
It doesn't hang. It shows the normal sequence of GOogle screen and colored dots, then reboots.
I've accessed LG download mode but don't know what to do with it.
I assume you mean to follow these instructions:
http://forum.xda-developers.com/nexus-5x/help/unbrick-nexus-5x-t3438133
leolittlebook said:
It doesn't hang. It shows the normal sequence of GOogle screen and colored dots, then reboots.
I've accessed LG download mode but don't know what to do with it.
I assume you mean to follow these instructions:
http://forum.xda-developers.com/nexus-5x/help/unbrick-nexus-5x-t3438133
Click to expand...
Click to collapse
I gave those directions a try and I'm back at the bootloop with a locked bootloader. I don't know how I'm supposed to flash anything with a locked bootloader, aside from those TOT files, which haven't worked yet... sigh. I really appreciate how much help the community here has been though, hopefully we can get this sorted out on our devices.
leolittlebook said:
I'm not sure whether I specifically ran the erase command manually on this iteration. I ran those exact two commands just now. It's bootlooping still.
Click to expand...
Click to collapse
Could you try: fastboot flash vendor (name of MTC20F vendor) then try restoring your boot, system, and data for your nandroid?
Sent from my Nexus 5X using Tapatalk
Huskehn said:
I gave those directions a try and I'm back at the bootloop with a locked bootloader. I don't know how I'm supposed to flash anything with a locked bootloader, aside from those TOT files, which haven't worked yet... sigh. I really appreciate how much help the community here has been though, hopefully we can get this sorted out on our devices.
Click to expand...
Click to collapse
OTAs can be sideloaded with a locked bootloader.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Could you try: fastboot flash vendor (name of MTC20F vendor) then try restoring your boot, system, and data for your nandroid?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Phone shows up on LGUP. Loathe to try the other thread's directions if it might lock my bootloader.
Tried your suggestion. Didn't work.
flashed vendor stock, then restored nandroid backup all.
android boot sticks on google screen.
Followed these instructions through step 15
http://forum.xda-developers.com/nexus-5x/help/unbrick-nexus-5x-t3438133
Still had bootloop. Cycling through colored dots. Couldn't continue, because couldn't unlock phone's bootloader.
Also can't flash images, because no TWRP recovery anymore.
Seems I'm dead in the water, yes?
Not a big change.
ma
leolittlebook said:
Followed these instructions through step 15
http://forum.xda-developers.com/nexus-5x/help/unbrick-nexus-5x-t3438133
Still had bootloop. Cycling through colored dots. Couldn't continue, because couldn't unlock phone's bootloader.
Also can't flash images, because no TWRP recovery anymore.
Seems I'm dead in the water, yes?
Not a big change.
Click to expand...
Click to collapse
why you cant access the bootloader?
may not. you now have a full stock phone with locked botloader. maybe you contact google at this point.
Thargorsson said:
why you cant access the bootloader?
Click to expand...
Click to collapse
because my DEVICE STATE - is now locked
I think I flashed the international tot file, whereas this phone is a different Hong Kong version.
see here:
http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740/page13#post68381176
Thargorsson said:
why you cant access the bootloader?
Click to expand...
Click to collapse
I think he means he has bootloader access, but it's locked (that is how my phone currently is as well). You can only flash valid/signed zips from there, not custom ROMs or recoveries.
My goal now at the very least is to get the bootloader unlocked again.