Develop Bugs

Having trouble with recovery and download mode

I got a hand me down S3 since my old phone (ancient infuse 4g) recently broke. It works fine at the moment, but I can't seem to get anything to work properly in terms of roms/odin/any customization.
Booting into download seems to work, as I can flash things in ODIN, but it shows a black screen. I've been using adb boot download to make sure I'm going into the right mode. ODIN shows success when flashing stuff, but I'm not so sure.
Booting into recovery just shows a black screen. Flashing to stock recovery, cwm, or twrp doesn't seem to change anything.
I can't get any of the root methods to work since I can't get into recovery. I found a rooted stock image that's current but it's in zip form, and since you can only install zip files from recovery, I can't use it. I tried a convert to tar utility but that also didn't work.
I've done a factory reset, and managed to wipe everything the one time I got into stock recovery (when I first got the phone). After that, any attempts to root, get back to stock, or do anything really but turn it on and use it, aren't working. I also tried towelroot, which worked once, then I reset the phone and towelroot no longer worked- probably due to a kernel upgrade.
A lot of the posts I found, including one about Kies, all dealt with older versions and possible bricking when downgrading bootloaders so I wanted to make sure before I did anything dumb.
Oh, and using rom manager to try to install cwm just freezes at 'flashing'. the twrp utility whose name I forget (replaced goo manager) just freezes as soon as I open it. I've also tried multiple usb ports, and made sure to only use ones directly connected to the mother board.
I'm running ucufnj1. Maybe if I had an odin flashable version of that?
What do?

Did you try flashing a custom recovery in Odin? When it finishes flashing recovery, do not let it reboot. Just remove the battery and try booting into recovery.
I recommend using Philz Touch for the d2lte.

audit13 said:
Did you try flashing a custom recovery in Odin? When it finishes flashing recovery, do not let it reboot. Just remove the battery and try booting into recovery.
I recommend using Philz Touch for the d2lte.
Click to expand...
Click to collapse
I tried that with cwm and twrp, removing the battery and all, but I got a black screen with both. Just an unresponsive black screen.

Please help!

yoonietang said:
I tried that with cwm and twrp, removing the battery and all, but I got a black screen with both. Just an unresponsive black screen.
Click to expand...
Click to collapse
Are you checking auto-reboot in Odin?

audit13 said:
Are you checking auto-reboot in Odin?
Click to expand...
Click to collapse
I make sure auto reboot is unchecked, then I take the battery out and try to start into recovery. I'm also having trouble booting into download mode with the button combo (vol down, home, power) so I've been using adb reboot download to do it.

Can you use adb commands to enter recovery?
Have you tried flashing the latest Philz Touch doe thr d2lte? I highly recommend it.

audit13 said:
Can you use adb commands to enter recovery?
Have you tried flashing the latest Philz Touch doe thr d2lte? I highly recommend it.
Click to expand...
Click to collapse
Doesn't work =( Still getting the same black screen when I try to get into recovery.

If you can somehow manage to get into download mode, let me know what it says on the screen. The important thing is to make note of the model # and the presence of a warranty bit line.
If you can't get into download mode, try installing the Samsung Info App from the Play Store and use the app to find your bootloader and modem version.

audit13 said:
If you can somehow manage to get into download mode, let me know what it says on the screen. The important thing is to make note of the model # and the presence of a warranty bit line.
If you can't get into download mode, try installing the Samsung Info App from the Play Store and use the app to find your bootloader and modem version.
Click to expand...
Click to collapse
I honestly can't tell if I'm getting into download mode or not. I *think* I'm getting into download mode except with a black screen for some reason, as ODIN claims success when flashing stuff. I also used adb reboot download to eliminate any doubt about holding the right buttons to access it, so that helps narrow down the possible source of the problem. I believe my dad (previous owner) had the screen replaced at some point. Could this be a wobbly connection?
Phone model is sgh-i747rwbatt.
Bootloader, Baseband, PDA, and CSC versions are all UCUFNJ1 (csc is i747attfnj1).
I can't seem to find modem version- is that baseband? Modem model is MSM8960.

Weird but the AT&T S3 is the sgh-i747. There should not be any letters or numbers after the second 7.
In download mode, are you seeing the Android guy? Are you sing the button combination or fastboot commands to get into download mode? USB debugging must be on to use fastboot commands.

audit13 said:
Weird but the AT&T S3 is the sgh-i747. There should not be any letters or numbers after the second 7.
In download mode, are you seeing the Android guy? Are you sing the button combination or fastboot commands to get into download mode? USB debugging must be on to use fastboot commands.
Click to expand...
Click to collapse
just had to go there. 1st three google search results for sgh i747rwbatt pulled up a white S3. (?). never knew or heard of.
"all i can really do , is stay out of my own way and let the will of heaven be done"

audit13 said:
Weird but the AT&T S3 is the sgh-i747. There should not be any letters or numbers after the second 7.
In download mode, are you seeing the Android guy? Are you sing the button combination or fastboot commands to get into download mode? USB debugging must be on to use fastboot commands.
Click to expand...
Click to collapse
usb debugging is on. Download mode just shows a black screen, nothing at all, whether I use adb reboot download or the button combo to get into. Odin reports that it sees the phone though.

would like to get @audit13 opinion on this , but you can use flashify and mobile odin to flash with. i have no experience with mobile odin and have only used flashify for .img and not .zips. he might be more knowledgeable about these apps performance records.
"all i can really do , is stay out of my own way and let the will of heaven be done"

Since the LCD remains black when you boot into download mode, I assume you obtained the phone information using the Samsung Phone Info App.
Are you able to issue fastboot commands in download mode? In download mode, does fastboot devices return your phone?
Unfortunately, I know nothing about mobile Odin or Flashify. I have never used these tools and don't have an s3 anymore.

audit13 said:
Since the LCD remains black when you boot into download mode, I assume you obtained the phone information using the Samsung Phone Info App.
Are you able to issue fastboot commands in download mode? In download mode, does fastboot devices return your phone?
Unfortunately, I know nothing about mobile Odin or Flashify. I have never used these tools and don't have an s3 anymore.
Click to expand...
Click to collapse
Fastboot commands don't work. I tried installing the fastboot drivers, but I still get nothing returned when I try 'fastboot devices', so I couldn't try any of the other fastboot commands. I'm not 100% sure if it's the drivers on my PC or the phone that's the issue, since a lot of the samsung/google drivers seem a bit finicky, but I did install minimal adb and fastboot from this forum.
Yes, I used the samsung phone info app (it's not official, right? It's made by vndnguyen?).
In regards to odin mobile and flashify, when I googled flashify (someone else mentioned it on reddit when I asked there) it said it required root. Unfortunately, I still can't get root due to the recovery issues, or I'd be able to use any number of methods.

When you try to enter download mode, do you see the warning screen where you press the volume key to continue to download mode?
Since you can't issue fastboot commands, this leads me to believe that the phone may not be entering fastboot mode. In fastboot mode, you may be able to push a recovery image to the phone.
Could you post a screen shot of your Odin screen with the phone connected?

audit13 said:
When you try to enter download mode, do you see the warning screen where you press the volume key to continue to download mode?
Since you can't issue fastboot commands, this leads me to believe that the phone may not be entering fastboot mode. In fastboot mode, you may be able to push a recovery image to the phone.
Could you post a screen shot of your Odin screen with the phone connected?
Click to expand...
Click to collapse
When I boot into download or recovery, there is nothing but a black screen, nothing else at any point at all.
{
"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"
}
Again, nothing but a black screen when I boot to recovery or download. I do get the vibration to confirm the device turning on though.
Also a screenshot showing fastboot

When using the button combination for download mode, I believe the first screen you see is a warning screen, then you need to press the volume + key to enter download mode. Are you pressing the volume up key?
Open Odin, flash recovery, and then take a screen shot of the Odin screen after it finishes flashing recovery. This may provide more clues as to what's happening.

audit13 said:
When using the button combination for download mode, I believe the first screen you see is a warning screen, then you need to press the volume + key to enter download mode. Are you pressing the volume up key?
Open Odin, flash recovery, and then take a screen shot of the Odin screen after it finishes flashing recovery. This may provide more clues as to what's happening.
Click to expand...
Click to collapse
Same when I try twrp of philz touch. However, when I flashed philz and then booted into recovery, I get a vibration when I touch the screen. This leads me to believe that the recovery is active, but the screen is off for some reason. Maybe if someone could walk me through flashing an image from recovery, step by step, I could do it blind?
Also, it seems that booting into download via key press requires you to press the volume up button to active download mode but using adb reboot download does not (based on when odin/my PC detected the phone entering download mode). Regardless, I tried both ways.
Edit: I copied and pasted the OP from another forum, and didn't realize it cut something off- I believe that my dad at some point had the screen replaced. Could it be a loose connection? It seems unlikely since I managed to get into recovery once when I first received the phone.

[Tutorial] Flash/Root/update elephone P8000

I know what you are thinking: "Another root/flash tutorial??, it's already explained multiple times right?"
Yes that's true. But for some reason it did not work when I followed the exact steps described (I tried it on 2 different elephone P8000 phones), and I believe I'm not the only one so i created this post to help others.
I folled these step: bbs.elephone.hk/thread-6616-1-1.html#.VkcZqL8WCnN (the guide link in the "Eragon v.5.9.2" thread.
Flashing instructions:
1. Install the usb drivers and reboot your PC.
(Download link: mega.co.nz/#!55BQkKiR!OPBrnj7SXxsUbuchAjV8orT9SMAOMpbDesYTMO2DDHY)
2. Check if the drivers are installed correctly.
Go to "Device manager" on your windows PC and check if there are no yellow question marks appearing when connecting the phone to the PC​3. Download the flashtool and firmware you would like to flash:
Latest version of the Flash tool: (androidmtk.com/smart-phone-flash-tool)
Stock Rom from official forum: (bbs.elephone.hk/forum-270-1.html#.Vkcc878WCnM)
Eragon ROM: (forum.xda-developers.com/elephone-p8000/development/rom-06-9-eragon-1-0-android-5-1-t3195007)
Philz recovery Touch 6.59.0 Port P8000 Version 2: (forum.xda-developers.com/elephone-p8000/development/recovery-philz-touch-6-59-0-port-p8000-t3224478)
?CWM Recovery (didn't work for me): (bbs.elephone.hk/thread-6616-1-1.html#.VkceZL8WCnN)
4. Open the flash tool and select the scatter download file included in your firmware you downloaded.
!the next steps differ from every tutorial I've read but seem to work perfectly.
5. Turn your phone on (normal no recovery).
6. Click on the download button in the flash tool.
7. turn your phone off (the normal way)
8. The flashing should automatically start while the phone is turning off.
9. Wait for the conformation in the flash tool (green check mark).
10. Remove the usb cable from the phone and hold to power button till the phone boots.
To root:
Just install superSU from the playstore and root. (confirm with rootchecker app, also from the playstore).
If that does not work for you. Install a custom recovery following the flash instructions above. Put de SuperSU binary's on your sd card. Boot into recovery by turning off your phone. Now hold the power and volume up buttons till you see a selection menu. Select "recovery" with the volume up button and confirm using the volume down button. In recovery use the install from zip function to install the superSU binary's.
To install latest stock firmware:
Follow the flash instructions and flash the stock ROM. I recommend doing this instead of updating from the phone itself. Because I updated the firmware from the phone itself to the latest firmware using the updater on the phone and there were some small bugs. After flashing everything worked perfectly.
(sorry the links are not clickable, Because I'm a new user with <10 post I can't add clickable links in the threats i create)

I am new to fiddling around android. Would you be able to tell me what's flashing and why do we do it?

elerraoind said:
I am new to fiddling around android. Would you be able to tell me what's flashing and why do we do it?
Click to expand...
Click to collapse
Please use google.
"Flashing a custom ROM" basically means to load a different version of the Android OS. This site actually explains it very well. A custom ROM is the full Android OS customized by the ROM builder usually to make it faster, provide better battery-life or add new features.
AOSP ROMs like CyanogenMod offer stock Android which will remove things like HTC's Sense or Sprint's Apps. CyanogenMod's ROM is one of the more popular ROM.
Other Roms like Fresh 3.5 offer a ROM very similar to the default experience (with added speed and battery-life) by leaving Sense (or whatever skin your device has) and incorporating over the air updates into an updated version of the ROM.
In order to flash a custom ROM you must first root your device. For information about rooting see Matt's comment on the OP or my original answer below:
When I had the same question this is where I found it: .talkandroid.com/7686-what-is-rooting-and-why-should-i-do-it-the-pros-cons-of-android-rooting
Depending on what device you have the rooting method will be different though. Personally I suggest reading up on your device at XDA.
Click to expand...
Click to collapse
Source: android.stackexchange.com/questions/6028/what-is-the-meaning-of-flashing-a-custom-rom

vetkak said:
Please use google.
Source: android.stackexchange.com/questions/6028/what-is-the-meaning-of-flashing-a-custom-rom
Click to expand...
Click to collapse
Appreciate your detailed response. Thanks.

Flashing Problem
Hi, I'm usually quite good at figuring out these problems myself but it has been about two days and still no luck,
I've got a Elephone_P8000_20151203 build, I've been trying the root it as I hate adverts, the problem I get is when I've followed the flashing procedure and enter recovery mode where it gives you the 3 options, every time I press recovery it just loads up the phone, and if I try and enter recovery mode without using flashtools I get no command, I have tried a few different ways now and I don't seem to be getting anywhere so any help would be amazing, I've also tried a different computer OS, I've tried win7/10.
Hope somebody can help,
Regards Chris

xhris1337 said:
Hi, I'm usually quite good at figuring out these problems myself but it has been about two days and still no luck,
I've got a Elephone_P8000_20151203 build, I've been trying the root it as I hate adverts, the problem I get is when I've followed the flashing procedure and enter recovery mode where it gives you the 3 options, every time I press recovery it just loads up the phone, and if I try and enter recovery mode without using flashtools I get no command, I have tried a few different ways now and I don't seem to be getting anywhere so any help would be amazing, I've also tried a different computer OS, I've tried win7/10.
Hope somebody can help,
Regards Chris
Click to expand...
Click to collapse
Have you tried going to settings, enabling developer options, enabling OEM unlocking, then downloading SuperSU from playstore,opening SuperSU, press continue,press normal,this should root your p8000

bjbirch said:
Have you tried going to settings, enabling developer options, enabling OEM unlocking, then downloading SuperSU from playstore,opening SuperSU, press continue,press normal,this should root your p8000
Click to expand...
Click to collapse
Cheers for the reply, I should have mentioned that I tried that also and it still says "there is no SU binary installed, and superSU cannot install it" I found OEM unlocking yesterday and it got my hopes up then shot me straight back down, I was hoping that it OEM unlocking was the reason I could not access recovery,
Thanks again, Chris

To access recovery, switch phone off completely, then press power and volume UP together, you will see three options in tiny white writing,use the volume UP to move marker to recovery which is the first option, then press volume DOWN to choose recovery, you will get a screen with a green android man with a red triangle, you then have to press power and then volume up this should get you into recovery

If recovery is broken. Turn off the phone, connect to PC. Open flashtool. Load philz recovery. Click in download. Turn phone on and flashing should start automaticly. Hope this helps
Verstuurd vanaf mijn Elephone P8000 met Tapatalk

I think it's easier when you use Kingroot for root and Flashify for the recovery

ok sp flash tools wont let me flash just a recovery. It wants me to format and flash the whole phone which wipes out my imei. any suggestions?
{
"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"
}

No matter what I try, my computer will not install the drivers. I keep getting "A service installation section in this INF is invalid". Any ideas on what to do?

Nokia N1, wiped system, stuck on splash screen (Powered by Android) (Update!)

Dear Xda,
This is my situation, i had a bootloop so i ran the temporary recovery method explained in the thread "Nokia N1 Rooted with Google Play!" in the general forum of the Nokia N1
But i accidentaly removed the system partition (which boots the system and shows the boot animation etc, after the splash screen)
I can however boot into the bootloader with volume down+power as well as going into the temporary recovery to wipe and flash stuff.
I figured a way to fix this, this is to push or copy a update.zip from my pc (with the original nokia n1 files) to my nokia n1,
but the problem is adb does not recognize this device in the cmd with the command adb devices, and the hardware id is having ???? in device manager (Windows).
Does anyone maybe know a way to push files to this device in either bootloader mode or temporary recovery or maybe another way, as i am stuck with this.
If something is not clear or if i need to post images of my situation of more information please say so,
also i have the taiwanese version not the chinese and i have also all the zip files for android 5.0.1 and 5.1.1 (latest) which 1 of the 2 i need to push to my device to restore the system partition.

Ok, so far i have not gotten an answer from someone,
so i went to look around other forums and identical devices, the closest being the zenphone 2, as they use the same intel processor the intel atom z3580.
I have also looked around alot in the nokia n1 forums on search for the original taiwenese firmware as i have found a way to custom flash the device if it is hard bricked (as in no adb, system or recovery)
I found out that the new intel phone flash tool required a flash.xml file to (re)flash firmwares in order to restore it, so i have been googling around for older phone flash tool programs as i have stumbled upon a nokia n1 thread somewhere where it showed a picture of a custom flash (without the flash.xml file)
I have managed to get a fastboot connection with an old intel phone flash tool program and been trying to flash chinese firmwares to it, but so far it keeps on failing for some reason
I have a feeling that it might be possible to resurrect a broken nokia n1 with the right firmware when you only have access to the fastboot (power up+volume down), we might as well use this method if succesfull to fix bootloops if no recovery is available (as it was with my taiwanese version for some odd reason)
I will attach screenshots of what i have so far, if anyone is interesting in helping me or have an idea please say so.
p.s. i keep on trying to do more research and fiddle more with it, as it cant be more broken than it is now.
{
"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"
}

Sadly, i can not go on any further, i have tried and flashed to much files and the nokia bootloader has locked itself, neither does oem unlock commands work with a fastboot flash file, i feel like i was very close to recover the nokia n1, but now it will forever be paperweight, as i have no recovery, no system, no adb, and a locked bootloader so no fastboot anymore.
If anyone have a solution or advise i'm open for this, but until then i can not proceed to test further for people who have like me bricked their device and turned it into useless paperweight (and i feel like the nokia was really vulnerable for bricking) i kinda regret buying the nokia now though.

do you have any ROM for CN version ????? my tablet is stuck in logo, i don't know how to fix it

2111002640 said:
do you have any ROM for CN version ????? my tablet is stuck in logo, i don't know how to fix it
Click to expand...
Click to collapse
Yes i do have, do you perhaps know which CN version you had? if not i can attach/link you a CN version.

It is possible to install the same or newer Version of the Firmware, which was installed on your N1
You need a full Firmware package for your tablet (CN or TW Version).
Sent from my N1 using Tapatalk

do you have full ROM for N1 tw or cn, if you have this can you share for me plêas

i have a solution to fix this error, anybody want to fix this error may be contact me
my fb: https://www.facebook.com/hjxhjx.huhu
i had fix 2 devices to live every oke

2111002640 said:
i have a solution to fix this error, anybody want to fix this error may be contact me
my fb: https://www.facebook.com/hjxhjx.huhu
i had fix 2 devices to live every oke
Click to expand...
Click to collapse
I don't have a Facebook account. Could you post your solution on here please? Thank you

Hello there! I think I had a similar problem but I managed to unbrick my device after good 24 hours of stress and facepalming after getting it stuck in splash screen late last night. I found your thread and a few others that suggested trying Intel's Phone Flash Tool, but it didn't work for me. I thought I had no fastboot, but suddenly I managed to get it to fastboot with Power + Vol Down (releasing power shortly after pressing while holding vol down a tad longer). Turns out my device was locked, so I couldn't flash anything. I had previously flashed the recovery file of A5FMB19, but I thought it hadn't worked. Alas, again I was wrong and from fastboot I was able to get to recovery mode! From there I was able to factory reset, adb sideload the full version of A5FMB19 and now my N1 is happily running with Google Play.
So if somebody still has the same problem I guess what I'm trying to say is that even if it first seems that recovery mode is not reachable, it might still be there since the device seems to be very picky about the button presses. It was that in my case, and it suddenly worked tonight while earlier it did not... This is the post that I mainly followed https://forum.xda-developers.com/no...1-chinese-version-5-1-1-update-t3183529/page6 I guess the important thing is to find a matching ROM to your recovery image.

srsface said:
Hello there! I think I had a similar problem but I managed to unbrick my device after good 24 hours of stress and facepalming after getting it stuck in splash screen late last night. I found your thread and a few others that suggested trying Intel's Phone Flash Tool, but it didn't work for me. I thought I had no fastboot, but suddenly I managed to get it to fastboot with Power + Vol Down (releasing power shortly after pressing while holding vol down a tad longer). Turns out my device was locked, so I couldn't flash anything. I had previously flashed the recovery file of A5FMB19, but I thought it hadn't worked. Alas, again I was wrong and from fastboot I was able to get to recovery mode! From there I was able to factory reset, adb sideload the full version of A5FMB19 and now my N1 is happily running with Google Play.
So if somebody still has the same problem I guess what I'm trying to say is that even if it first seems that recovery mode is not reachable, it might still be there since the device seems to be very picky about the button presses. It was that in my case, and it suddenly worked tonight while earlier it did not... This is the post that I mainly followed https://forum.xda-developers.com/no...1-chinese-version-5-1-1-update-t3183529/page6 I guess the important thing is to find a matching ROM to your recovery image.
Click to expand...
Click to collapse
How did you manage to enter recovery after entering fastboot, i can enter fastboot just fine, but my device is in a locked bootloader state after to many flash attempts, and when i try to enter recovery in fastboot it just reboots the device back into fastboot, any suggestions or ideas?

defendos said:
How did you manage to enter recovery after entering fastboot, i can enter fastboot just fine, but my device is in a locked bootloader state after to many flash attempts, and when i try to enter recovery in fastboot it just reboots the device back into fastboot, any suggestions or ideas?
Click to expand...
Click to collapse
It's been a week and it was the first time I ever tried to flash anything, but I think that in fastboot I just selected recovery mode with the volume buttons and then pressed the power button to confirm the selection. Since I had previously managed to flash in a recovery image of the Taiwan version, it worked. My saviour was that the recovery image wasn't corrupted even though my Android itself was, so I guess there was no magic trick - I just managed to do the right things finally after wrong physical button presses. If you can't get to recovery then maybe you are truly bricked. Would these suggestions be of any help? forums.oneplus.net/threads/solved-stuck-in-fastboot-bootloader-is-locked-need-help.435522/

same boat bump!
accidently wipe data cant boot stuck on android logo
i can access fastboot but no adb (unauthorize)
on 5.0.2

Help me please - something went haywire with unlocking bootloader.

I tried to follow directions here but in my haste and stupidity I may have followed incompatible directions.
Here's where I'm at. I have TWRP 3.0.2-M1 installed. I cannot install any system images and have them run (CM13 for example). I've tried unlocking my bootloader with no success.
I don't know what to do. I cannot load any images properly, but I am desperate to get things going. Am I totally screwed?
Would really, really appreciate direction. ZE551ML. I want the nightly CM13 image to run on my phone.
When I start my phone up, I get the Red Error that tells me my system isn't verified.
Please, please help.
EDIT: I have no OS installed.

You can boot into twrp.
Your bootloader is unlocked with the warning screen .
Do you know how to flash a Rom ?
What did you use to unlock ?
If you want people to help you need to describe what you used and why

timbernot said:
You can boot into twrp.
Your bootloader is unlocked with the warning screen .
Do you know how to flash a Rom ?
What did you use to unlock ?
If you want people to help you need to describe what you used and why
Click to expand...
Click to collapse
Yes, I tried to a flash a ROM but it keeps putting me back in the Recovery.
I used Giarmix's automatic tool to unlock and it said FAILED but I guess it worked once to get me TWRP.
I'm sorry, I'm trying to provide as much info as possible.

roach9 said:
Yes, I tried to a flash a ROM but it keeps putting me back in the Recovery.
I used Giarmix's automatic tool to unlock and it said FAILED but I guess it worked once to get me TWRP.
I'm sorry, I'm trying to provide as much info as possible.
Click to expand...
Click to collapse
Giovix modder tool ?
There is an option to return to stock.
Or gimme link to the one you used if not this one

timbernot said:
Giovix modder tool ?
There is an option to return to stock.
Or gimme link to the one you used if not this one
Click to expand...
Click to collapse
Yes, that one. Returning to stock doesn't work.
I also ran the following program in an attempt to get TWRP 3.0.2-M1 to install CM13:
M_BL_upgrade_for_zf2_551ml_6.0
After this, nothing works anymore.
EDIT: TWRP 3.0.2-M1 is installed, but when I go to install a ROM, I get an error:
When I try to wipe any partition, I get "ARGUMENT INVALID".
Sigh

You put the extracted folder in C/: of PC and run batch as admin?

timbernot said:
You put the extracted folder in C/: of PC and run batch as admin?
Click to expand...
Click to collapse
What extracted folder are you referring to?

Modder

timbernot said:
Modder
Click to expand...
Click to collapse
I have been running as admin and certain commands did work, but this is not. I erased my system/cache partitions in a panic.
{
"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"
}
EDIT: Is there a magic thing I can do within TWRP? **** I'm an idiot.

Can you fastboot flash stock recovery ?
Can you get into fastboot to flash stock recovery too ?

I flashed the newest stock recovery but it didn't work, I can only boot into my bootloader now.
I tried ASUS Flash Tool and it sees my device but it remains "Connected" and doesn't want to install the .raw file.

Wow just wow.
I'm going to bed lol

timbernot said:
Wow just wow.
I'm going to bed lol
Click to expand...
Click to collapse
Sigh.
I am an idiot. Thank you for trying ot help.

I will help later but need some rest

timbernot said:
I will help later but need some rest
Click to expand...
Click to collapse
I truly appreciate your time and assistance.

Okay, here's the issue I have.
When I install CM13 and GApps, it works fine. System patched unconditionally, success, etc.
When I reset my system, I get a red screen that says "Your device has failed verification and may not work properly. Go to www.g.co/ahg (just a guess)"
Then it boots back into my recovery, where normally, it should have gone to CM.
What gives? I have no idea what to do.
I tried to use the Asus Flash tool but it cannot install to my device.
I can still use fastboot.
I suspect that my problem is that I installed a MM Bootloader without rooting or without unlocking properly and it's not all effed.
I want to cry.
EDIT 2: I've spent all night doing this. I followed this:
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
But then I got caught up. xFSTK wasn't work so I unplugged my USB, BUT THEN IT STARTED RUNNING when it was unplugged?! But GET THIS. CM 13 RUNS.
But now when I turn on my phone, I get a weird line screen and I cannot boot into my Recovery OR my Bootloader. I can only load my ROM.
What the **** is going on?!?!?!?!?

Android version before bricking device?

CM 13, so Marshmallow.
Now the screen won't even turn on. This is ****ed.
EDIT: No screen at all. Nothing works. In boot cycle. Sending it to Asus and hopefully they fix this and send me it back. I'm never unlocking the bootloader or rooting, or doing anything to a phone ever ****ing again. This should not be that hard to do.

If u can boot cm then u can install recovery using adb
Download the latest recovery image file (.img) depending on which bootloader u have (MM/L).
Place it in the root of your /sdcard folder and rename it to twrp.img.
Run the following commands via adb shell or a terminal emulator app:
su
dd if=/sdcard/twrp.img of=/dev/block/by-name/recovery
Recoveries link http://theflamingskull.com/zenfone2.html

roach9 said:
CM 13, so Marshmallow.
Now the screen won't even turn on. This is ****ed.
EDIT: No screen at all. Nothing works. In boot cycle. Sending it to Asus and hopefully they fix this and send me it back. I'm never unlocking the bootloader or rooting, or doing anything to a phone ever ****ing again. This should not be that hard to do.
Click to expand...
Click to collapse
Wow and wow and more wow !
1)What firmware did you have on when you first used the modder ..........?
2)You can use the unbrick procedure in my signature below !

LG Phone returned from repair without OS

Hello,
I received my phone back from LG to fix the motherboard issue and it did not have an OS. Actually it did have an OS called Mini OS. The boot loader is locked and it won't verify proper google firmware when I adb sideload because it's using "test keys".
I was able to get root and adb into the device. Two questions:
1. Considering that I have root to the device, how can (is it possible) I put firmware to get back to a working state?
2. Because I have root on my device which is loaded with their keys and pre-OS flashed firmware, is there any value for the community here'?
Please forgive me if this is forbidden discussion and remove this post. I haven't been on XDA for more than a couple of years and don't know how things have changed.
Thank you.

FYI I fixed this issue. If you have this problem you can fix it by pushing twrp or other recovery to the device and dd-ing it to the boot loader block.
Let me know if you want help on this.
Also let me know if you want the system image I pulled from the stock weird LG manufacturer device.

Would be interesting to see, doubt it would be all that useful but interesting nonetheless
https://www.reddit.com/r/LGG3/comments/4g8d0p/g3_flash_tool_stuck_on_mini_os_screen_please_help/ This seems to be it running on a G3
https://www.youtube.com/watch?v=k8VWVzJJ0-U and on a G Flex2

This happened to me when i flash tot and unplug it before.
Sent from my Pixel using Tapatalk

Your phone boot into bootloader? To boot into bootloader press volume down and power button at the same time until it enable. If yes, download a factory image from Google's developer website, and flash it with fast boot.

AFK269 said:
Your phone boot into bootloader? To boot into bootloader press volume down and power button at the same time until it enable. If yes, download a factory image from Google's developer website, and flash it with fast boot.
Click to expand...
Click to collapse
{
"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"
}
Thanks for the help here. The interesting thing is that you can not do this because the boot loader is locked and you can't unlock it because there is no OS. When trying to side load a factory image the image will not verify. This is because the keys are still "test-keys" and can not verify official Google factory images.
The entire OS (mini-os) seems to be an LG manufacturer OS which comes default before swapped with whatever version of the OS they're pushing.
Managed to do this by the following steps:
1. ADB Root (it worked
2. ADB push twrp image
3. find the symlink to which partition (mmcblk) that the recovery is on
4. dd the file over the partition (DANGEROUS Do not do this unless you are 100% sure you have a non-corrupt recovery and it will work on the phone)
5. Reboot and use twrp (or cwm) to flash without verification

konceptz said:
Thanks for the help here. The interesting thing is that you can not do this because the boot loader is locked and you can't unlock it because there is no OS. When trying to side load a factory image the image will not verify. This is because the keys are still "test-keys" and can not verify official Google factory images.
The entire OS (mini-os) seems to be an LG manufacturer OS which comes default before swapped with whatever version of the OS they're pushing.
Managed to do this by the following steps:
1. ADB Root (it worked
2. ADB push twrp image
3. find the symlink to which partition (mmcblk) that the recovery is on
4. dd the file over the partition (DANGEROUS Do not do this unless you are 100% sure you have a non-corrupt recovery and it will work on the phone)
5. Reboot and use twrp (or cwm) to flash without verification
Click to expand...
Click to collapse
I think that you will need to make a call to the service center to tell your situation.

I followed this and it booted just fine.

I just had my Nexus 5x's board replaced by LG due to the device hitting the BLOD. When I got the phone back, it was in the same state as the OP's phone: an unbootable MiniOS terminating with the same red screen and error code.
As suggested by ks73417, I followed the unbrick guide to just get a version of Android loaded to unlock the bootloader:
https://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
Then I flashed a recent bullhead image from Google:
https://developers.google.com/android/images
Then I relocked the bootloader. All the errors and warnings are gone and it's a clean install of the OS.
I'm surprised LG is sending back phones in this state. Those who aren't as tech savvy would probably be in for at least one more frustrating round of sending the phone back to try and get this resolved.
After all that, I'm now trading in my 5X .

picodot said:
I just had my Nexus 5x's board replaced by LG due to the device hitting the BLOD. When I got the phone back, it was in the same state as the OP's phone: an unbootable MiniOS terminating with the same red screen and error code.
As suggested by ks73417, I followed the unbrick guide to just get a version of Android loaded to unlock the bootloader:
https://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
Then I flashed a recent bullhead image from Google:
https://developers.google.com/android/images
Then I relocked the bootloader. All the errors and warnings are gone and it's a clean install of the OS.
I'm surprised LG is sending back phones in this state. Those who aren't as tech savvy would probably be in for at least one more frustrating round of sending the phone back to try and get this resolved.
After all that, I'm now trading in my 5X .
Click to expand...
Click to collapse
Hi @picodot , which bullhead image version did you use?