Rooted, SndInit... What now? - Defy Q&A, Help & Troubleshooting

Well, not exactly what, but how... This is my first locked device and have read the beginners guide for 2 months now but still a bit confused...
My device runs Froyo and already did a backup... I plan to install CM9... Does my backup work? Should I install GB sbf and go from there?
Sent from my MB525 using Tapatalk 2

dbarrera said:
Well, not exactly what, but how... This is my first locked device and have read the beginners guide for 2 months now but still a bit confused...
My device runs Froyo and already did a backup... I plan to install CM9... Does my backup work? Should I install GB sbf and go from there?
Sent from my MB525 using Tapatalk 2
Click to expand...
Click to collapse
You did a NAND backup?
You could test your backup by doing a Wipe data , boot into stock to verify phone is wiped, then reboot into recovery and restore your NAND backup. That will give you some sense of security.
Then wipe data again and install the ROM of your choice.
DONT INSTALL A GB SBF on a MB525 - you will never be able to go back to Stock Froyo! .... Of course you already knew this if you read the beginners guide!!!

_ossie_ said:
You did a NAND backup?
You could test your backup by doing a Wipe data , boot into stock to verify phone is wiped, then reboot into recovery and restore your NAND backup. That will give you some sense of security.
Then wipe data again and install the ROM of your choice.
DONT INSTALL A GB SBF on a MB525 - you will never be able to go back to Stock Froyo! .... Of course you already knew this if you read the beginners guide!!!
Click to expand...
Click to collapse
Yes, a NAND backup with CWM... And the data backup is not what worries me, but the system partition backup...
LOL, yes I got that last part... But as I'm using my device overseas from where I bought it, kinda not that worried about it...
Sent from my MB525 using Tapatalk 2

dbarrera said:
Yes, a NAND backup with CWM... And the data backup is not what worries me, but the system partition backup...
LOL, yes I got that last part... But as I'm using my device overseas from where I bought it, kinda not that worried about it...
Sent from my MB525 using Tapatalk 2
Click to expand...
Click to collapse
OK Do you have a stock SBF file for your ROM?
If so, flash that to prove you can return to stock if you like.
Then re-root, reinstall CWM, reinstall your backup to prove you can do that.
Then wipe, install CM9, and play with it.
If you don't like it, recover your NAND backup.
If you don't have a current stock SBF for your ROM, then try to obtain a "fixed" SBF which you can use to restore your system in case you ever screw it up. Then the process would be to re-root, reinstall CWM and recover your original NAND backup.

_ossie_ said:
OK Do you have a stock SBF file for your ROM?
If so, flash that to prove you can return to stock if you like.
Then re-root, reinstall CWM, reinstall your backup to prove you can do that.
Then wipe, install CM9, and play with it.
If you don't like it, recover your NAND backup.
If you don't have a current stock SBF for your ROM, then try to obtain a "fixed" SBF which you can use to restore your system in case you ever screw it up. Then the process would be to re-root, reinstall CWM and recover your original NAND backup.
Click to expand...
Click to collapse
I don't have the stock sbf for the ROM that came loaded, and the list for official sbf files doesn't have it...
Where can I obtain a fixed sbf? I read that the process to install a fixed sbf is a bit different but its confusing how it is written in the guide...
Sent from my MB525 using Tapatalk 2

dbarrera said:
I don't have the stock sbf for the ROM that came loaded, and the list for official sbf files doesn't have it...
Where can I obtain a fixed sbf? I read that the process to install a fixed sbf is a bit different but its confusing how it is written in the guide...
Sent from my MB525 using Tapatalk 2
Click to expand...
Click to collapse
No the process is identical. Flash with RSD Lite.
But before you flash any SBF, you need to know which version of Bootloader you are on. You canot flash a full SBF with a lower Bootloader version. But you can flash any fixed SBF - you may need a matching NAND backup for the SBF you flash.
As you are not interested in returning your phone to stock for warranty purposes, you probably won't need to flash ANY SBF for the time being, unless you get stuck.
So you can jump in and flash CM9 or whatever ROM.

_ossie_ said:
No the process is identical. Flash with RSD Lite.
But before you flash any SBF, you need to know which version of Bootloader you are on. You canot flash a full SBF with a lower Bootloader version. But you can flash any fixed SBF - you may need a matching NAND backup for the SBF you flash.
As you are not interested in returning your phone to stock for warranty purposes, you probably won't need to flash ANY SBF for the time being, unless you get stuck.
So you can jump in and flash CM9 or whatever ROM.
Click to expand...
Click to collapse
There, that's the thing that confuses me "a matching nand backup"... Can you elaborate on that?
Sent from my MB525 using Tapatalk 2

dbarrera said:
There, that's the thing that confuses me "a matching nand backup"... Can you elaborate on that?
Sent from my MB525 using Tapatalk 2
Click to expand...
Click to collapse
I'm no expert but here goes:
A Nandroid backup is a backup of EVERYTHING.
Similarly, flashing a full SBF overwrites everything (well, almost!)
The full SBF contains a full self-consistent set of CG files.
A fixed SBF is missing some CG files (CG31 and CG39 deliberately omitted to circumvent version checking) so it allows for example "downgrading".
When flashing a full SBF you'll have no problems because you have a consistent system. No Nandroid restore is required, unless you want to get some data back. You can restore a backup if you want to.
However if you flash a "fixed" SBF you MAY need to also restore a Nandroid backup to restore the CG31 and CG39 bits that match the rest of the SBF (assuming you have changed versions). This Nandroid must be compatible with the fixed SBF you flashed. If not, it won't brick your Defy, but maybe it won't boot. So you'll be back to flashing an SBF to fix it.
You don't always have to use a Nandroid backup with fixed SBFs - it really depends on what's on your system and where you are trying to go.
Since you know your base SBF - you won't need any fixed SBFs or "matching backups" (aka custom Nandroids) unless you try to downgrade your system for some reason - just have a factory SBFon hand in case you ever need to go back to stock.

So, for example, if I install CM and want to go back to Froyo, I install a Froyo fixed sbf and use my backup to restore /system ?
Sent from my MB525 using Tapatalk 2

dbarrera said:
So, for example, if I install CM and want to go back to Froyo, I install a Froyo fixed sbf and use my backup to restore /system ?
Sent from my MB525 using Tapatalk 2
Click to expand...
Click to collapse
You won't need to restore system. If you flash a Froyo fixed SBF you'll have a Froyo system!
If you restore a nandroid backup you'll get the exact same system you backed up. (Froyo or whatever).
You can also selectively restore (system, data, boot, recovery, logo ... ) from your nandroid backup but this might yield unexpected results.
If you install CyanogenMod, you can just restore your (Froyo) nandroid backup from recovery and you'll be back to Froyo - no need to flash an SBF unless something screws up.

Then what's the deal with the eFuse? Installing CM9 doesn't make my device going up in CG version, does it?
Sent from my MB525 using Tapatalk 2

dbarrera said:
Then what's the deal with the eFuse? Installing CM9 doesn't make my device going up in CG version, does it?
Sent from my MB525 using Tapatalk 2
Click to expand...
Click to collapse
Nope. Only flashing a full SBF with a later CG version.

That gives me some confidence to take the plunge... Here we go...
Sent from my MB525 using Tapatalk 2

So I went, I saw and was conquered... Sorta...
Installed CM9, played with it for a while and now the screen (digitizer) doesn't recognize my input... What I did? In CM9 I elevated the points of I don't remember what (it has to do with the number of simoultaneous finger pressing being recognized) from default (2) to 4... But I went back to default and screen stopped responding... Thought it was SW issue, restored to my Froyo backup; no luck, still unresponsive... So the "bug" went from SW to HW issue... What went wrong?
Planning on flashing Froyo sbf and for my version, there are a whole lot of options... Whats all the fuss about CEE version? The original OS that was loaded didn't have any brand from any carrier, should I go for the ones that say Retail in the SBF list? Must I go with a fixed version?
Thanks in advance to anyone who answers any of my questions...

Related

SBF vs Nandroid vs madderstcok vs ?

What is the best/easiest method to return to out of the box stock and how do you do it?
-I've never used sbf.
-I have a nandroid backup of stock ota 2.2.1 but reverting back to it still leaves somethings like the liberty text when first booting up.
-To my understanding madderstock is a .zip file that you just flash the same a rom. Is that correct?
-Is there something better/easier?
Thanks
Sent from my DROIDX using XDA App
Jon El Canche said:
What is the best/easiest method to return to out of the box stock and how do you do it?
-I've never used sbf.
-I have a nandroid backup of stock ota 2.2.1 but reverting back to it still leaves somethings like the liberty text when first booting up.
-To my understanding madderstock is a .zip file that you just flash the same a rom. Is that correct?
-Is there something better/easier?
Thanks
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
just use the sbf
it takes a bit longer than flashing a .zip file but its better imo
Sbf is the only way to get to pure stock imo its super easy check out my video tutorial
http://www.youtube.com/watch?v=N0jrXqqiepI&feature=youtube_gdata_player
Sent from my DROIDX using XDA App
SBF is generally the most "100%" way to get completely back to stock... However if you are more comfortable flashing a zip file, then maderstcok is the way to go... Does the same thing as the 2.3.340 system only sbf.
SysAdmin-X said:
SBF is generally the most "100%" way to get completely back to stock... However if you are more comfortable flashing a zip file, then maderstcok is the way to go... Does the same thing as the 2.3.340 system only sbf.
Click to expand...
Click to collapse
If flashing the .zip does the same thing as the sbf why is the sbf better, or the only thing that is 100%. What is the difference?
Sent from my DROIDX using XDA App
Jon El Canche said:
If flashing the .zip does the same thing as the sbf why is the sbf better, or the only thing that is 100%. What is the difference?
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
It kind depends on the situation that you are in. If you have only messed up the /system portion of the phone, then flashing the zip is easier for those who aren't super android savvy. You just run the zip file, and when it finishes, it achieves the same result as the sbf, but that is only for the /system portion of the phone.
The reason I say the SBF is the best way to "100%" redo your phone is the sbf is an official moto file. If you download the latest full sbf, it completely wipes your current phone image and then loads the default image on the phone, leaving no remains of you phone prior to the sbf.
That make a little more sense?
Ya that's great, thanks. And thanks for the video Owenbeals.
Sent from my DROIDX using XDA App
Glad I could help!
Sent from my DROIDX using XDA App
maderstcok does more them just the system folder, it just doesn't do it the same way as SBF does (from the devs that made it: This is the FULL, OTA 2.3.340 - contains radio, kernel, and all other updates, even those EXCLUDED by the 2.3.340 system only sbf.).
If you can reboot into bootstrap recovery maderstcok is fine, if not the SBF may still be able to fix your phone. Just remember if you flash maderstcok or sbf you still have to reboot into recovery and wipe your phone for it to be bootable again.
for more info on the maderstcok:
http://www.droidforums.net/forum/droid-x-rooted-help/112152-maderstcok-ota-2-3-340-update-zip.html
Still up to you which you use but either should get it done the say way.
PS: Its a good idea to have maderstcok, z4root, the SBF, and RDS lite on your SD card incase your phone gets messed up and your not at your primary pc.
Instructions:
Using the Droid X Bootstrapper make a backup. (more information here)
Browse (using volume buttons) to "install zip from sdcard" and select it with the camera button.
Select "choose zip from sdcard".
Select "maderstcok340.zip"
Confirm the install.
Be patient, wait for the install to finish.
Reboot the Droid X. DO NOTHING ELSE IN CLOCKWORKMOD!!!!!!!
Activate the phone with VZW (more instructions below).
If you attempt to create a backup or flash a rom post maderstcok installation you're going to have a paperweight. This seems to be because maderstcok removes root and the clockworkmod recovery area, so it doesn't like you playing around in there. Re-root and reinstall the bootstrapper, then create a backup or flash a new rom, DON'T DO IT BEFORE REBOOTING THE DX AFTER ISNTALL.
Formatting Data and Cache is optional; however, if you want a really clean install do so. If you factory reset you'll be forced to activate the phone automatically while if you don't you'll have to follow the quick and dirty activation instructions below - the choice is ultimately yours.
EDIT: coming from ANY non-blur based ROM and doing Maderstcok is guaranteed to bootloop due to mismatch in framework without a data/cache wipe
__________________________________ These are the instructions for the maderstcok. In the second to last paragraph it says that if you want a really clean install you should format data and cache. When is this step performed? The last step in the list of instructions after flashing the .zip is to reboot NOT DOING ANYTHING ELSE IN CLOCKWORKMOD. So before I reboot should i wipe data and cache or do I need to re-root, run bootstrap recovery, and then wipe data and cache?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Maderstock will erase bootstrap/recovery right? I need to send my phone in to Motorola for repair. Thanks
Sent from my DROIDX using Tapatalk
These are the instructions for the maderstcok. In the second to last paragraph it says that if you want a really clean install you should format data and cache. When is this step performed? The last step in the list of instructions after flashing the .zip is to reboot NOT DOING ANYTHING ELSE IN CLOCKWORKMOD. So before I reboot should i wipe data and cache or do I need to re-root, run bootstrap recovery, and then wipe data and cache?
http://www.droidforums.net/forum/droid-x-rooted-help/112152-maderstcok-ota-2-3-340-update-zip.html
Sent from my DROIDX using XDA App
Anyone know when to wipe cache and data? Explained above
Sent from my DROIDX using XDA App

Rooted my GF's Fascinate, Need Help Nandroiding

I just rooted my girlfriend's year old fascinate that was bone stock from day 1. In CWM I am unable to make a nandroid (I get an error). I've heard I need a modded stock kernel in order to successfully make a backup in CWM 3.x or something along those lines.
I looked in the developer forum under the sticky with the list of everything, but it only shows three or so kernels (none of which hint at stock).
I have a Thunderbolt and before that a Droid 2 so I know a lot about rooting and flashing with those two devices, but I am new to the Fascinate. I messed around a bit with Odin when I rooted the phone, but I'm still learning.
Any help is greatly appreciated.
Older recoveries supported amend scripting (2.x.x) while newer ones support edify scripting (3.x.x)...depending on which rom your running it may cause problems with backups and restores if you don't have the right recovery...unless you plan on going to an Mtd build (cm7, Miui, ect) I would recommend using the (2.5.1) recovery also called the 3/30 fix all recovery because this version supports both amend and edify scripting..so you make a nandroid with out issues....if you can get to recovery still I would install this zip and then select reboot recovery...it will bring you to the 3/30 fix all recovery where you should be able to backup and restore your nandroid...link to follow shortly...
Scroll down in the first page to the .zip file, download and continue with the steps I listed...I know its confusing at first mainly because development has happens rather quickly which is a good thing! its just a lot to catch up on!
http://forum.xda-developers.com/showthread.php?t=942021
Sent from my SCH-I500 using XDA App
What would you recommend if my plan was to install MIUI or OMFGB?
I'm deciding between those two because I use OMFGB on my Thunderbolt all the time, but MIUI is very good for my girlfriend I think because it's very straight forward and simplistic.
http://forum.xda-developers.com/showthread.php?t=1124391
Its not hard to get in to these roms, but you must be sure if you have problems or want to go to anything non Mtd you will have to Odin an official VZW tar and pit file to repartition before going to any non Mtd rom
http://forum.xda-developers.com/showthread.php?t=1124391
Sent from my SCH-I500 using XDA App
So basically:
1. Flash the CWM you posted in your original reply
2. Nandroid her current stock setup
3. Flash MIUI
4. If I ever want to return to stock or a non-mtd rom I have to do what's posted in your second reply?
If all that is correct please let me know. Also lets say she doesn't like MIUI, can I simply flash that nandroid or will I have to do what's posted in the second reply?
When I try to flash that older CWM in CWM I get this message:
http://i.imgur.com/3QiwQ.jpg
want a droid said:
So basically:
1. Flash the CWM you posted in your original reply
2. Nandroid her current stock setup
3. Flash MIUI
4. If I ever want to return to stock or a non-mtd rom I have to do what's posted in your second reply?
If all that is correct please let me know. Also lets say she doesn't like MIUI, can I simply flash that nandroid or will I have to do what's posted in the second reply?
Click to expand...
Click to collapse
Yes you will have to do what's in the second reply.
You have it all correct, if you nandroid her current stock setup you can only restore it on a non Mtd build you would have to do what I linked to in the second post to use a vzw rom with pit file to repartition...boot fully, flash recovery then you could restore her stock nandroid..for example you get her on Miui you can only do a nandroid with the recovery that comes with it...I think its a 4.x.x recovery...trying to restore the stock nandroid before repartitioning back to stock will cause problems...so basically you only want to restore a nandroid on the same build (Mtd to Mtd nandroid, or ext4/rfs to ext4/rfs nandroid) and if all else fails and you run into big problems, doing the VZW restore (although can be a lengthy process) will get the phone back running to start over!
Sent from my SCH-I500 using XDA App
Did you see my reply before this? I was unable to get CWM 2.x to flash so I'm still on CWM 3.x.
want a droid said:
Did you see my reply before this? I was unable to get CWM 2.x to flash so I'm still on CWM 3.x.
Click to expand...
Click to collapse
I did see it after I replied, is her phone on ed05? I'm surprised that neither the 3/30 fix all or 3.x.x is working
Edit after looking at the pick again you're using times infinity's recovery....you would need to Odin the 3/30 fix all recovery and immediately three finger boot into recovery without letting the phone boot or if you installed the 3/30 fix all via .zip file, you need to choose reboot recovery to enter the fix all one, it should be 2.5.1 I believe
Sent from my SCH-I500 using XDA App
Here's a picture of her phone info:
http://i.imgur.com/rs1Jd.jpg
And as you can tell from the other photo, both making a backup and flashing the CWM 2.x doesn't work.
Trying a backup results in: "Error while backing up boot image!"
Trying to flash CWM 2.x results in that long information message.
That sucks man i'm sorry I've never been on ed05 so I don't know if that why your having problems my suggestion...back up all her contacts by exporting them to sd card, download titanium backup its free in the market, backup all of her apps and screw the nandroid, flash what you want, restore her apps with titanium, but do not restore data, restore get contacts and then boot into the recovery that comes with the rom/kernel and then do a nandroid and that WILL work..again sorry for the trouble, just trying to help.
Sent from my SCH-I500 using XDA App
I appreciate all your help. I'll let you know how it goes.
ed05 is not the problem...You have to use cwm 2.5.1.x if your trying to nandroid backup a stock rom. This version of cwm works on all froyo roms and powerwashed gingerbread. After you make a nandroid with cwm2.5.1.x, then flash cwm4 and proceed to installing miui.
Read this link for flashing mtd based roms such as miui, cm7, vgb...etc
http://forum.xda-developers.com/showthread.php?t=1212239
That was my first reply to him...to use 2.5.1 but he said he still got errors? I don't have a clue what the problem is...he's said he's used ti's 3x.x, and the 3/30 fix all still with errors? confused?
Sent from my SCH-I500 using XDA App
droidstyle said:
ed05 is not the problem...You have to use cwm 2.5.1.x if your trying to nandroid backup a stock rom. This version of cwm works on all froyo roms and powerwashed gingerbread. After you make a nandroid with cwm2.5.1.x, then flash cwm4 and proceed to installing miui.
Read this link for flashing mtd based roms such as miui, cm7, vgb...etc
http://forum.xda-developers.com/showthread.php?t=1212239
Click to expand...
Click to collapse
I guess you skipped the entire thread, but we already went through all that.
want a droid said:
I guess you skipped the entire thread, but we already went through all that.
Click to expand...
Click to collapse
I think you skipped a step... Are you flashin cwm via the PDA function in ODIN?
If not you need to:
ODIN the cwmAll.tar here: http://api.viglink.com/api/click?format=go&drKey=1359&loc=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D1238070&v=1&libid=1316306736482&out=http%3A%2F%2Fwww.mediafire.com%2F%3F6x5utoca59et7o9&title=%5BGUIDE%5D%20Installing%20a%20rom%2F%20cwm%20recovery%2F%20or%20going%20back%20to%20stock%20for%20NEWBIES!%20-%20xda-developers&txt=http%3A%2F%2Fwww.mediafire.com%2F%3F6x5utoca59et7o9&jsonp=vglnk_jsonp_13163071702031
make a nandroid back up of the stock rom.
go back to odin and flash the jt's cwm4
boot into recovery
wipe data, cache, dalvik
install miui.zipfrom sd card
Follow the rest of the directions in the link I provided
+1 there ya go. Beat me to it.
Plus, I wouldn't even worry about backing up your stock ROM. Just flash the full official package. This will wipe your slate clean if you run into problems. Restoring nandroid backups leads to glitches eventually from what I've seen.
Sorry, I didn't see there was a second page here...I'm a bum.
want a droid said:
I guess you skipped the entire thread, but we already went through all that.
Click to expand...
Click to collapse
Should probably try not being a **** when you're begging for help from people.
Sent from my SCH-I500 using XDA App
Personally, I thought his reply was honest and effective. I commend him on his frankness, and respect him for his boldness.
grenade01 said:
Personally, I thought his reply was honest and effective. I commend him on his frankness, and respect him for his boldness.
Click to expand...
Click to collapse
Really? Snide, snarky comments are respectable? At the very least, they shouldn't be coming from the person asking for help.
Sent from my SCH-I500 using XDA App

[Q] Help with Defy (green lens) and custom ROMS

I am currently on a stock Android 2.1-update1 TMobile US ROM on my Defy (green lens) ROM. I would like to try out CyanogenMod 7.1 (or 7.2 RC) and need help confirming my understanding of the process. I am already rooted and have installed the GoAPK recovery.
1. I need to flash my kernel to froyo to 2.2. In order to be able to downgrade back to 2.1 I need to use a "fixed" sbf. If I run the smgver.exe utility on the sbf file and it says "no version found" than this is a safe sbf to flash (can still downgrade).
2. Before I flash this new kernel I need to (should) do a full nandroid backup of my current rom so I can restore it if things go wrong. I might need to install SuperOneClickFor2.x to do the backup and future recoveries.
3. Once I flash one of these "fixed" sbf I can then do the "update.zip" process to flash CM7 onto my defy. I will need to do a factory reset and wipe the data/cache partitions. This will cause me to lose my contacts/calendar/etc AND my installed applications (and their data, so I need to back them up using something like TitaniumBackup).
4. Once I've got CM7 (with froyo kernel) I can flash one of the CM9 builds for the defy green lens that is built specifically for the froyo kernel
I've searched and read as much as I can, I feel like I "got it" but I just wanted a little confirmation before I start hacking this phone apart =)
Thanks for any help you can give me =)
Here is the explanation from all that I know:
1. I need to flash my kernel to froyo to 2.2. In order to be able to downgrade back to 2.1 I need to use a "fixed" sbf. If I run the smgver.exe utility on the sbf file and it says "no version found" than this is a safe sbf to flash (can still downgrade). Ya, that is true. But after flashing fixed SBF you also need Nandroid backup to be restored.(This is not your nandroid backup. Its the nandroid backup supplied with the fixed sbf)
2. Before I flash this new kernel I need to (should) do a full nandroid backup of my current rom so I can restore it if things go wrong. I might need to install SuperOneClickFor2.x to do the backup and future recoveries.
Yes Nandroid backup is always recommended. Superoneclick is a software needed to root your phone. That answers the rest.
3. Once I flash one of these "fixed" sbf I can then do the "update.zip" process to flash CM7 onto my defy. I will need to do a factory reset and wipe the data/cache partitions. This will cause me to lose my contacts/calendar/etc AND my installed applications (and their data, so I need to back them up using something like TitaniumBackup).
Yes, however its not update.zip but its <ROM NAME>.zip Your contacts,calender can be backed up in your google account and if you use gapps(google apps. Needs to be installed separately by install .zip in CM) in your CM those will come again. Your installed apps and data yes can be restored from TB. You can backup SMS using SMS backup+
4. Once I've got CM7 (with froyo kernel) I can flash one of the CM9 builds for the defy green lens that is built specifically for the froyo kernel
Yes either that or you can even directly flash CM9 for Froyo kernel.
Hope that helps...

[Q] TWRP won't install over CWM

I tried to install TWRP from CWM. The process goes down, it tells me to reboot recovery. I rebooted, and still, i have CWM. What should i do?
defy red lens cm9 epsylon
if youre not opposed to starting over with a fresh sbf, then do just that. this time stick to twrp. seems to be doing much better than CWM
undyingvisage58 said:
if youre not opposed to starting over with a fresh sbf, then do just that. this time stick to twrp. seems to be doing much better than CWM
Click to expand...
Click to collapse
but i can't install twrp. i just does not replace cwm, and from froyo or éclair i cant install it with goomanager. from cm9 goomanager tells my device is not supported
gyorgyszemok said:
but i can't install twrp. i just does not replace cwm, and from froyo or éclair i cant install it with goomanager. from cm9 goomanager tells my device is not supported
Click to expand...
Click to collapse
my next advice is to learn how to manage your own roms without goomanager. for the most part you can read the tutorials on the defy wiki page to install "2ndInit Recovery". then use the 2ndinit recovery to install twrp. from there you install 10.2/4.3 and enjoy. just make sure you know well how to do sbf flashes just in case you goof and softbrick your phone in the process.
plus you should be able to install goo manager once youve settled in with twrp.
undyingvisage58 said:
my next advice is to learn how to manage your own roms without goomanager. for the most part you can read the tutorials on the defy wiki page to install "2ndInit Recovery". then use the 2ndinit recovery to install twrp. from there you install 10.2/4.3 and enjoy. just make sure you know well how to do sbf flashes just in case you goof and softbrick your phone in the process.
plus you should be able to install goo manager once youve settled in with twrp.
Click to expand...
Click to collapse
You misunderstood me maybe. I never used Goomanager. The first time I did was like 2 days ago when I found out I can't install CM10.x with CWM v5, but v6 or TWRP, and tried to install TWRP from it. It didn't work. Also, the TWRP flashable zip won't install from CWM. I mean... It says it's ok and reboot recovery but nothing. Gwah I know all about sbf flashes in case of softbrick and all...
edit: im very, VERY familiar with cwm... never used any apk to manage my roms just 2ndinit to install.
gyorgyszemok said:
You misunderstood me maybe. I never used Goomanager. The first time I did was like 2 days ago when I found out I can't install CM10.x with CWM v5, but v6 or TWRP, and tried to install TWRP from it. It didn't work. Also, the TWRP flashable zip won't install from CWM. I mean... It says it's ok and reboot recovery but nothing. Gwah I know all about sbf flashes in case of softbrick and all...
edit: im very, VERY familiar with cwm... never used any apk to manage my roms just 2ndinit to install.
Click to expand...
Click to collapse
theres nothing else i can help you with then. all i can say is start from sbf flash and stay away from cm 10 2ndboot
Maybe not enough memory?
Sent from my MB526 using xda app-developers app
undyingvisage58 said:
theres nothing else i can help you with then. all i can say is start from sbf flash and stay away from cm 10 2ndboot
Click to expand...
Click to collapse
yeah... but i'd like to try it at least...
hotdog125 said:
Maybe not enough memory?
Sent from my MB526 using xda app-developers app
Click to expand...
Click to collapse
I don't think so. Something is very fishy about my phone. very-VERY strange... I can't install cm10.x cuz' of no update-binary support in cwm v5, and i can't find a way to make TWRP work, nor can I find any CWM v6 install methods... srsly WUT EVERY OTHER stuff works as intended. everything. all roms before jelly bean. i need to make twrp work or a cwm v6 installation.
gyorgyszemok said:
yeah... but i'd like to try it at least...
I don't think so. Something is very fishy about my phone. very-VERY strange... I can't install cm10.x cuz' of no update-binary support in cwm v5, and i can't find a way to make TWRP work, nor can I find any CWM v6 install methods... srsly WUT EVERY OTHER stuff works as intended. everything. all roms before jelly bean. i need to make twrp work or a cwm v6 installation.
Click to expand...
Click to collapse
Only CM10.2 needs the new CWMv6. CM10 and CM10.1 should work.
Your phone seems to trolling you:laugh:. But seriously, as a last resort I would flash DFP sbf. Gingerbread isn't half bad (especially with MS2Ginger, which is really stable and is compatible with Green Lens too).
hotdog125 said:
Only CM10.2 needs the new CWMv6. CM10 and CM10.1 should work.
Your phone seems to trolling you:laugh:. But seriously, as a last resort I would flash DFP sbf. Gingerbread isn't half bad (especially with MS2Ginger, which is really stable and is compatible with Green Lens too).
Click to expand...
Click to collapse
Well then it's trolling me 'cuz CM10 gives the same status 7 error. It IS trolling me. But i'm scared of flashing a DFP sbf. What if things go wrong? I won't be able to rollback then.
You can try to use twrp on gb roms by replacing the boot menu folder in system by that of cm10 or later. Try once with a clean folder, and once by copying over the existing files.
As for defy plus sbf, if you have a green lens, camera won't work on any gb except ms2ginger. In addition a battery patch must be flashed after every rom for full charging. For red lens only battery patch has to be flashed.
None of the above applies to cm10 and later.
Sent from my MB526 using Tapatalk 2
gyorgyszemok said:
Well then it's trolling me 'cuz CM10 gives the same status 7 error. It IS trolling me. But i'm scared of flashing a DFP sbf. What if things go wrong? I won't be able to rollback then.
Click to expand...
Click to collapse
If things go wrong, try a different SBF.
thekguy said:
You can try to use twrp on gb roms by replacing the boot menu folder in system by that of cm10 or later. Try once with a clean folder, and once by copying over the existing files.
As for defy plus sbf, if you have a green lens, camera won't work on any gb except ms2ginger. In addition a battery patch must be flashed after every rom for full charging. For red lens only battery patch has to be flashed.
None of the above applies to cm10 and later.
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
I tried replacing the bootmenu folder with different apps, but all got some "Operation failed!" or "Error with files" in itself, so I also tried to replace some of the files 1 by 1, they still failed. So that could be the reason why the zip won't flash properly... Maybe some safety option somewhere in CM9??? My phone can't seem to handle the recovery zips, only the 2ndinit apk. Very strange!
That must be done from recovery. I recall helping someone replace the recovery using a flashable zip because only a legacy recovery worked for him. I think it was zer0-gravity. Check my posts on that.
Replacing the recovery files with twrp ones in the zip I had made on that thread should with hopefully.
Also, your problems indicate file system errors, and I'll advise you to flash a different(higher) sbf, since that has in the past worked out well, for me and others. Beyond this point I'm out of ideas.
Sent from my MB526 using Tapatalk 2
thekguy said:
That must be done from recovery. I recall helping someone replace the recovery using a flashable zip because only a legacy recovery worked for him. I think it was zer0-gravity. Check my posts on that
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
another fast question. i recover my phone using the JORDN_U3_97.21.51 method, after that i have to do a root, nandroid, then instantly flash a fixed sbf (firmware.sbf...). its cuz i got the phone 2nd hand, and he f-ed up smth upgrading to gingerbread or so... can it be the root of my problem?
http://forum.xda-developers.com/showpost.php?p=14762402&postcount=143
Why do you need a fixed sbf? After rooting try directly 2ndinit. Don't restore nandroid. Also, root using framaroot since its much easier and faster. You can jump from 2.1 to
2ndboot directly.
Sent from my MB526 using Tapatalk 2
thekguy said:
Why do you need a fixed sbf? After rooting try directly 2ndinit
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
Cuz' my mb525 got flashed a GB sbf accidentally, from which you can't downgrade (by its user before me), and you can only recover it from éclair via the method i linked. other sbf's wont work
Ok, so when you flash the first sbf, and root, what stops you from directly using 2ndboot at that point
Sent from my MB526 using Tapatalk 2
thekguy said:
Ok, so when you flash the first sbf, and root, what stops you from directly using 2ndboot at that point
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
It just won't install, with status 0 or 7.
But right now I grew tired of this problem and i will flash a DFP 231.sbf from here:
http://forum.xda-developers.com/showthread.php?t=1542956
I will follow these steps. Can i do that? (MB525 Red Lens)
edit: 4.5.1-134 DFP-231 Retail.en.EU CEE
Yes. Flash that and root with framaroot.
Don't follow the guide for rooting, just flash dfp 231 , if it hangs on moto wipe data and cache from stock, and use framaroot.
Depending on eu or cee you've flashed, you may require a kernel to boot successfully with 2ndboot roms(otherwise you will just hang even after waiting a lot). It can be found in the defy custom kernel thread in General
Best of luck
Sent from my MB526 using Tapatalk 2

[Q] Motorola Defy+: Return phone to factory state

Hi,
I have Defy+ running quarx's CM10 android 4.1.2.
What I want is to recover my phone as it was, with official gingerbread and no 2nd init or other software installed on it.
Is there any way to do that?
If yes I would appreciate some help with it.
Thanks!
That's quite easy, isn't it? Simply download one of the offical bilds (sbf files), copy it (i mean if needed thing you need for flash like safe wipe) on sd card, wipe everything, boot into stock recovery (well i believe dl-mode) and flash official rom.
I was thinking about doing that and thanks for confirming it. What I am not sure about is if everything else installed that does not run in android, like 2nd init and other stuff lets call them , pre os, get deleted and only the stock firmware will be left. I will do this though and we will see how it goes.
Now do any of you helpful people have an sbf for Europe without blur UI in it?
A link would be helpful if so.
Thanks again!
Sbf cannot be flashed from sdcard! It must be done thru RSDLite. 2ndinit, etc will get wiped. If stuck in a boot loop after flashing, wipe data after stock recovery
Sent from my MB526 using Tapatalk
Quite simple. Wipe Data / Cache first via Stock Motorola Recovery. Flash SBF for your region. Voila! your phone is all stock again.
If you want a good De-Blur ROM try WIUI or if you still dont want the customizations move to MS2Ginger ->
http://forum.xda-developers.com/showthread.php?t=1140839

Categories

Resources