Hello, so i got a asus nexus 7 wifi model, never seen it working. Recovery says booting failed. The one thing that works is fastboot. So i decided to reflash everything. But when i run fastboot oem unlock after about 6mins i get FAILED (remote: () as i understand no error.
I tried 3 drivers, official, naked and from asus nexus toolkit everytime same result. I tried few different pc's diferent usb ports. So maybe someone had a same problem and knows what to try next.
Bootloader version 4.13
full log:
...
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: ()
finished. total time: 391.390s
Thx in advance
xz33r0x said:
Hello, so i got a asus nexus 7 wifi model, never seen it working.
Click to expand...
Click to collapse
I hope you didn't pay much for it. At this time there is no known workaround, as APX mode on the N7 has not been cracked with an nvflash-like tool.
You might consider donating it to the folks at androidroot.mobi, or... becoming the person that breaks into APX on the N7.
bftb0 said:
I hope you didn't pay much for it. At this time there is no known workaround, as APX mode on the N7 has not been cracked with an nvflash-like tool.
You might consider donating it to the folks at androidroot.mobi, or... becoming the person that breaks into APX on the N7.
Click to expand...
Click to collapse
I didn't pay for it at all yeah have read about apx. Just was wandering is there any other options, or the nand is dead like a brick
Hi everyone,
In the past days I tried to unlock and root my Nexus 10, and looks like something went very wrong.
Right now, I'm stuck with the bootloader screen; the tablet boots into bootloader and I can only go to "bootloader" (power + vol up + vol down) or "download" (power and vol up).
The bootloader screen reads:
PRODUCT NAME: mantra
VARIANT: wifi
H/W VERSION: 8
BOOTLOADER VERSION : MANTAMD003
CARRIER INFO: NONE
SERVIAL NUMBER: XXXXXXXXX
LOCK STATE: UNLOCKED
REBOOT MODE FLAG: NONE
I've tried using different tools, including "Wugs Nexus Root Toolkit" and command line fastboot.
Some fastboot commands seem to work - e.g.:
fastboot devices (it does recognise my device)
fastboot -w (the messages on the screen seem to suggest it's all ok)
fastboot getvar all:
(bootloader) product: manta
(bootloader) variant: wifi-only
(bootloader) serialno: XXXXXXXXX
(bootloader) version-hardware: 8
(bootloader) version-bootloader: MANTAMD03
(bootloader) secure: yes
(bootloader) unlocked: yes
(bootloader) off-mode-charge: enabled(1)
(bootloader) signing: yes
(bootloader) boot partition- type: raw, size: 0x0000000001000000
(bootloader) recovery partition- type: raw, size: 0x0000000001ff0000
(bootloader) metadata partition- type: raw, size: 0x0000000000010000
(bootloader) misc partition- type: raw, size: 0x0000000000400000
(bootloader) cache partition- type: ext4, size: 0x0000000021000000
(bootloader) system partition- type: ext4, size: 0x0000000032000000
(bootloader) userdata partition- type: ext4, size: 0x0000000352c00000
The problem is with commands like:
fastboot flash bootloader bootloader-manta-mantamd03.img
(or any flashing command for what it matters).
None of them works; after waiting for a long while, the error returned is "Too many links".
I have googled the command, but I haven't found anything meaningful. ADB doesn't work - I must use fastboot to unbrick the device.
Any suggestions?
Andres
I haven't unlocked & rooted yet.. just started looking at it today. It seems you can already get into bootloader. Shouldnt you be flashing a recovery in download mode?
---------- Post added at 10:11 PM ---------- Previous post was at 10:10 PM ----------
Also the toolkit has an option for bricked devices. I'd look into that as a last resort.
faiyo said:
I haven't unlocked & rooted yet.. just started looking at it today. It seems you can already get into bootloader. Shouldnt you be flashing a recovery in download mode?
---------- Post added at 10:11 PM ---------- Previous post was at 10:10 PM ----------
Also the toolkit has an option for bricked devices. I'd look into that as a last resort.
Click to expand...
Click to collapse
Hi, thanks for the suggestion.
I've tried to flash a recovery image already - that didn't work. That's why I tried flashing anything. I've also tried the "Back to stock" option in the toolkit, and it hangs when trying to flash anything to the tablet...
Andres
I was still curious so i went googling. I think u should try a different cable and another usb port and different computer. It has fixed this issue for some people. Others said to try odin but what you're doing should really work. Otherwise there is a hardware failure and replacement parts dont seem to be an option... except at best a pogo connector cable in case the microusb jack is borked. I hope someone else chimes in for you. I haven't had any experience with this device. Maybe take some comfort in the asus nexus 10 coming out in a few months?
Have you tried using Wugs to Flash the Stock ROM and Unroot? I have been unable to get ADB to find my Nexus 10, even though it's been listed in the Device Manager of Win 8 with each of the 4 suggested drivers suggested. After getting stuck in a Bootloop I was still able to use the 'Back to Stock' option to recover my Nexus 10.
Good luck.
faiyo said:
I was still curious so i went googling. I think u should try a different cable and another usb port and different computer. It has fixed this issue for some people. Others said to try odin but what you're doing should really work. Otherwise there is a hardware failure and replacement parts dont seem to be an option... except at best a pogo connector cable in case the microusb jack is borked. I hope someone else chimes in for you. I haven't had any experience with this device. Maybe take some comfort in the asus nexus 10 coming out in a few months?
Click to expand...
Click to collapse
Hi all,
thanks for your suggestions/comments. I did quite a lot of reading while trying to get this sorted, and the suggestion to check different cables/ports was popping up a lot.
I was on holiday - I tried all ports of the laptop, and 2 cables, with no success. Let me stress that with my first 2 cables the table was recognised - I couldn't just write (anything).
I didn't have access to more cables/computers and I though that I had done my homework with 2 cables/3 USB ports.
I was wrong; once I was back home I managed to sort it out in few minutes with a third cable.
I hope that my error does help anyone else reading this.
Right now I would like to know if there is some kind of cable that I can buy and know that it will work... Does anyone have any suggestions?
4ndres said:
Hi all,
thanks for your suggestions/comments. I did quite a lot of reading while trying to get this sorted, and the suggestion to check different cables/ports was popping up a lot.
I was on holiday - I tried all ports of the laptop, and 2 cables, with no success. Let me stress that with my first 2 cables the table was recognised - I couldn't just write (anything).
I didn't have access to more cables/computers and I though that I had done my homework with 2 cables/3 USB ports.
I was wrong; once I was back home I managed to sort it out in few minutes with a third cable.
I hope that my error does help anyone else reading this.
Right now I would like to know if there is some kind of cable that I can buy and know that it will work... Does anyone have any suggestions?
Click to expand...
Click to collapse
Definitely stick to non-counterfeit OEM samsung cables as best as you can. In the past few years, Samsung/Apple have bastardized and corrupted the usb standard. It's usually only noticeable for charging, though in any practical use we find one usb cable is actually better than another It's really disappointing.
Flash the factory image via fastboot. And never use toolkits.
Sent from my Galaxy Nexus using XDA Premium HD app
Hello Friends,
I got the bootloop problem on my nexus 6p from the last few days.
I Google it to solve the problem with various methods but I am unable to solve the problem. I tried command fastboot flashing unlock but I am getting remote: device is locked. I am unable to unlock usb debugging and oem through fastboot command prompt. When I write command fastboot devices then I get the serial number and when I write the command adb devices then I failed to get the device. I am also unable to get recovery mode.
here is some details of my nexus 6p
BL: angler-03.68
baseband: angler-03.81
product/variant: ANGLER-ROW-VN1
Serial Number: XXXXXXXXXXX
CPU: MSM8994 0x20001
eMMC: 64GB Samsung
DRAM: 3072MB SAMSUNG LPDDR4
Console: ttyHSL0,115200,n8
Battery ok
Device is LOCKED.
Qfuse status: ENABLED.
off-mode-charge: ENABLED.
Download Mode: DISABLED.
Connect USB Data Cable
can you guys help me to overcome this problem and install the new android os.
Looking for your response.
Thank You guys.
sumitpetal said:
Hello Friends,
I got the bootloop problem on my nexus 6p from the last few days.
I Google it to solve the problem with various methods but I am unable to solve the problem. I tried command fastboot flashing unlock but I am getting remote: device is locked. I am unable to unlock usb debugging and oem through fastboot command prompt. When I write command fastboot devices then I get the serial number and when I write the command adb devices then I failed to get the device. I am also unable to get recovery mode.
here is some details of my nexus 6p
BL: angler-03.68
baseband: angler-03.81
product/variant: ANGLER-ROW-VN1
Serial Number: CVH7N15C14001695
CPU: MSM8994 0x20001
eMMC: 64GB Samsung
DRAM: 3072MB SAMSUNG LPDDR4
Console: ttyHSL0,115200,n8
Battery ok
Device is LOCKED.
Qfuse status: ENABLED.
off-mode-charge: ENABLED.
Download Mode: DISABLED.
Connect USB Data Cable
can you guys help me to overcome this problem and install the new android os.
Looking for your response.
Thank You guys.
Click to expand...
Click to collapse
Try the following thread then post after your attempts in there as well:
https://forum.xda-developers.com/showthread.php?t=3640279
Sent from my Nexus 5X using Tapatalk
sumitpetal said:
... can you guys help me to overcome this problem and install the new android os. Looking for your response.
Click to expand...
Click to collapse
Unlocking your device is failing because you haven't ever enabled Allow OEM Unlock or USB Debugging from within the OS. The only way you will be able to unlock the phone is to get it to boot into the OS first, and going into Developer Options to toggle these two settings on. You may be able to use the method linked above to briefly get your phone booted into the OS long enough so you can do this. If you are lucky enough to accomplish this, then you can disable the big cores using a custom kernel.
SlimSnoopOS said:
Try the following thread then post after your attempts in there as well:
https://forum.xda-developers.com/showthread.php?t=3640279
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Hello SlimSnoopOS,
Thanks for giving the link. I checked it but in that links it showing the method to enable OEM and I am totally failed to boot into the OS. I got only Google Logo and it loop again and again. I tried fastboot flashing unlock but It showing me Remote: Device is locked.
Is there any way to installed the New OS or downgrade or repair current version with unlocked OEM Devices?
Looking for your response.
Thank you.
v12xke said:
Unlocking your device is failing because you haven't ever enabled Allow OEM Unlock or USB Debugging from within the OS. The only way you will be able to unlock the phone is to get it to boot into the OS first, and going into Developer Options to toggle these two settings on. You may be able to use the method linked above to briefly get your phone booted into the OS long enough so you can do this. If you are lucky enough to accomplish this, then you can disable the big cores using a custom kernel.
Click to expand...
Click to collapse
Hello v12xke,
Thank you for your response.
I am totally failed to go into the os. I am getting only Google Logo and its looping. so I am unable to go in to setting and enable OEM unlocking option in developer option.
do you have any other option to install, repair current version with Unlocked OEM devices ?
Thank You so much.
sumitpetal said:
Hello SlimSnoopOS,
Thanks for giving the link. I checked it but in that links it showing the method to enable OEM and I am totally failed to boot into the OS. I got only Google Logo and it loop again and again. I tried fastboot flashing unlock but It showing me Remote: Device is locked.
Is there any way to installed the New OS or downgrade or repair current version with unlocked OEM Devices?
Looking for your response.
Thank you.
Click to expand...
Click to collapse
You have to try either of those two methods (extreme heat or extreme cold) to see if you can get it to boot even for a couple minutes. Neither method is quick nor do you have time to mess around once the phone finally boots. You can only upgrade with a locked bootloader. So you are stuck unless you are under warranty or can try the fix.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
You have to try either of those two methods (extreme heat or extreme cold) to see if you can get it to boot even for a couple minutes. Neither method is quick nor do you have time to mess around once the phone finally boots. You can only upgrade with a locked bootloader. So you are stuck unless you are under warranty or can try the fix.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Hello SlimSnoopOS,
I found a video on youtube which fix the bootloop by opening the whole phone. can It possible ?
could you please check the video -> https://www.youtube.com/watch?v=-A-FQp1DP7A
can It be possible ?
Thank You.
sumitpetal said:
Hello SlimSnoopOS,
I found a video on youtube which fix the bootloop by opening the whole phone. can It possible ?
could you please check the video -> https://www.youtube.com/watch?v=-A-FQp1DP7A
can It be possible ?
Thank You.
Click to expand...
Click to collapse
I'm at work so I can't watch your video. I don't recommend opening up a device if you aren't technically sound enough to follow whatever the instructions are. So, try at your own risk and loss of warranty.
Sent from my Nexus 5X using Tapatalk
Hey man, here is what I did though my device was rooted/unlocked/custom kernal (EX)
- Put the phone on charge
- Switch on, let it bootloop, eventually it booted [takes a day at times]
- Backup if you need to (eg. ADB pull).
- I have EX manager so I enabled power save mode which disables the 4 big cores. As long as the phone doesn't reboot or die no bootloops.
boeder9 said:
Hey man, here is what I did though my device was rooted/unlocked/custom kernal (EX)
- Put the phone on charge
- Switch on, let it bootloop, eventually it booted [takes a day at times]
- Backup if you need to (eg. ADB pull).
- I have EX manager so I enabled power save mode which disables the 4 big cores. As long as the phone doesn't reboot or die no bootloops.
Click to expand...
Click to collapse
Hello boeder9,
Thanks for reply.
my device is not rooted and unlocked but let me try it, hope it works...!!
Thank you
sumitpetal said:
Hello v12xke, Thank you for your response.
I am totally failed to go into the os. I am getting only Google Logo and its looping. so I am unable to go in to setting and enable OEM unlocking option in developer option.
do you have any other option to install, repair current version with Unlocked OEM devices ? Thank You so much.
Click to expand...
Click to collapse
You will need to get into the OS somehow to toggle the dev settings. Otherwise you will not be able to unlock the bootloader. You will not be able to apply the fix (flash custom kernel) with a locked bootloader, and there is no way to unlock it unless your phone can boot. There are a few "tricks" to use with the heatgun/hairdryer that force the phone into limp mode so it will boot into the OS. Others have claimed that once booted, they have enabled "power savings" under settings>>battery and that prevents the phone from going back into the looping. Keep trying, and good luck with the hairdryer!
v12xke said:
You will need to get into the OS somehow to toggle the dev settings. Otherwise you will not be able to unlock the bootloader. You will not be able to apply the fix (flash custom kernel) with a locked bootloader, and there is no way to unlock it unless your phone can boot. There are a few "tricks" to use with the heatgun/hairdryer that force the phone into limp mode so it will boot into the OS. Others have claimed that once booted, they have enabled "power savings" under settings>>battery and that prevents the phone from going back into the looping. Keep trying, and good luck with the hairdryer!
Click to expand...
Click to collapse
Hi v12xke,
Thanks for the details, Let me try with hairdryer. Hope it works...!!!
Thank You so much once again.
SlimSnoopOS said:
Try the following thread then post after your attempts in there as well:
https://forum.xda-developers.com/showthread.php?t=3640279
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Same problem... , i tried several flashes ... nothing!
but seems to me it's a fault on the software ... a bug or a glitch, because it came at the end of february! or a malware of some kind!
moshu_fc said:
Same problem... , i tried several flashes ... nothing!
but seems to me it's a fault on the software ... a bug or a glitch, because it came at the end of february! or a malware of some kind!
Click to expand...
Click to collapse
If it's a software issue best thing to do is completely wipe your phone. Easiest way is to install Twrp and wipe all incuding internal then flashing fresh stock image. I'm sure there is fastboot commands also to erase (or some other way if can't do neither.) This will remove every last thing from your phone so make sure if you are able to back up pics,docs,downloads,music etc. Last thing though don't think it's causes issues make sure your flashing the right version of February stock image Google finally labled them. Or March if it's out.
sumitpetal said:
Hello Friends,
I got the bootloop problem on my nexus 6p from the last few days.
I Google it to solve the problem with various methods but I am unable to solve the problem. I tried command fastboot flashing unlock but I am getting remote: device is locked. I am unable to unlock usb debugging and oem through fastboot command prompt. When I write command fastboot devices then I get the serial number and when I write the command adb devices then I failed to get the device. I am also unable to get recovery mode.
here is some details of my nexus 6p
BL: angler-03.68
baseband: angler-03.81
product/variant: ANGLER-ROW-VN1
Serial Number: XXXXXXXXXXX
CPU: MSM8994 0x20001
eMMC: 64GB Samsung
DRAM: 3072MB SAMSUNG LPDDR4
Console: ttyHSL0,115200,n8
Battery ok
Device is LOCKED.
Qfuse status: ENABLED.
off-mode-charge: ENABLED.
Download Mode: DISABLED.
Connect USB Data Cable
can you guys help me to overcome this problem and install the new android os.
Looking for your response.
Thank You guys.
Click to expand...
Click to collapse
Hello, you describe a cluster A57 failure, to fix it you need to boot into your phone enough time to enable USB debugging and OEM unlock then flash a modified kernel or a modified ramdisk
See this thread : https://forum.xda-developers.com/nexus-6p/general/guide-fix-nexus-6p-bootloop-death-blod-t3640279/
To boot into your device you need to overheat the CPU so the software will shutdown the faulty A57 clusters to cool down the device as soon as it boot up enable USB debugging and OEM unlock before the A57 clusters goes online (because it will shutdown your device) once you succeed enable USB debugging and OEM unlock flash modified files and enjoy your working (but slower) N6P
I had that problem too, but wasn't able to live thinking that my phone was working with CPU issues, so I bought an other Nexus 6P from a guy on the internet, he was selling it because the screen was broken, I got it for real cheap ! I swapped the screen of my BLOD N6P to the one from the guy, it cost me 60$ to completely fix my phone (way less than buying a new phone or buying a new microprocessor)
Exodusche said:
If it's a software issue best thing to do is completely wipe your phone. Easiest way is to install Twrp and wipe all incuding internal then flashing fresh stock image. I'm sure there is fastboot commands also to erase (or some other way if can't do neither.) This will remove every last thing from your phone so make sure if you are able to back up pics,docs,downloads,music etc. Last thing though don't think it's causes issues make sure your flashing the right version of February stock image Google finally labled them. Or March if it's out.
Click to expand...
Click to collapse
Hy!
Already done that... Today It comes back from service, they told me they replaced the PCB ... so... it could be a hardware problem or a malware of some kind that ruins the memory... that's what i think about those problem, but i suspect google has something to do whit it!
So... i'll get back to you when I will have IT! :fingers-crossed:
bootloop can't unlock device
I have had exactly the same problem. I tried in vain using heat or cold to get the thing to boot, but independently found the method of leaving it on charge for a few days, occasionally it will get into the O/S.
So while in the O/S I enabled developer options and adb too (the second time) and unlocked the bootloader.
However it still claims to be "device is LOCKED" in recovery mode. This is really weird. I have also factory reset the phone but that hasn't helped.
Luckily I have read the other posts about power saving mode so I'll try that next, it will save having to flash a non-stock OS.
When people ask why unlocking the bootloader is important to me, this specific situation comes to mind. If you had unlocked your device you could have fixed this easily, mind you you would lose 4 cores.
Nexus 6P Huawei H1511 Bootlooping fix with OEM Unlock off
sumitpetal said:
Hello Friends,
I got the bootloop problem on my nexus 6p from the last few days.
I Google it to solve the problem with various methods but I am unable to solve the problem. I tried command fastboot flashing unlock but I am getting remote: device is locked. I am unable to unlock usb debugging and oem through fastboot command prompt. When I write command fastboot devices then I get the serial number and when I write the command adb devices then I failed to get the device. I am also unable to get recovery mode.
here is some details of my nexus 6P.
Can you guys help me to overcome this problem and install the new android os.
Looking for your response.
Thank You guys.
Click to expand...
Click to collapse
*** I ran into a similar catch-22 issue on my 6P (H1511) the dreaded bootlooping with OEM Unlock turned OFF. ***
*** Couldn't flash the phone because OEM Unlock was off, and couldn't turn OEM Unlock on because it was bootlooping. ***
*** You MUST be able to fix the bootlooping/freezing at least temporarily, in order to turn on OEM Unlock in Developer Options ***
I have tried the "squeezing" method to no avail.
Then tried the heating method, which worked to a point where it has reached the color circles while booting, but then it started looping again.
I figured there's nothing to loose, so I cranked up the heat on the digital heating plate to exactly 140 Celsius for about 10 minutes covered with a paper towel, with only the upper half of the phone's back touching the heating plate (no need to "cook" the lower part with the battery).
It was still looping after the circles appeared, BUT by leaving it to cool off for about an hour, it has finally booted up into the setup page, so I quickly went to Settings > About/Phone/Software Info > clicked the "Build" line 7 times to enable Developer Options, under which I enabled OEM Unlock and ADB Debug.
If it's still bootlooping, you may try to "freezing" method where you would put the phone into the deep freezer for about an hour.
However, heating has worked for me.
Following that, in FastBoot mode I entered the following 3 versions of the flash unlock commands (only one will work out of the 3 which is fine):
fastboot oem unlock
fastboot flashing unlock
fastboot flashing unlock_critical
Downloaded the latest full stock firmware directly from Google.
https://dl.google.com/dl/android/aosp/angler-opm6.171019.030.b1-factory-ab13a98b.zip
Unzip it, and run flash-all.bat
Once the flashing has finished, DO NOT let it boot up, instead hold down the Volume Down as it's about to reboot, which will kick it into bootloader/fastboot mode.
I have tried flashing the Osmosis zip to patch the boot but it didn't work, it was still bootlooping.
So I have flashed a pre-patched 4-Core Boot kernel to fix the bootlooping issue permanently.
For Android 8.1 OPM6.171019.030 flash this 4-Core Boot with the commands below:
https://androidfilehost.com/?fid=13356325061477269711
fastboot flash boot Huawei_H1511_6P_OPM6.171019.030_Boot_4Core.IMG
fastboot reboot-bootloader
At this point flash a 4-Cores patched TWRP, go into TWRP recovery (hold down Volume Down + Power for 10 seconds, Volume Down to "Recovery", Power) and first "format" Data, then "wipe" Cache, Dalvik-Cache, and Data.
Note, all information on your phone will be lost by the above format/wipe operation.
All done, hope this method may help some of you.
And here are some interesting FastBoot commands I've come across....
C:\ADB>fastboot flashing get_unlock_ability
(bootloader) 1
OKAY [ 0.018s]
Finished. Total time: 0.019s
C:\ADB>fastboot getvar all
(bootloader) version:0.01
(bootloader) unlocked:yes
(bootloader) hardware-revision:ANGLER-VN2
(bootloader) version-baseband:angler-03.87
(bootloader) version-bootloader:angler-03.79
(bootloader) display-panel:
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x1d800000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x6400000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xdaa17ee00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xc0000000
(bootloader) serialno:8XV5T15C11000453
(bootloader) kernel:lk
(bootloader) product:angler
all:
Finished. Total time: 0.172s
Instead of "fastboot getvar all", you can also use "fastboot getvar <variable>" (without the quotes and <>)
Any <variable> from the log above, between "(bootloader)" and the second ":"
For example:
fastboot getvar serialno
Enjoy!
My nexus 6P recently went through this bootloop,
Google screen coming up and stuck there, for 5 days, i was going through many possible solutions throughout the web, but they all said it must boot to OS to be able to unlock oem bootloader,
Finally stuck at extreme heat or cold, extreme heat did'nt work for me, but YES extreme cold did actually work, i kept it in the deep freezer for about half an hour, and then waited 2 min, and plugged the charging cable and powered ON the phone, to my astonishment, it did start and i was able to use the phone.
I have rebooted several times since then, it works fine for certain time, and then crashes and restarts all the time, i can still use th phone but its uncertain when it will restart again.
I tried to install new custom rom, but it still says DEVICE IS LOCKED and i cannot do anything else.
Hello Guys,
I am currently facing a phone that stopped working after I switched it of for the night.
All I get is the Mi logo when powering on the device. I guess it is a boot-loop???
I have no clue what might have caused it since I did not update the system.
My Problem is that I need the data stored on it like Phone numbers, Pictures and my WhatsApp conversations.
Is there any possibility that I might get them back?
Maybe over Fastboot?
I spend quite some time on this issue but I am totally lost and would really appreciate it if someone would help me out!
This is the device info from fastboot
fastboot oem device-info
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
Yeah u got bootloop , u need to download ROM from MIUi downloads and then u need to reflash ur ROM with Mi-Flash , I think u have backup contact phone number and pictures from Mi-Cloud and Google account ( hope u not turn off this backup ) .. About WhatsApp , u can login right ? When u login all message will gone but u still member of group if u consider about this ..
Thanks for the answer. Well that's exactly my problem I don't have a backup that is up to date.
Is there any way to get to my data?
Garmetola said:
Hello Guys,
I am currently facing a phone that stopped working after I switched it of for the night.
All I get is the Mi logo when powering on the device. I guess it is a boot-loop???
I have no clue what might have caused it since I did not update the system.
My Problem is that I need the data stored on it like Phone numbers, Pictures and my WhatsApp conversations.
Is there any possibility that I might get them back?
Maybe over Fastboot?
I spend quite some time on this issue but I am totally lost and would really appreciate it if someone would help me out!
This is the device info from fastboot
fastboot oem device-info
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
Click to expand...
Click to collapse
As per your fastboot comand detail your bootloader is locked...you can not directly flash with miflash... U need to unlock your bootloader or u can also use deep flash cable to boot into download mode then you can dirty flash with miflash tool i.e. Flash all except data and storage....
Hope this helps to you..
r_rocky07 said:
As per your fastboot comand detail your bootloader is locked...you can not directly flash with miflash... U need to unlock your bootloader or u can also use deep flash cable to boot into download mode then you can dirty flash with miflash tool i.e. Flash all except data and storage....
Hope this helps to you..
Click to expand...
Click to collapse
Yeah .. This is what I mean .. Ur devices must be download mode bcz bootloader is locked , flash with miflash and I think that is good answer for not flash data and storage for devices
Hello,
My A1 is bricked since few days.
I've made few trys to get access on the data and i don't find any solution.
I can comunicate with the phone via Fastboot, but did not find a way to do something....
with fastboot oem device-info, i have this result:
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.060s]
finished. total time: 0.062s
the oem unlock is not allowed.
With ADB, no success, the USB depuration was not on before the brick so....
Does someone know a way to do something?
is there is a way to load something from a SD card to turn on again the device without erasing everything?
Thank you very much.
Regards
Lebenjb
Nope there is no way. You basically hard brick the device. Did you lock the bootloader after modifying system?
The only way I know of is EDM mode, but it requires opening the phone and short curcuit some contact ponit.
Thanks for your answer.
The A1 get bricked by itself using it with the original rom.
I was so interested to have access to save some files!
I have a new phone, so I'm not in hurry, but if someone knows a way to make a recovery with data or just to have access to the files.
Then I will "wipe and delete" to give it to my son
Regards