hello
i reinstalled my ROM after installing FREEDOM and the google play wasn't working
i installed it about a month ago and it worked out fine, i rooted the phone again but didn't do anything with it
today after using the phone for a couple of hours i plagged the charger in and then i saw that the screen is all black
and all that says is :
fastboot mode started
udc start
i tried everything with the power + vol down and it keeps getting into the same screen
the phone just stuck in this and i can't recover it
i have read the other questions that people wrote here about this problem and couldn't find an answer
PLEASE HELP ME SOLVE THIS!!!
nir3011 said:
hello
i reinstalled my ROM after installing FREEDOM and the google play wasn't working
i installed it about a month ago and it worked out fine, i rooted the phone again but didn't do anything with it
today after using the phone for a couple of hours i plagged the charger in and then i saw that the screen is all black
and all that says is :
fastboot mode started
udc start
i tried everything with the power + vol down and it keeps getting into the same screen
the phone just stuck in this and i can't recover it
i have read the other questions that people wrote here about this problem and couldn't find an answer
PLEASE HELP ME SOLVE THIS!!!
Click to expand...
Click to collapse
I was in the same situation tonight. I have the AT&T variant. I found the answer on droidforum(dot)net by member HARVESTERX:
"OK, so you're booting into fastboot and trying to ADB from there? Have you tied booting into recovery (since you said that you were able to successfully flash one)? I'm on the Verizon G2 so not too familiar if it's the same on your model, but to get into recovery I power on the phone by pressing and bring the power and volume - buttons at the same time. After seeing the LG logo I have to release both buttons and press and hold power and volume - once more which takes me into the factory reset mode. From here press the power button a few times as if I'm doing a factory reset and it loads up TWRP from there.
This has saved my ass once already because I wiped my internal storage mount by accident and deleted all my backups and ROMs, so I used a Windows XP computer (can't get any other version of Windows to recognize my device...well I know how but it involves more time than I have at the computer as it's not mine) and pushed a ROM over using ADB that way. It's been a few days so hopefully you've fixed the issue... "
This method put me into TWRP and I was able to RESTORE my phone to the backup I had done earlier this evening.
I hope this helps!
JACE759
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.
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.
So I updated my rooted 6t to Android 10 using Magisk, and everything went as expected prior to rebooting. I hit uninstall and restored images via Magisk, downloaded and installed the Android 10 update package to the inactive slot, downloaded the TWRP A/B partition module then finally installed Magisk to the inactive slot as well. Finally, from there I rebooted and it seemed to boot normally, hung a bit longer on the animation than normal but no more than 30 second or so.. it then skipped the lock screen and went straight to my wallpaper (the same one i has set, not default) BUT the system doesn't start. No icons. Can't pull up the app drawer, can't pull down the notification menu. No notification bar... Nothing.
The only thing I can do is restart the phone by holding PWR button but that just brings me right back to the same deal. I tried fastboot>TWRP recovery and was able to determine that all the system data is in fact present anyway but rebooting from TWRP also lead to the same situation.
I'm asking for advice BC the last time I messed around without knowing fully what I was doing, I hard bricked it. I'm using Blu_Spark TWRP if that makes any difference at all...
It's possible that I just need to wait longer, I read a number of reports of pixel users needing to wait hours after OTA updates but they were stock on the boot logo/animation. I'm beyond that point, only it skips the lock screen, goes straight to my wallpaper and that's it. I can't do anything at all from there.
PLEASE HELP?
Thanks!
QNE
Use MSM tool.
Download MSM tool. Unzip it on PC desktop. ConnectUSB typC cable to PC. Shutdown your OnePlus 6. Open msm download too. Click start. Press volume up and dn key simultaneously(don't touch power button). Now connect cable to phone. Progress bar of MSM download too will be active. Let it completed. Phone will boot to os. Now upgrade to Android 10. That's it.
I ended up factory resetting prior to your response, but thanks just the same. Fortunately, I didn't lose root which was my main concern anyway so no harm done. Thanks again!
Hello, I have a problem that I've tried to solve in many ways. I unlocked the bootloader a while ago and installed twrp and a custom rom for my Moto C Plus. Recently I wanted to reset it and I did it through the cell phone settings reset option. It started with twrp and then I ran the rom and everything needed for the memory card to flash. The installation happens normally and without any errors and then I reboot the phone, but it always comes back to twrp.
And I can't use the commands by the buttons, only when I reboot the phone from the bootloader inside twrp (Reboot>Bootloader), and appears written right in the lower left corner "=> FASTBOOT mode. . ." and the rest of the screen is all black.
I already tried to install the original stockrom that I got with the IMEI of my cell phone in the program Rescue and Smart Assistant from Motorola, but whenever I try to install by twrp, it says that the zip file is invalid.
If anyone can help me I would be VERY grateful. I'm desperate for a solution.
-->My brother solved the problem!!! Thanks to him.
He used the rescue tool from the program Rescue and Smart Assistant to install the stock rom back (download link: https://www.motorola.com/us/rescue-and-smart-assistant/p). He said too that this error happens because TWRP "dies" and don't work anymore
Process:
1- Remove the battery from you device
2- Open the program Rescue and Smart Assistant, click in "Rescue" and then "Phone Rescue"
3- Plug the usb cable in your device (The program should recognize your phone)
4- With this, the program will give to you the informations and under this have a buttom to "Rescue". Click it and wait the installation
5- After the installation is finished, put the battery back and the device will turn on automatically, but you have to press and hold the power buttom to turn off and turn on again
6- After turning on again, boom!! Your device has been saved ans will start normally