Related
Hey here goes my nexus 7 grouper has some how got corrupted and the only thing that is still working is fastboot, However the usual recovery using the google stock roms i ether get signature mismatch or unknown error code (really useful error code).
Currently running bootloader 4.23 and was using stock android 4.4.3 before it all went oh so wrong.
I have tried flashing it back to stock with the nexus root toolkit and the flash batch file provided by google and both have failed.
Is there a way to force a flash to ignore all signatures and i will go back to an earlier rom from google that worked properly?
or do i need a new tablet as Asus support has been less than useful?
Cheers
Support
ScoTTisH-GingeR said:
Hey here goes my nexus 7 grouper has some how got corrupted and the only thing that is still working is fastboot, However the usual recovery using the google stock roms i ether get signature mismatch or unknown error code (really useful error code).
Currently running bootloader 4.23 and was using stock android 4.4.3 before it all went oh so wrong.
I have tried flashing it back to stock with the nexus root toolkit and the flash batch file provided by google and both have failed.
Is there a way to force a flash to ignore all signatures and i will go back to an earlier rom from google that worked properly?
or do i need a new tablet as Asus support has been less than useful?
Cheers
Click to expand...
Click to collapse
Hello,
Hvae you tried flashing a recovery though fastboot? Once you have done this you should be able to sideload a new rom and BAM your done.
See here for fastboot flashing a new recovery: http://teamw.in/project/twrp2/103
See here for sideloading in recovery: http://teamw.in/ADBSideload
[email protected] said:
Hello,
Hvae you tried flashing a recovery though fastboot? Once you have done this you should be able to sideload a new rom and BAM your done.
See here for fastboot flashing a new recovery
See here for sideloading in recovery:
Hey Scott cheers for the reply here is the result of the attempting to flash twrp.
C:\nexus\4.4.4>fastboot flash recovery openrecovery-twrp-2.7.1.1-grouper.img
sending 'recovery' (8502 KB)...
OKAY [ 1.039s]
writing 'recovery'...
FAILED (remote: (FileWriteFailed))
finished. total time: 3.863s
Any more ideas or am i binning my nexus?
Click to expand...
Click to collapse
ScoTTisH-GingeR said:
Hey here goes my nexus 7 grouper has some how got corrupted and the only thing that is still working is fastboot, However the usual recovery using the google stock roms i ether get signature mismatch or unknown error code (really useful error code).
Currently running bootloader 4.23 and was using stock android 4.4.3 before it all went oh so wrong.
I have tried flashing it back to stock with the nexus root toolkit and the flash batch file provided by google and both have failed.
Hello,
My August 2012 Nexus 7 got same issue.
Boot loop up to animated circles or Android update.
Rooted. CWM recovery. Stock ROM 4.4.3
General remark/ the device was getting really slow in spite of regular use of Lagfix.
Fastboot OK. That is in fact the only way to power off the device.
Wipe Data / Factory reset had no effect on bootloop.
Errors trying to flash official Factory image through adb: example " recovery.sig files not found". I tried to flash them individually
I tried the Nexus Toolkit: Error trying to load a factory image. Error trying to return to stock recovery.
I suspect a memory issue.
Finally I just return this morning the device to ASUS France, after requesting a Return Agreement.
No more warranty; I wonder if the resulting cost are worst this action if tablet is not reparable.
I am really upset.
Click to expand...
Click to collapse
Hello,
Have you tried the steps to flash a system imagem, all you need is to have access to fastboot. Please visit: https://developers.google.com/android/nexus/images for instructions on how to do this.
I hope these steps help, If you need further assistance you can email me at [email protected]. Be sure to place case number N140811561 in the subject line for reference.
Regards,
Scott
ASUS Customer Loyalty
Motherboard issue
[email protected] said:
Hello,
Have you tried the steps to flash a system imagem, all you need is to have access to fastboot. Please visit: https://developers.google.com/android/nexus/images for instructions on how to do this.
I hope these steps help, If you need further assistance you can email me at [email protected]. Be sure to place case number N140811561 in the subject line for reference.
Regards,
Scott
ASUS Customer Loyalty
Click to expand...
Click to collapse
-----------------------------------------------------------------------------------------------------------
I just got the answer from Ename, ASUS repair contractor in France.
Motherboard got problems. Need replacement.
Total cost 192 €.
Basically I have better to buy a new one.
That is really bitter after just 2 years .....!!!!!
Is the 2013 model more robust?
marcelin99 said:
-----------------------------------------------------------------------------------------------------------
I just got the answer from Ename, ASUS repair contractor in France.
Motherboard got problems. Need replacement.
Total cost 192 €.
Basically I have better to buy a new one.
That is really bitter after just 2 years .....!!!!!
Is the 2013 model more robust?
Click to expand...
Click to collapse
Hello,
The Nexus 7 21013 is slightly lighter, has a better resolution (1920 x 1200 pixels), adds a rear camera and sports the Qualcomm Snapdragon S4 Pro APQ8064 with 2048 MB RAM. So it is a nice increase in the specs. With a your repair cost of 192 it might be better to consider upgrading your Nexus experience. If you need further support feel free to email me at [email protected] with case number in the N140820223 subject line.
Regards,
Scott
ASUS Customer Loyalty
For anyone interested here is the firmware image for Verizon Nexus 6 [5.1] [ LMY47E].
VRZ_XT1103_5.1_SHAMU_LMY47E_release-keys_subsidy-default_CFC.xml.zip
http://www.filefactory.com/file/12c...Y47E_release-keys_subsidy-default_CFC.xml.zip
Nexus 6 Firmware Folder
http://www.filefactory.com/folder/74e3c3d68254b075
This where I upload my stuff so sorry if I offend anyone for doing so.
So the difference in between whats out there and this is? I'm curious as the build is different.
coldconfession13 said:
So the difference in between whats out there and this is? I'm curious as the build is different.
Click to expand...
Click to collapse
Not sure what's actually different but the build number is different, LMY47D vs LMY47E.
Could this be flashed with twrp without losing custom recovery?
Sent from my Nexus 6 using XDA Free mobile app
Hopefully we will find out if there are any significant changes or additions. I really hope that I do not need to follow a Verizon firmware through the life of this phone. I hope that there is nothing meaningful in the E version.
Not positive as I am just downloading it, but pretty sure it is the factory image for the Nexus 6 for VZW so I imagine it will remove root and probably custom recovery.
But the nice thing about the Nexus 6 is that you are NOT tied to your carrier's firmware/ROM's for it. Unlike previous phones, there are only two versions, US and International. So we don't have to worry if 'x ROM' is for the T-Mobile version, the Sprint version, etc., etc.
Well no worries this all but confirms vzw is rootable and unlockable
Anyone Flash this yet?
Has anyone flashed this yet...very interested how you went about it and what the results are.....thx
Is there a rooted version??
Parsing the image filename
coldconfession13 said:
So the difference in between whats out there and this is? I'm curious as the build is different.
Click to expand...
Click to collapse
Also waiting another few hours for download to complete. In the mean time, just parsing all the attributes of the file name:
LMY47E: Newer than LMY47D, which is explicitly called 5.1.0 on the Nexus Factory Image page (not the usual numbering convention, which would be 5.1; possibly foreshadowing that they know 5.1.1 is hot on its heels)
release-keys: signed by Google
subsidy-default: Includes parameters that resets the SIM Lock on the radio to "default" status, which we assume is factory-unlocked.
CFC: any idea what means?
I would assume this also gives us an image for the /oem partition
Judging by the name this was made on the same day as the image on Google's website, so it is very unlikely that there are major changes.
Nexus 6 subsidy lock config
@autoprime:
1. Does the contents of the included slcf_rev_b_default_v1.0.nvm look like plain QMI commands to you?
2. Do you still have a user-friendly one-click tool that can send DFS commands to a device in diag mode?
How to Flash
Maybe a dumb question... but can this be TWRP flashed (I thinking no) or is there some other method? I was thinking this was a standard recovery image that could be flashed in stock recovery?? Other than that, I am not sure... if anyone has success flashing let me know!
edit...
duh.... ok sorry... my bad for not looking into the zip.... I see the flash all .bat
mahst68 said:
Maybe a dumb question... but can this be TWRP flashed (I thinking no) or is there some other method? I was thinking this was a standard recovery image that could be flashed in stock recovery?? Other than that, I am not sure... if anyone has success flashing let me know!
Click to expand...
Click to collapse
I believe you will need the Motorola Fastboot tool (mfastboot) to flash this in the motoboot mode. You can get it from the MotoDev site, or search on the forums. Note that this is NOT the same as the standard fastboot that ships with the Android SDK (which will also work with the Nexus 6, but not with this particular zip file).
Did It!!!
DA6030 said:
I believe you will need the Motorola Fastboot tool (mfastboot) to flash this in the motoboot mode. You can get it from the MotoDev site, or search on the forums. Note that this is NOT the same as the standard fastboot that ships with the Android SDK (which will also work with the Nexus 6, but not with this particular zip file).
Click to expand...
Click to collapse
As described, used mfastboot... flashed each individual image file based on the steps in the flashfile.xml!!! Booted up everything real nice.... download myverizon and voicemail as soon as I went through initial setup.... rooting now!!! :good:
bootloader remained unlocked the whole time!!!!
mahst68 said:
As described, used mfastboot... flashed each individual image file based on the steps in the flashfile.xml!!! Booted up everything real nice.... download myverizon and voicemail as soon as I went through initial setup.... rooting now!!! :good:
bootloader remained unlocked the whole time!!!!
Click to expand...
Click to collapse
Does the firmware seem configured for VZW? VZW ringtones and boot animation and the like? Or does it appear like something that Google will drop on us in the near future? I wonder if it will ever hit the factory images page?
elreydenj said:
Does the firmware seem configured for VZW? VZW ringtones and boot animation and the like? Or does it appear like something that Google will drop on us in the near future? I wonder if it will ever hit the factory images page?
Click to expand...
Click to collapse
only thing Verizon really are the 2 app downloads.... everything else is the same... not boot animations nothing. Root and TWRP setup worked fine as well.... Not going to relock bootloader though... I know the horror stories of Hard Bricks.... Not going to take off force encrypt either.... was having trouble with the phone wanting to go bootloopy with the regular image from google when I made it force before... I will let everyone know bugs and post some pictures as well once I set it up fully!! :highfive:
mahst68 said:
only thing Verizon really are the 2 app downloads.... everything else is the same... not boot animations nothing. Root and TWRP setup worked fine as well.... Not going to relock bootloader though... I know the horror stories of Hard Bricks.... Not going to take off force encrypt either.... was having trouble with the phone wanting to go bootloopy with the regular image from google when I made it force before... I will let everyone know bugs and post some pictures as well once I set it up fully!! :highfive:
Click to expand...
Click to collapse
Question: I think I may have been under the same circumstances as you. I am rooted, with TWRP, and bootloader unlocked. I am however, running a custom rom (5.0.1 encrypted). I won't be relocking the bootloader. What steps (if you are able to provide them) should I take to achieve 5.1 with bootloader still locked and then root and install TWRP. (Please keep in mind I a have not had a Nexus device since the very first one).
Edit: I am on VZW network but Google Play Store Nexus 6.
TIA
Will do... I am still setting up the phone. Once I complete it and make sure it works fine for a little bit then I'll post. Don't want to cause any issues that might lead to someone bricking their phone
Initial observations
DA6030 said:
LMY47E: Newer than LMY47D, which is explicitly called 5.1.0 on the Nexus Factory Image page (not the usual numbering convention, which would be 5.1; possibly foreshadowing that they know 5.1.1 is hot on its heels)
Click to expand...
Click to collapse
System partition looks complete, but I won't have time to do a diff between the two until next week. But by then, we might have an official changelog.
DA6030 said:
subsidy-default: Implies there's something within this file that sets the SIM Lock parameters on the radio? Extracting that could be very interesting to AT&T and Sprint customers.
Click to expand...
Click to collapse
I don't have an AT&T device to test, but applying this file certainly attempts to set the SIM lock to it's default factory-unlocked state. But it's also possible the radio firmware could reject the unlock commands if it has been previously locked by a carrier. Only way to know is to test.
DA6030 said:
I would assume this also gives us an image for the /oem partition
Click to expand...
Click to collapse
There is an oem partition file within the zip, but it's literally just the string "Hi, Fly Guy". Just open oem.img with a text editor to see it. I cannot imagine that is a valid ext img file, so I'm shocked that it was able to be flashed. If so, that would suggest that the Verizon devices will ship with no unique customizations (e.g., bootanimation, ringtones, that cannot be removed without root), and has a sense of humor.
---------- Post added at 10:39 AM ---------- Previous post was at 10:32 AM ----------
mahst68 said:
As described, used mfastboot... flashed each individual image file based on the steps in the flashfile.xml!!!
Click to expand...
Click to collapse
@mahst68, did you flash only the image files, or also the subsidy_lock_config file (slcf....nvm)? What mfastboot command did you use to send the slcf? What was the response did you get back from that command? And when you flashed the oem.img what response did you get back?
Hi All.
I am in a bit of a situation right now.
My video recording app filled up internal storage and corrupted system files (because i forgot to point it to my external SD card).
This caused a boot loop, so I went into recovery and (regrettably) wiped the internal storage. Now when I try to flash or install a new (stock) rom, none will work. I have tried sideloading, installing through (TWRP) recovery and wiping the cache multiple times as I comb through the internet for files like the system.img, boot.img, and droidboot.img, to no avail.
TLDR; I need either a backup of someone elses Zenfone 2 ZE500KL, or the system files required to get me up and running, otherwise I have a brick on my hands.
Thanks for any help
Matt
Unlock bootloader, flash the official firmware, I think you can find it on the internet. Have you tried that? You can even get a deodexed rom from here and extract files needed and flash them...
Sent from my Tab3 Lite 7.0 using XDA Labs
Yep, found it on the official asus site...
Sent from my Tab3 Lite 7.0 using XDA Labs
jocamucko said:
Yep, found it on the official asus site...
Sent from my Tab3 Lite 7.0 using XDA Labs
Click to expand...
Click to collapse
Yeah, I have.
I've tried 2 different stock roms (Marshmallow, Lollipop) about 10 different times in both stock recovery and TWRP, mixing in some full wipes and just wiping the cache. I've been looking at a whole lot of tutorials on how to go back to stock, to no avail. I've tried modifying the rom so I no longer get the status 7 error (which I dont believe I should need to do) because I get signature verification errors on both my unmodified stock roms.
Sometimes it does do through the installation fine with the modified roms (in TWRP) and everything seems fine until I click reboot. On the screen it says that there is no OS installed, and when I do reboot to the OS I get stuck on the ASUS logo.
Not gonna give up, but a bit of a headache anyway.
I dont believe I have ever unlocked the bootloader, but how would I do that from outside Android?
Thanks in advance, Matt
mapooo said:
Yeah, I have.
I've tried 2 different stock roms (Marshmallow, Lollipop) about 10 different times in both stock recovery and TWRP, mixing in some full wipes and just wiping the cache. I've been looking at a whole lot of tutorials on how to go back to stock, to no avail. I've tried modifying the rom so I no longer get the status 7 error (which I dont believe I should need to do) because I get signature verification errors on both my unmodified stock roms.
Sometimes it does do through the installation fine with the modified roms (in TWRP) and everything seems fine until I click reboot. On the screen it says that there is no OS installed, and when I do reboot to the OS I get stuck on the ASUS logo.
Not gonna give up, but a bit of a headache anyway.
I dont believe I have ever unlocked the bootloader, but how would I do that from outside Android?
Thanks in advance, Matt
Click to expand...
Click to collapse
That's the problem, locked bootloader. forum.xda-developers.com/zenfone-2-laser/general/talking-ze500kl-g-unlock-bootloader-t3352776 there you got the old content, try it, it's from the outside of the phone. If your phone boots after that normaly, you got bootloader unlocked and your phone unbricked.
jocamucko said:
That's the problem, locked bootloader. forum.xda-developers.com/zenfone-2-laser/general/talking-ze500kl-g-unlock-bootloader-t3352776 there you got the old content, try it, it's from the outside of the phone. If your phone boots after that normaly, you got bootloader unlocked and your phone unbricked.
Click to expand...
Click to collapse
Thanks for your help.
My phone is now up and running.
Now I can close my 10 tabs on the Zenfone 2 lol.
mapooo said:
Thanks for your help.
My phone is now up and running.
Now I can close my 10 tabs on the Zenfone 2 lol.
Click to expand...
Click to collapse
It's nothing, that's the least I can do, put that phone to good use! :good:
Help !! you can give me all the files * img
Please
trongnguyen(vietnamese) said:
Help !! you can give me all the files * img
Please
Click to expand...
Click to collapse
Why do you need it? I can only assume that you haven't unlocked your bootloader. More info?
mapooo said:
Why do you need it? I can only assume that you haven't unlocked your bootloader. More info?
Click to expand...
Click to collapse
unbick
help
trongnguyen(vietnamese) said:
unbick
help
Click to expand...
Click to collapse
have you tried unlocking your bootloader?
mapooo said:
have you tried unlocking your bootloader?
Click to expand...
Click to collapse
I want file "img (system.img,boot.img...)
trongnguyen(vietnamese) said:
I want file "img (system.img,boot.img...)
Click to expand...
Click to collapse
I'm not sure if you understand, but it would be helpful if you told us your problem, rather than continuing to nag for an img file. I didn't need it to fix my phone, so without you giving us more info all I can say is try unlocking your bootloader.
I know you want an img file, but if life was that simple, you wouldn't need an img file in the first place *insert inception music*
This is my first post on XDA and i am in desperate need of help. I own a Asus Zenfone 6. Recently i tried unlocking bootloader and installing TWRP recovery so that i can flash a custom ROM. It went horribly wrong and i bricked my device. I managed to unbrick it and revert to Stock ROM which i also upgraded to LOLIPOP using adb sideload. I also managed to root it and have super user access. The problem is that i cannot install a TWRP or any other recovery. When i try to install a custom recovery i get and error " cannot install unsigned image on secure device" which probably suggests that the boot loader is locked. I ran the commands to unlock the boot loader and they ran successfully but i am not sure if the bootloader is locked or unlocked.
I tried running fastboot oem devices but i get an error " Unknown Oem command".
It was after hours of troubleshooting that i decided that i am OK with stock LOLIPOP rom as long as i have a rooted device. It was after sometime that i noticed that the camera wasn't working. Also the flashlight wasn't working. I uninstalled the updates and flashlight was working. However the camera just gives me a black screen for some time after which it quits with an error message " Camera is used by another application. Please reboot your device and try again". I uninstalled the updates for Camera and reverted to a previous version by also removing the camera application using super user access. However for an older version i get an error " Camera not found". I have also tried installing other camera applications but none seem to work even after making them a part of system. Currently flashlight works but only under an older version , as soon as i update it stops working. I decided to lock the boot loader again as it was just not worth it. However after running the commands and locking the bootloader i still cannot get the camera to work. I tried in safe mode and the camera won't work there either.
When i go to recovery i just have four options, there is no install from internal storage or SD card which suggests i am on stock recovery.
Currently i just want my camera to work. I am OK with the stock ROM and recovery as long as i have a rooted device. I have spent hours researching and nothing seems to work. I am in desperate need of help. Some of the friends suggested to try my luck here. I would be indebted as i dont want to purchase another device just because i screwed my camera. Also when i was under kitkat i ran the SIMI test and was getting an error 1667 and 1668 for both cameras. The test is failing under LOLIPOP as well. I dont think its a hardware issue or maybe i am wrong. Any help would be appreciated.
Thanks.
Not even a single reply. DISAPPOINTED!
You need to Lock Bootloader then reflash the rom (wipe all) to fix it. Custom ROMs sometimes cause camera not working cuz there are some devices that have different camera.... Next time, just make sure you Lock Bootloader => Flash Stock recovery => Wipe => Flash Stock ROM
qureshiburhan92 said:
Not even a single reply. DISAPPOINTED!
Click to expand...
Click to collapse
NOT EVEN A REPLY BACK
But yeah that sounds like a roller coaster.
Just picked up the Zenfone 6 to see what I could do with it, I'm going to try to flash the RR rom on here.
Just something I noticed though, I did some research myself, and a couple of sites like this one (https://zenfones.gajetzki.com/) say that you should root your original stock before doing anything. Now this wasn't a requirement at all in my experience for all other phones so I'm a bit skeptical. Anyway I thought that may help in some way.
Good luck!
LGenius3 said:
NOT EVEN A REPLY BACK
But yeah that sounds like a roller coaster.
Just picked up the Zenfone 6 to see what I could do with it, I'm going to try to flash the RR rom on here.
Just something I noticed though, I did some research myself, and a couple of sites like this one say that you should root your original stock before doing anything. Now this wasn't a requirement at all in my experience for all other phones so I'm a bit skeptical. Anyway I thought that may help in some way.
Good luck!
Click to expand...
Click to collapse
Hey buddy.
Thanks for the reply.
I am on stock rom as well as recovery and i have already gone through all these steps. Bootloader is locked as well as far as i can tell but still the camera doesn't seem to work. I am literally out of ideas now. Any help would be great!
Thanks
may zenfone 6 with stock rom 3.24.40.87 can't be unlock,pleas help me
qureshiburhan said:
Hey buddy.
Thanks for the reply.
I am on stock rom as well as recovery and i have already gone through all these steps. Bootloader is locked as well as far as i can tell but still the camera doesn't seem to work. I am literally out of ideas now. Any help would be great!
Thanks
Click to expand...
Click to collapse
Sorry for the late reply, but I'll try to help as much as I can. First things first, I know there are two different models of the Zenfone 6, the A600CG and the A601CG, but apparently this shouldn't make a difference, but it could have in this case, after all they must have different names for a reason. Also, the support for the Zenfone 6 is pretty terrible in terms of custom roms and the such, so you may even be better off with the stock experience, just root it and you'll have all the functionality you could ever dream of.
If you're still keen for the custom roms and stuff maybe check out this thread:
https://forum.xda-developers.com/zenfone-5/general/recovery-twrp-2-8-6-0-asus-zenfone-5-t3136263
Other than that, I guess Google is your friend, but so are we!
I haven't been able to hold onto my Zenfone 6, as it was a friends, so I no longer have it and never got the opportunity to have some fun with it, so I'm just going off my own experience with my HTC One M9, which is probably vastly different, but I suppose the process isn't too different. Nonetheless, I hope all goes well!
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