hello. first of all, i am a complete noob. although i will be glad to learn, i guess i will need slow explanations...
so, i have rooted my defy plus 2.3.6 , then installed 2nd init bootmenu and took a backup. then tried to flash this and ever since im getting only the moto splash screen and a reboot over and over.
ive tried looking all over this forum for a solution... tried doing custom recovery but it says no such file or directory, tried doing a stock recovery and it gets me to android system recovery. i also tried flashing different roms on my sd, using the android system recovery, but it says signature verification failed
even did a factory reset .
am i doomed to see this logo till the rest of my life?:crying:
The solution should be simple, you must flash your phone using RSDLite again.
your clockworkmodrecovery-menu is gone with the factoryreset in stock-recovery.
So you must flash again the rooted SBF for the defy+, installing 2nd init bootmenu and choose the right flashable zip for your device.
A flashable.zip for a samsung galaxy s2 will not work on a defy+.
in which stage should i connect my droid to the computer ?
usually when i connect it , RSDlite dont see it.
can you post a link to some stable flashable zip for defy plus?
You can use this:
http://roms.custom-android.de/counter/click.php?id=86
it is the white Rabbit Plus Edition v1.6.
To flash a brand new SBF you must enter the bootloader, then rsdlite should recognize your device.
animated image how to enter the bootloader:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
wow!! i guess it was nothing for u, it was everything for me!!
u literally saved me! :victory:
(ok, ok at least my phone... )
really, the thanks button is to small..:fingers-crossed:
can i do something else?
oh and another thing , will the defy+ work with miui?
or alternatively is there a rtl fix for cm7 ?
You can also try this ROM:
http://forum.xda-developers.com/showthread.php?t=1543272
but AFAIK MIUI CM9 (V4) lags a little bit more then CM7-Built, or cyanogenmod CM9-builds.
AFAIK, there not really full ported MIUI for the defy+.
The WhiteRabbit emulates the miui-Style in the best way.
Related
hello to all xda members
in the past i update a gt540 (1.6) to 2.1 and then to cyanogenmod, this come new from store with 1.6 and never have a problem with this phone.
Now i buy a gsm unlocked gt540 wich come from store with 2.1 and then i tried to update to 2.1 stock fastboot rom with kdz updater(using the same guide that i used in the first phone), the problem is that the process was stopped and the Phone was COMPLETELY bricked.
The only way to come back to life was a complex conection(jtag) with a box named "Medusa box", but the problems no stop here, when the phone turn on there is no way to grab signal until i used a lge oficial box to repair NVM and then unlockconfused: the phone was from factory unlocked) again the phone.
i need install cyanogenmod, bacause the phone is actually no fully working since enach time, this said some like this."process android was stoped," an others like this saying a process o app stop working.
i need your help to now how update, or if the phones that come from factory with 2.1 use a diferent way to update.
the photo is my actual rom(2.1 oficial rom)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Need to think this through...
you can go into download mode right? then follow this guide to install fastboot.. then the phone will bootloop. Just download cwm or twrp from android development section and flash using fastboot.. then install any ROM...
XiproX said:
you can go into download mode right? then follow this guide to install fastboot.. then the phone will bootloop. Just download cwm or twrp from android development section and flash using fastboot.. then install any ROM...
Click to expand...
Click to collapse
Thanks this finally works.
hi,
with fastboot mod, my phone d'ont won't to pass the cyanogen blue cross at the first boot.
So, i install the clockworkrecovery.img, i download the SDSL rom for recovery, and it was quickly and secure installed.
So I rooted my phone well over a year ago now and had no issues with CM7 and updates. I have been reading about the CM10 on Jellybean and would like to upgrade to that. Now I have never had an issue before now installing .zip files but yesterday I went to install it yesterday following this thread http://forum.xda-developers.com/showthread.php?t=1795647.
After downloading the files, wiping, installing from SD, wiping and rebooting the phone just goes into a boot loop mode. I was able to get back into the recovery and revert back to CM7 to at least stabilize the phone to use and noticed that the Android being run is Gingerbread (see screen capture) and from what I read and understood I needed to be in Froyo? Correct me if I am wrong.
I am wondering if I am using the wrong gapps file or possible the 2ndboot, I still have the original 2ndinit on the phone, could that be the issue? Or perhaps I need to go back to Froyo to go up to Jellybean?
Any help is appreciated, I am tech savvy but perhaps not the best at understanding all the nuances in rooting a device.
Here are the files I installed:
CM10-20120924-NIGHTLY-mb525.zip
gapps-jb-20121011-signed.zip
kernel-froyo-222-179-4-signed.zip
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Or should I have used this kernel kernel-gb-234-451-134-signed.zip?
how do i find green or red lens defy
sunil_defy said:
how do i find green or red lens defy
Click to expand...
Click to collapse
Check out this thread.....http://forum.xda-developers.com/showthread.php?t=1116694
how to find green and red lens defy
sunil_defy said:
how to find green and red lens defy
Click to expand...
Click to collapse
Are you looking to identify your phone or to buy a Defy?
I think I may be the first person to successfully brick a Defy. I tried following this thread (http://forum.xda-developers.com/showthread.php?t=1691901) and succeeded in getting the bootloader screen to show Err: A5,69,4E,00,41
It seems I may have gotten in over my head so any suggestions would be appreciated at this point. Trying to not have to buy a new phone.
Thee GOC said:
I think I may be the first person to successfully brick a Defy. I tried following this thread (http://forum.xda-developers.com/showthread.php?t=1691901) and succeeded in getting the bootloader screen to show Err: A5,69,4E,00,41
It seems I may have gotten in over my head so any suggestions would be appreciated at this point. Trying to not have to buy a new phone.
Click to expand...
Click to collapse
This happened to me as well...i think it's to do with the version of the cmg files inside the sbf. keep this thread handy - Defy is unbrickable: http://forum.xda-developers.com/showthread.php?t=1216982
I installed the latest Merruks kernel and my device got stuck in a bootloop. I reinstalled whitexp kernel and the device booted sucessfully, but I lost root. I tried re-rooting the device but it seems it tries to do copy su to /merruk/su which doesn't exist, and "root by CWM" apps don't work either.
What do I do?
I'd post in the kernel's thread but since I'm new I can't.
el_isma said:
I installed the latest Merruks kernel and my device got stuck in a bootloop. I reinstalled whitexp kernel and the device booted sucessfully, but I lost root. I tried re-rooting the device but it seems it tries to do copy su to /merruk/su which doesn't exist, and "root by CWM" apps don't work either.
What do I do?
I'd post in the kernel's thread but since I'm new I can't.
Click to expand...
Click to collapse
reflash your rom if you are in a custom rom,. . . either reflash your stock fw via odin and reroot it,
el_isma said:
I installed the latest Merruks kernel and my device got stuck in a bootloop. I reinstalled whitexp kernel and the device booted sucessfully, but I lost root. I tried re-rooting the device but it seems it tries to do copy su to /merruk/su which doesn't exist, and "root by CWM" apps don't work either.
What do I do?
I'd post in the kernel's thread but since I'm new I can't.
Click to expand...
Click to collapse
Follow.my guide in the general section.named
Safest way to install meruk kernel
I have solver this problem there
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
=========HOLO-UBUNTU========theme
After part 3, I reboot my phone and it's stuck in the booting screen (the one that says galay y). I left it there, to see if it eventually boots, but it's been over an hour and nothing yet. Do I continue to part 4?
For future reference, the post is here: http://forum.xda-developers.com/showthread.php?t=2229940
2-3 mins are enough to know if ur phone has entered a bootloop or not -_-
Yeah continue to part 4
=========HOLO-UBUNTU========theme
Good news: The next step worked, and I got to see the kernel loaded.
I had to reboot a couple of times for all to take. Still, my widgets wont load... strange.
Thanks for your help and your guide, btw.
*##### EDIT #####*:
Who would have thought that running Windows with VMWare Fusion on Mac OS X could mean that Flashing tasks aren't always a possibility... Tried on a nearby Windows computer and it worked completely fine..! How disappointing, sorry the waste of post, could a Mod please delete this.
Cheers again.
_____________________
Hello all.
I have a Galaxy S4 GT I-9505 which, to date, has shown me that it seems to be impossible to revert it back to stock firmware, of any kind...
I have tried numerous different stock firmwares and every single one has failed. I came from a Rom called 'Foxhound' and was a newly released 4.4.2 at the time, so I'm guessing KNOX has done something to the bootloader which has deemed my device in limbo - to my knowledge.
The thing is, I've come across a leaked 5.0.1 firmware for this device, so I thought I'd download it, only to notice that the Odin flash file wasn't a single TAR file but a series of other files that correspond to the functions of Odin.
From this point on, I decided to try and flash the Bootloader file by itself, and that WORKED. Of course, the only progress I was getting from this was the basic boot logo at the beginning of powering on the device.
Seeing as I was unable to boot into recovery, I thought I'd try and download an Odin flashable CWM Recovery, and this also WORKED.
The thing is, whenever I attempt to flash a full Rom through Odin, it will go through the inevitable error that it does with all attempts.
Here are some images:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm beyond frustrated by this as I can't deem the phone usable until I have it up and operational, and it is basically worth nothing in this state.
I would be endlessly grateful if someone would be able to point out what the possible issue may be, I would be beyond thankful!
Best regards,
Try to use Odin 3.09
Hi folks,
My phone is unlocked & rooted and it only starts showing the android logo after I updated with the official updater in the phone, the december update.
When I want to flash it with the stock rom in fastboot mode, according to this (https://forum.xda-developers.com/mi-a1/how-to/rom-factory-images-t3688548 ), the flasher says just"can not found file flash_all_except_storage.bat"
I have no idea what to do.
Can anybody help me?
Don't want to throw away another 200 dollars
Thank you,
Michael
Youre missing a file in the stock rom
ProchyGaming said:
Youre missing a file in the stock rom
Click to expand...
Click to collapse
O rly?
I extracted the stock rom now with 7zip because it was a tgz and extracted the stock rom.
Now I used the flash_all.bat but it gets stuck at 'Writing system_a'.
Maybe because of lack of space.
ADB doesn't recognize my phone. Fastboot does. Can't go into recovery mode.
Partition table seems to be ****ed up. Any ideas? :/
OK, for all people with the same problem:
I used the linux scripts on my linux system and it booted / worked perfectly.
No idea why the windows crap didn't work.
Hope to have helped you
I had a similar issue yesterday but fixed it following a couple of guides from mi forum. Basically tried mifalshtool which did not work to begin with, then tried manual flashing using CMD commands. Got stuck at writing system.img. went back to the sourcefile, unzipped it and copied the file path, then pasted in the mifalshtool. Flashed it and 'BOOM" it worked. Took about 12mins but it booted. My 8hrs of yesterday morning (IST) got screwed.
zeyaan said:
I had a similar issue yesterday but fixed it following a couple of guides from mi forum. Basically tried mifalshtool which did not work to begin with, then tried manual flashing using CMD commands. Got stuck at writing system.img. went back to the sourcefile, unzipped it and copied the file path, then pasted in the mifalshtool. Flashed it and 'BOOM" it worked. Took about 12mins but it booted. My 8hrs of yesterday morning (IST) got screwed.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}