[Q] Flashing Mods - General Questions and Answers

Ok yes I am a noob at this and after much searching I have not found an answer to my question so I decided to make a thread.
Can anyone explain to me the process of flashing mods to your ROM? More specifically do you have to wipe data and everything to flash a mod to your ROM or can you just flash it on top of your ROM and keep it moving ?

To flash a mod usually you download a file in. Zip form. You then flash it in recovery the same way you flash a rom. (Install zip) make sure you know where the file is external or internal. Wiping anything should not be necessary unless the dev specifies. And you flash it at anytime after the rom has been installed. Check versions and make sure its compatible. Hope this helps
Sent from my GT-P7510 using xda premium

roughneckboren said:
To flash a mod usually you download a file in. Zip form. You then flash it in recovery the same way you flash a rom. (Install zip) make sure you know where the file is external or internal. Wiping anything should not be necessary unless the dev specifies.
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
Thank you so much ! I have been searching for an answer for weeks now.

No problem man.
Sent from my GT-P7510 using xda premium

Beast to wipe cache and Dalvik immediately before flashing the zip.
But, most important (other than reading the flash instructions) -- Nandroid BACKUP -- with CWM Recovery prior to flash so you can restore your ROM if you don't like, have issues etc with the mod just flashed.
Sent from my GT-I9100 using xda premium

Thanks
Sent from my PC36100 using XDA

UpInTheAir said:
Beast to wipe cache and Dalvik immediately before flashing the zip.
But, most important (other than reading the flash instructions) -- Nandroid BACKUP -- with CWM Recovery prior to flash so you can restore your ROM if you don't like, have issues etc with the mod just flashed.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
U don't need to wipe data or cache if ur just flashing a mod. Those are only needed if ur flashing a rom

QuantumFoam said:
U don't need to wipe data or cache if ur just flashing a mod. Those are only needed if ur flashing a rom
Click to expand...
Click to collapse
Sorry, you are incorrect. Flashing certain mods and apps you should most definitely.
This guy explains it simply, and better than I could put it:
http://androidforums.com/4287822-post4.html
Sent from my GT-P6810 using XDA Premium HD app

UpInTheAir said:
Sorry, you are incorrect. Flashing certain mods and apps you should most definitely.
This guy explains it simply, and better than I could put it:
http://androidforums.com/4287822-post4.html
Sent from my GT-P6810 using XDA Premium HD app
Click to expand...
Click to collapse
I stand corrected

Recovery
Most mods (if not all) will require root access and a custom recovery tool like CWM and 4EXT. To get the recovery tool the phone will need S-Off mode enabled (Security Off). If you are on 2.2, S-Off wasn;t around then so you shouldn't have that problem, but startgin with 2.3 it was introduced, so you will need to get S-Off in order to get the recovery tool installed.
Getting into Recovery mode is another thing that depends on your phone. My Samsung uses Power + Volup and Vol Down togheter, then Vol Up plus Vol Down after it turns on forseverl aseconds. I have an HTC that is the same, but just with Vol down (no Vol up required). Of course to do anything there you need the S-Off plus root plus custom recovery tool.
You can also get a USB driver and adb (plus dll) toolkit to access the phone via yoru USB cable (this requires turning on USB debugging under phone settings). From there you can get into recovery by issuing commands in DOS.
> adb reboot bootloader
You can even flash some img files (mods) from the command line also ...
> fastboot flash radio radio.img
and then reboot the phone to normal
> fastboot reboot

Related

Help Please!!!

Alright, I rooted my Nexus S 4G this guide. My phone was running 2.3.5 but I figured that these steps in Terminal wouldn't really change. When I flashed the "recovery-clockwork-3.0.0.5-crespo.img" it didn't install properly (I assume because it was out of date/wrong version) Anyway, I flashed this instead with no problems.
In my euphoria over solving my clockwork problem, I forgot to flash the "su-2.3.6.1-ef-signed.zip" and flashed the current version of MIUI. I am now stuck in a bootloop and I cannot enter recovery by using power+volume. I cannot turn the phone off. I can load the bootloader screen using Terminal while I plug it into my computer, but I don't know what to flash to fix the phone, and start over/end up with a Nexus running MIUI.
i dont know much about macs but you can flash the img files through fastboot.
imgs files are here
thank buglesspete
chewbz said:
i dont know much about macs but you can flash the img files through fastboot.
imgs files are here
thank buglesspete
Click to expand...
Click to collapse
I can handle the mac part if you can show me which files to flash in which order to make my phone work again.
Okay this will take your phone back to stock. Download the grj22 image files. When you open it up it should have like 4 or 5 img files. After that open up cmd and type in the commands buglesspete has in his first post. It should be under "return to stock" or sometime like that.
Sent from my Nexus S 4G using XDA App
XikkeN said:
Alright, I rooted my Nexus S 4G this guide. My phone was running 2.3.5 but I figured that these steps in Terminal wouldn't really change. When I flashed the "recovery-clockwork-3.0.0.5-crespo.img" it didn't install properly (I assume because it was out of date/wrong version) Anyway, I flashed this instead with no problems.
In my euphoria over solving my clockwork problem, I forgot to flash the "su-2.3.6.1-ef-signed.zip" and flashed the current version of MIUI. I am now stuck in a bootloop and I cannot enter recovery by using power+volume. I cannot turn the phone off. I can load the bootloader screen using Terminal while I plug it into my computer, but I don't know what to flash to fix the phone, and start over/end up with a Nexus running MIUI.
Click to expand...
Click to collapse
Just a general hint... if oyu own a Nexus S 4G, Crespo isn't the right codename to look for.. it's crespo4g. Get the cwm recovery from here and flash the 4G version via "fastboot flash recovery <recoveryname>.img": http://forum.xda-developers.com/showthread.php?t=988686
rentaric said:
Just a general hint... if oyu own a Nexus S 4G, Crespo isn't the right codename to look for.. it's crespo4g. Get the cwm recovery from here and flash the 4G version via "fastboot flash recovery <recoveryname>.img": http://forum.xda-developers.com/showthread.php?t=988686
Click to expand...
Click to collapse
I know. I linked to that thread in my first post. What step am I skipping to run MIUI without a bootloop?
XikkeN said:
I know. I linked to that thread in my first post. What step am I skipping to run MIUI without a bootloop?
Click to expand...
Click to collapse
I have no experience with the 4G version of this phone but I can tell your that bootloops are usually caused by failing permissions (fix permissions in cwm rec) or missing wipes before isntalling the actual rom.
So I'd go back to start, flash the 4g recovery, wipe everything (including "mount and storage"'s /boot and then flash MIUI for 4g from here afterwards.
Basically, that MIUI (and most other custom roms) includes superuser.zip aka root. No need to root the devices before, all you need is an unlocked bootloader.
rentaric said:
I have no experience with the 4G version of this phone but I can tell your that bootloops are usually caused by failing permissions (fix permissions in cwm rec) or missing wipes before isntalling the actual rom.
So I'd go back to start, flash the 4g recovery, wipe everything (including "mount and storage"'s /boot and then flash MIUI for 4g from here afterwards.
Basically, that MIUI (and most other custom roms) includes superuser.zip aka root. No need to root the devices before, all you need is an unlocked bootloader.
Click to expand...
Click to collapse
What he said, I always wipe 3x everything just to make sure it is a clean install. And some people will also suggest to let the rom boot up normally before flashing a different kernel.
Sent from my Nexus S 4G using XDA App
chewbz said:
What he said, I always wipe 3x everything just to make sure it is a clean install. And some people will also suggest to let the rom boot up normally before flashing a different kernel.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
wiping 3 times is senseless! and the kernel should be flashed right after the rom install!
oh and wiping the dalvik cache and chache after a rom-update is also senseless! the updater-script do this automatic!
Sent from my Nexus S using XDA Premium App
Borky_16 said:
wiping 3 times is senseless! and the kernel should be flashed right after the rom install!
oh and wiping the dalvik cache and chache after a rom-update is also senseless! the updater-script do this automatic!
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
your assuming that the devs took the time to make sure to include that

Error Formatting System

Ok I am new to this phone and have done a lot of reading and have already flashed 3 roms on my phone and I set up the Flash Clockworkmod Recovery the real one and not the rom manager version. For some reason I now get a Error when trying to format system to flash another Rom and when I go to wipe dalvik cache it does not even let me go into to wipe that is there something I'm missing I have not see this problem with no one else.
Are you shouting down your phone and turning it back on holding power+volume down. Don't use rom manager to reboot to recovery it may be taking you to the fake cwm on your memory card.
Sent from my LG-P999 using xda premium
Perhaps try re flashing cwm with nvflash
Sent from my Galaxy Nexus using xda premium
It's weird the only way I'm able to flash a rom is when I go into rom manager and I go to backup rom through there.
It sounds like the real recovery didn't flash. Make sure you install the apx drivers correctly and check in device manager that your pc sees the phone.
Sent from my LG-P999 using xda premium
http://www.tmonews.com/2011/12/t-mobile-restarts-gingerbread-rollout-for-t-mobile-g2x/
Follow this topic you might have installed an older version I believe the first few we had did that. Make sure you shut down and use (power+volume down) to get to cement it is much safer.
Also are you try the factor reset in cwm or trying to do the advanced- format system. The advanced- format system requires you to first mount the system to do so.
Sent from my LG-P999 using xda premium

Horrible clarifying question

Ok everyone. Horrible question I know but here goes. I want to be right so please excuse a question I am sure has been asked many many times.
Situational info:
HTC one s s4 boot loader 1.06
No regular PC access.
Extensive knowledge and experience rooting and flashing G1 and G2X
Goal: unlock boot loader and open root access to enable flashing of roms via recovery while remaining PC independent
Steps I plan to execute:
1) unlock bootloader on htcdev site
2)grant root access following instructions(or all in one tool - your input here is appreciated)
3)instal CWM
4)download rom and kernel of choice
5) boot into boot loader, enter recovery, wipe, flash, boot
If I have any of this wrong please advise.
Again I apologize for the redundancy of this thread. Mods please delete after my process is verified to keep board clean. I only have one crack at this (PC access extremely limited) and I want to get it right.
Sent from my HTC VLE_U using xda app-developers app
Looks correct. First install HTC drivers & HTC Sync software (in order to unlock bootloader, I believe HTCdev site will instruct this).
I recommend (as well as many others, I believe) TWRP over CWM. ESPECIALLY if you do not have computer access. The 1S does not have S-OFF, which makes it very hard for us to flash kernels & radios. Well, not hard, but you need a PC if using CWM. Using TWRP, you can usually flash these things from your device. So definitely use TWRP for your situation.
You can't root without a PC. It's impossible. You are required to get a token that you can only get from a command prompt on the computer. Sorry, but you're out of luck. But when/if you get a PC the steps you wrote were mostly right
1) Correct
2) FLASH RECOVERY (use TWRP, CWM is not good on this device)
3) Then root by flashing a SuperSU zip in RECOVERY (that's why #2 and #2 are switched)
4) Yep
5) Always always always BACKUP YOUR ROM. Then wipe system, data, cache, and dalvik cache. then flash the ROM. If you have extra time you should fastboot your kernel if your hboot is below 1.13 (meaning 1.13 is NOT able to flash the kernel.)
Hope I helped. If I did press thanks
OP did mention that he will have limited PC access to perform the unlock process, so he will be able to do it initially.
Here's the link for TWRP: http://forum.xda-developers.com/showthread.php?t=1677670 (make sure to use this one, the other link in the forums is for the S3 processor)
Ok so I can flash recovery as soon as I unlock boot loader and use twrp check.
The supersu, that's just a zip to flash in recovery to grant root access?
What is fasbooting kernel?
Thanks guys, appreciate the help. Will be performing this within the next two hours. Just trying to be ready so it goes off smooth. Once I get this done I need to do my friend's G2(condition for PC time lol)
Sent from my HTC VLE_U using xda app-developers app
TWRP is a recovery. You will use that instead of CWM, not in addition to.
If you're going to flash a custom rom then you don't have to worry about rooting first. The rom will be rooted already.
Fastbooting kernel is a method of using a pc + command prompt to flash the kernel on your phone. Because HTC hasn't completely "unlocked" the 1S, we need workarounds like that to do certain things. However. TWRP will allow you to flash most things, including most kernels. If you use TWRP and yout hboot is low (which yours is) you shouldn't have too many issues.
Brief note here, I won't have adb access on this pc....will I be able to flash twrp without adb? I see there is an app in the market for it but seems to require root first. Thanks again for the input
Also, downloaded roms and kernels will need to reside on my SD card. This will become an issue if pre install format/wipe kills my SD card. Please advise. Roms and kernels will need to always be installed from SD card via recovery
Sent from my HTC VLE_U using xda app-developers app
briandresstoyota said:
Brief note here, I won't have adb access on this pc....will I be able to flash twrp without adb? I see there is an app in the market for it but seems to require root first. Thanks again for the input
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
You need adb access. That's how you flash recovery, using command prompt on the PC.
Not sure about this app, what's the name of it? To my knowledge you need adb to flash recovery on this phone.
If this isn't possible, you will still be able to root, just not have a custom recovery or flash roms. I don't believe you need to unlock the bootloader to root...not 100% sure but I believe you can root without it, which should be pretty simple.
On twrp website there is an option to install recovery via an app called goomanager. In the app store goo manager states root required. Should I revise my steps to this:
1)unlock bl
2) root using supersu img
3)goomanager install twrp
4)use twrp to flash roms and kernels
I would really love to avoid flashing radios btw. I just feel like it might be safer to let it be. Radios always made me nervous on previous devices
Sent from my HTC VLE_U using xda app-developers app
You could download goo manager from the play store then install open recovery script from menu..then flash the SuperSU zip. You wouldn't require ADB then.
invasion2 said:
You could download goo manager from the play store then install open recovery script from menu..then flash the SuperSU zip. You wouldn't require ADB then.
Click to expand...
Click to collapse
This is correct. I forgot about goomanager.
As for the radios, there isn't really too much risk on the 1S. I remember it was always a scary issue on the HD2 because of EU vs. US radios, which could cause a brick. On the 1S you can flash EU radios with no prob. Actually, some people report better performance in the US with EU radio. So yeah, don't be worried about it, it's pretty safe on this device - with normal precautions and proper flashing of course.
HOWEVER:
Make sure to only use S4 radios/roms on S4 processor. There is an S3 version of the 1S as well, and you cannot switch any roms/kernels/radios between the two.
Hey hey!!! Made it work. Flashed aokp. Running sooooo amazing. Anyone know how to make home screen and app store rotate?
Sent from my HTC One S using xda app-developers app
Can't make home screen. But turn on auto-rotate in settings and it should rotate the store.
So I am a happy rooted owner. No sound in music apps or YouTube.
Sent from my HTC One S using xda app-developers app
Soo started with aokp then cm10. No sound on either except in power amp. So weird
Sent from my HTC One S using xda app-developers app
Try flashing official CM10
http://get.cm/?device=ville
If you prefer a stock look try TrickDroid or Viper
Sent from my HTC One S using xda app-developers app
Actually flashed most recent cm10 nightly after my go with AOKP. Still no dice. I've posted the issue on both ROM dev forums so hopefully it will get resolved. I feel like it is operator error but I have flashed each ROM twice with a full wipe before each install. I understand the process for flashing so I hope its something small I missed.
Sent from my HTC One S using xda app-developers app
briandresstoyota said:
Actually flashed most recent cm10 nightly after my go with AOKP. Still no dice. I've posted the issue on both ROM dev forums so hopefully it will get resolved. I feel like it is operator error but I have flashed each ROM twice with a full wipe before each install. I understand the process for flashing so I hope its something small I missed.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Do you have no sound from the speaker or do you have headphones or something plugged in?

[Recovery][Unofficial]TWRP 2.7.0.0 & Clockwork Recovery Touch 6.0.4.4 W/loki (D800)

[Recovery][Unofficial]TWRP 2.7.0.0 & Clockwork Recovery Touch 6.0.4.4 W/loki (D800)
Clockwork recovery touch with Loki for AT&T LG G2 (D800) Only.
TWRP recovery touch with Loki for AT&T LG G2 (D800) Only.
The only difference between official recoveries and this version is that Loki is built in to recovery.
THIS IS ONLY FOR 10d FIRMWARE. IF YOU ARE ON 10o THEN DO NOT USE!!!
You may want to flash 10d firmware. It can be found HERE with instructions. If you plan on using ROMs it is best to flash 10d firmware first.
Install Methods
Flashable Zip - Must have TWRP or whatever custom recovery already installed.
Boot into recovery and flash Recovery Zip file.
Manual Method - With no custom recovery already installed.
Must have Root first. Check HERE for root
Download the zip file to which recovery you want
Extract zip file to C:\
Open command prompt in root of C drive
You will need adb installed and properly setup in your environment variables. If not place the recovery.img wherever your adb file is located.
Type the following commands:
Code:
adb push recovery.img /data/local/tmp/recovery.img
adb shell
su
cd /data/local/tmp
dd if=/data/local/tmp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
exit
exit
adb reboot recovery
Now you should be in recovery.
Downloads
TWRP 2.7.0.0 with Loki
File Name openrecovery-twrp-2.7.0.0-d800-loki.zip
MD5 f640c221e4a6c575b375094f765d63ba
Clockwork Recovery Touch 6.0.4.4 with Loki
File Name recovery-clockwork-touch-6.0.4.4-d800-loki.zip
MD5 d50fbe2e026463e5df698f0b8b0a4d91
Download HERE
Mirror - Goo.im
Enjoy!
Web Presence:
Twitter
Google+
Credits
TWRP team for great recovery
Koush for original clockwork recovery
djrbliss for Loki
manojsuper said:
Does everything worked.
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Everything I have tested so far.
Can I flash using flashify?
Sent from my LG-D802 using XDA Premium 4 mobile app
holeshot77 said:
Can I flash using flashify?
Sent from my LG-D802 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have not tested that way but I am sure you can. If you just need the img file than extract from zip file.
If you try then let us know how it worked out
Using flashify works like a charm. Just extract img file and flash using flashify. As a third alternative.
Sent from my LG-D802 using XDA Premium 4 mobile app
I haven't used cwm since the days of the vibrant but ,my question is does this recovery speed up flashing a rom? It takes me less then a minute to flash a rom on the nexus 4 so I was just curious. Thanks.
Sent from my Nexus 7 2013 using XDA Premium 4 mobile app
ManOnTheMoon said:
I haven't used cwm since the days of the vibrant but ,my question is does this recovery speed up flashing a rom? It takes me less then a minute to flash a rom on the nexus 4 so I was just curious. Thanks.
Sent from my Nexus 7 2013 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you been flashing OEM modified ROMs on G2 the speed may have been due to the size of the ROMs.
AndroidUser00110001 said:
If you been flashing OEM modified ROMs on G2 the speed may have been due to the size of the ROMs.
Click to expand...
Click to collapse
Sorry I meant to include CM/AOSP based roms. The days of flashing 250mb+ roms are over :good:
I also havent used CWM in a long time now, are there any real differences between this and TWRP besides layout? Any special features unique to CWM?
EniGmA1987 said:
I also havent used CWM in a long time now, are there any real differences between this and TWRP besides layout? Any special features unique to CWM?
Click to expand...
Click to collapse
They all do the same so people will use what they prefer...
Will I lose my twrp backups if I flash this clockwork recovery?
If not, then would I be able to restore twrp backups with cwm? May be a silly question but I never tried this and worried about losing backups.
You will not lose them until you delete them but I am not sure if you can restore twrp backups with clockwork.
SysAdmNj said:
Will I lose my twrp backups if I flash this clockwork recovery?
If not, then would I be able to restore twrp backups with cwm? May be a silly question but I never tried this and worried about losing backups.
Click to expand...
Click to collapse
Sent from my LG-D800 using XDA Premium 4 mobile app
Thanks for this! Always good to see people doing stuff on this phone : )
Flashing was a breeze. Thanks.
Does this mount usb-otg? When I try "Mount USB Storage" nothing happens. I am pretty sure TWRP also does not yet support usb-otg. My hopes were CWM did.
Thanks
Adb side load is an alternative for Mount usb. Install Zip --> Install from adb sideload. Unfortunately this didn't work for me either. If it works for any of you guys please let me know the steps you followed. Sideload doesn't work in TWRP also.
In case of a soft brick either Mount usb or adb side load should help. Otherwise you have to go back to stock using Lg tools and start all over again.
varunkumars said:
Adb side load is an alternative for Mount usb. Install Zip --> Install from adb sideload. Unfortunately this didn't work for me either. If it works for any of you guys please let me know the steps you followed. Sideload doesn't work in TWRP also.
In case of a soft brick either Mount usb or adb side load should help. Otherwise you have to go back to stock using Lg tools and start all over again.
Click to expand...
Click to collapse
Thanks for the reply. I will be a happy camper when we get real usb-otg support from both recoveries
Format Cache is not working
Hey guys,
I flashed this and seem to have a problem with formatting the cache- it just stops so I cannot wipe becuase it stops at formatting cache. Anybody else experienced this before? I flashed again with same results.
thanks,
AC
aaronc_98 said:
Hey guys,
I flashed this and seem to have a problem with formatting the cache- it just stops so I cannot wipe becuase it stops at formatting cache. Anybody else experienced this before? I flashed again with same results.
thanks,
AC
Click to expand...
Click to collapse
Just let it finish, it takes a long time. I thought the same and then it finished up.
Worked like a charm. Thanks!
Sent from my LG-D800 using Tapatalk
Is wiping always going to take this long?
Sent from my LG-D800 using Tapatalk

[Q] Anyone had success using "Flashify"?

I currently can't use my usb port to receive data, so adb isn't an option.
I'm looking to flash the new PAC rom, and need to update my TWRP recovery from 2.6.0.0 to 2.7.0.8. I'm using HBOOT 2.19 if that makes a difference?
I want to use Flashify to do this as its my only option without using adb that I can see.
Has anyone here had experience using this? If it doesn't work I don't have any other way of restoring my recovery and my phone will dead weight.
Also will updating my recovery wipe the sdcard? I hope not as I need the rom file to survive to be able to bring my phone back to life, as sideload won't work for me.
Thank you for any help received on this.
Sent from my GT-I9000 using xda app-developers app
i could be wrong mate but I'm sure I've read you can get ADB to work over WiFi, think you have to enable it in developer options.. surely there is a tutorial kicking around someplace on XDA.
flashing new recovery.img shouldnt wipe. only Unlocking the bootloader, super wipe, flashing a ruu, factory reset - they all wipe the phone
ill have a look about and get back to you
**UPDATE**
Found this amongst many other tutorials, not sure if it will work but worth a try
http://forum.xda-developers.com/showthread.php?t=2570432 apparantly he has updated it to http://forum.xda-developers.com/showthread.php?t=2707556
there is also a twrp manager app (by jmz) on playstore, i think you can flash a new recovery direct fom the app ????
I had problems flashing a boot.img via flashify. Flashed successfully but got problems later. flashed via fastboot and everything was fine.
Many thanks for the input. Will try this when I get my phone back from HTC.
@Braddison
Can you flash recoveries thru the android os over adb? Thought you had to do that thru hboot.
@theodorius123
What exactly did you try to flash with Flashify?
Sent from my GT-I9000 using Xparent Red Tapatalk 2
no idea what it was exactly, only know that it was a boot.img - as i wrote before
Not sure, but check out jmz app on play store.... Twrp manager I think you can do it from that or try goo manager, also on play store. i'm sure you can flash new recoveries directly from within these apps?
Good luck
twrp = https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager
goomanager = https://play.google.com/store/apps/details?id=com.s0up.goomanager
again not sure as i haven't tried them myself
Or this one: http://forum.xda-developers.com/showthread.php?t=2730305
Ah! Forgot about the aroma recovery installer. That's a great option. Then it should just be a matter of flashing rom. Are you s-off? If so shouldn't need to flash boot. Img afterward
I am s-off. Think the aroma installer is my best bet. But I may not bother just because its to much of a risk without being able to use fastboot to restore things in case something goes wrong...
Bloody HTC.
Sent from my GT-I9000 using Xparent Red Tapatalk 2

Categories

Resources