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
Related
So I'm not new to flashing roms, bootloaders, recoveries, or rooting. Ive had a wing, a G1, a Behold II, a G2, and a mytouch 3g slide. All rooted, re-rom'ed, etc. Not to mention various friends and family phones I've worked with.
Anyway, I'm about to send my G2 in for warranty so I figured I need to at least unroot it if not S-on. Unfortunately I don't remember what exact method I used to reach Root and S-off, which is probably one of my problems, But it didnt have anything to do with Gfree. It was way before that and quite a while ago.
I've been over the G2 unroot thread here over and over again, as well as other forums and they all seem almost exact to what is posted here. I've tried this method over and over and I'm not getting anywhere. I have a few problems that I'm sure are what is keeping this from progressing. I cant seem to flash the PC10IMG - I get a no image or bad image error. I can't flash the stock_root rom via clockwork recovery due to some sort of scripting error. I have no Idea where to head from here, I can't seem to find any different methods to remove perm. root. Also that thread mentions using the hex editor to change the version number. When I open my misc.img it already shows the 1.19.531.1.
I'll include a few hopefully helpful images, Any help would be GREATLY appreciated. I should be getting my new one today, maybe tomorrow (I haven't been tracking it), and need to send my old G2 back in before too long.
{
"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"
}
flash a stock 1.19 rom through bootloader or fastboot RUU.
If you have fake s-off, then it will be straight to stock.
otherwise just run gfree with -s on switch after flashing a stock rom.
-Nipqer
Do you have any idea, preferably a link, to find a stock 1.19 rom? I feel like ive been looking all day and nothings turned up.
http://www.shipped-roms.com/download.php?category=android&model=Vision&file=PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip
md5: 531c08dc402e15577b947bf4cd22aec2
-Nipqer
Thanks man! I really appreciate it. I don't know why but I just could not find it yesterday. I'm not usually this slow =x lol.
I went through the same thing last week....After receiving the replacement G2, and using ADB to use the recommended gfree method and did a CLEAN PERFECT root I went about removing root from the old phone....No matter what I did I could not get the old root removed, so I did the unthinkable.....I creatively changed the dd command and was able to brick the phone.....Hopefully that will prevent any notice of previous rooting....(I couldn't boot, bootloader, etc...)
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.
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.
I have just got my G2, yay!
LG G2, 32GB
D802 20d-EUR-XX
Android 4.4.2 Kitkat
It's still stock with stock recovery, but I have rooted it successfully with Towelroot. Everything works fine. Now I would like to flash a custom recovery and eventually a custom ROM.
(The thing that scares me, as a former Galaxy Nexus owner, is that I can boot neither into the bootloader nor into recovery by using hardware keys. This is apparently normal, but it means I will be stuck if I ever can't get the phone into a state where ADB works. I can boot into (stock) recovery using ADB, and I can boot into Download Mode using the hardware key.)
- What is the safest way to flash a custom recovery on stock Kitkat 4.4.2? Auto Rec? Is there anything in particular I should be careful about? I read about all kinds of horror stories with malfunctioning touch screens...
- Will I be able to boot into a custom recovery using the hardware keys then?
Thanks!
I used Auto Rec to install TWRP, and it worked! Now I can also boot into recovery using the hardware buttons.
I removed the back cover to make sure I actually had a D802. Some people buy D800's on Ebay or Amazon with D802 back covers, and often the settings in Android say it is a D802 even though it's not. Only what's underneath the battery cover is completely reliable, and only if there is no sticker over the real type number. This is what it should look like:
{
"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"
}
The easiest way to remove the back cover is by removing the SIM tray first, then using a pry tool and your thumbnails in the direction of the seam (once the nail is in between the cover and the body).
Many thanks to Bender_007 and Iowabowtech, who were patient enough to guide me. I have seen them patiently help so many other people too in various threads like "help, I'm bricked!".
I don't know if this is a right thread for that but I tried somewhere else and no one was able to help me.
After some fun with magisk modules I got stuck in fast boot. I reinstalled a stock Rom because the one I was running wouldn't work for some reason. After first boot the '' android setup stopped working '' pop up came up the screen and when I tried to log into my wifi it automatically turned itself off.
Sim cards doesn't work either. I tried many different roms but any of them fixed my problem. I don't have much knowledge about this stuff but I know how to flash/ root my phone so I know it was a module fault. If anyone had a simmilar problem and fixed this please help. I've been trying to fix this for 4 days now and nothing worked. Sorry for my English I'm still learning.
{
"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"
}
Corgar39 said:
I don't know if this is a right thread for that but I tried somewhere else and no one was able to help me.
After some fun with magisk modules I got stuck in fast boot. I reinstalled a stock Rom because the one I was running wouldn't work for some reason. After first boot the '' android setup stopped working '' pop up came up the screen and when I tried to log into my wifi it automatically turned itself off.
Sim cards doesn't work either. I tried many different roms but any of them fixed my problem. I don't have much knowledge about this stuff but I know how to flash/ root my phone so I know it was a module fault. If anyone had a simmilar problem and fixed this please help. I've been trying to fix this for 4 days now and nothing worked. Sorry for my English I'm still learning.
Click to expand...
Click to collapse
Did you use miflash for installing stock rom?
NOSS8 said:
Did you use miflash for installing stock rom?
Click to expand...
Click to collapse
I used mi flash/recovery/fastboot/adb. Nothing worked
I tried other roms but problem was the same. I run out of ideas already. If you have any other ideas on what should I try i would really appreciate that
Corgar39 said:
I used mi flash/recovery/fastboot/adb. Nothing worked
I tried other roms but problem was the same. I run out of ideas already. If you have any other ideas on what should I try i would really appreciate that
Click to expand...
Click to collapse
CN version I guess?
try to flash the rom which was on it originally and relock the bootloader but be careful not to go wrong otherwise the phone is dead.
or try with miphone assistant(repair option).
Go to *#*#4636#*#* and see if you can copy config, just paste all your data for wifi