[Q] MB525 flashed to MB526, rooted but cant install cm9, 10, kitkat or any other ROM - Defy Q&A, Help & Troubleshooting

Hi
I had a Motorola Defy mb525.
Bricked the phone while trying to install CM9
Got it alive somehow by Flashing it with .sbf
Now my phone shows as mb526 and I was able to root it again.
System Version - 45.0.231.mb526.AsiaRetail.en.03
Version - 2.3.6
Kernel - 2.6.32.9-ge281b6e [email protected] #1
The problem now is I am not able to flash any of the Custom ROM's.
Tried CM10, Cm9 and also the latest kitkat
Downloaded different ones for each ROM's.
I get the message when i try to update from SDcard "Signature verification failed"
If someone could help me in Upgrading to JellyBean or Kitkat

rahulpillai said:
Hi
I had a Motorola Defy mb525.
Bricked the phone while trying to install CM9
Got it alive somehow by Flashing it with .sbf
Now my phone shows as mb526 and I was able to root it again.
System Version - 45.0.231.mb526.AsiaRetail.en.03
Version - 2.3.6
Kernel - 2.6.32.9-ge281b6e [email protected] #1
The problem now is I am not able to flash any of the Custom ROM's.
Tried CM10, Cm9 and also the latest kitkat
Downloaded different ones for each ROM's.
I get the message when i try to update from SDcard "Signature verification failed"
If someone could help me in Upgrading to JellyBean or Kitkat
Click to expand...
Click to collapse
Are you sure you are using custom recovery?
Sent from my Nexus 7 using Tapatalk

Feel like a real dumb person now, I did not install Sndinit
hotdog125 said:
Are you sure you are using custom recovery?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Feel like a real dumb person now, I did not install Sndinit
Now I am in the Custom Recovery menu
Backing up my current ROM
Will try to flash Kit Kat and update

Still no Luck
rahulpillai said:
Feel like a real dumb person now, I did not install Sndinit
Now I am in the Custom Recovery menu
Backing up my current ROM
Will try to flash Kit Kat and update
Click to expand...
Click to collapse
Tried Kit Kat, still same
Tried CM10 twice, installs but when I reboot it gets Stuck on startup "Startup has encoutered an error" something like that
No matter what language I select still same
Any Inputs

For KitKat you need to flash an updated recovery. Check the thread.
Sent from my Nexus 7 using Tapatalk

CM10.2 works but Kit Kat Still not installing
hotdog125 said:
For KitKat you need to flash an updated recovery. Check the thread.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
CM10.2 works after installing gapps but Kit Kat Still not installing
I updated the recovery as well
My phone was bricked when I was installing Kit Kat
It stopped at Step 7
I had to flash the stock SBF to get it alive again
Will wait for updates to the kit kat mod
CM10.2 works but really slow

Related

Dead Android bot on update install

SO my N7 is rooted through Wugs tool, it has been great so far!
Now though, when I try to install the system update, my little android bot dies with an exclamation mark above him and I have to hard reboot.
Any ideas?
Probably because you now have a custom recovery instead of stock.
Travisdroidx2 said:
Probably because you now have a custom recovery instead of stock.
Click to expand...
Click to collapse
So what would be the best route to fix this, I am overly tired of getting prompted to install my system update.
Thanks
Freeze the update apk.
Sent from my SPH-L710 using Tapatalk 2
I think he's asking for a way to update it with the custom recovery installed...I could be wrong though.
Sent from my Nexus 7 using Tapatalk 2
ExploreMN said:
I think he's asking for a way to update it with the custom recovery installed...I could be wrong though.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
My goal would be to update my N7, if for no other reason, than to stop getting pop ups every 10mins asking to install the update.
I am running WugFresh's toolkit 1.5.2, My tablet is running Jellybean 4.1.1 RO03C
An OTA update will not install or will not install correctly on a device that has been modified from stock.
But if your device has a custom recovery installed (flashed via Wugs) you can install a custom 4.2 ROM and you will have everything you would get from the OTA. The 4.2 stock rooted rom from scrosler is a good ROM to start with. Or use wugs to return to stock and take the OTA. Then from there you can root/ flash whatever you want to do.
Sent from my Nexus 7 using xda premium
thanks for this thread,
im in exactly the same position except havent clicked accept update yet and glad i havent lol
asked many times but always get mixed answer's about updating my rooted nexy with twrp recovery, i did use goo manager to update to the latest twrp recovery
so im not sure if i need to un-root to update as the new twrp is supposed to work with 4.2?
ezas said:
An OTA update will not install or will not install correctly on a device that has been modified from stock.
But if your device has a custom recovery installed (flashed via Wugs) you can install a custom 4.2 ROM and you will have everything you would get from the OTA. The 4.2 stock rooted rom from scrosler is a good ROM to start with. Or use wugs to return to stock and take the OTA. Then from there you can root/ flash whatever you want to do.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks for the response, that makes sense, and gave me the info I needed!

[Q] Custom Rom to stock 4.3?

The situation is fairly complex right now;
Earlier today;
I had my Nexus 7 (2012) running Paranoid Android 3.something with 4.2.2 as the base rom.
My objective was:
To update to Paranoid Android 3.the latest version (which uses 4.3 as the base rom)
What I did:
I downloaded both the latest rom + gapps from the proper xda site for Nexus 7 and tried flashing them from TWRP.
It installs the rom just fine, but gives me an error on the Gapps (Error 7, if that helps).
I'm guessing this is because I'm not on 4.3 but on 4.2.2. Can someone confirm this please?
What I have done now:
So I thought I should flash a stock 4.3 rom and then try installing the new PA rom. But The flashing method for the stock rom is completely different than a custom rom, it seems.
What I think I should do:
So, should I somehow install the stock 4.3 rom and THEN try to flash the new PA rom?
If not that, then what can I do to get to the latest Paranoid Android?
Thank you!
It is totally unnecessary to upgrade to stock 4.3 prior to PA 3.9x.
Firstly, which GAPPS package did you attempt to install? The packages for 4.2.2 and 4.3 are not interchangeable.
najaboy said:
It is totally unnecessary to upgrade to stock 4.3 prior to PA 3.9x.
Firstly, which GAPPS package did you attempt to install? The packages for 4.2.2 and 4.3 are not interchangeable.
Click to expand...
Click to collapse
The 4.3 gapps gives me an error and says incompatible rom, the 4.2.2 gapps installs just fine, but the my tablet is stuck at the PA boot logo.
If I'm on 4.3 stock, shouldn't it install 4.3 gapps and 4.2.2? :S
And if 4.2.2 is the right one for me, then what to do if I'm stuck at the boot?
railpressureflip said:
The 4.3 gapps gives me an error and says incompatible rom, the 4.2.2 gapps installs just fine, but the my tablet is stuck at the PA boot logo.
If I'm on 4.3 stock, shouldn't it install 4.3 gapps and 4.2.2? :S
And if 4.2.2 is the right one for me, then what to do if I'm stuck at the boot?
Click to expand...
Click to collapse
Are you using pa_gapps-full-4.3-20130808-signed.zip? There should be no issues using it with PA 3.9x. If you're having problems installing 3.9x with that package, you may have a corrupted download.
Sent from my Nexus 7 using Tapatalk 4
najaboy said:
Are you using pa_gapps-full-4.3-20130808-signed.zip? There should be no issues using it with PA 3.9x. If you're having problems installing 3.9x with that package, you may have a corrupted download.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
All good now, I fixed it.
The issue was that the Paranoid Android rom link is of the 3.5x version, which is essentially a 4.2.2 rom. And that was the latest rom the PA poster had. I realized it's not 3.91, which was the one I needed. So I went fetching for it on google and finally found it, then ran the 4.3 gapps and **** was all good.
Thanks for your help though, I truly appreciate it!

[Q] Problem with 4.4.2

hi. I install kitkat 4.4.2 on my nexus 4 and everything be ok until now when i try install miui on my nexus and phone crash on logo google. Kitkat have new bootloader so it may be the reason for this problem ?? pleas help.
nosteres said:
hi. I install kitkat 4.4.2 on my nexus 4 and everything be ok until now when i try install miui on my nexus and phone crash on logo google. Kitkat have new bootloader so it may be the reason for this problem ?? pleas help.
Click to expand...
Click to collapse
I would just try to install 4.3 or even 4.2 (don't know what is miui built from) bootlader and radio. You can find the old ones in general section.
gt-kingz said:
I would just try to install 4.3 or even 4.2 (don't know what is miui built from) bootlader and radio. You can find the old ones in general section.
Click to expand...
Click to collapse
miui built is from jellybean 4.2.2. I did like you say i install 4.3 and everything fine, so bootloader make problems. Can i install 4.4 without newest bootloader??
nosteres said:
miui built is from jellybean 4.2.2. I did like you say i install 4.3 and everything fine, so bootloader make problems. Can i install 4.4 without newest bootloader??
Click to expand...
Click to collapse
Yes sir!

safestrap rom problem

i have a droid razr m
running 98.30.1
root only
i am trying to use safestrap 3.11 to flash a custom rom and every attempt has failed stating unable to open zip file i have tried multiple download links and roms and still nothing. also tried internal and external storage...other attempts were done on older versions of safestrap and still nothing
the only rom i was successful with was the rage m rom
Musiv said:
i have a droid razr m
running 98.30.1
root only
i am trying to use safestrap 3.11 to flash a custom rom and every attempt has failed stating unable to open zip file i have tried multiple download links and roms and still nothing. also tried internal and external storage...other attempts were done on older versions of safestrap and still nothing
the only rom i was successful with was the rage m rom
Click to expand...
Click to collapse
you are going to get deleted!! post this in QnA section. And BTW change your recovery to TWRP.
Musiv said:
i have a droid razr m
running 98.30.1
root only
i am trying to use safestrap 3.11 to flash a custom rom and every attempt has failed stating unable to open zip file i have tried multiple download links and roms and still nothing. also tried internal and external storage...other attempts were done on older versions of safestrap and still nothing
the only rom i was successful with was the rage m rom
Click to expand...
Click to collapse
Man!!! READ forum before posting!!
I did not realize you were boot locked.
Before this thread gets moved or deleted: you must tell us that whether you have unlocked your bootloader. If you haven't unlocked it, then you're stuck with SafeStrap and you should give up on ANY AND ALL custom ROMs beyond Android 4.2. Otherwise, if you have an unlocked BL, just fastboot flash a custom recovery and flash any ROM from there.
And stop posting the same question everywhere!
Sent from Google Nexus 4 @ CM11
Sounds like you tried to flash some ROMs that aren't compatible with SS.
AndyYan said:
Before this thread gets moved or deleted: you must tell us that whether you have unlocked your bootloader. If you haven't unlocked it, then you're stuck with SafeStrap and you should give up on ANY AND ALL custom ROMs beyond Android 4.2. Otherwise, if you have an unlocked BL, just fastboot flash a custom recovery and flash any ROM from there.
And stop posting the same question everywhere!
Sent from Google Nexus 4 @ CM11
Click to expand...
Click to collapse
You're telling me I can run 4.2 roms in safestrap with a 4.1.2 base?
The only 4.2 ROM that worked was a CM10 port. It's running around in this forum somewhere.
You mean CM10.1(4.2)? or CM10 (4.1.2)
Playb3yond said:
You mean CM10.1(4.2)? or CM10 (4.1.2)
Click to expand...
Click to collapse
I think it was 10, so yeah 4.1.2.
Playb3yond said:
You're telling me I can run 4.2 roms in safestrap with a 4.1.2 base?
Click to expand...
Click to collapse
No, I mean everything Android 4.2+ will not run, including 4.2, 4.2.1, 4.2.2 and so on. I should've been clearer when describing. Just try that CM10 (Android 4.1.x).
Sent from Google Nexus 4 @ CM11
AndyYan said:
No, I mean everything Android 4.2+ will not run, including 4.2, 4.2.1, 4.2.2 and so on. I should've been clearer when describing. Just try that CM10 (Android 4.1.x).
Sent from Google Nexus 4 @ CM11
Click to expand...
Click to collapse
There was a 10.1 in development for SS, but the BL unlock came out and they shifted focus away from SS.
Musiv said:
i have a droid razr m
running 98.30.1
root only
i am trying to use safestrap 3.11 to flash a custom rom and every attempt has failed stating unable to open zip file i have tried multiple download links and roms and still nothing. also tried internal and external storage...other attempts were done on older versions of safestrap and still nothing
the only rom i was successful with was the rage m rom
Click to expand...
Click to collapse
Only SS compatible rom i know of is this
http://forum.xda-developers.com/showthread.php?t=2609263/
Updated 3/22/2014

[Q] Softbrick? [solved]

Hi,
I just got a new phones so I decided it'd be cool to root my old RAZR M. I got the root and unlocked bootloader, and then I went in to try and install a custom rom. It ended failing and it gets stuck on the "WARNING BOOTLOADER UNLOCKED" screen. I'm able to go into fastboot and recovery.
I did some looking around, and I found that you can use RSD to get stock ROMs back. I tried downloading the 4.4.2 ROM from here, but it for some reason ends up going down to 0b/s and then says network error, so I tried the 4.1.2. It downloaded, and i went in using RSD to flash it, but it says that gpt_main0.bin failed and it stops. Since I did that, whenever I go into recovery it just freezes and I can't do anything.
Anyone have any idea what I can do to either get the 4.1.2 one working and root that or get the 4.4.2 one downloaded and try that?
Thanks
EDIT: Got 4.4.2 loaded back and did research and got CM11 loaded. Thanks anyways!
Please tell us what stock version you're on and what recovery and ROM you installed. It sounds like you've combined a JB BL ROM with a KK BL phone or vice versa.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
I'm on 4.4.2 stock, the recovery I have is TWRP. I tried to install CarbonRom. I guess i should have done more research for ROMs.
Also, I've been able to keep a download of stock 4.4.2 rom going and it's ~85% done so I'm hoping it's able to finish this time.
EDIT: Got 4.4.2 downloaded and installed using RSD. Going to get it all rooted again. Does CyanogenMod 11 work with version 183.46.10.XT907.Verizon.en.us?
Thanks
wholocked10 said:
EDIT: Got 4.4.2 downloaded and installed using RSD. Going to get it all rooted again. Does CyanogenMod 11 work with version 183.46.10.XT907.Verizon.en.us?
Thanks
Click to expand...
Click to collapse
Yes it does, however CM11 for KK BL (moto_msm8960) still has these nasty WiFi and GPS bugs. If you want a bug-free CM11, you'll have to follow the guide in General section to downgrade to JB (98.30.1) and then flash CM11 for JB BL (moto_msm8960_jbbl). Don't worry, if you've unlocked your BL, then nothing would relock it, not even downgrading.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]

Categories

Resources