Database Users

[Q] Somewhat Broken Beta Streak

So I have had this US beta streak since around January, the one that says 'Dell Confidential' at boot up, but it's never really worked correctly. I purchased it from a person that I know that got it through some sort of beta testing; the details weren't provided and I didn't press him for them. Anyways, I am currently trying to get the clockwork recovery flashed and able to be booted into, although the streak is giving me every possible problem I can imagine. I'll try to provide as much background info as I possibly can.
Firmware: 1.5
Baseband Version AUS_090716_01_BOSS_EVT2_3135
Kernel Version 2.6.27
Build Number QTC_3135
OEM Version: AustinBuild_090724_03_boss_evt2_3135_FixTouchSuspend
Under About Phone > Status
IMEI 011954000020995
IMEI SV 00
Service Tag FF8R6K1 (which dell.com cannot find)
The Problems:
When I try to get into bootloader to get into fastboot, by holding the camera button down while hitting the power button, rather than going into the screen that is shown in all of the different tutorial threads, I instead go into some sort of a diagnostic menu that doesn't have an option for fastboot, as much as I have seen. There is a picture attached below.
I (think) that I can get the phone recognized by adb, although I am not totally positive. When in cmd in windows, and I type adb devices, instead of getting the proper serial number of my devices, it shows instead 0123456789ABCDE (I may not have that exact, but it does start at 0 and ends in hex at E or F, I can't remember right now and don't have it connected at the moment.)
There was one time where I was able to flash recovery.clockwork.img to where it said that it successfully flashed the img, but when I go to try and boot into recovery by holding both volume up and down at the same time, and then hitting power, the phone just hangs at a blank, black screen. It will stay there for 30 minutes and not do a thing, I can't see it via adb or fastboot.
So I then gave recovery.alt.img a shot, was able to successfully flash that, or so it told me that it was successful, but still the same problem: just a black screen.
The reason that I think that it actually was working was that after flashing the recovery image both times, I sent the command adb reboot recovery, and the phone reboots, but not into recovery, just into android. adb reboot-bootloader doesn't work at all and returns an error or nothing, I can't remember.
I then focused my attention on trying to get fastboot to work, assuming that adb was not working at all. This is where fastboot gets strange. The only way for me to get the command 'fastboot devices' to show anything at all is by holding the volume down button prior and then hitting the power button to start it. This puts the phone into essentially a 'soft brick', which my friend calls 'safe mode', where it gets totally stuck at the 'Dell Confidential' screen and will not progress past it no matter what.
So, once I am in 'safe mode', I am able to then issue a 'fastboot devices' command, which ... partially works? I hope that my totally unsure tone of voice was able to be conveyed through that message, because the info returned once that command is sent is totally confusing to me. Unlike before, where I feel as though the Streak is just lying to me by saying 0123...DEF for the device ID, for fastboot devices it just gives me a question mark .. yes, simply a ?
The weird thing is that it will follow commands. I was able to flash recovery.clockwork.img to the streak, it gave me a read out that said successful, and I got very excited. And then I pulled the battery, put it back in, held both the volume buttons, and .... the same result, the black screen. So, not allowing myself to be deterred, I got right back into fastboot, or at least my quasi working version of fastboot which may not be working at all, and flashed recovery.alt.img, which turned around and told me that it was successful as well. This time, not allowing myself to get excited, I pulled the battery and, with both volume buttons held down, hit power to try to get into recovery.
Again, I was let down and found only a blank screen. At this point, I have no idea what else to try. With the bootloader not being where it's suppose to be, not really being able to get into fastboot or adb (I think), I turn to xda to try and find some answers. Does anyone have a suggestion as to what I am doing wrong or might be missing. I am hoping that it is something that is really obvious that I feel very stupid, like I'm hitting the wrong set of volume buttons, but ... I don't think it's that easy.
Again, I feel as though the phone was getting the commands from fastboot because I sent fastboot reboot recovery, and the phone rebooted, just not into recovery but android. Same thing for bootloader, it just didn't work at all
Also, as for android 1.5 itself, almost nothing works. This appears to be running a very early edition of android where most apps just end up with: Sorry! No applicatons can perform this action, so the One touch root is kind of out of the question.
I was able to do the dialer unlock method to get EMList, but the similarities end there. I don't have the Unknown sources option or anything else after leaving dialer.
Any and all suggestions are appreciated and will be accepted and followed (within reason). I'm just at the point where I'm hoping that it's not totally broken and that with determination and hard work and some critical thinking I (we) will be able to get it working again. Hopefully it isn't a paperweight.
Thanks,
Thursday

[Q] What to double check before confirming hardware issues?

Hey guys,
I recently went to power on my Nexus 7 (2013) after a weekend of having it off, and it got stuck on the white Google start up screen with no further responses. Holding power the devices still turns off, and I am able to get into Bootloader and Recovery. From bootloader "start" just sends it back to the Google start up screen. I'm able to enter Recovery but the Android logo with the red warning triangle doesn't have the No Command script below it, Power and Vol. Up gets me into the Recovery menu. Entering recovery I get errors of : Can't open, failed to mount, can't mount etc which continues as I try to clear the cache, and wide the partition (I'd post pictures but I can't as a new poster). Moving on I tried some of the guides to flashing a new factory image with fastboot or Adb. Since I don't have normal access to the device I'm sure sure is USB debugging was enabled or not, but in bootloader that shouldn't matter correct? Anyways here is where I hit my snag, my device is still in LOCKED bootloader, and the fastboot oem unlock command gets me to the unlock bootloader screen, but after I select and confirm the option the device freezes and no progress is made. From that screen I am still able to turn it off by holding the power button down, so I'm somewhat confused about it becoming unresponsive to the unlock bootloader command. All of the other fastboot commands like fastboot erase cache come back with "Failed: Too many Links". From my knowledge I've checked through everything I can do software wise, and I was curious if you guys had any input before attributing this all to a hardware failure? I've got some experience rooting and flashing custom ROMS on my phone so I have somewhat of an understand of all this but its by no means vast. Thanks for the help, and I tried to provide you with as much info as possible but I'll attempt to answer additional questions to the best of my ability.
Stock Nexus 7 2013
Version : KTU84P
Bootloader: Locked, FLO-04.02

scbikep2 said:
Hey guys,
I recently went to power on my Nexus 7 (2013) after a weekend of having it off, and it got stuck on the white Google start up screen with no further responses. Holding power the devices still turns off, and I am able to get into Bootloader and Recovery. From bootloader "start" just sends it back to the Google start up screen. I'm able to enter Recovery but the Android logo with the red warning triangle doesn't have the No Command script below it, Power and Vol. Up gets me into the Recovery menu. Entering recovery I get errors of : Can't open, failed to mount, can't mount etc which continues as I try to clear the cache, and wide the partition (I'd post pictures but I can't as a new poster). Moving on I tried some of the guides to flashing a new factory image with fastboot or Adb. Since I don't have normal access to the device I'm sure sure is USB debugging was enabled or not, but in bootloader that shouldn't matter correct? Anyways here is where I hit my snag, my device is still in LOCKED bootloader, and the fastboot oem unlock command gets me to the unlock bootloader screen, but after I select and confirm the option the device freezes and no progress is made. From that screen I am still able to turn it off by holding the power button down, so I'm somewhat confused about it becoming unresponsive to the unlock bootloader command. All of the other fastboot commands like fastboot erase cache come back with "Failed: Too many Links". From my knowledge I've checked through everything I can do software wise, and I was curious if you guys had any input before attributing this all to a hardware failure? I've got some experience rooting and flashing custom ROMS on my phone so I have somewhat of an understand of all this but its by no means vast. Thanks for the help, and I tried to provide you with as much info as possible but I'll attempt to answer additional questions to the best of my ability.
Stock Nexus 7 2013
Version : KTU84P
Bootloader: Locked, FLO-04.02
Click to expand...
Click to collapse
A clear explanation of the problem alone with everything that you have tried will do for reporting hardware/software issues and also help others help you.
Sent from my Nexus 5 using Tapatalk

How to boot LG Leon into recovery?

I've successfully rooted my T-Mobile LG Leon, and I've successfully installed TWRP, but for the life of me, I can't get the phone to boot into recovery. I can RE-boot into recovery from TWRP manager, but I can't actually boot into it from a fully powered-down state. I've tried every combination of the power and volume buttons I can think of, and nothing ever works. Download Mode works, the factory restore menu works, but I CANNOT get into recovery. Is there a very specific set of instructions anywhere that I can follow?
EDIT: Okay, I finally figured it out: You need to actually select to do a factory reset, and it throws you into the recovery menu.

Yeah, it was because the stock recovery doesn't exist as a menu, when you're running stock and enter the adb command "adb reboot recovery" it will reboot to the "factory reset mode" and the actual file of this mode is stored on partition named "recovery". Choosing the factory reset option boots the custom recovery because it replaces the said " factory reset mode" and that's the trick.

You can access recovery from the powered off state by holding volume down and power on until you see the lg sign. Without letting go of volume down, depress on the power button before clicking it back in and holding both buttons in until you see twrp pop up.

If you reboot to recovery now, it''ll probally say secure booting error. Simply go to the Developer options and enable OEM Unlock and that'll make you boot to it

You boot in the download mode by holding the vol up 10 seconds and during this 10 seconds you insert the usb. The LG Leon brand screen will come on a minute then it will go into download mode. It says not to unplug until firmware is done updating. So I guess you should have your custom recovery or whatever before you do this. I have only got this far, and thusly it sits. All Dressd up with no where to go...haha

kruc Ire said:
You boot in the download mode by holding the vol up 10 seconds and during this 10 seconds you insert the usb. The LG Leon brand screen will come on a minute then it will go into download mode. It says not to unplug until firmware is done updating. So I guess you should have your custom recovery or whatever before you do this. I have only got this far, and thusly it sits. All Dressd up with no where to go...haha
Click to expand...
Click to collapse
can't find "enable OEM" at all in developer options. have phone hooked computer, and on, it's sending and receiving. No OEM. Isn't there.
See, I'm trying to root this without using KingUser. Since I found that it was pretty easy to do from the very beginning with Samsung, and I just don't see any way to do it here. I can't get ADB Devices command to see the phone.

kruc Ire said:
can't find "enable OEM" at all in developer options. have phone hooked computer, and on, it's sending and receiving. No OEM. Isn't there.
See, I'm trying to root this without using KingUser. Since I found that it was pretty easy to do from the very beginning with Samsung, and I just don't see any way to do it here. I can't get ADB Devices command to see the phone.
Click to expand...
Click to collapse
I think I have the same issue, but I rooted my phone using kingroot, I haven't tested the adb commands, I just want to use twrp but no luck, it says Secure booting error and I can't find OEM Unlock option in Developer Menu.

duffycop said:
I think I have the same issue, but I rooted my phone using kingroot, I haven't tested the adb commands, I just want to use twrp but no luck, it says Secure booting error and I can't find OEM Unlock option in Developer Menu.
Click to expand...
Click to collapse
I got a good way to get it rooted with SuperSU. Ran a command window script I found out there. It worked and now I have SuperSU root. I also figured out how to get into recovery. It looks as though my phone is not the standard LEON that people are talking about here. It's got a few designations, and the T Mobile site advertises a Leon that seems very similar and is called by the name most are using..
Anyhow my LG Leon is designated as a H320. It also carries a v10 desiganation, v10b. The v10 is variable from a-h or a-i. It would seem that once it is updated to 5.1.1 android it gets upped, and becomes unrootable. Mine being a v10b was rootable, but it took me a while to get used to it, and make the command window work.
Unfortunately for me one of many things I tried before getting it rooted, was ADB fastboot. And since this told me to wait for too long, I pulled the plug on it and pulled the battery to get back into "normal" operations. Perhaps I should have waited, because after finding out a few things about the phone, I discovered the true way to get it into recovery:
The real way into recovery for my phone, is to (from power off state) hold the volume up, a few seconds, then plug the USB cable which is going to the computer into the phone. While holding the volume up until it comes to recovery. This will activate the recovery, (Now for me it activates that fastboot command line...and does nothing else). This was the bit of information I could have used from the beginning, that no one knows. All these places tell you to hold the power and volume up, and then let off power when the screen changes, but that never worked even once. You just hold the volume, and plug the USB from computer. This works.
For me it goes into a "FASTBOOT" header at the bottom of the screen that never changes.
I believe it does this because of my unsuccessful attempt to fastboot it before. And it does not have the right driver to get recognized in the computer. So I'm screwed as far as the recovery goes now.
It is rooted though. And it doesn't seem to have any alternate ROMS available anyways. so we're dealing with the loss of the recovery.
When I do try to use an app such as TWRP manager or CWM (ROM) Manager to reboot into recovery, I get a "boot certification verification -1" error instead of the fastboot line at the bottom of the startup screen and it boots normally from there. So many people asked about this "boot certification verification -1" and NO answers are available anywhere online. So that's where it stands for this phone right now.
Anyone know what driver I should use to get the thing recognized in the computer? I have downloaded a zipped fastboot tools, and it won't get recognized inside the driver manager as "android" only as "unknown device" so I can't use that route....I'm thinking about doing a factory reset to try to erase the fastboot attempt. That may not help though. Anyone?

kruc Ire said:
I got a good way to get it rooted with SuperSU. Ran a command window script I found out there. It worked and now I have SuperSU root. I also figured out how to get into recovery. It looks as though my phone is not the standard LEON that people are talking about here. It's got a few designations, and the T Mobile site advertises a Leon that seems very similar and is called by the name most are using..
Anyhow my LG Leon is designated as a H320. It also carries a v10 desiganation, v10b. The v10 is variable from a-h or a-i. It would seem that once it is updated to 5.1.1 android it gets upped, and becomes unrootable. Mine being a v10b was rootable, but it took me a while to get used to it, and make the command window work.
Unfortunately for me one of many things I tried before getting it rooted, was ADB fastboot. And since this told me to wait for too long, I pulled the plug on it and pulled the battery to get back into "normal" operations. Perhaps I should have waited, because after finding out a few things about the phone, I discovered the true way to get it into recovery:
The real way into recovery for my phone, is to (from power off state) hold the volume up, a few seconds, then plug the USB cable which is going to the computer into the phone. While holding the volume up until it comes to recovery. This will activate the recovery, (Now for me it activates that fastboot command line...and does nothing else). This was the bit of information I could have used from the beginning, that no one knows. All these places tell you to hold the power and volume up, and then let off power when the screen changes, but that never worked even once. You just hold the volume, and plug the USB from computer. This works.
For me it goes into a "FASTBOOT" header at the bottom of the screen that never changes.
I believe it does this because of my unsuccessful attempt to fastboot it before. And it does not have the right driver to get recognized in the computer. So I'm screwed as far as the recovery goes now.
It is rooted though. And it doesn't seem to have any alternate ROMS available anyways. so we're dealing with the loss of the recovery.
When I do try to use an app such as TWRP manager or CWM (ROM) Manager to reboot into recovery, I get a "boot certification verification -1" error instead of the fastboot line at the bottom of the startup screen and it boots normally from there. So many people asked about this "boot certification verification -1" and NO answers are available anywhere online. So that's where it stands for this phone right now.
Anyone know what driver I should use to get the thing recognized in the computer? I have downloaded a zipped fastboot tools, and it won't get recognized inside the driver manager as "android" only as "unknown device" so I can't use that route....I'm thinking about doing a factory reset to try to erase the fastboot attempt. That may not help though. Anyone?
Click to expand...
Click to collapse
I dunno, I have the H340AR, with this phones happens the same that with the Samsung Galaxy Ace 3, there are, 3G versions, 4G versions, regional versions, etc.. GA3 have 7275R, 7275B, 7272L, 7272T, I dunno, maybe if we could get a device tree for a H340 and an H320 we could make some TWRP and CM compiling, but I just can't figure it out how to make a device tree or even where to begin..
I successfully rooted my H340AR with Kingroot, it works like a charm. I haven't tried fastboot and I tried to install TWRP in this link https://dl.twrp.me/c50/ but I get that F error "Secure booting error". I guess I have my bootloader locked, so I'm trying to figure out how to unlock my bootloader.
I'm trying to contact with some developers and see if anyone can help me build a device tree.

]
Hi, I have that same phone H340AR LTE. I rooted it with Kingroot and also tried to use TWRP to gen into recovery and got that Security error. I only pulled out the baterry and turn it on again so it booted normally. I made a factory reset because I read that it could be a problem of OTA firmware update. Then I installed TWRP and BusyBox again and tried to get into recovery from TWRP option. When I did that, it showed up the Android lying in his back with a red triangle. I pulled a out the battery again and yes, it seems very dumb and simple but it worked and could reboot the phone.
However, I can't get into recovery from TWRP yet. I read that the problem with us not being able to unlock the bootloader(we don't have the OEM option) is because Leon has Lollipop 5.0.1 and OEM is for 5.1.1

pedrovay2003 said:
I've successfully rooted my T-Mobile LG Leon, and I've successfully installed TWRP, but for the life of me, I can't get the phone to boot into recovery. I can RE-boot into recovery from TWRP manager, but I can't actually boot into it from a fully powered-down state. I've tried every combination of the power and volume buttons I can think of, and nothing ever works. Download Mode works, the factory restore menu works, but I CANNOT get into recovery. Is there a very specific set of instructions anywhere that I can follow?
EDIT: Okay, I finally figured it out: You need to actually select to do a factory reset, and it throws you into the recovery menu.
Click to expand...
Click to collapse
when i pressed factory reset all it did was to a factory reset even though i flashed twrp.img successfully... help?
lg leon h345 lollipop 5.1.1

This device has a locked bootloader. If you flash a custom recovery on it, it will not boot into recovery, but will report a security issue. You will lose all recovery functionality, including factory reset, adb, fastboot. If your phone fails to boot, you have a brick.

Weird Root issue / Assistance please

Hi, I bought a second hand zte axon 7 a2017. I want told it was rooted or anything. Power button is squashed in so got it for cheap so bought it. Phone runs fine on stock rom and for restarting etc I use mi pop and power button can still be used by poking it hard at an angle with stick etc. I'm familiar with rooting, flashing etc but it is the first time I'm using zte so it's bit different.
Issue is I want to root it to get rid of bloatware etc. I downloaded Root Check app and it says it is rooted and busybox is installed but there is no super user app. Funny thing is I have no means to check if bootloader is unlocked and can't even boot to bootloader mode as it just gets stuck at zte logo when I try to boot to bootloader mode from recovery mode. I get to recovery mode by restarting the phone from mi-pop and holding the volume up button. I don't even think there is custom recovery installed too which I don't know how that's possible as my understanding was custom recovery needs to be installed earlier in order to root.
Can someone please throw some light and give me some guidance. I want to go full stock but rooted and want custom recovery too just so that i can make a nandroid back up.
I'm on Mi favor 4.0
ZTE_A2017V1.0.0.B07.0
Thank you in advance

I'm on the US variant so I'm not too familiar with yours. I would suggest starting from stock, and downloading MiFlash, and the latest MiFlash edl package for your variant.

Jay_Nz said:
Hi, I bought a second hand zte axon 7 a2017. I want told it was rooted or anything. Power button is squashed in so got it for cheap so bought it. Phone runs fine on stock rom and for restarting etc I use mi pop and power button can still be used by poking it hard at an angle with stick etc. I'm familiar with rooting, flashing etc but it is the first time I'm using zte so it's bit different.
Issue is I want to root it to get rid of bloatware etc. I downloaded Root Check app and it says it is rooted and busybox is installed but there is no super user app. Funny thing is I have no means to check if bootloader is unlocked and can't even boot to bootloader mode as it just gets stuck at zte logo when I try to boot to bootloader mode from recovery mode. I get to recovery mode by restarting the phone from mi-pop and holding the volume up button. I don't even think there is custom recovery installed too which I don't know how that's possible as my understanding was custom recovery needs to be installed earlier in order to root.
Can someone please throw some light and give me some guidance. I want to go full stock but rooted and want custom recovery too just so that i can make a nandroid back up.
I'm on Mi favor 4.0
ZTE_A2017V1.0.0.B07.0
Thank you in advance
Click to expand...
Click to collapse
Okay, couple o' things:
- If your bootloader is unlocked, there should be a screen when your turn on the phone that says 'Your phone can't be checked for corruption. Please lock the bootloader' which is there for around 10 secs. If you use the volume buttons from there you should be able to select recovery or bootloader
-It is possible that you don't even have a working bootloader mode. IN CASE THAT YOU DON'T HAVE THE SCREEN I PREVIOUSLY TALKED ABOUT, try with adb: install adb, enable usb debugging, authenticate in the phone, "adb reboot bootloader". If it reboots into the bootloader (Should say START in green plus some text) then you can unlock the bootloader. But follow a guide before attempting that, or you'll risk a brick
-Having the stock recovery doesn't necessarily mean that the phone is not rooted. If you have the stock recovery it could be because the previous owner simply rooted it, used it, then flashed the stock recovery and sold the phone like that. Which is really weird in itself
-What you should do to recover from this mess is use MiFlash. Find a package called "A2017_NOUGAT_FULL_EDL" (might have a version number somewhere, just use the most recent). Enable OEM unlocking and USB debugging, then issue "adb reboot edl". The phone seems off but it's not. Now unpack the file and install it to the phone with MiFlash.
After you reflash the system you can proceed with a guide. If you get the warning screen when you turn on the phone then your bootloader is already unlocked and you can proceed with installing TWRP (maybe via axon7tool) then flashing Magisk.

axon7 stuck in loop

Hi all ....sure someone has asked this before but........
When I power on my phone it jumps directly into Start screen with a message "visit this link on another device g.co/ABH. Then it shuts down. If I press the volume key within 5 secs it will go to the next screen which has recovery, fastboot power off etc.....any option I select at that point it restarts and goes back to the first screen. I have tried ADB devices and it cannot find the phone. When I check device manager and select "show hidden devices" it shows android phone/android composite ADB Interface and under portable devices it show ZTE A2017U.
It makes no difference if the phone is plugged in or not as it does not recognize it.
Thoughts much appreciated. Chuck

@here2for: You're getting the "visit this link on another device" because your bootloader is unlocked. This is just a guess, but you're probably running the stock ROM, and the system partition has probably been modified by whatever means, so the phone shuts down after this screen as a result of failing the bootloader's dm-verity check. dm-verity can be disabled but it must be done manually. Am I correct in assuming that you are running a stock ROM?
ADB commands wont work on the bootloader screen, except when booted into FTM mode or recovery.

AnonVendetta said:
@here2for: You're getting the "visit this link on another device" because your bootloader is unlocked. This is just a guess, but you're probably running the stock ROM, and the system partition has probably been modified by whatever means, so the phone shuts down after this screen as a result of failing the bootloader's dm-verity check. dm-verity can be disabled but it must be done manually. Am I correct in assuming that you are running a stock ROM?
ADB commands wont work on the bootloader screen, except when booted into FTM mode or recovery.
Click to expand...
Click to collapse
Yes stock...

Nothing going on here,continue walking

here2for said:
Yes stock...
Click to expand...
Click to collapse
If you've lost recovery and lost boot, you're going to need to use EDL.