Related
Guys, I need some help. I rooted with Androot and flashed PSGroove with ROM Manager. Now I need to flash the stock recovery back.
I followed a guide (cant post link) but I get "error: cannot load recovery.img", I don't want to touch the ROM because it's stock.
Anyway, where can I find stock FRF91 recovery.img?
Also, there is no install-recovery.sh in system/etc/ and I didn't delete it, where can I get it too?
Thanks.
Download a stock FRF91 image, extract the ZIP, you'll see recovery.img.
I downloaded around 3 stock FRF91's and none included recovery.img
I need it too...Where can I find this stock recovery.img ?
thx for help
i have massive problems restoring stock recovery.img on frf91 nothing works ...
i re enabled install-recovery.sh started it ... did not work ---
downloaded the stock recovery.img
/mnt/sdcard $ md5sum recovery.img
md5sum recovery.img
336f05884ade218f2a0932df9bd770a2 recovery.img
flash_image it .. did not worked ... any help ?
Restore the two files you deleted when you rooted:
/system/etc/install-recovery.sh
/system/recovery-from-boot.p
Sent from my Nexus One using XDA App
did this already ... invoked the install-recovery.sh manualy ... will post output later ... STILL NO OTA updates :/
So this one isn't working when I flash it with TWRP ( http://forum.xda-developers.com/desire-510/development/virgin-sprint-htc-desire-510-stock-t2961521 ). I wasn't successful looking for one so I was hoping I could find some help here. After I flash back to stock I want to flash this kernel ( http://forum.xda-developers.com/des...sprintboost-modded-desire-510-kernel-t2969979 ).
Correct me if I'm wrong but I feel as though this combination is better than just having CM11. Less hardware issues is a huge plus for me.
Sent from my HTC Desire 510 using XDA Free mobile app
meeniemuffin said:
So this one isn't working when I flash it with TWRP ( http://forum.xda-developers.com/desire-510/development/virgin-sprint-htc-desire-510-stock-t2961521 ). I wasn't successful looking for one so I was hoping I could find some help here. After I flash back to stock I want to flash this kernel ( http://forum.xda-developers.com/des...sprintboost-modded-desire-510-kernel-t2969979 ).
Correct me if I'm wrong but I feel as though this combination is better than just having CM11. Less hardware issues is a huge plus for me.
Sent from my HTC Desire 510 using XDA Free mobile app
Click to expand...
Click to collapse
Flash the kernel then restore.
Also, you don't flash that zip of stock. Unzip on your computer and drop the files in the TWRP/BACKUPS/FAJBLAHBLAHBLAH folder and restore in TWRP. You may not have to flash the kernel first because the boot.img should be backed up.
Did now know all this. Thanks for the help, I'm going to get started on this now that I got off work. Also, not obligatory, but can you explain how that works?
Sent from my HTC Desire 510 using XDA Free mobile app
dipspit said:
Flash the kernel then restore.
Also, you don't flash that zip of stock. Unzip on your computer and drop the files in the TWRP/BACKUPS/FAJBLAHBLAHBLAH folder and restore in TWRP. You may not have to flash the kernel first because the boot.img should be backed up.
Click to expand...
Click to collapse
Just letting you know that perhaps we are not on the same page here. Im coming from Cyanogenmod 11, is flashing the Kernel the only thing I have to do in order to back to Boost Mobile stock? ROM and everything come withing the Kernel?
meeniemuffin said:
Did now know all this. Thanks for the help, I'm going to get started on this now that I got off work. Also, not obligatory, but can you explain how that works?
Sent from my HTC Desire 510 using XDA Free mobile app
Click to expand...
Click to collapse
Download the zip and the kernel img
Unzip in Windows/Linux
cd to folder where the folder you unzipped is located
In a file explorer on your phone navigate to wherever you make TWRP backups to (ie. /sdcard or /sdcard2 )
In /sdcard or /sdcard2 there will be a folder named TWRP, tap it
In TWRP there will be a folder named BACKUPS, tap it
In BACKUPS there will be a folder with your devices serial number (eg. FA4AJSR24392), tap it, this is where you need to place the folder from the zip
Open cmd/terminal and move the folder to the device by executing
Code:
adb push [B][COLOR="DarkRed"]"2014-12-01--07-42-35 KOT49H release-keys"[/COLOR][/B] "/sdcard/TWRP/BACKUPS/[B]<device serial #>[/B]/[B][COLOR="DarkRed"]2014-12-01--07-42-35 KOT49H release-keys[/COLOR][/B]/"
Now move the kernel over by executing
Code:
adb push HTC-Desire-510-Modded-Kernel-v1.img /sdcard/HTC-Desire-510-Modded-Kernel-v1.img
Reboot to bootloader by executing
Code:
adb reboot recovery
In TWRP tap Install and find HTC-Desire-510-Modded-Kernel-v1.img
Tap it and swipe to flash/install
Afterwards back out to the main menu
Now tap Restore and restore 2014-12-01--07-42-35 KOT49H release-keys
I thought rb had backed up the boot.img along with system but that backup is only a system backup so you will have to flash the kernel first and then restore the stock.
dipspit said:
Download the zip and the kernel img
Unzip in Windows/Linux
cd to folder where the folder you unzipped is located
In a file explorer on your phone navigate to wherever you make TWRP backups to (ie. /sdcard or /sdcard2 )
In /sdcard or /sdcard2 there will be a folder named TWRP, tap it
In TWRP there will be a folder named BACKUPS, tap it
In BACKUPS there will be a folder with your devices serial number (eg. FA4AJSR24392), tap it, this is where you need to place the folder from the zip
Open cmd/terminal and move the folder to the device by executing
Code:
adb push [B][COLOR="DarkRed"]"2014-12-01--07-42-35 KOT49H release-keys"[/COLOR][/B] "/sdcard/TWRP/BACKUPS/[B]<device serial #>[/B]/[B][COLOR="DarkRed"]2014-12-01--07-42-35 KOT49H release-keys[/COLOR][/B]/"
Now move the kernel over by executing
Code:
adb push HTC-Desire-510-Modded-Kernel-v1.img /sdcard/HTC-Desire-510-Modded-Kernel-v1.img
Reboot to bootloader by executing
Code:
adb reboot recovery
In TWRP tap Install and find HTC-Desire-510-Modded-Kernel-v1.img
Tap it and swipe to flash/install
Afterwards back out to the main menu
Now tap Restore and restore 2014-12-01--07-42-35 KOT49H release-keys
I thought rb had backed up the boot.img along with system but that backup is only a system backup so you will have to flash the kernel first and then restore the stock.
Click to expand...
Click to collapse
Im trying what you suggested and TWRP isnt recognizing that the image file is there. Any ideas?
Never mind. I flashed the kernel using flashify and then I rebooted into TWRP and restored to stock. Thanks for the help.
Sent from my 0PCV1 using XDA Free mobile app
I know how to fastboot flash .img files and understand it includes the radio and kernel components. I'm rooted and have TWRP recovery. But which .img file contains the radio and which the kernel? I ask because I'll be going from the latest T-Mo rom (LYZ28J) to Project Fi having just received my sim. If I flash just the system.img from LYV48E (Fi rom) will I have the correct kernel and radio or will I have to flash boot.img also or something else? Since kernels and radios can be flashed separately I'm just not sure where everything comes from. I would appreciate some clarity.
Groid said:
I know how to fastboot flash .img files and understand it includes the radio and kernel components. I'm rooted and have TWRP recovery. But which .img file contains the radio and which the kernel? I ask because I'll be going from the latest T-Mo rom (LYZ28J) to Project Fi having just received my sim. If I flash just the system.img from LYV48E (Fi rom) will I have the correct kernel and radio or will I have to flash boot.img also or something else? Since kernels and radios can be flashed separately I'm just not sure where everything comes from. I would appreciate some clarity.
Click to expand...
Click to collapse
have you ever unzipped a factory.img .tar file to see what files it contains?
Groid said:
I know how to fastboot flash .img files and understand it includes the radio and kernel components. I'm rooted and have TWRP recovery. But which .img file contains the radio and which the kernel? I ask because I'll be going from the latest T-Mo rom (LYZ28J) to Project Fi having just received my sim. If I flash just the system.img from LYV48E (Fi rom) will I have the correct kernel and radio or will I have to flash boot.img also or something else? Since kernels and radios can be flashed separately I'm just not sure where everything comes from. I would appreciate some clarity.
Click to expand...
Click to collapse
simms22 said:
have you ever unzipped a factory.img .tar file to see what files it contains?
Click to expand...
Click to collapse
If I were a betting man, I'd be backing the horse called "Wish I'd done that before posting"
Tiptonian said:
If I were a betting man, I'd be backing the horse called "Wish I'd done that before posting"
Click to expand...
Click to collapse
Hahaa. Unzip and you shall receive. LMAO
simms22 said:
have you ever unzipped a factory.img .tar file to see what files it contains?
Click to expand...
Click to collapse
Not sure what you mean by this. I have the system, boot, recovery, and userdata .img files. I don't know which one has the kernel or which one has the radio. You imply I can unzip, for example, system.img to see what files are there, but I cannot unzip it or any of the .img files. My main question still is unanswered which is which .img files do I need to (m)fastboot flash to insure I have the correct (stock) kernel and radio for the Project Fi rom? I may just flash them all, flash TWRP, re-root and start clean, but I wanted to consider the option of keeping data. Any helpful answers?
Tiptonian said:
If I were a betting man, I'd be backing the horse called "Wish I'd done that before posting"
Click to expand...
Click to collapse
prdog1 said:
Hahaa. Unzip and you shall receive. LMAO
Click to expand...
Click to collapse
So glad my post was such a source of amusement for you. Sorry I didn't make it clear I know how download factory images, unzip the .tgz file to get the .tar file. Unzip the .tar file to get to the .zip file. Unzip the .zip file to get the boot, recovery, system, and userdata .img files. But no one actually tried to answer my question.
Groid said:
So glad my post was such a source of amusement for you. Sorry I didn't make it clear I know how download factory images, unzip the .tgz file to get the .tar file. Unzip the .tar file to get to the .zip file. Unzip the .zip file to get the boot, recovery, system, and userdata .img files. But no one actually tried to answer my question.
Click to expand...
Click to collapse
kernel is boot.img, radio is radio.img
Thank you for your reply. I suspected boot.img is the kernel but wanted to make sure. I notice that the radio-shamu-. . .02.78.02.img and boot-shamu. . .71.10.img are in the shamu-lvy48e folder in the .tar file with the flash batch files. The enclosed .zip file has the system, boot, userdata, recovery, and cache .img files along with the text file specifying the bootloader (kernel) and baseband (radio). I now understand that the boot.img is the kernel which is the same version my current one in LYZ28J, so I need not flash it. The radio is different based on the android-info.txt file. So, the last piece of the puzzle for me is will I get the updated radio by flashing the system.img or must I separately flash the radio-shamu -. . .-02.78.02.img?
Groid said:
Thank you for your reply. I suspected boot.img is the kernel but wanted to make sure. I notice that the radio-shamu-. . .02.78.02.img and boot-shamu. . .71.10.img are in the shamu-lvy42e folder in the .tar file with the flash batch files. The enclosed .zip file has the system, boot, userdata, recovery, and cache .img files along with the text file specifying the bootloader (kernel) and baseband (radio). I now understand that the boot.img is the kernel which is the same version my current one in LYZ28J, so I need not flash it. The radio is different based on the android-info.txt file. So, the last piece of the puzzle for me is will I get the updated radio by flashing the system.img or must I separately flash the radio-shamu -. . .-02.78.02.img?
Click to expand...
Click to collapse
youll get the updated radio in the factory.img, but you can always flash the radio itsrlf via fastboot(fastboot flash radio radioname.img).
Groid said:
Thank you for your reply. I suspected boot.img is the kernel but wanted to make sure. I notice that the radio-shamu-. . .02.78.02.img and boot-shamu. . .71.10.img are in the shamu-lvy48e folder in the .tar file with the flash batch files. The enclosed .zip file has the system, boot, userdata, recovery, and cache .img files along with the text file specifying the bootloader (kernel) and baseband (radio). I now understand that the boot.img is the kernel which is the same version my current one in LYZ28J, so I need not flash it. The radio is different based on the android-info.txt file. So, the last piece of the puzzle for me is will I get the updated radio by flashing the system.img or must I separately flash the radio-shamu -. . .-02.78.02.img?
Click to expand...
Click to collapse
If have updated SDK will get everything in flash-all.bat. If not and have to do all separate they are all separate. Bootloader, radio, boot, system, cache, userdata. There is no radio in system.img. It is the radio. img. On first unzip get bootloader, radio, flash-all and the folder for the rest of the images. If want radio fastboot flash radio (radio.img).
Thank you for answering my question about whether or not the radio gets updated by flashing system.img. Unfortunately, I cannot get ADB to work properly. I initially seem to have it working with the ADB devices statement from the command prompt, it returns the serial #, but when I try to execute the batch file ADB seems to be disconnected. At least I have experience with (m)fastboot and will just flash the radio and system .imgs since the bootloader is the same. I'll keep TWRP recovery, format cache, update supersu for root and I should be good to go.
Groid said:
Thank you for answering my question about whether or not the radio gets updated by flashing system.img. Unfortunately, I cannot get ADB to work properly. I initially seem to have it working with the ADB devices statement from the command prompt, it returns the serial #, but when I try to execute the batch file ADB seems to be disconnected. At least I have experience with (m)fastboot and will just flash the radio and system .imgs since the bootloader is the same. I'll keep TWRP recovery, format cache, update supersu for root and I should be good to go.
Click to expand...
Click to collapse
well, adb doesnt work in the bootloader, and its only fastboot that can flash those files..
Thanks, I was responding to using adb to sideload with the flash(all).bat. Fastboot works fine for me so I don't really miss using adb commands.
Hello!
I looked for this, but can't seem to find a clear answer. The other thread on this is over 3,000 posts (can't look through all that).
I am currently on 6.0.1 with February 1 security update on rooted Nexus 6, stock, with TWRP recovery. I want to apply the latest security patches using NRT....How to?? What is my easiest method to doing this? Thanks in advance, cheers!
The easiest method is not to use NRT. Much as I'm a fan of it, having contributed to Wug several times, the manual method is simpler. Boot into bootloader, start a CMD session, flash system.img & boot.img, and radio.img if you want to be particularly careful, and reboot. Job done. No data loss, everything as normal apart from the new security patches.
If the above isn't familiar, you need to read these forums a lot more. Not trying to be funny - I had to before I had the balls to offer advice to others.
Would we have to flash SuperSU again to reroot?
iluvatrix said:
Would we have to flash SuperSU again to reroot?
Click to expand...
Click to collapse
yes
dahawthorne said:
. Boot into bootloader, start a CMD session, flash system.img & boot.img, and radio.img if you want to be particularly careful, and reboot. Job done. No data loss.......
Click to expand...
Click to collapse
.....with the newest twrp-recovery (v3.0.0.1) it is possible to flash the boot.img and system.img, directly from the internal memory.
so what we do is dl the factory image , extract the boot.img and system.img , drag over to phone internal memory, boot twrp 3.0.0.1 then flash?
"flash the boot.img and system.img, directly from the internal memory"
"boot twrp 3.0.0.1 then flash?"
I don't believe you can install an img file in TWRP, and I've never tried. If you extract everything from the factory ROM image, including the zip within the zip, you'll find boot.img, system.img & radio.img. Copy them across to your PC folder where ADB.exe & fastboot.exe live, open a CMD window, boot your phone into bootloader mode, attach via USB, and separately fastboot flash the 3 img files. Then install TWRP, and from there you can install SuperSU v2.70 if you want to root.
dahawthorne said:
"flash the boot.img and system.img, directly from the internal memory"
"boot twrp 3.0.0.1 then flash?"
I don't believe you can install an img file in TWRP, and I've never tried. If you extract everything from the factory ROM image, including the zip within the zip, you'll find boot.img, system.img & radio.img. Copy them across to your PC folder where ADB.exe & fastboot.exe live, open a CMD window, boot your phone into bootloader mode, attach via USB, and separately fastboot flash the 3 img files. Then install TWRP, and from there you can install SuperSU v2.70 if you want to root.
Click to expand...
Click to collapse
You can flash images in TWRP 3.0.0-1
Recovery, system and boot. My PC is down and that's how I flashed N preview. Works great
Sent from my Nexus 6 using XDA Free mobile app
iluvatrix said:
so what we do is dl the factory image , extract the boot.img and system.img , drag over to phone internal memory, boot twrp 3.0.0.1 then flash?
Click to expand...
Click to collapse
Yes ?
---------- Post added at 01:11 PM ---------- Previous post was at 01:06 PM ----------
dahawthorne said:
...
I don't believe you can install an img file in TWRP, and I've never tried...
Click to expand...
Click to collapse
Try and you will believe. ?
That's why we're here - to learn...
Thanks, people.
31ken31 said:
You can flash images in TWRP 3.0.0-1
Recovery, system and boot. My PC is down and that's how I flashed N preview. Works great
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Do we then have to re-root after going this method? Also, will everything be the way it was before flashing (no data loss, no settings loss, etc.)?
Shaundiesel said:
Do we then have to re-root after going this method? Also, will everything be the way it was before flashing (no data loss, no settings loss, etc.)?
Click to expand...
Click to collapse
None and yes flash appropriate su to restore root
Sent from my Nexus 6 using XDA Free mobile app
http://forum.xda-developers.com/showpost.php?p=65136208&postcount=13
Works like a charm Every time.
Hi all, I want to clean install stock rom via fastboot. I used to do this on my oneplus one a while back. I think that I need to install img files to five partitions (boot.img, recovery.img, system.img, userdata.img and cache.img). Are there any other files that need to installed (eg bin or mbn files)?
I think I should be able to get the img files by unzipping the stock rom files. Has anyone tried to get the img files from unzipped stock rom and install via fastboot?
Any help is greatly appreciated.
Thanks
Don't know exactly, but also interested to learn about this!
OnePlus does not provide fastboot flashable roms, the only way to get them would be to update uusing the recovery first and extracting the .img files afterwards, but then you don't need them anymore since you are already upgraded.
Jo_Jo_2000 said:
OnePlus does not provide fastboot flashable roms, the only way to get them would be to update uusing the recovery first and extracting the .img files afterwards, but then you don't need them anymore since you are already upgraded.
Click to expand...
Click to collapse
The system.new.dat format is not unique to oneplus, but the standard for flashable android zips since version 6 (aka marshmellow). The system.new.dat, system.patch.dat and system.transfare.list are build from system.img while building a rom (aka compile rom from source). This process is NOT unidirectional; you can easily revert it. I'm on linux, so you have to google, how this is accomblished on win or darwin. For linux users:
https://github.com/xpirt/sdat2img