Related
Need some help.
I just sideloaded the 4.3 update to phone and now it's stuck on the 'X' loading screen.
My phone was rooted, but all stock (including the bootloader). I used the sideload ADB command and everything went fine, but the phone now won't boot.
How do I fix this?
did you data wipe(factory reset) before flashing?? if not, you have too.
I applied the OTA...didn't think I had to
Any idea on how I fix it now?
Really don't want to lose all my data
Install a custom recovery and wipe or apply factory image
favaroooo said:
Install a custom recovery and wipe or apply factory image
Click to expand...
Click to collapse
Is there a way I can fix it without wiping everything?
theprodigy85 said:
Is there a way I can fix it without wiping everything?
Click to expand...
Click to collapse
I do not think because you have to change recovery you must unlock the bootloader and unlock bootloader wipe the phone
theprodigy85 said:
Is there a way I can fix it without wiping everything?
Click to expand...
Click to collapse
no, its the data(and other stuff) causing it not to boot. same thing when flashing custom rom, you wipe when fkashing different roms. and going from android 4.2.2 to 4.3, theres many changes, enough to consider it a different rom.
Shoot...I should have done more research before doing this.
I did a factory reset through the stock bootloader...but it's still looping on the 'X' screen.
Can someone walk me through this or point me to a guide?
Bootloader is currently unlocked and I'm able to get into the factory recovery.
theprodigy85 said:
Shoot...I should have done more research before doing this.
I did a factory reset through the stock bootloader...but it's still looping on the 'X' screen.
Can someone walk me through this or point me to a guide?
Bootloader is currently unlocked and I'm able to get into the factory recovery.
Click to expand...
Click to collapse
are you flashing a zip or an img file??
simms22 said:
are you flashing a zip or an img file??
Click to expand...
Click to collapse
Initially, I flashed the OTA zip.
I'm okay with just restoring everything back to factory at this point...
Try to restore using the factory image
theprodigy85 said:
Initially, I flashed the OTA zip.
I'm okay with just restoring everything back to factory at this point...
Click to expand...
Click to collapse
yea, the zip youd want to wipe data/factory reset, then flash the rom. dirty flashing wont help since the changes are big enough.
theprodigy85 said:
Initially, I flashed the OTA zip.
I'm okay with just restoring everything back to factory at this point...
Click to expand...
Click to collapse
I bought my ole lady a Nexus 4 for Valentines day, anyway, today she got the OTA update and let it install the update. Now mind you she is 100% stock, adb debugging was not enabled, and her bootloader was still locked. (She would not let me touch her Nexus 4 lol) When the device rebooted it stuck on Android Upgrading finishing boot. So I said well let me see what I can do, this is what I did to fix it.
I use only Ubuntu so this may not work on windows i do not know. I Booted the device to the bootloader, connected it to my laptop via USB. I opened a terminal and typed in "sudo fastboot devices" and entered my password when promted and this gave me the device ID and fastboot letting me know fastboot was working. I then typed in "sudo fastboot reboot" and the device rebooted but was stuck on the bootanimation. I opened the internal storage up on my laptop in my file explorer and made a copy of her internal storage. Next I booted the device back into the bootloader then opened a terminal and typed in "sudo fastboot oem unlock" and the device gave me the unlock warning and the yes or no options. I selected yes so it would factory reset. After it did the factory reset the device reboot and booted to the setup welcome screen. Hope this helps others, also thanks to my good good friend Ljjehl for reminding me to use "sudo".
Edit: If you open the command promt with Administrative permissions in Windows this will work in Windows as well. Go to C:\Windows\System32\cmd.exe and right click on the cmd.exe file and select run as administrator. Then CD to the location with your fastboot.exe command. Thanks to another good friend TheBr0ken.
Thanks for the help...
I just ended up flashing each of the 4.3 components from the factory image. Just annoyed that I lost everything...
I'm stuck at the same screen. I received the OTA update, I didn't do anything special. My phone is unlocked and rooted (or WAS) but that was months ago, the rest is stock.
I think having encryption on my phone may have made it do this. I don't think Google anticipated doing the update properly for encrypted phones. Now I fear I've lost everything because even if I could connect, all data is encrypted...
similar problem
After starting to OTA update it was going smoothly, i was making breakfast, came back to find my screen at the "starting apps" screen frozen. The little circle that rotated wasnt doing anything so i left it there for awhile longer and still nothing. It would not move off that screen so i held power button down and restarted. now its stuck at the X screen also.
Yeah, I'm stuck there too. Already tried Factory Rest, didn't work. So what can I do?
I was on stock 4.2.2 and unrooted. I used the 'Google Services Framework' hack to force the 4.3 OTA update. The update downloaded successfully, phone restarted to apply the update and then restarted again. And now its stuck at the Google screen and keeps on restarting :crying:
I dont have the USB drivers installed on my PC too.
Same Problem
I have a nexus 4 (stock and unrooted),after 4.3 update,it is lagging during phone lock on/off (2 sec/5 sec).Hence I restarted my phone,and it stuck at "x" logo.Did clean data 3 times and then its working.
The problem is,in 2 days,I have experienced and done above thrice?
What could have gone wrong?
Hi guys,
I've just found how to correct this problem. All you have to do is to correctly wipe your phone before flashing factory image.
So :
Fastboot erase boot
Fastboot erase recovery
Fastboot format cache
Fastboot format system
Fastboot format userdata
I've just unbrick a n4 this way 15 minutes ago.
I have found the problem in recovery where you can see error log saying "cannot mount cache"
So formating correct the issue.
Hope it can help, fingers crossed.
Sent from my Galaxy Nexus using xda premium
My Nexus 6P is stuck on the Android boot animation after installing the Android Beta OTA that came out today. I waited like 30 Minutes and nothing was happening so I tried Clearing Cache which did nothing then factory resetting, Clearing Cache & Even sideloading the OTA using ADB to no avail. My huge mistake was not having OEM Unlocking enabled so now I can't even flash stock android.. I know this is my fault for being so stupid but is there anything at all I can do to save my phone?
AlfexOmega said:
My Nexus 6P is stuck on the Android boot animation after installing the Android Beta OTA that came out today. I waited like 30 Minutes and nothing was happening so I tried Clearing Cache which did nothing then factory resetting, Clearing Cache & Even sideloading the OTA using ADB to no avail. My huge mistake was not having OEM Unlocking enabled so now I can't even flash stock android.. I know this is my fault for being so stupid but is there anything at all I can do to save my phone?
Click to expand...
Click to collapse
I'm in the exact same boat...hopefully something can be done, but I'm afraid we're idiots for not having checked OEM Unlocking. I've tried adb sideloading the OTA image, but as you said, with a locked bootloader, we've got nothing. Anybody have any ideas?
You might be able to use ADB to modify the OEM Unlock setting while booting.
Also, if you ever plan to mess with your OS, especially alpha/beta versions, always have your bootloader unlocked to prevent issues like this.
Use Fastboot boot [[[name of latest twrp]]].img (make sure the .img is in the adb folder on your pc) and then do a full system wipe (not just factory reset, but literally everything, internal and external -- access this from the advanced menu in twrp). That should boot you into the system so that you can enable oem unlocking, unlock the bootloader, and carry on like normal.
imatts said:
Use Fastboot boot [[[name of latest twrp]]].img (make sure the .img is in the adb folder on your pc) and then do a full system wipe (not just factory reset, but literally everything, internal and external -- access this from the advanced menu in twrp). That should boot you into the system so that you can enable oem unlocking, unlock the bootloader, and carry on like normal.
Click to expand...
Click to collapse
Live booting TWRP works on the 6P even with the bootloader is locked?
Sent from my Nexus 5X using Tapatalk
imatts said:
Use Fastboot boot [[[name of latest twrp]]].img (make sure the .img is in the adb folder on your pc) and then do a full system wipe (not just factory reset, but literally everything, internal and external -- access this from the advanced menu in twrp). That should boot you into the system so that you can enable oem unlocking, unlock the bootloader, and carry on like normal.
Click to expand...
Click to collapse
Can't boot twrp.img because the device is locked. Anything else I can do?
I had something similar like this happen, for my fix, all I did was boot to bootloader, cleared cache and then did a complete shutdown, do not just reboot, just rebooting, would go thru the boot loop, but a full power down allowed it to boot up normally. Not sure if it will help in your situation, but it's an easy try
spookytay said:
I had something similar like this happen, for my fix, all I did was boot to bootloader, cleared cache and then did a complete shutdown, do not just reboot, just rebooting, would go thru the boot loop, but a full power down allowed it to boot up normally. Not sure if it will help in your situation, but it's an easy try
Click to expand...
Click to collapse
No luck for me, unfortunately. Keep in mind that I tried to sideload the OTA.zip with a locked bootloader before doing this, so that may have made this process not work. For those who haven't tried to "fix" their failed installation like I did, give the cache clear a try first.
Apparently some people can use the fastboot format command while their bootloader is locked. You can try booting into the bootloader and issuing these commands. (THIS WILL WIPE YOUR ENTIRE DEVICE INCLUDING SDCARD/INTERNAL STORAGE. Of course, your device is now bricked, so I'm sure this is fine for you.)
Code:
fastboot format cache
fastboot format userdata
My 6P is now fully working thanks to Matt1515 on another thread! This is a link to the OTA downgrade from N developer preview 3 to 6.0.1 worked like a charm for me! Just use recovery ADB sideloading
https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
AlfexOmega said:
My 6P is now fully working thanks to Matt1515 on another thread! This is a link to the OTA downgrade from N developer preview 3 to 6.0.1 worked like a charm for me! Just use recovery ADB sideloading
https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
Click to expand...
Click to collapse
Glad you got it working! Hopefully it works for the other guy too. Probably best to use the factory image if you wanna update to N, with OEM Unlocking enabled
lightmastertech said:
Glad you got it working! Hopefully it works for the other guy too. Probably best to use the factory image if you wanna update to N, with OEM Unlocking enabled
Click to expand...
Click to collapse
This method will work 100% just adb sideload the package and done. My idea worked thanks to the guy who posted the ota zip
Ame123 said:
This method will work 100% just adb sideload the package and done. My idea worked thanks to the guy who posted the ota zip
Click to expand...
Click to collapse
Hello guys. I'm having the same problem here: installed the update last Thursday, apparently didn't have usb debugging checked on and I can't get past the boot animation.
Tried everything: format several times, cleared cache, sideload, etc. I've tried to sideload this package you guys are talking about but unfortunately this doesn't work either... In cmd it says <waiting for devices>. Tried different usb ports and everything - still nothing
silviuardelean said:
Hello guys. I'm having the same problem here: installed the update last Thursday, apparently didn't have usb debugging checked on and I can't get past the boot animation.
Tried everything: format several times, cleared cache, sideload, etc. I've tried to sideload this package you guys are talking about but unfortunately this doesn't work either... In cmd it says <waiting for devices>. Tried different usb ports and everything - still nothing
Click to expand...
Click to collapse
Seems like it could be a driver issue. If you run adb devices does your device show up?
freezerbite said:
Seems like it could be a driver issue. If you run adb devices does your device show up?
Click to expand...
Click to collapse
Yes, the device was showing up in cmd but couldn't get over <waiting for devices>... I've tried to install TWRP and failed again. After trying to sideload the image a dozen times and clearing cache, formatting data, etc several times, it somehow worked in the end. Thank you very much!
It might sound like a dumb question, but how do i Side load through ADB? can you please point me in the right direction. I'd really appreciate it! @silviuardelean @Ame123 @AlfexOmega Actually, I don't think I ever enabled usb debugging
GeorgeOSbeta said:
It might sound like a dumb question, but how do i Side load through ADB? can you please point me in the right direction. I'd really appreciate it! @silviuardelean @Ame123 @AlfexOmega Actually, I don't think I ever enabled usb debugging
Click to expand...
Click to collapse
I was able to get mine to work without having it enabled you could try using Nexus Root Toolkit it guides you through how to do everything
https://www.youtube.com/watch?v=LfDSZsr6230
Locked bootloader 7.1.1 ota preview help!
I have the latest preview build directly installed ota from Google. The phone just started bootlooping the other day for no apparent reason. I didn't have the developer options on or oem unlock enabled.
I can get to bootloader mode and recovery mode. I have wiped and reset from recovery with no help. I can access adb and fastboot on the pc but it won't let me write any files because of the locked bootloader. Anything I try to sideload so far gives an error. Any further suggestions?
AlfexOmega said:
My 6P is now fully working thanks to Matt1515 on another thread! This is a link to the OTA downgrade from N developer preview 3 to 6.0.1 worked like a charm for me! Just use recovery ADB sideloading
https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
Click to expand...
Click to collapse
I'm full stock with locked bootloader. How do I install this package? Flashing through recovery or with adb (and in this case, which commands should I use)?
solefero69 said:
I'm full stock with locked bootloader. How do I install this package? Flashing through recovery or with adb (and in this case, which commands should I use)?
Click to expand...
Click to collapse
You use recovery to sideload it via adb. If you are unsure how to do so you can download and use Nexus Root Toolkit it does everything for you, it's really useful This video will help
https://www.youtube.com/watch?v=LfDSZsr6230
Hi everybody, i would like to remove the devices encription under Security-Encryption
Under Encrypt device i've got Encrypted.
I've tried to restore to factory default, from recovery, from fastboot using format userdata, but, no way.
How i can remove the encryption?
My device is ZE552KL
Thanks
swet90 said:
Hi everybody, i would like to remove the devices encription under Security-Encryption
Under Encrypt device i've got Encrypted.
I've tried to restore to factory default, from recovery, from fastboot using format userdata, but, no way.
How i can remove the encryption?
My device is ZE552KL
Thanks
Click to expand...
Click to collapse
I had a same issue with this device, but I had some experiment.
If your device is unlocked, you can flash TWRP, boot to recovery, wipe, format data.
Backup your data first! It will erase all of your data (Very noob answer)
Totally careful, don't do this if you didn't want a unexpected things. Or something...
The ASUS Zenfone 3 comes shipped encrypted by default. This is required by Google's Play Services agreement for phone OEMs. You cannot remove decryption on the Zenfone 3 without using a custom ROM.
sensi277 said:
The ASUS Zenfone 3 comes shipped encrypted by default. This is required by Google's Play Services agreement for phone OEMs. You cannot remove decryption on the Zenfone 3 without using a custom ROM.
Click to expand...
Click to collapse
Thanks!
TWRP isn't allowing me to Mount my Storage because it's asking for a password I don't know.
ZeldaLinkAaron said:
TWRP isn't allowing me to Mount my Storage because it's asking for a password I don't know.
Click to expand...
Click to collapse
I'm having the same issue. I just got my daughter this phone (the 552KL?), downloaded the official Asus bootloader unlocker APK and ran it, then rebooted to the bootloader to flash TWRP.
TWRP installed, but wants a password to unlock it. Before the bootloader unlock, I did put her Google account on the phone, but the tool said it would completely wipe the phone. Either way, I tried her google account password, but it just says wrong password. Same thing when I tried to boot to system.
Any tips?
@Flapjack
Format through twrp
wang1chung said:
@Flapjack
Format through twrp
Click to expand...
Click to collapse
That's what I ended up doing. I got some help on another thread. The problem I'm having now is that I can't format /cache. It's really weird. If I do a full wipe on the phone, it says it can't format it. I even tried formatting it through fastboot ("fastboot erase cache" then "fastboot format cache"), which says "OKAY finished", but doesn't fix the issue when trying to wipe cache inside of TWRP.
This phone is flat out weird compared to other phones. I don't get the bootloader unlock screen. It doesn't seem to want to boot system... it just keeps going to TWRP. On the few times I have gotten to boot into system (after flashing Carbon 6.1 unofficial), it ends up hanging on a blank screen. Windows makes a sound that a new device is connected, so I'm guessing it's connecting in EDL mode or something (no devices show with a "fastboot devices" or a "adb devices").
I really don't know where to go from here. I'm used to working with Axons, Motorolas, and OnePlus phones. They just work.
@Flapjack
The cache issue is a glitch with the build of twrp, it's not a big deal. There's a workaround posted somewhere, can't remember. Just use the file browser and delete the files on it. I think there's only one file that isn't 0 bytes.
Have you flashed magisk?
Sometimes a full wipe (system/data) and then flashing the raw firmware helps. Try magisk first.
wang1chung said:
@Flapjack
The cache issue is a glitch with the build of twrp, it's not a big deal. There's a workaround posted somewhere, can't remember. Just use the file browser and delete the files on it. I think there's only one file that isn't 0 bytes.
Click to expand...
Click to collapse
So you're saying it doesn't need to be actually wiped, I just need to go into cache and delete all the files in there? How about getting it to boot to system? It just keeps booting to recovery. Not sure when it started that, as after the first time I flashed the ROM, I was able to get it to boot to system by pressing the power button when the "bootloader unlocked" screen came up. That isn't working now.
Have you flashed magisk?
Sometimes a full wipe (system/data) and then flashing the raw firmware helps. Try magisk first.
Click to expand...
Click to collapse
For my first non-stock ROM flash, I flashed the Oreo modem, Carbon 6.1 unofficial ROM, ARM64 Gapps nano, and Magisk 16.0... all at once. I tried booting and it looked like it was setting up... but as I mentioned, it just went to a blank screen. After trying a full wipe and seeing the "couldn't wipe cache" message, I figured that was why.
How will flashing Magisk help me with wiping the cache partition or getting the thing to boot right? Sorry for my ignorance.
Flapjack said:
So you're saying it doesn't need to be actually wiped, I just need to go into cache and delete all the files in there?
Click to expand...
Click to collapse
wiping/formatting cache is the same as deleting all the files. Wiping is easier but as I said, doesn't work at the moment.
Flapjack said:
How will flashing Magisk help me with wiping the cache partition or getting the thing to boot right? Sorry for my ignorance.
Click to expand...
Click to collapse
magisk won't help with cache, but it will remove the verity flag that is tripped from having twrp. From my experience, if I don't flash magisk, it'll bootloop.
Yeah.... absolutely nothing I do will get it to boot to system now. I've flashed the ROM and Magisk, but no matter what, it keeps booting to recovery.
There were two folders under /cache... "Lost&Found" and "recovery". I deleted both, but that didn't help.
---------- Post added 5th July 2018 at 12:40 AM ---------- Previous post was 4th July 2018 at 11:44 PM ----------
wang1chung said:
wiping/formatting cache is the same as deleting all the files. Wiping is easier but as I said, doesn't work at the moment.
Click to expand...
Click to collapse
So I take it I did it right? I would say it's "pretty much" the same. Formatting a partition is different than deleting files/folders in an existing partition. Still, if deleting the files/folders is good enough, then that rules out why the system wouldn't boot after the first ROM install attempt. It would also explain why "fastboot erase cache" seems to work, but TWRP still throws an error. Fastboot erase is probably working just fine.
magisk won't help with cache, but it will remove the verity flag that is tripped from having twrp. From my experience, if I don't flash magisk, it'll bootloop.
Click to expand...
Click to collapse
Is there a custom version of Magisk for this phone? I'm just installing the usual magisk 16.0 zip file you can get on their site, but it doesn't seem to be helping with the phone continuously booting into recovery. Is there a way to remove that verity flag via adb?
@Flapjack
Magisk modifies one of the partitions to get around the flag (I believe), not doable through adb.
Standard magisk off their site is fine
Try this:
Format system/data
Flash custom Rom
Flash magisk
"Wipe" cache and davlik
Reboot
OR
Flash the raw firmware
Flash twrp
Flash whichever custom Rom & gapps where needed
Flash magisk
Factory reset and "Wipe" cache and dalvik
Reboot
wang1chung said:
@Flapjack
Magisk modifies one of the partitions to get around the flag (I believe), not doable through adb.
Standard magisk off their site is fine
Try this:
Format system/data
Flash custom Rom
Flash magisk
"Wipe" cache and davlik
Reboot
Click to expand...
Click to collapse
No go. Still just boots into recovery. Here's what the boot screen looks like (then the Asus logo pops up, then recovery loads)
Code:
< More information :
Dm-Verity in EIO mode
Your device software can't be
checked for corruption. Please
lock the bootloader.
Visit this link on another device:
g.co/ABHg.co/placeholder
Your device will shutdown in 10 seconds
I can press the power button to boot immediately, or wait the 10 seconds... which just boots anyway (doesn't shut down). If I press the volume buttons, I get the following options menu:
Power off
Restart
Recovery
Fastboot
Back to previous page
Flash the raw firmware
Flash twrp
Flash whichever custom Rom & gapps where needed
Flash magisk
Factory reset and "Wipe" cache and dalvik
Reboot
Click to expand...
Click to collapse
I haven't tried this yet. Would this be the best guide to follow?
HOW-TO: Go back to Stock Rom on ZE552KL/ZE520KL
https://forum.xda-developers.com/zenfone-3/how-to/how-to-to-stock-rom-recovery-zenfone-3-t3666223
@Flapjack
That is the correct screen for an unlocked bootloader.
Try this guide for the raw firmware instead, and verify it boots to the OS. Then flash twrp and the rom again.
wang1chung said:
@Flapjack
That is the correct screen for an unlocked bootloader.
Try this guide for the raw firmware instead, and verify it boots to the OS. Then flash twrp and the rom again.
Click to expand...
Click to collapse
Grrr... no matter what I do, it won't flash. The guide says to put it in fastboot mode, but the flash tool won't detect it (even though "fastboot devices" shows it just fine). If I boot it to recovery, it'll show up in the tool, but never actually flashes (see screenshot).
Flapjack said:
Grrr... no matter what I do, it won't flash. The guide says to put it in fastboot mode, but the flash tool won't detect it (even though "fastboot devices" shows it just fine). If I boot it to recovery, it'll show up in the tool, but never actually flashes (see screenshot).
Click to expand...
Click to collapse
This is why I stopped using Windows. Maybe try disabling "driver signature verification"? Swap USB ports? My computer has some high power and low power USB ports, certain devices won't work properly in the low power ones. A couple of guides mentioned unplugging and re-plugging the USB.
wang1chung said:
This is why I stopped using Windows. Maybe try disabling "driver signature verification"? Swap USB ports? My computer has some high power and low power USB ports, certain devices won't work properly in the low power ones. A couple of guides mentioned unplugging and re-plugging the USB.
Click to expand...
Click to collapse
That's a good idea. I'm going through a powered hub right now, but who knows...
I'll try that as soon as I get home.
Ok, different computer. This is my laptop I normally use to flash.
This time, I can get it it to start to flash, but with a second or two, it throws an error (see attached).
Flapjack said:
Ok, different computer. This is my laptop I normally use to flash.
This time, I can get it it to start to flash, but with a second or two, it throws an error (see attached).
Click to expand...
Click to collapse
are you running ASUS flash tool with admin privileges?
While I was on vacation my N6P (Android 6.01 MTC20L) decided it was time to give me the bootloop of death - talk about timing!
I have a recent backup I made via Flashfire saved on my PC but I need to get my phone booted - at least temporarily.
As I said my phone is on 6.01, but the fix offered by @XCnathan32 (https://forum.xda-developers.com/nexus-6p/general/guide-fix-nexus-6p-bootloop-death-blod-t3640279) is for Nougat and above. So what are my options?
- Should I use fastboot to upgrade to Nougat or Oreo then apply the fix?
- How do I dirty flash N or O without losing my data?
- Any ideas on the heating notion? Some people have had their phones working using a blow/hair dryer..is it dangerous to heat the phone? Will any parts get damaged?
Any response would be useful to me, thanks!
boeder9 said:
While I was on vacation my N6P (Android 6.01 MTC20L) decided it was time to give me the bootloop of death - talk about timing!
I have a recent backup I made via Flashfire saved on my PC but I need to get my phone booted - at least temporarily.
As I said my phone is on 6.01, but the fix offered by @XCnathan32 (https://forum.xda-developers.com/nexus-6p/general/guide-fix-nexus-6p-bootloop-death-blod-t3640279) is for Nougat and above. So what are my options?
- Should I use fastboot to upgrade to Nougat or Oreo then apply the fix?
- How do I dirty flash N or O without losing my data?
- Any ideas on the heating notion? Some people have had their phones working using a blow/hair dryer..is it dangerous to heat the phone? Will any parts get damaged? Any response would be useful to me, thanks!
Click to expand...
Click to collapse
More information would be useful to determine whether you really have BLOD or just bootlooping. What were you doing when it bootlooped? Was it just spontaneous? Are you able to access stock recovery or TWRP? Do you have a stable fastboot mode? If so, two options to try would be to use ADB to update using a newer version full OTA (eg. 7.0.0 (NRD90T)) or flash a full image (not OTA) with flash-all.bat, removing the -w (wipe) switch. Both of these methods will leave your data intact. If you don't have access to recovery mode (bootloops on selecting) or an unstable fastboot mode, then you are pretty much left with the hairdryer.
v12xke said:
More information would be useful to determine whether you really have BLOD or just bootlooping. What were you doing when it bootlooped? Was it just spontaneous? Are you able to access stock recovery or TWRP? Do you have a stable fastboot mode? If so, two options to try would be to use ADB to update using a newer version full OTA (eg. 7.0.0 (NRD90T)) or flash a full image (not OTA) with flash-all.bat, removing the -w (wipe) switch. Both of these methods will leave your data intact. If you don't have access to recovery mode (bootloops on selecting) or an unstable fastboot mode, then you are pretty much left with the hairdryer.
Click to expand...
Click to collapse
Thanks for the response.
- Phone was idle for a few moments thats when the bootlooping started.
- I was rooted (bootloader unlocked) with TWRP, I am unable to access it, takes me to the bootloop again
- What do you mean by stable fastboot. I can get to the fastboot mode by power button, volume down, remains there (if that's what you mean?)
boeder9 said:
Thanks for the response.
- Phone was idle for a few moments thats when the bootlooping started.
- I was rooted (bootloader unlocked) with TWRP, I am unable to access it, takes me to the bootloop again
- What do you mean by stable fastboot. I can get to the fastboot mode by power button, volume down, remains there (if that's what you mean?)
Click to expand...
Click to collapse
No access to Recovery mode is one hallmark of the BLOD. Without Recovery you have no ADB, even if it was enabled previously. Stable fastboot mode means you can actually flash something successfully and it completes before bootlooping again. Many people who are unlocked can start flashing, but it won't finish -or- flashing completes successfully, but the phone never boots up. Try the following: fastboot format your system, userdata, and cache and observe for errors. Do these 3 complete successfully? Next, fastboot FLASH the latest TWRP to your recovery partition.... errors? Try fastboot BOOT the same in an effort to get a working Recovery where you have some additional tools. If these fail, you are looking at either RMA if eligible or replacing the phone.
fastboot format system
fastboot format userdata
fastboot format cache
v12xke said:
No access to Recovery mode is one hallmark of the BLOD. Without Recovery you have no ADB, even if it was enabled previously. Stable fastboot mode means you can actually flash something successfully and it completes before bootlooping again. Many people who are unlocked can start flashing, but it won't finish -or- flashing completes successfully, but the phone never boots up. Try the following: fastboot format your system, userdata, and cache and observe for errors. Do these 3 complete successfully? Next, fastboot FLASH the latest TWRP to your recovery partition.... errors? Try fastboot BOOT the same in an effort to get a working Recovery where you have some additional tools. If these fail, you are looking at either RMA if eligible or replacing the phone.
fastboot format system
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
Do these commands (espec system and userdata) erase my data and app data/personal files?
Ill try these and get back
boeder9 said:
Do these commands (espec system and userdata) erase my data and app data/personal files? Ill try these and get back
Click to expand...
Click to collapse
Formatting userdata will, but you won't be saving anything if you can't access recovery. If you like, try formatting system and cache first. Look for errors. Then try fastboot flashing or fastboot booting TWRP. The action of formatting each partition will tell you if there is a problem with the internal memory, and correct it (if possible).
v12xke said:
Formatting userdata will, but you won't be saving anything if you can't access recovery. If you like, try formatting system and cache first. Look for errors. Then try fastboot flashing or fastboot booting TWRP. The action of formatting each partition will tell you if there is a problem with the internal memory, and correct it (if possible).
Click to expand...
Click to collapse
OK so I did fastboot format cache, finished fine (see attached)
Haven't done format system, is it safe? what will the system formatting erase?
As for TWRP do you mean fastboot flash recovery twrp.img?
EDIT: after the cache format I'm getting 1-2 red LED flashes before each bootloop, is this the battery being down? If I turn off the device, hook up the charger it shows a full battery with electricity charge sign and phone boots again to bootloop.
boeder9 said:
OK so I did fastboot format cache, finished fine (see attached)
Haven't done format system, is it safe? what will the system formatting erase?
As for TWRP do you mean fastboot flash recovery twrp.img?
EDIT: after the cache format I'm getting 1-2 red LED flashes before each bootloop, is this the battery being down? If I turn off the device, hook up the charger it shows a full battery with electricity charge sign and phone boots again to bootloop.
Click to expand...
Click to collapse
System is a read only partition. Formatting it will not cause any data loss of yours, but will temporarily render the phone not bootable... BUT It can easily be restored via fastboot from any factory image. You just extract and flash the system image back to the system partition. Userdata is your personal data. When you format that partition your personal data will be gone. You did mention you had a FF backup so I'm guessing that was on the backup.
Yes on flashing TWRP. If after FLASHING twrp you cannot access Recovery, then try BOOTING recovery- fastboot boot recovery twrp.img
If you get to a point where nothing is working and you decide to format system and userdata and they complete successfully, you can flash a full Google image using flash-all.bat
Not sure about the LED's but just make sure your battery is close to fully charged. You didn't ever mention an battery issue, so there shouldn't be one. If in doubt hook the charger up and let it sit before proceeding.
@v12xke
Thank you for all your help. I left the phone on charge and let it bootloop for a good period of time and went out, came back and it was booted. I disabled the big clusters as suggested by @nicotinic in ElementalX and the device appears to be working fine aside from a little lag. I can live with that
Currently doing a little ADB pull, then will clear some space for a full nandroid backup!
Thanks a bunch to you both.
Hi everyone, my case is very simple.
I need to wipe datas my samsung J7 in a recovery mode using adb, a command for that is "adb shell recovery --wipe_data".
The thing is I don't want it to reboot immediately, because I need to change a bit in data files using adb.
As far as I know, other devices have a fastboot mode which you can wipe data there and go back to a recovery mode to change data files.
Since Samsung devices do not support the fastboot mode, I can't achieve that.
So now I am stuck.
Are there any suggestions how to deal with my case?
Or do I need to buy other brand phones which support a fastboot mode?
It may be possible to do this via a custom recovery, but the factory recovery will automatically reboot after a data wipe, and there isn't much that can be done about that.
V0latyle said:
It may be possible to do this via a custom recovery, but the factory recovery will automatically reboot after a data wipe, and there isn't much that can be done about that.
Click to expand...
Click to collapse
Okay, thanks for answering, maybe I will try other devices to look up some workaround methods.