Database Develop

[RECOVERY][UNOFFICIAL]Clockworkmod 3 series

Wiping and backup problems have been fixed in CWM3 > 3.0.0.5. If you had trouble before, try again with ROM Manager. Try to flash the recovery at least twice before giving up, or use an alternate method below.
Ensure that "wipe recovery" option in ROM Manager settings is checked. There is no good reason to not have this checked. It should probably be the default. This will not affect your backups.
3.0.0.8 has fixed the SLCD problems. If you get the black screen with white bars, upgrade to 3.0.0.8.
Koush's official answer as to why you can't flash old .zip files with 3x.
Why you should upgrade to CWM 3 series from 2 series
CWM2 IS NO LONGER SUPPORTED AND MAY BREAK AT ANY TIME
ROM Manager won't work with 2 series anymore
support for journaling filesystems. Your data is safer.
pretty orange color
power down from recovery
better partitioning support
may be required for Cyanogenmod in the future. It is not required for the inc as of now.
Why you should not upgrade to CWM3 series
Fear of messing with recovery is not a good excuse
You want to install ROMs from ROM developers that use 2 year old technology and have refused to upgrade their zipping mechanisms (put pressure on them to change their installation scripts)
You like old ROMs that haven't been updated in ages
You are one of the few that the new recoveries don't work on. Ask and someone can probably help you get through this.
WHERE TO GET OLD VERSIONS OF CLOCKWORKMOD:
http://mirror1.kanged.net/recoveries/ - contains img files for all old versions
*http://dougpiston.com/?page_id=85 - contains PB31IMG for flashing through HBOOT, including 2.5.12 and 3.0.0.8. This is the easiest way to manually update recovery.
HOW TO INSTALL IMG FILES
***YOU SHOULD INSTALL THROUGH ROM MANGER IF AT ALL POSSIBLE. TRY TWICE IF IT DOESN'T WORK ON THE FIRST TRY***
Rename the image file you're interested in to recovery.img
OPTION1: ADB
Code:
C:\YOUR_ADB_DIR\>adb shell
$su
$/system/bin/flash_image recovery /sdcard/recovery.img
OPTION2: Android Terminal from phone
Copy the recovery.img to the root of your sd card.
Code:
$su
$/system/bin/flash_image recovery /sdcard/recovery.img
OPTION3: Use PB31IMG.zip
Download specific recoveries from dougpiston.com
If it is not available elsewhere, oll your own PB31IMG.zip
This is not as hard as you think. Download any recovery PB31IMG.zip, such as the one attached to this thread. Replace the recovery.img in the zip file with the one of the desired CWM recovery. Rename to PB31IMG.zip. Place in root of your SDCARD. Reboot into HBOOT. Install.
What to do if you have trouble with CWM3
Check partitions for errors
Try installing through ROM Manager, or installing through one of the alternate methods listed above
make sure wipe recovery is checked in ROM Manager settings.
make sure you have the latest version of ROM Manager. Check in the market.
How to manually wipe recovery partition.
The utility is present in CM7 builds. I cannot vouch for other ROMs. This can also be done easily through fastboot mechanisms, but afaik fastboot is not available for the incredible because there are not leaked engineering HBOOTs.
This should never need to be done except in extreme circumstances.
Code:
$su
$/system/bin/erase_image recovery
How to get into recovery manually w/out ROM Manager
Shut down your phone. Hold down volume down. Press power, keeping volume down held. This is HBOOT. Scroll down to recovery and push the power button again.
HTC Incredible Amend vs. Edify: How to get old ROMs working with CWMv3
Amend and Edify are scripting languages used to write the installation routines for .zip files, including ROMs. Amend is quite old, from the cupcake days, and as such does not have features necessary for modern ROMs. To simplify development, Koush removed amend support with the advent of CWMv3. He had announced that he was going to do this for months. Nonetheless, some older ROMs that are not actively developed anymore may be desirable, and many of these do not use the more modern edify scripting. There is a thread here on how to easily convert amend scripts to edify using amend2edify: http://forum.xda-developers.com/showthread.php?t=903598.
Other sources for help
IRC
#cyanogenmod or #koush - it is recommended you try the solutions noted in this thread first. Self initiative is important, but seek help if you need it.
Who are the people behind CWM:
koush is the primary developer, slayher and CUViper help adapt it to the incredible, I'm sure many others.
How to build Clockworkmod yourself:
http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
EDIT 2/27/11: This thread used to contain info regarding a custom build of CWM3006. It is still attached to this thread, but koush has upgraded CWM to 3008 which contains the 3006 fixes and more.
Click to expand...
Click to collapse

Thank you I haven't really had any problems with 3.0.0.5, but I've seen a lot who have. Maybe this fixes some of the wiping bugs people were having?

BrettApple said:
Thank you I haven't really had any problems with 3.0.0.5, but I've seen a lot who have. Maybe this fixes some of the wiping bugs people were having?
Click to expand...
Click to collapse
It is really odd, as I can install this version and backup/restore fine, then switch back to 3.0.0.5 and backup locks up consistently.
Its true re: the wiping bugs. It seems there's a lot more noise about the 3 series CWM than the 2 series, although I wonder if its just a lot more people are installing it and not quite understanding how cwm/hboot/cm7 interact. Hard to tease it apart.
I'm talking to koush and trying to get him to recompile it and make it official, regardless.

I tried the above CWR and my recovery screen is all black with white boarder on each sides.

meazz1 said:
I tried the above CWR and my recovery screen is all black with white boarder on each sides.
Click to expand...
Click to collapse
Thats quite odd. Try reflashing a working recovery and then back to this one?
What ROM/Radio/Phone (inc slcd or amoled)?
You can also extract the recovery.img out of the zip file and flash it with adb or flash_image.
Let me know please, I'll pull it down if there's consistent problems.

dont pull it booted on my device and ROM.... i'll do some extensive testing and report back

Sounds like this is for AMOLED only
Side note, I looked at an SLCD Incredible today. Noticeable difference in screens. I will say that AMOLED is much brighter and produces better color than SLCD, but SLCD wins hands down in crispness.

ok
1. doesnt show proper version in rom manager
2. will not flash rom via rom manager... probably hook issue
3. works fine in recovery mode
imo if it dont work via rom manager its kind of a deal breaker for me... alot of my users want to use it as well as be able to flashover without having major issues
right now with 3.0.0.5 if you flash via rom manager without a full wipe... chances are... you'll end up wiping and reinstalling because of fc issues

Flashed fine here. In the process of making a back up.
I'm diggin the power-off feature.
I only use RM to DL roms, flashing within RM only breaks ****.
Backup sucessfully made.

lllboredlll said:
ok
1. doesnt show proper version in rom manager
2. will not flash rom via rom manager... probably hook issue
3. works fine in recovery mode
Click to expand...
Click to collapse
1) I believe if a recovery doesn't show up in the clockworkmod available recoveries, it will not show the proper ROM Manager version. Flash 2.5.0.5 and you'll see the same effect.
2) Looking into this now.
3) That's good to hear! Thank you for testing this! This, coincidentally, is primarily how I use CWM as RM has not been stable/consistent for me in ages.
lllboredlll said:
ok
imo if it dont work via rom manager its kind of a deal breaker for me... alot of my users want to use it as well as be able to flashover without having major issues
Click to expand...
Click to collapse
I hear what you're saying.
To get the hooks in place, install 3.0.0.5 first via ROM manager, then go into hboot and install this 3.0.0.6. ROM Manager still thinks you have 3005 and backup/etc. works.
I don't mean this to be production quality, but it should help bridge the gap until koush gets a new version out.

shoman24v said:
Flashed fine here. In the process of making a back up.
I'm diggin the power-off feature.
I only use RM to DL roms, flashing within RM only breaks ****.
Backup sucessfully made.
Click to expand...
Click to collapse
Thank you for testing this! I've updating the OP with notes from both you and bored. And made the disclaimer larger with more ***

No problem. RM still shows 3.0.0.5, but that's not a big deal. I still see the latest nightlies available from RM.
And, like I said, I never flash within RM.
Nor do I recommend that.

tdiman said:
EDIT 2/26/11: This information, as hoped, has been deprecated by the release of CWM 3.0.0.7. You should use that one, because CUViper and koush found more bugs re: the communication between ROM Manager and CWM, as well as the fixes noted below.
Click to expand...
Click to collapse
Just in case someone comes along late to the party, please note the above information added to the OP.

Is it true that v2.5.x.x nandroid backups will not restore under v3.0.x.x clockwork recovery?
Sent from my ADR6300 using XDA App

jdmba said:
Is it true that v2.5.x.x nandroid backups will not restore under v3.0.x.x clockwork recovery?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
no. thats not correct - i have restored a bunch without issues.

I updated to 3.0.0.5 a few weeks ago when it came out. All seems to work fine for me except I can't restore to a previous version to flash other Roms (well at least from Rom Manager). Many of the other Roms that are out right now are not Edify.
Sorry if this is the wrong thread to post this in.
I've googled changing the Roms to edify myself, but I'm kind of lazy and switching recoveries seemed like it would be the easier route.

I think koush has been trying to gently encourage app developers for months to change over.
If you search this forum you'll find older versions of cwm.

The version number is reporting fine for me..... and i Love the new look of the recovery. I'm missing the fast scrolling from the previous builds, other then that I love it

Anyone notice 3007 disappeared from ROM manager for the DINC, I mean as the newest version that is. It is still in the experimental recoveries.

thelunchboxosu said:
Anyone notice 3007 disappeared from ROM manager for the DINC, I mean as the newest version that is. It is still in the experimental recoveries.
Click to expand...
Click to collapse
3008 is in there now also. Fast scrolling is back. I don't know if the glitch with some slcds is fixed.

Noob still on CM 7.1 needs KK.

Every time I trie to update to the latest ROMs I notice they specifically target the new bootloader. I have no idea what the old vs new bootloader dilemma is about but I bet my device runs the old one, I read somewhere the white LG logo on startup hints to an old bootloader,
My question is how to upgrade my bootloader or ROM directly to Kitkat the easiest way possible, I bought my handset already CMed and unrooted but I have never done it myself.
Thank you in advance, and if you could bother throw in some links to relevant threadshttp://forum.xda-developers.com/images/icons/icon8.gif

xdaCyborg said:
Every time I trie to update to the latest ROMs I notice they specifically target the new bootloader. I have no idea what the old vs new bootloader dilemma is about but I bet my device runs the old one, I read somewhere the white LG logo on startup hints to an old bootloader,
My question is how to upgrade my bootloader or ROM directly to Kitkat the easiest way possible, I bought my handset already CMed and unrooted but I have never done it myself.
Thank you in advance, and if you could bother throw in some links to relevant threadshttp://forum.xda-developers.com/images/icons/icon8.gif
Click to expand...
Click to collapse
for tonyps kitkat , the only one for daily usage workign at the moment. you need his version of twrp 2.6 or as i know the cwm version 6.0.4.7, which can be found somewhere in the development forum.
tonyps cm11 : tonyps Cm11
kowalski kernel: kowalski kernel by pengus
dl links: cm11 by tonyp and bs86
working twrp by tonyp

They are New Bootloader only! The process seems as easy as full wipe + flash the zip (my phone came with ROM Manager 4.5.0.1 with old recovery) but I fear my bootloader in incompatible. Is there a way to update or something.
Also does my sd card and all applications get removed, and how to back them up, also if I brick my device does the recovery still work to flash the back up or what? very noob I know, I learned alot of terms but never managed to make good sense of it all, thank you.............
Oh one minute my ROM Manager has an Install ROM from SD Card button, can I do it right inside ROM Manager?

xdaCyborg said:
They are New Bootloader only! The process seems as easy as full wipe + flash the zip (my phone came with ROM Manager 4.5.0.1 with old recovery) but I fear my bootloader in incompatible. Is there a way to update or something.
Also does my sd card and all applications get removed, and how to back them up, also if I brick my device does the recovery still work to flash the back up or what? very noob I know, I learned alot of terms but never managed to make good sense of it all, thank you.............
Oh one minute my ROM Manager has an Install ROM from SD Card button, can I do it right inside ROM Manager?
Click to expand...
Click to collapse
With that you can backup/resotre and change the bootloader and alot more AiO-Toolkit
If you change the bootloader layout, as i know all stuf will be removed. so make a nandroid backup, if your new rom is not working and make a sdcard backup(also in aio) to get appdata back if you want.
If you dont want to download all apps new after having new rom use titanium backup. the recovery is not breakable. it will always work. not important if you **** your rom

xdaCyborg said:
They are New Bootloader only! The process seems as easy as full wipe + flash the zip (my phone came with ROM Manager 4.5.0.1 with old recovery) but I fear my bootloader in incompatible. Is there a way to update or something.
Also does my sd card and all applications get removed, and how to back them up, also if I brick my device does the recovery still work to flash the back up or what? very noob I know, I learned alot of terms but never managed to make good sense of it all, thank you.............
Oh one minute my ROM Manager has an Install ROM from SD Card button, can I do it right inside ROM Manager?
Click to expand...
Click to collapse
As you do have CM 7.1 installed, I guess you've got a custom recovery installed too? I don't think you can directly use ROM manager to install a kernel, but you can use ROM manager to boot into recovery mode and flash the zip from there Just be sure to make a nandroid backup, just in case KK isn't compatible with 7.1.
If you ever want to get tonyp's CM 11 though, the AIO toolkit, as @Zubeplanet pointed out, is really easy to use to get the new bootloader.
Happy flashing!

[Q] codinMetroPCS???

I can't seem to find a recovery that will flash a rom for MY phone. I have the MetroPCS version/variant of the sgh-t599n and I really want to be able to flash a custom rom to my phone, but I can't seem to find anyone with (codinMetroPCS) files for it. The only reason I say that is because when I finally got CWM 6.0.3.2 downloaded and working, tried to flash beanstalk rom and it told me "THIS ROM IS FOR CODINALTE PHONES NOT CODINMETROPCS PHONES" Is there a different rom for the Metro phones? Or am I doing something wrong....Im rooted through cydiaimpactor, well, i guess technically through the pre-rooted stock rom I had to flash through Odin...BTW-Over the last two weeks I've learned that flashing a rom on a samsung (at least mine) takes a custom recovery, which needs to be flashed via Odin (something I didn't know how to do at the time)...I almost feel like Im starting to get confused with all these different programs needed to run or flash or download this or that....I'm not sure if the info is even in the correct order in my head......could someone please walk me through this? or call me! lmao...this is giving me a headache. lol....but I REALLY REALLY want to know what Im doing.....ANYONE? PLEASE??

Cdbarron727 said:
I can't seem to find a recovery that will flash a rom for MY phone. I have the MetroPCS version/variant of the sgh-t599n and I really want to be able to flash a custom rom to my phone, but I can't seem to find anyone with (codinMetroPCS) files for it. The only reason I say that is because when I finally got CWM 6.0.3.2 downloaded and working, tried to flash beanstalk rom and it told me "THIS ROM IS FOR CODINALTE PHONES NOT CODINMETROPCS PHONES" Is there a different rom for the Metro phones? Or am I doing something wrong....Im rooted through cydiaimpactor, well, i guess technically through the pre-rooted stock rom I had to flash through Odin...BTW-Over the last two weeks I've learned that flashing a rom on a samsung (at least mine) takes a custom recovery, which needs to be flashed via Odin (something I didn't know how to do at the time)...I almost feel like Im starting to get confused with all these different programs needed to run or flash or download this or that....I'm not sure if the info is even in the correct order in my head......could someone please walk me through this? or call me! lmao...this is giving me a headache. lol....but I REALLY REALLY want to know what Im doing.....ANYONE? PLEASE??
Click to expand...
Click to collapse
Just flash the recovery listed in the BeanStalk thread.
There's 3 variants of the phone; T599, T599N, T599V (codinatmo, codinametropcs/codinanewcotmo, codinavid) they're pretty much the same exact phone, there's just slight differences in proprietary files - so the developers decided to unify the all of them into one (codinalte), as it's easier to build for one phone then three seperate times. The recovery's responsible for the phone; which is why the recovery plays a key-role, basically the recovery you have right now can only accept roms that are specifically 'titled' as codinametropcs, and by flashing that recovery, you'll be able to flash any of the 4.4.x roms (BeanStalk, Vanir, OmniROM, CM, AOKP, and soon pure-vanialla AOSP).

ok so....
Exothermic said:
Just flash the recovery listed in the BeanStalk thread.
There's 3 variants of the phone; T599, T599N, T599V (codinatmo, codinametropcs/codinanewcotmo, codinavid) they're pretty much the same exact phone, there's just slight differences in proprietary files - so the developers decided to unify the all of them into one (codinalte), as it's easier to build for one phone then three seperate times. The recovery's responsible for the phone; which is why the recovery plays a key-role, basically the recovery you have right now can only accept roms that are specifically 'titled' as codinametropcs, and by flashing that recovery, you'll be able to flash any of the 4.4.x roms (BeanStalk, Vanir, OmniROM, CM, AOKP, and soon pure-vanialla AOSP).
Click to expand...
Click to collapse
?
When you say flash....you mean through Android System Recovery (stock recovery)? right? ....sry man...back when i was rooting my droid x, I never ran into any issues and it seemed a little easier to flash roms

Cdbarron727 said:
?
When you say flash....you mean through Android System Recovery (stock recovery)? right? ....sry man...back when i was rooting my droid x, I never ran into any issues and it seemed a little easier to flash roms
Click to expand...
Click to collapse
flash it through odin.

Thank you....now....I think I've actually gotten this far already.....had cwm installed...then tried to flash beanstalk with cwm and I got the codin error saying "this is not for codinmetropcs" ...if I get that problem again...is there something conflicting with it in some way? Or where did I go wrong? do i have to have twrp?

sorry to bug bro
Exothermic said:
Just flash the recovery listed in the BeanStalk thread.
There's 3 variants of the phone; T599, T599N, T599V (codinatmo, codinametropcs/codinanewcotmo, codinavid) they're pretty much the same exact phone, there's just slight differences in proprietary files - so the developers decided to unify the all of them into one (codinalte), as it's easier to build for one phone then three seperate times. The recovery's responsible for the phone; which is why the recovery plays a key-role, basically the recovery you have right now can only accept roms that are specifically 'titled' as codinametropcs, and by flashing that recovery, you'll be able to flash any of the 4.4.x roms (BeanStalk, Vanir, OmniROM, CM, AOKP, and soon pure-vanialla AOSP).
Click to expand...
Click to collapse
I just flashed cwm through odin and it passed....I havn't rebooted just yet, but I know it was working before.... But just saw that the cwm I downloaded from the beanstalk thread says its for kitkat builds only. My phone is running 4.1.2..does that matter? or does that mean I just need a 4.4 rom to be flashed with it? Sorry if these are dumb questions

Cdbarron727 said:
I just flashed cwm through odin and it passed....I havn't rebooted just yet, but I know it was working before.... But just saw that the cwm I downloaded from the beanstalk thread says its for kitkat builds only. My phone is running 4.1.2..does that matter? or does that mean I just need a 4.4 rom to be flashed with it? Sorry if these are dumb questions
Click to expand...
Click to collapse
It's cool; it just means you can only flash 4.4 roms, so you cannot flash cm10.1, cm10.2, and pac. It doesn't matter that your phone's running 4.1.2.

[Q&A] [FXZ][OTA]Nexus 6 Recovery Flashable Fastboot Files (Unlocked Bootloader Only)

[Q&A] [FXZ][OTA]Nexus 6 Recovery Flashable Fastboot Files (Unlocked Bootloader Only)
Q&A for [FXZ][OTA]Nexus 6 Recovery Flashable Fastboot Files (Unlocked Bootloader Only)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [FXZ][OTA]Nexus 6 Recovery Flashable Fastboot Files (Unlocked Bootloader Only). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

A Noob needs Help
Hi guys, I am running custom 5.1 ROM (Chroma) with a no-force-encrypt kernal. I am on metropcs (t-mobile) network. Which one of these files do I need to flash in order to update to the 5.1 radio, and how do i do it so I can keep my current rom and kernal? I am currently running 2.55.04p baseband. Thanks guys!

so if I understand correctly this is a flashable package to ota future updates without flashing back to stock or flashing stock recovery IMG?
Sent from my Nexus 6 using Tapatalk

Been reading all night on how to upgrade to 5.1 without a computer by just using my phone, I wanna flash a custom 5.1 ROM, so I was wondering if I flash the files here and I get to the completely stock 5.1 (Besides the recovery) ROM after its all up and running if i can go back into TWRP and flash "BlissPop 5.1" and everything will work fine? So what I'm asking is can I go from BlissPop5.0.2 to Completely stock 5.1 to BlissPop 5.1? Thanks

OK so I'm about to flash this to go back to stock, I'm downloading the TMo version, so I download the stock ROM file, the stock recovery zip, and the decrypt zip file?
Then I flash in this order:
ROM
Recovery
Decrypt
Correct?
---------- Post added at 01:53 AM ---------- Previous post was at 01:52 AM ----------
owyheendn said:
Been reading all night on how to upgrade to 5.1 without a computer by just using my phone, I wanna flash a custom 5.1 ROM, so I was wondering if I flash the files here and I get to the completely stock 5.1 (Besides the recovery) ROM after its all up and running if i can go back into TWRP and flash "BlissPop 5.1" and everything will work fine? So what I'm asking is can I go from BlissPop5.0.2 to Completely stock 5.1 to BlissPop 5.1? Thanks
Click to expand...
Click to collapse
Yes you should, add long as you're on 5.1 you can then flash Bliss 5.1

Lrx22c -> lmy47d ?
Sorry if this is a stupid question, but I currently have 5.0.1 LRX22C running on my phone. Is it safe to download the LMY47D and flash it?
Thanks

THANK YOU SO MUCH!!!
i was struggling big time trying to figure out how to get fastboot to work. tried different things and nothing worked.
flashed this zip and i am finally on 5.1 !! woop woop!
make sure you follow the instructions:
On device option:
Copy update zip to internal storage
Reboot into recovery
Wipe system, cache, and dalvik-cache (data wipe is optional)
Install zip
Profit
and NO DATA will be lost.
---------- Post added at 01:07 AM ---------- Previous post was at 01:04 AM ----------
robputer said:
Sorry if this is a stupid question, but I currently have 5.0.1 LRX22C running on my phone. Is it safe to download the LMY47D and flash it?
Thanks
Click to expand...
Click to collapse
definitely. thats what i did. i flashed LMY47D from 5.01 and i am currently running 5.1 on vzw. let me know if you have any questions

I have the same question that was mentioned above but I don't think it was answered. I have at&t I am currently running 5.1 Benzo Rom, I did not do anything special to upgrade to 5.1 from 5.0 5.01, just found a rom that was on 5.1 that I liked and cleaned flashed. But I have noticed that my data LTE is spoty and battery life is horrible and has been on the 3-4 different 5.1 roms. Question is should I flash any of this that might help, that I didn't do going up to 5.1? Thank you for the help!

[/COLOR]Ok, i've had a read through this forum.
Just want to double check as i don't want to stuff it up.
I'm on Chroma 5.1.1 Build LMY47V
I'd like to go back to stock rom, with TWRP still intact and Decrypted and Rooted.
As far as i understand I follow these steps.
1. Download this (link on first post)
LMY47E (vzw)
http://batakang.com/ftp/devs/mhous33...MY47E-full.zip
2. Download this
no force encryption boot (optional):
http://forum.xda-developers.com/nexu...ernel-t3000788
3. Download SU zip. (already have on device)
4. Boot to recovery.
5. Wipe device. (default TWRP wipe device options ok?)
6. Install stock rom from point 1.
7. Install decrypt from point 2.
8. Install SU from point 3.
9. Reboot to system and grin.
I guess the other question is will this wipe EVERYTHING from the device, or is it just like installing any custom rom, which would leave all my Titanium Backups, photos etc on the device.
Thanks heaps

Is Verizon still stuck with 98 or does newer radio work, better?

713brianp27 said:
Is Verizon still stuck with 98 or does newer radio work, better?
Click to expand...
Click to collapse
Flash it and try it. I am running it on Sprint and it works fine.

Evolution_Tech said:
Flash it and try it. I am running it on Sprint and it works fine.
Click to expand...
Click to collapse
I did. No real difference. Probably just enhanced 95for a T-Mobile fix. They seem to be the only ones getting updates. Either Google messed up or TMobile but as far as I know, Verizon, ATT, and Sprint haven't got any OTAs.

jason3w said:
[/COLOR]Ok, i've had a read through this forum.
Just want to double check as i don't want to stuff it up.
I'm on Chroma 5.1.1 Build LMY47V
I'd like to go back to stock rom, with TWRP still intact and Decrypted and Rooted.
As far as i understand I follow these steps.
1. Download this (link on first post)
LMY47E (vzw)
http://batakang.com/ftp/devs/mhous33...MY47E-full.zip
2. Download this
no force encryption boot (optional):
http://forum.xda-developers.com/nexu...ernel-t3000788
3. Download SU zip. (already have on device)
4. Boot to recovery.
5. Wipe device. (default TWRP wipe device options ok?)
6. Install stock rom from point 1.
7. Install decrypt from point 2.
8. Install SU from point 3.
9. Reboot to system and grin.
I guess the other question is will this wipe EVERYTHING from the device, or is it just like installing any custom rom, which would leave all my Titanium Backups, photos etc on the device.
Thanks heaps
Click to expand...
Click to collapse
Post #7 maybe can help you

Doh. Been posting in main thread - Sorry.
Can't get T-Mobile Wifi - calling to work...
Ok here's what I've done.
was on 'I' stock image
installed bootloader / radio / Nocturnal ROM 5.1.1
WIFI-Calling is enabled, but not working.
I am unencrypted.
Is this file able to be installed at this point of the process...
LYZ28E (5.1.1 TMO)
http://batakang.com/ftp/devs/mhous33...YZ28E-full.zip
And does this encrypt?

Doubt it. Could always flash a decrypted kernel after ROM if it makes you feel better. I've only got encrypted once. Thanks to CM
---------- Post added at 02:40 PM ---------- Previous post was at 02:37 PM ----------
What's the deal with TMO anyway. 2nd "special" update for them while the rest of us are still running same radio.

713brianp27 said:
Doubt it. Could always flash a decrypted kernel after ROM if it makes you feel better. I've only got encrypted once. Thanks to CM
---------- Post added at 02:40 PM ---------- Previous post was at 02:37 PM ----------
What's the deal with TMO anyway. 2nd "special" update for them while the rest of us are still running same radio.
Click to expand...
Click to collapse
Flash the radio and bootloader. I did and I'm on Sprint.

Im on att can i flash the new tmo bootloader ?

Mervingio said:
Post #7 maybe can help you
Click to expand...
Click to collapse
Are you trying to decrypt?

I got my phone from Google Play and am currently on the LMY47D build (rooted).
Can someone point me in the right direction or provide instructions for upgrading to the 5.1.1 T-Mobile build (LYZ28E)?

ArmoredCavalry said:
I got my phone from Google Play and am currently on the LMY47D build (rooted).
Can someone point me in the right direction or provide instructions for upgrading to the 5.1.1 T-Mobile build (LYZ28E)?
Click to expand...
Click to collapse
Just follow the instructions at http://forum.xda-developers.com/showpost.php?p=59728002&postcount=1
But in summary,
Download the file linked by "LYZ28E (5.1.1 TMO)" at that post to your phone's storage
Reboot into recovery
Wipe system, cache, and dalvik-cache (data wipe is optional)
Install zip
Reboot

Good start ?

Hi all, glad to find this
I have ..., guess what ? a RAZR i (Ok, it's a friend's one) that I repaired changing the mad battery after factory resets didn't do anything. Then found OTA was available, applied and the RAZR i was 4.1.2 IIRC and the new battery went OK. My mistake, another OTA went soon, which I applied too, making the RAZR i a 4.4.2 kitkat piece of crap (no more write access to sdcard, this is well known ... by the ones aware , know I'm one).
Then I thought I could make the phone free and search the web for days to try to understand, found a french forum which said I can't do anything without unlocking the bootloader, what I did.
They directed me there to remove the boot-logo-warning but that's a razr hd thread and nothing worked for me. I can't remember where I read I should have CWM to do this, but as the french guy said he rather like twrp I didn't do anything at the moment, only failed to flash some logo from fastboot with various errors....
Well, I'm there, and it's cool because I hope this is the good place to have answers to questions that are still in my mind for years, and 2/3 new ones... fortunately they'll overlap and self-resolve once I get one. I'm not at all skilled in android, I only flashed a phone in 2010 and that's why I still have android SKD in my ubuntu (I also have a xp box, but I couldn't do anything for my old Acer LiquidMT). As you see, I'm a vintage things amateur (... okay, I'm vintage too).
Now the scene is built, please let me dare ask what still puzzles me :
1) For the Razr i 4.4.2 (french from sfr-vodafone kia20.74 now used with another carrier) do I have to search a specifically dedicated recovery ? Parsing this RAZR i Q&A, I found twrp seems to the preferred recovery, but I'd rather like to get confirmation from skilled ones, and also for version.
2) And please tell me if I'm wrong thinking the [RECOVERY] Unofficial TWRP 3.0.2-0 thread aim is to bring support to the RAZR i which is not supported by official teamw.in ? (BTW, @Hazou, the 1st link in the thread - DataMedia - is dead)
3) Assumed I have to go the TWRP way and I only have currently the stock recovery, do I guess right the only way is download img.zip and extract then do
Code:
./fastboot flash recovery recovery.img
, then only after that the phone can be rooted ?
4) You see I'm puzzled here because I still don't have understood the logical path: is this one the good ? unlock boot loader -> fastboot flash reco -> is the device rooted at this point ? If not, install su from recovery option "install zip from sdcard", then it's done and I get a so called "rooted stock ROM" ? Then only I can figure installing a custom ROM if exists for the RAZR i ?
5) And I should always flash a custom ROM based on the same 4.4.2 android release as my current stock one AND disable OTA updates ?
I read so many threads with guys having issues with hard-bricked RAZR i and all are about ICS and JB, so I wander the only custom are for ICS or JB, and still don't understand why they want to revert back.
Thanks for advices.

1stStep said:
Hi all, glad to find this
I have ..., guess what ? a RAZR i (Ok, it's a friend's one) that I repaired changing the mad battery after factory resets didn't do anything. Then found OTA was available, applied and the RAZR i was 4.1.2 IIRC and the new battery went OK. My mistake, another OTA went soon, which I applied too, making the RAZR i a 4.4.2 kitkat piece of crap (no more write access to sdcard, this is well known ... by the ones aware , know I'm one).
Then I thought I could make the phone free and search the web for days to try to understand, found a french forum which said I can't do anything without unlocking the bootloader, what I did.
They directed me there to remove the boot-logo-warning but that's a razr hd thread and nothing worked for me. I can't remember where I read I should have CWM to do this, but as the french guy said he rather like twrp I didn't do anything at the moment, only failed to flash some logo from fastboot with various errors....
Well, I'm there, and it's cool because I hope this is the good place to have answers to questions that are still in my mind for years, and 2/3 new ones... fortunately they'll overlap and self-resolve once I get one. I'm not at all skilled in android, I only flashed a phone in 2010 and that's why I still have android SKD in my ubuntu (I also have a xp box, but I couldn't do anything for my old Acer LiquidMT). As you see, I'm a vintage things amateur (... okay, I'm vintage too).
Now the scene is built, please let me dare ask what still puzzles me :
1) For the Razr i 4.4.2 (french from sfr-vodafone kia20.74 now used with another carrier) do I have to search a specifically dedicated recovery ? Parsing this RAZR i Q&A, I found twrp seems to the preferred recovery, but I'd rather like to get confirmation from skilled ones, and also for version.
2) And please tell me if I'm wrong thinking the [RECOVERY] Unofficial TWRP 3.0.2-0 thread aim is to bring support to the RAZR i which is not supported by official teamw.in ? (BTW, @Hazou, the 1st link in the thread - DataMedia - is dead)
3) Assumed I have to go the TWRP way and I only have currently the stock recovery, do I guess right the only way is download img.zip and extract then do
Code:
./fastboot flash recovery recovery.img
, then only after that the phone can be rooted ?
4) You see I'm puzzled here because I still don't have understood the logical path: is this one the good ? unlock boot loader -> fastboot flash reco -> is the device rooted at this point ? If not, install su from recovery option "install zip from sdcard", then it's done and I get a so called "rooted stock ROM" ? Then only I can figure installing a custom ROM if exists for the RAZR i ?
5) And I should always flash a custom ROM based on the same 4.4.2 android release as my current stock one AND disable OTA updates ?
I read so many threads with guys having issues with hard-bricked RAZR i and all are about ICS and JB, so I wander the only custom are for ICS or JB, and still don't understand why they want to revert back.
Thanks for advices.
Click to expand...
Click to collapse
Hey 1stStep,
A lot off assumptions and questions. And most of them are right.
1. Afaik there are 2 recoveries for the RAZR I. Stock and my build TWRP 3.0.2-0 unofficial. (Thanks for the heads up about the link)
2. Answered in 1.
3. Yep. If your bootloader is unlocked it gives u the function to flash non-stock firmware to the phone. Stock firmware are signed to prevent normal users flashing wrong firmware. Firmware consist of a couple of images. Those images contain data for the partition, just like in your PC. Every image does something else. Most known are boot, data, system, recovery and cache. There are many more. Some needed, some unnecessary.
To answer your question: when u have flashed the TWRP recovery u override the stock one. The TWRP can flash zip files and images to the most known device partitions. From here on u can flash a superuser zip(gives root access on the current ROM/system). Make sure u have the right superuser zip. There are many.
4.
Path to root on stock:
Unlock bootloader->install custom recovery (TWRP)->install superuser zip->reboot and test root on device
Path to custom ROM:
Unlock bootloader->install custom recovery (TWRP)->install ROM zip and extra's if needed like (Gapps(needed for Google playstore and more))->reboot and play with your new ROM.
Off course if u already have the bootloader unlocked and installed a custom recovery, u can skip those.
In the recovery u can also make backups, called nandroid backup. Read up on them and everything u wanna do.
5. The only thing u never want/should do is flashing Android 4.0.4 stock firmware without prior modifications. This is because from 4.0.4 to 4.1.2 there was a change in bootloader (the thing u unlock). If u go back it corrupt a part of the firmware which is difficult to overcome or even impossible without some factory stuff. Everything above 4.1.2 is save. And can always be flashed. The latest stock is 4.4.2 (KIA 20.74) and latest available custom ROM is 4.4.4 (CM11 or soon Lineage 11).
Good luck!

Thanks so mush great dev to spend time and even surely repeat yourself (hope you're not under stress) for a newb.
In your answer for path to custom ROM you say "Unlock bootloader->install custom recovery (TWRP)->install ROM zip and extra's if needed like".
Do I have to understand custom ROMs are yet rooted (OOTB), or root yet made on stock will survive flashing the custom (I though flashing a custom was some kind of infant clear brain graft?
BTW, is it general good advice to test recovery before flashing? I found this in Moto Play unofficial recovery 3.0.2-r5 from Vache:
Code:
fastboot boot recovery.img
?
Thanks again

1stStep said:
Thanks so mush great dev to spend time and even surely repeat yourself (hope you're not under stress) for a newb.
Click to expand...
Click to collapse
Not at all , just replying if I have some time.
1stStep said:
In your answer for path to custom ROM you say "Unlock bootloader->install custom recovery (TWRP)->install ROM zip and extra's if needed like".
Do I have to understand custom ROMs are yet rooted (OOTB), or root yet made on stock will survive flashing the custom (I though flashing a custom was some kind of infant clear brain graft?
BTW, is it general good advice to test recovery before flashing? I found this in Moto Play unofficial recovery 3.0.2-r5 from Vache:
Code:
fastboot boot recovery.img
?
Thanks again
Click to expand...
Click to collapse
- Most custom roms are prerooted.
- Cyanogenmod/LineageOS are prerooted
- Root installed by a zip will not survive any system flashing (rom flashing)
- Any modification to your system partition will not survive and system flashing (rom flashing), though 1 exception:
- installed gapps package (google apps/play store etc.) will survive system flashing on cyanogenmod based roms. But only when updating the rom to a newer version on the same android version. So:
CM11 version 1 to CM11 version 2. (because of a special script in the install zip)
Pre testing a boot or recovery image is blocked on our bootloader. So u can't do it. It's a shame they did it. Working on any boot or recovery changes is a pain in the spoken ass.
If u flash the recovery with:
Code:
fastboot flash recovery recovery.img
there is nothing to be afraid off. The TWRP 3.0.2-0 recovery is well tested on this device.

Thank you again man for all detailed answer.
You're right, it's a shame all these locked things in our phones. I'm sure the guys that agree (our security, blah blah) with these ways to do won't be so happy the day their computers will be locked the same way.
bye bye Hazou.
[Edit] .... hmmm, how long does it take to flash? Yet a 1/4h elapsed and razr still says "Flashing recovery..."
Please, what is the md5 of the image (not the zip, this you give us)? Thanks
[Edit] : Downloaded twice and get md5sum 60dff26f3ee5e9338ee4a6f8cf7df098
but still same forever Flashing recovery ...
[Edit] : I've been puzzled for days being stuck in endless "Flashing recovery ..."
In the ended I decided, after saying 1 hour waiting a hypothetical "success/congrats message", NOT QUITTING the current fastboot screen, to select the recovery option in this very fastboot menu (on a Razr i : Vol- to highlight recovery item, then Vol+ to select) and bang I was in TWRP menu. What to do next once in, it is another story.