Database Users

[Q] Vega stuck?

Situation:
Advent Vega running r6 Modaco ROM by Paul
Ubuntu 10.10 desktop PC in case it's needed
Tried to activate the USB Host Mode, as I wanted to plug a USB stick
It had been done before flawlessly.
The device came to a black screen with a prompt: "Starting Fastboot USB download protocol".
The device is unresponsive. Powering off the device and turning it on again brings only the same black screen with the prompt.
I've read somewhere that it's not bricked, but I certainly can't bring it to work. Has anyone encountered this issue?

Re-flash original rom from recovery. Power off and fully charge. Then hold down the back button for 2 sec then power for 2 sec then back for 2 sec. You also need to install the recovery drivers from the advent website. Not sure how that goes with ubuntu. Good Luck

First of all, thanks for your help.
Sigh. I've tried putting the device in Recovery mode (with a timer to count the seconds for every press) and the same Fastboot screen appears.
The lsusb command doesn't return any changes after plugging the Vega either, so I can say the computer is blind to the device. I have another Android device which is recognized flawlessly.

It took me a few attempts to get my device into recovery. Just keep trying with the device plugged in to your pc, eventually i got a unknown device in hardware manager. I then had to install the recovery drivers to get the device to show up.
I dont use ubuntu so cant tell you if its any different.

Oh,, it is. Nobody programs drivers for Linux, and Advent is no exception. I guess I can try and... compile the Windows ones?
For what it's worth my device is not recognised no matter where I plug it, so adb is out of the question.

Using a windows pc would be the easiest. Advent only likes windows for the time being. Sorry i cant help any further, i am not a Linux user.

Then I'll try tomorrow in college. Thanks for your help!
...Forgot to ask: Has anyone had the issue I'm reporting and successfully solved it after flashing?

I've never heard of a Fastboot prompt before, however, as far as I know, getting in to recovery should always be possible.
1) Get the screen on (doesn't matter what is on it).
2) Make sure it is unplugged.
3) Hold power for ~7 seconds until the screen turns off.
4) Plug it in and wait for the charge light.
5) Plug in the USB cable.
6) Hold back.
7) While holding back, press power for 1 to 2 seconds and release (keep holding back)
8) Within 2 seconds you should hear the PC's found USB noise (the screen will not turn on)
9) Once you hear the PC's USB connect noise, you can release back, install the nVidia driver (not ADB driver) and run the FW updater.
PS: I think devs would actually be interesting in getting it in fastboot mode. I wonder how you did that.

rpmccormick said:
PS: I think devs would actually be interesting in getting it in fastboot mode. I wonder how you did that.
Click to expand...
Click to collapse
I *think* I got that prompt because my device was already in USB host when I intended to toggle USB host. However, it's kind of disheartening to hear that the issue is new...
Shall I post a picture of the prompt?

Here is a (regrettably very poor, I'm no photographic whiz and the college lightning conditions are horrible) picture of the Fastboot prompt I receive.
{
"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"
}
I've tried to enter Recovery mode today in one of college's computers (Windows XP). The device was recognized as "Nvidia ANdroid Fastboot device" after executing the recovery mode operation successfully. I was prompted to install the drivers, which I did, I was warned that they were unsigned, but on executing the Advent updater I had the following output:
Pressing Enter leads to the console closing and no changes have been done on the device: I'm not told that the image has been installed or anything, the Fastboot screen is still there, and powering on and off does bring me to the same than before.

Hi - I'm now in the same situation with the Fastboot error and no recovery no matter what I try.
Have you been able to boot to recovery / flash your Vega or is it still sitting with the error message ?

I'm going to try again today (Free day, no college )

A re flash will sort it out. I done it 5 times in the past 2 days to test CWM. Just count 2 seconds back button, 2 seconds back and power and 2 seconds back button alone again and it will be in recovery. I do it every time first time. It's just a matter of getting used to it. Then plug the vega in and it will recognise it, you will see by starting the original 1.08 firmware again, the vega screen is blank, no back-light.

I couldn't do it yesterday, but it worked today. I am now on stock 08 and I'm very happy. Thanks for all the help!

Dead nexus 4?

Hi guys, this is my first time posting problems like these as I've never encountered anything I can't fix by myself or with help from fine developers and the community here, but now I'm desperate so I wanted to give it a shot.
Anyways here's what happened. My battery died, along with my USB port (the latter of physical damage - it's not burned just the port got damaged from usage I guess). Anyways, I got original replacement parts, put them in all good. And now when I plug in the charge cable, the LED briefly flashes green and after that nothing happens. However, I found out that if I hold power and volume down and plug in the USB cable then, bootloader turns on. It's interesting how the bootloader was marked as locked even though I unlocked it ages ago. Anyways, when I try to start it normally it shows the Google logo, and after a second or so, it shuts down completely (after the screen goes off, the green LED flashes again). I tried doing rebooting bootloader and recovery, same thing occurs. I tried using factory images and here's the weird/interesting part. When I manually flash the images from the latest 5.1.1 set, everything passes except when I tried doing fastboot flash data userdata.img . It downloads as it should, but it stops after the write part (it says that it can't flash a filesystem with type ' ' - Same goes for fastboot format and fastboot wipe and fastboot erase). However, when I use flash-all batch, it passes as it should (write phase included - or that's at least what it says), but still, the phone won't turn on. I can't do fastboot boot recovery.img as it gives the same result. I should note that I did try fastboot oem unlock, and it pops up the confirmation screen and all, and when I press yes, it works as it should, unlocks the bootloader (I know since when I booted into bootloader again, it showed that it's unlocked, and on the Google logo it shows the little symbol on the bottom), but shuts down on the Google logo again. Flashing any other custom made image (for example this http://dmitry.gr/index.php?r=06.+Thoughts&proj=02.%20Android%20M%20on%20Nexus4 Android M image) gives the same outcome. I really ran out of ideas and could appreciate any help or at least ideas on what could be broken on it so I can let it rest in peace.
Also might be noteworthy that my Ubuntu didn't recognize anything when I attached it in fastboot. As in nothing happened.
Here are screenshots of the fastboot output if someone's interested (ignore the red marking on the screenshot, it was for a friend ):
{
"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"
}

I think you flash the recovery the wrong way.
To flash via fastboot, this is the command:
fastboot flash recovery twrp-2.8.x.x-xxx.img
Source: http://androiding.how/how-to-install-twrp-recovery-via-fastboot/
You tried to flash a recovery in the kernel location.
To flash a kernel via fastboot:
fastboot flash boot boot_name_img

dcop7 said:
I think you flash the recovery the wrong way.
To flash via fastboot, this is the command:
fastboot flash recovery twrp-2.8.x.x-xxx.img
Source: http://androiding.how/how-to-install-twrp-recovery-via-fastboot/
You tried to flash a recovery in the kernel location.
To flash a kernel via fastboot:
fastboot flash boot boot_name_img
Click to expand...
Click to collapse
Yeah sorry those are typos, I came from work and I was tired as hell while I was posting this. If you are referring to the first screenshot, I wasn't flashing the recovery, I was simply trying to boot it off my PC without actually flashing it. Anyways, the recovery flash that I did afterwards was ok, as well as any other except for /data. I think that's the culprit, but it still wouldn't explain why the phone shuts down as soon as it tries to (at least to my understanding) load the kernel. Boot.img is ok, so that can't be the problem.

Hi,
Have you had any luck? I am having the exact same problem with my new battery and charging port replacement which are all genuine parts.
Thanks

[SOLVED] Can't boot, can't boot recovery, oem locked, usb debugging disabled

Happened when I was updating twrp:
I downloaded the .img from their website, booted into my older version of twrp, went to flashing pressed the butting in the bottom right corner, selected the file and selected 'recovery'
Said it was successful, so I rebooted, then it wouldn't do anything anymore except for fastboot.
1. Can't boot into recovery
2. Can't boot normally
3. USB debugging disabled
4. oem locked
Only thing I can enter is fastboot.
I followed this guide, but no luck on my end.
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/

Have you tried this?
http://forum.xda-developers.com/oneplus-2/general/guide-return-op2-to-100-stock-unbrick-t3229606
and
All in one toolbox by mauronofrio.
I my self had lost recovery myself and flashed stock image in toolbox and then flashed image from above link to restore to stock and started custom rom process again.
Should not erase twrp once recovered if it has reflash your previous version of twrp or hybrid version.
Hope this helps.

passion8059 said:
Have you tried this?
http://forum.xda-developers.com/oneplus-2/general/guide-return-op2-to-100-stock-unbrick-t3229606
and
All in one toolbox by mauronofrio.
I my self had lost recovery myself and flashed stock image in toolbox and then flashed image from above link to restore to stock and started custom rom process again.
Should not erase twrp once recovered if it has reflash your previous version of twrp or hybrid version.
Hope this helps.
Click to expand...
Click to collapse
It's no use because oem is locked. That means I can't flash anything.

toolbox should still help you unlock bootloader again

Just use the Qualcomm factory restore image to return the phone to original shape of things.

passion8059 said:
toolbox should still help you unlock bootloader again
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"
}
pitrus- said:
Just use the Qualcomm factory restore image to return the phone to original shape of things.
Click to expand...
Click to collapse
I have no idea how I would do this without being able to flash anything.

Do you mean that the Qualcomm download program also crashes like fastboot? Sounds like you either have some problems with your windows installation or perhaps you haven't searched for and downloaded the Qualcomm restore if your still trying to flash the ordinary way instead of the emergency way.

Was able to fix it when I was messing around. Not sure what I did but it worked.
Thank you for all your help guys

Theevilsocks said:
Was able to fix it when I was messing around. Not sure what I did but it worked.
Thank you for all your help guys
Click to expand...
Click to collapse
I'm having this problem too, and this isn't helpful. What were the last steps, or at least some of them, that you took to get it working? Which toolkit/script/program were you using? etc

Redjax said:
I'm having this problem too, and this isn't helpful. What were the last steps, or at least some of them, that you took to get it working? Which toolkit/script/program were you using? etc
Click to expand...
Click to collapse
I used this tool: http://forum.xda-developers.com/oneplus-2/general/guide-official-op2-stock-reset-to-oos-3-t3402020
I fiddled around a bit with it, but I'm not sure what I did, and I already deleted the files.

Theevilsocks said:
I used this tool: http://forum.xda-developers.com/oneplus-2/general/guide-official-op2-stock-reset-to-oos-3-t3402020
I fiddled around a bit with it, but I'm not sure what I did, and I already deleted the files.
Click to expand...
Click to collapse
Literally JUST finished with this guide, and my OP2 is alive again! I was going to come back and post. Thanks for the link.
Anyone trying to use this guide without success:
There's one very important step I somehow missed. You MUST disconnect your phone, hold the power button for ~15-20 seconds until it's off, and hold the Volume+ button, THEN plug it back in. Your computer will make the "device connected" sound, but the screen will stay black. THIS IS OK! That means you're in a special recovery, which is where you need to be for the tool.
I also installed the certificate file in the folder I downloaded, then rebooted (it did not work before a reboot, but did work after).
So, the steps:
1. Download the files, make sure your signature signing for drivers is off.
2. Install the trusted certificate, then the driver.
3. Reboot PC
4. Power off phone (hold power for 15-20 secs), hold volume+, then connect through USB (wait for device connected sound, screen on phone will still be black)
5. Run the tool (I ran as admin, not sure if that's required)
6. Weep with joy that you finally found a solution that works.

Bootloop Android 10: enablefilecrypto_failed boot issue after recent update

I got an OTA security update few days back. The update was done successfully. Then I ran out of charge and the phone switched off during usage. When I charged and tried turning back it on, the phone got stuck in the android one screen and it rebooted. It again got stuck in the android one screen and the following message opens up in android recovery mode.
Code:
Android Recovery
Nokia/Dragon_00WW/DRG_sprout
10/QKQ1.190828.002/00ww_4_10D
user/release-keys
Use volume up/down and power.
Code:
Cannot load Android system. Your data may be corrupt.
If you continue to get this message, you may need to perform
a factory data reset and erase all user data stored on this device.
Then it shows options to select either Try again or do Factory data reset
The following code is shown at the bottom
Code:
Supported API: 3
Boot Reason: enablefilecrypto_failed
I found a similar issue in Nokia 7.1 after January update. The phone does not boot up. Is there a way to solve this issue?
I have some important data in my phone. Is there a way to recover them before resetting the phone?
Note: The phone is in stock condition with only usb debugging on.

Change slot, boot the device make sure there's enough storage available and then apply update.

same probelm , it return to recovery mode , any help

On these phones. If phone stuck on Android One screen.
And when doing factory reset from recovery, if device stuck at wiping data.
Then it is a dead EMMC.

Same problem, can anyone help?

today i tried to flash OSt service tool this type problem facing device... than find [15:15:42::203][03964] [FB]: [Recv] FAILError flashing partition : Write Protected this error.... thats mean motherboard damage.
Sent from my TA-1054 using Tapatalk

D-Mi said:
Change slot, boot the device make sure there's enough storage available and then apply update.
Click to expand...
Click to collapse
Tried it and no improvement. Could you explain in detail so that I'll check whether proceeded correctly or will try again.
Is there any way in which I can recover the data even before the problem being solved?

Jenish_SweetRascal said:
Tried it and no improvement. Could you explain in detail so that I'll check whether proceeded correctly or will try again.
Is there any way in which I can recover the data even before the problem being solved?
Click to expand...
Click to collapse
At this point there's no way to recover your data, and the guide to change the current active slot you can find in the below link
https://www.google.com/amp/s/www.te...-stuck-on-download-mode-after-ota-update/amp/
The issue mentioned might not be similar but the solution you're looking for could be it I had a similar problem with a 7.1 that can't boot after a security patch update and everytime the update will download and after restart the phone will throw error and ask to factory reset I couldn't test this method on that phone as the person had set it up for work after a reset and willing to hold till he can visit a service center. And he said he didn't have much storage at the time of update so it got corrupted somehow

I tried the method I mentioned by changing the slot, my current slot is b and update is supposed to install on a, a is corrupt or something as soon I changed active to a the device will bootloop in android one screen and go to failed page and ask for reset after which it will boot on slot b, also tried to install the Feb SP manually which installed fine via adb but again after reboot it will act same, so the only way is to visit a service center or better pay it directly for a bootloader Unlock service to avoid any future software problems

?
juwelrana091 said:
On these phones. If phone stuck on Android One screen.
And when doing factory reset from recovery, if device stuck at wiping data.
Then it is a dead EMMC.
Click to expand...
Click to collapse
R u sure bro....ost is detecting my phone though

emmc damaged device also detect fastboot... when u try to flash through ost tool u will get those error. check ost tool log data... if it say write protected than u should be sure emmc damaged
{
"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"
}
Sent from my TA-1054 using Tapatalk

Same issue I was facing but is fixed
So what did I do?
Downloaded stock ROM and installed using OST LA.
Then the update was installing but failed. [I was trying from last 1-2 months but getting same enablefilecryto_failed message but finally I solved it]
I downloaded OTA from website of same update and installed via ADB.
After installin OTA, It said it needs to "Format data" upon reboot.
I formated and mobile now has "Stock ROM".

How to bypass fastboot low battery warning / FAILED (remote: Warning: battery's capacity is very low)

Hello Everyone I'm writting this post to hoping that This would help many people. Because I didn't find any proper solution for this on the internet.
Scenario: Suppose you flashed wrong file or did something wrong and somehow you bricked your device in such a state where your device will only go to fastboot mode stable or unstable fastboot mode ( fastboot restarts itself after few seconds).
Means your boot/recovery all destroyed. Luckily your bootloader is unlocked. So you felt realx thinking that you can flash recovery/boot from fastboot to fix your device. Then you flashed an image through fastboot and saw an warning like " FAILED (remote: Warning: battery's capacity is very low)".
{
"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"
}
Thats when the problem begins .
It's because before device got bricked it had very low charge. And without boot or recovery image your device don't know how to charge itself. So weather if your device is in fastboot or edl 9008 don't expect it to charge itself. And by fastboot rule it won't accept any file if it has low battery.
For exactly below 3478mV any file writing is unacceptable.
I found a solution on XDA How to fix the 'Low Battery' fastboot loop . Basically it's a fastboot script which restarts bootloader in a continues loop to charge it in the mean-time of reboot to fastboot.
Code:
@echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
I mean no disrespect to that post, The way it was trying to do it maybe it make some sense but not much.
Because like others I have run this script for several hours for several times and got no result. I was running this script on laptop then i thought maybe laptop is not giving proper output delivery. Then I tried with my desktop back usb port but no good.
Instead for running this script so long that in those thousands reboot my device surely lost some of its lifetime early and it corrupted my internal partition which I've discoverd after fixing my device.
Ok then the next option I had was opening the backshell which I don't want. Tried customer service they denied because of unofficial device. Local shops failed also they tried to open back shell but I didn't let them.
So your'e basically doomed like me because Brands like realme doesn't provide any flash tool/flash tool credentials for free. And remote unbrick is very much costly.
Solution:
After trying many things I found an App on play store Called Bugjaeger Mobile ADB - Develop & Debug via USB OTG.
Requisitions :
1. NO Root Required
2. App itself
3. Good OTG cable
4 Proper USB cable
5. Nothing else
For stable fastboot user:
First download the app in a device which support OTG connection. plug in otg cable.
Now connect your device to other device via OTG in fastboot mode. Now press on < > This icon and type your command like you do In pc
for example "fastboot flash recovery" after recovery give a space and click on attachment icon in the top right corner then select your file. Then run the command .
Boom you have successfully ignored fastboot low battery warning. Enjoy.
For unstable fastboot users:
I have calculated that my device was restarting in every 5 secons. could be different for you.
So what I did. Before going to fastboot mode the app show some AD.
so first disable it by adding private DNS like dns.adguard.com or better turn off wifi/mobile data.
Then suppose you want to flash recovery so make copy of command 'fastboot flash recovery" this will save 2 seconds and keep your file in your root directory so it will also save time. After everything set hit flash As soon as possible.
My recovery size was 98 mb and It had only 2 seconds to push it to the device. It said " sending recovery ok- writing failed" so you better use good cable.
Means it was able to successfully sent the file but didn't got image writing status because your device got turned off. But don't worry.
sent the img file was all the things we needed. I tried it 2 times and it works.
If it is unclear please watch the video to how to use this app
Tips:
1. Never do any risky task with low battery .
Conclusion : I'm not responsible if anything goes wrong with your device. I shared it only thinking that this will save many people from hassels.
Thank you.

So you need a second device via OTG to fix the unstable bootloader?
My case is that the phone works perfectly, IMEI wifi calls etc, recovery works aswell but fastboot is broken.
Restarts after 2 or 3 seconds while holding the button, If release the phone will just boot normally.
This happened right after trying to lock the bootloader again coming from realmen UI 2.0 beta
Any thoughts?

mike_san said:
So you need a second device via OTG to fix the unstable bootloader?
My case is that the phone works perfectly, IMEI wifi calls etc, recovery works aswell but fastboot is broken.
Restarts after 2 or 3 seconds while holding the button, If release the phone will just boot normally.
This happened right after trying to lock the bootloader again coming from realmen UI 2.0 beta
Any thoughts?
Click to expand...
Click to collapse
Yes seccond device will ignore low battery or any other warning.
in 2-3 seconds your device get detected in fastboot?
did you checked that in device manager of windows?

Bishnu840 said:
Yes seccond device will ignore low battery or any other warning.
in 2-3 seconds your device get detected in fastboot?
did you checked that in device manager of windows?
Click to expand...
Click to collapse
I've to run; adb reboot recovery, then in stock recovery I can run 9008 qualcomm state and it is detected by windows.

I has the same problem, but only with recovery flashing. For other partitions flashing works correct.
I just deleted recovery:
Code:
fastboot erase recovery
Аnd the problem is gone.
Now i can flash it:
Code:
fastboot flash recovery recovery.img
Device: Oukitel k7 power.
Sorry for bad englich.