[Q] Problem with booting - Desire Q&A, Help & Troubleshooting

Hi, here is the situation. I got one half-broken Desire.
Fully formatted, s-off,cwm 5.0.2.0 with broken volume up and down keys.
So, when I get into the bootloader I can't get into the recovery to flash zip.
Anyone has some rooted image with boot.img, system.img data.img so I can flash it via fastboot?
Thanks.

You can flash .zip ROM through fastboot : http://forum.xda-developers.com/wik...id#Android_Flashing_Guide_.28with_fastboot.29
I think you can also flash rom from Rom Manager

byglet said:
You can flash .zip ROM through fastboot : http://forum.xda-developers.com/wik...id#Android_Flashing_Guide_.28with_fastboot.29
I think you can also flash rom from Rom Manager
Click to expand...
Click to collapse
Thanks didn't know that... But pretty much useless since community roms don't contain android-info.txt file and some other related stuff.
However, I've figured out that after flashing boot.img via fastboot, it shows itself up in adb devices command so I managed to get into recovery by adb reboot recovery and flashed.

Related

[DEV] recovery

attached is a semi-working recovery, you can flash it with "fastboot flash recovery recovery.img".
update: the recovery can flash boot.img's too, if the custom rom uses "dd" instead of "write_raw_image" to flash the boot.img. i hope mike updates his rom
don't use anything except for "install from sdcard"
i take no responibility for any harm to your device or data
it's basicaly a repacked cwm recovery combined with the stock 1.26 recovery kernel/ramdisk with modifications to init.rc
it is intented for developers wanting to toy around with custom roms, until someone makes a real recovery
no support nor updates will be made for this
is it tested or not yet.
I've tested it
ok thanks, since currently there is no other option to unlock bootloader other than htcdev & lack of RUU sources is too risky to flash custom recovery at this point. so technically it will skip zip package signature check? so we can start working on working custom rom.
You can always flash the stock recovery again ith fastboot
The reason why this recovery is useful is because i dont have to repack system qnd userdata images with ext4. Plus, you can update the userdata partition. Flashing with fastboot erases it
looks nice!
could you maybe share your knowledge about creating this recovery? i'm trying the same for the one s but can't get it packed together correctly...
blubbers said:
You can always flash the stock recovery again ith fastboot
The reason why this recovery is useful is because i dont have to repack system qnd userdata images with ext4. Plus, you can update the userdata partition. Flashing with fastboot erases it
Click to expand...
Click to collapse
Understand. My concern is no RUU for my device available yet & im afraid to use from other region stock rom Thanks for ur effort.
Do I have to unlock my phone to install this recovery?
moom999 said:
Do I have to unlock my phone to install this recovery?
Click to expand...
Click to collapse
yes, there are only 2 ways of installing a recovery.
fastboot and adb
fastboot requires you to unlock in order to "fastboot flash recovery"
and in order to possibly do it through adb you need root and in order to get root at the minute you need to be able to flash an insecure boot image through fastboot, which again, you need to unlock in order to "fastboot flash boot"
Hi blubbers,
There is a guy on general thread who wants to dump a developer phone. It's s4 not tegra but might help.
http://forum.xda-developers.com/showthread.php?p=24496390
sent from my HTC one X using tapatalk

[Q] Booting strait to custom recovery *Help*

Hey guys, I think i screwed up big time. I have just received my Htc one M8 from rogers (with no bloatware on it .. weird lol ) And i wanted to root it in order to use titanium back up.
So i followed a guide to root the phone everything went well execpt that now my phone boots straight into philz custom recovery....
When i was entering the fastboot commands to flash the recovery to the phone i made a mistake i wrote :
fastboot flash boot recovery.img
instead of
fastboot flash boot recovery recovery.img
....
So my guess is that i have overwritten the boot.img of the phone with the custom recovery which is bad... now i can't use the phone...
Is there a way to flash the stock boot image back? of to restore the phone like it was brand new?
Thanks for you help
Reflash the both with the correct commands !!!
Fastboot flash recovery recovery.img
and
Fastboot flash boot boot.img
Mr Hofs said:
Reflash the both with the correct commands !!!
Fastboot flash recovery recovery.img
and
Fastboot flash boot boot.img
Click to expand...
Click to collapse
Yeah this is what i wanted to do but i couldn't find a boot.img. I did find it eventually. here it is in case anyone needs it
Straight, just saying.
The boot.img is always in the rom....Most roms contain the stock boot.img. or check my backup collection and download the stock rom. It has the stock boot.img inside
Thanks a lot.

Won't boot after flash cyanogenmod boot.img

Hi Guys,
I got into a bit trouble with my Hongkong version one x and hope someone can point me to the right direction.
I was trying to flash the cyanogenmod stable rom by following instructions provided on their website. I have unlocked my phone and have found that it's actually an s-off version as well.
The first step I took is to extract the boot.img from the installer zip and run fastboot flash boot boot.img from fastboot mode. This all went well. However, when I was trying to copy the zip file using the adb push YOURROMZIP.zip /sdcard/ command, I got the no device found error. And my phone is stuck at HTC logo.
With the guidance of Thant, I have tried Clockworkmod 5.8.2.7 recovery and Philz recovery, but I got the same error when I tried to ADB side load rom in both recoverys.
Now I am totaly stuck. Does anyone know the boot.img in cyanogenmod stable rom contain, Kernal I assume? Is there anyway that I can flash the kernal of my old rom so I can at least get in Android?
My Hboot Screen
https://drive.google.com/file/d/0BwqQHN9e6x81bnBQTEQ0aUUyWFk/edit?usp=sharing
-----------------------
Problem solved, all the thanks go to Thant.
Flashed philz recovery 5.15.9, mount sd card, copy rom to sd card, flash again latest Philz and flash the rom.
---------------------
The photos are not available...also try in fastboot fastboot erase cache and try again to boot into recovery...just hold power button and volume -
And if command writing failed try another recovery and which hboot do you have?
Gesendet von meinem HTC One_M8 mit Tapatalk
mmp7 said:
Hi Guys,
I got into a bit trouble with my honkong version one x and hope someone can point me to the right direction.
I was trying to flash the cyanogenmod stable rom by following instructions provided on their website. I have unlocked my phone and have found that it's actually an s-off version as well.
The first step I took is to extract the boot.img from the installer zip and run fastboot flash boot boot.img from fastboot mode. This all went well. However, there is no way to get into recovery mode so now I have a phone that stuck in a screen with only HTC logo. Is there any way I can rectify this?
Many thanks In advance,
Ian
my fastboot screen
https://drive.google.com/file/d/0Bwq...it?usp=sharing
when I try to enter recovery from fastboot
https://drive.google.com/file/d/0Bwq...it?usp=sharing
when I try to flash clockworkmod, I got an error, command write failed, unknown error.
Click to expand...
Click to collapse
You must to flash custom recovery TWRP 2.7 or from CM11 one x forum inside have recovery and then to go in recovery and flash the rom
Second when you connect the phon try command fastboot devices and see if your phone is attachen if you dont see your phone install the google drivers from one thread from @and313 again here in the thread and then try again many people report problem with fastboot after flashing the boot.img from CM11 and on all of them is problem with the drivers
Thant said:
You must to flash custom recovery TWRP 2.7 or from CM11 one x forum inside have recovery and then to go in recovery and flash the rom
Second when you connect the phon try command fastboot devices and see if your phone is attachen if you dont see your phone install the google drivers from one thread from @and313 again here in the thread and then try again many people report problem with fastboot after flashing the boot.img from CM11 and on all of them is problem with the drivers
Click to expand...
Click to collapse
I have managed to flashed CM 11 recovery. tried TWRP 2.7 but touch screen doesn't work.
Now the problem that I am facing is to copy the zip file to SD card.
Tried using the fastboot push command but return the error device is not found. My Hboot version is 1.73.
Do you mind posing a link to the driver? I am using the latest driver in HTC sync manager.
mmp7 said:
I have managed to flashed CM 11 recovery. tried TWRP 2.7 but touch screen doesn't work.
Now the problem that I am facing is to copy the zip file to SD card.
Tried using the fastboot push command but return the error device is not found. My Hboot version is 1.73.
Do you mind posing a link to the driver? I am using the latest driver in HTC sync manager.
Click to expand...
Click to collapse
Try to flash latest Philz recovery it is for kitkat rom and tuch work and maybe in your case the SD card mounting. If not try to flash 5.15.9 there sd card mounting work 100% copy the rom and flash again latest fil and flash the CM11 rom
Thant said:
Try to flash latest Philz recovery it is for kitkat rom and tuch work and maybe in your case the SD card mounting. If not try to flash 5.15.9 there sd card mounting work 100% copy the rom and flash again latest fil and flash the CM11 rom
Click to expand...
Click to collapse
Hi Thant, will you be able to point me to the Google driver? I have flashed the latest Philz recovery but still couldn't side load ROM. When I check the device manager, the android phone is not recognized.
mmp7 said:
Hi Thant, will you be able to point me to the Google driver? I have flashed the latest Philz recovery but still couldn't side load ROM. When I check the device manager, the android phone is not recognized.
Click to expand...
Click to collapse
you flash the recovery with command fastboot flash recovery recovery.img? and this finish with success? What you see when you write fastboot devices?
This is the thread
Thant said:
you flash the recovery with command fastboot flash recovery recovery.img? and this finish with success? What you see when you write fastboot devices?
This is the thread
Click to expand...
Click to collapse
The flash was successful and I have entered the PhilZ recovery. Very nice interface.
Now back to fastboot, the screen shows FASTBOOT USB, which means it connected but when I run fastboot devices I got nothing, yet I can still flash any recovery I like. I am wondering if I can download the HongKong rom recovery anywhere so I can get into android and repeat the whole process.
mmp7 said:
The flash was successful and I have entered the PhilZ recovery. Very nice interface.
Now back to fastboot, the screen shows FASTBOOT USB, which means it connected but when I run fastboot devices I got nothing, yet I can still flash any recovery I like. I am wondering if I can download the HongKong rom recovery anywhere so I can get into android and repeat the whole process.
Click to expand...
Click to collapse
download philz recovery 5.15.9 and flash it after this mount sd card copy your rom to sd card after this flash again latest Philz and flash the rom
Thant said:
download philz recovery 5.15.9 and flash it after this mount sd card copy your rom to sd card after this flash again latest Philz and flash the rom
Click to expand...
Click to collapse
Thanks a bunch. It worked!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Flashing OTA failed. I need help to restore my phone.

Hi,
My phone is rooted and the DPI was customized. I tried to manually flash the OTA but the installation got stuck so I cannot boot into Android anymore. I tried those restore tutorials but when I try to flash using fastboot I get a "FAILED (remote: Permission denied). I tried to clear the cache in the recovery and then it got also stuck and now I can't access recovery.
This is what I can read in the bootloader
---------------------------
FASTBOOT MODE
PRODUCT_NAME - Z00A
VARIANT - ASUS_Z00A
HW_VERSION -
BOOTLOADER VERSION - unknown
IFWI - 0094.0177
SERIAL NUMBER - Xxxxx....
SIGNING - ?
SECURE_BOOT - ?
continue fastboot process
-----------------------------
I just been successful in installing TWRP recovery using the toolkit.
Edit: I installed the latest CM 13 build and it can't boot to Android. It goes straight to TWRP recovery no matter how I turn on the phone. My bootloader still looks the same.
Edit: I tried flashing a prerooted .img and stock recovery and I can go back to recovery but I still can't boot into Android or factory reset or nothing.... I'm desperate!
manlord said:
I just been successful in installing TWRP recovery using the toolkit.
Edit: I installed the latest CM 13 build and it can't boot to Android. It goes straight to TWRP recovery no matter how I turn on the phone. My bootloader still looks the same.
Edit: I tried flashing a prerooted .img and stock recovery and I can go back to recovery but I still can't boot into Android or factory reset or nothing.... I'm desperate!
Click to expand...
Click to collapse
You may need to flash boot.img and droidboot.img for the same version of rom you flashed, ie. if you flashed 139 then you must flash the recovery, boot and droidboot images for 139...
As you found the pre-root rom files, download the whole file and flash these image files too making sure you use the right commands or you will brick your phone...
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
fastboot flash system system.img
Just remember, flashing these partitions can, potentially, brick your phone. You do this at your own risk...
Happy flashing....
ultramag69 said:
You may need to flash boot.img and droidboot.img for the same version of rom you flashed, ie. if you flashed 139 then you must flash the recovery, boot and droidboot images for 139...
As you found the pre-root rom files, download the whole file and flash these image files too making sure you use the right commands or you will brick your phone...
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
fastboot flash system system.img
Just remember, flashing these partitions can, potentially, brick your phone. You do this at your own risk...
Happy flashing....
Click to expand...
Click to collapse
Thanks for your help. I did that earlier with the latest pre-rooted OTA and now it gets stuck on the splashscreen. I tried going to recovery (stock now) and doing a factory reset after flashing system.img and it still the splashscreen after I reboot. I know the 1st boot after flahing a ROM can be long, but now it's been an hour and I'm still on the splash screen...
The only other thing I can recommend is to flash a RAW rom image. As I have never needed to do this I can't say how this works but if you do a search you should find out the procedure...
This may relock your bootloader so just be aware....

Unable to Root AT ALL

So I wanted to install a CM ver on my mother's Redmi 1s and first thing I have to do is root the device right?
<image>
I have tried downloading several SuperSU.zip from multiple sources, including here at xda forums and the miui forums, to no avail.
Every single attempt has been a failure using the Stock Recovery that comes with the phone.
Fine then, I'll just use a custom recovery. I then connected the phone to my laptop via USB and used the sdk I downloaded.
After typing this line >>adb reboot bootloader, the phone booted into a screen with the fastboot bunny, all normal yes?
Then I typed >>fastboot oem unlock, but the image below doesn't show up on the phone
<image>
Instead, the command prompt just shows a few lines of the process completing
<image>
I continued to enter>>fastboot flash recovery customrecovery.img into cmd with the custom recovery image IN the platform-tools folder in sdk. Cmd again shows a few lines saying that the process completed.
<image>
However the phone still stays on the screen with the fastboot bunny, even after rebooting and then entering recovery mode, it is still the stock one. I have searched everywhere on how to root this phone but they just showed to install the SuperSU.zip using the stock recovery or the sdk method. If anyone could just help me solve this issue that would be great. If you need more information that I can provide regarding the issue feel free to ask. Thanks in advance !
P.s. Due to xda preventing me from posting outside links since I have not met the threshold, anyone who needs the pictures can message me privately.
Edit: Ah yes, I should also mention that I have tried using the stock Updater app to install the SuperSU.zip as well but that doesn't work. Also, I have tried using King Root and Kingo Root as the easy way, same thing.
Find the TWRP image for our device. I don't prefer the fastboot method; flashing TWRP and then the SuperSU zip is a whole lot more convenient as you don't need a computer.
NightRaven49 said:
Find the TWRP image for our device. I don't prefer the fastboot method; flashing TWRP and then the SuperSU zip is a whole lot more convenient as you don't need a computer.
Click to expand...
Click to collapse
But doesn't flashing TWRP without PC (with an app) requires the phone to be rooted to begin with? Or is there any workaround method?
Then use Philz recovery. There's a sticky in the general section that provides a link to such a guide using Philz. After rooting you can flash TWRP.
NightRaven49 said:
Then use Philz recovery. There's a sticky in the general section that provides a link to such a guide using Philz. After rooting you can flash TWRP.
Click to expand...
Click to collapse
Nope, still doesn't work. Tried using the stock recovery to install update.zip and also flashing the .img via sdk, both doesn't work. I'm again out of options.
before do this backup your device
you can install custom recovery with official fastboot rom.
download any official fastboot rom for your device (stable or beta does not matter)
download twrp .img file for your device
rename your recovery image file to "recovery.img"
extract the fastboot rom
go to "images" folder in extracted fastboot rom
overwrite recovery.img file with your downloaded file
flash the fastboot rom with mi flash.
wait for the installation to complete
setup your device
turn off your device and go to custom twrp recovery.
after that you can install supersu or any custom rom via twrp.
I hope you have checked this post
http://en.miui.com/thread-104048-1-1.html
For me..I started with a zip file containing the custom recovery (TWRP) it was named as Update.zip I got it from a tutorial I googled (noob, I know)...and I flashed it using stock recovery (Redmi 1s don't have locked bootloaders, I guess) and then I had Custom recovery installed..I made a backup of MIUI (it was unrooted, stock) and then flashed the CM 12.1( it was the latest then). Then there was no looking back.

Categories

Resources