PROBLEM SOLVED USE LATEST TWRP BUILD BUT BE CAREFUL WITH FLASHING ROMs COZ THEY STILL DOES NOT SUPPORT THIS SCREEN PANEL​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
tried both dummy image and straight up booting nothing works
just flashing miui with unlocked sign and then just straight nothing
official twrp
arb 4
it just not booting
edit: just flashed latest dev rom and still nothing
here are some dmesg logs and hardware:
https://i.imgur.com/giIki1W.png
https://i.imgur.com/v8jyDkQ.png
https://i.imgur.com/UAcukty.png
https://drive.google.com/open?id=1M8V80-gKEpnxRgy1-iUGt9Oj76RDqGD2
I was having the same issues using a Windows PC. I tried on my Mac this morning and worked right away.
Maybe try using Ubuntu Live if you don't have a Mac available.
1. Download TWRP
From Terminal:
2. Install Android Platform Tools
Code:
sudo apt-get install android-platform-tools
3. Reboot phone to bootloader(fastboot) I find it easiest just to use ADB
Code:
adb reboot bootloader
4. Change directory to Downloads
Code:
CD Downloads
5. Use Fastboot to boot to TWRP
Code:
fastboot boot twrp-3.2.3-1-whyred.img
If you need to transfer downloaded files to your phone from Mac/Linux, just use adb push in terminal. (note, file names and directories are case sensitive)
Code:
adb push [I]complete-file-name.zip[/I] /sdcard/
I know this is a big hassle, but still better than nothing
daggorlad said:
I was having the same issues using a Windows PC. I tried on my Mac this morning and worked right away.
Click to expand...
Click to collapse
it doesn't work
after fastboot boot twrp.img screen flashes miui logo and unlocked for couple seconds and then goes black
NiNoX14 said:
it doesn't work
after fastboot boot twrp.img screen flashes miui logo and unlocked for couple seconds and then goes black
Click to expand...
Click to collapse
Sounds like you were having a slightly different issue than I was. Mine was just sticking on downloading image. Sorry it was of no help.
daggorlad said:
Sounds like you were having a slightly different issue than I was. Mine was just sticking on downloading image. Sorry it was of no help.
Click to expand...
Click to collapse
thanks
no problems
i don't know why my phone don't want to be like the others
NiNoX14 said:
thanks
no problems
i don't know why my phone don't want to be like the others
Click to expand...
Click to collapse
maybe try using XMT to reflash MIUI 10 then reattempting
NiNoX14 said:
thanks
no problems
i don't know why my phone don't want to be like the others
Click to expand...
Click to collapse
I have the same problem, Please Help me!!!
NiNoX14 said:
thanks
no problems
i don't know why my phone don't want to be like the others
Click to expand...
Click to collapse
twrp unzip run install
https://drive.google.com/open?id=1XLncxs4UDcSxiefQomwT4yZpWthwfAES
---------- Post added at 07:09 AM ---------- Previous post was at 07:07 AM ----------
duckiemhy said:
I have the same problem, Please Help me!!!
Click to expand...
Click to collapse
use twrp in link
raptorddd said:
twrp unzip run install
https://drive.google.com/open?id=1XLncxs4UDcSxiefQomwT4yZpWthwfAES
---------- Post added at 07:09 AM ---------- Previous post was at 07:07 AM ----------
use twrp in link
Click to expand...
Click to collapse
still black screen after flashing
nothing happens
bump
NiNoX14 said:
bump
Click to expand...
Click to collapse
Which HW do you have? (phone).
Which FW?
On my case, during the first boot after TWRP, the only way I could boot in recovery was using the buttons:
fastboot.exe flash recovery twrp\twrp.img (should say sending recovery okay, writing recovery okay, it did for you)
fastboot.exe reboot
quickly hold volume UP + power button (how until it should show TWRP, if it shows some chinese boot, redo the fastboot flash)
htchd2sucks said:
Which HW do you have? (phone).
Which FW?
On my case, during the first boot after TWRP, the only way I could boot in recovery was using the buttons:
fastboot.exe flash recovery twrp\twrp.img (should say sending recovery okay, writing recovery okay, it did for you)
fastboot.exe reboot
quickly hold volume UP + power button (how until it should show TWRP, if it shows some chinese boot, redo the fastboot flash)
Click to expand...
Click to collapse
there is screenshots of hardware in OP
NiNoX14 said:
there is screenshots of hardware in OP
Click to expand...
Click to collapse
Well... I saw some screenshot with some HW related info but I need you to tell exactly (I don't know all devices references!)
Which phone, exactly! I saw referenced to whyred in the screenshots, but do tell!
I'm thinking maybe it's a chinese version? I saw some Russian in your text, maybe you are trying something incorrect.
Just tell, I'll try to help you now.
What is your TWRP version? I saw you renamed it in twrp.img. What is the full version?
---------- Post added at 05:55 PM ---------- Previous post was at 05:36 PM ----------
What FW is that, how do you got this 660_GEN_PACK-1.172780.3.174030.1?
It doesn't corresponds to any stable version I know...
htchd2sucks said:
Well... I saw some screenshot with some HW related info but I need you to tell exactly (I don't know all devices references!)
Which phone, exactly! I saw referenced to whyred in the screenshots, but do tell!
I'm thinking maybe it's a chinese version? I saw some Russian in your text, maybe you are trying something incorrect.
Just tell, I'll try to help you now.
What is your TWRP version? I saw you renamed it in twrp.img. What is the full version?
---------- Post added at 05:55 PM ---------- Previous post was at 05:36 PM ----------
What FW is that, how do you got this 660_GEN_PACK-1.172780.3.174030.1?
It doesn't corresponds to any stable version I know...
Click to expand...
Click to collapse
Xiaomi Redmi Note 5
whyred - short name for this phone
what else do you need ?
https://dl.twrp.me/whyred/twrp-3.2.3-0-whyred.img.html
NiNoX14 said:
Xiaomi Redmi Note 5
whyred - short name for this phone
what else do you need ?
https://dl.twrp.me/whyred/twrp-3.2.3-0-whyred.img.html
Click to expand...
Click to collapse
So it's the global version, are you sure? It matters for the FW...
I know whyred is the shortname, but in fact it's also for the RN5 pro (indian version).
So you are using the latest TWRP then...
Have you tried what I told you about holding buttons? I told you the steps, tell me exactly what you see after the reboot.
htchd2sucks said:
So it's the global version, are you sure? It matters for the FW...
I know whyred is the shortname, but in fact it's also for the RN5 pro (indian version).
So you are using the latest TWRP then...
Have you tried what I told you about holding buttons? I told you the steps, tell me exactly what you see after the reboot.
Click to expand...
Click to collapse
yes i've tried and still twrp not booting, same old blackscreen
definitely global version
but somehow my manual and other papers were in spanish or something similar anything but english
there is recovery.log: https://paste.omnirom.org/view/e2d3ea1f
NiNoX14 said:
yes i've tried and still twrp not booting, same old blackscreen
definitely global version
but somehow my manual and other papers were in spanish or something similar anything but english
there is recovery.log: https://paste.omnirom.org/view/e2d3ea1f
Click to expand...
Click to collapse
its weird because "by defaul" you shopuzld have chinese recovery...
What about micro sd card, remove any if you have.
By the way, when I hold vol up and power button for 15 seconds until I see the TWRP logo, it goes black a second after.
I know I can release the buttons and press power once again to light the screen again.
---------- Post added at 07:01 PM ---------- Previous post was at 06:54 PM ----------
By the way it's possible that TWRP is too old for your latest firmware because you appears to have "xxxxx17xxxxxx" and I saw the latest stable is only "xxxxxx16xxxxxxx".
I would suggest, since you have ARBV4 and can't easily install older, to try another recovery, such as:
https://forum.xda-developers.com/redmi-note-5-pro/development/twrp-orangefox-recovery-project-t3837547
or
https://forum.xda-developers.com/redmi-note-5-pro/development/recovery-red-wolf-recovery-project-t3766997
You can see an example bug report here:
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1314
FYI, there's even a workaround, to replace some blob vendor file.
I also have other issues with TWRP, I have the impression this TWRP for whyred is "paused" or even maybe stopped.
---------- Post added at 07:18 PM ---------- Previous post was at 07:01 PM ----------
I updated the thread of Whyred TWRP for you.
He has a latest version there, maybe it contains updated blobs:
twrp-3.2.3-1-whyred.img:
https://www.androidfilehost.com/?fid=1322778262904029848
https://forum.xda-developers.com/redmi-note-5-pro/development/recovery-twrp-3-2-1-0-whyred-t3766113
htchd2sucks said:
its weird because "by defaul" you shopuzld have chinese recovery...
What about micro sd card, remove any if you have.
Click to expand...
Click to collapse
i've tried without sdcard and there was no change
i have default Mi Recovery
it basically can be booted after you boot into system > turn off > use buttons to boot recovery
more logs
https://paste.omnirom.org/view/d03a276b
https://paste.omnirom.org/view/133173e9
folder with logs without sd: https://drive.google.com/open?id=1VBTmObqpUrBv9IVk29OQ-pFpmAH2eLzS
htchd2sucks said:
its weird because "by defaul" you shopuzld have chinese recovery...
What about micro sd card, remove any if you have.
By the way, when I hold vol up and power button for 15 seconds until I see the TWRP logo, it goes black a second after.
I know I can release the buttons and press power once again to light the screen again.
---------- Post added at 07:01 PM ---------- Previous post was at 06:54 PM ----------
By the way it's possible that TWRP is too old for your latest firmware because you appears to have "xxxxx17xxxxxx" and I saw the latest stable is only "xxxxxx16xxxxxxx".
I would suggest, since you have ARBV4 and can't easily install older, to try another recovery, such as:
https://forum.xda-developers.com/redmi-note-5-pro/development/twrp-orangefox-recovery-project-t3837547
or
https://forum.xda-developers.com/redmi-note-5-pro/development/recovery-red-wolf-recovery-project-t3766997
You can see an example bug report here:
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1314
FYI, there's even a workaround, to replace some blob vendor file.
I also have other issues with TWRP, I have the impression this TWRP for whyred is "paused" or even maybe stopped.
---------- Post added at 07:18 PM ---------- Previous post was at 07:01 PM ----------
I updated the thread of Whyred TWRP for you.
He has a latest version there, maybe it contains updated blobs:
twrp-3.2.3-1-whyred.img:
https://www.androidfilehost.com/?fid=1322778262904029848
https://forum.xda-developers.com/redmi-note-5-pro/development/recovery-twrp-3-2-1-0-whyred-t3766113
Click to expand...
Click to collapse
orange installing from twrp so i cant use that
redwolf same - no effect
i don't know how to do this "FYI, there's even a workaround, to replace some blob vendor file."
ill be googling this, if you can link me tutorial or smthing
ill try new version of twrp later ill update this thread
thanks for help by the way
NiNoX14 said:
orange installing from twrp so i cant use that
redwolf same - no effect
i don't know how to do this "FYI, there's even a workaround, to replace some blob vendor file."
ill be googling this, if you can link me tutorial or smthing
ill try new version of twrp later ill update this thread
thanks for help by the way
Click to expand...
Click to collapse
Sorry, I don't know how to actually replace the vendor file myself. Maybe it's about extracting the content of the "twrp.img", replace the file (given in the workaround) and recreate a .img?
I haven't looked at that.
Edit:
I just tried to extract the .img, it extracts only a big file, maybe binary? I don't know how to open.
I am talking in the livechat of TWRP in freenode, for you, right now, but nobody replies to help (they hardly reply to me there).
I updated the TWRP thread to ask if it's dead or paused, the dev hasn't posted since 22 october. TWRP for whyred seems abandonned or paused.
Try Orangefox anyway, even if it's from TWRP; they have updated plenty of things, such as the "PIN/PATTERN" (an issue I have with latest TWRP, which is not in ORangeFox recovery).
Or yes, try the latest twrp-3.2.3-1-whyred.img (it has no changelogs, I don't know the changes).
---------- Post added at 07:49 PM ---------- Previous post was at 07:33 PM ----------
Looks like you created a bug report #1335 in githubTWRP, I think it's related to #1314 (if so, we will probably need to wait for an update).
Related
Ok i've flashed 100's of boot.img's but i've never encountered this.
Fastboot flash boot boot.img
sending
Phone show the little loading bar. Nothing happens. I waited about 3 minutes and still nothing. So i stopped it. Tried multiple times same thing. Used a different .img same thing. Googled and searched the website for it and found nothing. I have all my req drivers for my htc and fastboot. I have my rom on the phone and installed i just need to get my fastboot to send my boot.img.....
My phone is Virgin mobile usa CDMA btw.
Are you bootloader unlocked,?
Did you make sure you have ADB AndroidDebuggingBridge enabled?
---------- Post added at 10:33 PM ---------- Previous post was at 10:30 PM ----------
Also, first send cmd
Code:
fastboot devices
and make sure it recognizes your phone. It will return your phone serial number if it does
russellvone said:
Are you bootloader unlocked,?
Did you make sure you have ADB AndroidDebuggingBridge enabled?
---------- Post added at 10:33 PM ---------- Previous post was at 10:30 PM ----------
Also, first send cmd
Code:
fastboot devices
and make sure it recognizes your phone. It will return your phone serial number if it does
Click to expand...
Click to collapse
Yeah solved. Thanks.
Android#! said:
Yeah solved. Thanks.
Click to expand...
Click to collapse
People with the same problem will be grateful for the solution, even if its because you missed a step. Google indexes this forum quite quickly, so they will end up here. Could you share your solution so that others can benefit from your problem resolution.
sent from a phone that's running a rom
mrcorey said:
People with the same problem will be grateful for the solution, even if its because you missed a step. Google indexes this forum quite quickly, so they will end up here. Could you share your solution so that others can benefit from your problem resolution.
sent from a phone that's running a rom
Click to expand...
Click to collapse
Wrong Gapps version was the solution for me. Was really weird. Also don't try to install fm radio manually. That was the original cause.
HAS BEEN FIXED...
I have TWRP recovery, and wiped EVERYTHING before trying to install the Rom, never had a phone that didn't really have a MicroSD, and I guess I wiped the internal memory also... meaning I have no rom to flash...
"adb devices" is not recognizing the phone so I can't Push/Sideload...
I can boot into recovery, but can't do much else without being able to use adb
HELP... any suggestions.
lexknight said:
I have TWRP recovery, and wiped EVERYTHING before trying to install the Rom, never had a phone that didn't really have a MicroSD, and I guess I wiped the internal memory also... meaning I have no rom to flash...
"adb devices" is not recognizing the phone so I can't Push/Sideload...
I can boot into recovery, but can't do much else without being able to use adb
HELP... any suggestions.
Click to expand...
Click to collapse
Have you tried mounting the usb storage via recovery and copying the rom from there?
Payton95 said:
Have you tried mounting the usb storage via recovery and copying the rom from there?
Click to expand...
Click to collapse
I see the mount button, but when I go in there I dont see anything about usb storage?
Am I missing something?
install the driver on your computer again and try ADB...
if not...gluck man I dont think there is another way.
lexknight said:
I see the mount button, but when I go in there I dont see anything about usb storage?
Am I missing something?
Click to expand...
Click to collapse
No. Sorry, I believe it is just Cwm that allows usb storage in recovery.(I could be wrong) As stated above, install the drivers to try to fix adb if that fails then you may need to take a look at this. Good Luck:good:
http://forum.xda-developers.com/showthread.php?t=2471370
[Guide] Unroot/Unbrick - flash official factory firmware with LG Launcher
Payton95 said:
No. Sorry, I believe it is just Cwm that allows usb storage in recovery.(I could be wrong) As stated above, install the drivers to try to fix adb if that fails then you may need to take a look at this. Good Luck:good:
http://forum.xda-developers.com/showthread.php?t=2471370
Click to expand...
Click to collapse
I tried that "[Guide] Unroot/Unbrick - flash official factory firmware with LG Launcher"
It seems to see the phone, and all, but when it goes to download the firmware from LG, it just hangs, reading the posts there, looks like others have it hang at the same place mine did...
I think I am just SOL, till someone figures out how to make a tool that will fix this...
I am sure I am not the only one that will accidently wipe everything leaving it in a state where you don't have a rom to flash back on it...
so I am sure someone will make something soon...
till then will just have to go back to my old phone.
Thanks.
I would assume you need to try to get fastboot working, but I have never tried to get into the G2's bootloader. But you'll get ADB - Fastboot working, you will, you just need to keep trying. Try someone else's computer if you have to.
I really need to just find the kdz firmware for the Sprint LG G2... I think I have a way of flashing it... just need to find it...
I have found about every G2 except the Sprint one...
lexknight said:
I really need to just find the kdz firmware for the Sprint LG G2... I think I have a way of flashing it... just need to find it...
I have found about every G2 except the Sprint one...
Click to expand...
Click to collapse
I found it herehttp://forum.xda-developers.com/showthread.php?t=2432476 and am in the exact same boat as you. I was about to flash a recovery I made and accidentally wiped EVERYTHING including my recovery image. I'm downloading the Sprint kdz as we speak and please let me know what else you are thinking as a way of flashing that file. I can get into TWRP, stock hard reset mode (which doesn't seem to do anything) and download mode.
InsanePostman said:
I found it herehttp://forum.xda-developers.com/showthread.php?t=2432476 and am in the exact same boat as you. I was about to flash a recovery I made and accidentally wiped EVERYTHING including my recovery image. I'm downloading the Sprint kdz as we speak and please let me know what else you are thinking as a way of flashing that file. I can get into TWRP, stock hard reset mode (which doesn't seem to do anything) and download mode.
Click to expand...
Click to collapse
You are looking at doing the same thing I am going to try, but when I went to where you download... the only Sprint image I see is a .zip... not a .kdz... and that program they use only recognizes .kdz's...
In reading that feed, they said that in the US they don't use .kdz's... so still looking into that, I have a post in that thread and maybe we can get more help...
But your in the EXACT spot I am in, I can get into TWRP, hard reset, and download
If you can figure it out PLEASE post here, and I will be doing the same, I am sure there will be a lot of people doing what we did without thinking, and I guess we were the first, and will be the leaders... LOL
Thanks.
lexknight said:
You are looking at doing the same thing I am going to try, but when I went to where you download... the only Sprint image I see is a .zip... not a .kdz... and that program they use only recognizes .kdz's...
In reading that feed, they said that in the US they don't use .kdz's... so still looking into that, I have a post in that thread and maybe we can get more help...
But your in the EXACT spot I am in, I can get into TWRP, hard reset, and download
If you can figure it out PLEASE post here, and I will be doing the same, I am sure there will be a lot of people doing what we did without thinking, and I guess we were the first, and will be the leaders... LOL
Thanks.
Click to expand...
Click to collapse
well ****. I'm going to try the method listed in that thread but I don't know if it's going to work. Nothing seems to identify my phone properly. The LG mobile support tool recognizes it as "testdevice" and when I try updating recovey through the program it hangs once it says "downloading files". I'll post anything I can find as soon as I find anything. Please do the same. I just bought this phone yesterday and already managed to f it up.
InsanePostman said:
well ****. I'm going to try the method listed in that thread but I don't know if it's going to work. Nothing seems to identify my phone properly. The LG mobile support tool recognizes it as "testdevice" and when I try updating recovey through the program it hangs once it says "downloading files". I'll post anything I can find as soon as I find anything. Please do the same. I just bought this phone yesterday and already managed to f it up.
Click to expand...
Click to collapse
Mine does the same with the hanging in "downloading files" I sort of think they might not actually have the file up for Sprint yet... I think its just to new... I bought mine 2 days ago also, just long enough to say, what a cool phone, let me BRICK IT... LOL
Will keep you posted on anything I find...
thanks again.
lexknight said:
Mine does the same with the hanging in "downloading files" I sort of think they might not actually have the file up for Sprint yet... I think its just to new... I bought mine 2 days ago also, just long enough to say, what a cool phone, let me BRICK IT... LOL
Will keep you posted on anything I find...
thanks again.
Click to expand...
Click to collapse
I got adb to recognize my device as "02f1a913c6922256" but it says it's offline. if I can get it online somehow you think i could sideload a zip?
Also where do I get the "LGE Android MTP Device" drivers? They say failed and I'v tied the newest available drivers package. Or iss this just an error cause of the state of the phone?
InsanePostman said:
I got adb to recognize my device as "02f1a913c6922256" but it says it's offline. if I can get it online somehow you think i could sideload a zip?
Click to expand...
Click to collapse
You should be able to, as long as you can get adb to see it, you are good, you can even just adb push a rom over to the "NON" SDCard... and then just flash from TWRP...
The main problem we have is that without a SDCard that you can take out and put a rom on, we are stuck.
lexknight said:
You should be able to, as long as you can get adb to see it, you are good, you can even just adb push a rom over to the "NON" SDCard... and then just flash from TWRP...
The main problem we have is that without a SDCard that you can take out and put a rom on, we are stuck.
Click to expand...
Click to collapse
wonderful... i guess i'll have to activate my old phone for the time being
---------- Post added at 07:47 PM ---------- Previous post was at 06:48 PM ----------
InsanePostman said:
wonderful... i guess i'll have to activate my old phone for the time being
Click to expand...
Click to collapse
I'm guessing there's no way to unroot either in order to try and get it covered by the warranty?
---------- Post added at 08:11 PM ---------- Previous post was at 08:10 PM ----------
I think I figured it out dude. Follow these instructions from this guide. http://forum.xda-developers.com/showthread.php?t=2448960 Only using the Sprint files located in this thread. http://forum.xda-developers.com/showthread.php?t=2432476
EDIT: The flash program, DLL's, and Sprint .tot file are located here in this link to avoid confusion http://storagecow.eu/index.php?dir=Xda%2FLG+G2%2FStock%2FSprint+LS980%2F. These are the only files you need. So get that zip and extract it then use those files with the instructions in the first link I posted.[/URL]
---------- Post added at 08:13 PM ---------- Previous post was at 08:11 PM ----------
It worked!!!! I"m back baby.
InsanePostman said:
wonderful... i guess i'll have to activate my old phone for the time being
---------- Post added at 07:47 PM ---------- Previous post was at 06:48 PM ----------
I'm guessing there's no way to unroot either in order to try and get it covered by the warranty?
---------- Post added at 08:11 PM ---------- Previous post was at 08:10 PM ----------
I think I figured it out dude. Follow these instructions from this guide. http://forum.xda-developers.com/showthread.php?t=2448960 Only using the Sprint files located in this thread. http://forum.xda-developers.com/showthread.php?t=2432476
EDIT: The flash program, DLL's, and Sprint .tot file are located here in this link to avoid confusion http://storagecow.eu/index.php?dir=Xda%2FLG+G2%2FStock%2FSprint+LS980%2F. These are the only files you need. So get that zip and extract it then use those files with the instructions in the first link I posted.[/URL]
---------- Post added at 08:13 PM ---------- Previous post was at 08:11 PM ----------
It worked!!!! I"m back baby.
Click to expand...
Click to collapse
Downloaded it all, installed the LGFlashTool, put into download mode, changed to port 41, and when I try to run the LGFlashTool program after saying yes to ??? Korean camp, I get "LG USB/Paralle Lock Key is not detected"... when I hit the "OK" I then get a Login screen with Country Republic of Korea, ID, PASSWORD ...
lexknight said:
Downloaded it all, installed the LGFlashTool, put into download mode, changed to port 41, and when I try to run the LGFlashTool program after saying yes to ??? Korean camp, I get "LG USB/Paralle Lock Key is not detected"... when I hit the "OK" I then get a Login screen with Country Republic of Korea, ID, PASSWORD ...
Click to expand...
Click to collapse
you have to extract the megalock.dll from its archive and overwrite the existing one in the LG flash tool directory. Then launch the program.
InsanePostman said:
you have to extract the megalock.dll from its archive and overwrite the existing one in the LG flash tool directory. Then launch the program.
Click to expand...
Click to collapse
Ahhhhhhhhhhhhhhhhhhhhhhh... I HAVE A PHONE AGAIN... NOT JUST A COOL BRICK !!!...
IF YOU WERE A WOMAN, I WOULD GIVE YOU A BIG KISS !!!!!!!
THANKS MORE THAN YOU WILL EVER KNOW...
Now, time to root and try to brick it again... LOL
lexknight said:
Ahhhhhhhhhhhhhhhhhhhhhhh... I HAVE A PHONE AGAIN... NOT JUST A COOL BRICK !!!...
IF YOU WERE A WOMAN, I WOULD GIVE YOU A BIG KISS !!!!!!!
THANKS MORE THAN YOU WILL EVER KNOW...
Now, time to root and try to brick it again... LOL
Click to expand...
Click to collapse
Haha no problem. Many others deserve credit for the files and instructions. I just did the heavy searching.
InsanePostman said:
Haha no problem. Many others deserve credit for the files and instructions. I just did the heavy searching.
Click to expand...
Click to collapse
Just read the info in the links - thanks for posting about your success. Good to know there's a way out if I get into the same situation flashing a ROM on my G2.
phone will arrive tomorrow. need to know haha
Nothing yet. I got my phone and I've unlocked the bootloader in preparation, but so far no news of recoveries. I have no idea how long this takes because I've never been an early adopter before...
randman2011 said:
Nothing yet. I got my phone and I've unlocked the bootloader in preparation, but so far no news of recoveries. I have no idea how long this takes because I've never been an early adopter before...
Click to expand...
Click to collapse
Could you check the key combination needed to cold boot in to fastboot mode please. Im assuming its volume down and power together from a shut down.
Thanks, Mark.
It is.
randman2011 said:
It is.
Click to expand...
Click to collapse
Thanks, last question before I can release my Toolkit for this device. Is forced encryption enable by default on this device (if you don't know then you can find the answer in Settings, Security)? If so I can easily enable the no encryption option in the Unified Android Toolkit.
Mark.
mskip said:
Thanks, last question before I can release my Toolkit for this device. Is forced encryption enable by default on this device (if you don't know then you can find the answer in Settings, Security)? If so I can easily enable the no encryption option in the Unified Android Toolkit.
Mark.
Click to expand...
Click to collapse
It is encrypted with no option to disable it.
mskip said:
Thanks, last question before I can release my Toolkit for this device. Is forced encryption enable by default on this device (if you don't know then you can find the answer in Settings, Security)? If so I can easily enable the no encryption option in the Unified Android Toolkit.
Mark.
Click to expand...
Click to collapse
You have a custom recovery and / or modified boot image for the Nexus 5X?!
oscillik said:
You have a custom recovery and / or modified boot image for the Nexus 5X?!
Click to expand...
Click to collapse
No sorry there isn't one available yet but all options apart from recovery based ones are enabled including disabling forced encryption and flashing stock images (or parts of).
I have to go out now but have uploaded the Toolkit and will make a new thread in the Original Android Development section when I get back in a few hours.
Mark.
Waiting for custom recoveries! OP2 got custom recovery faster
mskip said:
No sorry there isn't one available yet but all options apart from recovery based ones are enabled including disabling forced encryption and flashing stock images (or parts of).
I have to go out now but have uploaded the Toolkit and will make a new thread in the Original Android Development section when I get back in a few hours.
Mark.
Click to expand...
Click to collapse
modified boot image - bullhead-mdb08i-boot.zip http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
i did a factory reset after i fastboot flashed the boot image for encryption to be off. https://goo.gl/photos/Wq6bMCqD1XVBWQdQ9
dees_troy said he might be able to take a stab at making a recovery later today, if he can get around to it and figure it out, rooting should be easy. otherwise i was thinking about repacking the system.img with su and seeing if that works.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
renzyyy said:
modified boot image - bullhead-mdb08i-boot.zip http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
i did a factory reset after i fastboot flashed the boot image for encryption to be off. https://goo.gl/photos/Wq6bMCqD1XVBWQdQ9
dees_troy said he might be able to take a stab at making a recovery later today, if he can get around to it and figure it out, rooting should be easy. otherwise i was thinking about repacking the system.img with su and seeing if that works.
Click to expand...
Click to collapse
I have a no encyption patched stock kernel included in the Toolkit with automation to make it easier for the average user.
You can certainly repack the system image to include root but if you are publishing it you will also need to include chainfires patched kernel (the one you linked to) to flash with the modified system image or the system will go in to a bootloop (requirement of Android 6 root at the moment. I may look at it later but I have no Nexus 5X to test anything on.
I have published the new Toolkit with the Nexus 5X added and made an xda thread *HERE*.
One thing, does the Nexus 5X suffer from the same problem as other Nexus devices, where the USB mode switches back from PTP mode (for adb commands) back to Charging only on EVERY reboot. Its a pain in the ass and always switches back even if the mode is set in developer options.
Mark.
roooooooot!
---------- Post added at 03:38 PM ---------- Previous post was at 03:00 PM ----------
Dees_Troy posted the recovery btw, http://forum.xda-developers.com/showthread.php?t=1943625
renzyyy said:
roooooooot!
---------- Post added at 03:38 PM ---------- Previous post was at 03:00 PM ----------
Dees_Troy posted the recovery btw, http://forum.xda-developers.com/showthread.php?t=1943625
Click to expand...
Click to collapse
I'll give you a cookie for that root
just a word of advice - make sure your phone is already running build MDB08I, and not any other build, before you flash that modified boot img: I just tried flashing it, and it just sticks on boot animation. My Nexus 5X is currently running MDA89E
renzyyy said:
roooooooot!
---------- Post added at 03:38 PM ---------- Previous post was at 03:00 PM ----------
Dees_Troy posted the recovery btw, http://forum.xda-developers.com/showthread.php?t=1943625
Click to expand...
Click to collapse
Any idea if it is safe to re-enable encryption after flashing the modified boot.img, factory wipe, TWRP flash?
bqq100 said:
Any idea if it is safe to re-enable encryption after flashing the modified boot.img, factory wipe, TWRP flash?
Click to expand...
Click to collapse
my guess is that you can, but then you wont be able to use recovery again. dont quote me on that, ive never tried re-enabling it.
oscillik said:
just a word of advice - make sure your phone is already running build MDB08I, and not any other build, before you flash that modified boot img: I just tried flashing it, and it just sticks on boot animation. My Nexus 5X is currently running MDA89E
Click to expand...
Click to collapse
I modified the mda89e and mda89f stock boot images for no-force encryption and re-packed them for use with the android toolkit. If you have MDA89E try flashing *THIS* image and see if it fixes the bootloop problem.
Mark.
mskip said:
One thing, does the Nexus 5X suffer from the same problem as other Nexus devices, where the USB mode switches back from PTP mode (for adb commands) back to Charging only on EVERY reboot. Its a pain in the ass and always switches back even if the mode is set in developer options.
Mark.
Click to expand...
Click to collapse
Yes it still makes you do that Although my N6 did not require it to be toggled after every reboot like the N5X does. It needs to be in PTP to get ADB commands to work, on my windows machine that is, not on the Mac.
mskip said:
I modified the mda89e and mda89f stock boot images for no-force encryption and re-packed them for use with the android toolkit. If you have MDA89E try flashing *THIS* image and see if it fixes the bootloop problem.
Mark.
Click to expand...
Click to collapse
The link doesn't seem to work , need a username and password.
Hayth said:
The link doesn't seem to work , need a username and password.
Click to expand...
Click to collapse
He put it up as an sftp:// (protocol for secure ftp) link. Try this one instead: http://skipsoft.net/tempuploads/boot_images/boot-noforce-encrypt-mda89e-bullhead.img
Seems @nheolinkin solved this problem with a fair solution that I haven't tried (yet). Please go to his thread, I abandoned this experiment, but I thought I need to edit this post for a better solution and keep forum cleaner. Please visit:
https://forum.xda-developers.com/zenfone-5/general/share-discussion-users-problems-unlock-t3629739
Old experiment:
Hello folks!
I think i made it to unlock bootloader without any freezes.
This unlocker provides 6 different method to try.
If none of these work, there's nothing I can do more, sorry (for now...).
There's a latest beta script. I don't know it will freeze or not, go and test it.
First of all I am not responsible if it bricks your device and becomes unusable, so try if you want.
===AUTOMATED QUICK SCRIPT===
I made an automated flasher. Here's a quick explaination:
1 for my freeze patch.
2 for relock bootloader.
https://drive.google.com/open?id=0B6AxuGkWld1yYU5zNGR0SzQ2OXc
It will give you a better result but not the real fix.
==============================
===MY CONFIGURATION'S SCRIPT===
Quick explaination:
1 for unlock bootloader
https://drive.google.com/file/d/0B6AxuGkWld1yMUhpWWd5TWN0ZFk
This is the LATEST testing version.
Probably it won't work. Use Automated Quick.
=============================
==========KERNEL==========
Latest version number: 16.05
http://forum.xda-developers.com/zen...ne-5s-bootloader-freeze-t3362234/post66882948
===========================
Important Notes:
Thanks all the XDA Zenfone 5 Community and the friends that I've been talking about.
Disable dt2w for the reboots and I recommend using the latest Resurrection Remix by @tank0412, CM is a bit old; so that might do reboots.
Fastboot Archive (WIP): https://drive.google.com/folderview?id=0B6AxuGkWld1yYVdFZTFLckhaUDQ&usp=drive_web
Ifwi Archive: https://drive.google.com/open?id=0B6AxuGkWld1yWHV5Rm0yZUd4Q1U
When trying a new fastboot; for the best results you should wipe cache and dalvik cache.
If anyone bricked the phone when doing this, check the link: http://forum.xda-developers.com/zenfone-5/help/zenfone-5-a500cg-zenfone-6-a600cg-t3354645 (Credits to @swiczak )
@kanodiatushar tested and it worked. Thanks.
I searched about camera bugs and when i disable one core of my cpu, camera is not launching (I normally have camera on unlocked bootloader). So, about camera: Some cpu based bug on some devices makes camera bug on custom roms. Make sure you have four of four cores active and available.
Please give a credit to http://ozankaraali.com when sharing if it worked as i did to other users.
As I said, this is experimental and may or may not be working, even maybe it can brick your device and I need feedbacks negative or positive.
you are still experience freezing?what rom are you using @ozank?
davidjay26 said:
you are still experience freezing?what rom are you using @ozank?
Click to expand...
Click to collapse
i am still experiencing freeze sometimes but not that frequent, as i said i used 12 hours no-freeze then freezed. i am taking logcat now for the next time if it happens. until i make this i was getting freeze nearly every 30 minute-like and as i said, i need feedbacks for this experiment. i think this is not the end of all the freezes but still noticeable difference for me and i need to hear from the others
by the way using dgadelha's cm13, 18 apr kernel and 15 apr system.
Will try.i use cm13 by dgadelha too
Sent from my ASUS_T00F using Tapatalk
i used it on stock LP (.78 ) for 2-3 hrs
it freezes every 10mins
my device is zenfone 5 T00J
kanodiatushar said:
i used it on stock LP (.78 ) for 2-3 hrs
it freezes every 10mins
my device is zenfone 5 T00J
Click to expand...
Click to collapse
Thanks for the information, i will try better about that.
By the way can you see your serial number properly on this fastboot?
ozank said:
Thanks for the information, i will try better about that.
By the way can you see your serial number properly on this fastboot?
Click to expand...
Click to collapse
Yes, it did change to something EZA***
Edit: its E8AZCY***
kanodiatushar said:
Yes, it did change to something EZA***
Edit: its E8AZCY***
Click to expand...
Click to collapse
thanks for the information, i will try to find a more proper way, as i said, i partially fixed on my phone with this and i will try to fix for most of the devices
ozank said:
thanks for the information, i will try to find a more proper way, as i said, i partially fixed on my phone with this and i will try to fix for most of the devices
Click to expand...
Click to collapse
Thank you very much for your efforts and time
---------- Post added at 11:33 AM ---------- Previous post was at 10:54 AM ----------
ok i followed the procedure in OP and after the freezes i decided to relock the bootloader
i used the tool provided in the RR-LP thread to relock the bootloader
but then i unlocked it again by the flashing dnx then if.bin provided in the OP
and haven't faced any freezes since then
---------- Post added at 11:37 AM ---------- Previous post was at 11:33 AM ----------
@ozank is it because of the if.bin i placed in /system/etc/firmware/ ?
or does it have something to do with the your fastboot?
kanodiatushar said:
Thank you very much for your efforts and time
---------- Post added at 11:33 AM ---------- Previous post was at 10:54 AM ----------
ok i followed the procedure in OP and after the freezes i decided to relock the bootloader
i used the tool provided in the RR-LP thread to relock the bootloader
but then i unlocked it again by the flashing dnx then if.bin provided in the OP
and haven't faced any freezes since then
---------- Post added at 11:37 AM ---------- Previous post was at 11:33 AM ----------
@ozank is it because of the if.bin i placed in /system/etc/firmware/ ?
or does it have something to do with the your fastboot?
Click to expand...
Click to collapse
I thank you for your efforts about trying at least and giving me a feedback
I am happy that seeing you having not much freezes at all until now
And i don't know what's making the freeze and what is not making the freeze, i was just trying to get a solution, i researched that from the other users' ideas.
I think the if.bin placement is the key, without it, it freezed a lot more according to my experiment.
But as i said this solution wasn't the end of the all freezes so i am still searching the problem but it makes a little bit difference at least and wanted to share for relaxing our devices a bit.
Files were from the 1.18ish version (JB) and i will try earlier files like 1st asus rom and if it makes difference i will share.
i tried reverting back to 1.17.40.16WW and use the official unlocker and after unlock i immediately flashed the RR-MM rom and it freezed....
I will test it for a day... but can you suggest me if it will work on the RR-MM rom?
i mean i flash the rom
place the if.bin
set permission
and then unlock again using the files you provided?
---------- Post added at 12:30 PM ---------- Previous post was at 12:09 PM ----------
1st freeze
---------- Post added at 12:52 PM ---------- Previous post was at 12:30 PM ----------
2nd freeze
kanodiatushar said:
i tried reverting back to 1.17.40.16WW and use the official unlocker and after unlock i immediately flashed the RR-MM rom and it freezed....
I will test it for a day... but can you suggest me if it will work on the RR-MM rom?
i mean i flash the rom
place the if.bin
set permission
and then unlock again using the files you provided?
---------- Post added at 12:30 PM ---------- Previous post was at 12:09 PM ----------
1st freeze
Click to expand...
Click to collapse
I did like so on cm13 rom. I didn't revert, only changed fastboot images and i am having 12 hour no freeze duration and wanted to share the way, no need to officially unlock, it makes no difference except warranty. I will try to use ifwi, dnx and fastboots of other versions for no freeze at all and i think it varies for the different product bands (like august vs june factory phones).
So, when you trying this way make sure fastboot and ifwi, dnx files of same date and copy if to firmware.
There is just one if.bin for unlocking so this makes the problem and it cannot be compiled by anyone except asus, so we are trying to find the most compatible fastboot and dnx-ifwi bins to our phone. I think that's the key and kernel might search for if.bin on firmware folder if i understand correctly, if it couldnt find it freezes. (If the case is not placebo at all)
Well done... your solution make mine less freeze than before... thank you.
Sr for my bad english
akiralee said:
Well done... your solution make mine less freeze than before... thank you.
Sr for my bad english
Click to expand...
Click to collapse
i thank you for the giving feedback and trying my solution, have a good day and if i find any better solution i will update the first post
Edit: Check the first post, I uploaded a new kit, haven't tried that much so if you want to be a tester, go ahead and check it
ozank said:
i thank you for the giving feedback and trying my solution, have a good day and if i find any better solution i will update the first post
Edit: Check the first post, I uploaded a new kit, haven't tried that much so if you want to be a tester, go ahead and check it
Click to expand...
Click to collapse
Hi, I tried the tutorial in the first post with V2 files and I get a locked bootloader with ifwi 59.27. Why I get a locked bootloader?
leonardohenrique10 said:
Hi, I tried the tutorial in the first post with V2 files and I get a locked bootloader with ifwi 59.27. Why I get a locked bootloader?
Click to expand...
Click to collapse
try to flash if.bin again, if it doesn't work revert to v1.
edit: it's a testing build and as i said it may not work and even brick the device, so be careful.
that gave me a a1 bootloader and when i controlled that said signed bootloader, maybe this was a bug and first post edited with your feedback, i will try this build for a night and will report if it freezes.
i have noticed that my zen5 got freeze only when charger is conected, and i play some game (eg Contest of Chamions, Marvel)... after some like 40-50 mins, device is overheating, and freeze.
in other cases i dont have freezes
killar_aka_arabu said:
i have noticed that my zen5 got freeze only when charger is conected, and i play some game (eg Contest of Chamions, Marvel)... after some like 40-50 mins, device is overheating, and freeze.
in other cases i dont have freezes
Click to expand...
Click to collapse
yes i was talking about "not the end of the freezes" :laugh: on normal usage it works okay with this tutorial, but on charging and using heavy apps occurs freezes.
actually on another thread @pedromd did some ifwi.bins that i haven't tried yet. if anyone wants to try that, can check out his files.
that night, i will look at my v2-like solution and logcat it.
(it may not be working for the other users according to reports but i am now o my v2)
ozank said:
i thank you for the giving feedback and trying my solution, have a good day and if i find any better solution i will update the first post
Edit: Check the first post, I uploaded a new kit, haven't tried that much so if you want to be a tester, go ahead and check it
Click to expand...
Click to collapse
i think i dont need to try it.. because i used my phone last night and have no freezing during 3-4h... i think there no freeze more... thank for your help... :highfive::highfive::highfive::highfive:
akiralee said:
i think i dont need to try it.. because i used my phone last night and have no freezing during 3-4h... i think there no freeze more... thank for your help... :highfive::highfive::highfive::highfive:
Click to expand...
Click to collapse
You're welcome.
With 20 Kernel 19 System of dgadelha's CM, i didn't get any reboots on night charge and logcat terminal was there on morning. Only a bit network issue i found on latest release but not that much, if anyone encountering freezes, should try the latest build. I am going to test for daily freezes now. But it should be fixed with these files i suppose.
Thanks for the feedback and have a good day!
Does anyone know the system.prop to disable the high volume warning? I see in this Magisk Module that it modifies
Code:
audio.safemedia.bypass=true
but that doesn't seem to work on Samsung firmware. I remember finding the alternative setting somewhere, but I had to flash stock firmware and lost it, and can't seem to find it again.
By the time you are using Magisk instead of SuperSu just download the module ... If you want to do it by yourself just download BuildCrop from PlayStore, find the line,change it and you are done !
---------- Post added at 12:23 AM ---------- Previous post was at 12:21 AM ----------
DaleSwanson said:
Does anyone know the system.prop to disable the high volume warning? I see in this Magisk Module that it modifies
but that doesn't seem to work on Samsung firmware. I remember finding the alternative setting somewhere, but I had to flash stock firmware and lost it, and can't seem to find it again.
Click to expand...
Click to collapse
And if I'm not wrong you will find the same code with the difference that it will has true instead of false. I have not tried such a thing before so do it with your own risk
Andriano24 said:
By the time you are using Magisk instead of SuperSu just download the module ... If you want to do it by yourself just download BuildCrop from PlayStore, find the line,change it and you are done !
And if I'm not wrong you will find the same code with the difference that it will has true instead of false. I have not tried such a thing before so do it with your own risk
Click to expand...
Click to collapse
I do have the module, but it doesn't work (other comments on the thread have noted other Samsung phones it doesn't work for). I was planning on just changing the line the module edits to the line Samsung uses. Do you know what it is?
I really don't want you to boot loop or something like that... So in... Let's say 12 hours I will provide you a way to remove that option. I may boot loop but I really don't care, I'm gonna install a new room anyways
Andriano24 said:
I really don't want you to boot loop or something like that... So in... Let's say 12 hours I will provide you a way to remove that option. I may boot loop but I really don't care, I'm gonna install a new room anyways
Click to expand...
Click to collapse
I was just in a boot loop, and just reflashed stock rom (which is why I need this setting, cause I had it before, but lost it). Thanks for the concern, but this is the ideal time to boot loop.
DaleSwanson said:
I was just in a boot loop, and just reflashed stock rom (which is why I need this setting, cause I had it before, but lost it). Thanks for the concern, but this is the ideal time to boot loop.
Click to expand...
Click to collapse
Ahahaha I feel you man. But something is stared getting on my nerves !!! I don't know if it is because I'm running Android 7.0 instead of Android 6.0, but I tried editing build.prop by adding a line on it...
audio.safemedia.bypass=true
But it does not seems to be working ... I found a threat on Reddit about that but they werre based on Android 6.0 .... So I have no idea what to do (you can download an app from PlayStore or even download Xposed and download a module ...) But it is even worth it ?
---------- Post added at 02:12 AM ---------- Previous post was at 01:58 AM ----------
Hahaha stupid me ! https://forum.xda-developers.com/apps/magisk/module-volume-steps-increase-magisk-v10-t3554996/page5
Go there and download the file on that page, and then flash it , I'm gonna try it! If I won't be back at least in 10 minutes , that means I ran intro a boot loop
---------- Post added at 02:16 AM ---------- Previous post was at 02:12 AM ----------
None of those flashable files seems to work. I'm truly sorry ... Maybe just go and ask the OP of that threat instead