Can anyone answer this?
I am attempting to unlock bootloader so I can flash CWM:
Reboot Bootloader ADB commands force this Nobis Tablet device to stay stuck in the boot logo screen and ADB just says waiting for device.
The tablet starts to reboot and then just stays stuck in boot logo for as long as I leave it there, (minutes, hours, days.)
Thank you!
DeathOfAStar said:
Can anyone answer this?
I am attempting to unlock bootloader so I can flash CWM:
Reboot Bootloader ADB commands force this Nobis Tablet device to stay stuck in the boot logo screen and ADB just says waiting for device.
The tablet starts to reboot and then just stays stuck in boot logo for as long as I leave it there, (minutes, hours, days.)
Thank you!
Click to expand...
Click to collapse
Try use fastboot command. Does it work?
Every device have different unlock bootloader.And it easy make your phone brick.I think your softbrick.You need find in forum.
Related
Hi I was routing my phone and trying to downgrade the OS. It was already unlocked.
I typed the following command
sudo ./fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
it completed successfully. Post which I restarted and wanted to boot into recovery mode. However it got stick in the Google logo and pulled out the battery and tried to restart it. But it will not start.
I tried again and again and there is nothing happening.
What do I do? Please help me.
krish.ubuntu said:
Hi I was routing my phone and trying to downgrade the OS. It was already unlocked.
I typed the following command
sudo ./fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
it completed successfully. Post which I restarted and wanted to boot into recovery mode. However it got stick in the Google logo and pulled out the battery and tried to restart it. But it will not start.
I tried again and again and there is nothing happening.
What do I do? Please help me.
Click to expand...
Click to collapse
Will it go into boatloader mode?
Vs Nexus S4G using tapatalk2
The other day my WiFi Xoom stopped getting past the "Motorola Dual Core" screen.
I have removed the SD card.
Android recovery mode gives me the error android with the "!"
It does this plugged in or on battery.
Not rooted.
What else should I try?
neoka said:
The other day my WiFi Xoom stopped getting past the "Motorola Dual Core" screen.
I have removed the SD card.
Android recovery mode gives me the error android with the "!"
It does this plugged in or on battery.
Not rooted.
What else should I try?
Click to expand...
Click to collapse
What were you trying to do before this hapened? Need more info to be able to help.
24348542 26
DavilaDarkness said:
What were you trying to do before this hapened? Need more info to be able to help.
Click to expand...
Click to collapse
Hadn't really done anything. Just normal use. No out of the ordinary installs. Turned it off. Next day I tried turning it on and it won't boot.
Did you ever resolve this ?? I was give one to repair for a child and it too is stuck on the red boot screen. The good thing is the person who sold it to them was a hacker and put TWRP on it of all things. I was floored when I tried to enter recovery and found teamwin.
but the problem is its still stuck on the boot screen, i did flash it 3-4 times with M604 M602 flashes and some other customs but nothing works, it completes flashing and wiping caches but always goes back to stuck on boot screen..
perhaps I have to unclock the bootloader or something for the flash to be succesfull ?
Just wanted to say I fixed it with these commands and firmware if anyone is interested. I tried everything else including flashing with twrp and wiping all caches and it didn't work, getting the stock firmware and doing it like this worked to clear boot screen endless stuck
download fastboot and adb and xoom drivers 6.4 (about 5mb) and the appropriate stock firmware. for me it was ZM604
at the command type
adb reboot bootloader
you may need to unplug and replug cable after it goes in fastboot mode.
fastboot devices
.. should return something "02a439cj0skjdke fastboot" to proceed.
fastboot oem unlock
.. look at your tablet and follow the instructions, for me it was down twice and up once to accept unlock conditions, then it reboots
on reboot press vol down 2 seconds after you see moto logo, it will enter fastboot
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot erase userdata
fastboot reboot
no need to relock after, you will see android logo and first boot pop up after 2-3 mins
Hi guys,
My Nexus 5 (hammerhead D821 (E) ) died on me two day ago. It's showing the google logo without any progress and then restarts itself.
I can boot into bootloader from the device. If I issue <adb devices> command it won't show any devices however when using <fastboot devices> it finds the device's ID.
My devices was running the latest official marshmallow 6 when it happened (it was working just fine for more than a week).
Currently my device is in <lock state - Locked> I tried issuing <fastboot oem unlock> command without any success. The phone would run the command shows the <lock state - Unlocked> then it shows <erasing...> (I left the phone for 10Hours, no change) .
It won't finish nor respond unless I reboot the device into bootloader again.
I'm using the google USB drivers and universal drivers for my phone, they seem to be working, showing as android bootloader interface in my system (win7). I can't boot into recovery mod from the bootloader it will just show a black screen until I restart the phone.
I'm suspecting my eMMC is dead, my knowledge with adb and fastboot is limited, I would appreciate to hear your feedback regarding the issue.
Is there are way I can run some low level diagnostics commands to understand if its dead?
Can I revive my phone in anyway as I can't flash anything at the moment while the device is in <lock state - Locked> .
Waiting to hear from the experts =) thanks in advance guys!
Alex
Fish7 said:
Hi guys,
My Nexus 5 (hammerhead D821 (E) ) died on me two day ago. It's showing the google logo without any progress and then restarts itself.
I can boot into bootloader from the device. If I issue <adb devices> command it won't show any devices however when using <fastboot devices> it finds the device's ID.
My devices was running the latest official marshmallow 6 when it happened (it was working just fine for more than a week).
Currently my device is in <lock state - Locked> I tried issuing <fastboot oem unlock> command without any success. The phone would run the command shows the <lock state - Unlocked> then it shows <erasing...> (I left the phone for 10Hours, no change) .
It won't finish nor respond unless I reboot the device into bootloader again.
I'm using the google USB drivers and universal drivers for my phone, they seem to be working, showing as android bootloader interface in my system (win7). I can't boot into recovery mod from the bootloader it will just show a black screen until I restart the phone.
I'm suspecting my eMMC is dead, my knowledge with adb and fastboot is limited, I would appreciate to hear your feedback regarding the issue.
Is there are way I can run some low level diagnostics commands to understand if its dead?
Can I revive my phone in anyway as I can't flash anything at the moment while the device is in <lock state - Locked> .
Waiting to hear from the experts =) thanks in advance guys!
Alex
Click to expand...
Click to collapse
Sounds like it (eMMC) died.
beekay201 said:
Sounds like it (eMMC) died.
Click to expand...
Click to collapse
Thanks for the feedback beekay201. I hope someone will know if this can be confirmed with some sort of test etc...
I think my emmc is dead too because my n5 does the same thing in fastboot - unlocked, locked, unlocked. Also, I can't mount partitions or perform a factory wipe in stock recovery. Also tried flashing TWRP right after unlocking the bootloader. Fastboot says recovery was successfully flash but, when I immediately boot to recovery, I still have stock recovery.
Time for me to find a n5 with a smashed screen
audit13 said:
I think my emmc is dead too because my n5 does the same thing in fastboot - unlocked, locked, unlocked. Also, I can't mount partitions or perform a factory wipe in stock recovery. Also tried flashing TWRP right after unlocking the bootloader. Fastboot says recovery was successfully flash but, when I immediately boot to recovery, I still have stock recovery.
Time for me to find a n5 with a smashed screen
Click to expand...
Click to collapse
Hi audit13,
My Nexus is locked. I can't unlock it at all. It's stuck in "erasing" if I run <fastboot oem unlock> command.
Hey guys.
Some issues right now....
I can't get the phone to boot. It gets stuck on boot logo. I can get it into fastboot, but not recovery.
If I try to enter recovery, it shows boot logo, then change brightness level a little bit for some reason, then nothing. Back to boot logo after screen goes black.
So it appears that the TWRP isn't installed correctly, but I've reinstalled it several times, but it never actually seems to work.
I can see the device in fastboot. Bootloader is also unlocked.
So, does anyone have a solution for this issue?
I can get it into fastboot
Click to expand...
Click to collapse
This is good news as it means you should be able to just flash the recovery from fastboot.
1. Download the latest TWRP Recovery: http://twrp.me/devices/bacon (I believe this is the link, it's blocked at school )
2. type the command
fastboot flash recovery /location/of/twrp/img
Click to expand...
Click to collapse
3. Wait for it to complete and then reboot the device by holding down power and volume down.
4. Then if it boots into TWRP you should be able to mount it on the computer you plug it into and then carry over a ROM and/or GApps files.
I'm in the exact same boat, happened after I tried an OTA update. I can't flash anything into the phone via ADB because my phone isn't recognised. isn't recognised in ADB. This is while I am in Fastboot. I'm on OSX.
Rorys-MBP:~ Rory$ adb devices
List of devices attached
Click to expand...
Click to collapse
Hi guys,
I'm facing the following issue:
I took my pixel 4a, unlocked the bootloader, later worked on the boot.img to with magisk to root the device... prepared the modified img file and launched the command fastboot and it went successfully. Later sent the fastboot reboot comand, and the device booted up, it is stuck with the google logo and from there, trying to get back into fastboot mode but whenever I do the procedure (presso volume down + power up) , I first get a screen telling that the device is corrupted and it might be not safe... later starting to bootup but straight away stuck at google logo ... the device is not seen from adb commands or fastboot commands... how can i recover the device according to you guys ?
thanks,
giuseppe
letsrock666 said:
Hi guys,
I'm facing the following issue:
I took my pixel 4a, unlocked the bootloader, later worked on the boot.img to with magisk to root the device... prepared the modified img file and launched the command fastboot and it went successfully. Later sent the fastboot reboot comand, and the device booted up, it is stuck with the google logo and from there, trying to get back into fastboot mode but whenever I do the procedure (presso volume down + power up) , I first get a screen telling that the device is corrupted and it might be not safe... later starting to bootup but straight away stuck at google logo ... the device is not seen from adb commands or fastboot commands... how can i recover the device according to you guys ?
thanks,
giuseppe
Click to expand...
Click to collapse
If you are getting the unlocked bootloader message of "being corrupted", that is normal. You'll see it every time you reboot now that your bootloader is unlocked. Sounds like you are having trouble getting back into fastboot. I find it easier if I unhook my phone from the pc while holding the power and volume down (not up) buttons. You should be able to fastboot flash your stock boot.img to get your phone back. Make sure you have the correct boot.img for your firmware.