Related
Hi!
Is it possible to flash a original HTC ROM with the appropriate RADIO, without loosing the unlocked bootloader?
I want to have an original ROM to have a reference if my phone works properly.
Thanks,
newpipe
if you have the rom parts, you could flash them via fastboot- system, boot, and userdata. You can also flash recovery and radio if you want to go full stock except for the bootloader. You might have to pack the rom parts into the appropriate formats. Either ext3 images or images packed with ANDROID! magic.
There isn't much fastboot info since everyone seems to like the one-click methods or the methods that require minimal typing. You can look around the G1 forums for fastboot info and unpack a few images.
Just don't erase hboot and you'll be OK- and by OK, I mean that you'll be able to recovery from any semi-bricked, boot looping, non-functional state.
sent from my cyanogen(mod) vision
Somethere in development section i saw a rooted stock rom in .zip format for flashing by custom recovery. Worked for me.
lw_temp said:
Somethere in development section i saw a rooted stock rom in .zip format for flashing by custom recovery. Worked for me.
Click to expand...
Click to collapse
Talking about this?
Thanks for your answers!
lw_temp said:
Somethere in development section i saw a rooted stock rom in .zip format for flashing by custom recovery. Worked for me.
Click to expand...
Click to collapse
I think I'll do it that way.
Barton82 said:
Talking about this?
Click to expand...
Click to collapse
You're right. The first post in this thread looks promising.
Can we flash the ROM and RADIO linked without risk?
Edit: One more question: what does "Deodexed" mean? I saw the "Deodexed" ROM in the first post in the linked thread.
GO TO THE POST BELOW FOR THE RECOVERY AND INFO. PLEASE THANK HIM
CLICK ME FOR POST.
This is his topic full of stock recoveries and what-not
--------------------
Bear in mind that I do not have the time to restore to stock, and then check it for myself if you can extract the stock recovery without root, but you probably can. Please refer to the quote I will post below as I have little time to clean this post up.
Please thank user Davy Jones for actually finding the solution!
Davy Jones said:
Okay, I don't know any coding so I apologize if this is a dumb suggestion, but is it possible to follow the article's directions to pull recovery? So from shell:
dd if=/dev/block/mmcblk0p22 of=/sdcard/recovery.img bs=4096
I'm already on cwm so I have no way of testing this. Also, please don't try this unless you know what you are doing. I tried this on cwm and it created a file that was 10MB instead of the .img I originally flashed, which was 5.98MB.
Click to expand...
Click to collapse
My post starts here
-------------------------------------------
Alrighty that's wonderful. I am trying a guide right now and I will see if I am successful at extracting a recovery and I will report back.
EDIT
I've made wonderful process, and I've extracted a 10mb file which what the recovery.img supposed to be resized to.
So i've basically typed in
After this, I got a huge list of the partitions, and using this I've confirmed that mmcblk0p22 is the block that contains the recovery (I also made sure that I didn't extract something else, etc by checking what the userdata and sdcard size is supposed to be?
Then I typed in
and got
So I ended up with a 10MB file sitting in the root of my internal memory (known as sdcard)
Now I will try to confirm if it is the same file as my recovery.
EDIT
Well after more digging around.. I found this and where it says "Download - Recovery Image Method (using dd):" It shows that the block which the recovery is in in actually the same as the one above, so there was an easier way. Oh well! At least we confirmed that we have the correct file, the question is, can we flash it, guess I'll try after I get home.
If you want to try this out on a NON-Rooted one, you'll have to go to Settings>Developer Options>Root access and allow ADB.
-----------------------------------------------
Quote ends here.
Hopefully you're a Koodo owner reading this and have noticed the title.
Many of us Koodo owners, have rooted, installed a custom recovery, and have started the flashing frenzy, but we have forgot one thing.
No its not making a NAND of the stock ROM, its the fact the we forgot to backup our stock recoveries! I know it might not be a difference compared to the Telus recovery, but we still need to be sure, that when we want to update, or if we want to return the phone, what we are fully stock.
So what I'm asking you, is to make a backup of your Koodo stock recovery, and share it with us
Unfortunately I do not know how to extract a recovery.img. So hopefully an XDA member will post a guide in this to help us extract the .img
or as always, Google is your best friend
Cheers, and thanks
EDIT
Koragg618 said:
I have found a link on how to get it
http://www.addictivetips.com/mobile...es-boot-recovery-and-system-partition-images/
Download link for RomDump is at the end of the article
Click to expand...
Click to collapse
Those are the instructions.
Thanks everyone for contributing!
I have a stock phone still but need a guide on pulling my recovery. Would I just use ADB or?...
chevymeister said:
I have a stock phone still but need a guide on pulling my recovery. Would I just use ADB or?...
Click to expand...
Click to collapse
Im not a koodo member but is it not the same way for tmobile users? With stock ODIN flash? when I ODIN flash my t989 to stock it also flash the stock recovery
I have found a link on how to get it
http://www.addictivetips.com/mobile...es-boot-recovery-and-system-partition-images/
Download link for RomDump is at the end of the article
Bump, since no one is really noticing the pinned topic
Koragg618 said:
Bump, since no one is really noticing the pinned topic
Click to expand...
Click to collapse
I could help, Ive got a Koodo S2 X. However, its not rooted, would i still be able to make a backup of my stock recovery.
Yes I believe it is still possible, just make sure Debugging mode is on and you are using the ADB method, and not the one that has the Android Terminal one. Thanks
My friend and my girlfriend both have Stock Koodo Phone... so i'm gonne try to bring the original Koodo Recovery.img. I read the articles from addictive tips... but i think i missed something, They said we need to root the phone but the first step in the method to root the phone is to install CWM recovery IMG via Odin... So it will overwrite Koodo original Recovery.img.... before i extract it...
Any clue or hint ???
Maybe another way to root via ADB ???
I have a Koodo T989D still on stock everything. I want to root my phone and do all this fancy stuff on it but I'm not in a hurry. I can make a copy of my stock recovery if I get the proper instructions.
edit: isn't this what you're looking for anyway?? http://forum.xda-developers.com/showthread.php?t=1849748
tazmania12345 said:
I have a Koodo T989D still on stock everything. I want to root my phone and do all this fancy stuff on it but I'm not in a hurry. I can make a copy of my stock recovery if I get the proper instructions.
edit: isn't this what you're looking for anyway?? http://forum.xda-developers.com/showthread.php?t=1849748
Click to expand...
Click to collapse
No. What you're pointing to us is a custom Rom... Based on the Stock Koodo Rom. What we are looking for is the Stock Recovery... Just to put back the entire phone in original condition if you have to bring it back to manufacturer for repair...
Tornade69 said:
No. What you're pointing to us is a custom Rom... Based on the Stock Koodo Rom. What we are looking for is the Stock Recovery... Just to put back the entire phone in original condition if you have to bring it back to manufacturer for repair...
Click to expand...
Click to collapse
Oh i see... I'm still on stock 4.0.4 so i'll definitely try to provide the backup. Like i said, i'd need the proper instructions because i'm new to all of this.
Someone previously posted the stock recovery which I have attached. Use at your own risk since I have not tested it!
Amazing, where did you find this!
Koragg618 said:
Amazing, where did you find this!
Click to expand...
Click to collapse
Someone previously posted it few weeks ago on the XDA forums in the device dev section and I had downloaded and kept a copy in case I needed it.
jumran said:
Someone previously posted it few weeks ago on the XDA forums in the device dev section and I had downloaded and kept a copy in case I needed it.
Click to expand...
Click to collapse
Thanks! This will come in handy.
Sorry to be the bad news but I believe this recovery is the one that I've packaged before I though I've found the TLLG2 stock recovery from this site page 68( post by netusername and uploading it without testing it 1st.... then later installed/tested it and it was a CWM touch recovery and not the TLLG2 stock recovery, Sorry again.
Source:
User:netusername
KOODO STOCK IMAGE/RESTORE
Directions: Download these three in the same folder - Part 1, Part 2, Part 3
Use Winrar/7zip to only extract Part 1 after you have all three parts in the same folder. You should get a folder called clockworkmod. There should be another folder called "backup" inside.
Put the "clockwordmod" folder in your sd card.
Use clockwordmod to restore after factory reset, wipe system, wipe dalvik cache.... It is recommended that you use Clockwordmod 6 - it can be found here - http://forum.xda-developers.com/show....php?t=1823117
Enjoy!
Click to expand...
Click to collapse
Sent from my ♛ SGH-T989 ♛ using XDA app.
Oh well thats confusing Thanks for the info man!
Sorry I'm not following.
Do you mean the post by jumran (http://forum.xda-developers.com/showpost.php?p=32299219&postcount=12) is not the stock recovery and is actually a CWM recovery that you're mentioning?
KRZ-2pa said:
Sorry to be the bad news but I believe this recovery is the one that I've packaged before I though I've found the TLLG2 stock recovery from this site page 68( post by netusername and uploading it without testing it 1st.... then later installed/tested it and it was a CWM touch recovery and not the TLLG2 stock recovery, Sorry again.
Source:
Sent from my ♛ SGH-T989 ♛ using XDA app.
Click to expand...
Click to collapse
Yes it is a CMW Touch recovery and no problem
[curious] What are you guys doing? [/curious]
You realize backing up any part of your original stock ROM is pointless? All you have to do pick up the original stock tarball from Samsung's website, fire up ODIN, flash, and then not even Samsung can tell you ever did something to your phone. It will be stock everything: radio, recovery, ROM...
---------- Post added at 08:41 PM ---------- Previous post was at 08:31 PM ----------
Here, follow the instructions: http://fus.nanzen.se/
There are no presets for Koodo, but all the information you need is readily available on the original box your phones came in.
And if you really need the Koodo recovery for whatever reason, it is an IMG file inside the TARball. You can just DD it in place.
I've been reading these forums in my spare time for the last week or so but I'm still a bit confused or just overlooking something. According to the CM 10.1 thread install instructions are
Install instructions:
1. Install ClockworkMod Recovery for "I927". Sorry, CM cannot provide support for other recoveries, although they may work fine.
3. Reboot into recovery and install
Click to expand...
Click to collapse
and a few people in some of the guide threads have basically stated the same. Is it really this simple now or do I still need to follow the guide from a year ago or the one in this thread http://forum.xda-developers.com/showthread.php?t=1962633 ?
So far all I have done is install CWMR Touch 6.0.1.2 Recovery and run backup in both blob and tar formats. Actually does this even work properly without rooting first?
You don't need root, but you can't quite go straight either. The current SOP is:
Flash TW-ICS, meaning UCLG9 or UCLH2 or UCLJ3, using the respective OneClick
Flash CWMR using Odin (the previous step overwrites recovery so you will have to do this again even if you flashed CWM previously)
Boot into CWM
Flash your AOSP-JB ROM of choice
Flash the correct gapps for your ROM
Format /data (aka factory reset)
Reboot into ROM and enjoy
Step 1 may or may not be necessary -- nobody's tried going from TW-GB straight to AOSP-JB yet. If you're feeling adventurous, try it and let us know how it goes.
Once you've flashed a TW-ICS once, you won't need to do it again -- at that point flashing a new TW-ICS or AOSP-JB ROM is as simple as flash-format-boot.
Thanks for the updated info, I didn't think it would be that simple.
Not sure what TW stands for since I haven't seen that abbreviation yet.
But basically for step one I can grab the UCLG9 from this thread http://forum.xda-developers.com/showthread.php?t=1841502
and flash it with CWM and then follow on from step 2? Or would I be better off grabbing the newer UCLJ3 from SamMobile and using Odin?
Bram Skull said:
Thanks for the updated info, I didn't think it would be that simple.
Not sure what TW stands for since I haven't seen that abbreviation yet.
But basically for step one I can grab the UCLG9 from this thread http://forum.xda-developers.com/showthread.php?t=1841502
and flash it with CWM and then follow on from step 2? Or would I be better off grabbing the newer UCLJ3 from SamMobile and using Odin?
Click to expand...
Click to collapse
Nope no zips or Odin just use one click the first time. So for step 1 above follow this http://www.theandroidsoul.com/android-4-0-4-ice-cream-sandwich-update-for-att-captivate-glide-i927uclg9/. Can't get easier then this.
Bram Skull said:
Thanks for the updated info, I didn't think it would be that simple.
Not sure what TW stands for since I haven't seen that abbreviation yet.
Click to expand...
Click to collapse
TW == TouchWiz. Basically official Samsung stuff and ROMs based directly on such.
But basically for step one I can grab the UCLG9 from this thread http://forum.xda-developers.com/showthread.php?t=1841502
and flash it with CWM and then follow on from step 2? Or would I be better off grabbing the newer UCLJ3 from SamMobile and using Odin?
Click to expand...
Click to collapse
I would get the full EXE, just to be sure. The CWM zips generally don't include bootloader or baseband and that's the important stuff.
I would get the full EXE, just to be sure. The CWM zips generally don't include bootloader or baseband and that's the important stuff.
Click to expand...
Click to collapse
I used the CWM flash and can confirm the no updated baseband since it still had the stock Rogers one on AT&T-ICS and in CM-10.1. Not sure about ICS but in CM-10.1 I could get voice but no data and haven't tested txt.
Going to flash back to stock with the backup I made for now while I research solutions to a few personal gripes I have with CM-10.1.
And would the UCLJ3 from SamMobile with odin or kies be as effective as the EXE version since I already have it downloaded?
Thanks for helping a total noob and to be honest this is my first Android phone.
Bram Skull said:
I used the CWM flash and can confirm the no updated baseband since it still had the stock Rogers one on AT&T-ICS and in CM-10.1. Not sure about ICS but in CM-10.1 I could get voice but no data and haven't tested txt.
Going to flash back to stock with the backup I made for now while I research solutions to a few personal gripes I have with CM-10.1.
And would the UCLJ3 from SamMobile with odin or kies be as effective as the EXE version since I already have it downloaded?
Thanks for helping a total noob and to be honest this is my first Android phone.
Click to expand...
Click to collapse
I just took a peek... ooh. Looks like pretty much everything is in there. You should be good.
Hello xda,
I tried rooting my SGH-T999 and it took a while so I unplugged the USB and restarted the phone. Phone keeps saying it has encountered a problem with the current firmware, connect to KIES and select recovery. Kies does not connect to the device. I read on xda to reflash using ODIN. I have ODIN v1.85 from trying to root, is this the right version to use because I also found the ODIN3_v3.07? As far as USB driver, is there separate drivers for ODIN or are people referring to the Samsung Kies drivers (I just installed KIES). I read to do it on this screen and I also read to try to go into the recovery mode (holding vol down, home, power) and then reflashing; which should I do?
Also, I found this link on xda for the T-mobile firmware ( http://forum.xda-developers.com/showthread.php?t=1949687 ). No idea which one to choose, why are there so many, I am currently downloading the latest one
"UVDLJA
PDA: T999UVDLJA
CSC: T999TMBDLJA
Version: 4.1.1 JB
Date: Nov. 14, 2012
Sammobile Link
Samsung-Updates Link"
If I want to use the pre rooted file do I need to fix my problem first and try flashing with stock firmware or can I try to fix the issue directly with the pre rooted firmware?
Re: [Q] SGH-T999 Rooted bad, phone stuck on start screen
Use the Odin from my signature.
You can probably just flash mrRobinson's stock rooted rom to fix it. And Kies is garbage. Uninstall it.
I would like to see the root guide you used as well.
Aerowinder said:
Use the Odin from my signature.
You can probably just flash mrRobinson's stock rooted rom to fix it. And Kies is garbage. Uninstall it.
I would like to see the root guide you used as well.
Click to expand...
Click to collapse
I used this guide to root.
http://galaxys3root.com/galaxy-s3-r...gh-t999sgh-i747sph-l710-fail-proofnoob-proof/
Before I try to flash with mrRobinson's stock rooted rom which I just finished downloading, I will uninstall Kies and install the USB drivers first?
Thanks for your response Aerowinder.
I got USB drivers earlier today that was a newer version but I will be using the files from your sig since it works :good:
Another question I had was, does the phone need to be in download mode or can I do it in the screen where it says "encountered problem with current firmware. Connect to KIES and select recovery" screen when I flash with Odin? I know normally I would have to be in the download mode but I'm wondering if it is the same when I am getting this error.
Re: [Q] SGH-T999 Rooted bad, phone stuck on start screen
Phone must be in download mode to use Odin.
The drivers in my signature are not the newest, you are correct. They are the last version I found that work without any issues. The newer ones pretty much suck. Constant disconnects mainly.
Aerowinder said:
Phone must be in download mode to use Odin.
The drivers in my signature are not the newest, you are correct. They are the last version I found that work without any issues. The newer ones pretty much suck. Constant disconnects mainly.
Click to expand...
Click to collapse
Awesome thanks!
So I am watching the root video on your sig, so in my case I would choose the rom I want for the PDA instead of the cwm-touch-6.0.2.3-d2tmo right? Should I extract the rooted firmware or just load the zipped file onto ODIN PDA?
Re: [Q] SGH-T999 Rooted bad, phone stuck on start screen
Root66 does not contain a recovery so you still need to flash one of those but don't use my link. Get ROM Manager once you're up and running.
If you don't care about the flash counter you can flash the tar in my signature.
Sorry to interject here but you can get an Odin flashable recovery from here.
You can flash one of these and then flash Root66 right after and you'll have stock Rooted ROM with stock or custom recovery (your choice).
Not to be a buzzkill or anything but you are probably the 5th or 6th person in the past 2 weeks that have encountered the "encountered problem with current firmware. Connect to KIES and select recovery" error. Only a few of them have been able to pull out of it. The ones that have, have had to flash Root66 (or their device respective FW) multiple times.
I hope that you can get out of it and please post here if you do. Aerowinder knows what he is doing. Follow his lead.
Aerowinder said:
Root66 does not contain a recovery so you still need to flash one of those but don't use my link. Get ROM Manager once you're up and running.
If you don't care about the flash counter you can flash the tar in my signature.
Click to expand...
Click to collapse
Okay I don't care about the counter, I just want my phone to work and I'll be happy.
But now I'm getting a little confused about the cwm recovery.
So just to be clear, you are saying I need to flash a recovery (cwm-touch-6.0.2.3-d2tmo in my case since I don't care about the counter), BUT do I flash the recovery before or after I flash with Root66 firmware? That part I am confused about. And do I flash one right after another or do I need to restart my phone or ODIN first?
Thank you so much for helping me out. I was freaking out this morning and I am very grateful for your help and knowledge. I hope I am not being too much of a pain or hassle with these questions. Sorry that I am quite new to this
Woody said:
Sorry to interject here but you can get an Odin flashable recovery from here.
You can flash one of these and then flash Root66 right after and you'll have stock Rooted ROM with stock or custom recovery (your choice).
Not to be a buzzkill or anything but you are probably the 5th or 6th person in the past 2 weeks that have encountered the "encountered problem with current firmware. Connect to KIES and select recovery" error. Only a few of them have been able to pull out of it. The ones that have, have had to flash Root66 (or their device respective FW) multiple times.
I hope that you can get out of it and please post here if you do. Aerowinder knows what he is doing. Follow his lead.
Click to expand...
Click to collapse
Woody, I went to the link you posted. What are the 4 files for?
Don't use those - they are older versions.
If you don't care about the counter, then flash the CWM in my signature using Odin (can provide TWRP tar link if that's your thing), then flash root66 using Odin. You can reboot in between... but no real reason to do so.
If you are still having issues after you flash these, drop into recovery (vol up + home) and reset factory defaults. If still having problems, only thing left to do is flash a full stock image, link also in my signature. The page you linked to does not contain the newest version because DocHolliday hasn't been around here much lately.
buzzking00 said:
Woody, I went to the link you posted. What are the 4 files for?
Click to expand...
Click to collapse
Top one is TWRP version 2.3.0.0
Second is 6.0.1.2 CWR touch version
Third is TWRP version 2.3.1.0
Fourth is Stock recovery.
Do not flash all of them. Are you a TWRP or CWR kind of person? Instead of re-typing it out, go here and I come in on post #20 on the 2nd page. Read that to the end and let us know if you understand it. Pretty easy to follow but I understand your Panic Mode, so take your time.
Aerowinder said:
If still having problems, only thing left to do is flash a full stock image, link also in my signature.
Click to expand...
Click to collapse
^^ This is what I see in his future.
Like I said above, I haven't seen too many people get out of that "Encountered..." error without some real technical expertise.
Aerowinder said:
Don't use those - they are older versions.
If you don't care about the counter, then flash the CWM in my signature using Odin (can provide TWRP tar link if that's your thing), then flash root66 using Odin. You can reboot in between... but no real reason to do so.
If you are still having issues after you flash these, drop into recovery (vol up + home) and reset factory defaults. If still having problems, only thing left to do is flash a full stock image, link also in my signature. The page you linked to does not contain the newest version because DocHolliday hasn't been around here much lately.
Click to expand...
Click to collapse
Awesome. Thanks Aerowinder!
I will try this when I get home (assuming I can go into download mode...) and post what happened
Woody said:
^^ This is what I see in his future.
Like I said above, I haven't seen too many people get out of that "Encountered..." error without some real technical expertise.
Click to expand...
Click to collapse
I will take a look at the link Woody.
I am really hoping this will work on the first try!
Okay so from reading your post Woody I can use EITHER the TWRP and CWR, but I want to use the one that is easiest to use. Which one do you guys think is easier to use?
Also, SU3.3 or SU1.04 which one should I use? Aerowinder, your sig shows both now but earlier I didn't notice the SU1.04. I just realized I only need the SU file IF the prerooted file doesn't work but just in case it doesn't I guess it is better to know.
Draw straws. I use CWM/Superuser. I use Superuser because CM comes with it. AOKP comes with SuperSU... both work fine. Just make sure you use the ones from my signature, as they are newer versions. You won't need su if you get a prerooted rom, only for stock.
Aerowinder said:
Draw straws. I use CWM/Superuser. I use Superuser because CM comes with it. AOKP comes with SuperSU... both work fine. Just make sure you use the ones from my signature, as they are newer versions. You won't need su if you get a prerooted rom, only for stock.
Click to expand...
Click to collapse
I am going to try it in an hour.
Wish me luck!
1. Download mode
2. Flash CWM
3. Flash Root66
4. Hopefully no problems
:good:
Aerowinder said:
Don't use those - they are older versions.
If you don't care about the counter, then flash the CWM in my signature using Odin (can provide TWRP tar link if that's your thing), then flash root66 using Odin. You can reboot in between... but no real reason to do so.
If you are still having issues after you flash these, drop into recovery (vol up + home) and reset factory defaults. If still having problems, only thing left to do is flash a full stock image, link also in my signature. The page you linked to does not contain the newest version because DocHolliday hasn't been around here much lately.
Click to expand...
Click to collapse
OMFG OMFG OMFG
OMFG OMFG OMFG
OOOOOOH MYYYYYY FOOOOOOOOKIN GOOOOOOOOOOOOSH
AEROWINDER AND WOODY
I LOVE YOU SO MUCH
IT WORKED AND NOTHING GOT ERASED. I THOUGHT PUTTING THE NEW FIRMWARE WOULD'VE ERASED EVERYTHING WITH THE NEW ROM BUT NOPE.
Uninstalled KIES and USB drivers.
Installed USB drivers from Aerowinders sig
So the Odin 3.07 didn't work either so I ended up using ODIN 1.85
Turned off auto reboot and left f reset on (no idea what f reset does lol)
Flashed CWM
Flashed root66 rom
Restarted phone and it was back to normal with all the data saved, but no SU (wasn't unlocked)
So reflashed CWM
Then restarted in clockwork recovery and ran super user and now the phone is rooted
Thanks for your helpful knowledge and now I am going to learn everything about android so I too can help another new android user in the (hopefully near) future.
:good::good::good: 3 thumbs up to the knowledge members above Aerowinder and Woody!
THANK YOU!
Panic mode TRANSFORMMMMM! *Panic mode has now transformed into excitement mode*
buzzking00 said:
Thanks for your helpful knowledge and now I am going to learn everything about android so I too can help another new android user in the (hopefully near) future.
Click to expand...
Click to collapse
So, ahh, are you excited? Haha. Great. Glad you got it up and running.
I hope that you do learn more about Android and share it with someone who needs help someday. When I first came, that is what someone did for me and I have tried to do it ever since. We are all still learning, including Aero and myself, so there will never be an end but rather more.
Good job and now you should make a Nandroid backup just in case you ever get in a bind again.
Well now I gotta learn how to make back-ups and what a Nandroid backup is lol.
Time to search the forums
buzzking00 said:
Well now I gotta learn how to make back-ups and what a Nandroid backup is lol.
Time to search the forums
Click to expand...
Click to collapse
That's the attitude, with Android you have to be a sponge and try to learn as much as you can. A single Google search will give you the answers you seek and making a backup is pretty much universal no matter what Rom, phone you have. Good luck
Sent from my SGH-T999 using xda app-developers app
hello every body
is there a .ftf file with root and cwm in it ?
i need it because every time i try a rom and have a no boot i need to flash a stock rom and root it and install cwm w then i can try again with another rom so is there a prerooted ftf file with cwm preinstalled ?? or is there a shorter way ??
sorry about my bad english (it is not my first language)
AW: ftf with root and cwm
ash-ta said:
hello every body
is there a .ftf file with root and cwm in it ?
i need it because every time i try a rom and have a no boot i need to flash a stock rom and root it and install cwm w then i can try again with another rom so is there a prerooted ftf file with cwm preinstalled ?? or is there a shorter way ??
sorry about my bad english (it is not my first language)
Click to expand...
Click to collapse
that was also my first question on xda, good old times...
No, it's not possible, ftf. files can only be made by Sony, so you've got to do always the same prodecure for flashing, rooting,....
Sent from my LT18i using xda app-developers app
Master of Bisaster said:
that was also my first question on xda, good old times...
No, it's not possible, ftf. files can only be made by Sony, so you've got to do always the same prodecure for flashing, rooting,....
Sent from my LT18i using xda app-developers app
Click to expand...
Click to collapse
thank you so much for your answer
so i think i will keep doing that long thing again and again
That's a really tedious procedure you're following. When I try a custom ROM and don't like it, all I do is:
1) If switching between an ICS ROM and a JB ROM and vice versa, reflash the kernel, then reflash the ROM.
2) If moving from one ICS ROM to another, or one JB ROM to another, just reflash the ROM.
3) If moving from ICS/JB to GB or vice versa, flash the stock ROM, flash the kernel, and then flash the custom ROM.
You don't need to keep on flashing the stock ROM, rooting it, installing CWM, then installing the custom ROM. Kernels, as far as I know, usually come with recovery installed. If you're in a bootloop, just follow the pertinent steps from the list outlined above.
MarcSinger said:
That's a really tedious procedure you're following. When I try a custom ROM and don't like it, all I do is:
1) If switching between an ICS ROM and a JB ROM and vice versa, reflash the kernel, then reflash the ROM.
2) If moving from one ICS ROM to another, or one JB ROM to another, just reflash the ROM.
3) If moving from ICS/JB to GB or vice versa, flash the stock ROM, flash the kernel, and then flash the custom ROM.
You don't need to keep on flashing the stock ROM, rooting it, installing CWM, then installing the custom ROM. Kernels, as far as I know, usually come with recovery installed. If you're in a bootloop, just follow the pertinent steps from the list outlined above.
Click to expand...
Click to collapse
that is rghit but the problem is i need the cwm for flashing the new rom and i have no boot (just sony logo) i cant enter the cwm so i find that i need to reinstall the cwm and try again
if i say any thing wrong please correct it to me maybe you teach me some thing that is new to me
ash-ta said:
maybe you teach me some thing that is new to me
Click to expand...
Click to collapse
Go read the stickys, get some basic knowledge and learn something for yourself, then ask questions about what you don't fully understand, on an existing thread that you found while Googling.
bootloader locked or unlocked because it sounds like you have a locked bootloader, if it is unlocked then why dont you flash a kernel eg. kernel rush with CWM already on it ?
ash-ta said:
that is rghit but the problem is i need the cwm for flashing the new rom and i have no boot (just sony logo) i cant enter the cwm so i find that i need to reinstall the cwm and try again
if i say any thing wrong please correct it to me maybe you teach me some thing that is new to me
Click to expand...
Click to collapse
You don't need to install CWM again, even if you're in a boot loop. Once the phone reboots, keep pressing the "down" volume rocker, as you always do, and you'll enter into recovery. If you're moving to a different Android version (for example, ICS to JB), switch off your phone and flash the appropriate kernel. Then all you need to do is reflash your previous ROM or flash any other ROM that you want. However, that's only possible if you've download your previous and/or other ROMs onto your SD card, too. Do you do that before you flash?
I don't have any experience with locked bootloaders, but the user above IS of the opinion that you might be on one. If that's the reason you're having to go through so many steps to flash a ROM, why don't you try unlocking the bootloader of your phone? I'm more than certain your phone's not covered under warranty anymore, and unlocking the bootloader is definitely not going to fry your phone or anything of the sort.