Related
Hello!
Yesterday I found myself in a very terrible situation. I spend about 6-7 hours...
It just happened that I deleted the recovery (through fastboot), and before that deleted firmware of the phone. That is, there remained only mode HBOOT (fastboot). Around the internet and google there are no guides on how to return
recovery by the alternative methods or how to flash a new ROM through
fastboot.
Thats why i want to present to you my little guide... Coz i think it will be very useful for some ppls like me with the same trouble.
So, if you're in a situation where you do not have Recovery, and the phone is not started in boot ROM then first try a standard way to flash a new Recovery through fastboot mode
Standart way of flashing new recovery via fastboot
1.Connect your phone with PC via USB and power off your phone (if it up).
2.Than start up in fastboot mode - (in my situation, fastboot mode is CAMERA+POWER, then button "send") in all other (as i know) this is starting the phone while pressing button BACK.
3.Open -> Start->Run->cmd (open command prompt in windows*) and write:
Code:
fastboot devices
Than you must see your device serial number like this:
Code:
H94XTGAMSHDY
and should say "fastboot".
If all right - go next. If not - check fastboot mode (is on?) and USB cable.
4.Than change directory via cmd to where you have saved your recovery image (NEW recovery.img !!! ALWAYS CHECK MD5 SUM)
5. Than type this :
Code:
fastboot flash recovery recovery.img [enter]
(while you are stay in the same dir where you saved recovery.img)
(if you got some error about previously version or smth like this you can try to use this: fastboot erase recovery and only than try to flash new recovery from step №5)
6.Check your phone's display, as recovery is being sent and flashed to your device. And check your command prompt/shell to make sure the process is over.
7.Reboot into recovery by holding Home and Power (before it power off device).
Thats all! You can use any recovery, all what you like. I use Amon_RA's recovery.
IF WHILE FLASHING YOU GOT :
Code:
sending 'recovery' <4594kb>... OKAY [ 1.734s]
writing 'recovery'... INFOsignature checking...
FAILED <remote: signature verigy fail>
finished. total time: 3.125
Use next steps (my Alternative method)
And IF you can't flash recovery by this method it is not big trouble as you think now
Alternative way of BOOTING new recovery via fastboot checked and founded by me
Everything here is much easier and faster!
Do not be scared as I did it yesterday
Only what you need it :
Change directory via cmd to where you have saved your recovery image (NEW recovery.img !!! ALWAYS CHECK MD5 SUM)
And than TYPE:
Code:
fastboot boot recovery recovery.img
And your phone will be rebooted about 2 seconds in RECOVERY MODE. Yes!
After this you can use your old Nand Back up (restore it) and start up your old ROM. Or you can wipe all and try to flash new ROM and many operations what you can use via recovery. When you will get working ROM and flash it - you can flash recovery via adb. Or Use Rom Manager (Not recommended!)
Why we use this method? Because if you got error while flashing - FAILED <remote: signature verigy fail> you CAN'T FLASH ANY .img. Why? I Don't know, i hope some android guru's help us with it theory
(ALL AFTER THIS LINE ALL TEXT COPYED FROM WIKI.CYANOGEN.COM CREDITS GOES TO Cyanogen. Thx you, god)
If you want to flash recovery via adb (using power on phone with working firmware) (This method working 100% but strongly need working phone with working ROM)
Working only with HTC DREAM (G1) - Attention.
adb method by cyanogen version
Restoring the custom recovery image
Download the flash_image tool (HERE LINK
Next, place the file on your desktop
Change the directory to where "flash_image" is located, e.g. in Windows: cd C:\<path-to-flash_image-location>, in Linux: cd /home/USERNAME/path/to/flash_image on a Mac: cd /Users/USERNAME/path/to/flash_image)
IMPORTANT: Turn on USB debugging. Settings -> Applications -> Development -> check the box "USB Debugging"
Open up and adb shell
With your phone booted, type the following command
s:
Code:
adb root
This will start ADB as root, or notify if it is already running as root.
Code:
adb remount
This will mount the system partition (/system) as writable, allowing the following
Code:
adb push flash_image /system/bin
This will send the flash_image script into the /system/bin, so we can use it from within the shell
Code:
adb shell chmod 0755 /system/bin/flash_image
Finally, change the permissions of the script to allow it to perform the desired action.
Now that the script is installed, we are ready to proceed with flashing the custom recovery, saved on the root of the SD card earlier:
Code:
adb shell flash_image recovery /sdcard/recovery.img
P.S. If you want i can post here method by flashing original 1.6 ADP Rom via fastboot (but as i think it is on htc dev web... But i can post here cut version of this - coz original version have many not needed things.)
Credits:
Cyanogen
all xda cool ppls
ANtiHazarD
hey ANtiHazarD i have a desire so im not sure if this is suppose to work but all 3 methods fail for me, any advice, thanks in advance
Nice steps! man hope this gets a good stick or added to the rom bible, you do know though fastboot method is a common way to flash recovery
ilostchild said:
Nice steps! man hope this gets a good stick or added to the rom bible, you do know though fastboot method is a common way to flash recovery
Click to expand...
Click to collapse
That's what I was thinking... Seems almost pointless for a guide since there's instructions how to fastboot on every recovery thread.
Either way, nicely written guide. Someone will probably find this useful.
pablo34 said:
hey ANtiHazarD i have a desire so im not sure if this is suppose to work but all 3 methods fail for me, any advice, thanks in advance
Click to expand...
Click to collapse
With a desire this is quite different, as it has an activated nand flash protection (s-on), so no fastboot flash recovery here. Although this should prevent you from not having a recovery at all...
* note: I don't have a desire (yet) so this is speculation *
Best is probably something similar to this http://forum.xda-developers.com/showthread.php?t=750852
I guess if you get the correct PB99IMG.zip for exactly your device/brand you will not need a goldcard, so don't follow the howto blindly (it is for the newer SLCD versions, but the basics will still be applicable to AMOLED devices). Best would be a PB99IMG.zip that still has a hboot version < 0.92, otherwise you will need to downgrade to root. If you already have 0.92, then just take the newest image, as older ones are normally not flashable.
After step 7 of the howto, you are either done, or you will need to find instructions to downgrade if you want to root.
As soon as you have a working system, with a 0.8* hboot you can just use unrevoked to root and flash a custom recovery.
Enough OT... @ANtiHazarD: Very useful overview. Thanks.
WAY WAY WAY more complicated than it should be...
It is a simple matter of:
fastboot flash recovery recovery.img
Done.
lbcoder said:
It is a simple matter of:
fastboot flash recovery recovery.img
Done.
Click to expand...
Click to collapse
Its not quite that simple,
1) if eng spl use fastboot instructions from RA recovery post (fastboot flash recovery recovery.img)
2) if older stock spl with fastboot ruu modes (1.33.000*) where the * is
lbcoder said:
WAY WAY WAY more complicated than it should be...
It is a simple matter of:
fastboot flash recovery recovery.img
Done.
Click to expand...
Click to collapse
maybe so
but i want to post here ALL known methods thats why so much text is here
why? coz it was a trouble and the method with
fastboot flash recovery recovery.img
not working! thats why - all ways is here.
(all pre-info into 1st post in the top)
pablo34 said:
hey ANtiHazarD i have a desire so im not sure if this is suppose to work but all 3 methods fail for me, any advice, thanks in advance
Click to expand...
Click to collapse
oh... i want to give to you some advice, but don't know what exact. because i don't have desire at my hands... and can't test.
so... thats why only - sorry
maybe there is some guide in the same way in desire section?
p.s. and thanks one more time to ezterry for old support
Can you please help me,
I have stuck here with the G1 phone,
it starts up and stucks on the G! logo.
I can get into fastboot bet have the same problem :
writing 'recovery'... INFOsignature checking...
FAILED <remote: signature verigy fail>
I get into fastboot with thre android logos on skates,
even tried to restore nandroid using fastboot but I get the same error? could you help me out?
I have HTC DREAM with 1.33.0013d and radio 2.22.27.08
I am really frustrated,
I tried all you gave up here but none worked for me.
Also when I try to get into recovery I see a G1 logo with a fastboot usb written on top left in red.
behzadbayat said:
Can you please help me,
I have stuck here with the G1 phone,
it starts up and stucks on the G! logo.
I can get into fastboot bet have the same problem :
writing 'recovery'... INFOsignature checking...
FAILED
I get into fastboot with thre android logos on skates,
even tried to restore nandroid using fastboot but I get the same error? could you help me out?
I have HTC DREAM with 1.33.0013d and radio 2.22.27.08
I am really frustrated,
I tried all you gave up here but none worked for me.
Click to expand...
Click to collapse
Did you read everything before you flashed the 1.33.0013d SPL?
If yes, you would have noticed, that this SPL is not able to flash a recovery or radio using fastboot. You have to flash the orange-...nbh file to get back a full engineering SPL, but you will loose everything you have installed on the phone ...
Send from my G1 with HTCClay's UNOFFICIAL Superfly 1.6 D/S ADS using XDA App
i don't know about this spl, but all what you can do (what i know) you can use this method which named in prev. post. with RC29 or RC7 stock firmware *.nbh
after flashing all data, radio, recovery will be reflashed by a stock data. All must be fine after this... i hope
ezterry can give for your advanced advice, may be
ANtiHazarD said:
i don't know about this spl, but all what you can do (what i know) you can use this method which named in prev. post. with RC29 or RC7 stock firmware *.nbh
after flashing all data, radio, recovery will be reflashed by a stock data. All must be fine after this... i hope
ezterry can give for your advanced advice, may be
Click to expand...
Click to collapse
Don't use RC29.. its once of the most annoying NBH files to need to re-root for the dream.
If you have 1.33.0013d note the orange.nbh posted on the new radio OP post: here
ezterry said:
If you find yourself stuck without recovery!!
Dream
1) Download: orange-1.58.73.2.nbh (MD5: aca4dee0c1ece7e9773f2ecbdfbba7c0) (mirror)
2) enter fastboot and run 'fastboot flash nbh orange-1.58.73.2.nbh'
3) wait for the entire nbh to flash
4) boot into the bootloader again (it will be an engineering SPL 1.42.2000)
5) You can now re-flash the radio/hboot/recovery via fastboot that you wish to have installed.
Click to expand...
Click to collapse
basically if you intend to still use the new radio; after installing 1.58.73.2 you can reboot-bootloader; and use my fastboot installation steps at the top of that post
You can do this without a goldcard because I bypass various checks in 1.33.0013d
(It will let you install any other signed NBH but that will still wipe the phone completely; and if it fails to flash cleanly it will leave you without an engineering SPL thus make it harder to make android go again)
hey i tried to flash the MTD too and now i keep getting "E:cant open CACHE:recovery/log" when i go into recovery . I can flash roms but when i reboot my phone my phone stays in the G1 Logo . and when it does make it to the rom i can not get my market or gapps no matter what i do . please help me guys .
EDIT: theres times when i get past the g1 logo but itll just stay on the roms boot screen forever until the phone dies . does anyone have any ideas ?
try to 'fastboot wipe system -w'
after
wipe all (data/cache, cache, dalvik, ext, stats)
and move log to sd
ANtiHazarD said:
try to 'fastboot wipe system -w'
after
wipe all (data/cache, cache, dalvik, ext, stats)
and move log to sd
Click to expand...
Click to collapse
ive never really done fastboot tho . is there any other way ?
breezy169 said:
ive never really done fastboot tho . is there any other way ?
Click to expand...
Click to collapse
It's worth learning to use it ...
Really, especially when using the 14MB-hack or CustomMTD and it's not so difficult. There should be a tutorial on adb and fastboot here in the forum.
AndDiSa said:
It's worth learning to use it ...
Really, especially when using the 14MB-hack or CustomMTD and it's not so difficult. There should be a tutorial on adb and fastboot here in the forum.
Click to expand...
Click to collapse
i agree but i just finished reading the forum that shows how to do it but it sounds so complicated .
EDIT: i ended up flashing another recovery and that solved the problem . that was the weirdest thinq ive ever seen . and honestly i thought i bricked my phone but it was a simpleee fix lol . thanks for the advice tho
I am hanging at booting while trying to do this any ideas?
When I flashed a kernel I did boot boot.img first and it worked so I did flash boot boot.img with fastboot. Well that didn't work. So I just got the other boot.img for cm7 and tryed to do that. Well I got this error:
C:\adb>fastboot flash boot boot.img
sending 'boot' (3196 KB)... OKAY [ 0.875s]
writing 'boot'... FAILED (remote: partition does not exist)
finished. total time: 0.885s
When a wipe is issued:
C:\adb>fastboot -w
erasing 'userdata'... FAILED (remote: : partition doesn't exist)
finished. total time: 0.002s
I am in fastboot but I can not get into twrp2 because when I hold down the power button to enter recovery it just turns amber and just hangs. I do have some mmcblk0pXX .img's if it helps.
I think I'm having the same problem. When I try to boot the bootnew.img for intersectRaven's kernel, it hangs at the FIREFIREFIRE yellow triangle with an amber light. No fastboot commands will take me out of it. If it makes a difference, I installed the custom WiFi driver.
Thats the exact same thing is for me.
TyHi said:
Thats the exact same thing is for me.
Click to expand...
Click to collapse
I guess we're in the same boat then. I think my problem came from booting the kernel up, then installing the custom wifi driver, then trying to boot it up again.
When I flashed a kernel I did boot boot.img first and it worked so I did flash boot boot.img with fastboot. Well that didn't work. So I just got the other boot.img for cm7 and tryed to do that. Well I got this error:
C:\adb>fastboot flash boot boot.img
sending 'boot' (3196 KB)... OKAY [ 0.875s]
writing 'boot'... FAILED (remote: partition does not exist)
finished. total time: 0.885s
I am in fastboot but I can not get into twrp2 because when I hold down the power button to enter recovery it just turns amber and just hangs. I do have some mmcblk0pXX .img's if it helps.
Click to expand...
Click to collapse
Did you follow precisely the commands given here? It sounds like you did, but I just wanted to make sure. I was going to suggest you reset the bootmode to 4000. Have you already tried that?
rwphwp said:
Did you follow precisely the commands given here? It sounds like you did, but I just wanted to make sure. I was going to suggest you reset the bootmode to 4000. Have you already tried that?
Click to expand...
Click to collapse
Since apparently the OP and I have the same problem, yes I tried that. The command "fastboot -i 0x1949 oem idme bootmode 4000" doesn't work for me. It just boots into fastboot again.
I read someplace when I rooted 6.2.1 with perhaps a Burrito Root prog. The recommended order to get CM7 and TWRP . Is to go - in this order. Root, then TWRP AND lastly update.zip to sdcard for install of CM7. I made space avail. for TWRP'S Backup ( STRONGLY RECOMMEND ) BACKUP. ======which saved me a few times already on a couple frozen boots. Cause I experiment with various launchers, I think.
Yes I have. It just hangs on the yellow boot with a green light.
Smmoph said:
I read someplace when I rooted 6.2.1 with perhaps a Burrito Root prog. The recommended order to get CM7 and TWRP . Is to go - in this order. Root, then TWRP AND lastly update.zip to sdcard for install of CM7. I made space avail. for TWRP'S Backup ( STRONGLY RECOMMEND ) BACKUP. ======which saved me a few times already on a couple frozen boots. Cause I experiment with various launchers, I think.
Click to expand...
Click to collapse
The thing is that I cant even root it. It is just stuck it at boot screen for FIREFIREFIRE v1.0.
Smmoph said:
I read someplace when I rooted 6.2.1 with perhaps a Burrito Root prog. The recommended order to get CM7 and TWRP . Is to go - in this order. Root, then TWRP AND lastly update.zip to sdcard for install of CM7. I made space avail. for TWRP'S Backup ( STRONGLY RECOMMEND ) BACKUP. ======which saved me a few times already on a couple frozen boots. Cause I experiment with various launchers, I think.
Click to expand...
Click to collapse
I suck at pushing buttons on forums now (hence the accidental thank), but I'm not really trying to install CM7.
Have you tried the hard reset? Hold power button for app. 18 seconds till screen goes totally dark, then press power bttn on again, once.
Yes I have many times.
I can suggest changing the driver on usb in pc or rebboot pc after uninstall and the change it . But I wanted to show a procedure. win utility 7 gave me the necc. usb driver v. 6 did not have.
TyHi said:
Yes I have. It just hangs on the yellow boot with a green light.
Click to expand...
Click to collapse
Gotcha. Any luck with this method?
There was also A kindlefire utility v.? with an option in red for "factory reset" on the device, perhaps.
rwphwp said:
Gotcha. Any luck with this method?
Click to expand...
Click to collapse
Yes I have. Can't even do adb push. When I get into adb with using boot boot.img from cm7. I get, exec /system/bin/sh' failed no file or directory.
I would not give in, but try to stay calm with all methods to reclaim functionality. I started with rootwiki and Jayce Ooi's And Burrito in order to stay clear of CMD console cause I was not even recognised till Win_usb drivers eventually fell in place. Saw some stuff about editing path's also. Reading alot helped.
I'd join IRC and see what we can accomplish there. You all are all over the place, and some of you aren't even bricked at all.
Vashypooh said:
I'd join IRC and see what we can accomplish there. You all are all over the place, and some of you aren't even bricked at all.
Click to expand...
Click to collapse
I was in there all day, and I never got a working solution.
TheMagicPancake said:
I was in there all day, and I never got a working solution.
Click to expand...
Click to collapse
Join there ~12:45-1am EST, ill be available to help then.
Michael Hall writes about how you can win an OPPO Find 5 by porting Ubuntu Touch to it!
http://mhall119.com/2013/08/win-an-oppo-find-5/
So they're asking:
-developers who don't own the phone to develop for it so they can win one, which is nearly impossible.
-developers who own the phone to develop for it so they can win a second one.
sounds a bit weird.
(Of course winning somthing is always cool, but you get the point)
RaspberryJam said:
So they're asking:
-developers who don't own the phone to develop for it so they can win one, which is nearly impossible.
-developers who own the phone to develop for it so they can win a second one.
sounds a bit weird.
(Of course winning somthing is always cool, but you get the point)
Click to expand...
Click to collapse
-True, but during XDA: DevCon we had 3 people without a phone produce images for it, and it's not a one-chance thing, you can resubmit as often as you like.
-How about this, if you already have a Find 5, give me the same of somebody who you think should get this one instead. Could be a friend, or somebody who's work in the XDA community you think should be rewarded.
Despite having three separate developers build images and flash them onto the phone, none were able to boot into Ubuntu Touch.
Click to expand...
Click to collapse
wait, what?
http://forum.xda-developers.com/showthread.php?t=2254114
I was able to make one without major code modifications to the CM10.1 base... maybe something changed since then
of course, that image boots but isn't complete (apps don't work properly).
got other stuff on my plate, not going for the contest
paperWastage said:
wait, what?
http://forum.xda-developers.com/showthread.php?t=2254114
I was able to make one without major code modifications to the CM10.1 base... maybe something changed since then
of course, that image boots but isn't complete (apps don't work properly).
got other stuff on my plate, not going for the contest
Click to expand...
Click to collapse
Oh wow, I didn't know you had already gotten that much working. If you're not going to try for the contest, maybe somebody else can use yours as a stepping-off point and just fix what's currently broken.
Testers needed
OK guys, I've just completed a build, but I don't own the device, so I need testers.
If any of you is willing to give it a shot, here is the link: http://goo.im/devs/Androguide/Ubuntu-Touch/find5/saucy-preinstalled-find5-armhf-2.zip
Please grab a logcat for anything that doesn't work (especially if it does not boot).
mhall119 said:
Oh wow, I didn't know you had already gotten that much working. If you're not going to try for the contest, maybe somebody else can use yours as a stepping-off point and just fix what's currently broken.
Click to expand...
Click to collapse
Throw your files and what youve done so far over here. Im willing to continue work on it.
Androguide.fr said:
OK guys, I've just completed a build, but I don't own the device, so I need testers.
If any of you is willing to give it a shot, here is the link: http://goo.im/devs/Androguide/Ubuntu-Touch/find5/saucy-preinstalled-find5-armhf_2.zip
Please grab a logcat for anything that doesn't work (especially if it does not boot).
Click to expand...
Click to collapse
Re-upload again THE LINK IS DEAD & I will try and flash it and report back. Thanks a million
SystemErrorOne said:
Throw your files and what youve done so far over here. Im willing to continue work on it.
Re-upload again THE LINK IS DEAD & I will try and flash it and report back. Thanks a million
Click to expand...
Click to collapse
There you go, sorry: http://goo.im/devs/Androguide/Ubuntu-Touch/find5/saucy-preinstalled-find5-armhf-2.zip
You'll also need to flash the Ubuntu base after flashing this build: http://cdimages.ubuntu.com/ubuntu-t...ed/current/saucy-preinstalled-touch-armhf.zip
Thanks a lot :good: I can't really do anything until I got some feedback & logs for what works & doesn't.
Androguide.fr said:
There you go, sorry: http://goo.im/devs/Androguide/Ubuntu-Touch/find5/saucy-preinstalled-find5-armhf-2.zip
You'll also need to flash the Ubuntu base after flashing this build: http://cdimages.ubuntu.com/ubuntu-t...ed/current/saucy-preinstalled-touch-armhf.zip
Thanks a lot :good: I can't really do anything until I got some feedback & logs for what works & doesn't.
Click to expand...
Click to collapse
No problem buddy but hey guess what... I flashed "saucy-preinstalled-find5-armhf-2.zip" now I cant get into recovery I was using TWRP and i know you said "need to flash the Ubuntu base after flashing this build" but since i cant get into recovery I can only get into fastboot mode Do I flash this one via adb? Sorry for the noobish question
SystemErrorOne said:
No problem buddy but hey guess what... I flashed "saucy-preinstalled-find5-armhf-2.zip" now I cant get into recovery I was using TWRP and i know you said "need to flash the Ubuntu base after flashing this build" but since i cant get into recovery I can only get into fastboot mode Do I flash this one via adb? Sorry for the noobish question
Click to expand...
Click to collapse
It shouldn't touch your recovery partition at all, do you mean you can't go to recovery because it doesn't boot?
What does adb reboot recovery do?
Otherwise just fastboot flash recovery recovery.img a TWRP image, but this is pretty weird.
Oh, and when I say flash the Ubuntu base after, you don't need to reboot in between, just flash both zips one after the other, the build first and the ubuntu base afterwards. (Also remember to do a factory reset, wipe dalvik-cache and, optionally, /system
Androguide.fr said:
It shouldn't touch your recovery partition at all, do you mean you can't go to recovery because it doesn't boot?
What does adb reboot recovery do?
Otherwise just fastboot flash recovery recovery.img a TWRP image, but this is pretty weird.
Oh, and when I say flash the Ubuntu base after, you don't need to reboot in between, just flash both zips one after the other, the build first and the ubuntu base afterwards. (Also remember to do a factory reset, wipe dalvik-cache and, optionally, /system
Click to expand...
Click to collapse
fuqqqq well right now it WONT boot up just stays in the green oppo logo splash screen but....
This is what ive done so far so i can flash the TWRP image back on....I do fastboot flash recovery "here i put the recovery .img" but it doesnt want to flash it.
Then I thought why dont i just flash the other file you told me to flash So I try to do that..
I run fastboot flash recovery saucy-preinstalled-touch-armhf and i get the following error
I get error cannot load ' saucy-preinstalled-touch-armhf''
I even tried it on the recovery .img file but i get
error cannot load 'openrecovery-twrp-2.6.0.0-find5'
What i should of done was what you said, flash one right after the other but I didnt...... I by 2nd nature just wiped dalvik cache and i tapped reboot system. So im kinda stuck right now. Does it help that when I do fastboot devices I can see the random numbers generated by my device? I read on a blog for the oppo find 5 that After entering this command ( fastboot devices ), you’ll see the random numbers appeared in the command prompt. This is to ensure that your device is properly connected.)
ANY help you give me is valued. Thank you sir.
SystemErrorOne said:
fuqqqq well right now it WONT boot up just stays in the green oppo logo splash screen but....
This is what ive done so far so i can flash the TWRP image back on....I do fastboot flash recovery "here i put the recovery .img" but it doesnt want to flash it.
Then I thought why dont i just flash the other file you told me to flash So I try to do that..
I run fastboot flash recovery saucy-preinstalled-touch-armhf and i get the following error
I get error cannot load ' saucy-preinstalled-touch-armhf''
I even tried it on the recovery .img file but i get
error cannot load 'openrecovery-twrp-2.6.0.0-find5'
What i should of done was what you said, flash one right after the other but I didnt...... I by 2nd nature just wiped dalvik cache and i tapped reboot system. So im kinda stuck right now. Does it help that when I do fastboot devices I can see the random numbers generated by my device? I read on a blog for the oppo find 5 that After entering this command ( fastboot devices ), you’ll see the random numbers appeared in the command prompt. This is to ensure that your device is properly connected.)
ANY help you give me is valued. Thank you sir.
Click to expand...
Click to collapse
From your error message, you simply didn't add the .img extension to the twrp image
Also, you can't fastboot a zip, don't try.
But, did you try to simply do the following?
Code:
adb reboot recovery
There's absolutely no reason why it would have overwritten your recovery, my guess is you can't reboot to recovery using the button combination.
Anyway, if the above doesn't work, follow these steps to reflash your recovery:
Open a terminal on your pc
Make sure you cd to the directory where your twrp image is
issue the following command:
Code:
fastboot flash recovery openrecovery-twrp-2.6.0.0-find5[COLOR="DarkRed"].img[/COLOR]
Reboot to recovery using:
Code:
adb reboot recovery
Are you on windows or linux?
Okay so I did that I flashed the recovery.img then I rebooted using fastboot reboot
Now i proceed to doing adb reboot recovery but i get
error: device not found
Please excuse me as i am not an elite developer im not a noob nor an expert but It could be that I couldnt get the drivers for the phone installed. I know adam outler on G+ said as quoted
+Franco Colomba I had no such issues with drivers. The only thing was ADB needed an extra USB VID added.
Click to expand...
Click to collapse
May that be the resolution ?
im on windows 8 (Yes i know... Windows 8 Sucks)
SystemErrorOne said:
Okay so I did that I flashed the recovery.img then I rebooted using fastboot reboot
Now i proceed to doing adb reboot recovery but i get
error: device not found
Please excuse me as i am not an elite developer im not a noob nor an expert but It could be that I couldnt get the drivers for the phone installed. I know adam outler on G+ said as quoted
May that be the resolution ?
im on windows 8 (Yes i know... Windows 8 Sucks)
Click to expand...
Click to collapse
I don't think it's an usb driver issue since you have fastboot working. It's true that we don't have adb access when in fastboot mode.
Follow this guide, it's exactly about your issue and assumes you're on windows: Unbrick the Find 5(Software unbrick via fastboot)
Androguide.fr said:
I don't think it's an usb driver issue since you have fastboot working. It's true that we don't have adb access when in fastboot mode.
Follow this guide, it's exactly about your issue and assumes you're on windows: Unbrick the Find 5(Software unbrick via fastboot)
Click to expand...
Click to collapse
Okayy sorry im taking forever to reply im trying it out and its not working...
no matter what img i flash to it it wont go into recovery when i hold down power + vol down
dunno what to do from this point. I will keep trying
SystemErrorOne said:
Okayy sorry im taking forever to reply im trying it out and its not working...
no matter what img i flash to it it wont go into recovery when i hold down power + vol down
dunno what to do from this point. I will keep trying
Click to expand...
Click to collapse
Try this:
Download a CM build
Open it with winrar and extract the boot.img from it
hold shift and do a right-click in the folder where you extracted the boot.img, and select "open a terminal here" (or whatever the header is)
Issue this command
Code:
fastboot flash boot boot.img
Now try again to reboot to recovery using the buttons combination
hurray so i managed to get the phone working by using a script found in that one thread you linked me too.. never the less i managed to get into TWRP and from there i had already made a backup (THANK GOD) and i restored and the phone is up and running perfectly. Now what Im going to do is what you instructed to do first.
1. the build first
2. then the ubuntu base afterwards
with
factory reset, wipe dalvik-cache
i will post back my results wish me luck
SystemErrorOne said:
No problem buddy but hey guess what... I flashed "saucy-preinstalled-find5-armhf-2.zip" now I cant get into recovery I was using TWRP and i know you said "need to flash the Ubuntu base after flashing this build" but since i cant get into recovery I can only get into fastboot mode Do I flash this one via adb? Sorry for the noobish question
Click to expand...
Click to collapse
I've noticed that the Find 5 is kind of hit-or-miss when trying to get into recovery using the power+volume-down combo. It seems that maybe you need to have it disconnected from USB, and start pressing volume-down very soon after, but not at the same instant, as the power button. Also, it takes a while of looking at the OPPO splash before it gets into recovery.
mhall119 said:
I've noticed that the Find 5 is kind of hit-or-miss when trying to get into recovery using the power+volume-down combo. It seems that maybe you need to have it disconnected from USB, and start pressing volume-down very soon after, but not at the same instant, as the power button. Also, it takes a while of looking at the OPPO splash before it gets into recovery.
Click to expand...
Click to collapse
Yes mhall you are correct. I found a little trick to get it into recovery...well im not sure if its a trick or not but its what helped me get back into recovery after it not booting up. I might make a video about it later. But heres an update:
So i flashed both the build and the preinstalled package and then did factory reset which wipes out cache and dalvik
then i rebooted.
RESUTLS: it stays on the bootscreen aka OPPO GREEN LOGO.
what do you think is the problem now Androguide.fr ?
I did EVERYTHING you told me too
SystemErrorOne said:
Yes mhall you are correct. I found a little trick to get it into recovery...well im not sure if its a trick or not but its what helped me get back into recovery after it not booting up. I might make a video about it later. But heres an update:
So i flashed both the build and the preinstalled package and then did factory reset which wipes out cache and dalvik
then i rebooted.
RESUTLS: it stays on the bootscreen aka OPPO GREEN LOGO.
what do you think is the problem now Androguide.fr ?
I did EVERYTHING you told me too
Click to expand...
Click to collapse
Yeah, Michael Hall reported to me that the build doesn't boot either.
I'm working on a new build using a different toolchain, as with the stock Google TC I had to hack my around -Werror flags and this might be the problem.
I'll post the progress here.
So this is what happened, I was on I MedroM v3, so I was there was a firmware in beta (the 7.0 update) so I've done it and now I'm stuck in a bootloop
, I flashed the Nougat recovery so it locked my bootloader
and removed TWRP so I can't even go to flash the old rom
again. I also can't get the product id now cause I don't have an OS installed, there's no way to pull it without it an OS. I have tried every existing method possible and nothing (including the sd
card method with update.app and bla bla bla)
So I can't flash files through fastboot It says " Command not allowed"
Can somebody please help me, I have experience with flashing and everything but I in my entire life have not seen that a phone company so big doesn't have a ******** flashtool
or some other way of recovering hard bricked devices instead of buying a new motherboard or something..
If somebody could help me I would be so grateful! Please excuse my language I'm very mad and frustrated, I need my phone for work and now I'm offline..
- Fastboot is available but the bootloader is locked
- No TWRP
- No OS Installed
Download a firmware you want, extract the update.app and put it in sd card folder. From the phone completely shutdown, press vol +, vol - and power at the same time hold it until the updater with percentage progress moving appears.. you should be fine after that.. ? i believe. Maybe try it. That's what i did on my case
No, It says "Software Install failed! Incompatability with current software version"
When I go to eRecovery t says that it cant connect to WIFI.
As I said i tried every known method and I can't get it to work. Spent my whole day trying to fix it, I'm out of ideas
akseon said:
So this is what happened, I was on I MedroM v3, so I was there was a firmware in beta (the 7.0 update) so I've done it and now I'm stuck in a bootloop
, I flashed the Nougat recovery so it locked my bootloader
and removed TWRP so I can't even go to flash the old rom
again. I also can't get the product id now cause I don't have an OS installed, there's no way to pull it without it an OS. I have tried every existing method possible and nothing (including the sd
card method with update.app and bla bla bla)
So I can't flash files through fastboot It says " Command not allowed"
Can somebody please help me, I have experience with flashing and everything but I in my entire life have not seen that a phone company so big doesn't have a ******** flashtool
or some other way of recovering hard bricked devices instead of buying a new motherboard or something..
If somebody could help me I would be so grateful! Please excuse my language I'm very mad and frustrated, I need my phone for work and now I'm offline..
- Fastboot is available but the bootloader is locked
- I can't boot into TWRP
- No OS Installed
Click to expand...
Click to collapse
I had the same problem, but with the L31.
First try to use https://www.xda-developers.com/how-to-install-twrp/
Then with the file i send you attached (MAF32)
- Fastboot flash boot boot.img
- Fastboot flash system system.img
- Fastboot flash cust cust.img
- and finally TWRP
After that i puted the first exctrated uppdate.pp in my memory card and with the "3 buttons" process i flashed it. Then i repeated the same process with the second one (http://forum.xda-developers.com/hua...droid-nougat-dev-build-huawei-t3488360/page33). After this finished, again with the 3 buttons i made a factory reset.
5 minutes later, it was working.
i don't understand how to boot to fastboot ? and where to get these img files i am really stuck here pleaase
You don't understand, In order to unlock the bootloader i need the product ID which you get by typing some number combination in the dialer. I cant get to the dialer cause I dont have any OS installed, cause the old was dirty flashed. So thats why i cant flash TWRP etc..
hello, i'm using Huawei P9 Lite VNS-L21. i tried to flash the stock nougat Firmware Which i actually did and it worked flawless! but there was a little problem because there wasn't any Software update option in there, so after that i wanted to downgrade to stock MM. IDK what happened wrong while installing that, my phone got BRICKED. i don't have the Erecovery and twrp either. i cant flash firmware via DLOAD Method. the only thing i have is FASTBOOT mode..
i tried literally everything.. but nothing working..
I sent it to HUAWEI CUSTOMER CARE and they returned it back after a couple of days...
im really very worried because ive been using this phone for like 2 months ... and now im helplesss, If anybody is reading this please help/ assist me out of this.. i'd be really greatfull if anybody's going to help me out..
hash26 said:
hello, i'm using Huawei P9 Lite VNS-L21. i tried to flash the stock nougat Firmware Which i actually did and it worked flawless! but there was a little problem because there wasn't any Software update option in there, so after that i wanted to downgrade to stock MM. IDK what happened wrong while installing that, my phone got BRICKED. i don't have the Erecovery and twrp either. i cant flash firmware via DLOAD Method. the only thing i have is FASTBOOT mode..
i tried literally everything.. but nothing working..
I sent it to HUAWEI CUSTOMER CARE and they returned it back after a couple of days...
im really very worried because ive been using this phone for like 2 months ... and now im helplesss, If anybody is reading this please help/ assist me out of this.. i'd be really greatfull if anybody's going to help me out..
Click to expand...
Click to collapse
Why don't you flash TWRP in fastboot mode?
fasboot flash recovery recovery.img
PS: You need to start your own thread, really, rather than hijack someone else's
StrangerWeather said:
Why don't you flash TWRP in fastboot mode?
fasboot flash recovery recovery.img
PS: You need to start your own thread, really, rather than hijack someone else's
Click to expand...
Click to collapse
I'm new to this forum, if i did something that i shoud not I'm sorry about that and thanks for replying..
Ive tried many times to flash twrp recovery through fastboot it says installed but when i try to go to recovery there isnt any recovery...
i have a post with a same problem but with frp active, any sugestions?
hash26 said:
I'm new to this forum, if i did something that i shoud not I'm sorry about that and thanks for replying..
Ive tried many times to flash twrp recovery through fastboot it says installed but when i try to go to recovery there isnt any recovery...
Click to expand...
Click to collapse
What happens when you type : adb reboot recovery?
StrangerWeather said:
What happens when you type : adb reboot recovery?
Click to expand...
Click to collapse
Nothing happens it just reboots itself again n again but recovery doesn't open itself
hash26 said:
Nothing happens it just reboots itself again n again but recovery doesn't open itself
Click to expand...
Click to collapse
Ok, this is what I would do if I were you. I would pick a rom in the development section, eg. RR. Then I would extract it and get the system image and boot image and fastboot flash them. To extract the rom, use SuperR's Kitchen.
Hope this helps.
StrangerWeather said:
Ok, this is what I would do if I were you. I would pick a rom in the development section, eg. RR. Then I would extract it and get the system image and boot image and fastboot flash them. To extract the rom, use SuperR's Kitchen.
Hope this helps.
Click to expand...
Click to collapse
I'm about to do this! Thanks you
StrangerWeather said:
Ok, this is what I would do if I were you. I would pick a rom in the development section, eg. RR. Then I would extract it and get the system image and boot image and fastboot flash them. To extract the rom, use SuperR's Kitchen.
Hope this helps.
Click to expand...
Click to collapse
thank you so much for replying but there is something i want to ask you about..
the tool you told me about "SuperR's Kitchen" works on Linux.. and i'm a windows user is there any other software that runs on Windows and works as same as super'R ..
Waiting for your reply!!
hash26 said:
thank you so much for replying but there is something i want to ask you about..
the tool you told me about "SuperR's Kitchen" works on Linux.. and i'm a windows user is there any other software that runs on Windows and works as same as super'R ..
Waiting for your reply!!
Click to expand...
Click to collapse
Hi!
There is this but I haven't tested it: https://forum.xda-developers.com/android/help/extract-dat-marshmallow-lollipop-easily-t3334117
Let us know how it goes!
Greetings, I tried flashing my LG H440F to its original state via LG Flash Tool.
At the time being it was stuck on 1% and after several errors I desisted and tried another KDZ to flash with same result (stuck at 1%)
Now the phone is stuck in fastboot, I can't boot it to Download mode neither do a Hard Reset as it does nothing.
Adb does not recognize the device and fastboot always throws a FAILED (remote: unknown command) when trying to do anything.
Did I just entirely brick my phone?
Best regards.
No one?
MathewBricks said:
No one?
Click to expand...
Click to collapse
Try to post it in general thread. Maybe someone there will look into it. Btw, fastboot is disabled on lg spirit, so any fastboot command won't work on it.
mayankjet said:
Try to post it in general thread. Maybe someone there will look into it. Btw, fastboot is disabled on lg spirit, so any fastboot command won't work on it.
Click to expand...
Click to collapse
Thanks for the advice. I noticed that kinda late.
MathewBricks said:
Greetings, I tried flashing my LG H440F to its original state via LG Flash Tool.
At the time being it was stuck on 1% and after several errors I desisted and tried another KDZ to flash with same result (stuck at 1%)
Now the phone is stuck in fastboot, I can't boot it to Download mode neither do a Hard Reset as it does nothing.
Adb does not recognize the device and fastboot always throws a FAILED (remote: unknown command) when trying to do anything.
Did I just entirely brick my phone?
Best regards.
Click to expand...
Click to collapse
helo i had a very bad stuck too for weeks.... coulnt found the way to... after many try i could finaly enter in download state,...yes you have to try and try...then i got stuck again untill i found out that if you want back the original state , you ca only do it with the country native rom.... hope it help
papilonaa said:
helo i had a very bad stuck too for weeks.... coulnt found the way to... after many try i could finaly enter in download state,...yes you have to try and try...then i got stuck again untill i found out that if you want back the original state , you ca only do it with the country native rom.... hope it help
Click to expand...
Click to collapse
I had same error while trying to flash wrong .zip file, i did hard reset and while TWRP was trying to hard reset i used adb commands, i dont know will this be helpful, cause you dont have custom recovery.
Sent from my LG-H440n from Serbia