Related
owner lg g2-d802
Hey guys,
a while ago i rooted my d802 and flashed some roms and my experience was that my batterlife was worsen. So i tried to flash official kdz firmware in order to unroot my phone.
What i did was verry simple, flash the kdz and factory reset the whole device. But then i went back to download mode to see if i still had root. to my suprise it showd this (kdz 220b, userB99- rooted)
my question is why is it still rooted ?
abati said:
owner lg g2-d802
Hey guys,
a while ago i rooted my d802 and flashed some roms and my experience was that my batterlife was worsen. So i tried to flash official kdz firmware in order to unroot my phone.
What i did was verry simple, flash the kdz and factory reset the whole device. But then i went back to download mode to see if i still had root. to my suprise it showd this (kdz 220b, userB99- rooted)
my question is why is it still rooted ?
Click to expand...
Click to collapse
Use official LG KDZ ROMs and flash with LG Flash Tools 2014 :
http://forum.xda-developers.com/showthread.php?t=2797190
Flash mode: CSE flash
and dont forget to backup your sd card files. All will be wiped in this mode.
Official ROMs:
http://lg-firmware-rom.com
abati said:
owner lg g2-d802
Hey guys,
a while ago i rooted my d802 and flashed some roms and my experience was that my batterlife was worsen. So i tried to flash official kdz firmware in order to unroot my phone.
What i did was verry simple, flash the kdz and factory reset the whole device. But then i went back to download mode to see if i still had root. to my suprise it showd this (kdz 220b, userB99- rooted)
my question is why is it still rooted ?
Click to expand...
Click to collapse
Don't worry
http://forum.xda-developers.com/showthread.php?t=2703501
thnx i will try that !
Vogie said:
Use official LG KDZ ROMs and flash with LG Flash Tools 2014 :
http://forum.xda-developers.com/showthread.php?t=2797190
Flash mode: CSE flash
and dont forget to backup your sd card files. All will be wiped in this mode.
Official ROMs:
http://lg-firmware-rom.com
Click to expand...
Click to collapse
hey men, i tried exactly what you said, but it stil the same after i flashed the kdz with CSE flash mode.
when i go back to download mode it stil says (user b97 - rooted in) i forgot to say that rooted is in red letters, does that say annything ? i am bit confused
abati said:
hey men, i tried exactly what you said, but it stil the same after i flashed the kdz with CSE flash mode.
when i go back to download mode it stil says (user b97 - rooted in) i forgot to say that rooted is in red letters, does that say annything ? i am bit confused
Click to expand...
Click to collapse
Let me know, did you download KDZ ROM from http://lg-firmware-rom.com ?
You have to enter your IMEI to get you download link. It's a kdz file with around 1.6 Gigabytes.
Right?
Vogie said:
Use official LG KDZ ROMs and flash with LG Flash Tools 2014 :
http://forum.xda-developers.com/showthread.php?t=2797190
Flash mode: CSE flash
and dont forget to backup your sd card files. All will be wiped in this mode.
Official ROMs:
http://lg-firmware-rom.com
Click to expand...
Click to collapse
Vogie said:
Let me know, did you download KDZ ROM from http://lg-firmware-rom.com ?
You have to enter your IMEI to get you download link. It's a kdz file with around 1.6 Gigabytes.
Right?
Click to expand...
Click to collapse
yes that is correct
abati said:
yes that is correct
Click to expand...
Click to collapse
It doesn't make sense!
Stocks KDZ will make your phone like first day and repartition all partitions.
CES mode should works and Its delete all of your files.
BTW, It's just way I know to back to completely stock ROM.
Try again maybe works.
Vogie said:
It doesn't make sense!
Stocks KDZ will make your phone like first day and repartition all partitions.
CES mode should works and Its delete all of your files.
BTW, It's just way I know to back to completely stock ROM.
Try again maybe works.
Click to expand...
Click to collapse
i totally agree with you, but i already tried more then once.
I remeber that around 3 months ago i flashed an official kdz file and i tried to install root and recovery but it kept failing, so i installed an app called autrec and this app fixed everything .
Could this thing cause the problem ?
No, autorec just install recovery.
LG flash tools 2014 flash lg's recovery from KDZ file.
Vogie said:
No, autorec just install recovery.
LG flash tools 2014 flash lg's recovery from KDZ file.
Click to expand...
Click to collapse
i have also to mention, each time i went back to stock kdz i installed root checker, and the app kept saying root is not properly installed blabla, realy weird.
and yes i always used lg flash tools 2014 but nothing changes
abati said:
i have also to mention, each time i went back to stock kdz i installed root checker, and the app kept saying root is not properly installed blabla, realy weird.
and yes i always used lg flash tools 2014 but nothing changes
Click to expand...
Click to collapse
Hello abati.
The "rooted" tag in download mode is an error by LG, when they updated the LG G2 to KitKat. You can manually replace some files (rct.config), but even though it shows ROOTED in download mode, it isn't unless you manually rooted it after flashing a kdz.
If you're thinking of sending the phone in for a repair, I recall hearing that it doesn't have any effect at all.
But if it really bothers you that much you can flash a Jelly Bean ROM kdz (4.2.2) and UNROOTED will appear in dowload mode or just replace the files. But it has no practical value since your phone is not rooted.
Hope this helps!
vPro97 said:
Hello abati.
The "rooted" tag in download mode is an error by LG, when they updated the LG G2 to KitKat. You can manually replace some files (rct.config), but even though it shows ROOTED in download mode, it isn't unless you manually rooted it after flashing a kdz.
If you're thinking of sending the phone in for a repair, I recall hearing that it doesn't have any effect at all.
But if it really bothers you that much you can flash a Jelly Bean ROM kdz (4.2.2) and UNROOTED will appear in dowload mode or just replace the files. But it has no practical value since your phone is not rooted.
Hope this helps!
Click to expand...
Click to collapse
thnx m8, i was about to flash a jb rom actualy and see if it will change ^^ i will report back
abati said:
thnx m8, i was about to flash a jb rom actualy and see if it will change ^^ i will report back
Click to expand...
Click to collapse
It will change make sure you download and flash the correct model and storage (16 GB or 32 GB).
Also, it's easier to press thanks button than to say thanks - unless you're out of thanks for today, like I am
vPro97 said:
It will change make sure you download and flash the correct model and storage (16 GB or 32 GB).
Also, it's easier to press thanks button than to say thanks - unless you're out of thanks for today, like I am
Click to expand...
Click to collapse
hey m8 what you said is right, i flashed a kdz (D80210A_00) but it acted strangely cuz it kept rebooting and I then shutdown the phone with a combination of the buttons and then powered on but it kept rebooting. eventualy i checked in the download mode and there it said unrooted in white text.
eventualy i went back to kdz (D80220H_00) kitkat rom, and i factory reset everything and downloaded root checker, root checker says LG g2 device is not rooted. But when i went back to download mode and just see what it said ^^
It says rooted men -_- realy disturbing
did LG do this intentialy ? cuz if i am going to send tis device for repair the chance is very high that they will charge me the cost for the repair because my phone shows that i rooted.
how should i deal with this
abati said:
hey m8 what you said is right, i flashed a kdz (D80210A_00) but it acted strangely cuz it kept rebooting and I then shutdown the phone with a combination of the buttons and then powered on but it kept rebooting. eventualy i checked in the download mode and there it said unrooted in white text.
eventualy i went back to kdz (D80220H_00) kitkat rom, and i factory reset everything and downloaded root checker, root checker says LG g2 device is not rooted. But when i went back to download mode and just see what it said ^^
It says rooted men -_- realy disturbing
did LG do this intentialy ? cuz if i am going to send tis device for repair the chance is very high that they will charge me the cost for the repair because my phone shows that i rooted.
how should i deal with this
Click to expand...
Click to collapse
Like vPro97 said, "The "rooted" tag in download mode is an error by LG, when they updated the LG G2 to KitKat".
I suggest installing the Stock Jelly Bean .kdz file for your device, and then upgrading to KitKat ONLY via OTA.
d00lz said:
Like vPro97 said, "The "rooted" tag in download mode is an error by LG, when they updated the LG G2 to KitKat".
I suggest installing the Stock Jelly Bean .kdz file for your device, and then upgrading to KitKat ONLY via OTA.
Click to expand...
Click to collapse
But when i flashh jb kdz it keeps rebooting, totally nonsense if you ask me, but when i hold power and volume down for a couple sec. then the phone shuts down, after that i pressed the power butten but it still kept rebooting. I was able to enter the download mode and see for my self that it showed that it was not rooted, but besides that the phone always keeps rebooting.
After I flashed the kdz based on kitkat, i did not had anny problem at all, except that download mode shows that im rooted when in realtime its not.
abati said:
But when i flashh jb kdz it keeps rebooting, totally nonsense if you ask me, but when i hold power and volume down for a couple sec. then the phone shuts down, after that i pressed the power butten but it still kept rebooting. I was able to enter the download mode and see for my self that it showed that it was not rooted, but besides that the phone always keeps rebooting.
After I flashed the kdz based on kitkat, i did not had anny problem at all, except that download mode shows that im rooted when in realtime its not.
Click to expand...
Click to collapse
Hello again. Sorry for the delay, was busy reading!
After flashing a jelly bean KDZ you need to perform a hard reset if it bootloops.
Just press and hold volume down and power button till lg logo pops up, then release the buttons and then immediately press and hold volume down and power button again. Then follow the instructions.
If you flashed the correct file, you'll get an OTA update to kitkat
.
vPro97 said:
Hello again. Sorry for the delay, was busy reading!
After flashing a jelly bean KDZ you need to perform a hard reset if it bootloops.
Just press and hold volume down and power button till lg logo pops up, then release the buttons and then immediately press and hold volume down and power button again. Then follow the instructions.
If you flashed the correct file, you'll get an OTA update to kitkat
.
Click to expand...
Click to collapse
No problem MEN !!
Damnn your a Hero ^^ it worked !!
I had rooted my 4.4.4 with kingroot, changed to SuperSU with supersume and unrooted with SuperSU. Then Iwent back to stock (all official no Knox) with Odin (4.4.4 (A500FUXXU1AOB4_A500FUATO1AOB1_A500FUXXU1AOB4_HOME.tar.md5).
Then I went from stock to 5.0.2 (A500FUXXU1BOE6_A500FUATO1BOE1_A500FUXXU1BOE6_HOME.tar.md5) with Odin.
Actually after updating from 4.4.4 to 5.0.2 (with odin) the phone converted a lot of apps during startup - Did this also take minutes for you guys ?
All fine and phone quite fast, but no chance to root with Kingroot.
So I wanted back to 4.4.4 I used Odin again and flashed the 4.4.4 as written above. I did not tick reboot in Odin and so I powered off the phone after Odin said that all was flashed OK.
Now the phone is off (body is cold) and not repsonding to POWER+HOME+VOL+(or -).
After searching in xda it looks like I should have flashed all except the bootloader or flashed another BL first. I am confused and frustrated.
Hope you can help !
deleted
deleted
did you try a soft reset? remove battery and sim card for 30 seconds and put back.
!!! Bat is built in !!!
- Jig (300kOhm between Pin 4 an 5/GND on USB plug) works on S5mini immediately after plug in.
- On Tab S (built in bat like my A5) one has to press power additionally to the JIG plugged in.
Still no luck on A5 (SM-A500FU)
1 Still no idea what I did wrong
2 How could I empty the bat ??? (I did not measure any power on the USB plug, so no chance to drain it and its 2300mA fully loaded)
Does the screen comes up when you plug jn the charger?
no nothing
gggg said:
no nothing
Click to expand...
Click to collapse
Try leaving it on charger for a few mins or maybe an hour. If that doesnt make it react then its a hard brick and woukd suggest a repair center.
Sent from my SM-G850F
THX ... I ll tried that ... no change
Could you guys please give me some ideas, what possibly could have gone wrong !
gggg said:
THX ... I ll tried that ... no change
Could you guys please give me some ideas, what possibly could have gone wrong !
Click to expand...
Click to collapse
Probably you can t downgrade the bootloader... If you plug it to your pc does odin show something?
You said you cant boot in download mode that means your stuck in a hard brick that you cant recover by yourself. I managed to unbrick devices that at least could boot in download mode, i think only a repair center can help you
No nothing. No, not even the JIG does work. (Usally after plugging the JIG an hitting POWER or supplying power from charger through the JIG plug, it should go to download mode). So I will give up on it.
But I still would like to know what I did wrong ... lots of others seem to downgrade without an issue:
http://forum.xda-developers.com/galaxy-alpha/general/downgrade-5-0-2-to-4-4-4-t3141337, http://forum.xda-developers.com/galaxy-alpha/general/downgrade-5-0-2-to-4-4-4-t3125264
gggg said:
I had rooted my 4.4.4 with kingroot, changed to SuperSU with supersume and unrooted with SuperSU. Then Iwent back to stock (all official no Knox) with Odin (4.4.4 (A500FUXXU1AOB4_A500FUATO1AOB1_A500FUXXU1AOB4_HOME.tar.md5).
Then I went from stock to 5.0.2 (A500FUXXU1BOE6_A500FUATO1BOE1_A500FUXXU1BOE6_HOME.tar.md5) with Odin.
Actually after updating from 4.4.4 to 5.0.2 (with odin) the phone converted a lot of apps during startup - Did this also take minutes for you guys ?
All fine and phone quite fast, but no chance to root with Kingroot.
So I wanted back to 4.4.4 I used Odin again and flashed the 4.4.4 as written above. I did not tick reboot in Odin and so I powered off the phone after Odin said that all was flashed OK.
Now the phone is off (body is cold) and not repsonding to POWER+HOME+VOL+(or -).
After searching in xda it looks like I should have flashed all except the bootloader or flashed another BL first. I am confused and frustrated.
Hope you can help !
Click to expand...
Click to collapse
You were meant to downgrade after making a full reset. However, failing to do that will still allow the phone to boot and it will be a soft brick. And recovery and boatloader shouldn't be affected and be perfectly functional.
Can you boot into recovery? If you can, do a full wipe and then install the ROM you desire.
droidqwerty said:
...
Click to expand...
Click to collapse
This is what I also dont understand .... because as I said no reaction at all (no recovery, download mode, not even with a JIG) ....
gggg said:
This is what I also dont understand .... because as I said no reaction at all (no recovery, download mode, not even with a JIG) ....
Click to expand...
Click to collapse
You mean no logo or even no turn-on vibration?
droidqwerty said:
You mean no logo or even no turn-on vibration?
Click to expand...
Click to collapse
yes
What happens when you plug it into charger?
My final opininon is that it needs service.
Sent from my SM-G850F
this downgrade from 502 to 444 than again 502 you have mess up with bootloader ,
I dont know who bootloader 502 or 444 FW but that you yourself make mess is true
all recommend avoiding the frequent downgrade of FW
hensk said:
this downgrade from 502 to 444 than again 502 you have mess up with bootloader ,
I dont know who bootloader 502 or 444 FW but that you yourself make mess is true
all recommend avoiding the frequent downgrade of FW
Click to expand...
Click to collapse
I went 4.4.4>5.0.2>4.4.4 - no more !
1 Can you please explain more in detail what caused the trouble in your opinion
2 How can this be avoided = how to to that with Odin / how to just flash Stock.tar without or with another Bootloader ?
3 Which bootloaders (primary and secondary??) should be flashed togerther with 4.4.4 or 5.0.2 ?
You should factory reset before downgrading, otherwise your phone would be soft bricked
I'm on an N9005. I did not know about Knox when I first got it (came from an S3) and flashed TWRP and Cyanogen (unofficial v13 MM). Funnily enough I tripped Knox 0x1. Since then the phone comes up as custom, etc. and no matter what I do it stays that way, even on completely stock ROM. I have tried Triangle Away but it made no difference (stock rom, rooted with CF Auto Root).
I'm on Arch Linux so I flash everything via Heimdall. Everything else flashes fine, but the bootloader and modem flashes will not stick. I have tried on a Windows PC with Odin as well and didn't work with Odin either. I have tried the trick of flashing and then booting straight back into DL mode and flashing again, but that did not work either.
I have tried flashing the BL/BB on multiple different ROMS, didn't work. I even experimented with flashing the stock rom but with the updated BL/BB files - didn't work and bootlooped so I had to reflash stock. I've tried a different kernel, no difference.
It keeps the original original BL/BB no matter what I do. This phone was originally bought in another country and thus far I have only been able to flash it with the stock rom of that country. If I use my own country's (New Zealand) stock rom, it boot loops.
Could it be refusing this particular BL and BB build? Should I try an older build and see if that works? Or is this a problem related to something else? How can I fix this?
Thanks in advance!
You need to power off the phone completely before flashing them. If doesn't work remove battery for a few seconds then retry. Do not flash with reboot into download mode from rom's power menu.
Sent from my SM-N920C
Thorned_Rose said:
I'm on an N9005. I did not know about Knox when I first got it (came from an S3) and flashed TWRP and Cyanogen (unofficial v13 MM). Funnily enough I tripped Knox 0x1. Since then the phone comes up as custom, etc. and no matter what I do it stays that way, even on completely stock ROM. I have tried Triangle Away but it made no difference (stock rom, rooted with CF Auto Root).
I'm on Arch Linux so I flash everything via Heimdall. Everything else flashes fine, but the bootloader and modem flashes will not stick. I have tried on a Windows PC with Odin as well and didn't work with Odin either. I have tried the trick of flashing and then booting straight back into DL mode and flashing again, but that did not work either.
I have tried flashing the BL/BB on multiple different ROMS, didn't work. I even experimented with flashing the stock rom but with the updated BL/BB files - didn't work and bootlooped so I had to reflash stock. I've tried a different kernel, no difference.
It keeps the original original BL/BB no matter what I do. This phone was originally bought in another country and thus far I have only been able to flash it with the stock rom of that country. If I use my own country's (New Zealand) stock rom, it boot loops.
Could it be refusing this particular BL and BB build? Should I try an older build and see if that works? Or is this a problem related to something else? How can I fix this?
Thanks in advance!
Click to expand...
Click to collapse
Flash bootloader twice without reboot.
Don't let the phone get into OS.
Remove the battery and flash the boot loader twice. It will stick.
Telling from experience
Rosli59564 said:
You need to power off the phone completely before flashing them. If doesn't work remove battery for a few seconds then retry. Do not flash with reboot into download mode from rom's power menu.
Sent from my SM-N920C
Click to expand...
Click to collapse
vishnu vijay said:
Flash bootloader twice without reboot.
Don't let the phone get into OS.
Remove the battery and flash the boot loader twice. It will stick.
Telling from experience
Click to expand...
Click to collapse
Thank you!!!! Pulling the battery was the missing piece!
I was powering off the phone fully before booting into D/L and then flashing (twice over). Removing the battery beforehand has finally made it stick. Thank you muchly! This was driving me nut so really appreciate you taking the time in aswering
Thorned_Rose said:
Thank you!!!! Pulling the battery was the missing piece!
I was powering off the phone fully before booting into D/L and then flashing (twice over). Removing the battery beforehand has finally made it stick. Thank you muchly! This was driving me nut so really appreciate you taking the time in aswering
Click to expand...
Click to collapse
I am glad it worked. Cheers
vishnu vijay said:
Flash bootloader twice without reboot.
Don't let the phone get into OS.
Remove the battery and flash the boot loader twice. It will stick.
Telling from experience
Click to expand...
Click to collapse
Do you know if this still takes effect on new(er) phones? I have an S5 Mini. I'm flashing with Debian heimdall (just param.bin, i'm trying to change the bootlogo). I took out the battery before booting to D/L, and flashed twice (removing battery between flashes). Heimdall reports success, and if I pull the partition with root+dd, I can see my changes. It just doesn't change the logo.:crying: This is driving me crazy,
Thanks in advance,
Hackintosh5
P.S. Please tell me if you think this should be a separate thread!
hackintosh5 said:
Do you know if this still takes effect on new(er) phones? I have an S5 Mini. I'm flashing with Debian heimdall (just param.bin, i'm trying to change the bootlogo). I took out the battery before booting to D/L, and flashed twice (removing battery between flashes). Heimdall reports success, and if I pull the partition with root+dd, I can see my changes. It just doesn't change the logo.:crying: This is driving me crazy,
Thanks in advance,
Hackintosh5
P.S. Please tell me if you think this should be a separate thread!
Click to expand...
Click to collapse
Instead of booting into the OS have you tried booting into recovery.
Volume home and volume plus combo
Usually there are some patches so the OS doesn't overwrite the Recovery.
vishnu vijay said:
Instead of booting into the OS have you tried booting into recovery.
Volume home and volume plus combo
Usually there are some patches so the OS doesn't overwrite the Recovery.
Click to expand...
Click to collapse
No, you've misunderstood. I'm trying to flash a bootlogo to the PARAM (.bin) partition, not recovery. Should I try to make an odin package?
I would ask in your phones forum.
Most of Notes cannot modify param.bin
vishnu vijay said:
Flash bootloader twice without reboot.
Don't let the phone get into OS.
Remove the battery and flash the boot loader twice. It will stick.
Telling from experience
Click to expand...
Click to collapse
i have the same problem just for bootloader. cp is ok.
i've turned off my phone n9005 and pull out battery and turn on n download mode and flashed BL file in BL section twice without reboot and my bootloader didn't change. any suggestion?
titan-computer said:
i have the same problem just for bootloader. cp is ok.
i've turned off my phone n9005 and pull out battery and turn on n download mode and flashed BL file in BL section twice without reboot and my bootloader didn't change. any suggestion?
Click to expand...
Click to collapse
Use Odin 3.04,
Maybe the BL you tryna stick is older than the one you already have?
Flash, reboot & pull off the battery when it begins to load bootanimation.
Do it again for 3 times at least.
I could downgrade to KitKat bootloader this way.
Mohamedkam000 said:
Use Odin 3.04,
Maybe the BL you tryna stick is older than the one you already have?
Flash, reboot & pull off the battery when it begins to load bootanimation.
Do it again for 3 times at least.
I could downgrade to KitKat bootloader this way.
Click to expand...
Click to collapse
doesn't work.
yeas. it's older than my current bootloader.
i did all things with odin 3.04 but didn't change the bootloader.
in odin 3.04 it has an option "phone bootloader update", do i need to check this? default is unchecked.
titan-computer said:
doesn't work.
yeas. it's older than my current bootloader.
i did all things with odin 3.04 but didn't change the bootloader.
in odin 3.04 it has an option "phone bootloader update", do i need to check this? default is unchecked.
Click to expand...
Click to collapse
Of course you need to check it.
Other than that, is the bootloader packed with NON-HLOS.bin or just the *.mbn files?
I mean, is it ~7 MB in size or ~1.7 MB?
You may need to flash a modem file as well to enforce the BL?
If all that didn't work, there's one proved way that will work, use a box (software).
Mohamedkam000 said:
Of course you need to check it.
Other than that, is the bootloader packed with NON-HLOS.bin or just the *.mbn files?
I mean, is it ~7 MB in size or ~1.7 MB?
You may need to flash a modem file as well to enforce the BL?
If all that didn't work, there's one proved way that will work, use a box (software).
Click to expand...
Click to collapse
no it's just mbn files almost 1.7 MB.
i've checked boot loader update and didn't work again. modem got update at the first time but BL doesn't.
what is this? box software?
titan-computer said:
no it's just mbn files almost 1.7 MB.
i've checked boot loader update and didn't work again. modem got update at the first time but BL doesn't.
what is this? box software?
Click to expand...
Click to collapse
Windows software, named Z3X Box, download it and update your bootloader with, it will definitely success.
Hello guys, I noticed this morning that MM was officially released today. I followed the steps on to update my phone. I downloaded the rom for 551ml put it on my root of my internal storage, after that a pop up showed that there was a system update. I did the update and now my phone wont turn on now. It vibes twice and nothing comes on the screen. I have no idea how to fix it. I was on the latest firmware that system update would give me (184). If someone isn't busy could they possibly help me out. thx..
Same issue here, have you found a solution yet?
arturocr said:
Same issue here, have you found a solution yet?
Click to expand...
Click to collapse
tyring a guide atm but links seem to be outdated. I managed to get in fastboot or whatever its called when you can boot in to recovery. but from there I cant do anything.
You cant get into recovery after fastboot?
Sent from my ASUS_Z00AD using XDA Premium HD app
same problem ,
so im from cm 13 lastest build , and then i wipe data from twrp , after that i directly flash MM offical rom and its done without any problem. the problem start after i reboot system. my phone just vibrating twice with no lights led on , no screen on , no asus logo , can't go to recovery nor fastboot just keep restarting i guess because after a couple minute it vibrate again.
when i charge it wont show charging battrey , only stuck at battrey logo with zap with no charging animation.
don't have any clue. can anyone help ?
try to connect to pc but only show "moorefield" with (?).
sorry for my bad english.
Same for me...
baonxxx said:
same problem ,
so im from cm 13 lastest build , and then i wipe data from twrp , after that i directly flash MM offical rom and its done without any problem. the problem start after i reboot system. my phone just vibrating twice with no lights led on , no screen on , no asus logo , can't go to recovery nor fastboot just keep restarting i guess because after a couple minute it vibrate again.
when i charge it wont show charging battrey , only stuck at battrey logo with zap with no charging animation.
don't have any clue. can anyone help ?
try to connect to pc but only show "moorefield" with (?).
sorry for my bad english.
Click to expand...
Click to collapse
I think mm system.img boot.img splashcreen.img need mm bootloder to run and at the moment twrp doesnt work with it, if you install mm via twrp you only updating these img and bootloader still lp that causes your phone cant boot. (Correct me if im wrong)
So now you need xfstk downloader to recover your fastboot and then flash .194 raw firmware using asus flash tool then adb sideload mm firmware from stock .194 recovery, theres guide how to do that in here but im forget where
Sorry my english are bad too..
miku1024 said:
I think mm system.img boot.img splashcreen.img need mm bootloder to run and at the moment twrp doesnt work with it, if you install mm via twrp you only updating these img and bootloader still lp that causes your phone cant boot. (Correct me if im wrong)
So now you need xfstk downloader to recover your fastboot and then flash .194 raw firmware using asus flash tool then adb sideload mm firmware from stock .194 recovery, theres guide how to to that in here but im forget where
Sorry my english are bad too..
Click to expand...
Click to collapse
how does make xfstk work ? don't have idea how. it just show nothing after i open xfstk , have a reference link ?
baonxxx said:
same problem ,
so im from cm 13 lastest build , and then i wipe data from twrp , after that i directly flash MM offical rom and its done without any problem. the problem start after i reboot system. my phone just vibrating twice with no lights led on , no screen on , no asus logo , can't go to recovery nor fastboot just keep restarting i guess because after a couple minute it vibrate again.
when i charge it wont show charging battrey , only stuck at battrey logo with zap with no charging animation.
don't have any clue. can anyone help ?
try to connect to pc but only show "moorefield" with (?).
sorry for my bad english.
Click to expand...
Click to collapse
baonxxx said:
how does make xfstk work ? don't have idea how. it just show nothing after i open xfstk , have a reference link ?
Click to expand...
Click to collapse
I found the link!
You need You need asus usb and intel soc drivers
Heres
http://forum.xda-developers.com/zenfone2/general/guide-fix-bricked-ze550ml-ze551ml-usb-t3405840
Try this: http://forum.xda-developers.com/zenfone2/general/guide-how-to-update-to-official-mm-t3452082
miku1024 said:
I think mm system.img boot.img splashcreen.img need mm bootloder to run and at the moment twrp doesnt work with it, if you install mm via twrp you only updating these img and bootloader still lp that causes your phone cant boot. (Correct me if im wrong)
So now you need xfstk downloader to recover your fastboot and then flash .194 raw firmware using asus flash tool then adb sideload mm firmware from stock .194 recovery, theres guide how to do that in here but im forget where
Sorry my english are bad too..
Click to expand...
Click to collapse
I used XFSTK to upload firmware etc... but after upload firmware, the phone will vibrate twice and download of OS will not start... the soft will try 20 attemps to connect with the phone and the OS part can't be download on the phone... I'm stick at this point.
Hello guys, i'm trying to unbrick my phone, i'm following this guide http://forum.xda-developers.com/zenf...l-usb-t3405840 but when i get to the end of te install of intelSoC my device is detected as Moorefield for like 4-5 seconds and then it disappears. I've been trying to solve this for like 4 hours now, a little help would be much appreciated.
quarterbreed said:
tyring a guide atm but links seem to be outdated. I managed to get in fastboot or whatever its called when you can boot in to recovery. but from there I cant do anything.
Click to expand...
Click to collapse
try this if you unable to flash
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
sukhwant717 said:
try this if you unable to flash
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Click to expand...
Click to collapse
I did this morning and it worked. Im on 6.0.1 now, I guess the cause of my brick was that I had TWRP installed. Now I know next time to remove it before updating lol.
quarterbreed said:
I did this morning and it worked. Im on 6.0.1 now, I guess the cause of my brick was that I had TWRP installed. Now I know next time to remove it before updating lol.
Click to expand...
Click to collapse
glad to know that it worked. but sad to know that despite that you didn't hit thanks
quarterbreed said:
I did this morning and it worked. Im on 6.0.1 now, I guess the cause of my brick was that I had TWRP installed. Now I know next time to remove it before updating lol.
Click to expand...
Click to collapse
If you don't need to use twrp everyday (maybe just a backup from time to time) you'd better keep stock recovery and whenever you need something from twrp, you just boot into it without flashing with the usual "fastboot boot twrp.img" command. That way if you ever upgrade again you don't have to remember whether you removed twrp before. But that's just an opinion, since if done that way, you'd need to have yor phione hooked to a computer to get into twrp, an that's not always possible.
thanks
quarterbreed said:
I did this morning and it worked. Im on 6.0.1 now, I guess the cause of my brick was that I had TWRP installed. Now I know next time to remove it before updating lol.
Click to expand...
Click to collapse
sukhwant717 said:
try this if you unable to flash
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Click to expand...
Click to collapse
that link saved my phone, thanks man
sukhwant717 said:
glad to know that it worked. but sad to know that despite that you didn't hit thanks
Click to expand...
Click to collapse
I just hit thanks now, I was at my limit of 8 at the time.
Just got November ota update in 60mb i am just curious to know if it is gonna lock the bootloader.
UPDATE-/ BOOTLOADER STILL UNLOCKED I TESTED & DOWNGRADED TO 5.1.1 OK1 .
I just received it as well. I use my phone for work so it's encrypted but could you try to downgrade and let's us know what happened
Yes, you can still downgrade to 4.4.4 with the new update
This update should give me enough time to read the details of the update before it reboots my phone in the 25 seconds. At that point, we don't have the ability to "abort" or decline the agreement anyway.
Note 4 tmo, downloads the 60mb update, phone enters recovery mode then i get "update failed phone will recover the original configuration" .
I'm full stock, no root, no custom recovery no nothing. Anyone could help me?
I'd recommend you use the desktop version of ODIN with the latest FULL ROM to restore your device (without wiping) to the version before the OTA update. You can then try the update process again.
enian.doda said:
Note 4 tmo, downloads the 60mb update, phone enters recovery mode then i get "update failed phone will recover the original configuration" .
I'm full stock, no root, no custom recovery no nothing. Anyone could help me?
Click to expand...
Click to collapse
I encountered the same error last night. I held POWER + VOLUME DOWN to boot into Recovery mode, then I rebooted to System. My phone went through the app optimization process (you know, the screen that you'd see after wiping the Cache/Dalvik Cache).
I assumed that the update failed, but when I checked "About Device," I noticed that it now has the November 1, 2016 security patch (Baseband Version N910TUVS2EPK2).
Anonymously_Unknown said:
I'd recommend you use the desktop version of ODIN with the latest FULL ROM to restore your device (without wiping) to the version before the OTA update. You can then try the update process again.
Click to expand...
Click to collapse
ru_benz said:
I encountered the same error last night. I held POWER + VOLUME DOWN to boot into Recovery mode, then I rebooted to System. My phone went through the app optimization process (you know, the screen that you'd see after wiping the Cache/Dalvik Cache).
I assumed that the update failed, but when I checked "About Device," I noticed that it now has the November 1, 2016 security patch (Baseband Version N910TUVS2EPK2).
Click to expand...
Click to collapse
Sadly mine didn't, as it gave the update failed it reboot normally without app optimization, checked about phone, no changes.
I gave up and updated through Smart Switch... althought the "dm-verification " error still present.
enian.doda said:
Sadly mine didn't, as it gave the update failed it reboot normally without app optimization, checked about phone, no changes.
I gave up and updated through Smart Switch... althought the "dm-verification " error still present.
Click to expand...
Click to collapse
How do u update firmware through smart switch
Sent from my SM-N910T using XDA-Developers mobile app
Anonymously_Unknown said:
This update should give me enough time to read the details of the update before it reboots my phone in the 25 seconds. At that point, we don't have the ability to "abort" or decline the agreement anyway.
Click to expand...
Click to collapse
I noticed it said something about gear3 and RCS messaging system. Didn't have time to read the rest of the change log
SelfElevated2 said:
How do u update firmware through smart switch
Sent from my SM-N910T using XDA-Developers mobile app
Click to expand...
Click to collapse
With phone ON, connect phone to pc through usb, amart switch will tell you automatically THERE'S AN UPDATE AVAILABLE.
Full rom n910tuvs2epk2
Anonymously_Unknown said:
I'd recommend you use the desktop version of ODIN with the latest FULL ROM to restore your device (without wiping) to the version before the OTA update. You can then try the update process again.
Click to expand...
Click to collapse
I just download this from sammobile. Just want to share it...use at your own risk. https://mega.nz/#!oMdHRYaa!vRIN02PsMG6ozSeiRRJ-OBWf0a88x7gVo768my7wpO8
murayoshi said:
I just download this from sammobile. Just want to share it...use at your own risk. https://mega.nz/#!oMdHRYaa!vRIN02PsMG6ozSeiRRJ-OBWf0a88x7gVo768my7wpO8
Click to expand...
Click to collapse
Thanks for sharing
Did you tested it ?
Trex888 said:
Thanks for sharing
Did you tested it ?
Click to expand...
Click to collapse
You're welcome. Not yet because i am in the middle of setting up RamRom when I download it. I am still playing with it. Probably later
murayoshi said:
You're welcome. Not yet because i am in the middle of setting up RamRom when I download it. I am still playing with it. Probably later
Click to expand...
Click to collapse
I flashed the rom through odin, all good.
Still, dm-verification error hunts my phone when entering recovery.
Still no one has a solution to the dm error?
enian.doda said:
I flashed the rom through odin, all good.
Still, dm-verification error hunts my phone when entering recovery.
Still no one has a solution to the dm error?
Click to expand...
Click to collapse
To get rid of it flash custom recovery.
Trex888 said:
To get rid of it flash custom recovery.
Click to expand...
Click to collapse
This thing is i wanted a full stock rom, so to be able to update ota as soon as available.
Custom recovery doesnt offer that.
enian.doda said:
This thing is i wanted a full stock rom, so to be able to update ota as soon as available.
Custom recovery doesnt offer that.
Click to expand...
Click to collapse
Don't take ota updates whenever updates came out sammobiles.com release whole firmware with update.
I had same issue with n910t my i got drk error and i don't see any working method so far the only way is to change motherboard .so whenever i want to update i simply flash whole firmware via odin
Hope that helps
Trex888 said:
Don't take ota updates whenever updates came out sammobiles.com release whole firmware with update.
I had same issue with n910t my i got drk error and i don't see any working method so far the only way is to change motherboard .so whenever i want to update i simply flash whole firmware via odin
Hope that helps
Click to expand...
Click to collapse
Well, I also used odin until now. The fact that you tell me there's no "working method " assures me that you made your searches like I did and found nothing.
Trex888 said:
Don't take ota updates whenever updates came out sammobiles.com release whole firmware with update.
I had same issue with n910t my i got drk error and i don't see any working method so far the only way is to change motherboard .so whenever i want to update i simply flash whole firmware via odin
Hope that helps
Click to expand...
Click to collapse
I have custom ROM and Custom Recovery TWRP.
Will updating the Modem and Bootloader cause me to have to reinstall the ROMS?
Thanks in advance