I've spend much of the day trying to root and then flash my new Optimus V. For some reason I keep running into snafus, even after rooting two Eris phones and a Nook color without too much difficulty. Would REALLY appreciate the group's assistance.
After much trial and error, I finally got root using SuperOneClick.
After that, I first tried to use adb to install the asop ROM per http://forum.xda-developers.com/showthread.php?t=962862 , but would always get stuck on the blue bootloader screen. By trying to fix that, I got stuck in a clockworkmod recovery loop. I finally got out of that by doing a flash_image of the stock ROM via adb. But then, the google market, and hence my google apps (including clockworkmod) was gone.
So now I'm stuck without access to clockwork mod, and a broken stock rom/interface (with no market access.) There may be a way to launch CWM even with the vashished google apps, but I'm not sure what it is...
Here is what I do have readily available in my "toolkit":
-root still working (via superoneclick);
-Root Explorer (having manually installed the Amazon marketplace apk);
-abd access to my 4g SD card;
-a backup 4g SD card, should one prove helpful.
My goal is pretty simple: to get a good custom rom (probably ASOP) with a fully functional suite of apps, and to MAKE SURE that the other corruption I've unwittingly done to my phone's data is complete eradicated.
I apologize for the jumbled nature of this post. I'm sure I'm leaving some diagnostic stuff out that would be useful--please fire away and I'll be more than patient about trying to clarify.
THANK YOU in advance for any help you can offer!
polphi said:
I've spend much of the day trying to root and then flash my new Optimus V. For some reason I keep running into snafus, even after rooting two Eris phones and a Nook color without too much difficulty. Would REALLY appreciate the group's assistance.
After much trial and error, I finally got root using SuperOneClick.
After that, I first tried to use adb to install the asop ROM per http://forum.xda-developers.com/showthread.php?t=962862 , but would always get stuck on the blue bootloader screen. By trying to fix that, I got stuck in a clockworkmod recovery loop. I finally got out of that by doing a flash_image of the stock ROM via adb. But then, the google market, and hence my google apps (including clockworkmod) was gone.
So now I'm stuck without access to clockwork mod, and a broken stock rom/interface (with no market access.) There may be a way to launch CWM even with the vashished google apps, but I'm not sure what it is...
Here is what I do have readily available in my "toolkit":
-root still working (via superoneclick);
-Root Explorer (having manually installed the Amazon marketplace apk);
-abd access to my 4g SD card;
-a backup 4g SD card, should one prove helpful.
My goal is pretty simple: to get a good custom rom (probably ASOP) with a fully functional suite of apps, and to MAKE SURE that the other corruption I've unwittingly done to my phone's data is complete eradicated.
I apologize for the jumbled nature of this post. I'm sure I'm leaving some diagnostic stuff out that would be useful--please fire away and I'll be more than patient about trying to clarify.
THANK YOU in advance for any help you can offer!
Click to expand...
Click to collapse
Boy, First of all don't panic. Without bricking you can't learn.
Second for Root you can use Gingerbreak. This should work. http://forum.xda-developers.com/showthread.php?t=1044765
for Flashing on all use custom recovery tool. And its like one two three from your phone only using terminal apps. Here is the guidehttp://androidforums.com/getitnowmarketing/221388-custom-recovery-optimus-one-p500-thunderg.html
After entering in Custom recovery mode you can do what ever you want to do. Flash rom as per your desire.
have you flashed clockworkmod recovery before?? if yes access it using the three button combo....you can flash any rom you want from recovery....
hit the thanks button if i have helped you.
sajjan said:
have you flashed clockworkmod recovery before?? if yes access it using the three button combo...
Click to expand...
Click to collapse
Alas, after restoring the stock, the three button combo brings up not clockworkmod, but "Android system recovery <3e>", which *only* allows:
reboot
apply sdcard update.zip
wipe data/factory reset
wipe cache partition
Since I don't have an update.zip file that works, I can't seem to get beyond this. When I tried renaming a custom rom recovery file update.zip, I got a signature mismatch, which makes sense.
First, thanks to both sweetbinodray and sajjan for the replies.
sweetbinodray said:
Boy, First of all don't panic. Without bricking you can't learn.
Click to expand...
Click to collapse
Hehe, that's similar to what I keep trying to tell myself.
Second for Root you can use Gingerbreak. This should work.
Click to expand...
Click to collapse
I have root, even have root explorer working via Amazon mktplace. (I shouldn't need or want to re-root, should I?)
for Flashing on all use custom recovery tool. And its like one two three from your phone only using terminal apps. Here is the guidehttp://androidforums.com/getitnowmarketing/221388-custom-recovery-optimus-one-p500-thunderg.html
After entering in Custom recovery mode you can do what ever you want to do. Flash rom as per your desire.
Click to expand...
Click to collapse
When I follow that guide, I'm linked to an updated thread which asks me to enter shell (no problem) then use the following command as first in a series:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
that results in "mount: operation not permitted".
Basically, having (regrettably) tried to to start from scratch by reflashing stock, I keep running into these permission snags.
Seems like if I could get to the CWM recovery screen, or figure out a way to trick the stock recovery screen into accepting a different update.zip, I'd be OK.
Then again, perhaps that's making things too complicated?
TIA once again!
Also, this looks like it might work, but I can't seem to get the validation email necessary to validate a board membership, which appears necessary to download the Quick Boot file.
polphi said:
First, thanks to both sweetbinodray and sajjan for the replies.
Hehe, that's similar to what I keep trying to tell myself.
I have root, even have root explorer working via Amazon mktplace. (I shouldn't need or want to re-root, should I?)
When I follow that guide, I'm linked to an updated thread which asks me to enter shell (no problem) then use the following command as first in a series:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
that results in "mount: operation not permitted".
Basically, having (regrettably) tried to to start from scratch by reflashing stock, I keep running into these permission snags.
Seems like if I could get to the CWM recovery screen, or figure out a way to trick the stock recovery screen into accepting a different update.zip, I'd be OK.
Then again, perhaps that's making things too complicated?
TIA once again!
Click to expand...
Click to collapse
Ok what i can suggest you is do manual set up for custom recovery using terminal apps. Here is the guide http://forum.xda-developers.com/showthread.php?p=15185778#post15185778 and start form install terminal emulator. And write following commands.. its like one to three....
Related
Hello!
I did something really stupid. I rooted my Vibrant, and all was super easy and fine, but my home button was being unresponsive so without thinking enough did a reset on my phone. I wanted to make sure I covered my bases so I downloaded Titanium Backup and "backed up" all of the important things....call log, contacts, browser history, etc. etc. then did the master reset, but I don't think it worked. So now that I have done the reset it gives me force close messages on all of the main functions of the phone....dialer, web, you name it. Plus my home button still isn't working :/
So, the way I see it I have two options; risk sending the phone back to t-mobile under the guise of the home button issue....and maybe pay dearly for it (Superuser is still in the apps)
OR....
Hope and pray in the power of the XDA Gods, at least in order to get this to the workable category.
Thanks for any advice!
Are you able to get to the "Terminal Emulator" without it FCing?
You could boot into Clockwork Recovery and flash eugene's STOCK rom to see if that fixes anything.
hmmm, there's only the superuser and then the preinstalled apps. i did the one click root, so maybe that was missing the terminal app?
twag said:
hmmm, there's only the superuser and then the preinstalled apps. i did the one click root, so maybe that was missing the terminal app?
Click to expand...
Click to collapse
No its not missing, the "one click" just does rooting for you. You have go to into the market and download the application "Terminal emulator," if you're able to get that then you can unroot yourself and exchange your phone without T-Mobile ever finding out that you rooted. Or you could try flashing a stock ROM with Clockwork Recovery
got it! unfortunately though, every time i click market i get the force close :/ Meanwhile, I downloaded the clockwork recovery, but I'm definitely new to this, so where would I wanna go from there?
Thanks a lot by the way
twag said:
got it! unfortunately though, every time i click market i get the force close :/ Meanwhile, I downloaded the clockwork recovery, but I'm definitely new to this, so where would I wanna go from there?
Thanks a lot by the way
Click to expand...
Click to collapse
Get Terminal Emulator as well; where do you want to go from now? You want to try to troubleshoot this problem or just unroot the phone and exchange it
Edit: Figure ill just make it easier.
If you want to troubleshoot: http://forum.xda-developers.com/showpost.php?p=7329357&postcount=2 is what you're looking for. Follow those instructions and your problems will most likely go away.
To unroot
Code:
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
Also remove apps that require root access.
Either one will do the trick. I would go with troubleshooting, the directions are simple. If it doesn't work then.. unroot and make sure that all the bloatware is there + no root applications so they wont be able to tell.
Here dude. It seems you can not download terminal emulator from the market, so here it is with the root file for good measure. Only thing is I hope you have a way to download it and get it to your phone. Gl, and let me know if you need any more help.
Just making sure we're on the same page.....so you meant to install clockwork on my computer right?
My market FC's every time i try to go in there.
Any way that I can at least get this guy to fly in under the warranty inspection radar and be functional is the way I'm wanting to go. should i attempt to load the files from the clockwork program into my phone? Sorry I'm so fuzzy on this.
One click root and unroot here http://forum.xda-developers.com/showthread.php?t=746129
twag said:
Just making sure we're on the same page.....so you meant to install clockwork on my computer right?
My market FC's every time i try to go in there.
Any way that I can at least get this guy to fly in under the warranty inspection radar and be functional is the way I'm wanting to go. should i attempt to load the files from the clockwork program into my phone? Sorry I'm so fuzzy on this.
Click to expand...
Click to collapse
If you can follow directions good, this post should solve your problem. http://forum.xda-developers.com/showthread.php?t=747634&page=2
Hey bro, here is a simple fix.
Download ROM Manager which I attached below and install it. Within ROM Manager you will have a option to install Clockwork, so go ahead and install in through ROM Manager. ( Clockwork gets installed on your device ). Then follow this link http://forum.xda-developers.com/showthread.php?t=740077 to download a stock Vibrant Rom. Follow the instructions on how to install the ROM, and you should be good.
Forgot permission for "unknown" in superuser app
Ok, so I accidently tapped forget for the "unknown" in super permissions and now when I try to type su in adb shell it says access denied. Any help?
I ve tried about 4 imulaters none will open.then I thought I had found the aswers to one of my issues, getting terminal imulator to work. But after ive installation and reboot just for good measure. I get the message that I cant install apps connected to the market. Im thinking maybe I should try unrooting and resetting the imei. Is there another way?
if youre getting a lot of fc errors, then odin back to JFD. make sure to use the .pit and .tar files. you'll be on official stock. then you can root/ update to official. anyway, its never a bad idea to go back to complete stock after major errors.
I tried this emulater su removal thing but it said that none of those fials exist. I am clearly rooted with su. Could it have something to do with my 17 digit imei cant seem toswitch back?
No and you seem to be pretty clueless to what they are suggesting you do. The easiest way to fix most problems with FC. Are using Odin to flash the OS back to stock. Several guides in the bible. Look under android development for the vibrant bible.
Maybe I should elaborate my issues so I dont seem so clueless, I dont have sync! I have tried kies, and odin but does didly squat w/o sync.
I dont have market access or OTA support. I just got back terminal after about 15 tries.
So im basically try to see which I get first; unrooted or stock reset. All of which seem to have some OTA necesity unless I can find a complete APK or termina access deal. Yea im a noob to
If your going to do anything to your phone such as rooting you need to download odin. There is a tutorial in the dev section under the vibrant bibal. Odin will restore your phone back to stock like it was out of the box. There are plenty of ppl willing to help on these forums so if you run into problems just ask. Every time I thought I screwed up my phone odin has saved my life.
Sent from my SGH-T959 using XDA App
Hi all! I'm really hoping that some Andriod guru out there can figure out the predicament I've gotten myself into. First a litte background info:
The other day I successfully flashed the new JI5 update to my phone. It worked great, and seems to have at least patched (not fixed) the majority of this phones shortcomings. But of course most of you already know all this.
I attempted to flash the same update to my wife's phone tonight, however as soon as ODIN finished doing it's thing the phone rebooted, and I now seem to be stuck in recovery with the following error:
update media, please wait
E:Can't mount /dev/block/stl10(Invalid argument)
E:copy_dbdata_media:Can't mount DBDATA:copy default media content failed.
The process I used to flash the phone is pretty standard. Fired up ODIN, used ADB to throw the phone into download mode (Both our phones seem to be HW locked), pushed the update to the phone. The one thing I DID do differently this time was select the Re-Partition option, as I've noticed some strange issues with my phone since throwing JI5 on it. I figured that repartitioning the phone back to it's prestine state might fix the issues. I made sure to use the correct 512 PIT file, which I think I remember reading was responsible for setting up the system partitions, thus I figured I wouldn't have any problems. I've read about many others that routinely repartition their phones, so I didn't think this would be an issue. Her phone was bone stock, aside from being rooted. No OC kernals, lagfixes, etc.
I've tried to throw the phone back into download mode via adb, but it just reboots the device and it immediatly goes into recovery mode. Since the phone still boots and gets into recovery mode I'm thinking it's not bricked, but I'll be damned if I know what to do next!
So how about it, any guru's out there that have seen this problem before? Any way it can be fixed?
Update: Still borked and at wits end! Since I still apparently have the ability to reinstall packages via recovery I'm hoping that there is a way to reflash the OS by utilizing a crafty update.zip file. Based off what I've read so far, I simply need to reflash to stock OS to get things rolling again, but I can't get the damn thing into download mode! So close, yet so far away. Thank you Samsung QA! I guess this is what I get for not clockwork modding her phone prior to working on it. But still, frigging ridiculous that this company is sending out broken hardware and untested products.
If anybody happens to know a way to utilize the recovery console to flash a firmware revision (without using clockworkmod recovery), or possibly how to perform a fix action via ADB, any info you can lend to me would be much appreciated.
Bumping for the sake of my sanity.
Anyone have any ideas as to how to fix this thing? I'm a hair's-breadth away from donating this thing to willitblend.
First I must scold you for not having Clockwork Recovery Flashed, it is the first thing you do when you have root. Period. Nothing else takes priority over being able to save your phone.
Secondly I must praise you for asking this in Q&A / General, NOT DEV! I FUC*ING HATE THAT! So thanks!
Steps to fix your wife's phone:
Step 1: Download attached zip, and put on phones internal SD. (adb push update.zip /sdcard/update.zip)
Step 2: Select Re-Install Packages from Stock Recovery Menu.
Step 3: Phone may reboot, if so see step 2. If phone enters clockwork go to step4.
Step 4: Flash Rom. Flash a full rom that is flashable via Clockwork. THAT OR::: try adb reboot download from clockwork.
Step 5: Reroot phone, install clockwork recovery (rom manager on market).
Optional: If all this doesn't work feel free to purchase my Vibrant, link in Sig
Edit: Also don't just do things you don't understand, like check repartition
Thank you sir! You're a saint!
zaduma said:
First I must scold you for not having Clockwork Recovery Flashed, it is the first thing you do when you have root. Period. Nothing else takes priority over being able to save your phone.
Secondly I must praise you for asking this in Q&A / General, NOT DEV! I FUC*ING HATE THAT! So thanks!
Steps to fix your wife's phone:
Step 1: Download attached zip, and put on phones internal SD. (adb push update.zip /sdcard/update.zip)
Step 2: Select Re-Install Packages from Stock Recovery Menu.
Step 3: Phone may reboot, if so see step 2. If phone enters clockwork go to step4.
Step 4: Flash Rom. Flash a full rom that is flashable via Clockwork. THAT OR::: try adb reboot download from clockwork.
Step 5: Reroot phone, install clockwork recovery (rom manager on market).
Optional: If all this doesn't work feel free to purchase my Vibrant, link in Sig
Edit: Also don't just do things you don't understand, like check repartition
Click to expand...
Click to collapse
Thanks for the fast reply! And yes, I feel retarded for not clockworking her phone. In my defense, I thought I knew what I was doing when I ticked the option, as I had read countless threads about repartioning the phone. I think the problem is that the JI5 update is an incremental update, not a full OS. By repartitioning and flashing I think the process removed some key OS files. Or not, I'm no expert when it comes to this OS.
Anyhoo, I tried pushing the file to the sdcard, however I am getting a permission denied error message. I've verified that the directory exists via the shell command, so I seem to be having some kind of a permissions problem. The root on her phone must have been undone, as when I try to enter SU I get the same permission denied error message. Is there a way around this?
Thank you for all the assistance thus far!
So while in recovery mode, I can see both drives showing up in disk manager and windows explorer on my computer, however they are grayed out. Typically at this point one would hit the "mount" button from the dropdown menu on the phone, but obviously this action is currently out of grasp due to my problem. Is there a way to manually mount the sdcard via adb?
I kind of figured that adb pushing stuff to the SDCARD didn't require root access, as I was always able to mount the two stores without root permissions from the phone...
I'm rather curious now. Has any one tried using the adb push command to copy files to the /sdcard directory on their phone without root? Everything I've read makes it sound like this should be possible, unless the phone is just that messed up.
Any and all replies appreciated!
Okay, so I've seen these issues dealt with separately, but never in conjunction. Unfortunately, I am having both in conjunction.
Starting with a fresh Droid Eris, I used a one-click root to allow superuser permissions.
From there, I flashed CM7. Along with many other users, I ran into the issue where I had no data or voice signal.
I'll let you know here, that I've wiped EVERY time I did anything. This is NOT a wipe issue.
I flashed the newest radio... No luck. So, I went through clockwork's recovery and reverted back to the original 2.1 ROM. Still no luck on the signal issue. At this point, I decided to reflash CM7 and try to deal with the issue through ADB.
This is where things went wrong. The load for CM7 corrupted (I'm assuming) and gave me a nice case of Bootloop. Thinking everything was fine, (Assuming I'd do a battery pull and just go back to 2.1) I booted into the original Android recovery and NOW the damn track ball will no longer make selections. It will scroll, but not select.
Here's my question: Seeing as I can not boot fully to allow usb debugging, and I can not recover through Android (Thank you, trackball), is there ANY way to reflash the original RUU through ADB?
Thus far, I can't get passed the obvious "This device is not ready," prompt.
Any help is greatly appreciated.
FYI, adb is available when the custom recovery is booted.
what that means is that with the recovery booted you can:
1) drop a smallish (say, less than 100 MB) ROM file into /cache (e.g. "adb push")
2) create an Android command file (/cache/recovery/command) with a single line that points at the ROM file as an update
3) do a "adb shell reboot recovery"
This will cause the subsequent boot to the recovery to automatically install the ROM file you dropped in cache.
Voila. No trackball needed.
The syntax for the command file (/cache/recovery/command) will be a single line:
--update_package=CACHE:your_ROM_file_name_goes_here.zip
See this post for an expanded explanation.
cheers
[ Edit ]
Note that the above is a thumbnail sketch which requires you to fill in the blanks. For instance, wiping /data and /cache and flashing packages after the main ROM. Cumbersome, but you only need to do it once. Once you have a rooted ROM installed, you should flash a trackball-free version of the recovery so you don't need this method for every ROM you install. Instructions for that (using "flash_image" via adb) can be found elsewhere.
Scott,
Whoa! You got a lot going on there...
Okay, I don't have all of the answers here for you, but I know enough to ask a few questions that we'll need a clarification on.
1. Can you tell us your HBOOT version and whether its S-ON or S-OFF?
2. You mentioned that you've used ClockworkMod (not good , but maybe not terrible)...you also have mentioned using/having Amon_RA custom recovery. Which custom recovery do you have currently installed and can you boot into said recovery?
3. By the way, I think the voice/data signal thing is fixable--it sounds familiar to me, but I don't know the answer right off-hand and this is not your primary issue at the moment.
4. You should be able to run the RUU to restore 2.1 back to your phone. It doesn't require a working custom recovery running and/or adb. Although you might simply be asking if you can flash a ROM through adb, then the answer is yes, you can. Although you will need custom recovery running to make sure its adb server is running and that, of course, require USB connectivity (alluding to your "This device is not ready." message).
5. Usually, installing HTC Sync will install the USB drivers necessary for you to use adb. If that doesn't work for you, PM me with your email address and I'll send you about 10MBs worth of USB drivers I've collected over the last year that might help you with this issue.
6. Lastly, there is a version of Amon_RA's custom recovery available that does not require the use of the trackball. You're not really in a position to flash/install that at this point unless you have the S-OFF engineering bootloader.
I'll hold-off with additional info pending your responses to the above.
Cheers!
edit: trumped by the Master himself, LOL! [I knew you'd be along sometime soon, bftb0 ]
scary alien said:
Scott,
Whoa! You got a lot going on there...
Okay, I don't have all of the answers here for you, but I know enough to ask a few questions that we'll need a clarification on.
1. Can you tell us your HBOOT version and whether its S-ON or S-OFF?
2. You mentioned that you've used ClockworkMod (not good , but maybe not terrible)...you also have mentioned using/having Amon_RA custom recovery. Which custom recovery do you have currently installed and can you boot into said recovery?
3. By the way, I think the voice/data signal thing is fixable--it sounds familiar to me, but I don't know the answer right off-hand and this is not your primary issue at the moment.
4. You should be able to run the RUU to restore 2.1 back to your phone. It doesn't require a working custom recovery running and/or adb. Although you might simply be asking if you can flash a ROM through adb, then the answer is yes, you can. Although you will need custom recovery running to make sure its adb server is running and that, of course, require USB connectivity (alluding to your "This device is not ready." message).
5. Usually, installing HTC Sync will install the USB drivers necessary for you to use adb. If that doesn't work for you, PM me with your email address and I'll send you about 10MBs worth of USB drivers I've collected over the last year that might help you with this issue.
6. Lastly, there is a version of Amon_RA's custom recovery available that does not require the use of the trackball. You're not really in a position to flash/install that at this point unless you have the S-OFF engineering bootloader.
I'll hold-off with additional info pending your responses to the above.
Cheers!
edit: trumped by the Master himself, LOL! [I knew you'd be along sometime soon, bftb0 ]
Click to expand...
Click to collapse
Yup bftb0 is a beast at these things, lol
Hi all,
I'm trying to install ClockworkMod with no luck. I'm getting the "Signature verification failed" error.
I have a Samsung Galaxy s2 9100M (bell/virgin version). Currently running everything stock except that I manually gained root access, compiled su binary and placed it in /system/bin (with appropriate permissions of course). I also installed busybox from source. So my phone is fully rooted, the superuser app works fine as well (used chainsdd su).
Now an obvious option is to use Odin and flash CWM recovery. However, I'm running Linux, so no Odin (I'd also like to avoid using a VM). What's the alternative? The stock recovery will not allow me to flash unsigned files.
Please feel free to provide complex solutions. I'm a professional software engineer with extensive unix/linux knowledge. I'm just not entirely familiar with the SGS2/android architecture but I can google the missing bits.
As an aside, if I end up having to flash the recovery partition with CWM, is this recovery overwritten when flashing the stock rom? I.e. does it rebuild it on first boot? Is it part of the rom?
To get CWM recovery, you need to flash a kernel which comes with it. Since you're rooted already, you can either do that using Heimdall, via an app such as Mobile Odin (several others exist) or manually via adb/terminal.
Why do I need an entire kernel? Can't I just install the recovery? I was planning on making a full backup of my stock phone, including the kernel, for recovery purposes.
I used Rom Manager and tried to flash CWM with it. It failed and left me with the update.zip which I can't flash in recovery because of the signature issue.
About the Apps, I've heard that Rom Manager isn't safe to use (i.e. may brick the phone). What about Mobile Odin (which isn't free)? Does using a pay app make it any safer?
Simple method .
Root + CWM .
http://forum.xda-developers.com/showthread.php?t=1103399
Why do I need an entire kernel? Can't I just install the recovery? I was planning on making a full backup of my stock phone, including the kernel, for recovery purposes.
As recovery is in the kernel the answer is no .
jje
ldiamond2 said:
Hi all,
I'm trying to install ClockworkMod with no luck. I'm getting the "Signature verification failed" error.
I have a Samsung Galaxy s2 9100M (bell/virgin version). Currently running everything stock except that I manually gained root access, compiled su binary and placed it in /system/bin (with appropriate permissions of course). I also installed busybox from source. So my phone is fully rooted, the superuser app works fine as well (used chainsdd su).
As an aside, if I end up having to flash the recovery partition with CWM, is this recovery overwritten when flashing the stock rom? I.e. does it rebuild it on first boot? Is it part of the rom?
Click to expand...
Click to collapse
I had this problem originally when i first rooted my phone, (S2 International). Signature Verification Failed.
I flashed a CWM based recovery, 4.0 or something and my problems went away. S2 Kernels and Recoveries are merged in one, thats why you can't have one with out the other.
If you flash a different rom, unless it comes with its own recovery, it won't overwrite yours.
ldiamond2 said:
I was planning on making a full backup of my stock phone, including the kernel, for recovery purposes.
Click to expand...
Click to collapse
Any backup you make will still be rooted, which is likely to invalidate warranty anyway.
Read this thread for how to achieve what you want: http://forum.xda-developers.com/showthread.php?t=1409484
Rooted is fine since I can manually remove the su binary and busybox.
I've seen this method before but I have seen no comments on if it really works or not. Maybe you have?
ldiamond2 said:
I'm a professional software engineer with extensive unix/linux knowledge. I'm just not entirely familiar with the SGS2/android architecture but I can google the missing bits.
Click to expand...
Click to collapse
ldiamond2 said:
I've seen this method before but I have seen no comments on if it really works or not. Maybe you have?
Click to expand...
Click to collapse
It's dd, not much else to explain to a Linux user .
If you follow the advice of dd'ing the kernel first, then flashing a kernel containing CWM and dd'ing all the partitions from within recovery (adb) and doing nandroid backup for good measure, there's really not a lot that can go wrong when it comes to restoring.
oinkylicious said:
there's really not a lot that can go wrong when it comes to restoring.
Click to expand...
Click to collapse
Well, one thing that comes to mind is missing partitions... Another is partitions residing in read-only memory (which you can't remount as read-write) for which dd wouldn't be helpful for restoring.
Also using dd to copy partitions mounted as read-write can cause a corrupted output. Who knows what happened while you were copying it.
Quoting the post: "Put back your Backups [untested]"
hi guys
i'm now using NEAK 2.0 SAMMY kernel on ICS that is working with CWM 5.5 (touch)
how can i change it to the simple CWM that just use button to work ?
is it possible?
I can't give you the verification you're looking for, I've never had an interest in getting my phone back to the condition it was in when I bought it (I rooted it the day I bought it, 11 months ago, and never looked back).
I don't believe any of the partitions are incapable of being mounted R/W. If they were, it would surely be irrelevant for you anyway since if you can't write to them, they're not going to change no matter what you do. Also, dd'ing from recovery over adb should ensure nothing is writing to the partitions.
oinkylicious said:
If they were, it would surely be irrelevant for you anyway since if you can't write to them, they're not going to change no matter what you do.
Click to expand...
Click to collapse
Well, depends what the flashing process involves. It can flash memory that otherwise can't be flashed from the OS.
Also, dd'ing from recovery over adb should ensure nothing is writing to the partitions.
Click to expand...
Click to collapse
That's definitely a way to avoid the corruption of the dd image.
god.fsl: Don't try to hijack the thread.
ldiamond2 said:
Well, one thing that comes to mind is missing partitions... Another is partitions residing in read-only memory (which you can't remount as read-write) for which dd wouldn't be helpful for restoring.
Click to expand...
Click to collapse
I am not really sure why you are trying to make easy things that difficult.
Have a look at the CF-Root Kernels.
These are kernels taken from stock ROM and only included necessary things like busybox, superuser, CWM and so on.
With CWM you can easily make a backup of your entire system.
Seriously it's a pretty easy things and you would have to worry alot less. Even if you are a professional linux software engineer.
PS: When working on the system like you are it might probably be a good idea to do a quick backup of your efs Folder
Hey everyone, (It's a long story: But I would really appreciate any help...)
[I know the easy solution: Boot into RECOVERY MODE and factory reset the phone and if all goes well...DONE.]
I'm running on Android 4.4.(the latest I think its '2'), Stock Firmware, 4G LTE form MetroPCS, and able to get into a so called 'recovery mode' (you can only factory reset the phone) and download mode. I can't get into safe-mode. and I'm Currently stuck in a bootloop or a 'soft-brick'.
Here's what happened:
I've recently been messing around with the tether_dun_required on my LG in order to get it be able to tether WiFi to my laptop.
The phone was rooted using this method: [GUIDE] New Root Method for LG Devices
[ROOT was successful]
I tried various SQLite3 editing apps to try and change the tether_dun_required record in settings.db in data/data/com.android.providers.settings/databases but after looking ant the SuperSU logs I got this error: Cannot [mount or chmod] ... because the filesystem is Read-Only...
So, I decided to use ES-File Explorer to pull the settings.db file to my computer and modified it using SQLite Studio then I copied the files to sdcard and renamed the old settings.db to settings_old.db using ES-File Explorer. (all over WiFi) Then I ran ADB shell and got root using 'su'. I remounted '/' , '/data', and '/system' as RW using "mount -o rw,remount /" and etc... Then, I used the "cp" command to copy the files from "/sdcard/settings.db" to "/data/data/com.providers.settings/databases". I assumed you needed to reboot. So I rebooted the phone. AND....bootloop.
I was going to make a nandroid backup or atleast copy anything important out of the phone but: being a noob... I didn't.
I can't get ADB to run either of the Download or Recovery modes.
I know (have a feeling...) I can fix the phone if I can rename the settings.db to something else and the settings_old.db to settings.db but I don't have access to the filesystem because I can't start ADB.
Ophidian_DarkCore said:
if your savvy with the shell, aroma fm has a built in terminal.
flash this in recovery http://forum.xda-developers.com/showthread.php?t=1646108
then cd to the directory.
rm settings.db
mv settings_old.db settings.db
Click to expand...
Click to collapse
Thanks you for you reply. I have one question though, I have no idea if my bootloader or my kernal or any of that is 'unlocked' I only rooted my phone. If I try to flash aroma fm and they are locked or something would that actually really brick my phone?
ALSO: I don't have an SDCARD... I don't think it's possible to flash anything then? Because flashing from the Internal Storage might brick the device. right?
ALSO: I don't think the LG Optimus F60 has ARM Neon support... & the "Recovery mode" doesn't have any flashing support. It's all STOCK.
LG Optimus F60 Specifications
Any Ideas?
Ophidian_DarkCore said:
well damn, if you have a custom recovery usb-otg you can make a flashable zip that runs some shell commands.
flashing wont brick a device. putting unsigned boot/recovery imgs usually bricks locked devices.
as with all lg devices, there is download mode to load stock firmware/updates. [LOL apparently I can't post outside links yet even, if their a quote...]
Click to expand...
Click to collapse
That's RIGHT! But, sorry for the noob question: What is a custom recovery usb-otg and how do I make a flashable zip that runs some commands? (For example: maybe one that just runs the commands but doesn't actually change the recovery software or the boot just one that can rename the files?)
Also, I don't think it would work but, would flashing the recovery to stock not delete any data, and have the phone be able to boot?
If it's too much to explain that's okay just show me some related posts that can show me how.
Thanks again for your time.
Ophidian_DarkCore said:
maybe try this http://forum.xda-developers.com/showpost.php?p=59637778&postcount=62
EDIT: Disregard below
you need a custom recovery before anything. and apparently your device supports fastboot.... so give this a go http://forum.xda-developers.com/and...8-5-0-touch-recovery-lg-t3049800#post59310323
and later you might get android L
Click to expand...
Click to collapse
I'm not sure, because the phone already has the factory boot and I haven't flashed anything into the Boot Partition. It's probably an error that happens when it tries to validate the settings.db or the permissions it has [chmod or that its mounted read write]. [To my understanding] what TWRP boot loop fix does is install fastboot then the custom recovery and the stock boot again. Which should do about the same thing because the phone is already stock. Right?
Would installing a custom recovery then allow me to access adb or the filesystem? (If so any recommendations?) Or how would I run a script from download mode?
Thanks for your time.
Ophidian_DarkCore said:
you only need to flash the recovery. not the boot img.
installing a custom recovery will either give you adb, or an on device shell.
Click to expand...
Click to collapse
That's right, Thank you. I'm going to try flashing one right now. Do you know of any that give you access to adb? (and maybe have low risk of bricking LG phones?)
Ophidian_DarkCore said:
the one in that thread should work.
fyi, recoveries, roms, and kernels are specialised software usually only compatible with one model. so no mixxy matchy
i guess using those instructions you could try the img from here http://forum.xda-developers.com/and...8-5-0-touch-recovery-lg-t3049800#post59310323
Click to expand...
Click to collapse
How would I install the img? I would need to install fastboot, right? Then run fastboot ****.img?
Is fatboot run from adb or from SendCommand.exe?
Thanks again for all your help.
Ophidian_DarkCore said:
yea, just grab a fastboot binary, the lg driver, go into whatever mode in that thread and
Code:
fastboot flash *.img
edit: fastboot is it's own binary. so it's run in a command shell on your pc like adb is.
Click to expand...
Click to collapse
One last question (Need to make sure...): I have fastboot.exe from the SDK tools, so all I need to do is:
1. Connect the USB
2. Boot into Download Mode
3. Run fastboot flash *.img
4. When finished unplug the USB and take the battery out.
5. Then boot back into Download mode or Recovery Mode to get TWRP?
6. Then try to see if I can get ADB to work?
Also, sorry for all the questions: But If I ever needed to, will a factory reset delete TWRP or will I need to flash it again with the Stock recovery?
Thanks for your time. You are awesome.
Hi, thank you for using XDA Assist. Unfortunately there is no device specific forum for your device. I'm going to ask a moderator to move your thread here, http://forum.xda-developers.com/android/help
Solved it.
I used an exploit to access the filesystem and fix the corrupt db.
crazy_code said:
Hey everyone, (It's a long story: But I would really appreciate any help...)
[I know the easy solution: Boot into RECOVERY MODE and factory reset the phone and if all goes well...DONE.]
I'm running on Android 4.4.(the latest I think its '2'), Stock Firmware, 4G LTE form MetroPCS, and able to get into a so called 'recovery mode' (you can only factory reset the phone) and download mode. I can't get into safe-mode. and I'm Currently stuck in a bootloop or a 'soft-brick'.
Here's what happened:
I've recently been messing around with the tether_dun_required on my LG in order to get it be able to tether WiFi to my laptop.
The phone was rooted using this method: [GUIDE] New Root Method for LG Devices
[ROOT was successful]
I tried various SQLite3 editing apps to try and change the tether_dun_required record in settings.db in data/data/com.android.providers.settings/databases but after looking ant the SuperSU logs I got this error: Cannot [mount or chmod] ... because the filesystem is Read-Only...
So, I decided to use ES-File Explorer to pull the settings.db file to my computer and modified it using SQLite Studio then I copied the files to sdcard and renamed the old settings.db to settings_old.db using ES-File Explorer. (all over WiFi) Then I ran ADB shell and got root using 'su'. I remounted '/' , '/data', and '/system' as RW using "mount -o rw,remount /" and etc... Then, I used the "cp" command to copy the files from "/sdcard/settings.db" to "/data/data/com.providers.settings/databases". I assumed you needed to reboot. So I rebooted the phone. AND....bootloop.
I was going to make a nandroid backup or atleast copy anything important out of the phone but: being a noob... I didn't.
I can't get ADB to run either of the Download or Recovery modes.
I know (have a feeling...) I can fix the phone if I can rename the settings.db to something else and the settings_old.db to settings.db but I don't have access to the filesystem because I can't start ADB.
Maybe it's the fact the system was still mounted as Read-Write when I rebooted and the stock firmware just doesn't like that...
I'm new to android but love to code C, C++, and C#. Does anybody know of any API's that might help me access the filesystem in download mode. Because I'm almost certain the root method I used, used that as an exploit to root the phone.
Or can someone at least point me in the right direction as to how to UN-softbrick the phone without 'factory-resetting' it. I would really love to be able to recover my contacts and pictures.
Click to expand...
Click to collapse
I did the same thing, you installed the wrong model FW. just install the base rom and start over.
crazy_code said:
Hey everyone, (It's a long story: But I would really appreciate any help...)
[I know the easy solution: Boot into RECOVERY MODE and factory reset the phone and if all goes well...DONE.]
I'm running on Android 4.4.(the latest I think its '2'), Stock Firmware, 4G LTE form MetroPCS, and able to get into a so called 'recovery mode' (you can only factory reset the phone) and download mode. I can't get into safe-mode. and I'm Currently stuck in a bootloop or a 'soft-brick'.
Here's what happened:
I've recently been messing around with the tether_dun_required on my LG in order to get it be able to tether WiFi to my laptop.
The phone was rooted using this method: [GUIDE] New Root Method for LG Devices
[ROOT was successful]
I tried various SQLite3 editing apps to try and change the tether_dun_required record in settings.db in data/data/com.android.providers.settings/databases but after looking ant the SuperSU logs I got this error: Cannot [mount or chmod] ... because the filesystem is Read-Only...
So, I decided to use ES-File Explorer to pull the settings.db file to my computer and modified it using SQLite Studio then I copied the files to sdcard and renamed the old settings.db to settings_old.db using ES-File Explorer. (all over WiFi) Then I ran ADB shell and got root using 'su'. I remounted '/' , '/data', and '/system' as RW using "mount -o rw,remount /" and etc... Then, I used the "cp" command to copy the files from "/sdcard/settings.db" to "/data/data/com.providers.settings/databases". I assumed you needed to reboot. So I rebooted the phone. AND....bootloop.
I was going to make a nandroid backup or atleast copy anything important out of the phone but: being a noob... I didn't.
I can't get ADB to run either of the Download or Recovery modes.
I know (have a feeling...) I can fix the phone if I can rename the settings.db to something else and the settings_old.db to settings.db but I don't have access to the filesystem because I can't start ADB.
Maybe it's the fact the system was still mounted as Read-Write when I rebooted and the stock firmware just doesn't like that...
I'm new to android but love to code C, C++, and C#. Does anybody know of any API's that might help me access the filesystem in download mode. Because I'm almost certain the root method I used, used that as an exploit to root the phone.
Or can someone at least point me in the right direction as to how to UN-softbrick the phone without 'factory-resetting' it. I would really love to be able to recover my contacts and pictures.
Click to expand...
Click to collapse
i need to restore my lg f60 (i'm in the us and the carrier it supports is metropcs). i have TWRP recovery on it. can someone link to stock firmware/rom (whatever the terminology is...basically the operating system that the phone came w/), usb drivers, software tool to install the firmware, and everything i need to restore my phone back to how it was when i bought it.
i was curious and tried lollipop (i think i tried both 5.0 something or 5.1 something or just one of them ended up working) but the camera was completely non-functional so now i need to go back to the phone being how it was when i bought it.
the firmware i've installed on the phone right now is MS39510G_00 (i think "MS39510G" is the actual identifier of the firmware, and the 00 is probably not useful for anything; the site i got it from maybe just appends it for some reason). but this firmware doesn't seem like what the phone came with or i'm not using/not doing everything i need to to restore it back to normal.
couple of things that strike me as odd and make me think that i don't have the right firmware or just didn't do something right:
there's a weird white area at the bottom, which i think was transparent and took on the color of the wallpaper on the phone when you just bought it & didn't mess around w/it
some of the icons are just the generic green android icon. a lot of apps have this same icon instead of different icons of their own
the lock screen seems also seems kind of different. it doesn't look like the lock screen of a new lg f60. maybe i was using a custom lock screen (i doubt it, but it's possible) but still it doesn't look like the standard lock screen to me
how do i restore my us metropcs lg f60 phone back to stock?
i need to restore my lg f60 (i'm in the us and the carrier it supports is metropcs). i have TWRP recovery on it. can someone link to stock firmware/rom (whatever the terminology is...basically the operating system that the phone came w/), usb drivers, software tool to install the firmware, and everything i need to restore my phone back to how it was when i bought it
i was curious and tried lollipop (i think i tried both 5.0 something or 5.1 something or just one of them ended up working) but the camera was completely non-functional so now i need to go back to the phone being how it was when i bought it.
the firmware i've installed on the phone right now is MS39510G_00 (i think "MS39510G" is the actual identifier of the firmware, and the 00 is probably not useful for anything; the site i got it from maybe just appends it for some reason). but this firmware doesn't seem like what the phone came with or i'm not using/not doing everything i need to to restore it back to normal.
couple of things that strike me as odd and make me think that i don't have the right firmware or just didn't do something right:
there's a weird white area at the bottom, which i think was transparent and took on the color of the wallpaper on the phone when you just bought it & didn't mess around w/it
some of the icons are just the generic green android icon. a lot of apps have this same icon instead of different icons of their own
the lock screen also seems kind of different. it doesn't look like the lock screen of a new lg f60. maybe i was using a custom lock screen (i doubt it, but it's possible) but still it doesn't look like the standard lock screen to me
Help Help
Help anyone, i have LG f60 (390n) running with 5.0.1 lollipop. I wanted to instal custom recovery and install custom rom CM. But i have two problems:
1. If i want to boot to download mode - i have error "SECURE BOOT ERROR" (but it boots up normally, and work normally)
2.If i want to boot to recovery mode - i have error "LOADING KETSTORE FAILED STATUS 5"
Please help.
I am not able to flash it trough LG Flash tool, and i am not able to boot into custom recovery.