Hello.
I have an X9077 and was trying to flash the latest stable ROM coming back from Beta2.
I tried a few times with no luck and then I read that someone had had more luch by flashing 1.2 first and then the latest ROM.
I tried with that ROM and it caused a split screen image and when I tried again it just caused a blank screen. So no OPPO logo or noting but the backlight is on and the soft keys glow a bit.
If I try to enter recovery I have the same thing happening.
The computer sees the phone and the sd card and I can access it in fastbook mode but don't get any visuals in the screen to reload the beta2 Rom.
Please help. All I wanted was to get the GAPPS and to be able to make and receive calls without chinese characters popping out everywhere.
I downloaded the stock recovery from:
oppoforums . com / threads / stock-recovery-for-find-7-7a.17397 /
and then did a
fastboot erase cache
Which worked fine and then I did a
fastboot flash recovery recovery.img
Which worked but still can't access the recovery part. I get a blank black screen with glowing buttons underneath.
Everything went south before when I installed X9006_12_OTA_INT_001_all_svn5596_wipe.zip which I now know was not for my phone.
munecito said:
Hello.
I have an X9077 and was trying to flash the latest stable ROM coming back from Beta2.
I tried a few times with no luck and then I read that someone had had more luch by flashing 1.2 first and then the latest ROM.
I tried with that ROM and it caused a split screen image and when I tried again it just caused a blank screen. So no OPPO logo or noting but the backlight is on and the soft keys glow a bit.
If I try to enter recovery I have the same thing happening.
The computer sees the phone and the sd card and I can access it in fastbook mode but don't get any visuals in the screen to reload the beta2 Rom.
Please help. All I wanted was to get the GAPPS and to be able to make and receive calls without chinese characters popping out everywhere.
I downloaded the stock recovery from:
oppoforums . com / threads / stock-recovery-for-find-7-7a.17397 /
and then did a
fastboot erase cache
Which worked fine and then I did a
fastboot flash recovery recovery.img
Which worked but still can't access the recovery part. I get a blank black screen with glowing buttons underneath.
Everything went south before when I installed X9006_12_OTA_INT_001_all_svn5596_wipe.zip which I now know was not for my phone.
Click to expand...
Click to collapse
Hi, since you're also here, the link:
http://www.oppoforums.com/threads/find-7-x9077-soft-bricked.16918/
Good luck.:fingers-crossed:
tropical cactus said:
Hi, since you're also here, the link:
http://www.oppoforums.com/threads/find-7-x9077-soft-bricked.16918/
Good luck.:fingers-crossed:
Click to expand...
Click to collapse
Well I have installed the stock recovery but my phone still does all the things that Suyi's did.
I have written to Suyi and Coldbird to see if they can guide me on how to manually restore the partitions.
Thank you very much.
Coldbird and Suyi are legends!!! I have rescued my phone back from the darkness thanks to your amazing work.
The only thing is that there is an unnecessary line there which is 521. The syntax in it is wrong but it doesn't harm the procedure, but it can be a bit unnerving.
I did not use the ROM that they used but the latest stable 1.2.1
Instructions are here:
http://www.oppoforums.com/threads/find-7-x9077-soft-bricked.16918/page-2#post-218544
munecito said:
Coldbird and Suyi are legends!!! I have rescued my phone back from the darkness thanks to your amazing work.
The only thing is that there is an unnecessary line there which is 521. The syntax in it is wrong but it doesn't harm the procedure, but it can be a bit unnerving.
I did not use the ROM that they used but the latest stable 1.2.1
Instructions are here:
http://www.oppoforums.com/threads/find-7-x9077-soft-bricked.16918/page-2#post-218544
Click to expand...
Click to collapse
Well done. Oppo should at least have set the numbers of the models further apart e.g. 9008 for find 7 & 9007 for 7a. It seems 7 is feng shui for them. Launch date for find 7 in Malaysia is 7.7.14. 7+7=14.
Oppo. Symmetry. Should be opqo.
My phone's model number is X9076. I am facing this same issue. The only difference is that my phone is not even rooted. Whenever I try installing TWRP on my phone the screen goes black. When I try pressing the hardware buttons, it gives a haptic feedback but doesn't show anything on the screen. Because of that I am not able to root my device and also can't install any custom ROMs. Also my phone is in stock condition and I haven't done anything to it before. How can I fix this (please don't provide me with any links, please explain me the procedure so it becomes easy for me )
Devansh Bharatia said:
My phone's model number is X9076. I am facing this same issue. The only difference is that my phone is not even rooted. Whenever I try installing TWRP on my phone the screen goes black. When I try pressing the hardware buttons, it gives a haptic feedback but doesn't show anything on the screen. Because of that I am not able to root my device and also can't install any custom ROMs. Also my phone is in stock condition and I haven't done anything to it before. How can I fix this (please don't provide me with any links, please explain me the procedure so it becomes easy for me )
Click to expand...
Click to collapse
https://forum.xda-developers.com/find-7/help/how-to-debrick-unbricka-oppo-7-7a-t3717802/page1
knusto said:
https://forum.xda-developers.com/find-7/help/how-to-debrick-unbricka-oppo-7-7a-t3717802/page1
Click to expand...
Click to collapse
Thank you but my phone is not bricked.
Is this thread dead already? Because I need some serious help with my Find 7
Devansh Bharatia said:
Is this thread dead already? Because I need some serious help with my Find 7
Click to expand...
Click to collapse
Setup?
Skickat från min Find7 via Tapatalk
Hi All.
I have a Samsung Galaxy S4 Mini LTE (GT-I9195) which displays a White Screen when powered on.
The only thing that I can see is the SGS4 splash screen at boot and after that the screen turns to White. When I try booting into Recovery Mode, The splash screen pops up saying "RECOVERY BOOTING" and afterwards, the screen turns white. I can, however, boot into download mode which leads me to think that this is a software problem
I have opened up the entire phone and ran an inspection on the parts and they seem to be fine. I have tried flashing the JB software using a guide posted on this forum but it failed as I'm stuck on Bootloader v2 (Curse you Samsung) from the update to KK some time ago which makes it impossible to downgrade the OS.
Another thing to note is that the device responds to touch as I have an assistive light widget and it turns on when I tap the place in which I have it on my homescreen.
The phone is not under warranty anymore as my carrier only has a 1 year warranty for phones purchased from them and I would like to try and fix it myself instead of having to pay a sum of money to get this device working again.
I have spent several hours searching and have basically landed myself back at step 1 - with a non-working device.
I appreciate any and all help provided with this issue and will try and provide more information if needed.
Thanks!
Why don't You try to flash it with 4.4.2?? If You can see splash and nothing after that it's not related with screen but firmware or memory. Boot Your phone in download mode and flash it with Odin to stock 4.4.2. If it doesn't help Your eMMC can be fried. Unfortunately it's common issue in S4 Mini but the first time I've heard about white screen with fried eMMC. Anyway good luck.
Chamelleon said:
Why don't You try to flash it with 4.4.2?? If You can see splash and nothing after that it's not related with screen but firmware or memory. Boot Your phone in download mode and flash it with Odin to stock 4.4.2. If it doesn't help Your eMMC can be fried. Unfortunately it's common issue in S4 Mini but the first time I've heard about white screen with fried eMMC. Anyway good luck.
Click to expand...
Click to collapse
Thanks so much for the quick reply.:good:
I will try doing so. Could you please provide me with a link to download from, I would really appreciate it.
http://www.sammobile.com/firmwares/database/GT-I9195/
You need to register to download but it's free. Choose Your country and then You will see all available files.
Chamelleon said:
You need to register to download but it's free. Choose Your country and then You will see all available files.
Click to expand...
Click to collapse
Okay Thanks Man. I'll let you know how it goes:good:
Chamelleon said:
You need to register to download but it's free. Choose Your country and then You will see all available files.
Click to expand...
Click to collapse
Okay, so after getting around to downloading the files for my country (I chose the South Africa (Vodafone)) and trying to flash that, I'm now recieving an error near the end saying invalid ext4 image while flashing some hidden.img (something like that) file. After some googling, I found that I need to Flash a new Partition Information Table (PIT) with the OS because of different file sizes, however, I am unable to find that PIT file. What do I do now?
First try to flash different file. For example choose stock GB without any brand. Sometimes branded flashes are corrupted.
---------- Post added at 08:16 AM ---------- Previous post was at 08:13 AM ----------
When I will be in my service center today I'll look on server for PIT file. I should have some.
Well, double whammy, one problem resulting from trying to fix the other.
I was having screen problems where the lower half of my screen would take a long time to refresh and followed a post to wipe the partition cache hoping to help the issue.
Well, not sure what happened with that (since I couldn't see the loading or anything because of the screen issue) but after half an hour I rebooted my phone and now it boots into an error (android logo error).
I tried flashing firmware back on and it didn't help.
Any possible assistance?
The only thing I can access is the bootloader and nothing else currently
GlitchZenfone2 said:
Well, double whammy, one problem resulting from trying to fix the other.
I was having screen problems where the lower half of my screen would take a long time to refresh and followed a post to wipe the partition cache hoping to help the issue.
Well, not sure what happened with that (since I couldn't see the loading or anything because of the screen issue) but after half an hour I rebooted my phone and now it boots into an error (android logo error).
I tried flashing firmware back on and it didn't help.
Any possible assistance?
The only thing I can access is the bootloader and nothing else currently
Click to expand...
Click to collapse
Hello,
Thanks for using XDA Assist.
Moving your thread to Zenfone 2 Q&A,Help and Troubleshooting.Experts there may be able to help you
___
v7
XDA Assist
Hi Guys
please help me fix a few problem which are driving me crazy.
here's the story
my zenfone is z00ad 4ram 64gb version, everything was fine until recently, i tried upgrade to Android M using asus flash tool with the latest raw file provided by realyoti, as a result got it hard bricked, black screen no vibration and pc could not detect the device too
took it to a repair center (there is no official asus service center in my country), they were successful doing a boot repair but couldn't flash any roms ,they told me that they had to replace the hard drive of the device, did so but still took them more than a week to call me saying the phone is ready
they somehow changed my phone to a "Z00ADA" variant with a rooted CN rom, the serail number was 111111111 in the settings, but in the bootloader the serial number was 0123456789..G, and my imei was different from what the box said but since they were both in the back of my phone i assumed it is ok. there were too many Chinese apps and no gapps, so i decided to change to ww version, but there were no recovery and when i tired to boot into recovery phone just booted into the bootloader instead, let the repair technician know asked him why there is no recovery told me that he had to replace the motherboard to do that and that i should use the device as is or give him yet more time to solve the recovery and Z00ADA version, it was nearly a month so i told him no thanks
found the guide on how to do it myself , using fastboot comands and upgraded straight to the latest android M, by the time i finished the typing fastboot reboot that i noticed the op had written its best to flash a L rom before flashing M rom ( which i didnt, and since there was no APD.IMG in the MM rom i skipped flashing it) phone booted up perfectly though
upon connecting the phone pc still recognized the device as Z00ADA when the bootloader was Z00AD, strange!
phone was working fine except for the fast-charge which was working sometimes and not the other times and the com process.phone.stopped working error
then one morning when i restarted the phone it didn't turn back on, thought it is because of the come.phone .process so wiped cache did a factory reset but ran out of battery when booting up. recharged it when i got home and phone booted up but those two problems i mentioned was persistent, then fastcharging stopped working and it was taking me 8 hours to recharge, decided to flash again but pc was not recognizing the device, used sd card to flash the update zip and did a factory reset, phone was ok with those same problems
found a guide deleted every intel driver using a tool and got the pc to recognize my device as Z00AD, since fastcharging was ok in android LP tried to downgrade , used fastboot comands flashed everything but got error in
fastboot oem partition /tmp/partition.tbl
fastboot flash /tmp/partition.tbl partition.tbl
phone was stuck in boot screen , used asus flash tool flashed the LP raw and phone booted up
but the screen was acting up and was doing things on its own, used asus flash tool to upgrade to MM raw , phone booted up screen was fine except when i tried the one layer mode in asus zenui launcher, changed back to two layer mode and it is fine til now, fast charging is working too
but now i have this strange problem, i have to plug the charger in and switch the phone on otherwise after loading the home screen phone will shut down though i have like 70 in the battery , and sometimes the phone shuts down when im using it
please tell me what to do , had i messed the phone changing from Z00ADA to Z00ad , it was working fine on that cn rom
too long didn't read, my phone got bricked , had it repaired and upgraded to android MM, but the phone either shuts down automatically or doesn't stay in home screen if it is not plugged
please help me solve it and change my serial number to the original one
thanks in advance for your replies:angel:
Edit: so today i downgraded to Android LP WW_ZE551ML_2.20.40.194_20160713 using asus flash tool 1.0.0.17, and i no longer had the issue, it didn't turn off, used it for a whole day like that for testing purposes and i got to 5% battery percentage without no hiccups lol, seeing that the issue worked itself out i decided to upgrade to Android MM UL-Z00A-WW-4.21.40.352 using update from adb sideload command and then wiped cache and data and rebooted the system, the welcome screen popped up and as i was choosing the language the phone shut itself down again, what is the problem , is there any log file i could share with you guys to see what is causing this system shut downs?
Edit 2: i took out the sim cards and phone was ok . it was not turning off, tested all apps installed and i noticed every app is working fine except for camera, the second i clicked to take a picture the phone shut down and was not switching back on unplugged, how ever i can take pictures and have both sims installed and phone is functioning properly when it is plugged to power supply. can somebody help me fix it?
here are two scenarios, 1 battery is bad. second if they really changed storage chip, there is a pretty good chance it came with pre flashed firmware. which might be causing the issue. very first of all open your phone and post high resolution images of the motherboard from both sided. i will try to look into it then only i will tell you what to follow. serial is not an issue though. it should not cause any issue in booting or rebooting. we can get it back first you need to resolve reboot issue!
don't forget to remove heat spreading plated before clicking images
sukhwant717 said:
here are two scenarios, 1 battery is bad. second if they really changed storage chip, there is a pretty good chance it came with pre flashed firmware. which might be causing the issue. very first of all open your phone and post high resolution images of the motherboard from both sided. i will try to look into it then only i will tell you what to follow. serial is not an issue though. it should not cause any issue in booting or rebooting. we can get it back first you need to resolve reboot issue!
don't forget to remove heat spreading plated before clicking images
Click to expand...
Click to collapse
hi there buddy thanks for the quick reply, it was working fine without me updating it from cn build straight into MM but ok ill take your advice , will have to watch a video on how to disassemble it, will post pictures and what do you mean by "don't forget to remove heat spreading plated before clicking images" .are there any instructions to follow when taking pictures?
cjdandy said:
hi there buddy thanks for the quick reply, it was working fine without me updating it from cn build straight into MM but ok ill take your advice , will have to watch a video on how to disassemble it, will post pictures and what do you mean by "don't forget to remove heat spreading plated before clicking images" .are there any instructions to follow when taking pictures?
Click to expand...
Click to collapse
i meant about plates covering the components. If you are inexperienced, Better do not take out the mother board. Just one thing, remove the back panel and click pic without removing anything. also disconnect battery connector and reconnect it.
sukhwant717 said:
i meant about plates covering the components. If you are inexperienced, Better do not take out the mother board. Just one thing, remove the back panel and click pic without removing anything. also disconnect battery connector and reconnect it.
Click to expand...
Click to collapse
yeah you guessed right i am a toatal noob when it comes to taking it apart,lol ill do that and just remove the back cover as a last resort since i am a noob
and i kinda felt it is somehow software related, cause i used to be able to change my network type using *#*#4636#*#* code to lte only but now no matter how hard i push on that it reverts back to lte/gsm auto
so today i downgraded to Android LP WW_ZE551ML_2.20.40.194_20160713 using asus flash tool 1.0.0.17, and i no longer had the issue it didn't turn off used it like that for testing and i got to 5% battery percentage without no hiccups lol, seeing that the issue worked itself out i decided to upgrade to Android MM UL-Z00A-WW-4.21.40.352 using update from adb sideload command and then wiped cache and data and booted the system it, the welcome screen popped up and as i was choosing the language the phone shut itself down again, what is the problem , is there any log file i could share with you guys to see what is causing this system shut downs?
i booted into recovery and there they were these logs which alright i had no idea what they were most of the times but at 96% percent of the log file i saw something, it said the kernel header is different from the kernel built kernel must be built with correct footer, do you guys see that too?
edit: i noticed that simcards are causing the problem turned the airplane mode on and phone switched back on unplugged, camera app is also making the phone shut down. what do you think it is, is there a fix?
cjdandy said:
yeah you guessed right i am a toatal noob when it comes to taking it apart,lol ill do that and just remove the back cover as a last resort since i am a noob
and i kinda felt it is somehow software related, cause i used to be able to change my network type using *#*#4636#*#* code to lte only but now no matter how hard i push on that it reverts back to lte/gsm auto
so today i downgraded to Android LP WW_ZE551ML_2.20.40.194_20160713 using asus flash tool 1.0.0.17, and i no longer had the issue it didn't turn off used it like that for testing and i got to 5% battery percentage without no hiccups lol, seeing that the issue worked itself out i decided to upgrade to Android MM UL-Z00A-WW-4.21.40.352 using update from adb sideload command and then wiped cache and data and booted the system it, the welcome screen popped up and as i was choosing the language the phone shut itself down again, what is the problem , is there any log file i could share with you guys to see what is causing this system shut downs?
i booted into recovery and there they were these logs which alright i had no idea what they were most of the times but at 96% percent of the log file i saw something, it said the kernel header is different from the kernel built kernel must be built with correct footer, do you guys see that too?
edit: i noticed that simcards are causing the problem turned the airplane mode on and phone switched back on unplugged, camera app is also making the phone shut down. what do you think it is, is there a fix?
Click to expand...
Click to collapse
i believe it can be fixed. but before that i want to make sure of motherboard version number. can you click photograph just removing back battery cover. can you see NFC antennas?
do you have imeis? *#06# post firrst few numbers of you imeis. please don't post complete imei
sukhwant717 said:
i believe it can be fixed. but before that i want to make sure of motherboard version number. can you click photograph just removing back battery cover. can you see NFC antennas?
do you have imeis? *#06# post firrst few numbers of you imeis. please don't post complete imei
Click to expand...
Click to collapse
i sure hope so thanks, i will remove the back cover and reconnect the battery connector under the volume down button when i get home and will snap some photos for you to see, i have it turned off but i assume it will, will test it and get back to you on that
IMEI1:3577980....
IMEI2:3577980....
the Last 3 digits are different , would imei s change if they changed storage chip? what do they need to replace for that to happen ?
but serial number is changed to 01234....F can i change the serial number using the whatchamacallit sofamia tool?
thanks for bearing with me
QUOTE=sukhwant717;78780989]i believe it can be fixed. but before that i want to make sure of motherboard version number. can you click photograph just removing back battery cover. can you see NFC antennas?
do you have imeis? *#06# post firrst few numbers of you imeis. please don't post complete imei[/QUOTE]
attached the pics buddy, will you take a look
reconnected the battery connector but didnt solve it
cjdandy said:
QUOTE=sukhwant717;78780989]i believe it can be fixed. but before that i want to make sure of motherboard version number. can you click photograph just removing back battery cover. can you see NFC antennas?
do you have imeis? *#06# post firrst few numbers of you imeis. please don't post complete imei
Click to expand...
Click to collapse
attached the pics buddy, will you take a look
reconnected the battery connector but didnt solve it[/QUOTE]
which firmware version you are currently on?
are your imeis correct?
put your phone on charge overnight only with a genuine or good charger. we will solve it other day. which time zone you live in?
sukhwant717 said:
which firmware version you are currently on?
are your imeis correct?
put your phone on charge overnight only with a genuine or good charger. we will solve it other day. which time zone you live in?
Click to expand...
Click to collapse
yes IMEIs are correct sir
I am on the latest marshmellow build (WW_ZE551ML_4.21.40.352_20170623)
IFWI version: 0094.0183
serial number-0123456789ABCDEF ( dunno why asus flash tool doesn't detect the correct SN!)
ok i will put it on charge overnight, +3:30 time zone iran
phone was on a CN z00ADA version and was rooted and had no recovery when i got it back from the repair center and was ok (used it like that for two days). using your Guide (https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785) , i directly flashed WW_ZE551ML_4.21.40.352_20170623.raw
sukhwant717 said:
Flashing Firmware Without AFT:
perform the following commands
1. fastboot devices ( see if it is recognized: else plug out usb and plugin again)
2. fastboot oem erase_osip_header
3. fastboot oem start_partitioning
4. fastboot flash /tmp/partition.tbl partition.tbl
5. fastboot oem partition /tmp/partition.tbl
6. fastboot erase system
7. fastboot erase cache
8. fastboot erase data
9. fastboot erase APD
10. fastboot erase ADF
11. fastboot oem wipe splashscreen
12. fastboot oem stop_partitioning
13. fastboot flash splashscreen splash_sign.bin
14. fastboot flash token MFG_BOM_Full.bin
15. fastboot flash ifwi ifwi-prod.bin
16. fastboot flash boot boot_sign.bin
17. fastboot flash recovery recovery_sign.bin
18. fastboot flash fastboot droidboot_sign.bin
19. fastboot flash APD APD.img
20. fastboot flash system system.img
21. fastboot reboot
Phone will successfully reboot into system. don't worry, first boot gonna take a little longer time. so have patience and watch some funny video till phone boots up.
Now you can install any firmware version via adb sideload. make sure to install latest lollipop firmware before flashing Marshmallow. follow the guide to sideload.
Click to expand...
Click to collapse
there was no APD.img, ifwi-prod.bin, token MFG_BOM_Full.bin, in the extracted raw file so i skipped flashing APD.IMG and flashed R60_BOM_FULL.bin, ifwi.bin. then i noticed this line "make sure to install latest lollipop firmware before flashing Marshmallow" and though i had killed my phone, but luckily phone booted up and i sighed in relief. phone was still OK except for the "unfortunately the process com.android phone has stopped" error which i wiped the cache for but didn't go away , so thought heck who cares it a minor error and i am gonna use it as it is, used the phone like that for almost a week, then one morning out of the blue when i tapped restart the phone the phone didn't load the zenui. and was shuting down, booted to recovery reseted to factory settings and now i ran out of battery, got back home plugged it in and phone booted up normally, the "unfortunately the process com.android phone has stopped" was still there and sometimes as i was playing games it would pop up and make the phone shut down, flashed the raw this time using asus flash tool no error message bu phone started this shutting down pattern.
trying to fix it i bricked my phone and using your guide and xfstk-downloader, phone was alive again and i was on your mentioned WW_ZE551ML_2.20.40.194_20160713 rom. and even i was getting ota updates , and phone was not shutting down but when i downloaded the ota update the phone did not restart and when i switched it on no update installing process was shown and phone booted up but was shutting down so flashed the rom using asus flash tool again and was OK used for a whole day to test if it is not shutting down and it was OK , updated to marhmellow and phone started shutting down automatically again, and even sometimes the touch screen acts up and press things on its own and starts programs and whatnot's
I am counting on your help to solve it, thanks a lot man
cjdandy said:
yes IMEIs are correct sir
I am on the latest marshmellow build (WW_ZE551ML_4.21.40.352_20170623)
IFWI version: 0094.0183
serial number-0123456789ABCDEF ( dunno why asus flash tool doesn't detect the correct SN!)
ok i will put it on charge overnight, +3:30 time zone iran
phone was on a CN z00ADA version and was rooted and had no recovery when i got it back from the repair center and was ok (used it like that for two days). using your Guide (https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785) , i directly flashed WW_ZE551ML_4.21.40.352_20170623.raw
there was no APD.img, ifwi-prod.bin, token MFG_BOM_Full.bin, in the extracted raw file so i skipped flashing APD.IMG and flashed R60_BOM_FULL.bin, ifwi.bin. then i noticed this line "make sure to install latest lollipop firmware before flashing Marshmallow" and though i had killed my phone, but luckily phone booted up and i sighed in relief. phone was still OK except for the "unfortunately the process com.android phone has stopped" error which i wiped the cache for but didn't go away , so thought heck who cares it a minor error and i am gonna use it as it is, used the phone like that for almost a week, then one morning out of the blue when i tapped restart the phone the phone didn't load the zenui. and was shuting down, booted to recovery reseted to factory settings and now i ran out of battery, got back home plugged it in and phone booted up normally, the "unfortunately the process com.android phone has stopped" was still there and sometimes as i was playing games it would pop up and make the phone shut down, flashed the raw this time using asus flash tool no error message bu phone started this shutting down pattern.
trying to fix it i bricked my phone and using your guide and xfstk-downloader, phone was alive again and i was on your mentioned WW_ZE551ML_2.20.40.194_20160713 rom. and even i was getting ota updates , and phone was not shutting down but when i downloaded the ota update the phone did not restart and when i switched it on no update installing process was shown and phone booted up but was shutting down so flashed the rom using asus flash tool again and was OK used for a whole day to test if it is not shutting down and it was OK , updated to marhmellow and phone started shutting down automatically again, and even sometimes the touch screen acts up and press things on its own and starts programs and whatnot's
I am counting on your help to solve it, thanks a lot man
Click to expand...
Click to collapse
download Raw from my guide for ZE551ML version will be 2.20.40.194.
I think you already have that one! but that definitely have APD.img.
copy all the files including unbrick files and extracted raw to desktop. i will help you through what to do.
sukhwant717 said:
download Raw from my guide for ZE551ML version will be 2.20.40.194.
I think you already have that one! but that definitely have APD.img.
copy all the files including unbrick files and extracted raw to desktop. i will help you through what to do.
Click to expand...
Click to collapse
yes i did download it and have that rom and im gonna download the ze550 files too and charge my phone overnight ,thanks
sukhwant717 said:
download Raw from my guide for ZE551ML version will be 2.20.40.194.
I think you already have that one! but that definitely have APD.img.
copy all the files including unbrick files and extracted raw to desktop. i will help you through what to do.
Click to expand...
Click to collapse
ready when you are sir
sukhwant717 said:
download Raw from my guide for ZE551ML version will be 2.20.40.194.
I think you already have that one! but that definitely have APD.img.
copy all the files including unbrick files and extracted raw to desktop. i will help you through what to do.
Click to expand...
Click to collapse
I still have the issue and dunno why my SN doesn't get restored to the original one
could you please help me
Edit: i rooted the phone and using this guide https://forum.xda-developers.com/sho...6&postcount=28 i was able to restore my SN but my BT address and mac remained unchanged, and i noticed there is also a config folder that contains this information and in its locale config it is stated that my phone model is 550ml when its 551ml, can you please share the contents of the config and factory folder , change your SN and mac address to zero so i can replace them with mine, i would really much appreciate your help