I just received my new nexus 5.
This is what i did:
1. enabled adb in settings.
2. booted in fastboot mode and launched the "fastboot oem unlock" command
3. rebooted end re-enabled adb settings
4. booted in fastboot mode with "reboot bootloader"
5. flashed latest CWM recovery with "flastboot flash recovery ..."
now my recovery is empty with a scary red triangle in the middle. If i reboot the phone all works normally.
I can even flash other recovery images through the fastboot mode but nothing changes.
What can i do now?
Thanks
Red triangle is stock recovery. You didn't flash other recovery.
Not sure what commands you're using for flashing but I wrote a detailed adb and fastboot thread which you can get to via my signature.
Sent from my Nexus 5 using Tapatalk
what command are you using to flash other recoveries?
i renamed the downloaded file as recovery.img then typed "fastboot flash recovery recovery.img"
it said transferring and flashing done
PacManZ86 said:
i renamed the downloaded file as recovery.img then typed "fastboot flash recovery recovery.img"
it said transferring and flashing done
Click to expand...
Click to collapse
Download it again. In fact you should download TWRP not cwm. Also please read the thread I asked you to read.
Sent from my Nexus 5 using Tapatalk
So, i've tried with CWM, TWRP, with different cables, with different computers, it just seems that my recovery is not writable.
Have i received a faulty phone?
Now i'll try to flash stock recovery than again TWRP.
If it doesn't work i'll flash the whole factory image...
i dont have any other idea
Flashing stock recovery didn't work.
Flashing everything stock worked fine. I think something in the bootloader messed up
Backup everything then flash userdata.img with fastboot while in bootloader.
PacManZ86 said:
Flashing stock recovery didn't work.
Flashing everything stock worked fine. I think something in the bootloader messed up
Click to expand...
Click to collapse
I think you're doing something wrong.
Sent from my Nexus 5 using Tapatalk
I said that flashing everything stock and then TWRP worked fine
PacManZ86 said:
I said that flashing everything stock and then TWRP worked fine
Click to expand...
Click to collapse
You didn't. You said "flashing everything stock worked fine" with no mention of "TWRP". ;]
Sent from my Nexus 5 using Tapatalk
you're right
PacManZ86 said:
you're right
Click to expand...
Click to collapse
hehe sometimes I am..
Related
Hello everyone,
I am a new htc sensation user and I recently rooted it using the traditional method and have been installing roms since then.
However, recently when I was installing CarbonRom Kitkat 4.4.3, the ClockWork Mod recovery told me that I cannot flash the rom ( I don't know for what reason). I thought it was something to do with my recovery. So I decided to flash 4EXT touch recovery but as I have S-on, even after giving the command through fastboot for erasing recovery and all the partitions "fastboot -w" , the command prompt gave me this error " remote access not allowed". So I thought of going on with the flashing and flashed the 4EXT recovery image through fastboot. But when I tried to boot into recovery , the phone was just stuck on the htc white screen.
As I did not erase the recovery and flashed a new recovery, i think that I have overlapped the two recoveries and have corrupted them. Now, my phone boots only into the bootloader and I also have s-on. Can anyone please tell me how to install the stock rom (as I would like to revert back to the original rom) through bootloader and fastboot? i heard about the PG58IMG method but will it work on s-on? Please help me out.
Hi, im guessing u already have recovery.img in ur fastboot folder so try this command from fastboot
fastboot boot recovery.img
Hopefully that will get u there so u can flash a rom but u will have to download 4ext recovery updater app once phone is booted to flash recovery coz doing above command only boots recovery, doesnt flash it. It works on desire s and desire so it should work for sensation too (hopefully)
jmcclue said:
Hi, im guessing u already have recovery.img in ur fastboot folder so try this command from fastboot
fastboot boot recovery.img
Hopefully that will get u there so u can flash a rom but u will have to download 4ext recovery updater app once phone is booted to flash recovery coz doing above command only boots recovery, doesnt flash it. It works on desire s and desire so it should work for sensation too (hopefully)
Click to expand...
Click to collapse
So this means that I should first flash the recovery and then boot it using the command
fastboot boot recovery.img
?? or should I just boot it up using the command . And is there anyway to give any master commands like erase a partition while on s-on? And which recovery do u prefer CWM or 4EXT?
hammadyi said:
So this means that I should first flash the recovery and then boot it using the command
fastboot boot recovery.img
?? or should I just boot it up using the command . And is there anyway to give any master commands like erase a partition while on s-on? And which recovery do u prefer CWM or 4EXT?
Click to expand...
Click to collapse
since you are on S-ON go for 4ext
rzr86 said:
since you are on S-ON go for 4ext
Click to expand...
Click to collapse
That is actually where the problem started from. i tried to install 4ext before erasing CWM and I think that caused the problem.
Do you think that recoveries can be overlapped or am i just being pointless? And can you tell me about any master commands like erasing a parition that will work with s-on?
hammadyi said:
That is actually where the problem started from. i tried to install 4ext before erasing CWM and I think that caused the problem.
Do you think that recoveries can be overlapped or am i just being pointless? And can you tell me about any master commands like erasing a parition that will work with s-on?
Click to expand...
Click to collapse
you can overwrite 4ext in top of cwm
i used to have cwm but i changed it with 4ext using only the command
fastboot fash recovery recovery.img
i didn't use any command for erasing partitions
rzr86 said:
you can overwrite 4ext in top of cwm
i used to have cwm but i changed it with 4ext using only the command
fastboot fash recovery recovery.img
i didn't use any command for erasing partitions
Click to expand...
Click to collapse
I also used the same commands but since then I am not able to get into the recovery. it just shows the htc logo on white background
Do you think it has something to do with s-on? were you on s-off when you flashed the recovery?
hammadyi said:
I also used the same commands but since then I am not able to get into the recovery. it just shows the htc logo on white background
Do you think it has something to do with s-on? were you on s-off when you flashed the recovery?
Click to expand...
Click to collapse
Nothing to do with s-on. Try flashing 4ext recovery again
fastboot flash recovery recovery.img
If that doesnt work then try what i said earlier
fastboot boot recovery.img
hammadyi said:
I also used the same commands but since then I am not able to get into the recovery. it just shows the htc logo on white background
Do you think it has something to do with s-on? were you on s-off when you flashed the recovery?
Click to expand...
Click to collapse
no was on S-ON
I saw this forum on xda which says that we can use the riff box to install partitions so can I do the same with my recovery?
http://forum.xda-developers.com/showthread.php?p=53343296
hammadyi said:
I saw this forum on xda which says that we can use the riff box to install partitions so can I do the same with my recovery?
http://forum.xda-developers.com/showthread.php?p=53343296
Click to expand...
Click to collapse
i don't think you need the riff box now
you can go first for ruu.exe to restore everything back to stock
hammadyi said:
I saw this forum on xda which says that we can use the riff box to install partitions so can I do the same with my recovery?
http://forum.xda-developers.com/showthread.php?p=53343296
Click to expand...
Click to collapse
Did u try the command
fastboot boot recovery.img
I tried it last night on my sensation and it works, boots u into recovery.
jmcclue said:
Did u try the command
fastboot boot recovery.img
I tried it last night on my sensation and it works, boots u into recovery.
Click to expand...
Click to collapse
So i just flashed stock htc sensation recovery but I do not know how to install the stock rom through stock recovery can you tell me how to do that?
hammadyi said:
So i just flashed stock htc sensation recovery but I do not know how to install the stock rom through stock recovery can you tell me how to do that?
Click to expand...
Click to collapse
connect your device in fastboot mode to pc
double click the ruu from pc and follow the on screen instructions
by the way did you do first as jmcclue told you?
rzr86 said:
connect your device in fastboot mode to pc
double click the ruu from pc and follow the on screen instructions
by the way did you do first as jmcclue told you?
Click to expand...
Click to collapse
yes i did that but as there was no recovery it would not boot but after installing the stock rom it worked
hammadyi said:
yes i did that but as there was no recovery it would not boot but after installing the stock rom it worked
Click to expand...
Click to collapse
so now you have access to the OS
did you try again to flash a custom recovery?
rzr86 said:
so now you have access to the OS
did you try again to flash a custom recovery?
Click to expand...
Click to collapse
actually it did not go according to plan and while installing the ruu it failed. so now I am looking for a signed stock rom to install through fastboot using this command
fastboot update update.zip
would that be fine?
hammadyi said:
actually it did not go according to plan and while installing the ruu it failed. so now I am looking for a signed stock rom to install through fastboot using this command
fastboot update update.zip
would that be fine?
Click to expand...
Click to collapse
read from this thread-> 4. Flashing RUU manually
http://forum.xda-developers.com/showthread.php?t=1672425
i don't know if this command exists but you can use this one
fastboot flash zip pg58img.zip
edit: by the way what failure did you have with ruu?
Help pls i just installed CWM on my Tablet using this code
fastboot flash recovery recovery.img
then when i was about to test it i accidentally entered this code
fastboot flash boot recovery.img but i was supposed to enter fastboot boot recovery.img
now i can boot to CWM but everytime i boot it goes straight to CWM not to the system
so i tried flashing the boot-root.img using this code again fastboot flash boot boot-root.img (the boot-root.img was provide by superPichu before)
and now my tablet keeps on rebooting =( i can still enter fastboot and CWM any help pls?
What rom was originally on the tablet? You'll have to procure the boot image from that rom and flash it. That or just reinstall the entire rom ...either from fastboot or from cwm. Your data should be intact.
Sent from my SHIELD Tablet using Tapatalk
ailima said:
What rom was originally on the tablet? You'll have to procure the boot image from that rom and flash it. That or just reinstall the entire rom ...either from fastboot or from cwm. Your data should be intact.
Sent from my SHIELD Tablet using Tapatalk
Click to expand...
Click to collapse
thanks so much what i did was to install the zip file again from CWM i tried flashing the boot.img alone but didnt work so yeah flashing the zip did the trick thank you
No worries. Glad you got it sorted.
Hey there guys. I have recently flashed CWM-touch-6.0.4.7-falcon.img im able to go into recovery when i flash it, on reboot i selected yes for the fix install stock recovery, when back to recovery and it has an android with an exclamation mark coming out of it with it saying 'no command' at the bottom. How do i fix this? Moto G 3G 1st gen
You can try:
Code:
fastboot erase recovery
And then:
Code:
fastboot flash recovery recoveryname.img
After you flash the custom recovery boot into it right away and see if that works.
.:Dark:. said:
You can try:
Code:
fastboot erase recovery
And then:
Code:
fastboot flash recovery recoveryname.img
After you flash the custom recovery boot into it right away and see if that works.
Click to expand...
Click to collapse
I did that and it was all success but same thing happened
Also i tried flashing stock recovery but still no luck
An Android with an exclamation with 'no command' means you are on the stock recovery. Did you try the latest TWRP?
legolas06 said:
An Android with an exclamation with 'no command' means you are on the stock recovery. Did you try the latest TWRP?
Click to expand...
Click to collapse
Oh right ok. No i haven't used TWRP, i don't really like it. I tried CWM touch but i haven't tried normal CWM yet
You can also try philz recovery. Not sure why it won't stick after you flash but be sure go into recovery right after you finish flashing otherwise it will overwrite back to stock I believe.
.:Dark:. said:
You can also try philz recovery. Not sure why it won't stick after you flash but be sure go into recovery right after you finish flashing otherwise it will overwrite back to stock I believe.
Click to expand...
Click to collapse
I always go straight into recovery after i flash it but when i reboot it goes back to stock recovery :/
What message do you get after flashing the recovery? Previously I got 'partition size mismatch' indicating I flashed a recovery different from stock. Philz & TWRP worked fine for me.
legolas06 said:
What message do you get after flashing the recovery? Previously I got 'partition size mismatch' indicating I flashed a recovery different from stock. Philz & TWRP worked fine for me.
Click to expand...
Click to collapse
I forget, ill check it tomorrow as today i am a bit busy
I get a mismatch partition size (recovery) when i flash. I boot straight away to recovery, then say yes to disable flash stock recovery, reboot into recovery and stock recovery. I flashed the non touch CWM this time
bublz654 said:
I get a mismatch partition size (recovery) when i flash. I boot straight away to recovery, then say yes to disable flash stock recovery, reboot into recovery and stock recovery. I flashed the non touch CWM this time
Click to expand...
Click to collapse
Then sorry I'm not sure about the reason. May be you downloaded a wrong recovery or that recovery doesn't work with your bootloader. Just search the thread you downloaded this from to find any solution. Or if you don't like the TWRP try Philz touch as it is CWM based.
http://forum.xda-developers.com/showthread.php?t=2639583 .
Currently the only supported recovery for moto g is TWRP by h2o64.
legolas06 said:
Then sorry I'm not sure about the reason. May be you downloaded a wrong recovery or that recovery doesn't work with your bootloader. Just search the thread you downloaded this from to find any solution. Or if you don't like the TWRP try Philz touch as it is CWM based.
http://forum.xda-developers.com/showthread.php?t=2639583 .
Currently the only supported recovery for moto g is TWRP by h2o64.
Click to expand...
Click to collapse
I have flashed CWM-touch and normal CWM before until flashify came along and made my recovery screwed up
I suggest you try using mfastboot included here: https://www.androidfilehost.com/?fid=23578570567719065
NOTE: mfastboot erase recovery is not required. Simply use: mfastboot flash recovery recovery.img
lost101 said:
I suggest you try using mfastboot included here: https://www.androidfilehost.com/?fid=23578570567719065
NOTE: mfastboot erase recovery is not required. Simply use: mfastboot flash recovery recovery.img
Click to expand...
Click to collapse
I just tried that and still the same issue occurs
bublz654 said:
I just tried that and still the same issue occurs
Click to expand...
Click to collapse
Could you try the latest TWRP just to rule out a bad recovery.img: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
lost101 said:
Could you try the latest TWRP just to rule out a bad recovery.img: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Click to expand...
Click to collapse
I'll try the philz recovery first as Im not a real big fan of twrp lol
lost101 said:
Could you try the latest TWRP just to rule out a bad recovery.img: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Click to expand...
Click to collapse
I flashed philz recovery. Rebooted again and went into recovery and it worked, the recovery was still there
But one more thing on reboot of recovery it didn't ask if i wanted to fix root. Am i rooted already or not? :/
Are you on stock or a custom rom? Certain custom roms may have built in root access for everything else you will have to flash SuperSU.
Glad to see you got the recovery issue sorted. I'm with you I don't particularly like TWRP so I pretty much use Philz exclusively.
Hey,
first of all i KNOW there is a subject with nearly the exact same topic, and i followed the directions but somethng doesn't work.
I still have TWRP on the phone, and when im in bootloader mode and run "fastboot devices" i see the result.
but i can't seem to ADB push or anything else (maybe im missing some commands?)
so i used the NRT root kit and i use the "fastboot flash" function and install the .img file - the software says my device is identified and it installs the system.img file (found on the "image-hammerhead-mra58k" zip), but then the device boots to TWRP and still can't boot to the system itself.
help please!
Sideload a factory rom and u will be fine. U can do it in the advanced portion of TWRP, but u need a pc, or ur hit
Sent from my Nexus 6 using Tapatalk
Sounds to me like you're using adb commands in fastboot.
Boot into bootloader (not recovery)
Type fastboot devices
It should return showing your device
Then you need to make sure you have stock img's downloaded and completely extracted so you have all the img files in the folder you're running fastboot from (rename the radio to simply radio.img)
Then type
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash radio radio.img
Then boot back into recovery and wipe cache and dvalik for just in case fun
Then reboot system and wait
Sent from my Xperia z5 by Tapatalk
Thank you very very much guys!
that worked! WOOHOO!!
Good good!
Sent from my Xperia z5 by Tapatalk
Im fairly new at this kinda thing so i didnt know what i was doing. i tried flashing TWRP using fastboot but when i entered "fastboot boot recovery.img" it said "FAILED (remote: dtb not found). So i tried using the TWRP app and flashed my recovery, but when i went to recovery it was still stock recovery. And then because i didnt know what i was doing i flashed TWRP using the app to my boot and now when i boot it just shows the mi logo. Ive tried flashing it using MiFlash but the results were just the same. Pls help me
Nobic said:
Im fairly new at this kinda thing so i didnt know what i was doing. i tried flashing TWRP using fastboot but when i entered "fastboot boot recovery.img" it said "FAILED (remote: dtb not found). So i tried using the TWRP app and flashed my recovery, but when i went to recovery it was still stock recovery. And then because i didnt know what i was doing i flashed TWRP using the app to my boot and now when i boot it just shows the mi logo. Ive tried flashing it using MiFlash but the results were just the same. Pls help me
Click to expand...
Click to collapse
fastboot flash recovery recovery.img
fastboot reboot when pressing vol up maybe?
"FAILED (remote: dtb not found).
Click to expand...
Click to collapse
You choose the wrong TWRP for flash to mi4c. Probably TWRP version for nougat rom flashed on lollipop rom.
Here https://forum.xda-developers.com/showpost.php?p=71120584&postcount=9 follow the steps & you'll be fine. Next time doesn't do anything stupid & read all the introductions before mess with your phone.
Ive tried flashing it using MiFlash but the results were just the same.
Click to expand...
Click to collapse
It can't be same if you flash xiaomi official rom using MiFlash. Looks like you are not flashed it properly. do it corrently .