Related
I get to work this morning and noticed i have an update. the new version is 24.14.12.en.US. Currently on 24.14.11. which is 6.0. I'm gonna assume its safe to assume it's just a bug fix update or stability improvement update.
Anyone know anything about it yet?
bgoode2006 said:
I get to work this morning and noticed i have an update. the new version is 24.14.12.en.US. Currently on 24.14.11. which is 6.0. I'm gonna assume its safe to assume it's just a bug fix update or stability improvement update.
Anyone know anything about it yet?
Click to expand...
Click to collapse
I also recieved the update. I ran it and everything seems OK so far. I'll post back if I notice anything crazy or a battery drain.
Got it too just finished updating!
Does anyone know if it has a change log? I want to know if the MM radio bug has been fixed for the TMO users. Thanks in advance!
Sent from my XT1585 using Tapatalk
I'm having better performance and responsiveness since the update this morning. No Bluetooth audio stutters either, which were becoming more and more common for me.
Sent from my DROID Turbo 2
I just got it as well, I assumed bug fixes, but I can't seem to find any info on it online.
Just got it. Looks and feels the same. Anyone know what it is for?
why not 6.0.1
Sent from my XT1585 using XDA-Developers mobile app
I'd assume it's fixes to whatever bugs put the 6.0 rollout on hold.
mach01 said:
Just got it. Looks and feels the same. Anyone know what it is for?
Click to expand...
Click to collapse
Just a security patch and maybe a few minor tweaks.
PimpJim69 said:
Does anyone know if it has a change log? I want to know if the MM radio bug has been fixed for the TMO users. Thanks in advance!
Sent from my XT1585 using Tapatalk
Click to expand...
Click to collapse
Ambient Display has been removed in favor of Moto Display, and “Sleeping and Meeting” and “Driving and Places” modes have made their way onto the Moto Assist app.
classic757 said:
Just a security patch and maybe a few minor unnoticeable tweaks.
Click to expand...
Click to collapse
Ah ok. I was hoping for a bump to 6.0.1.
PimpJim69 said:
Does anyone know if it has a change log? I want to know if the MM radio bug has been fixed for the TMO users. Thanks in advance!
Sent from my XT1585 using Tapatalk
Click to expand...
Click to collapse
I don't think the MM radio bug has been fixed in the latest DT2 update. I say this because I am using my DT2 on T-Mobile and I get occasional loss of signal (complete signal goes out, no 4G, 3G, or anything. I usually have to reboot in order to get the signal back).
I know the DT2 does not have band 12 which could be an issue but there are lots of phones that don't have that particular radio band and still have no problem with keeping signal.
I am still trying to figure out if I can revert back to 5.1.1 and how to go about doing it.
PimpJim69 said:
I want to know if the MM radio bug has been fixed for the TMO users. Thanks in advance!
Sent from my XT1585 using Tapatalk
Click to expand...
Click to collapse
In an effort to try and resolve the 6.0 radio issue, I flashed the radio from the DT2 5.1.1 stock rom zip and it successfully flashed and works on the 6.0 stock rom but in the process it breaks wifi. When wifi is turned on it immediately toggles off. So that's not gonna work.
I may try once again to flash the entire (without flashing the gpt.bin partition) 5.1.1 stock rom zip through fastboot and see what happens. Don't know why I was able to flash the stock 5.1.1 radio but not the other parts of the zip.
Oh, and also just an FYI , if you want someone to know you have responded to their post just hit the reply button instead of posting a separate reply, that way they will be notified of your response instead of having to check in on xda occasionally to see if you have responded.
classic757 said:
In an effort to try and resolve the 6.0 radio issue, I flashed the radio from the DT2 5.1.1 stock rom zip and it successfully flashed and works on the 6.0 stock rom but in the process it breaks wifi. When wifi is turned on it immediately toggles off. So that's not gonna work.
I may try once again to flash the entire (without flashing the gpt.bin partition) 5.1.1 stock rom zip through fastboot and see what happens. Don't know why I was able to flash the stock 5.1.1 radio but not the other parts of the zip.
Oh, and also just an FYI , if you want someone to know you have responded to their post just hit the reply button instead of posting a separate reply, that way they will be notified of your response instead of having to check in on xda occasionally to see if you have responded.
Click to expand...
Click to collapse
Please show me how to flash the stock 5.1.1 radio
Sent from my XT1585 using Tapatalk
---------- Post added at 05:16 PM ---------- Previous post was at 05:01 PM ----------
They were saying that we have to delete a couple lines from the Xml file from the stock, but idk which lines...
Sent from my XT1585 using Tapatalk
PimpJim69 said:
Please show me how to flash the stock 5.1.1 radio
Sent from my XT1585 using Tapatalk
---------- Post added at 05:16 PM ---------- Previous post was at 05:01 PM ----------
They were saying that we have to delete a couple lines from the Xml file from the stock, but idk which lines...
Sent from my XT1585 using Tapatalk
Click to expand...
Click to collapse
Okay, first you need to have Developer Options enabled on your phone:
Settings>About Phone>Build Number-tap build number about 7 times and it will say you are now a developer>back to Settings>Developer Options>USB Debugging-turn it on and leave it on>exit Settings
Plug you phone into your PC-if you get a pop up asking if you want to allow usb debugging choose OK
You should get a popup asking if you want to allow rsa key fingerprint, choose OK
Now go to the zip folder of the stock 5.1.1 DT2 rom and extract it( I use 7-Zip extractor tool)to downloads folder on your PC. Now copy the entire contents of the rom into the platform tools folder on your PC (platform tools should be in your android sdk folder, copy the platform tools folder and paste it in your downloads folder on your PC).
Now open the platform tools folder and make sure you see a file called mfastboot(not fastboot but mfastboot) if you don't see it you can download it from here: https://drive.google.com/file/d/0B5jlU9JnLAZGbVU0UzJ3N3p4X2M/view?pref=2&pli=1
Extract the mfastboot folder into itself(right-click the mfastboot folder and then scroll up to 7-Zip and then choose "extract to mfastboot v2". Once extracted open the mfastboot folder and copy the contents into the platform tools folder). Now you will be able to issue mfastboot commands to your phone
Now (with your phone plugged in to your pc) hold the shift key and at the same time right click in an empty space in the platform tools folder and choose "open a command window". In the command window type (without quote marks) "adb devices". You should see your device serial number in the command window. If you don't you need to install on your pc either the Motorola Drivers or ADB drivers, or both. If you do see your serial number then type "adb reboot bootloader" and your phone will boot into fastboot mode.
Then type the command "fastboot devices". You should see your device serial number.
Then type "mfastboot.exe flash modem NON-HLOS.bin" You should see it flash and then say Okay after it is done.
Then type "mfastboot.exe erase modemst1"-you should get an Okay.
Then type "mfastboot.exe erase modemst2"-you should get an Okay.
Then type "mfastboot.exe flash fsg fsg.mbn"- you should get an Okay.
Then type "mfastboot.exe erase cache"-you should get an Okay.
Then type "mfastboot.exe reboot"- the phone will reboot.
Keep in mind though that you will not have wifi on the 5.1.1 radio.
And of course let me say as a disclaimer that I am not responsible for anything that may happen to your phone as a result of you trying this.
Also, as far as editing the xml file, you only need to do that if you are trying to downgrade via rsd lite. Not sure if that will work though. I do know that the DT2 works so much better on T-Mobile on 5.1.1.
Then type "mfastboot.exe flash modem NON-HLOS.bin" You should see it flash and then say Okay after it is done.
Then type "mfastboot.exe erase modemst1"-you should get an Okay.
Then type "mfastboot.exe erase modemst2"-you should get an Okay.
Then type "mfastboot.exe flash fsg fsg.mbn"- you should get an Okay.
Then type "mfastboot.exe erase cache"-you should get an Okay.
Then type "mfastboot.exe reboot"- the phone will reboot.
Keep in mind though that you will not have wifi on the 5.1.1 radio.
And of course let me say as a disclaimer that I am not responsible for anything that may happen to your phone as a result of you trying this.
Also, as far as editing the xml file, you only need to do that if you are trying to downgrade via rsd lite. Not sure if that will work though. I do know that the DT2 works so much better on T-Mobile on 5.1.1.[/QUOTE]
Why didn't u do the Bluetooth after flashing modem and before flashing the fsg.mbn?
mfastboot.exe flash bluetooth BTFM.bin
I believe this will fix our signal drop and WiFi issue. Wanna try that b4 u flash 5.1.1.?
Sent from my XT1585 using Tapatalk
I'm having excessive battery drain, disconnected calls (loses tower signal for 20 seconds or so), and lack of responsiveness since receiving this update. Might have to do a factory reset.
I accidentally left Wi-Fi connected and downloaded the update. I'm trying to stay as old as possible firmware wise in case a root exploit is discovered. I probably should give up hope... Anyway, a quick YouTube search got me into recovery and I wiped cache before the update installed. I'm still old school!
Sent from my XT1585 using Tapatalk
Clever choice. At least wait for 6.0.1, less chance for root but for Force way better than 6.0.0.
Hi guys!
Download OEM Image: http : // 4pda . ru/forum/dl/post/7735591/WileyfoxOEM.img
Download TWRP Backup: https : // drive. google . com/file/d/0B6yu5JrPyY9mdDVxZHo0b2ZsVFU/view
Requirements:
-Wileyfox Swift with TWRP installed
How to install:
1. Download Files
2. Enter Fastboot
3. Delete old OEM and flash new OEM
Code:
fastboot -i 0x2970 erase oem
Code:
fastboot -i 0x2970 flash oem WileyfoxOEM.img
4. Extract TWRP backup to sd:/TWRP/BACKUPS/*yourdevice*/*backupname*
5.*Optional* Wipe System, Boot, Data and Cache
6. Restore Backup via TWRP(System & Boot)
7. Reboot and enjoy!
Screenshots & Source: http : // 4pda . ru/forum/index.php?s=&showtopic=730213&view=findpost&p=52438437
PS: Remove the spaces in the links. I'm not able to post direct urls because of my low post count.
phncx said:
Hi guys!
Download OEM Image: http : // 4pda . ru/forum/dl/post/7735591/WileyfoxOEM.img
Download TWRP Backup: https : // drive. google . com/file/d/0B6yu5JrPyY9mdDVxZHo0b2ZsVFU/view
Requirements:
-Wileyfox Swift with TWRP installed
How to install:
1. Download Files
2. Enter Fastboot
3. Delete old OEM and flash new OEM
Code:
fastboot -i 0x2970 erase oem
Code:
fastboot -i 0x2970 flash oem WileyfoxOEM.img
4. Extract TWRP backup to sd:/TWRP/BACKUPS/*yourdevice*/*backupname*
5.*Optional* Wipe System, Boot, Data and Cache
6. Restore Backup via TWRP(System & Boot)
7. Reboot and enjoy!
Screenshots & Source: http : // 4pda . ru/forum/index.php?s=&showtopic=730213&view=findpost&p=52438437
PS: Remove the spaces in the links. I'm not able to post direct urls because of my low post count.
Click to expand...
Click to collapse
New user with 1 post, looks sketchy. Think I'll hold out on this one. Be careful with this people.
LaneyUK said:
New user with 1 post, looks sketchy. Think I'll hold out on this one. Be careful with this people.
Click to expand...
Click to collapse
I understand your concerns, but you can check the source I provided. It's the same thread where the DP was released. The OEM image is even the exact same. You don't have to believe me, I just saw that this wasn't posted here yet, so I figured I'll link it for english speaking audiences, who don't want to use Google Translate or simply don't know that it's out there.
Greetings!
EDIT: Goddamn, I just wanted to share some screenshots to confirm it's indeed legit, but unfortunately I can't even post pictures because of my low post count.
phncx said:
I understand your concerns, but you can check the source I provided. It's the same thread where the DP was released. The OEM image is even the exact same. You don't have to believe me, I just saw that this wasn't posted here yet, so I figured I'll link it for english speaking audiences, who don't want to use Google Translate or simply don't know that it's out there.
Greetings!
Click to expand...
Click to collapse
Roger that! I just went back to stock for the vulnerability patches so I'll wait for confirmation before trying this. Thanks for clearing that up.
Thank you. It's working like a charm. But in about phone our phone is Genereal mobile 4G.
Ferrumlan said:
Thank you. It's working like a charm. But in about phone our phone is Genereal mobile 4G.
Click to expand...
Click to collapse
Really? Mine's still showing "Wileyfox Swift"? Well, that's weird, but if it still works, I guess it shouldn't matter.
phncx said:
Really? Mine's still showing "Wileyfox Swift"? Well, that's weird, but if it still works, I guess it shouldn't matter.
Click to expand...
Click to collapse
did you forgot to edit build.prop?
I snatched Nougat for General Mobile 4G I remember it
Sounds interesting. Are there any known bugs or lacking functionality?
nhmanas said:
did you forgot to edit build.prop?
I snatched Nougat for General Mobile 4G I remember it
Click to expand...
Click to collapse
I didn't edit anything, I installed the OEM images and the DP5 system & boot images and then dirty flashed the full release. I don't know if that makes a difference. In build.prop my device is listed as "seed"(GM 4G) but anyway it's still showing "Wileyfox Swift" in Settings
pucka said:
Sounds interesting. Are there any known bugs or lacking functionality?
Click to expand...
Click to collapse
No, everything works. It's an official OTA from Google for an Android One device.
Followed the instructions in first post...installed fine but I'd recommend a wipe of cache,data otherwise first boot hangs.
Everything seems to work but you can see its an initial build...jerky animations for example. After a brief play I restored my CM 13 backup. There's a world of difference in polish and options between the two at the moment.
is it purely stock android? or is it as customizable as cyanogenmod/os?
goodybags said:
is it purely stock android? or is it as customizable as cyanogenmod/os?
Click to expand...
Click to collapse
Stock...wanted to change order of nav buttons but its a no go.
aww. guess ill have to wait for cm14 then
I've got the files...
Question..
There is no wifi eap sim auth in this rom.
Where can I enable/tweak/mod wifi eap sim auth on Android 7.0 ?
On 6.0.1 There was an option in wifi options to select.
Thanks
Can anyone confirm that cellular works? I thought Android One used a different modem to the Swift.
seb5049 said:
Can anyone confirm that cellular works? I thought Android One used a different modem to the Swift.
Click to expand...
Click to collapse
It's working just fine here. I don't know if that's making a difference, but I'm living in Europe(Germany).
piromanneo said:
I've got the files...
Question..
There is no wifi eap sim auth in this rom.
Where can I enable/tweak/mod wifi eap sim auth on Android 7.0 ?
On 6.0.1 There was an option in wifi options to select.
Thanks
Click to expand...
Click to collapse
I'm sorry, but I have no idea. Hopefully someone else, who knows a bit more than I do, is watching this thread and can help you with this.
BTW: @ all I just noticed the OEM link seems to be down. I'll look for a mirror in the next few hours. Unfortunately, I deleted the file after flashing it. If you find one, please share it in this thread, so I can update OP.
phncx said:
It's working just fine here. I don't know if that's making a difference, but I'm living in Europe(Germany).
Click to expand...
Click to collapse
Ok, thanks. One more question: How would I go about restoring Cyanogen OS back? Can I just flash a backup I made?
phncx said:
It's working just fine here. I don't know if that's making a difference, but I'm living in Europe(Germany).
I'm sorry, but I have no idea. Hopefully someone else, who knows a bit more than I do, is watching this thread and can help you with this.
BTW: @ all I just noticed the OEM link seems to be down. I'll look for a mirror in the next few hours. Unfortunately, I deleted the file after flashing it. If you find one, please share it in this thread, so I can update OP.
Click to expand...
Click to collapse
Edit: Found new bug with Bluetooth, I can't turn it on, in settings it says Bluetooth disabled and WiFi EAP SIM support is not available in settings...
Otherwise ROM is stable, battery performance is superb (better than marshmallow or cm), no problems with lagging, network etc... I've tested only one SIM, I don't know if dual sim works , othervise in settings second sim slot is listed.
I've successfully rooted rom with lastest chainfire supersu, waiting for xposed framework nougat support.
FOR INSTALLING I've used the SIMPLE twrp method:
1. Unlocked bootloader
2. Flashed lastest TWRP
3. Cleaned everything
4. downloaded this zip
https:// docs.google.com /uc?id=0B6yu5JrPyY9maUJfMGNKai03VEk&export=download
5. Flashed it in TWRP recovery, first boot takes more time, google apps are included.
DE NADA
any custom kernel for N?
---------- Post added at 11:26 AM ---------- Previous post was at 11:24 AM ----------
seb5049 said:
Can anyone confirm that cellular works? I thought Android One used a different modem to the Swift.
Click to expand...
Click to collapse
wileyfox swift modem works fine on android one.
little problematic but works. so there's no reason to not work for you
Hello!
I have a problem and would like know if I could fix it in any kind of way. My Mi Max hydrogen was first registered with an Mi account, which has now been deleted. I requested the unlock permission from Xiaomi accidentely with an other MI ID, that's why I have deleted the old one and wanted to register the new one.
First the device was locked after that and I couldn't access my phne anymore, because of an allegedly wrong password.
I managed to unlocked it with the Mi Max account solution flash file which I found in an other forum.
Now I can log in to my phone again with the new account ID, but the problem is, I get an error message on every boot "phone storage damaged". I think the old account information are still registered with the phone, because I can't register the phone to the new account under advance options/develeoper options/MI unlock status. When I click the register account/device button I always get the error message "failed, please try again later".
Because my phone seems to be still registered to that old account, the unlocking tool from xiaomi stucks at 50% completion with the error message current account is different from the account info on the device.
beside that, I now seem to have a problem with my persist mount storage on the phone. I tried to flash a custom ROM with TWRP and there is always a "unable to mount //persist (invaild argument)" error in red displaying. The only way I have found so far to fix this persist error, needs an unlocked bootloader so I think I'm stuck now :/
Flashing official ROMs old and new ones, global and china in EDL mode with Miflash did not fix the problem. I can't install any custom ROM now, since I flashed this Mi account solution thing. This persist error leads to bootloops or never ending loading screen after flashing LineageOS or CM.
does somebody know a way to fix it ?
Thanks in advance
Dave
SOLVED!!
All solved after flashing a modified ROM!! Flash in EDL or Fastboot with MIFlash tool. After that, flash TWRP again and the ROM of your choice.
http://forum.gsmdevelopers.com/showthread.php?t=16030
...
Davehimself said:
All solved after flashing a modified ROM!! Can't post the link to it cause of the min. 10 posts.
Click to expand...
Click to collapse
please send me (pm me) the link of modified ROM , I lose persist partition now, thank you
Yes share link of rom it will help many others
Davehimself said:
All solved after flashing a modified ROM!! Can't post the link to it cause of the min. 10 posts.
Click to expand...
Click to collapse
Can you pm me to because i'm facing similiar problem with my mi max phone..thanks..
Davehimself said:
...
Click to expand...
Click to collapse
please send me that link ,thanks.
www_123 said:
please send me that link ,thanks.
Click to expand...
Click to collapse
Link updated, please check again.
Davehimself said:
Link updated, please check again.
Click to expand...
Click to collapse
thanks.
Hello all!
This morning I updated Magisk Manager.
Once updated (or perhaps only downloaded update) the app prompted a reboot.
I rebooted and ended up in TWRP.
But I did not know what to do in TWRP so I rebooted system...
However, now the phone cannot boot and after one try it reboots into TWRP again.
PLEASE HELP ME!
I need my phone for work! Like now-now! :silly: :crying:
dustylambo said:
Hello all!
This morning I updated Magisk Manager.
Once updated (or perhaps only downloaded update) the app prompted a reboot.
I rebooted and ended up in TWRP.
But I did not know what to do in TWRP so I rebooted system...
However, now the phone cannot boot and after one try it reboots into TWRP again.
PLEASE HELP ME!
I need my phone for work! Like now-now! :silly: :crying:
Click to expand...
Click to collapse
How soon is now ? follow the white rabbit:good:
https://forum.xda-developers.com/zenfone2/help/help-bootloop-to-recovery-t3577504
timbernot said:
How soon is now ? follow the white rabbit:good:
https://forum.xda-developers.com/zenfone2/help/help-bootloop-to-recovery-t3577504
Click to expand...
Click to collapse
Well, that rabbit went into quite the hole... hehe
However, at the other end was a person who restored an old backup to revert this problem... And I -MAYBE- have an old backup on my external hdd, but won't that wipe all data that has been written to my phone since that "MAYBE" backup?
The other suggestion was wiping my MISC-partition using commands through ADB - something I have no clue how to setup and/or execute.
Still, thank you so much for your effort!
Reading all of this made me remember that one time I spaced out and tried to install an official firmware update upon release and prompt, which lead to the same issue. I could then just reinstall an older raw firmware version, which left all my files and data intact. Hopefully this will work here too.
BUT... It still feels very risky. If anyone out there has any sure-fire solution to this update Magisk Manager through the built-in updater no-boot issue, then please feel free to let me know - I would be forever in your debt
The best surefire solution is just don't. And BTW always backup before you flash anything in twrp.
Sent from my ASUS_Z00A using Tapatalk
---------- Post added at 08:49 AM ---------- Previous post was at 08:47 AM ----------
timbernot said:
How soon is now ? follow the white rabbit:good:
https://forum.xda-developers.com/zenfone2/help/help-bootloop-to-recovery-t3577504
Click to expand...
Click to collapse
I love what you did there! Lol
Sent from my ASUS_Z00A using Tapatalk
kenbo111 said:
The best surefire solution is just don't. And BTW always backup before you flash anything in twrp
Click to expand...
Click to collapse
I didn't flash anything in twrp. If you're gonna reply at least read the post. Also, none of what you wrote is a solution, unless you're in possession of a time machine. I'll keep it in mind for the next time though (of which there won't be one). Thanks, captain hindsight.
dustylambo said:
I didn't flash anything in twrp. If you're gonna reply at least read the post. Also, none of what you wrote is a solution, unless you're in possession of a time machine. I'll keep it in mind for the next time though (of which there won't be one). Thanks, captain hindsight.
Click to expand...
Click to collapse
That's what the update does. Reboots to twrp and installs the download. Maybe you should know what you're doing before you snap at us.
Sent from my ASUS_Z00A using Tapatalk
dustylambo said:
However, at the other end was a person who restored an old backup to revert this problem... And I -MAYBE- have an old backup on my external hdd, but won't that wipe all data that has been written to my phone since that "MAYBE" backup?
Click to expand...
Click to collapse
No, just restore the boot partition (16MB).
I learnt the hard way about backup, when years ago I didn't make one for my Galaxy S2 and lost everything (pictures, etc). Now after installing TWRP I always do a backup...
You should be able to reflash your boot partition with a fastboot command like "fastboot flash boot boot.img" (people with more knowledge than me can help you)
EDIT: the problem is that our Zenfone2 needs a signature for the boot partition, this is why we have a special Magisk installer that just add the signature to the image. The automatic update installer of Magisk has no clue about this, me and a few others here made the same mistake as you when Magisk popup "I have an update!" and we clicked "Install"...
All your data and app are still there, do not worry, no need to wipe anything, just reflash a signed boot.
kenbo111 said:
That's what the update does. Reboots to twrp and installs the download. Maybe you should know what you're doing before you snap at us.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Look... I am sorry if I "snapped" as you put it... But let's make one thing clear - I snapped at YOU; there is no "us" in this case, as you tried to skew it. Don't lump yourself together with these other helpful people, because so far you have nothing in common to me. If I were looking for someone to go "Hey, I got a solution - you know that thing you did? - Don't do it again!" I'd just go stand on the street corner with a sign asking for someone to slap my face.
As for your principal of don't do things if your not sure of how they work, I am totally behind that. But it has NOTHING to offer here as we are past that point. A broad comparison would be like "a solution to world hunger = eat food" ("but we don't have any food!" "you should have thought of that before you started starving now shouldn't you...?!").
In your defense, I guess you really believe you are trying to help. But compare your comment to the other ones posted and it is quickly clear that you are not. However, YOU ARE RIGHT, I should've known better and shouldn't do it again. And obviously I am enerved at this situation, but equally obvious (now) is that what you wrote is NOT "the best sure-fire solution" as what was posted afterward seems at least 100% (would have been more if possible) more applicable to my issue.
Anyway, I'll do the right thing here in the end, after having said so many things, and admit, once again, that I was wrong, you were right, I snapped for no good reason and you were just trying to help.
And I sincerely apologize for my rude behaviour. Hopefully now you can at least understand my reaction.
Also, fair is fair - Maybe TWRP flashes the update before it even enters into it. It would be the first I've EVER heard of something like that. But I am out of my element a bit here, so I will withdraw that comment and once again apologize for snapping at you because of it.
Magister54 said:
No, just restore the boot partition (16MB).
I learnt the hard way about backup, when years ago I didn't make one for my Galaxy S2 and lost everything (pictures, etc). Now after installing TWRP I always do a backup...
You should be able to reflash your boot partition with a fastboot command like "fastboot flash boot boot.img" (people with more knowledge than me can help you)
EDIT: the problem is that our Zenfone2 needs a signature for the boot partition, this is why we have a special Magisk installer that just add the signature to the image. The automatic update installer of Magisk has no clue about this, me and a few others here made the same mistake as you when Magisk popup "I have an update!" and we clicked "Install"...
All your data and app are still there, do not worry, no need to wipe anything, just reflash a signed boot.
Click to expand...
Click to collapse
NOW THIS IS HELPING!
THANK YOU SO MUCH!
Basically, you are saying that I would, in theory, just have to use fastboot and flash boot.img (extracted from any firmware?) again, which I am very familiar with how to do, and presto - boot partition restored and working (once again, in theory)?
Sounds amazing!:good:
dustylambo said:
NOW THIS IS HELPING!
THANK YOU SO MUCH!
Basically, you are saying that I would, in theory, just have to use fastboot and flash boot.img (extracted from any firmware?) again, which I am very familiar with how to do, and presto - boot partition restored and working (once again, in theory)?
Sounds amazing!:good:
Click to expand...
Click to collapse
Yes, if you have a Z00A for instance with MM version 223, take the Z00A.zip file from https://forum.xda-developers.com/zenfone2/general/bl-unlock-ze551ml-toolkit-t3546293 and use the file stock\z00a\223\boot.img
This is stock unsigned boot.img file for M .223
http://www.mediafire.com/file/rw73099svgbv0kv/boot.img
timbernot said:
boot.img file for M .223
http://www.mediafire.com/file/rw73099svgbv0kv/boot.img
Click to expand...
Click to collapse
Is there any way to check from TWRP or using fastboot, or otherwise find out what version of the rom I have (had)?
I am definitely still on LolliPo... I think I am one or two official updates from the switch to MarshMallow... But how can I be sure?
WW_ZE551ML_2.20.40.139_sal358-amtech.vn
Last year sometime I ran into a similar problem, where I had to flash raw firmware in order to unbrick the phone... This is the firmware that I downloaded and flashed then.
However, within this .raw-file there is no boot.img ...? There are a couple of .img-files, but none named boot.
On a side-note: When I bricked it last year and had to flash this raw firmware, which I did with Asus Flash Tool, if I am not mistaken... However, whichever way I did it, I managed to flash and then boot as usual. The phone then updated all apps, and I was just blessed with this wonderful sight of "my phone" with all the apps, files and data still intact.
And this problem, which resulted in the same boot issue, came from trying to apply an official OTA update, just after rooting and unlocking the bootloader (forgot myself for just a moment there), which to me seems like a way more serious screw-up than what I just managed to do today...?
@dustylambo
You still boot to TWRP ?
Simple questions
check date of back ups , course you won't be able to restore but title will have builds.
What twrp build ?
Then....
Select reboot in twrp then power off in twrp .
Wait 15 seconds...
Power plus vol+ , you can now boot to bootloader.
What IFWI version ?
0094.0177 or .0173 is LP
0094.0183 is M
Flash relevant raw , without ticking wipe data in AFT.
Check my unbrick thread in my signature for AFT and links to raws
Enjoy
timbernot said:
@dustylambo
You still boot to TWRP ?
Simple questions
check date of back ups , course you won't be able to restore but title will have builds.
What twrp build ?
Then....
Select reboot in twrp then power off in twrp .
Wait 15 seconds...
Power plus vol+ , you can now boot to bootloader.
What IFWI version ?
0094.0177 or .0173 is LP
0094.0183 is M
Flash relevant raw , without ticking wipe data in AFT.
Check my unbrick thread in my signature for AFT and links to raws
Enjoy
Click to expand...
Click to collapse
Yes, I still boot into TWRP.
I can't find my old backup for some reason, but after flashing the previously mentioned raw firmware I never up- or downgraded the ROM, so it MUST be that version. It's the only one I've ever downloaded and flashed.
IFWI version is 0094.0183
But so you are saying I could basically just flash [correct version FW].raw via AFT, without wiping data, and all should be good?
I am on your unbrick thread aws.
I will def bookmark it.
But I already have AFT and the same FW... so I could just go-go-go, right? Or is the IFWI version being M an issue?
Also, I downloaded the official Asus FW from their ZF2 website. In that .zip is in fact a "boot.img" - can I flash this via fastboot you think?
Thanks again for all your help!
You are unbelievable!
@dustylambo
0094.0183 is M
So flash a M raw.
You must've upgraded bootloader since flashing the last raw .139 which is LP to get to M bootloader .0183
In bootloader .0183
You flash raw for M, these have just been added by realyoti
drop him a thanks .
Flash without ticking wipe data in AFT
Damnit! I don't like where this is going... But it's late and I'm dumb
I never upgraded to M because I read that there were several apps that would lose support, MUSIC in particular, but there were others as well.
Will an M raw-file flash and still boot with all my old apps?
@dustylambo
It's simple really , what is the twrp build number ?
You never said
0094.0177
Is locked 5 LP bootloader.
.0173 is 5 unlocked bootloader
.0183 is M
What twrp build is yours ?
Ps , I don't think it matters which version raw you flash , only that it may fail and might have to wipe data to succeed which is better than what you have and are struggling with right now
gnite , enjoy
---------- Post added at 11:45 PM ---------- Previous post was at 11:30 PM ----------
Pls , remember the reason you installed twrp initially ?
For backing up
Sounds like you didn't only update Magisk Manager, you update Magisk itself. A non-signed Magisk update will always result in bootloop.
adobrakic said:
Sounds like you didn't only update Magisk Manager, you update Magisk itself. A non-signed Magisk update will always result in bootloop.
Click to expand...
Click to collapse
To be corrected: Not the Magisk, but the repacked boot.img. ?
Sent from my Redmi 3 using XDA Labs
So I installed the latest Oreo Global ROM on my Mi 6. Everything was smooth until I decided to install some dark theme from the Themes app and the phone bricked.
I booted into recovery mode, wiped all data and rebooted.
As I reboot, it shows the MIUI 9 intro screen. Select language, then select region. AFTER I select region, the phone setup shows 'wait a second...' and then the error happens: a message 'Find Device has stopped' appears and it boots. Eternally.
So far I've tried:
1) Xiaomi PC Suite - says I should update my phone before using it.
2) Xiaomi Mi Flash - says I need to unlock bootloader
3) I asked to unlock bootloader, was authorized for my Mi account a few hours later, but when I use the Mi unlocker app, it says my My Account was not bound to the device (well it was but I wiped data...)
4) If I try an unnoficial flash tool, it says I need to enable USB debugging. I can't enable it anymore because the phone is stuck in the initial setup screen when it boots after Find Device stops.
Any suggestions please? I have no idea how to recover my phone.
Thanks!
Here is a method that worked for bricked Mi 5 devices.
I don't have time to look in your particular problem right now, but rest assured, as a last resort you can always boot into EDL mode and flash right away without unlocked BL. You need to open up your phone for that though.
mkioshi said:
Any suggestions please?
Click to expand...
Click to collapse
Alright, I might have worked out a solution, make sure to follow these steps:
Download Global Dev 8.1.25 ROM zip.
Download Xiaomi ADB, extract the 3 files and put them in a folder with the ROM zip.
Hold Vol + Power down and in the following menu select "Connect to Mi Assistant" or "连接小米助手".
Drag the ROM zip onto the XiaomiADB.exe, let it do its thing.
On successful flash the device will reboot. Enter recovery-mode again.
Via cmd, run xiaomiadb format-data.
Let me know if this works. If you have any questions, feel free to ask.
Good luck!
DavidRJ said:
Let me know if this works. If you have any questions, feel free to ask.
Good luck!
Click to expand...
Click to collapse
Damn, I thought this would work.
I tried to flash your dev rom, it said I can only flash Global ROMs.
So I tried 9.2.2.0,it said I could not flash this because it's older.
Then I tried the current ROM I had, the 9.3 (Oreo) and it flashed alright, I formatted data via adb like you said... But no way, I get the same MIUI welcome screen, choose language, choose region, and after I choose region (only China is listed) I get the same Find Device closed message and it reboots.
Maybe I'll be able to do this with a future MIUI release? Maybe it's a 9.3 OCAMIEK bug?
mkioshi said:
Maybe I'll be able to do this with a future MIUI release? Maybe it's a 9.3 OCAMIEK bug?
Click to expand...
Click to collapse
Unlucky. Try with some more zips to be sure. Make sure to try China Dev and Stable too.
If nothing would work and there's really no other way, are you confident enough to open up your phone? You'd just need to connect 2 points to enter EDL mode which should allow you to flash anything you want.
But for now you could also wait for a new release and see if that helps.
It happened to me exactly the same this weekend in a mix 2. After all the afternoon trying to fix it in this way.
Install a recovery through adb in fastboot mode, from adb restart the device by pressing the volume up button to enter the recovery directly. Once in recovery mode I made all the wipes and then I copied a custom rom to the internal memory of the phone and the flash in my case was epic rom. And the cell phone already works perfectly for me.
I write from a translator I'm sorry if you do not understand something, I hope it helps.
A greeting from Spain!
I just spent hours fixing the same issue. In the end the following method worked. Note that it requires an unlocked bootloader.
Sorry I can't post links yet so just have to refer to Google searching...
1. Download latest miFlash v2017.7.20.0 (Google search for it)
2. Go to "Fastboot Update - Xiaomi MIUI Official Forum" site (again just Google search)
3. Download "★ Xiaomi Mi 6 Latest Global Stable Version Fastboot File Download" from the website in step 2 (other ROMs probably work too)
4. Follow the above guide from the Fastboot section
Good luck!
Pc suite wont work on our mi6 because it only works until android 6 or so, so its not for us.
Id wait for the next global stable release and try that one out. BTW, have u tried flashing MIUI china versions? Maybe that one works out (althugh it said only global, maybe referring to developers and not china stable). GL!
I can't unlock the bootloader. Applied for it on MIUI, it authorized me but the unlocked app says the device is not bound to my MIUI account.
Although i have logged in and backup stuff from my Mi account in that phone, that unlock app says its not associated. Maybe because I wiped the data when it bootlooped, i don't know. Anyway unfortunately can't unlock it right now. Thanks!
Sent from my SM-N920G using Tapatalk
DavidRJ said:
Unlucky. Try with some more zips to be sure. Make sure to try China Dev and Stable too.
If nothing would work and there's really no other way, are you confident enough to open up your phone? You'd just need to connect 2 points to enter EDL mode which should allow you to flash anything you want.
But for now you could also wait for a new release and see if that helps.
Click to expand...
Click to collapse
Oh I'll try other Roms. You did help me a lot tho because i was finally able to at least flash something to my phone. That relieves me a ton, because at least i know it can be saved someday lol.
I'm using my Galaxy note 5 and traveling now but will definitely try other Roms like the Chinese one next week. Thanks again, friend.
Sent from my SM-N920G using Tapatalk
mkioshi said:
That relieves me a ton, because at least i know it can be saved someday lol.
I'm using my Galaxy note 5 and traveling now but will definitely try other Roms like the Chinese one next week.
Click to expand...
Click to collapse
Not too bad of a substitute phone.
Apart from trying other ROMs, the notable thing here is that you can kind of access ADB commands via that tool which might help you fix the issue with "Find Device" FC.
Anyways, if you have any more questions later, I'll gladly help.
David
DavidRJ said:
Not too bad of a substitute phone.
Apart from trying other ROMs, the notable thing here is that you can kind of access ADB commands via that tool which might help you fix the issue with "Find Device" FC.
Anyways, if you have any more questions later, I'll gladly help.
David
Click to expand...
Click to collapse
Thanks David. I'll take a look at all the options in the adb tool when i come back home Monday.
I love my note 5, the screen is gorgeous and the camera is better than the Mi 6 IMHO. Reason i bought the Mi 6 are the 128 tb of storage, the size (this note i too big for my small hands) and the Mi 6 is so much faster, besides having tremendous battery life. My note5 battery was always ****, and I have been using it for the last 2 years (go the Mi 6 like 2 months ago).
You've been extremely helpful, bud. Are you from Brazil too? (Asking because of the RJ in your Nick)
Sent from my SM-N920G using Tapatalk
DavidRJ said:
Unlucky. Try with some more zips to be sure. Make sure to try China Dev and Stable too.
If nothing would work and there's really no other way, are you confident enough to open up your phone? You'd just need to connect 2 points to enter EDL mode which should allow you to flash anything you want.
But for now you could also wait for a new release and see if that helps.
Click to expand...
Click to collapse
I managed to flash the last global dev via xiaomiadb. It all went smooth.
Obviously, after selecting language and region, I get the same Find Device closed unexpectedly and it reboots.
And now, when I try to use xiaomiadb to flash or format data, it says ERROR and the phone reboots, like he's "rejecting" any xiaomiadb command. SO cannot flash anything now.
I'm giving up on this horrible phone.
mkioshi said:
And now, when I try to use xiaomiadb to flash or format data, it says ERROR and the phone reboots, like he's "rejecting" any xiaomiadb command. SO cannot flash anything now.
I'm giving up on this horrible phone.
Click to expand...
Click to collapse
Sorry to hear that. I can't really say what's the issue here as your phone is definitely not hard bricked but I have never seen such behavior before.
Well depending on where you bought your phone, you could definitely file an RMA with the seller. You didn't unlock bootloader and your phone bricked itself basically. If you bought it in China, it depends on how easy it is to ship phones overseas in Brazil. In Europe, we can't easily ship phones with non-removable batteries sadly. (Sou da Alemanha btw mas falo um poucinho de Português )
In any case, your last bet would be the EDL method. You will lose your warranty though.
But I understand that this is way too much hassle for a soft brick caused by a damn theming engine... I'm so glad I switched off MIUI months ago.
Anyways good luck and let me know if you get any further.
David
DavidRJ said:
Sorry to hear that. I can't really say what's the issue here as your phone is definitely not hard bricked but I have never seen such behavior before.
Well depending on where you bought your phone, you could definitely file an RMA with the seller. You didn't unlock bootloader and your phone bricked itself basically. If you bought it in China, it depends on how easy it is to ship phones overseas in Brazil. In Europe, we can't easily ship phones with non-removable batteries sadly. (Sou da Alemanha btw mas falo um poucinho de Português )
In any case, your last bet would be the EDL method. You will lose your warranty though.
But I understand that this is way too much hassle for a soft brick caused by a damn theming engine... I'm so glad I switched off MIUI months ago.
Anyways good luck and let me know if you get any further.
David
Click to expand...
Click to collapse
You're a very nice person, David, thanks a ton!
Oh no xiaomi RMA here. And yeah I saw some people who bricked their phones by installing some dark theme (not the same as mine, but it was always a dark theme) after upgrading to the Oreo global rom.
And just my luck, my Note 5 took a dive yesterday so I'm phoneless lol. Thinking bout getting a Xiaomi A1 or a Moto X4, theyre not expensive and about the same price here...
If you can use adb commands. Try:
> fastboot erase system
> fastboot erase userdata
> fastboot erase boot
> fastboot erase cache
> fastboot erase data
Then try flashing the the latest developer rom as you did before.
mkioshi said:
And just my luck, my Note 5 took a dive yesterday so I'm phoneless lol.
Click to expand...
Click to collapse
Damn... Well you could still try the advice from @golfinry, I didn't think of regular ADB commands at all. Then again, if you can't do RMA anyways, what's stopping you from trying the EDL method? As far as I know you can flash any MIUI ROM you want without unlocked BL with that.
golfinry said:
If you can use adb commands. Try:
> fastboot erase system
> fastboot erase userdata
> fastboot erase boot
> fastboot erase cache
> fastboot erase data
Then try flashing the the latest developer rom as you did before.
Click to expand...
Click to collapse
Oh but I cannot use fastboot on locked bootloader right? Got the message after trying these commands
fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
FAILED (remote: Erase is not allowed in Lock State)
finished. total time: 0.003s
DavidRJ said:
Damn... Well you could still try the advice from @golfinry, I didn't think of regular ADB commands at all. Then again, if you can't do RMA anyways, what's stopping you from trying the EDL method? As far as I know you can flash any MIUI ROM you want without unlocked BL with that.
Click to expand...
Click to collapse
Seems to require unlocked BL. Anyway have you ever seem this error:closed message when trying to do adb commands like adb usb (or xiaomiadb usb), adb format-data, adb sideload, etc?
Started happening after I managed to flash latest global. SO I cannot try to flash anything now
Figured as much... What about the data partition. Same thing?