The 6p is showing 'No Sim Detected' for some time now . I've tried doing the following steps but no result yet. Got no other back up phone so would be grateful is someone could point me in the right direction.
My build number is 6.0.1 (MTC20L) , also says 'unknown' under baseband version.
1) Yes i tried taking out the sim and back in several times , no result
2) Tried to restart , reboot still no result.
3) I've tried a full factory reset after backing up on helium of course , from the power and volume down steps .
4) I've tried wipe cache from the the power and volume down steps
5) some sites suggested to look in to the ##4636## and turn off and and switch on the radio. This is where it got really confusing since the option simply did not click , (it didn't switch off or change in any way, it was stuck in switch off the radio!!!!)
6) Tried unlocking the bootloader and flash factory image (this includes the radio image) , no change
Any one got any idea whats going on? maybe some thing to do with the modem ?
Have you tried wiping your efs partitions?
tr4nqui1i7y said:
Have you tried wiping your efs partitions?
Click to expand...
Click to collapse
How do i go about doing this ? do you mean through twrp ?
Thermoproblem said:
How do i go about doing this ? do you mean through twrp ?
Click to expand...
Click to collapse
No, through adb. Boot into recovery and then
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
and
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
tr4nqui1i7y said:
No, through adb. Boot into recovery and then
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
and
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
Click to expand...
Click to collapse
when i boot in to recovery and type the command adb devices, it does not list my device any reason for this?
Thermoproblem said:
when i boot in to recovery and type the command adb devices, it does not list my device any reason for this?
Click to expand...
Click to collapse
Yeah i managed to get past this problem and executed the commands you gave me .
still after i switched off and on my phone there was no changes, the base band still says 'unknown' .
Should i flash the factory images and return to stock ?
Also does returning to stock mean that i return to the very first build , or it the current build image i am on right now (mtc20l) ?
Have you tried the sim card in a different phone just to make sure it's OK? If it's not the card, it might be the sim card reader that's broken. You could also try another sim card in your phone. The message is actually 'No Sim detected', right? I had 'No service' show up one morning, did every wipe I could think of and eventually locked the bl, flashed a clean stock image and took it back after reading it might be the antenna. Basically they changed the internals and I just got it back yesterday after 2 weeks. All good now.
Edit: you can basically flash any stock you want. I actually got mine back with a may or june patch (and a flat battery.. :/ ). Out of curiosity I updated the phone with otas up to nougat. It took 6 or so update cycles. Kind of a frustrating thought if I was the customer who actually would've wanted to start using it straight away
Sent from my Z3 Compact using XDA Labs
sm4tik said:
Have you tried the sim card in a different phone just to make sure it's OK? If it's not the card, it might be the sim card reader that's broken. You could also try another sim card in your phone. The message is actually 'No Sim detected', right? I had 'No service' show up one morning, did every wipe I could think of and eventually locked the bl, flashed a clean stock image and took it back after reading it might be the antenna. Basically they changed the internals and I just got it back yesterday after 2 weeks. All good now.
Edit: you can basically flash any stock you want. I actually got mine back with a may or june patch (and a flat battery.. :/ ). Out of curiosity I updated the phone with otas up to nougat. It took 6 or so update cycles. Kind of a frustrating thought if I was the customer who actually would've wanted to start using it straight away
Sent from my Z3 Compact using XDA Labs
Click to expand...
Click to collapse
Yeah i tried another sim card before and there was no change .
I don't think it was the sim card reader because my base-band version does not show up at all (plus no imei number ).
Also it did work for a few minutes with the orginal sim card but showed the network name and displayed 'no service' but this time the baseband version and imei number worked, that is before it went back to 'no sim detected' and been stuck there ever since then !
I had the same problem yesterday after flashing new rom, I flashed Radio in recovery then reflashed vendor & rom, everything's working right now.
you'll find the radio here : http://forum.xda-developers.com/showpost.php?p=63049054&postcount=3
oussamalabbize said:
I had the same problem yesterday after flashing new rom, I flashed Radio in recovery then reflashed vendor & rom, everything's working right now.
you'll find the radio here : http://forum.xda-developers.com/showpost.php?p=63049054&postcount=3
Click to expand...
Click to collapse
Sorry i'm very new to this and don't know the terminolgy very well.
so when you say flash radio in recovery, is it the same commands that you use in heisenberg's guide for n6p but instead of bootloader you do it after entering recovery ? :
Code:
adb reboot recovery
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
The vendor image and rom flashed in the bootloader right ? Here is the rom and factory image the same ?
Thermoproblem said:
Sorry i'm very new to this and don't know the terminolgy very well.
so when you say flash radio in recovery, is it the same commands that you use in heisenberg's guide for n6p but instead of bootloader you do it after entering recovery ? :
The vendor image and rom flashed in the bootloader right ? Here is the rom and factory image the same ?
Click to expand...
Click to collapse
I tend to use fastboot rather than twrp for flashing images (.img files). See this thread for more info, it will give you a good overview of flashing stuffs and you'll catch up with the terminology as well.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page1
Sent from my Z3 Compact using XDA Labs
Just google it, flashing is very easy on a nexus phone
oussamalabbize said:
Just google it, flashing is very easy on a nexus phone
Click to expand...
Click to collapse
You are right about it being easy after reading up. But its just that i;ve tried just about everything and the baseband version just does not show up in the phone information (also no IMEI), even though it shows up in the bootloader. My wifi weems to be working fine but still shows no sim.
Starting to think this may be due to simething other than the radio .
Tried the initial suggestion from the 1st reply using the commands to wipe the partition with no success, then flashing radio, vendor and ROM from the 2nd suggestion no success here either .
Not sure what to do anymore
tr4nqui1i7y said:
No, through adb. Boot into recovery and then
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
and
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
Click to expand...
Click to collapse
Your suggestion to use the commands to wipe the partition had no success, then flashing radio, vendor and ROM from the 2nd suggestion no success here either .
The baseband version just does not show up in the phone information (also no IMEI), even though it shows up in the bootloader. My wifi weems to be working fine but still shows no sim.
Maybe its due to some other problem and not the radio since the wifi is working.
Thermoproblem said:
Your suggestion to use the commands to wipe the partition had no success, then flashing radio, vendor and ROM from the 2nd suggestion no success here either .
The baseband version just does not show up in the phone information (also no IMEI), even though it shows up in the bootloader. My wifi weems to be working fine but still shows no sim.
Maybe its due to some other problem and not the radio since the wifi is working.
Click to expand...
Click to collapse
Hi, I seem to be in your same situation, no network after trying the radio flashes, resets and reboots.
Did you manage to find a solution for this issue?
Any help would be appreciated. Thanks
Related
So for the first time in my history of Android's since the G1 I've finally bricked a phone. Apparently there was an OTA for the T-Mo devices and I managed to hamfist my notification and accept it.
Needless to say I'm now stuck permanently booting into TWRP. I've tried some various troubleshooting methods including doing what I thought was a successful sideload of the TMo-Stock-Rooted Rom. It showed a successful push and ran through the install but I got a message kicked back saying "No OS installed". Now I've seen other users receive this same message and after rebooting anyway they got their ROM to boot.
No such luck for me, after it reboots (post sideload install) it shows system as unmounted and then just boots back into recovery ad nauseum...I'm really at a loss here folks.
Have you already tried this?...
http://forum.xda-developers.com/showthread.php?t=2451696
redduc900 said:
Have you already tried this?...
http://forum.xda-developers.com/showthread.php?t=2451696
Click to expand...
Click to collapse
Hadn't tried it previously but I just attempted to run the ADB command and it still boots into TWRP. I'm not sure if those commands worked or not however. I got a big wall of text in terminal after the second command.
FWIW, on every reboot System is unmounted (Data & Cache remain mounted) but I can check it. Seems that it's irrelevant whether its checked or not.
Tried a sideload using the Stock Rooted 110G image and still nothing. Sideload appears to go, and install goes through without error but reboots only into TWRP with System unmounted.
k4ylr said:
Hadn't tried it previously but I just attempted to run the ADB command and it still boots into TWRP. I'm not sure if those commands worked or not however. I got a big wall of text in terminal after the second command.
FWIW, on every reboot System is unmounted (Data & Cache remain mounted) but I can check it. Seems that it's irrelevant whether its checked or not.
Click to expand...
Click to collapse
can you get the phone to shut off and stay off. If you can then simply put it in download mode and use LG flash tool to flash stock rom back on. Please let me know if this is an option if not I will try and figure out something else
joewaz said:
can you get the phone to shut off and stay off. If you can then simply put it in download mode and use LG flash tool to flash stock rom back on. Please let me know if this is an option if not I will try and figure out something else
Click to expand...
Click to collapse
I can get it to shut off and stay off no problem. I'm on OSX at the moment and likely won't be able to get to a PC until the 9th. I'll definitely give the LG Flash tool method a try when I can.
k4ylr said:
I can get it to shut off and stay off no problem. I'm on OSX at the moment and likely won't be able to get to a PC until the 9th. I'll definitely give the LG Flash tool method a try when I can.
Click to expand...
Click to collapse
yes I am afraid you are stuck in till you can get to a real man's computer lol. I'm just kidding though my girlfriend has a stupid Apple and I was stuck with the same problem I had to drive 50 miles to where I used to live to pick up my laptop to fix this. But the LG flash tool works like a charm and you will not have any problems. Just make sure that you read the procedure for the Verizon phone. If you are not surelookup the forum wink Link
joewaz said:
yes I am afraid you are stuck in till you can get to a real man's computer lol. I'm just kidding though my girlfriend has a stupid Apple and I was stuck with the same problem I had to drive 50 miles to where I used to live to pick up my laptop to fix this. But the LG flash tool works like a charm and you will not have any problems. Just make sure that you read the procedure for the Verizon phone. If you are not surelookup the forum wink Link
Click to expand...
Click to collapse
Haha I hear you. I moved recently and the apt I'm in doesn't have ethernet drops so I had to order up a PCI wireless nic card =\ I'll dig around for the LG flash tool guides and see what I can learn.
I was hesitant to even flash a recovery because of how ass backwards LG made it for us in the first place =\
k4ylr said:
Haha I hear you. I moved recently and the apt I'm in doesn't have ethernet drops so I had to order up a PCI wireless nic card =\ I'll dig around for the LG flash tool guides and see what I can learn.
I was hesitant to even flash a recovery because of how ass backwards LG made it for us in the first place =\
Click to expand...
Click to collapse
brother I feel your pain. But when you get everything all situated I will tell you the easiest way to install a backup recovery program. It is an app in the App Market called free GEE... One click and bam you have a backup lol.. You may want to use freegee to make sure twrp is installed right.. It will just over write all the files and correct any wrongs... Freegee.. Remember that!!
k4ylr said:
So for the first time in my history of Android's since the G1 I've finally bricked a phone. Apparently there was an OTA for the T-Mo devices and I managed to hamfist my notification and accept it.
Needless to say I'm now stuck permanently booting into TWRP. I've tried some various troubleshooting methods including doing what I thought was a successful sideload of the TMo-Stock-Rooted Rom. It showed a successful push and ran through the install but I got a message kicked back saying "No OS installed". Now I've seen other users receive this same message and after rebooting anyway they got their ROM to boot.
No such luck for me, after it reboots (post sideload install) it shows system as unmounted and then just boots back into recovery ad nauseum...I'm really at a loss here folks.
Click to expand...
Click to collapse
No worries friend! I almost went crazy last night trying to find a fix!! Here what fixed mine!
You need to be EXTREMELY CAUTIOUS when typing this in:
Go to Advanced in TWRP and run Terminal
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit go
after it pushes through again type:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot.
coldcrush390 said:
No worries friend! I almost went crazy last night trying to find a fix!! Here what fixed mine!
You need to be EXTREMELY CAUTIOUS when typing this in:
Go to Advanced in TWRP and run Terminal
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit go
after it pushes through again type:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot.
Click to expand...
Click to collapse
Are those commands pushable through ADB? For whatever reason when I get to the Terminal Command through TWRP it wants me to navigate to a different directory and there's no command line to type things in. I've always been a CWM flash a .zip kinda guy so digging into ADB is all new for me.
coldcrush390 said:
no worries friend! I almost went crazy last night trying to find a fix!! Here what fixed mine!
You need to be extremely cautious when typing this in:
Go to advanced in twrp and run terminal
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit go
after it pushes through again type:
Dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot.
Click to expand...
Click to collapse
this worked perfectly!!! Thanks sooooo much!!!!!!!!!!!
k4ylr said:
Are those commands pushable through ADB? For whatever reason when I get to the Terminal Command through TWRP it wants me to navigate to a different directory and there's no command line to type things in. I've always been a CWM flash a .zip kinda guy so digging into ADB is all new for me.
Click to expand...
Click to collapse
Don't navigate anywhere, I thought the same thing just tap on select below and follow the commands. Take your time doing it and don't rush!
---------- Post added at 07:24 PM ---------- Previous post was at 07:23 PM ----------
jwagman1 said:
this worked perfectly!!! Thanks sooooo much!!!!!!!!!!!
Click to expand...
Click to collapse
Your welcome
What about if your in CWR? How can I bring my wife's phone? It tried to update itself and I'm stuck on recovery
coldcrush390 said:
Don't navigate anywhere, I thought the same thing just tap on select below and follow the commands. Take your time doing it and don't rush!
Click to expand...
Click to collapse
Ran the terminal side commands, got to LG Splash and we're sitting there now. We'll see how long it sits or if it's a boot loop.
**EDIT**
10 minutes sitting at the LG splash no go. I managed to snag an interim wifi adapter for my desktop so I'm going to try the Flash tool posted from earlier and see if it works.
Update
I was able to bring the phone back with those commands using adb thank you guys for your help.
djeddieone said:
How can I do this on add? What would be the commands on adb? I'm on CWR so I can't use twrp
Click to expand...
Click to collapse
Can't say for sure, I had seen some to run this way:
adb shell
then the 2 lines of prompt. I'm stuck on a boot loop so I'm trying to get the Flash Tool method to work. I should have not messed with G2 in retrospect lol, way too little support and far too big of a PITA to bother.
coldcrush390 said:
No worries friend! I almost went crazy last night trying to find a fix!! Here what fixed mine!
You need to be EXTREMELY CAUTIOUS when typing this in:
Go to Advanced in TWRP and run Terminal
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit go
after it pushes through again type:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot.
Click to expand...
Click to collapse
This worked for me. I tried several other methods from other threads but could not complete them for various reasons.
This also is the simplest method as it installed the update without my having to download it again.
djeddieone said:
Update
I was able to bring the phone back with those commands using adb thank you guys for your help.
Click to expand...
Click to collapse
Did you have any driver issues? I'm stuck in the same situation booting just to ClockworkMod Recovery after an attempted OTA update. Can't connect to Win7 because driver can't configure properly even with the latest drivers installed. Connects file with my wife's working LG G2 so I know the drivers are right. Also tried to get into download mode with no luck. I'm stuck. Does anyone know how to get pass this?
Problem fixed!!!!
eat314 said:
Did you have any driver issues? I'm stuck in the same situation booting just to ClockworkMod Recovery after an attempted OTA update. Can't connect to Win7 because driver can't configure properly even with the latest drivers installed. Connects file with my wife's working LG G2 so I know the drivers are right. Also tried to get into download mode with no luck. I'm stuck. Does anyone know how to get pass this?
Click to expand...
Click to collapse
OK. Finally got it working. Wish I had figured it out before I factory reset my phone. My main issue was the driver. Even though I had the right LG drivers installed, it just would not recognize it properly. Here is what I had to do after a failed device configuration.
- Go to Computer Management and find the failed device and Update Driver.
- Choose to manually select device and then select Have Disk.
- Find and select \Program Files (x86)\LG Electronics\LG VZW United Driver\64BitADB\lgandadb.inf (Tried the other xxxadb.inf files but none worked)
- When the list of devices is presented, scroll down and select LGE Mobile Server Single ADB Interface
Your device should now be recognized by adb. Follow the steps provided by others above in this thread and you should be good to go. Worked for me. Good luck.
Thank you all for the great knowledge base. Saved me $500!!! ::good:
Hi everyone!
I was using Resurrection Remix ROM on my 6P, no custom kernel and TWRP 3.0.2-2 installed. I installed the ROM by going back to stock, reflashing the recovery, and installing ROM + GAPPS - I like my ROM installs squeaky clean, never had an issue. I set up my phone and moved in completley. I went on with my day until around 11 last night where I was rebooting into recovery to do a TWRP backup the phone just never booted. I rebooted bootloader and tried again but I kept getting the Google logo and the device rebooting. Then again Google logo and reboot. Never showed the TWRP splash screen.
I then went ahead and tried returning the phone back to stock. I downloaded the firmware from Google (latest Nougat), put the phone in bootloader, and began the installation (using flash-all from the zip file). Everything seemed like it installed fine (no errors) and the phone reboots. Same issue, Google logo and a reboot. I tried going into the stock recovery, but no dice - Google logo, reboot. I reflashed TWRP to see if maybe that'll work but it didn't (Google logo, Reboot, rinse and repeat).
I relocked the bootloader and for a split second I saw the "Erasing" with the colourful hoops then a reboot to the Google logo - never booting into the fresh install.
Fastboot responds and detects my phone, I have opened the phone and the power button isn't stuck, I have tried going back to MM stock (installs but no boot).
Is there anything else I can do before going out and buying a new phone?
Thank you!
xxxrichievxxx said:
Hi everyone!
I was using Resurrection Remix ROM on my 6P, no custom kernel and TWRP 3.0.2-2 installed. I installed the ROM by going back to stock, reflashing the recovery, and installing ROM + GAPPS - I like my ROM installs squeaky clean, never had an issue. I set up my phone and moved in completley. I went on with my day until around 11 last night where I was rebooting into recovery to do a TWRP backup the phone just never booted. I rebooted bootloader and tried again but I kept getting the Google logo and the device rebooting. Then again Google logo and reboot. Never showed the TWRP splash screen.
I then went ahead and tried returning the phone back to stock. I downloaded the firmware from Google (latest Nougat), put the phone in bootloader, and began the installation (using flash-all from the zip file). Everything seemed like it installed fine (no errors) and the phone reboots. Same issue, Google logo and a reboot. I tried going into the stock recovery, but no dice - Google logo, reboot. I reflashed TWRP to see if maybe that'll work but it didn't (Google logo, Reboot, rinse and repeat).
I relocked the bootloader and for a split second I saw the "Erasing" with the colourful hoops then a reboot to the Google logo - never booting into the fresh install.
Fastboot responds and detects my phone, I have opened the phone and the power button isn't stuck, I have tried going back to MM stock (installs but no boot).
Is there anything else I can do before going out and buying a new phone?
Thank you!
Click to expand...
Click to collapse
It's been an ongoing thing with the 6P's and 5X devices. Here's a thread that might be able to help you. I myself fell victim to this and nothing i did brought it back to life. Wound up doing an RMA with Huawei..
Check your warranty status http://consumer.huawei.com/us/support/warranty-query/index.htm
Thread: http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page41
One more Guide: http://forum.xda-developers.com/android/help/guide-revive-angler-bootloop-t3454938/page5
Hope this helps..
BIGSAMDA1ST said:
It's been an ongoing thing with the 6P's and 5X devices. Here's a thread that might be able to help you. I myself fell victim to this and nothing i did brought it back to life. Wound up doing an RMA with Huawei..
Check your warranty status http://consumer.huawei.com/us/support/warranty-query/index.htm
Thread: http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page41
One more Guide: http://forum.xda-developers.com/android/help/guide-revive-angler-bootloop-t3454938/page5
Hope this helps..
Click to expand...
Click to collapse
THANK YOU for shining some light on this issue! Looks like my phone is under warranty till 05/2017. But my next question is would the warranty be voided because I opened up the phone to make sure the power button wasn't the cause of the issue? :| I hope not!
Thanks again!
xxxrichievxxx said:
THANK YOU for shining some light on this issue! Looks like my phone is under warranty till 05/2017. But my next question is would the warranty be voided because I opened up the phone to make sure the power button wasn't the cause of the issue? :| I hope not!
Thanks again!
Click to expand...
Click to collapse
Absolutely, yes. Your warranty is void. That's always going to be the case on just about any electronic product. The only exceptions I know of are upgrading the hard drive in your PlayStation or Xbox, since you don't actually have to dismantle the entire system. They make the hard drives easily accessible without having to open anything else. As far as phones go, opening them will always void the warranty. They can tell as well, so you can't get a warranty replacement. Hopefully those links provided can help solve your issue so you don't need to pay out of pocket for a new phone. Good luck.
I had this problem when nougat previews first started. This is what worked to get me back up. I guess it erases the efs partitions and forces the phone to rebuild them. I tried fastboot flashing stock, etc, nothing worked, then I ran these two commands and it booted right up.
adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
Sent from my Pixel XL using Tapatalk
how did you get adb to work? The phone does not go into recovery mode, always bootloop.
shiftr182 said:
I had this problem when nougat previews first started. This is what worked to get me back up. I guess it erases the efs partitions and forces the phone to rebuild them. I tried fastboot flashing stock, etc, nothing worked, then I ran these two commands and it booted right up.
adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
guys have the same problem and Huawei does not help me and are under warranty, I have tried google but to no avail what can I do?
wonderdroid87 said:
guys have the same problem and Huawei does not help me and are under warranty, I have tried google but to no avail what can I do?
Click to expand...
Click to collapse
Where did you purchase the device from? Try Huawei again, maybe you'll get a different rep.
Amazon
I had a very similar problem. In the end, I used WugFresh's Nexus root toolkit to flash stock Nougat, with 'current status' set to 'soft-bricked'. That worked fine, and I'm back to normal...
jozomali said:
I had a very similar problem. In the end, I used WugFresh's Nexus root toolkit to flash stock Nougat, with 'current status' set to 'soft-bricked'. That worked fine, and I'm back to normal...
Click to expand...
Click to collapse
I'm a try but not work
I spoke with Huawei and as soon as I told them about the issue they right away were going to give me an RMA. I told them that the phone received an update from "google" and when I restarted the phone, the phone started to bootloop and never booting back to the home screen. But before we proceeded with the RMA I had to tell them the bad news - that my phone was opened because I was suggested to check if the power button wasn't the cause. She said that that voided the warranty and that my phone wont be covered for any repairs. I asked if I can pay them to fix it and they said no.
All in all I have a very pretty paperweight sitting, waiting to see if someone can come up with a fix. For now I'm using a Blackberry Passport with my android apps installed.
If not I'll either be moving to a OnePlus 3 or OnePlus 3T.
P.S. the toolkit "Soft-brick" option did not work for me either.
[Guide] Fool/Noob proof way to do clean installs on Nexus Devices
http://forum.xda-developers.com/nexu...talls-t3518311
try this clean install should work
I need your help, after upgrading to 7.1.1 the phone is dialed and restarted all the time in this way.
I would appreciate a solution, I leave an exact example of what happens to me.
OEM is not unlocked and debugging mode either because I can not start the phone
My problem is that it does not unlock OEM and I was not active debugging, the phone just let me enter Fastboot but at the time of choosing RECOVERY it restarts
emmafer44 said:
I need your help, after upgrading to 7.1.1 the phone is dialed and restarted all the time in this way.
I would appreciate a solution, I leave an exact example of what happens to me.
OEM is not unlocked and debugging mode either because I can not start the phone
Click to expand...
Click to collapse
Dude try Nexus toolkit my Wugfresh (NRT Toolkit) you have to boot to bootloader and use the application to clean install
I have this same problem. flashed MegaPixel6P, tried using the camera, and then my phone shut off and just keeps rebooting. i think /data and /system are corrupted. any attempt to nandroid backup or restore fails and causes TWRP to reboot.
Alot of users are facing this bootloop issue. So far no one has been able to figure out a pattern that will give us insight into what kind of devices might be affected by this issue. I have created this survey on GoogleForums so far there are very few responses. Please participate to help the community figure out the probable cause for this bootloop
https://docs.google.com/forms/d/1nGAVdnjbkOE1ohvZvqbntb_7afT4p2OzbFIJjJWiy9Q/edit?c=0&w=1
BTW what's your phone's manufacturing date? were you using Magisk or SuHide?
Dadud said:
I have this same problem. flashed MegaPixel6P, tried using the camera, and then my phone shut off and just keeps rebooting. i think /data and /system are corrupted. any attempt to nandroid backup or restore fails and causes TWRP to reboot.
Click to expand...
Click to collapse
If you can get to TWRP, you can just reflash via fastboot (or use NRT). You may be able to apply your TWRP backup afterwards if it is not corrupted.
As for OP, if the bootloader is locked, and "Allow OEM Unlock" is toggled off, your options are slim to none. If this setting was enabled before upgrading then it is still enabled. If it was not, you cannot unlock the bootloader.
v12xke said:
If you can get to TWRP, you can just reflash via fastboot (or use NRT). You may be able to apply your TWRP backup afterwards if it is not corrupted.
As for OP, if the bootloader is locked, and "Allow OEM Unlock" is toggled off, your options are slim to none. If this setting was enabled before upgrading then it is still enabled. If it was not, you cannot unlock the bootloader.
Click to expand...
Click to collapse
Ive tried literally every fix, its dead jim.
Dadud said:
Ive tried literally every fix, its dead jim.
Click to expand...
Click to collapse
Have you tried FORMATTING boot, system, data & vendor and then reflash? Format, not erase/wipe. Move your TWRP backup off to PC and try that. If you are rusty in ADB/Fastboot, then use NRT to do same in advanced tools. If you have a working recovery and your bootloader is unlocked, I would not give up yet. Good luck!
Dadud said:
I have this same problem. flashed MegaPixel6P, tried using the camera, and then my phone shut off and just keeps rebooting. i think /data and /system are corrupted. any attempt to nandroid backup or restore fails and causes TWRP to reboot.
Click to expand...
Click to collapse
Yeah your problem is a bit different that others and it's worth investigating.
To verify your complete emmc, you could try this command in twrp -> advanced settings -> terminal.
dd if=/dev/block/mmcblk0 of=/dev/null
Basically doing a read test by copying the complete mmc to the void. It should give you a status at the end that you can post here.
By the way, the recommended factory flashing is by using flash-all script that is inside the factory image itself. And you need the latests android SDK.
rchtk said:
Yeah your problem is a bit different that others and it's worth investigating.
To verify your complete emmc, you could try this command in twrp -> advanced settings -> terminal.
dd if=/dev/block/mmcblk0 of=/dev/null
Basically doing a read test by copying the complete mmc to the void. It should give you a status at the end that you can post here.
By the way, the recommended factory flashing is by using flash-all script that is inside the factory image itself. And you need the latests android SDK.
Click to expand...
Click to collapse
nope. i enter the command and it does nothing for about a minute before turning itself off
also, im not some complete n00b, so trust me when i say i've tried everything. any time i restore a backup, once it starts applying just /data or /system it'll shut off and bootloop without finishing.
Dadud said:
nope. i enter the command and it does nothing for about a minute before turning itself off
also, im not some complete n00b, so trust me when i say i've tried everything. any time i restore a backup, once it starts applying just /data or /system it'll shut off and bootloop without finishing.
Click to expand...
Click to collapse
You never know the level of the person you're talking about eh. Just tought you hadn't tried the dd.
So dd shutting down before completing wasn't expected but now if I read again your posts, you said doing a photo shuts down the phone and that's quite typical of power related problems. Sh*t.
Could be the battery not holding discharge. Can the device stay in twrp with screen off? Did you try to let it fully discharge and charge it with a slow charge?
There are a lot of information in /sys/ or dmesg but it won't solve your issue.
Still under warranty?
Dadud said:
nope. i enter the command and it does nothing for about a minute before turning itself off
also, im not some complete n00b, so trust me when i say i've tried everything. any time i restore a backup, once it starts applying just /data or /system it'll shut off and bootloop without finishing.
Click to expand...
Click to collapse
Forget restoring your backup for now. You're not a noob, so transfer your TWRP backup to PC, then FORMAT each partition first, including userdata and then reflash using a Google Imagehere. Ensure you are using the latest version of ADB/Fastboot. You didn't mention you have already attempted to Fastboot flash the NMF26F image. What was your result then? The reason I'm asking is that the Google script erases the partitions- does not format, but running the script will tell you which partition failed during writing.
Huawei Customer Service!!
Had the exact same problem creep up on me this past weekend. I ended up calling Huawei and they are doing a free warranty repair on my phone even though I'm almost two months out of warranty.
Make sure you are on SDK 25, I had the problem synonymous. I have been hunted at Huawei and only when I had already given it I realized that I was not on SDK 25 and I know of some others that was the reason with most.
Whether it was the reason with me, I know tomorrow, the device is back and can be picked up,
Tylog said:
Make sure you are on SDK 25...
Click to expand...
Click to collapse
Yes, the latest ADB / Fastboot is required. The rest of the SDK is not mandatory. You can get a minimalist ADB-Fastboot-Driver install from an XDA dev here.
Also, TWRP updated for Angler recently here. This update solved a persistent backup problem I had with the previous v3.0.2-2
bought it second hand, and the previous owner bought it at launch, so im just a month or so out of warranty. im trying to get the original receipt to attempt to RMA it. Huawei's IMEI lookup says its under warranty till april 4th next year.
Tylog said:
Make sure you are on SDK 25, I had the problem synonymous. I have been hunted at Huawei and only when I had already given it I realized that I was not on SDK 25 and I know of some others that was the reason with most.
Whether it was the reason with me, I know tomorrow, the device is back and can be picked up,
Click to expand...
Click to collapse
Was your phone stuck in Bootloop of death as well? How did you fix it? What do think causes this issue and how can it be avoided?
Hello
I decided to start from scratch and installed latest stock rom with mi flash. The tool reported successful but I ended up in a boot loop. Somehow it failed when the screen came up with 'data encryption....'. I flashed it again ad the phone only vibrated when power on. I hat to do the restore point method to gain EDL mode. I flashed an older firmware. Now the screen stays black. I'm able to boot into fastboot, unlock the bootloader and install TWRP. But the screen is just blank/black.
I have a feeling it haves something to do with emmc_appsboot.mbn or boot.emmc.win
When I flash boot.emmc.win with fastboot on Slot A (I tried both slots) at least the LED turns on when the device is plugged on a USB cable. But nothing more........
I still have my backups, created by TWRP. I don't know this is in some way helpful.
I find the tool TWRP Backup Tool. It seems I could restore a TWRP backup from there. But which file should I use? My backup is a folder. There isn't any .zip or .img file.
Some ideas?
Same here
i can flash with edl mode
flash nougat rom stock for oem unlock
flash twrp ok
flash rom black screen:crying:
laugeek57 said:
Same here
i can flash with edl mode
flash nougat rom stock for oem unlock
flash twrp ok
flash rom black screen:crying:
Click to expand...
Click to collapse
can you do me a favour please? After the rom I flashed last night (yes, I guess it was a Nougat version) I was able to enter edl mode and unlock the bootloader. Today I tried other ROMs. Now, I forgot which Nougat version exactly worked for unlock boot loader. If you can post the exact version or a link would be great.
I don't think it's a hardware fault. I guess we need only the correct boot files. It should be possible to extract those files from a TWRP backup. But I can't find any hint how to do it.
If you find something that helps. please post it here. I'll do the same....
XtraWater said:
can you do me a favour please? After the rom I flashed last night (yes, I guess it was a Nougat version) I was able to enter edl mode and unlock the bootloader. Today I tried other ROMs. Now, I forgot which Nougat version exactly worked for unlock boot loader. If you can post the exact version or a link would be great.
I don't think it's a hardware fault. I guess we need only the correct boot files. It should be possible to extract those files from a TWRP backup. But I can't find any hint how to do it.
If you find something that helps. please post it here. I'll do the same....
Click to expand...
Click to collapse
Android 7.1.2 [N2G47H.7.8.23]
this version for unlocked bootloader
but after i'm always bootloops it's crazy
laugeek57 said:
Android 7.1.2 [N2G47H.7.8.23]
this version for unlocked bootloader
but after i'm always bootloops it's crazy
Click to expand...
Click to collapse
Thank you. I'll try it again. I also got bootloops, but the screen never turned on. As mentioed above, I was even able to install TWRP. And it booted into TWRP. But without a screen....
XtraWater said:
Thank you. I'll try it again. I also got bootloops, but the screen never turned on. As mentioed above, I was even able to install TWRP. And it booted into TWRP. But without a screen....
Click to expand...
Click to collapse
I try other version flash with twrp but what version for... good luck
VICTORY !!!
Flash Pixel Experience 12/17 with modem december my mi a1 debricked lol
but now i lost imei ....plus jamais xiaomi !!!
laugeek57 said:
I try other version flash with twrp but what version for... good luck
VICTORY !!!
Flash Pixel Experience 12/17 with modem december my mi a1 debricked lol
but now i lost imei ....plus jamais xiaomi !!!
Click to expand...
Click to collapse
How did you flash the OS? Because My screen is dark, so I can't see anything.
XtraWater said:
How did you flash the OS? Because My screen is dark, so I can't see anything.
Click to expand...
Click to collapse
If dark screen flash december modem but becarrefull i lost imei after
laugeek57 said:
If dark screen flash december modem but becarrefull i lost imei after
Click to expand...
Click to collapse
Thank you. I installed december rom. But screen is still black. Probably hardware defect.
XtraWater said:
Yes, the bootloader is unlocked. I'm able to enter into fastboot. From there I can flash TWRP and boot into recovery. I installed even Magisk. It seems everything to work, but the screen. I was very careful when I did the testpoint method.
Here's the result of the fastboot oem device-info:
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.047s]
Finished. Total time: 0.047s
Do you think there is still a chance to fix the device? I thought about to send the device back where I bought it. The device isn't even 2 week old. But I doubt the dealer will grant me warranty since I opened the device.
Edit: THe cellphone starts normally me thinks. If I want to boot into bootloader I have to press power and vol -
I run the TOOL ALL IN ONE which shows me immediately when a Fastboot device is detected.
Click to expand...
Click to collapse
What ROM do you install through the TWRP? Have you tried only to install a rom, without Magisk or GAPPS and wait if it boots properly?
samuro625 said:
What ROM do you install through the TWRP? Have you tried only to install a rom, without Magisk or GAPPS and wait if it boots properly?
Click to expand...
Click to collapse
After I was in bootloop (with screen) I wasn't able to unlock bootloader. So I used the Mi Flash tool. I tried different (at least 6 or 8 )versions from this site: https://xiaomifirmware.com/roms/download-official-roms-xiaomi-mi-a1/
After flashing the roms, the phone only vibrated when tried to boot. It repeatedly vibrated when connected to the USB cable and charger.
Only one rom allowed me to enter fastboot and unlock the bootloader. Android 7.1.2 Nougat (N2G47H.7.8.23) ( https://xiaomifirmware.com/download/5117/ )
That's the rom which is currently on my phone.
I tried once to install the latest Oreo 8.1 with TWRP. Since my screen is black, I used the TOOL ALL IN ONE. The flash process was successful. But then again only vibration when try to boot.
Actually, in all those versions GAPPS or Magisk isn't included.
Just to mention; my Mi A1 is a MDG2. Not sure if that matters.
Without the screen, I'm kinda limited regarding to TWRP.
EDIT: I never did a backup by ADB. But I did several with TWRP. I wanted to recover one of them. But methinks, that's not possible with the TOOL ALL IN ONE.
Edit 2: I also made a TWRP backup from the Stock Oreo 8.1 version. It was the state on which the phone was delivered. I only did installation wizard like login to google account.....
The folder contains files like data.ext4.win000, data.ext4.win001, system.ext4.win000, system.ext4.win001. But once again, I don't know if this is helpful in any way.
XtraWater said:
(...)I wasn't able to unlock bootloader. (...) Only one rom allowed me to enter fastboot and unlock the bootloader. Android 7.1.2 Nougat (N2G47H.7.8.23) ( https://xiaomifirmware.com/download/5117/ ) That's the rom which is currently on my phone.
Click to expand...
Click to collapse
OK, we already know that it is with bootloader unlocked and in Nougat. That tells us 2 things: 1) It will not accept Stock Firmware until it blocks the bootloader and for now, that is not recommended. 2) You have to install a Nougat CustomROM, because to install Oreo you need to update the firmware.
XtraWater said:
I tried once to install the latest Oreo 8.1 with TWRP. Since my screen is black, I used the TOOL ALL IN ONE. The flash process was successful. But then again only vibration when try to boot.
Click to expand...
Click to collapse
Since the use of the AIO tool has not been effective, I would consider using the native firmware's own commands, especially flash_all.bat, which in theory leaves the cell phone as a factory and does not relock the bootloader.
Another aspect to keep in mind is that before decompressing the firmware file, rename it to a short one. It happened to me that a very long folder name was generated and the flashing was not completed.
Try this process with firmware N2G47H.7.8.23, using the instructions on the page that you mention, in the section "How to install Stock ROM (fastboot) on Xiaomi Mi A1"
XtraWater said:
Edit 2: I also made a TWRP backup from the Stock Oreo 8.1 version. It was the state on which the phone was delivered. I only did installation wizard like login to google account.....
The folder contains files like data.ext4.win000, data.ext4.win001, system.ext4.win000, system.ext4.win001. But once again, I don't know if this is helpful in any way.
Click to expand...
Click to collapse
For now these files are not useful, but do not erase them.
samuro625 said:
OK, we already know that it is with bootloader unlocked and in Nougat. That tells us 2 things: 1) It will not accept Stock Firmware until it blocks the bootloader and for now, that is not recommended. 2) You have to install a Nougat CustomROM, because to install Oreo you need to update the firmware.
Since the use of the AIO tool has not been effective, I would consider using the native firmware's own commands, especially flash_all.bat, which in theory leaves the cell phone as a factory and does not relock the bootloader.
Another aspect to keep in mind is that before decompressing the firmware file, rename it to a short one. It happened to me that a very long folder name was generated and the flashing was not completed.
Try this process with firmware N2G47H.7.8.23, using the instructions on the page that you mention, in the section "How to install Stock ROM (fastboot) on Xiaomi Mi A1"
For now these files are not useful, but do not erase them.
Click to expand...
Click to collapse
Ok, I did shorten the folder and file. The process flash_all.bat by itself was successful and I guess the phone rebooted. But still no screen. Still dark.
You mentioned to install a Nougat custom rom. Would you suggest a particular one?
XtraWater said:
Ok, I did shorten the folder and file. The process flash_all.bat by itself was successful and I guess the phone rebooted. But still no screen. Still dark.
Click to expand...
Click to collapse
I have a question: what images are seen on the screen? The logos of Xiaomi, the TWRP, others?
XtraWater said:
You mentioned to install a Nougat custom rom. Would you suggest a particular one?
Click to expand...
Click to collapse
Anyone who is allowed to install by TWRP, following the developer's instructions.
samuro625 said:
I have a question: what images are seen on the screen? The logos of Xiaomi, the TWRP, others?
Click to expand...
Click to collapse
Nothing. Absolute nothing. Even no LED when charging. The screen is just dead.
XtraWater said:
Nothing. Absolute nothing. Even no LED when charging. The screen is just dead.
Click to expand...
Click to collapse
So, in this case, there is physical damage that I can not deal with. You could try using the warranty, but you should trust that the marks on the screws are not noticed.
samuro625 said:
So, in this case, there is physical damage that I can not deal with. You could try using the warranty, but you should trust that the marks on the screws are not noticed.
Click to expand...
Click to collapse
They will see it. I tried with a common screwdriver. Since this didn't work, I bought a kit.
Well, bad luck.
However, thank you very much for your effort. That was very kind.
samuro625 said:
So, in this case, there is physical damage that I can not deal with. You could try using the warranty, but you should trust that the marks on the screws are not noticed.
Click to expand...
Click to collapse
A last question. If they replace the phone, I know, there chances are zero. Would I face the same issue if I want resurrection remix with the phone sound? Would I have to flash that modem.img?
If so, that's just not worth. It all started with that problem. Everything worked perfect but the phone.
XtraWater said:
A last question. If they replace the phone, I know, there chances are zero. Would I face the same issue if I want resurrection remix with the phone sound? Would I have to flash that modem.img?
If so, that's just not worth. It all started with that problem. Everything worked perfect but the phone.
Click to expand...
Click to collapse
Well, the truth, I never had any audio problem with calls with Resurrection Remix, and this rom I have used it in more than 6 phones of different manufacturers.
In my case, the problem of the calls was presented by flashing the modem of the version 8.1 of November, but downgrading to 8.0 was resolved.
Good luck with the cell phone, and it's a pity that it has been damaged.
It is advisable to learn to use the ADB and fastboot tools directly, rather than the AIOs.
Edit: May be this post can be usefull for you: https://forum.xda-developers.com/mi-a1/help/hard-bricked-phone-please-help-t3758606
samuro625 said:
Well, the truth, I never had any audio problem with calls with Resurrection Remix, and this rom I have used it in more than 6 phones of different manufacturers.
In my case, the problem of the calls was presented by flashing the modem of the version 8.1 of November, but downgrading to 8.0 was resolved.
Good luck with the cell phone, and it's a pity that it has been damaged.
It is advisable to learn to use the ADB and fastboot tools directly, rather than the AIOs.
Edit: May be this post can be usefull for you: https://forum.xda-developers.com/mi-a1/help/hard-bricked-phone-please-help-t3758606
Click to expand...
Click to collapse
Hello
I didn't give up so far. Something interesting happened.
I did the follow command: fastboot flash boot.emmc.win
The flash boot.emmc.win I extracted from my TWRP backup. Now, the phone rebooted and I hear a android notification. The charging LED is working too and the backlights of the buttons. When I touch the screen, the backlight of the buttons goes on. It looks like the phone is running. But, the screen is still off.
When I press the power button short, I hear the sound which indicates the screen goes off.
Tell me if I'm wrong, but with that behavior I think it isn't a hardware damage. Since still is Nougat installed, I might need a boot.emmc.win for Nougat?
We could be very close to fix the software.
EDIT: I used: fastboot boot boot.emmc.win
If I understand this correct, that way it is only temporary. So I tried:
fastboot flash boot_a boot.emmc.win
and
fastboot flash boot_b boot.emmc.win
With that, nothing happens. So, now again fastboot boot boot.emmc.win
Phone has restarted. I hear a sound. When touch the screen backligh of buttons goes on. I'm in a menu I guess. The installation wizard. I also hear the sound when I press something on the installation wizzard.
At least, that's new. Before there was nothing.
Edit 2: Might it be related to efs1.emmc.win and efs2.emmc.win ?
Edit 3: That's crazy. I touched the screen randomly and activated a 'Screen Reader' for blind people
Hi,
I was really unhappy with Pie and tried to prepare my device for Oreo downgrade.
What I did was
- unlock bootloader
- tried to install TWRP
- mixed something up in that processs
- realized TWRP cannot be installed apparently on Pie right now
- MiFlash seems to be not working as well when trying to install stock rom (says flashing but nothing happens)
Well Pie is running right now, but when trying to lock the bootloader again for future updates, the phones is only showing a black screen.
After that I am trying to unlock bootloader again (fastboot oem unlock) and everything works again, except when I try to boot into recovery ("the system is destroyed" or something like that).
Trying to "hotboot" into TWRP currently is also not working, "unable to mount..." and after that automatically reboots into the system itself.
Any idea how I can either put a standard Pie installation with working recovery and locked bootloader on?
Or how I can maybe install Oreo instead? As I said, the MiFlash tool doesn't do anything (tells me "flashing" but actually doesn't do anything).
Thanks for your help!
cyrrel said:
Hi,
I was really unhappy with Pie and tried to prepare my device for Oreo downgrade.
What I did was
- unlock bootloader
- tried to install TWRP
- mixed something up in that processs
- realized TWRP cannot be installed apparently on Pie right now
- MiFlash seems to be not working as well when trying to install stock rom (says flashing but nothing happens)
Well Pie is running right now, but when trying to lock the bootloader again for future updates, the phones is only showing a black screen.
After that I am trying to unlock bootloader again (fastboot oem unlock) and everything works again, except when I try to boot into recovery ("the system is destroyed" or something like that).
Trying to "hotboot" into TWRP currently is also not working, "unable to mount..." and after that automatically reboots into the system itself.
Any idea how I can either put a standard Pie installation with working recovery and locked bootloader on?
Or how I can maybe install Oreo instead? As I said, the MiFlash tool doesn't do anything (tells me "flashing" but actually doesn't do anything).
Thanks for your help!
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a1/development/treble-twrp-installer-treble-manager-t3793637
Hi,
I somehow managed to put 8.1 on and everything is back to normal.
Thanks
cyrrel said:
Hi,
I somehow managed to put 8.1 on and everything is back to normal.
Thanks
Click to expand...
Click to collapse
can you explain us the procedures that you have followed to downgrade. It would be really helpful. i have tried this
method but it didn't work for me. i am facing IMEI 0/no signal issues using this method.
Thanks
well I have done a lot of stuff that made my phone not working anymore because using a wrong .img file and didn'T understand the tutorial (same link you have provided) fully.
But at the end it was quite close to the link you have sent, the MiFlash tool I needed for example to try like 10 times per step until it worked, maybe a bad cable - I don't know.
But finally it was working, after March update without network signal, but with /boot & /efs partitions and Nov fastboot image, it was working.
If you need any more detail for a specific step, you can of course ask and I can check if there was anything special I can remember
cyrrel said:
well I have done a lot of stuff that made my phone not working anymore because using a wrong .img file and didn'T understand the tutorial (same link you have provided) fully.
But at the end it was quite close to the link you have sent, the MiFlash tool I needed for example to try like 10 times per step until it worked, maybe a bad cable - I don't know.
But finally it was working, after March update without network signal, but with /boot & /efs partitions and Nov fastboot image, it was working.
If you need any more detail for a specific step, you can of course ask and I can check if there was anything special I can remember
Click to expand...
Click to collapse
Are your imei & mac same as original? won't the imei/mac get affected by restoring someone else efs?
I don't know about mac, but imei is ok