Related
I have recently bricked my phone by flashing with SPH M920 (Samsung Transform) image and it went out completely. No post blankscreen and nothing came on. I realized that it was bricked but I also noticed that it is still running in the background. With my experience with computers, I noticed that my phone isn't bricked as in fully dead but rather still working with different software. Becaue of the software incompatibility, the screen doesn't turn on and the sound doesn't work because they do not work the same way in every software. (Kind of like when you install wrong driver for a hardware and it doesn't know what to do).
Since I know that I flashed it with Samsung Transform image, I downloaded Transform drivers from Samsung website and installed them. I tried multiple combo of keys to get my blankscreen phone to download mode and I finally got it by pressing Volume Up + Camera + End (The normal combo key is Volume Down + Camera + End). From there, I ran SWUpgrade and there it was, it was connected.
From there, the only thing I did was flash the stock virginmobile kernel (Sorry, the forums won't let me post link so you can just google the file.)
After doing there, the screen came back on. That's it. From there, you can just follow the guide in this forum called "Get your Virgin Intercept back to stock (even after 2.2 upgrade)" by showson1.
Thank you. If you have any questions or comments, feel free to do so.
Here is a link to download the Froyo software so you can do it via the sdcard instead of thru motorolas update program.
http://www.motorola.com/staticfiles...dcards/US-EN/flipside/index.html?pubid=987654
I am having difficulties updating my son's phone...it goes through the process of updating and ends up with the !
pamaguin said:
I am having difficulties updating my son's phone...it goes through the process of updating and ends up with the !
Click to expand...
Click to collapse
What was the setup on his phone before the update? Rooted, how much memory avail, etc. Also, did you try both methods, or just this one?
I've tried both methods and phone was not rooted. And I also did a factory reset, which cleared all data.
pamaguin said:
I've tried both methods and phone was not rooted. And I also did a factory reset, which cleared all data.
Click to expand...
Click to collapse
I wish I had the answer to this. It baffles me as so many have had luck. Hopefully someone will come along that knows more than I.
You should try reflashing 2.1 using SBF to get it completely back to how the phone was when you first got it (more of a full wipe then just a factory reset). Use RSD Lite to do this, do you know how to do that?
Another alternative is to rename the 2.2 update to "update.zip" and then put it on your sd card. And once you got the "!" screen you can do the hardware reset by either pressing fn and T and the same time, up and down arrow keys at the smae time, or press up and down on the volume keys (one of these works depending on version device is running). From there 3 options will popup and you should select the wipe option first and then after thats finished select apply update zip and it will automatically apply the 2.2 update you renamed to "update.zip" on your sd card. And that should install the update. Hope this helps
*Note that flashing back to 2.1 AFTER you've already made it to 2.2 will brick your phone...so know what you're doing*
*Also some computers will automatically have the ".zip" at the end of the file name so after you rename right-click and go to properties and check to see if it just says update.zip. If it says "update.zip.zip" then you only need to rename it "update"*
Where can I find on how to use RSD lite? And I've tried renaming the file to update with no luck; "installation abort".
JBallin4life27 said:
You should try reflashing 2.1 using SBF to get it completely back to how the phone was when you first got it (more of a full wipe then just a factory reset). Use RSD Lite to do this, do you know how to do that?
Another alternative is to rename the 2.2 update to "update.zip" and then put it on your sd card. And once you got the "!" screen you can do the hardware reset by either pressing fn and T and the same time, up and down arrow keys at the smae time, or press up and down on the volume keys (one of these works depending on version device is running). From there 3 options will popup and you should select the wipe option first and then after thats finished select apply update zip and it will automatically apply the 2.2 update you renamed to "update.zip" on your sd card. And that should install the update. Hope this helps
*Note that flashing back to 2.1 AFTER you've already made it to 2.2 will brick your phone...so know what you're doing*
*Also some computers will automatically have the ".zip" at the end of the file name so after you rename right-click and go to properties and check to see if it just says update.zip. If it says "update.zip.zip" then you only need to rename it "update"*
Click to expand...
Click to collapse
Sent from my Xoom using XDA App
Flipside Bootloader Mode - Restore with SBF File
To put the Flipside into bootloader mode:
Open the keyboard
Press and hold the up arrow key (to the left of the OK key)
Hold the power button down
Release both buttons after about 4 seconds
You should see a display that says:
Bootloader
91.2B
Battery Ok
OK to Program
Connect to USB
Data Cable
This mode is for flashing an sbf file (ROM) to your phone using RSDLite.
RSD Lite version 4.9 works with the Flipside
You can get a stock AT&T ROM here (2nd post) or here (2nd post). I believe that they both point at the same file.
I can state that when I DLed that file it did work for my Flipside.
The hashes for the file I tested were:
CRC32: 92E73801
MD5: 7B529FE7D732EC4E71F5955C887E33A5
SHA-1: 7B49401A107F6DD779DBA0F55DECF473501E554A
Filesize: 196 MB (206,426,725 bytes)
This hashes/filesize are for the extracted sbf file.
I have received info from a reliable source that downgrading the Flipside from the not-yet-released Froyo upgrade using the available SBF files will brick your AT&T phone.
*you can find RSD Lite by just googling and downloading it*
Will post instructions for using RSD Lite in a second
This guide is for anyone who:
Has ever used RSD Lite, given up at the "Please Reboot this Phone Manually" status, and closed RSD Lite despite being warned: "Application is currently busy. Closing application may DAMAGE the attached device. Do you wish to continue?".
Has never used RSD Lite, but are going to, and want to do it right when you do.
The action described in the first bullet is quite common, so if you've done it, you're not an idiot. I think pretty much every RSD Lite YouTube video shows it being done that way, and it doesn't seem to cause any trouble, so who cares, right? Maybe it's just me, but I'd rather see a result of "PASS" when doing something this critical if at all possible. Here's how to do just that.
Proper RSD Lite flashing procedure:
1. Be sure you have your SBF file somewhere that you can find it. Also, be sure your SBF file is good. If your file was originally zipped, then unzipping it would have given an error if it was corrupted so you're OK. Otherwise, hopefully the source of your file lists its MD5sum. If so, you should verify the MD5sum of your file to make sure it is not corrupt. You can permanently brick your phone with a corrupted SBF (if it's corrupted in just the right place).
2. Plug your phone into a USB cable attached to your computer. Depending on whether or not you have USB debugging turned on, have had your phone attached to the computer recently, etc., you will at least probably hear the "device insertion tone" in Windows, and you may see the New Hardware Wizard install the drivers for your phone. Wait until your computer settles and looks bored before continuing.
3. Power down your phone. Once your phone is all the way "off", slide your keyboard open (on the phone).
4. Summon your best contortionist skills, and press on the "up" direction of the directional keypad rocker (the direction toward the screen -- which could really be to the right depending on how you're holding the phone) [pic]. While holding the dpad in the up direction, simultaneously press and hold the power button of the phone. When you see the backlight of the screen come on you can release the power button and the bootloader screen should appear (it will say "Bootloader" in the upper left corner). You can release the dpad. At the bottom of the text on the screen it should say "Transfer Mode: USB" if your cable is properly connected. If it says "Connect USB Data Cable", then you need to do so.
5. Run RSD Lite. If you're on a version of Windows newer than XP, remember to run RSD Lite as administrator by right clicking its menu choice and choosing "Run as Administrator".
6. At this point the phone should show up in the grid in the bottom half of the RSD Lite window. Give it a minute or two if it doesn't show up right away. Sometimes it takes Windows a minute (or 2 or 3) to let go of the phone and pick it back up again after rebooting into the bootloader. If after a couple minutes your phone still isn't listed in the "Model" column of the bottom section, in RSD Lite, click Config, Device Id Options, and choose "First-Come-First-ServeDeviceId Mode" and press "OK". RSD Lite may say you need to restart RSD -- if so, do so.
7. Assuming that you now can see your phone listed, click the "..." button to the right of the "Filename:" box. Find the SBF file you intend to flash on your hard drive. After choosing the file the right hand File details pane will fill in.
8. OK, this step is where you are going to press "Start" in RSD Lite, but don't do that yet. Before you press Start, read step 9. Step 9 has some timing sensitive tasks. If you do step 9 wrong it's not going to break anything, but you'll waste some time going through an un-needed boot and shutdown of the OS. Once you've read Step 9 and know what you'll be doing next, go ahead and press Start.
9. So far this has all been routine and you're thinking "so what?". This next part is what will get you a result of PASS instead of a warning about destroying your phone. After clicking Start the flashing process goes through several distinct steps. At some point there will be a bit of a delay with RSD Lite showing a status of "Phone[0000]: Waiting for re-enumeration". After that is when the actual flashing happens. When the flashing has completed, RSD Lite is going to issue a "reboot-bootloader" command to your phone. Unfortunately the Droid does not appear to implement the reboot-bootloader command correctly and does a normal reboot instead. If you don't "catch the boot" by holding up on the dpad key the OS will boot. Just before sending the reboot instruction to your phone the status in RSD Lite will change to "Phone[0000]: Phone is being rebooted". On your phone the screen will change to "SW Update Complete" (unless the message has been changed by the person who built the SBF) and your phone will reboot shortly thereafter. You want to be already holding the dpad key up when this happens. If you followed the instructions for Step 8 you have pre-read this step and knew to be ready for this. If not, your phone is probably already rebooted into the OS. If you miss it and the phone boots the OS it's no big deal (unless the instructions for the particular SBF you're flashing say otherwise). If that happens, let the phone finish its boot, and then just do a shutdown like normal. Then press/hold up on the dpad key and power back on. RSD Lite is patient and will wait.
10. You should now be looking at the bootloader on the phone, and RSD Lite should still be saying "Phone[0000]: Phone is being rebooted". If too much time has passed RSD Lite may be saying "Please manually boot the phone". The "Progress" value on the screen will keep incrementing, and at some point before, or at, 100% the result should change to "PASS". You can now click Close to exit RSD Lite without getting any disturbing warnings.
Congratulations. You've just done a proper SBF flash! The result is not simply cosmetic. RSD Lite is doing a final integrity check after rebooting clean into the bootloader. If you do it the old way (just unplug after the reboot and ignore the warning about destroying the device) you may be just fine, but you may also miss the chance to know your flash didn't go quite right and needs to be redone.
Installing RSD Lite:
First you're going to need a Windows workstation. There is a utility called sbf_flash for Linux that will let you do it with Linux, but that is not the subject of this guide.
Next, grab RSD Lite 4.6 and the appropriate Motorola drivers (32-bit or 64-bit) for your machine. In addition to the preceding links you can get them by going to this link, then double clicking on "rsd_lite" in the right side panel (or single click in the left side panel). [Older versions of the drivers here in case they be useful to anybody: 32 bit or 64 bit.]
Install RSD Lite and the drivers on your computer. If you're running Windows XP, life is good. If you're running Vista or Windows 7 you need to be sure to run RSD Lite as Administrator (by right clicking on the choice in your Start menu and choosing "Run as Administrator"). Hopefully your computer isn't too old. Some machines with older BIOS (like 2002 era) have been known to have USB issues that cause trouble with flashing using RSD Lite.
That's all there really is to installation.
I just posted the 2.2.2 Froyo SBF file in the Flipside Development section. Check that out and use RSD Lite to flash the file...you shouldn't have any problems if you do it correctly. Let me kno if it works or you need more specific instructions
Thanks Jballin, I followed your tutorial to restore my flipside before updating to froyo. It was the only way I could install 2.2. I kept getting stuck on the exclamation point. Thanks so much for your tutorial.
thehotrod11 said:
Thanks Jballin, I followed your tutorial to restore my flipside before updating to froyo. It was the only way I could install 2.2. I kept getting stuck on the exclamation point. Thanks so much for your tutorial.
Click to expand...
Click to collapse
Anytime man!
any one get the white notification led working after upgrade?
data2318 said:
any one get the white notification led working after upgrade?
Click to expand...
Click to collapse
YES OMG its so damn annoying. I thought I had turned it off, but it still shows when getting an incoming call. Turning it off in settings did stop it from flashing if I have a missed call or voicemail tho.
Tutorial/Walkthrough How to update your Droid R2D2 Phone using 2.2 if it fails to update to Gingerbread 2.3.3 Build 4.5.1_57_DR2-32
After spending a few days dealing with my phone automatically downloading and trying to install the updating and failing at 25%. I had to fix this since it will killing my battery.
With the instructions below this should restore your phone to the stock version of your Droid R2D2. This method will not delete anything on your phone. I would recommend backing up everything before you proceed just in case something does go wrong but I didn't have any issues. It will only restore all the original settings on your phone. This includes unrooting your phone and restoring all apk's and system files edited/removed from your device.
WARNING : This must be done using your PC. Do not attempt this using your cell phone
This information is provided without warranty. I cannot be held responsible if you brick or damage up your cell phone. I simply wrote a walkthrough/tutorial to help deal with an update issue on your Droid R2D2. I did not produce the procedure or the steps below. I just simply consolidated all the information from multiple sources to make it easier to understand and execute. You are welcome to share this information anywhere you want. If needed I will reformat the instructions so it's easier to understand.
1) First download and install the Motorola RSD Lite v5.5 (I attached the file at the bottom of this thread)
2) Download the Motorola 5.2.0 Driver with Motohelper and install from the link below
Motorola Drivers - http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
3) Download the SBF Droid R2D2 file VRZ_A957_2.4.5_1FF_01.
http://www.multiupload.com/8XGQBDG3GV
4) Once you download the VRZ_A957_2.4.5_1FF_01 file. Unzip the file into a folder. You will be using this file shortly
5) Launch RSD Lite. Once the application is launched click on the button with the 3 dots.
Navigate to the SBF file you just unzipped and once you find it click open.
You will see on the right side in the File properties window
Filename: VRZ_A957_2.4.5_1FF_01.sbf
Creation Date: 09/15/2010 03:16:26
File size: 455655933
RAM DL Version: N / A
Bootloader Version: N / A
Platform: 4G OMAP
HAB Type: Signed Production
This is a video to give you an idea how to use RSD Lite. I used this as a guide to make sure I was doing everything in the correct order.
http://www.youtube.com/watch?v=9udWx-KXwGY&feature=player_embedded#!
6) (This step isn't necessary, but you can do it.)
Back up anything on your SD card to your computer. Plug in your Droid2 to the computer via USB cable. Pull down the notification menu/blind, choose USB connection, and then choose USB Mass Storage Device. Now there should be a removable storage in your "My Computer." Go through your SD card and back up your important things. Probably the DCIM and download folder. You should also make sure that your phone is set up to "Back Up Data." Go to the system menu (the 4 squares icon/button in the lower left), choose Settings, then Privacy, then make sure the "Back up my data" and "Automatic restore" are checked.
7) Plug the USB cable into your cell phone and Power off your phone. Once your phone is powered off, Slide out your keyboard and hold the Up Arrow and press the power button. You will see a boot loader screen pop up and it will say Battery OK, Transfer mode USB. You will see the computer detect the USB device and install the new drivers onto Windows.
If the drivers in Windows Fail DO NOT PROCEED. Reinstall the Motorola drivers and try this again
8) Once you see the Transfer mode say USB. Go back to RSD Lite and click Start. You will see the progress bar Executing and slowing moving up to 100%. Your phone will eventually Power on.
Do not unplug or touch it until it hits 100% if you unplug the phone early you risk screwing up the system files on your phone.
You'll know when it is done when the Progress field in the table of RSD Lite says complete. This will take between 5-10 minutes to complete
9) Once it hits 100% you will see the status change and say Please manually power up this phone.(You phone should be already powered on if not you could power it on). Once this is completed you could either turn off your phone and power it back on or you could click Close in RSD lite. A pop up window will appear saying Application is currently busy. Do you wish to continue click Yes.
UPDATE 10/27/11
After your phone reboots and doesn't get past the boot animation
1) Turn off your phone
2) Hold down X on the keyboard
3) Turn on your phone while continuing to hold X( it will boot into the recovery mode after the Motorola logo disappears)
4) When you get the Android guy with a '!' in a triangle push the search button on the keyboard (the magnifying glass button, two keys to the left of the space bar)
5) Select both 'wipe cache' and 'wipe data' from the menu.
6) Select Reboot your phone
10) Once you unplug your phone you should see all the apks or applications which were removed originally off the device back on the device (I removed practically everything and everything was restored). If you have used z4root you will notice if you open the application it is no longer rooted.
I had a Blue triangle in my notification bar. To clear this you will need to reactivate your phone. Dial *228 and press send. Once you hear the options press 1 to activate your phone. Once this is completed you get a message saying your phone is activated and to wait up to 15 mins. You will also see the blue triangle disappear and will see the 3g reappear.
11) Once you are connected start downloading over the air the new gingerbread update to your phone. Once it is complete your phone will reboot and start installing the file and once it completed you should have the new gingerbread update on your phone
To Root your Droid R2D2 Please follow the directions below (Special Thanks to psouza4 for creating this program) http://www.psouza4.com/droid3/
NOTE: Do this at your own risk. I am not responsible for any damage caused.
1. First step is that you need to make sure if all Drivers are installed.
2. Once that is done, download and install
(Windows) http://www.mediafire.com/?g226n7as6cb1y6e
(Mac/Linux) http://www.mediafire.com/?2ugcdue4cw7dtc5
3. Now, go to Settings > Applications > Development on your Droid R2D2 and enable the USB debugging option.
4. Now connect your device to the computer and make sure you select the ” Charge Only ” mode.
5. Go the folder where you extracted the zip and run MotorolaOneClickRoot.exe (Windows) or run_to_root_your_droid3.sh (Mac/Linux).
6. Once it finished just click any button to exit the program and you will see superuser installed on your Phone.
Thats it. Hopefully this was easy to understand and works for everyone.
I cannot even root my phone. It will not go past the first rebooting stage. Any advice?
Are you currently on 2.3.3 or you still on 2.2?
Also make sure debugging mode is on and you have the correct motorola drivers installed.
Cant get VRZ file to work.
Hello,
I am trying to run threw this to reset my R2D2 Droid 2. When I try and download the VRZ_A957_2.4.5_1FF_01 file from the the link you provided all I get is a rar file that doesn't work on RSD Lite. Am i missing something on the download sight for the VRZ file?
---------- Post added at 08:41 PM ---------- Previous post was at 08:09 PM ----------
Hello again,
Sorry for my stupidity I forgot a rar file is a compressed file and I had to download win zip to decompress it. Don't deal with a lot of compressed files. Thank you for all this info will post if I got it to work.
all good. let me know if it works or if you get stuck
ok so i've been working at doing this for roughly an hour the damn drivers won't install on my computer...
Where you able to install Download Motorola 5.2.0 Driver with MotoHelper or are you getting stuck when your phone is connected to the pc?
Worked for me
Awesome, worked for me from my mac. I did get an error between phases 2 and 3 of the root process, but it worked anyway:
* Running exploit [part 2 of 3]...
*
* Rebooting the phone... when the reboot is complete, you may need to unlock the phone to continue.
*
error: protocol fault (no status)
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
* Running exploit [part 3 of 3]...
remount succeeded
Does this only work for the Motorola Droid R2D2 or will it work for the Motorola Droid 2 with the Gingerbread 2.3.3? Which I thought are the same phone except for the R2D2 add-on's.
ehrune - I am glad it worked for you. I will write a email to psouza and see what he says on it or ill look for an new update maybe it was a known issue which is now fixed
dfthompson - I own a droid R2D2 phone which is technically a Droid 2 with all the add-ins as you stated. I wrote the instructions because if you were like me and deleted all the bloat and junk off your phone (when you originally purchased it) you are unable to do the OTH gingerbread update because it will fail once you are doing the installation.
The file is for 2.2
thank you for posting this. my phone has been trying to update for weeks every night around midnight and failing, this is a huge help.
I must admit, after using it for a week, this update sucks big-time. Everything is much slower, button presses take a second or two to register, etc. Anyone else seeing this?
well said, guys these instructions are flawless. basic computer skills required
Ok so does this exe file get run from the computer or launch it from the phone?
Sent from my DROID2 using XDA App
Everything is done using the PC the only thing you need to do with the phone is plug it into the computer and to turn it on to go into the boot screen as instructed.
Ehrune - Yes i notice a few things running slower. i removed a ton of apk's and changed some settings and it works a lot better
boot loop
the flash was 100% successful, but now my phone is stuck in a boot loop. should I try reflashing?
edit: I ended up booting into recovery & doing a factory reset. I was able to boot & run the update from there. Good thing I backed up first..
still locked! afther full flash & no way to factory reset on my phone
i only need to factory reset ive try any times with
---------------------------------------------------
Power down the DROID 2 by holding the power button and then selecting Power Off
Hold the X key on the keyboard and turn the power back on, keep holding down the X key until you see a yellow triangle icon
Now close the slider and hold down the Volume Up button, then press the Camera button while still holding volume up
A menu will appear and one of the choices will be "wipe data/factory reset" -- use the direction pad on they keyboard to select this option
Scroll down using the direction pad to the "yes" option and select it with the d-pad select key
---------------------------------------------------
& with
---------------------------------------------------
a. Turn off your phone
b. Hold down X on the keyboard
c. Turn on your phone while continuing to hold X
d. When you get the Android guy with a '!' in a triangle push the search button on the keyboard (the magnifying glass button, two keys to the left of the space bar)
e. Select both 'wipe cache' and 'wipe data' from the menu.
f. Reboot your phone
---------------------------------------------------
the hard reset no work for my with any form (& the keys7Buttons are working properly)
i been full flashed Thanks to your tutorial
But still locked
Too many attempts
any ideas¿?
I lost my SBF file for R2-D2, and the link not available for now (multiupload). can anyone help me where I can find the file?
Thanks
I'm also looking for the r2-d2 sbf. All the links I come across are 1 of 2 dead links. Either the multiupload or the adrive links. None of which are standing today. Am I to believe that no one has a copy to upload elsewhere? So can someone please point me in the right direction.
I already found the file.
u can email me for the link, I don't have any right to post the link here
my email: [email protected]
Hello XDAers,
I am a real noob at rooting or android-related, and a true one voided of any knowledge regarding anything IT- related.
So dear veterans, please go easy on me.
Due to my prior success of rooting and flashing my Nexus 4 successfully a few months back with no issues, I decided to give it a try to flash a custom ROM for my dad's LG Optimus L7 - which seemed an easy task compared to configuring my Nexus 4 - since there was no need for inputting any command lines or any dealing with the abd (using the easy shortcut, that is).
So, I followed the guide here: http://forum.xda-developers.com/showthread.php?t=1906133 ...
I first factory resettled the phone because it was bloated, then applied the "RunMe.bat" from the "What you desire!" folder. (Everything was already backed-up beforehand.) But the process didn't success until I've retried again and again by re-plugging the USB in because the application/PC couldn't detect the phone. In the same time, I was running KDZ_FW_UPD.exe in the background, so unexpectedly for me the phone shut itself and pushed itself to a vividly green emergency screen, then in a few seconds switched back to a screen of purple-white-blue glitches. I had to close KDZ_FW_UPD.exe without knowing what quite happened since it seemed to be the cause and restarted the process with RunMe.bat.
I didn't manage to "Restore" it first due to the fact that the phone stopped responding due to a lag asking for an encryption key. It was lagging so hard and I had to close the cmd around 5 tries while it was processing, but succeeded later on.
And then, to verify whether I've actually suceeded in rooting L7, I installed Root Checker from the Play Store. And again, for the first few tries the program froze on screen for a long period of time due to "system performance", but after rebooting and restarting the app a few times again, the ROOTING proves to be a success. Just to be sure, around this time I've reloaded KDZ_FW_UPD.exe and it suceeded.
So I went to install CWM and ES. CWM for recovery boot and ES for removing pre-installed system apps as the phone was lagging so badly. I've downloaded the CWM restoring(something like ~6.0.28?) first and tried fastbooting immediately right after, but instead of getting the fastboot menu I got a screen emptied in black with these words:
[5020] "Secure booting error"
[5020] "Cause: boot certification verify"
No hard keys could do anything on the presumed "fastboot", and so I had to hard boot again. I thought that it might be due to the lack of memory(checked on ES later on that it was 310~MB/2GB), and so I've used ES to uninstall a lot of system apps which I deemed uneccessary. So I've Googled a bit and it became apparent to me that that I've didn't unlock the device properly, so lurked around and found a file called L7CWM that is supposedly to resolve my problem, but I presume that it's the CWM recovery image that I've installed. So in the end, I didn't bother with it but kept it on tab just in case.
I repeated the same process with CWM again, but this time, the screen was joined with all kinds of flowery glitches. Restarted the device, and it went only downhill: now the Home launcher stayed all pitch black and nothing appeared. I waited a few minutes, but nothing there until the notification bar appeared. The home screen is apparently dead, and so are the menu keys. Switched to Nova Launcher(installed it just in case Home Launcher fails), and still dead. I couldn't access using any of the menu keys and had unusable launchers.
Hopefully I could still access to the settings from my status bar, but when I did, it started crashing immediately.
I've repeated the attempt a few times after restarting the device a few times, but nothing helped. It only got worse that the when the launcher did SEEM to work. It only showed the wallpaper without showing any of the icons/apps. And crashes again.
I could still access to the App menu via the settings, but couldn't open any of them and when I tried to uninstall them, the screen frozes immediately right after I gain access to the page (white page though) and gain this message: "Unfortunately Package Uninstaller Stopped!"
Then I convinced myself that the only thing I could do at the time was to factory reset the phone and then everything would go alright since I've just had to restore the system apps.
But then the black screen of death came right along with it:
"Secure booting error"
It seems that I'm out of luck... ... But just to check if I'm still left with resorts, I've downloaded the L7CWM file online...
... ...but it still didn't help.
So now I'm being left with no other choices other than asking for help. I never really understand what KDZ_FW_UPD.exe does since I had the LG Driver already before installing it, which I presume was for updating the phone to a newer or older version. And too complex tech articles are kind of alien for me.
EDIT(1 hour later): Okay, now I figured out the reason why L7CWM didn't work was because I didn't extract it to the right folder (after double checked via notepad that I was supposed to directly put it into the C:\ drive). Now it worked(?), but then it didn't.
After launching Flash_Bootloader.bat:
This message now appeared on the L7:
"Sorry!"
"SuperSU is not responding.
Would you like to close it?"
"Wait - Report - Close"
and a few minutes later
"Sorry!"
"Unfortunately, SuperSU has stopped."
"Report - OK"
Now I think the bugs till now happened was due to the fact that I've deleted a file that was required for me to launch apps... Now I just need the right fix.
After 5 minutes of screen inactivity the phone restarted by itself, kind of creepy... ...
Flash_Recovery.bat did nothing.
Reboot2Recovery.bat made it reboot but still struck on the same menu.
Nothing seems to be effective via the phone anymore, seems like I have to rely on abd but then again I don't know how... ... My dad is also f*cking pissed off ^ ^;...
__________________________________
I think that I explained the logs pretty precisely in case I missed something... I'll be very very very very very very thankful if someone could tell me what has caused my phone to fail though.
For references, here are the phone's specifications:
Model Number: LG-P705g
Android version: 4.0.3 (Stock)
Rooted:Yes (root checker)
Baseband version: MSM7227A-1-AA
Kernel version: 3.0.8-perf
Build number: IML74K
Software version: V10e-AUG-10-2012
If I don't get the phone fixed to being usable soon I think that I will get butchered real hard... ... Preferably needs a step-by-step guide made for toddlers... ...
remove the battery for 10 seconds,put it back pres VOL+ and VOL - same time and than press the power button.when you feel a vibration press for many times the button wich is down in right,try for many times and maybe it will working :}
Cydes said:
Hello XDAers,
If I don't get the phone fixed to being usable soon I think that I will get butchered real hard... ... Preferably needs a step-by-step guide made for toddlers... ...
Click to expand...
Click to collapse
simple answer for your
just download your stock rom
go to emergency mode
and flash that stock rom
hi.
Unfortunateley i bricked my lg l'fino d290n.
Is there a way of booting from sdcard?
my lg cant be seen by my computer using usb-connection any more.
Behavior:
powered off connected to usb: loadscreen appears, but freeze
normal start: lives good screen appears, but freeze
download start (volume up + usb-connection): lives good screen appers, but freeze (no downloadmode any more)
hard-reset start (volume down + poweron, pause,volume down+poweron): Hard-reset screen appers. you can answer both questions (with volume up/down and powerbutton), but the reset screen freeze (checked several times and waited up to an hour), no boot after that.
to get shure, i tested the usb-connection with a new cable on another pc using win10 ( installed new qualcomm driver). No connect.
system of my support-computer is win xpsp3.
this is what happened:
the handset was succesfully rooted 2 years ago.
10 days ago i tried to restore a backup with twrp, ignored the errors and decided to reboot (didnt add supersu).
lfino was not able to boot after this. I then didnt do a hard reset (and dont ask me why), but decided to flash
the device with flashtool2014, since the downloadmode was working.
apparently i missed to install the right .netc++distributable. An error popped up, but it was not readable. The downloadscreen - a loadbar- of lfino freeze at 2% while downloading . after some minutes i cut the usb-connection.
After this, the handset behaves like described above.:crying:
Well. later I found out, that the sd card (where the backupd files of twrp were saved) couldnt be saved by Win32Diskimager (2tb size????) . Having a look inside the files, i found out, that something was wrong with the backup-file system.ext4.win. (explorer chrashed trying to copy, terracopy showed an error too).
Looks like, the restore failed because of this.
Then the flashing failed because of the wrong c++distributable, or i just had to wait longer (as stated in one of the describtions found here).
any Ideas, e.g. a reset thru a reset point of the motherboard?