Related
So I am looking to flash a recovery image without RomMangaer from the device itself.
Should not be a issue since I can use flash_image to flash it, but ofc my ROM does not have it.
I found this thread here: http://forum.xda-developers.com/showthread.php?t=902493 that has a flash_image file attached to it...
My question is, can I use that flash_image file, even though that is in the G2 forum or do I need one built for the tbolt specifically? If I do can someone please link to it.
TIA.
It is ok to answer, I won't bite.
You need to grab the correct recovery file. Probably easiest to use Revolution to do this.
Sorry.... Revolutionary.
Look here as well.
http://forum.xda-developers.com/showthread.php?t=1179386
arbrouwer said:
You need to grab the correct recovery file. Probably easiest to use Revolution to do this.
Click to expand...
Click to collapse
arbrouwer said:
Sorry.... Revolutionary.
Click to expand...
Click to collapse
arbrouwer said:
Look here as well.
http://forum.xda-developers.com/showthread.php?t=1179386
Click to expand...
Click to collapse
Hi, I am not looking for a recovery file, I have CWMR already installed. I am looking for a flash_image file, so I can use a command such as flash_image recovery recovery.img if I wanted.
Thanks for trying.
Sounds like you want to run adb commands, not my specialty. Why not grab the appropriate img file and flash through hboot or clockwork.
http://rootzwiki.com/forum/11-thunderbolt/
MordyT said:
Hi, I am not looking for a recovery file, I have CWMR already installed. I am looking for a flash_image file, so I can use a command such as flash_image recovery recovery.img if I wanted.
Thanks for trying.
Click to expand...
Click to collapse
If you're meaning system partitions, you have to make those yourself through using dd and some mounting on linux.
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
http://www.slatedroid.com/topic/5799-repack-systemimg/
http://wiki.archosfans.com/index.php?title=Dump_your_Home_Tablet_rom_and_create_a_custom_rom
http://www.androidtablets.net/forum...notes-modifying-system-partition-desktop.html
Someone also JUST ASKED this on the same page of the q/a and got an answer. No one ever reads previous posts anymore
If you mean flashing recovery you have to grab it from the clockwork mod site and flash it using fastboot.
http://android-dls.com/wiki/index.php?title=Fastboot
arbrouwer said:
Sounds like you want to run adb commands, not my specialty. Why not grab the appropriate img file and flash through hboot or clockwork.
http://rootzwiki.com/forum/11-thunderbolt/
Click to expand...
Click to collapse
I do want to run adb commands - a very specific one - on the phone. The adb command is called "flash_image - such as flash_image boot boot.img.
I will be able to flash different partitions without the need of a PC. The only thing is, while a ASOP rom will have the flash_image command (and file called flash_image) a ROM like the one I am on (or even a stock rom) won't. So I need the file... The link I posted in the op has a flash_image file at the bottom, but I don't know if it works for thunderbolt since it is in a g2 forum...
yareally said:
If you're meaning system partitions, you have to make those yourself through using dd and some mounting on linux.
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
http://www.slatedroid.com/topic/5799-repack-systemimg/
http://wiki.archosfans.com/index.php?title=Dump_your_Home_Tablet_rom_and_create_a_custom_rom
http://www.androidtablets.net/forum...notes-modifying-system-partition-desktop.html
Someone also JUST ASKED this on the same page of the q/a and got an answer. No one ever reads previous posts anymore
If you mean flashing recovery you have to grab it from the clockwork mod site and flash it using fastboot.
http://android-dls.com/wiki/index.php?title=Fastboot
Click to expand...
Click to collapse
Actually, I was not asking that. I know how to make them and all. Do you see my low post count? It is because I read and read and read. Thanks for the advise though.
While I am asking about flashing recovery, I was not asking about hwo to do it in fastboot - I was asking how to do it on the device itself. Without ROM Manager.
In fact, I already know how to do it on the device itself... I need to use the command flash_image recovery recovery.img... except I am missing flash_image on my current ROM... so does anyone know where a version of that file is that is compatible with our tbolts?
MordyT said:
I do want to run adb commands - a very specific one - on the phone. The adb command is called "flash_image - such as flash_image boot boot.img.
I will be able to flash different partitions without the need of a PC. The only thing is, while a ASOP rom will have the flash_image command (and file called flash_image) a ROM like the one I am on (or even a stock rom) won't. So I need the file... The link I posted in the op has a flash_image file at the bottom, but I don't know if it works for thunderbolt since it is in a g2 forum...
Actually, I was not asking that. I know how to make them and all. Do you see my low post count? It is because I read and read and read. Thanks for the advise though.
While I am asking about flashing recovery, I was not asking about hwo to do it in fastboot - I was asking how to do it on the device itself. Without ROM Manager.
In fact, I already know how to do it on the device itself... I need to use the command flash_image recovery recovery.img... except I am missing flash_image on my current ROM... so does anyone know where a version of that file is that is compatible with our tbolts?
Click to expand...
Click to collapse
I dont look at post counts, they're deceiving anyways (and join dates).
Without rom manager? Who does it with that anyways (it's prone to issues)? You flash them in recovery. The commands you use to install something in recovery, if you wish to do it with adb in recovery instead of pressing the buttons are located here http://www.londatiga.net/it/how-to-create-android-update-zip-package/
And yes, you can flash stuff very well in fastboot as well, which is what it looks like you're trying to do by your command you listed. If you're not doing it in fastboot or recovery, you're just crazy and looking to screw something up. You can't do it elsewhere because it'll potentially break your phone.
When you named something recovery.img it makes it look like you're trying to flash a new version of recovery though and that is something you do in fastboot.
That file you wanted anyways, flash_image, just pull it out of another ROM. If it's not in there, then it's part of flashing a new recovery itself.
yareally said:
I dont look at post counts, they're deceiving anyways (and join dates).
Without rom manager? Who does it with that anyways (it's prone to issues)? You flash them in recovery. The commands you use to install something in recovery, if you wish to do it with adb in recovery instead of pressing the buttons are located here http://www.londatiga.net/it/how-to-create-android-update-zip-package/
And yes, you can flash stuff very well in fastboot as well, which is what it looks like you're trying to do by your command you listed. If you're not doing it in fastboot or recovery, you're just crazy and looking to screw something up. You can't do it elsewhere because it'll potentially break your phone.
When you named something recovery.img it makes it look like you're trying to flash a new version of recovery though and that is something you do in fastboot.
That file you wanted anyways, flash_image, just pull it out of another ROM. If it's not in there, then it's part of flashing a new recovery itself.
Click to expand...
Click to collapse
ROM Manager has its flaws. I can't flash boot.imgs in it, I can't flash custom recoverys (not cwm) in it, or any other partition I want....
I am not flashing in fastboot or recovery, or even using a PC. Call me crazy if you will but it is how I roll. The non-need of a computer is what I am after.
See this thread. What I am trying to do is something that can be done since day 1 with android..
http://forum.xda-developers.com/showthread.php?t=902493
http://www.clockworkmod.com/rommanager you can probably pull what you want out of the clockwork recovery image or rom manager.apk. Either mount the recovery image on linux or open up rom manager's apk with a zip program and pull it out.
EDIT: flash_image is in the rom_manager apk. Just get it out of that at the link above.
Having problems flashing CWM to Moto G 4.4 i get"ERROR Max Download size of 536870912 cannot load"
Can anyone help? Thanks
Marcusprit said:
Having problems flashing CWM to Moto G 4.4 i get"ERROR Max Download size of 536870912 cannot load"
Can anyone help? Thanks
Click to expand...
Click to collapse
You're either just going to have to use "fastboot boot recovery.img" (without quotes and where recovery.img is whatever the CWM file is named) instead of "fastboot flash recovery.img" or you will have to find a recovery.img that is small enough to actually flash. If you just use the boot method, this means you will have to reflash it every time you need something done with CWM.
es0tericcha0s said:
You're either just going to have to use "fastboot boot recovery.img" (without quotes and where recovery.img is whatever the CWM file is named) instead of "fastboot flash recovery.img" or you will have to find a recovery.img that is small enough to actually flash. If you just use the boot method, this means you will have to reflash it every time you need something done with CWM.
Click to expand...
Click to collapse
Hi thank you for your reply. I used fastboot boot recovery CWM6046-MotoG44.img but it cannot load recovery. I did read somewhere about sparse chunks in the US being 123 and 012 in the UK whatever that means. Is there anything else i can try?
I have unlocked the bootloader and rooted my phone, i really wanted to try some custom roms but without CWM its not possible
PS I am in the UK.
Marcusprit said:
Hi thank you for your reply. I used fastboot boot recovery CWM6046-MotoG44.img but it cannot load recovery. I did read somewhere about sparse chunks in the US being 123 and 012 in the UK whatever that means. Is there anything else i can try?
I have unlocked the bootloader and rooted my phone, i really wanted to try some custom roms but without CWM its not possible
PS I am in the UK.
Click to expand...
Click to collapse
Looks like you'll need the more updated version of CWM - 6.0.4.7 as that is built with Kit Kat sources and works with both 4.3 and 4.4 bootloaders. Or you can use the new TWRP 2.7.0. You can find links from here: http://forum.xda-developers.com/showthread.php?t=2608377
Hope this helps!
es0tericcha0s said:
Looks like you'll need the more updated version of CWM - 6.0.4.7 as that is built with Kit Kat sources and works with both 4.3 and 4.4 bootloaders. Or you can use the new TWRP 2.7.0. You can find links from here: http://forum.xda-developers.com/showthread.php?t=2608377
Hope this helps!
Click to expand...
Click to collapse
Thank you tried the updated versions but still won't load. I'm not sure what i'm doing wrong. I type in ADB DEVICES thats working fine then FASTBOOT DEVICES thats working too then i type in the recovery image but i get" ERROR CANNOT LOAD"
When i download the recovery image do i need to burn it onto a disk? I tried doing this but it says Disk image isn't valid.
Doesn't look like i'm going to be able to solve this problem.
Marcusprit said:
Thank you tried the updated versions but still won't load. I'm not sure what i'm doing wrong. I type in ADB DEVICES thats working fine then FASTBOOT DEVICES thats working too then i type in the recovery image but i get" ERROR CANNOT LOAD"
When i download the recovery image do i need to burn it onto a disk? I tried doing this but it says Disk image isn't valid.
Doesn't look like i'm going to be able to solve this problem.
Click to expand...
Click to collapse
Your device boots and is already rooted, right? If so, try to flash the updated img files with : https://play.google.com/store/apps/details?id=com.cgollner.flashify
recovery
Thank you I now have recovery
Marcusprit said:
Thank you I now have recovery
Click to expand...
Click to collapse
OK, so I was rolling along just fine...
Got Fastboot up and running, got myself an unlocked bootloader, got myself the latest TWRP image, and no matter WHAT I DO, I can not get TWRP to flash to my device, and it is driving me absolutely INSANE. Below is what i am getting from command prompt. Any help is GREATLY appreciated.
Code:
C:\Users\saltam\Downloads\TWRP>fastboot flash recovery recovery.img
sending 'recovery' (13186 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.000s
I am pulling what little hair I have out over here, and I am no beginner when it comes to this stuff. Please help if you can.
Only a couple of things I can think, which I'm sure you've already done. Have you re-downloaded the image file and you have renamed it recovery.img?
Edit, is your bootloader unlocked?
Sent from my Nexus 5 using XDA Free mobile app
Boot loader is unlocked, tried everything besides a different computer. Tried different cord, different USB port, everything. It's like once I unlocked the boot loader the tablet stopped communicating with fast boot. Anything I try to do hangs until I hit reboot fast boot then it fails. Irritating the hell out of me...
have you tired using the wugs Nexus root toolkit? http://forum.xda-developers.com/nexus-9/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2945451
I was having some trouble TWRP installing as well., and it was able to install TWRP just fine
Close any other running programs, especially Chrome. Then if still not doing it, install CWM Recovery instead, and if you still want TWRP flash it from CWM Recovery.
My N5 won't let me have TWRP, so if you just want the functions of a recovery, try a different one.
blakeslee14 said:
have you tired using the wugs Nexus root toolkit? http://forum.xda-developers.com/nexus-9/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2945451
I was having some trouble TWRP installing as well., and it was able to install TWRP just fine
Click to expand...
Click to collapse
Tried Wug's, and got the same result when I got to it sending the fast boot commands. Prompt just hangs until I select reboot fast boot.
craig.buckie said:
Close any other running programs, especially Chrome. Then if still not doing it, install CWM Recovery instead, and if you still want TWRP flash it from CWM Recovery.
My N5 won't let me have TWRP, so if you just want the functions of a recovery, try a different one.
Click to expand...
Click to collapse
I'm at my end right now, because I want to remove all this dumb Google bloatware so badly. Was thinking about trying to flash stock image, or relock and unlock boot loader again to see if that does anything, but I'm very nervous that those options might not work because of the fact that fast boot commands aren't working. Certainly don't want to end up with a $400 paperweight...
SwoRNLeaDejZ said:
Tried Wug's, and got the same result when I got to it sending the fast boot commands. Prompt just hangs until I select reboot fast boot.
I'm at my end right now, because I want to remove all this dumb Google bloatware so badly. Was thinking about trying to flash stock image, or relock and unlock boot loader again to see if that does anything, but I'm very nervous that those options might not work because of the fact that fast boot commands aren't working. Certainly don't want to end up with a $400 paperweight...
Click to expand...
Click to collapse
I assume you're on 5.0.1. Flash the boot or recovery image from the factory image in fastboot. See if that works. That might rule out a fastboot issue. If it flashed it won't do anything negative to your device
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
I assume you're on 5.0.1. Flash the boot or recovery image from the factory image in fastboot. See if that works. That might rule out a fastboot issue. If it flashed it won't do anything negative to your device
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Going to give this a shot now..
Worth mentioning, I ran an OEM Lock command, and successfully relocked the bootloader, so it appears fastboot is at least partially working. Going to attempt to flash the bootloader in the image from Google, because that is all there is. Just bootloader and image, no recovery image. I will post results here. I don't know why fastboot commands are broken after unlocking bootloader, but there is one thing that seems odd to me:
When I run fastboot devices, it returns the following (has been like this from the beginning):
Code:
C:\Users\saltam\Downloads\TWRP>fastboot devices
???????????? fastboot
Thoughts?
Something's not right. Do you have the newest fastboot?
di11igaf said:
Something's not right. Do you have the newest fastboot?
Click to expand...
Click to collapse
Yes, recently updated it via the minimalist fastboot/adb tool. This is REALLY irritating the hell out of me at this point... Been trying to get recovery on this stupid tablet all damn day...
I am starting to think this is a read/write error.. It is getting the error whenever it tries to write to the tablet... (sending boot.img results in the error every time)... Anyone know of fastboot/adb commands to check/fix read and write errors
**EDIT**
So, much to my chagrin, it appears to just be my computer... Tried on a different laptop, and was able to get it rooted.. For some odd reason though, I don't think TWRP is installing correctly ??
I am going to try and boot into recovery, but every time i try to flash it with fastboot flash recovery recovery.img it says it was successful, but a boot into recovery mode comes up as the dreaded NO COMMAND laying down Android icon. Super frustrating..
**EDIT 2**
So after much trying of different methods, I was able to successfully flash TWRP with Flashify. Not sure why I couldn't do it manually through fastboot but I'm good now. Thanks for all the replies and suggestions. This can be marked as closed or solved. Thanks!
SwoRNLeaDejZ said:
I am starting to think this is a read/write error.. It is getting the error whenever it tries to write to the tablet... (sending boot.img results in the error every time)... Anyone know of fastboot/adb commands to check/fix read and write errors
**EDIT**
So, much to my chagrin, it appears to just be my computer... Tried on a different laptop, and was able to get it rooted.. For some odd reason though, I don't think TWRP is installing correctly ??
I am going to try and boot into recovery, but every time i try to flash it with fastboot flash recovery recovery.img it says it was successful, but a boot into recovery mode comes up as the dreaded NO COMMAND laying down Android icon. Super frustrating..
**EDIT 2**
So after much trying of different methods, I was able to successfully flash TWRP with Flashify. Not sure why I couldn't do it manually through fastboot but I'm good now. Thanks for all the replies and suggestions. This can be marked as closed or solved. Thanks!
Click to expand...
Click to collapse
To your first edit, twrp is probably working correctly. Lollipop forces the stock recovery. There are two files, one in /system and one in /system/bin that force the stock recovery upon boot. You can remove those files or first
fastboot boot twrp.img
Then flash supersu in twrp, then
fastboot flash recovery twrp.img
Sent from my Nexus 9 using XDA Free mobile app
Got the right USB driver
Dirty Unicorns /Uber / Beanstalk Yuga adm.
xtcdk said:
Got the right USB driver
Dirty Unicorns /Uber / Beanstalk Yuga adm.
Click to expand...
Click to collapse
Kind of mystified with your response... Had nothing to do with the USB drivers. Found out afterward that the problem was the security that my company had setup on my laptop (was using my company thinkpad). Switching laptops solved the problem.
I installed SultanXDA's CM13 ROM and I am using TWRP (not the 3 version). I haven't installed SuperSU, so it means that I am not rooted, too... But...
I wanted to flash this camera: http://forum.xda-developers.com/one...t-oxygenos-3-0-1-beta-camera-cm-aosp-t3386799
The problem is that when I get to recovery mode in order to install the zip file, I see all kinds of folders, but not my "normal" ones... I am using my SD card as internal space...
I read somewhere that I have to update to new TWRP 3 in order to overcome this...
So, does it have to do with the version of twrp and if so, how can I update it without being root and without being able for the current TWRP to read the zip files that I will "feed" it?
Maybe my only method is through adb?
Flashing through adb will erase anything else other than changing the TWRP version?
Thanks in advance guys!
dimxr said:
Maybe my only method is through adb?
Flashing through adb will erase anything else other than changing the TWRP version?
Thanks in advance guys!
Click to expand...
Click to collapse
If your Bootloader is unlocked try Fastboot.
Reboot OPX into Fastboot Mode. (Power + Volume Up i think or trough TWRP or CM)
Connect it to your PC
On PC: Download the latest TWRP img File
Start CMD in same Folder as the downloaded File is.
Type: 'Fastboot devices' to make sure your OPX connected properly
Typ: 'Fastboot Flash Recovery *DownloadedTWRP*.img'
Flashing new TWRP only overwrites current TWRP and doesn't erease anything else
OverBit said:
On PC: Download the latest TWRP img File
Click to expand...
Click to collapse
Can you download it?
I can't seem to be able to start a download no matter which browser I use...
dimxr said:
Can you download it?
I can't seem to be able to start a download no matter which browser I use...
Click to expand...
Click to collapse
Without any problem.
Maybe you be able to download it when i attach it.
Was to big to upload it as img, so I renamed it to .apk,
So don't forget to rename it to .img
Great! So, the procedure begins!
EDIT: I encountered numerous problems in installing CM13 on Z5C, but a solution is already written here, and it's better than what I could write (because me no good english
Also the problem as explained below is determined only by a wrong environment, in which I blindly flashed uncompatible SW.
Hello, as in title I cannot get "fastboot flash recovery recovery.img" command to work.
This is what terminal gives me:
C:\adb>fastboot flash recovery TWRP-3.0.0.0-suzuran-v2.img
sending 'recovery' (21760 KB)...
OKAY [ 0.756s]
writing 'recovery'...
OKAY [ 0.179s]
finished. total time: 0.943s
Click to expand...
Click to collapse
Despite the lack of errors the phone is completely unaffected, there's no way I can enter recovery but flashing with "fastboot flash boot", which is improper and so OS loading is broken (it boots only the recovery).
EDIT: I then discovered that's normal behaviour, and that I wasn't able to boot in recovery normally because I flashed Marshmallow SW on Lollipop
I wasn't able to find a solution on the internet, I hope someone can help me.
Z5C E5823, Win7, adb and fastboot are OK
davidbevi said:
Hello, as in title I cannot get "fastboot flash recovery recovery.img" command to work.
This is what terminal gives me:
I wasn't able to find a solution on the internet, I hope someone can help me.
Z5C E5823, Win7, adb and fastboot are OK
Click to expand...
Click to collapse
There's nothing wrong here? Looks successful to me.
civicsr2cool said:
There's nothing wrong here? Looks successful to me.
Click to expand...
Click to collapse
My bad, I'll explain better; terminal is OK, but phone is unaffected by the command. I found that the only way to enter the recovery was flashing it in boot (found by error), in this way the phone finds it, but it can't boot properly anymore.
davidbevi said:
My bad, I'll explain better; terminal is OK, but phone is unaffected by the command. I found that the only way to enter the recovery was flashing it in boot (found by error), in this way the phone finds it, but it can't boot properly anymore.
Click to expand...
Click to collapse
You might want to re-download the TWRP and flash it again. You might be that one in a million person who have a corrupted downloaded file.
davidbevi said:
My bad, I'll explain better; terminal is OK, but phone is unaffected by the command. I found that the only way to enter the recovery was flashing it in boot (found by error), in this way the phone finds it, but it can't boot properly anymore.
Click to expand...
Click to collapse
Download twrp 3.0.2, you're using the wrong one. Also if you use flash tool you can hotboot the recovery to get into it if you don't have a custom kernel that will allow you to get into recovery.
firdyRAY said:
[...] corrupted downloaded file.
Click to expand...
Click to collapse
I doubt because I tried 3 different packages, and every single one works, just I have to flash it unproperly. I would follow your advice anyway if it wasn't for:
civicsr2cool said:
Download twrp 3.0.2 [...]
Click to expand...
Click to collapse
This is the only thing I found googling, can you please give me a link or more info?
I managed to get TWRP v2.8.7.0 on my phone.
I'd like to write a solution on the original post, so those who have my problem also have my solution, but I have to know better:
1) the TWRP I installed comes from a zip containing boot.img and recovery.img
2) flashing both ("fastboot flash boot boot.img" & "fastboot flash recovery recovery.img") did the job
My guess is that you need a piece of code that IS the recovery and a piece of code that MAKES the recovery ACCESSIBLE. If this is the case I don't get how I was able to boot into recovery when flashed on boot. I am confused!
davidbevi said:
I managed to get TWRP v2.8.7.0 on my phone.
I'd like to write a solution on the original post, so those who have my problem also have my solution, but I have to know better:
1) the TWRP I installed comes from a zip containing boot.img and recovery.img
2) flashing both ("fastboot flash boot boot.img" & "fastboot flash recovery recovery.img") did the job
My guess is that you need a piece of code that IS the recovery and a piece of code that MAKES the recovery ACCESSIBLE. If this is the case I don't get how I was able to boot into recovery when flashed on boot. I am confused!
Click to expand...
Click to collapse
twrp 3.0.2
https://www.androidfilehost.com/?fid=24499762636001943
twrp 3.0 and up is for marshmallow, anything below is lollipop. the boot.img is your kernel, like i said before you need to have a custom kernel to access twrp or hotboot it every time you need it. if you're running marshmallow with a lollipop kernel idk how well that will work out for you in the long run. to understand why you need the boot.img kernel i suggest looking up sony ric.
civicsr2cool said:
twrp 3.0.2
https://www.androidfilehost.com/?fid=24499762636001943
twrp 3.0 and up is for marshmallow, anything below is lollipop. the boot.img is your kernel, like i said before you need to have a custom kernel to access twrp or hotboot it every time you need it. if you're running marshmallow with a lollipop kernel idk how well that will work out for you in the long run. to understand why you need the boot.img kernel i suggest looking up sony ric.
Click to expand...
Click to collapse
Thanks a lot, I was able to determine that my problem was caused by a ROM that is too old for what I was trying.
I was trying to install CM13 following CTXz's guide, but I had no idea I had to start from Marshmallow (and it's not written).
davidbevi said:
Thanks a lot, I was able to determine that my problem was caused by a ROM that is too old for what I was trying.
I was trying to install CM13 following CTXz's guide, but I had no idea I had to start from Marshmallow (and it's not written).
Click to expand...
Click to collapse
its in the thread somewhere towards the middle because i tested lollipop to cm13 and got nowhere fast as well.
edit:it says in op that required firmware is 6.0 fwiw