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.
Related
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.
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.
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!".
*##### 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
Well, I think I need some help with this one.
So, I have been using Resurrection Remix as my daily driver for a while now (to be able to run lollipop). As I noticed the G2 now has an official lollipop build, so I wanted to install that(cam sucks on most ROMs and overall stability isn't always great). Since I figured the best way would be to go back to stock, and then run the OTA updates.
I made a backup of my current rom, found this, and tried the TOT method. Everything ran fine, but when the 85% reboot thing happened, it booted straight into TWRP. Decided to reboot to system via TWRP, but after showing the LG logo for about 5-10s, it goed straight back into recovery. Since i figured the install failed or something I decided to factory reset, and restore from my backup. TWRP says the restore is succesful, but it still won't boot into my ROM. Reinstalling any ROM doesn't work either
Already tried this, no result(, and I'm afraid of trying the above guide again, but let me know if i should just try again)!
I do have access to my recovery and download, and ADB still works. The only thing I see is that instead of this:
{
"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"
}
Mine says this:
(My PC is in Dutch )
(The LG Driver on the guide was an older version than the one on my pc still, but I don't think that will cause a problem).
Hope my phone isn't gone forever, and thanks for helping in advance!!
-Scrytal
EDIT:
Tried the above TOT method again, apparatly it skips a lot of things, and is done in like 30s, so it's not doing its job. I have no idea what's causing that though!
EDIT2:
IF ANYONE STILL FINDS THIS, this was the solution for me. I didn't know LG had a 'official' tool for fixing our sh*t . Hope it still helps you!
You should edit the title to include the word (solved) or (fixed).
Sent from my LG-LS980 using XDA Free mobile app
Scrytal said:
Well, I think I need some help with this one.
-Scrytal
EDIT:
Tried the above TOT method again, apparatly it skips a lot of things, and is done in like 30s, so it's not doing its job. I have no idea what's causing that though!
EDIT2:
IF ANYONE STILL FINDS THIS, this was the solution for me. I didn't know LG had a 'official' tool for fixing our sh*t . Hope it still helps you!
Click to expand...
Click to collapse
Hi, i can't boot any rom too,
I can access my download mode and recovery mode (twrp),
But i can't boot any custom rom,
And ADB can't recognize my phone,
I tried to back to stock using LG Flash Tool 2014 (the kdz ones), but nothing works,
And the official lg tool link is broken