Develop Bugs

[Q] can't acess bootloader but directly acess to cwm recovery

hi , first of all , sorry for my bad english
im have bought htc one v last week
so last night i tried to root and install custom rom
after i unlock the bootloader and rooting the device from this thread http://forum.xda-developers.com/showthread.php?t=1598964
then im choosing the custom room made by shubhamchamaria (thanks ) at http://forum.xda-developers.com/showthread.php?t=1640995
before i flash the room , my device still can access the boot loader
after flash the boot.img
then im entering the cwm recovery . then im installing the custom rom ,
so i did the reboot process
after the reboot process , it stuck at htc one logo (bricked?)
so i turn off the phone , turn off while pressing the volume down , it didnt enter the bootloader , but directly enter the cwm v5 recovery
so it bricked ? or another issue?
im downloading the stock rom right now
fyi ,
in the cwm recovery , ive format the data , cache partition and dalvik cache
thanks for the help

After you flashed the boot.img, did you do the "fastboot erase cache" ?
Not sure whether the boot.img that you have is secured or insecured, you can try this:
in CWM recovery, connect the usb cable to PC.
then go to your adb folder, in command prompt:
adb devices
if your device is listed, then the adb works
adb reboot bootloader
if it works
go to fastboot folder, in command prompt
fastboot erase cache
fastboot reboot-bootloader

[Q] [HELP] Bricked Galaxy Nexus (maguro)

Hello guys, a friend of mine has a galaxy nexus with some problems.
When I turn on the phone, it starts booting normally, but a few seconds after getting into "desktop" it starts popping up errors saying that the process as stopped.
I've already tried a few things, but without success. I'm running out of ideas and here I'm asking for your help.
Things I've tried:
-Boot into recovery mode and wipe all data.
The phone says that the operation completed successfully, but after rebooting the phone remains the same. All apps, wallpaper, lock screen, etc. It seems that nothing was changed by this process.
-Flash a original google ROM
Following the tutorials, the first step is to unlock the bootloader with fastboot oem unlock. The phone shows a confirmation asking if I want to unlock it, I say yes, and it shows "status: unlocked". But after rebooting the phone it is locked again!!!
I tried to flash the room without rebooting the phone after unlocking it,
Code:
fastboot flash bootloader bootloader-maguro-primela03.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-maguro-i9250xxla02.img
fastboot reboot-bootloader
sleep 5
fastboot -w update image-takju-imm76i.zip
The first command to flash the bootloader also says that completes successfully, but when I'm flashing the radio it will complain saying that the phone has the wrong bootloader version installed.
-Flashing via Odin
It fails when is flashing system.img to the phone
-Flash custom recovery - fastboot flash recovery recovery.img
The process completes "successfully" but when I boot into recovery mode, there is the original one and not the one I just flashed.
-emmc brickbug - partition scanner
I found this thread http://forum.xda-developers.com/showthread.php?t=1823918 and tried to run the partition scanner. As I can't have the phone on enough time to use adb shell, I tried to use this scanner via adb sideload but the phones returns an error when running it. (probably because it doesn't have busybox installed, not sure)
After trying all of steps above, the phone is still the same... nothing changed. Once, I managed to connect it to the pc as an usb storage device, and was able to copy some photos from the phone and deleted them. But after rebooting they were all there again. It seems that all write changes are not persistent.
I'm out of ideas now... Do you have any idea of what is the problem? Or any suggestion for me to try?
Thanks in advance

I believe that there is a script in the android SDK tools called flashall.bat which will reflash the kernel, bootloader, recovery, ROM ect. I'm not sure how to use it, but you could potentially try that

Hi, thanks for you suggestion, but unfortunately it didn't work.
I had a look at the flashall.bat script and it runs the same commands I run manually.
I think that the phone might have some hardware problem... Normally I would buy a new phone, but I'm trying to fix it because it is important for my friend and for me because it is challenging.
I guess that the next thing I will try, will be trying to run emmc_find_brick script by @hg42 via sideload

Try formatting /system and reinstall android. Power your device into bootloader mode. Make sure your device is unlocked. Also, make sure you have the factory image downloaded. After your device is plugged in into your computer, use this fastboot command: fastboot erase system. This will delete everything from /system. Also format /data and /cache: fastboot erase data and fastboot erase cache. After that, try installing the factory image again.

Android bot error blinking on boot after wipe partition cache process

Model: Asus Zenfone 2 ZE551ML
After updating to latest version i decided to wipe partition cache while on the process it showed erasing android bot then restarted and hung on asus logo for nearly an hour so i decided there is some problem and force switched off then after switching on it shows the blinking android error bot.........im unable to enter neither recovery mode nor fastboot mode(when entering it shows for a some seconds waiting fastboot cmd bt then comes again to the normal boot screen)....
Its been nearly a week i went thru various post and tried most of the methods like entering recovery mode thru adb(as im unable to enter fastboot mode it shows in cmd waiting for device) and pressing both buttons same for stock recovery(it shows some lines saying in last line can't mount recovery)
SO CAN SOMEBODY THROW LIGHT ON WHAT EXACTLY NEEDS TO BE DONE TO RECOVER MY PHONE FROM THIS ERROR.... would be grateful and thanks in advance.

Feel like you for the same worries as I did.
Try to flash bootdroid.img / boot.img / recovery.img with fastboot commands and that should do the trick.
For recovery I renamed twrp.img to recovery.img to get twrp right away

cuberio1 said:
Feel like you for the same worries as I did.
Try to flash bootdroid.img / boot.img / recovery.img with fastboot commands and that should do the trick.
For recovery I renamed twrp.img to recovery.img to get twrp right away
Click to expand...
Click to collapse
now i got some idea bt can u tell a bit elaborate what exactly i need to do..... (downloads and cmd commands)

Rockybala90 said:
Model: Asus Zenfone 2 ZE551ML
After updating to latest version i decided to wipe partition cache while on the process it showed erasing android bot then restarted and hung on asus logo for nearly an hour so i decided there is some problem and force switched off then after switching on it shows the blinking android error bot.........im unable to enter neither recovery mode nor fastboot mode(when entering it shows for a some seconds waiting fastboot cmd bt then comes again to the normal boot screen)....
Its been nearly a week i went thru various post and tried most of the methods like entering recovery mode thru adb(as im unable to enter fastboot mode it shows in cmd waiting for device) and pressing both buttons same for stock recovery(it shows some lines saying in last line can't mount recovery)
SO CAN SOMEBODY THROW LIGHT ON WHAT EXACTLY NEEDS TO BE DONE TO RECOVER MY PHONE FROM THIS ERROR.... would be grateful and thanks in advance.
Click to expand...
Click to collapse
maybe you have flashed wrong droidboot img for fastboot partition.. if you manage to enter fastboot mode, you may try to type
fastboot erase cache
but only if you able to enter fastboot..usually wiping cache from stock recovery may stuck but it can be cleared with that command.. but if you are unable to enter fastboot mode sorry then, hope that someone expert can help you..

NEED HELP !!! OPPO FIND 7 stuck on boot with logo only

Tried fixing my oppo find 7
Did all those Fastboot wipe .
Fastboot flash recovery and flash LOGO and stuffs
but im still stuck on logo ... WHUT

kevzwenhao said:
Tried fixing my oppo find 7
Did all those Fastboot wipe .
Fastboot flash recovery and flash LOGO and stuffs
but im still stuck on logo ... WHUT
Click to expand...
Click to collapse
Did you unlock bootloader?
1. Connect the device to the computer through USB.
2. From a terminal on a computer, type the following to boot the device into fastboot mode (or restart pressing power+vol up):
Code:
adb reboot bootloader
3. Once the device is in fastboot mode, verify your PC sees the device by typing:
Code:
fastboot devices
4. From the same terminal, type the following command to unlock the bootloader:
Code:
fastboot oem unlock
If the device doesn't automatically reboot, reboot it from the menu. It should now be unlocked.
5. Then you can flash the recovery what you want. In fastboot mode, type in terminal:
Code:
fastboot devices
6. And flash the recovery. Type:
Code:
fastboot flash recovery your_recovery_image.img
Good luck

roi_xordo said:
Did you unlock bootloader?
1. Connect the device to the computer through USB.
2. From a terminal on a computer, type the following to boot the device into fastboot mode (or restart pressing power+vol up):
Code:
adb reboot bootloader
3. Once the device is in fastboot mode, verify your PC sees the device by typing:
Code:
fastboot devices
4. From the same terminal, type the following command to unlock the bootloader:
Code:
fastboot oem unlock
If the device doesn't automatically reboot, reboot it from the menu. It should now be unlocked.
5. Then you can flash the recovery what you want. In fastboot mode, type in terminal:
Code:
fastboot devices
6. And flash the recovery. Type:
Code:
fastboot flash recovery your_recovery_image.img
Good luck
Click to expand...
Click to collapse
Hi, is it wrong to wipe the system partition before flashing a custom rom? Coming from stock ColorOS, I've wiped all dalvik cache, cache, system, and data, then flash a custom rom but it ended up getting endless bootanimation unable to boot into the custom rom.
I did unlock the bootloader with the adb code, flashing a temporary recovery was a success but endless bootanimation happened after flashing a custom rom. The custom rom was successfully installed according to TWRP's log.
Pls advice, thanks in advanced
P.s: I was referring to my friend's device X9076

Hi, i tried in the past some roms than not works, phone stuck in boot animation. The roms wich works for me and my x9076 with r63419 are:
Omnirom (6 or 5) THE BEST
Project Spectrum
Cyanogen 13 (modified version for new panel: http://community.oppo.com/en/forum.php?mod=viewthread&tid=44907&extra=)
Miui
If you install CM13, you need to flash unified partition script for CM13 (you can find it in the same post from the forum Oppo Community)
For the other roms i dont need to flash anything else than rom and gapps.
Now i give a chance to CM13, but i think that i will get back to Omni if developers dont fix the mobile radio issue.
Cheers

Can anyone guide me please, 1st time i bought MTK phone Oppo F7, its update automatically but suddenly dead like stuck on logo and restarting again and again, i didnt ever flash MTK phone, neither i have any android tool like MRT dongle or any other flash USB or Box... Kindly guide me step by step how to flash with which tool only USB cable and PC... Thanks in advance

In need of some backup

Problem:
Unlocked phone is seemingly stuck in bootloop. Need guidance fixing it.
Explanation:
Hey guys,
I bought a used Nokia 6 (2018) and want to install a custom ROM on it. Last year, I used the paid service to have it unlocked - worked like a charm! So thanks again for that! After reading up on the topic, I set up drivers, adb and fastboot on my PC (Win10). I used
fastboot erase cache
fastboot erase userdata
fastboot erase boot
fastboot erase system​to prepare the phone and then
fastboot boot twrp-3.3.1-1-PL2.img​to get into TWRP. Next is where I ****ed up I think.
I followed a guide and moved twrp-installer-3.3.1-0-PL2.zip on to my SD card. In TWRP, I chose "install" and then picked said installer. After that, I chose the option to reboot.
That must have been the wrong thing to do, because now the phone only boots into download mode. When I hold the power button it does not shut down, but instead instantly reboots into download mode.
When I type
fastboot devices​I still get
PL2GAR9811701240 fastboot​and Windows plays the "connect" sound, when I plug it in. Yet all fastboot commands (boot, flash, reboot) now return
FAILED (Write to device failed (Unknown error))​What can I do at this point? Can I somehow revert to stock? How is that done? Can I use this guide and the linked stock ROM?
If you'd like more information, just ask away. I'm glad for any guidance at this point, so thanks in advance for your help!