Please Help.
- Thread starter Rocka210
- Start date
We don't have the time or patience to split hairs in this case. Berating another member in a condescending post does no good for you, the other member, or anyone else reading this thread. I'd like to direct your attention to two of the forum rules that you agreed to follow when signing up for your account:
In regards to the post immediately preceding mine, I'd like to direct you to the following forum rule:
With that said, we can end discussion of this topic and get back to the topic of this thread. Any further off-topic posts will be deleted.
Sorry for the interruption folks, please continue
Ok thank you, I understand now, I wasn't trying to insult him but I could've had a more helpful tone. Thank you for clarifying that for me.
SORRY for taking thread OT. OP, I recommend you do more reading before you ask people questions, because from the looks of it, it seems that you have not done any reading at all, you just want people to explain everything for you. That is my opinion.
Sent from my LG-VM670 using Tapatalk 2
I actually have done a lot of reading, which is why I posted this thread... I've been trying to fix it for a day and then I thought I should ask for help. I'm not trying to be in anyone's hair or annoy anyone, I just really want to fix this.
You say you've done a lot of reading, I'm not sure what but maybe you missed this:
<a href="http://forums.androidcentral.com/optimus-v-rooting-roms-hacks/108282-how-simplified-root-recovery-custom-rom.html"> Simplified Rooting</a>
It's a guide that is a sticky here on the forum. It says clearly, do not hit factory reset after rooting your phone, that's a huge headache for everyone.
Sent from my LG-VM670 using Tapatalk 2
Last edited:
I'm a member of other Android forums, and every guide I've read says the same thing: do not factory reset after rooting. Do not use ROM manager on OV, it doesn't fully flash. Make a Nandroid backup.
Last edited by a moderator:
I'm sorry. I hadn't ever run into it while learning to root phone (odd)
I've learned my lesson, now I just want to fix it...
I've learned my lesson, now I just want to fix it...
There are threads all over the place. Check the stickies them go to the getting started thread. Everything is right there
Sent from my LG-VM670 using Tapatalk
Don't worry, you can recover your phone, it's just going to take some time and patience.
To get ADB working, check the stickies in this forum, they have step by step instructions. ADB is simply a means of using a command window to control your phone.
Once you have ADB installed, you will boot your phone into recovery, then hook it up to your computer. On your computer, (W7/XP) press your start button, then type in cmd and press enter. A command window should open up. Now look at where ADB was installed (usually the adb folder /platform-tools). You need to "cd" into that directory. So if it's C:\android-sdk\platform-tools, type in:
ADB should start up, then once it connects to your phone, you should see a different prompt. Now exit the shell by typing in exit and pressing return. You should now be back to the normal command prompt.
Download the flash_image binary, the xionia recovery img file, and the ROM zip file you want to use (and gapps in needed) and place them all on your sdcard by using the ADB push command:
(Note- only the ROM and gapps should be zip files, the flash_image binary has no extension, and xionia should be an img file)
Now, type in adb remount. If this succeeds, you are still rooted, a good thing. If it fails, stop now and see note at end of post.
Now you will install the flash_image binary, and use it to flash the xionia recovery image to your phone, then reboot so it can fix the bootloop issue.
Note- the last line is typed in the normal command window after exiting the ADB shell.
If you get errors at any step, it's probably due to not having root, post the errors so we can help.
Now, if everything worked, you'll be in xionia recovery. In here, you should wipe cache, then under advanced wipe dalvik-cache, then under mounts you should format boot, system, data, and cache.
Now go back to the main menu, and choose to install zip from sdcard. First install the ROM zip, then do the same steps to flash the gapps zip.
Now go back to the main menu, and reboot. Be patient, the first boot after doing all this may take a long time (rebuilding files). If the phone doesn't boot up after 10 full minutes, let us know.
[NOTE]If any of this fails, please use the forum's thread search feature. Click on one of the sticky threads, then near the top right, you'll see the link to search the thread. I recommend choosing show posts.
If you can't find the solution, let us know and we will attempt to help out.
The reason some people are being hostile is because all of this information has been posted over and over and over, and is included in the stickied threads. You may be new to these types of forums, and not be aware of the wealth of information available in most forum's stickied posts. Check them out, read them all the way through, and soon you'll be the one answering questions around here!
[/NOTE]
To get ADB working, check the stickies in this forum, they have step by step instructions. ADB is simply a means of using a command window to control your phone.
Once you have ADB installed, you will boot your phone into recovery, then hook it up to your computer. On your computer, (W7/XP) press your start button, then type in cmd and press enter. A command window should open up. Now look at where ADB was installed (usually the adb folder /platform-tools). You need to "cd" into that directory. So if it's C:\android-sdk\platform-tools, type in:
Code:
cd c:\android-sdk\platform-tools
adb shellDownload the flash_image binary, the xionia recovery img file, and the ROM zip file you want to use (and gapps in needed) and place them all on your sdcard by using the ADB push command:
(Note- only the ROM and gapps should be zip files, the flash_image binary has no extension, and xionia should be an img file)
Code:
adb push c:\PATH_TO_FILES\flash_image /sdcard/flash_image
adb push c:\PATH_TO_FILES\flash_image /sdcard/NAME_OF_XIONIA_RECOVERY.img
adb push c:\PATH_TO_FILES\flash_image /sdcard/NAME_OF_ROM.zip
adb push c:\PATH_TO_FILES\flash_image /sdcard/NAME_OF_GAPPS.zipNow, type in adb remount. If this succeeds, you are still rooted, a good thing. If it fails, stop now and see note at end of post.
Now you will install the flash_image binary, and use it to flash the xionia recovery image to your phone, then reboot so it can fix the bootloop issue.
Code:
adb shell
mv /sdcard/flash_image /system/bin/flash_image
chmod 0777 0655 /system/bin/flash_image
flash_image recovery /sdcard/NAME_OF_XIONIA.img
exit
adb reboot recoveryIf you get errors at any step, it's probably due to not having root, post the errors so we can help.
Now, if everything worked, you'll be in xionia recovery. In here, you should wipe cache, then under advanced wipe dalvik-cache, then under mounts you should format boot, system, data, and cache.
Now go back to the main menu, and choose to install zip from sdcard. First install the ROM zip, then do the same steps to flash the gapps zip.
Now go back to the main menu, and reboot. Be patient, the first boot after doing all this may take a long time (rebuilding files). If the phone doesn't boot up after 10 full minutes, let us know.
[NOTE]If any of this fails, please use the forum's thread search feature. Click on one of the sticky threads, then near the top right, you'll see the link to search the thread. I recommend choosing show posts.
If you can't find the solution, let us know and we will attempt to help out.
The reason some people are being hostile is because all of this information has been posted over and over and over, and is included in the stickied threads. You may be new to these types of forums, and not be aware of the wealth of information available in most forum's stickied posts. Check them out, read them all the way through, and soon you'll be the one answering questions around here!
[/NOTE]
Last edited:
I think during my experimental process I unrooted my phone. On adb when I type in "adb shell" I get this as my next line
~#
and then any command I give, it returns. I'm currently looking around the forums to try to reroot my phone while in recovery mode, is that what I need to do next?
~#
and then any command I give, it returns. I'm currently looking around the forums to try to reroot my phone while in recovery mode, is that what I need to do next?
"~#" means that you are in recovery mood, the instructions Jerry gave you you phone needs to be booted into your home screen. Plus factory reset does not unroot your phone, as everything need for root is installed in the system partition.
Sometimes I get (Status 0) but most of the time it just says "Installation aborted."
That is because you are trying to flash a zip without an update-binary and updater-script. Those files need to be copied and flashed while the phone is booted into your home screen.
I can't boot to my home screen, though. Whenever my phone is turned on, it loads the recovery and I can't leave it.
Do you have Android Platform-Tools installed and have you ever used it? If so then this is what you are looking for.
break recovery boot loop.
break recovery boot loop.
Is my timing still way off?
I keep doing it and I either get,
"error: device not found" or
"/sbin/sh:flash_eraseall: not found
/sbin/sh: adb: not found"
By the way:
does it matter that mine loads to clockworkmod recovery, not the stock recovery?
I keep doing it and I either get,
"error: device not found" or
"/sbin/sh:flash_eraseall: not found
/sbin/sh: adb: not found"
By the way:
does it matter that mine loads to clockworkmod recovery, not the stock recovery?
I would imagine when I had this issue and was told many times that the modded recovery is a bit better as you can flash whatever you want with it.
Similar threads
Trending Posts
-
PERMANENTLY disable wifi to switch to mobile data on INFINIX phone
- Started by stonefruit
- Replies: 1
-
-
-
-
Facebook
Twitter
Instagram