Related
Hi, i went out for a few drinks and got some party on.... it ended in my phone battery going dead..... now when i try to charge it, its just flashing read.. and it randomly boots into a white screen then shuts down after 10 seconds. something to do with my flashing recovery partition to get cwm and stuff which ofc didnt work look further down my post for more info about that, thats pretty much the only thing i have messed about with(rooted successfully tho... i dont understand why it wont charge just because of the bad flash, i tryed normal power outlet 230volt adapter to usb... the orginal that was bundled with my order... and tryed regular usb from my pc.
its just plain flat, and wont charge.. redlight flashing. some times it viberates boots into a white screen but wont charge..there should be a yellow light that should turn green at full capacity.
Now the question is if just could get myself into this fastboot or adb interface so i can flash my orginal recovery rom, i think the problem would solve, or if i maybe got to charge the battery manualy by physicaly removing it and charge it manualy without usb cable etc...
I have the firmware U9200-1V199R991C185B104.(norway)
In addition, I have rooted it.
used onkeys stuff, also realized i couldnt root it with my current windows 7 username (administrator) the script made it admini1 so errors appeared. I also used the Onekey_ROM_Ascendp1.exe it did some stuff copied some stuff, installed a recovery console that also didn’t work :S but nothing major changed, I think it has something to do with SD card mount names, but not sure about that
the thing is I can’t get the cwm_touch_recovery_viva_beta.img to work.
adb start-server
adb reboot-bootloader
2nd cmd prompt
fastboot erase recovery
fastboot flash recovery cwm_touch_recovery_viva_beta.img
fastboot reboot (unplugged usb as well)
Booted operating system
powered off, tried all the combinations of vol+up, vol+down and both vol-up/down + power, its basically stuck on the logo.
anyways so I went ahead to flash the stock recovery.img from page 7 8mb file.
now I have the standard recovery UI. with vol+up and power, that made me sure that the flash procedure is correct.
Right now I’m not sure if the cwm_touch_recovery_viva_beta.img is compatible with this b104... is anyone able to confirm this?
I have clockwork mod app installed on my phone though, it says my phone is not compatible yet.
+1 for our own ascend p1 forum tab!
Have a great day everyone n when its fully charged.
C:\Users\Administrator\AppData\Local\Android\andro id-sdk\platform-tools>fastboot devices
? fastboot
C:\Users\Administrator\AppData\Local\Android\andro id-sdk\platform-tools>fastboot erase recovery
erasing 'recovery'...
OKAY [ 1.878s]
finished. total time: 1.881s
C:\Users\Administrator\AppData\Local\Android\andro id-sdk\platform-tools>fastboot flash recovery cwm_touch_recovery_viva_beta.img
sending 'recovery' (3335 KB)...
OKAY [ 0.110s]
writing 'recovery'...
OKAY [ 0.452s]
finished. total time: 0.567s
C:\Users\Administrator\AppData\Local\Android\andro id-sdk\platform-tools>fastboot erase cache
erasing 'cache'...
OKAY [ 27.082s]
finished. total time: 27.084s
C:\Users\Administrator\AppData\Local\Android\andro id-sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.004s
When it was finished booting up i went for rom manager and reboot into recovery, then the app just froze and i could close or wait for it.
shut down device with usb cable in just froze up on huawei logo.
restarted did abd reboot recovery, after that no response in either fastboot or adb interface
Solved?
So did you solve the problem? and how?
its kinda same with my problem, cannot turn on, when plug the charge cable only vibrate, huawei logo and bootloop
but when I go to fastboot mode its only last around 40 seconds, its that normal
tried to flash the boot and recovery to stock still not working
anyone has solved the problem?
I have the same problem with a Huawei Ascend P1 U9200.
I have not flashed any new roms or recovery and it is not rooted.
The phone ran out of power, so was plugged into a wall charger, then when I checked on it later the "Huawei Ascend" screen displays for a few minutes then it powers off, vibrates, red led flashes and the Huawei Ascend screen displays again. It is stuck in a boot loop and unresponsive to the power and volume buttons.
adb devices displays nothing and
fastboot reboot displays < waiting for device >
I had a similar problem when flashing my Motorola Defy, and had to do the Macgyver Hack to directly charge the battery http://forum.xda-developers.com/showthread.php?t=1086953. But the U9200 has a sealed battery and it still has 11 months on the warranty so its not worth breaking the phone for.
As the battery is flat I cannot boot into recovery by pressing Vol Up + Vol down + Power as it has no power. So how can you boot into recovery with a flat battery?
Any advice would be greatly appreciated!
Hi all,
I have a major problem. My son played a game on my nexus 7 and the tabled freezes. After that moment is was impossible to start it up again, only till the google word came on screen. No further.
I tried the following things on my unrooted and locked Nexus 7. And maybe the worst, i never had that button in settings marked for unknown sources installation. Now its too late and i can not place that mark anymore since the tablet does not start.
Unlocking impossible, factory reset impossible, cache wipe impossible but i have screen. I can see fastboot an can get to adb
I went in fastboot and tried to unlock bootloader. No succes
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
FAILED (status read failed (Too many links))
finished. total time: 1092.130s
Have you booted into Android since unlocking and enabled usb debugging?
no
that is the problem.
If i rooted this thing the first second i got it a year ago i had no trouble flashing anything now.
What am i missing? How can i get it going again now?
Regards,
Herman
solved, sorry
I read some posts and i know now that its really unsolvable. I have to get my warranty at the store.
Regards,
Herman
Cheruska said:
Hi all,
I have a major problem. My son played a game on my nexus 7 and the tabled freezes. After that moment is was impossible to start it up again, only till the google word came on screen. No further.
I tried the following things on my unrooted and locked Nexus 7. And maybe the worst, i never had that button in settings marked for unknown sources installation. Now its too late and i can not place that mark anymore since the tablet does not start.
Unlocking impossible, factory reset impossible, cache wipe impossible but i have screen. I can see fastboot an can get to adb
I went in fastboot and tried to unlock bootloader. No succes
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
FAILED (status read failed (Too many links))
finished. total time: 1092.130s
Have you booted into Android since unlocking and enabled usb debugging?
no
that is the problem.
If i rooted this thing the first second i got it a year ago i had no trouble flashing anything now.
What am i missing? How can i get it going again now?
Regards,
Herman
Click to expand...
Click to collapse
Did you try a factory reset from Recovery? Hold Power and VOL DOWN until the bootloader starts. Press the volume keys to change the large green banner that says START to RECOVERY, press Power to make the selection. Once in Recovery you will see a dead Android icon. Hold the power button and tap the VOL UP button to get the Recovery options. One of them is for Factory Reset.
fury683 said:
Did you try a factory reset from Recovery? Hold Power and VOL DOWN until the bootloader starts. Press the volume keys to change the large green banner that says START to RECOVERY, press Power to make the selection. Once in Recovery you will see a dead Android icon. Hold the power button and tap the VOL UP button to get the Recovery options. One of them is for Factory Reset.
Click to expand...
Click to collapse
THX for thinking with me. Yes, i tried factory reset and cache clearing also. Only mount failures and dnothing is happening. I can control th etablet by typing a fastboot command line to reboot but nothing else works. So i try to get a reapair in teh store.
use wugs
I just used wugs and loaded 4.3then let it update to 4.4, got me out of trouble.
Hi all,
I've rooted 3 FTVs and I just recently got another one that's rootable. But I ran into a problem.
I followed the AFTVNEWS site like a good boy. I rooted then did a full unlock. Next I installed the newest recovery. I rebooted into recovery and tried to flash 51.1.4.0_514006420.
For some reason the flash failed with error 7. I verified the file pushed to the FTV was the one I downloaded with md5. Since flashing wasn't working I decided to reboot system in cwm. When the screen returned it was a black screen with white amazon logo.
I tried unplugging and still white amazon logo. I did a bit of looking around and found out about alt + print screen + i but still white amazon screen. I don't know what happened or how to fix it. Any help would be appreciated.
Thanks,
BlueKalel
Sent from my SM-N900V using XDA Free mobile app
I have the same problem, the aftv only show the Amazon white logo, I had done the alt+i+prtscr but nothing happen, I even connect to my Mac with a USB cable A to A and do the recovery mode process but I get the following error
sending ‘recovery’ (8360 KB)…
OKAY [ 0.266s]
writing ‘recovery’…
FAILED (remote: flashing not allowed for locked hw)
finished. total time: 0.276s
Please let me know what else I can do
Thanks
Hi. Long time lurker, but finally found myself in a pickle. So now I'm asking for help.
I have a first get Kindle Fire that I figured I'd experiment with after getting a new Kindle HD 8. It has OS 6.3.4 and has been stock until just now.
I already rooted it and was then going through the process outlined in this thread:
https://forum.xda-developers.com/showpost.php?p=54124313&postcount=3
so that I could add TWRP. But, after the step "Step 5: Forcing Fastboot Mode" and entering "adb reboot", the Kindle rebooted without the animated logo as the instructions said it would... except it stayed that way.
And, it's still that way. Any adb command I enter returns "error: device not found". I tried the Kindle Fire Unbrick utility, but it also couldn't find the device, even though it finished the attempt with the message that it's now unbricked - except, it's not. Even my Windows 10 PC throws up an error when I try to reconnect the USB that there's a device error.
It's not in a boot loop - it's flat stuck. I can turn it off by holding the power button for about 15 seconds. And I can turn it back on, and I've tried entering adb commands as soon as I do turn it on to see it if takes, but it doesn't. It just sits there displaying the "kindle fire" logo.
I was going to try to load regular android on it, but now that seems out of the question.
Is there anything else I could try? I will try letting it drain the battery, and then plugging it in again, but any other suggestions would be appreciated. Anything else I need to provide, please let me know.
Thanks,
-Joel
joeldf said:
Hi. Long time lurker, but finally found myself in a pickle. So now I'm asking for help.
I have a first get Kindle Fire that I figured I'd experiment with after getting a new Kindle HD 8. It has OS 6.3.4 and has been stock until just now.
I already rooted it and was then going through the process outlined in this thread:
https://forum.xda-developers.com/showpost.php?p=54124313&postcount=3
so that I could add TWRP. But, after the step "Step 5: Forcing Fastboot Mode" and entering "adb reboot", the Kindle rebooted without the animated logo as the instructions said it would... except it stayed that way.
And, it's still that way. Any adb command I enter returns "error: device not found". I tried the Kindle Fire Unbrick utility, but it also couldn't find the device, even though it finished the attempt with the message that it's now unbricked - except, it's not. Even my Windows 10 PC throws up an error when I try to reconnect the USB that there's a device error.
It's not in a boot loop - it's flat stuck. I can turn it off by holding the power button for about 15 seconds. And I can turn it back on, and I've tried entering adb commands as soon as I do turn it on to see it if takes, but it doesn't. It just sits there displaying the "kindle fire" logo.
I was going to try to load regular android on it, but now that seems out of the question.
Is there anything else I could try? I will try letting it drain the battery, and then plugging it in again, but any other suggestions would be appreciated. Anything else I need to provide, please let me know.
Thanks,
-Joel
Click to expand...
Click to collapse
When it's in fastboot mode, use fastboot commands, not adb
Sent from my sailfish using XDA Labs
Thanks,
The instructions were not clear on what to expect at that point, and I assumed it was stuck. It didn't occur to me to just keep going.
So I did, and it responded as it was supposed to. When I got to "fastboot -i 0x1949 oem idme bootmode 4000", it returned
FAILED (status read failed (Too many links))
finished. total time: 0.031s
But the "reboot" command took and got the white and blue. It flashed a bunch of times but finally got it to boot with the normal white and yellow logo. I think part of it was that the battery had gone down since I last posted. I'm now recharging it before going further.
Still, thanks. I guess it wasn't stuck or bricked after all.
joeldf said:
Thanks,
The instructions were not clear on what to expect at that point, and I assumed it was stuck. It didn't occur to me to just keep going.
So I did, and it responded as it was supposed to. When I got to "fastboot -i 0x1949 oem idme bootmode 4000", it returned
FAILED (status read failed (Too many links))
finished. total time: 0.031s
But the "reboot" command took and got the white and blue. It flashed a bunch of times but finally got it to boot with the normal white and yellow logo. I think part of it was that the battery had gone down since I last posted. I'm now recharging it before going further.
Still, thanks. I guess it wasn't stuck or bricked after all.
Click to expand...
Click to collapse
Did you watch my video?
Sent from my sailfish using XDA Labs
sd_shadow said:
Did you watch my video?
Sent from my sailfish using XDA Labs
Click to expand...
Click to collapse
I watched several videos, and I think I started yours at one point, but between my 8 year old running around saying it's almost midnight (it was new years eve), and then trying to get him to go to bed, by the time I came back to this, I may have lost track of what I was watching.
Moral of the story, do this kind of thing without interruptions...
I did re-watch your video all the way through and I see that what happened was normal.
Still, there was that error trying to reset the bootmode (I didn't get what you got), otherwise, it still works and re-boots fine now. Even went into Recovery.
Next thing is trying out a new rom.
Thanks again.
MY DEVICE IS ALSO STUCK!!! After doing the fastboot reboot it gets stuck with the lifeless bootscreen and doesn't do anything from there, I've also tried to use the set boot mode but it hangs on waiting for device
Hello @All,
I bought myself a new toy: a bricked Nexus 5x. The only thing I can do is enter the bootloader mode. Otherwise the phone is showing the Google logo.
In bootloader mode the last two lines are "Secure Boot - Enabled" and "Device State - Locked". The "fastboot devices" states that the device is present.
I can neither access any recovery nor install one (because bootloader locked). The device isn't rooted. Parallel to posting this I am searching the depths of the web. Of course without a solution.
Can I do anything else?
hmm, did you try going into the recovery and resseting it, if that didnt work go on your computer, go to bootloader mode, and on your computer try typing: fastboot flashing unlock or fastboot oem unlock, if none of those work, then try reflashing the firmware trough recovery or fastboot, here is the rom for adb sideload trough recovery...
here is a direct download cuz it wouldnt post the zip https://dl.google.com/dl/android/aosp//bullhead-ota-mhc19q-8fe67a2b.zip
I can't access the recovery, but I'll try fastboot again. "fastboot flashing unlock" and "fastboot oem unlock" don't work. I get a " FAILED (remote: 'oem unlock is not allowed')" message.
ok, try this, go in fastboot, and run this command, fastboot flash boot N2G47Z_4Cores.img with the img that i send you, if it works, then see if iit boots up!
it doesnt wanna send it, heres a link to download it https://www.dropbox.com/s/tm7qt98r6d7q2a6/N2G47Z_4Cores.img?dl=0
I tried
Code:
$ fastboot flash boot N2G47Z_4Cores.img
and the answer was
Code:
Sending 'boot' (12045 KB) OKAY [ 0.464s]
Writing 'boot' FAILED (remote: 'device is locked. Cannot flash images')
fastboot: error: Command failed
...
But thanks for your effort to help me
Heinz- said:
I tried
Code:
$ fastboot flash boot N2G47Z_4Cores.img
and the answer was
Code:
Sending 'boot' (12045 KB) OKAY [ 0.464s]
Writing 'boot' FAILED (remote: 'device is locked. Cannot flash images')
fastboot: error: Command failed
...
But thanks for your effort to help me
Click to expand...
Click to collapse
hey is there a way you can send me a video of what happens when it boots up and when you try to enter recovery, maybe i can still help.
if you cant here send it to my mail [email protected] , this is my mail since 2016 and zombie was mostly for minecraft . but then i was young, so yeah.
I can only describe it for you...
When I try to boot into recovery it happens the same as booting the system. The Google sign appears with a short buzz of the vibration motor, then disappears after 16 seconds, and a second later the same again. A classical boot loop. I can only access the bootloader mode. When I try to boot from there, the same happens. The "system state" is locked, and Secure Boot is enabled.
I can power off the device from the bootloader, then it stays off.
Is there any hope to bring it to life again, or is it a brick forever?
Heinz- said:
I can only describe it for you...
When I try to boot into recovery it happens the same as booting the system. The Google sign appears with a short buzz of the vibration motor, then disappears after 16 seconds, and a second later the same again. A classical boot loop. I can only access the bootloader mode. When I try to boot from there, the same happens. The "system state" is locked, and Secure Boot is enabled.
I can power off the device from the bootloader, then it stays off.
Is there any hope to bring it to life again, or is it a brick forever?
Click to expand...
Click to collapse
well it looks like a problem with either the ram, vibrator, or the partitions, sadly this happened with old nexus devices, so its a brick forever sadly. but if you want you can sell it online for parts.
Ok then, I hope I can sell the brick. Thank you again for your help, @NikolaTechGuy !
But there's one last hope: This thread, shown to me directly under this answer ("Similar threads") that I'm currently writing. One last try...
Heinz- said:
Ok then, I hope I can sell the brick. Thank you again for your help, @NikolaTechGuy !
But there's one last hope: This thread, shown to me directly under this answer ("Similar threads") that I'm currently writing. One last try...
Click to expand...
Click to collapse
Sorry if this is too late but are you sure you can't do anything with the phone?
To enter Bootloader Mode press and hold Vol Down + Power. You will automatically enter Fastboot Mode. You will see the settings of 'Secure boot' and 'Device State'
Use Vol up and Vol Down to scroll through menu and the Power button to select an option:
Start
Restart bootloader
Recovery Mode
Power Off
If you select Recovery Mode, wait until you see the 'Robot lying down' image and "No command" text appear on screen. Now hold Power button and briefly press the Vol up button. The 'Android Recovery' screen should now appear.
To enter LG 'Download Mode':
Power Off your phone.
Now press the Vol. Up button and hold it
Now Plug your phone into your computer using a USB cable
After a few seconds 'download mode' should appear on your phone screen, followed by a 'Firmware Update' screen.
If it doesn't enter LG Downoad Mode then check in your Windows Device Manager under COM/PORTS. See if you have connected in Qualcomm 9008 EDL (Emergency Download ) Mode. The connection will appear as Qualcomm HS-USB QDLoader 9008. You might have to download the Qualcomm driver for this to work.
If you can get into Recovery Mode or EDL mode you still have options! It depends how much time and effort you want to spend on a 7 year old phone with no sd card option.
You can become 'obsessed' like me, and buy a hot air gun solder rework station to try and reflow the solder under the MSM8992 chip to fix the 'bootloop of death'! NOTE: I have tried it on 3 bricked Nexus 5X and only got a temporary success on one phone - the other two I did a very good job of frying the chip! Mind you I now have alot of spare parts!
I took the Nexus to a repairman who calls himself "Handy-Doc". He told me it was the hardware. He couldn't install anything as well as me. But replacing the motherboard could help. So I ordered a motherboard on AliExpress. This is my last try!
Heinz- said:
I took the Nexus to a repairman who calls himself "Handy-Doc". He told me it was the hardware. He couldn't install anything as well as me. But replacing the motherboard could help. So I ordered a motherboard on AliExpress. This is my last try!
Click to expand...
Click to collapse
You will have to keep us updated. I looked at those motherboards but wasn't sure about them. What version of Android is installed? Do they come with a new IMEI or are they blank? etc. Taking a 5X apart is very straightforward with a couple of simple phone tools. There are plenty of Youtube videos that show you how to do it - it might save you having to pay "handy-Doc"!
No, it doesn't work. I can plugin the phone when it's in "Download Mode" but nothing more happens. After a few seconds the phone tries to boot again. The "Handy Doc" man gave me back the phone without asking for payment.
The motherboard is on its way from China to Germany. This can take several weeks.
Hi
I am sorry if I am posting this at the wrong place.
I bricked my Nexus 5x device flashing DivestOS on it.
I flashed two different LineagOS on this device successfully in the past and the genuine Android when I was rolling it back. It always worked, but not this time.
Trying to roll it back to genuine Android, there were errors that several ".img" was missing in the archive.
I tried to chat with Android developers on Matrix chat and also reported this problem here, on DivestOS forum, but they blame hardware and/or user mistake.
I took it farther to sort the device problem and made it unresponsive, the screen is black and it does not react to anything at all now.
All I needed to know if there is ANY way to bring this device back to life.
I found some "LGFlashTool_2.0.1.6" on one of the old forumes of (2016), but I did not try it, I believe it will not work, and wanted to know from Android developer's oppinion before I try anything else.
Thank you
---Update:
I opened it, unplugged and re-plugged the battery.
Was able to boot it into the fastboot menu.
1. secure boot - enabled
2. device state - unlocked
-Tried to flash the genuine Android (I did it several times and I know it works)
No success!
Please see the terminal screenshot attached for errors.
If you can get into fastboot have you tried flashing TWRP and getting into it again? Then try flashing a lineageOS that you know works.
bjlabuk said:
If you can get into fastboot have you tried flashing TWRP and getting into it again? Then try flashing a lineageOS that you know works.
Click to expand...
Click to collapse
Thanks for reply =).
This is a goot point.
I'll try and post the result here.
Now, not always I can boot it into fastboot menu, sometimes it's totally un-resposive, does not show any sights of life, it can be the battery charge problem (battery was not bad though).
balakarpo said:
Thanks for reply =).
This is a goot point.
I'll try and post the result here.
Now, not always I can boot it into fastboot menu, sometimes it's totally un-resposive, does not show any sights of life, it can be the battery charge problem (battery was not bad though).
Click to expand...
Click to collapse
Yea, looking at the log everything appears to be okay until that last line. Did you use flash-all.bat from the factory image bullhead-opm7.181205.001-factory-5f189d84.zip?