Related
Need help please... fellow vm670 users. (Clockworkmod) not working (rom manager)
Sent from my VM670 using XDA Premium App
Don't use rom manager manually flash recoveries
Sent from my Optimus V
belive me i wont.. I have locked up 2 other optimus v's... I dont under stand i have used rom manager on 2 different. phone models in the past and put custom
roms with no problems... obviously that is not the case with the vm670!!! Well than
Do you have the optimus vm670.... if so
I need some advise .. How do you manualy flash a recovery .... And witch version to use for the Optimus VM670
If you have terminal emulator type
Su
Flash_image recovery /sdcard/recovery.img (your recovery file might be called something else, mine is called vrecovery.img, so I typed that in) then turn off phone, hold the home button, volume down and power until your phone gets past the first LG screen. And I hope you have a backup to load. And don't forget to type su first.
Or you can hook it up to your computer and use adb to type in commands. I haven't tried that yet, so I don't know if the commands are the same.
Sent from my LG-VM670 using XDA App
ok thanks.. so that is what the terminal emulator is for... Well have you ever tried to do something in the past and ended up with a blue screen (fastboot)?
this had happened to me twice already, and had to replace. both devices almost afraid to try anything ... are you currently using
a custom rom? Also what would be the best way to backup with out. using Rom Manager ? or would it be ok to use RM
just for a backup
jessemc said:
ok thanks.. so that is what the terminal emulator is for... Well have you ever tried to do something in the past and ended up with a blue screen (fastboot)?
this had happened to me twice already, and had to replace. both devices almost afraid to try anything ... are you currently using
a custom rom? Also what would be the best way to backup with out. using Rom Manager ? or would it be ok to use RM
just for a backup
Click to expand...
Click to collapse
http://romrepo.info/wiki/index.php?title=Main_Page
Go to the link above and follow step by step, you could have saved your last two phones with this. Once you do this, you should be safe using rom manager on future flashes. I use it all the time... don't skip any steps
And the blue screen is the boot screen, that's about as much as I know a out it, I'm pretty new to all of this, I think it comes up if no recovery is installed
And I am using the most recent aosp cm7 if you follow the link uptop it will walk you through everything, even backing up. Its almost impossible to fully brick these things, and one more thing, leave all files zipped, ce recovery unzips them, they aren't normal .Zip files
Sent from my LG-VM670 using XDA App
Ok thanks...well the only problem is that I really don't have pc access to flash a custom recovery ...sucks..
Also tried to use terminal emulator
No luck.." flash.img not found"
Tons of people blogging same results .. well I guess I will have to wait, for computer access Or an easier way ...What really sucks is that I have a older 2.1 disconnected android with CyanogenMod 7 running android
2.3 Awesome ....
Wish could I could get on my optimus v ! Or something like it
Sent from my VM670 using Tapatalk
I ported over 2nd-init for Gingerbread from the Atrix to the Photon. The only thing I changed was init.rc, by replacing it with the Photon's init.rc. The real credit for this goes to eval. He is the one that got it working on Gingerbread for the Atrix.
Requirements:
Rooted Photon
Instructions:
1. Use your favorite method to get http://higgs.cygnusx-1.org/~edgan/2nd-init-Photon-0.9.tar.gz onto the phone in /mnt/sdcard/download
2. Start adb/ssh/terminal
3. Run su to become root
4. export PATH=/usr/bin:/usr/sbin:/bin:/sbin:/system/bin
5. Run mount -o remount,rw /system
6. mv /system/bin/remountpds /system/bin/remountpds.orig
7. Run tar -C / -zxf /mnt/sdcard/download/2nd-init-Photon-0.9.tar.gz
8. Run ls -a -l /system/bin/2nd-init to verify it is there. If it is not there, and you don't know how to fix it, then go to the revert instructions.
9. Reboot phone while holding volume down
10. Wait till you see Fastboot at the top of the screen
11. Press volume down repeatedly till it says USB Early Enumeration
12. Press volume up, and wait for it to boot
13. Start adb/ssh/terminal
14. export PATH=/usr/bin:/usr/sbin:/bin:/sbin:/system/bin
15. mount | grep debugfs
16. Look for good output, but if you get no output, it didn't work.
Good output:
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,relatime)
Revert instructions:
1. mv /system/bin/remountpds.orig /system/bin/remountpds
Thank you eval!
Thank you bane449!
Thank you Yay!
Happy my work could be of use =) Real credit goes to Skrilax_CZ for writing it!
Anyone curious to know what had to be changed to make it work on Gingerbread should read my posts here:
http://forum.xda-developers.com/showthread.php?t=1139768
http://forum.xda-developers.com/showpost.php?p=15067042&postcount=10
cheers!
edgan said:
I ported over 2nd-init for Gingerbread from the Atrix to the Photon. The only thing I changed was init.rc, by replacing it with the Photon's init.rc. The real credit for this goes to eval. He is the one that got it working on Gingerbread for the Atrix.
Requirements:
Rooted Photon
Instructions:
1. Use your favorite method to get http://higgs.cygnusx-1.org/~edgan/2nd-init-Photon-0.9.tar.gz onto the phone in /mnt/sdcard/download
2. Start adb/ssh/terminal
3. Run su to become root
4. export PATH=/usr/bin:/usr/sbin:/bin:/sbin:/system/bin
5. Run mount -o remount,rw /system
6. mv /system/bin/remountpds /system/bin/remountpds.orig
7. Run tar -C / -zxf /mnt/sdcard/download/2nd-init-Photon-0.9.tar.gz
8. Run ls -a -l /system/bin/2nd-init to verify it is there. If it is not there, and you don't know how to fix it, then go to the revert steps.
9. Reboot phone while holding volume down
10. Wait till you see Fastboot at the top of the screen
11. Press volume down till it says USB Early Enumeration
12. Press volume up, and wait for it to boot
13. Start adb/ssh/terminal
14. export PATH=/usr/bin:/usr/sbin:/bin:/sbin:/system/bin
15. mount | grep debugfs
16. Look for good output, but if you get no output, it didn't work.
Good output:
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,relatime)
Revert instructions:
1. mv /system/bin/remountpds.orig /system/bin/remountpds
Thank you eval!
Thank you bane449!
Thank you Yay!
Click to expand...
Click to collapse
Thank you very much for all the hardwork and job well done! Do we need to do this thru Terminal Emmulator, or just adb thru command prompt? Please advise.
Wondering what is second init? Me too... Here is the text from and-developers.com's wiki page.
The following binary will basically inject code to /init to “restart itself” allowing you to use custom init binary and init.rc scripts without side effects developed by Skrilax_CZ. Technically using code injection the code to call “execve(”/init”, {”/init”, NULL**, environ);” is injected and the environ variables are read from /proc/1/environ by the binary. Note that this is recomended only to be used with the “sh hijack” or inside recovery. You only need to replace the files in the filesystem.
Click to expand...
Click to collapse
Second init will allow aosp roms to be ran over the stock kernel with the locked bootloader. This is awesome news and i cant wait to see people working on CM7 and just aosp in general. Awesome work again guys
brianez21 said:
Wondering what is second init? Me too... Here is the text from and-developers.com's wiki page.
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
yyess!!!! you guys are the best. Cant wait to see AOSP
What is the difference between this and the cwm bootstrap recovery posted by kennethpenn? Which is better to have?
Sent from my MB855 using XDA Premium App
Two totally different things. This is not a recovery.
sub2k1 said:
What is the difference between this and the cwm bootstrap recovery posted by kennethpenn? Which is better to have?
Sent from my MB855 using XDA Premium App
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
mikeyinid said:
Two totally different things. This is not a recovery.
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
My experience is that they (2nd-init and CWM) are best used together.
I haven't had the chance to use the photon yet but I have worked a Defy and the 2nd-init gives a way to boot directly into the custom recovery which is super handy when you have flashed something that didn't work perfectly.
Maybe i dont fully understand 2nd init then. I know on the Droid X if your running CM7(2nd init) and you try to bootstrap into recovery you have to sbf. Guess I better do some more research...
* I think you misread the question that I was answering or something. He asked what the difference between 2nd init and bootstrap were.
mr_wrong_0 said:
My experience is that they (2nd-init and CWM) are best used together.
I haven't had the chance to use the photon yet but I have worked a Defy and the 2nd-init gives a way to boot directly into the custom recovery which is super handy when you have flashed something that didn't work perfectly.
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
mikeyinid said:
Maybe i dont fully understand 2nd init then. I know on the Droid X if your running CM7(2nd init) and you try to bootstrap into recovery you have to sbf. Guess I better do some more research...
* I think you misread the question that I was answering or something. He asked what the difference between 2nd init and bootstrap were.
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
Sir I yield to your knowledge.
I am admittedly new to Moto phones and I haven't put any custom roms on one except the Defy and I think that one might be a pretty odd duck.
The process on the Defy is: Root first of course (SuperOneClick was what I used) install both 2nd-init and CWM each via an APK.
Then you could restart the phone and when the blue light came on you had to push vol down and choose custom recovery.
I say they are best used together because if you don't have 2nd-init the only way to boot into the custom recovery was to boot into android and open the system recovery app and choose reboot into recovery, but there are times when something goes wrong and it doesn't boot. In that case it's nice to be able to hardware boot into the recovery using 2nd-init.
I understand that he was asking the difference between the two, but I wanted to point out that there are times when they are used together.
After thinking it over it's possible that it wasn't as helpful as I had hoped it would be.
EDIT ** I see you are from Idaho... What part? I'm in northern Utah just across the boarder.
If the photon gets cm7 or asop before ATRIX im going to throw my ATRIX in the ocean and buy an iphone. And never look at android again. Ever. Period.
Sent from my MB860 using XDA Premium App
In step 4 do I actually type export PATH= in adb or does it start with PATH=? Sorry for the noob question im new to this Motorola thing HTC rooting seemed so much easier! Trying to learn all over again. Lol. Actually I love learning all this. I thought I was an expert until getting this Photon.
Sent from my MB855 using XDA Premium App
And now I know what I'm replacing my locked EVO with next month! Strong work!
So, if I have the Bootstrap Recovery installed, how exactly would I go about getting to it from 2nd-init once I have made the necessary changes?
Thanks!
Im wondering the same thing!
Sent from my MB855 using xda premium
I was glad to see there was another option for custom ROMS via 2nd-init. By the looks of the dates on this thread, 2nd-init became a dead issue? That's too bad, reading thru the posts, it sounded promising for a user with a locked bootloader and possibly using Bootstrap Recovery. Guess imma have to do some more research regarding this because the OP, with the Title "Let the ROMS poor in!!" made it seem like everyone develops using 2nd-init or something to that effect!
Maybe with the locked down bootloader on 2.3.5, some one will come back to this and give it another run thru!!?
I'm currently on 2.3.5 and use BSR and am thinking imma run the 2nd-init script to see what happens. I'm just personally not sure where to go or what to do afterwards...
Typed on my Mo-Pho 4G (using SprintRocko235 ROM *locked* over 2.3.5 thru BSR) using xda-premium
Of course, Motorola Defy has CM9 running with less issues, than we have and that all with locked bootloader, because of this tool and Epsylon, Quarx, Maniac and others.
And probably thanks TI, for better development support, then Nvidia.
Here is a good description how 2nd-init works.
http://cvpcs.org/blog/2011-06-14/2nd-init._what_it_is_and_how_it_works
Sent from my MB855 using Tapatalk 2
That was a great read. Its a shame nobody ever developed a cm9 rom for 2nd init but Im not sure cm9 would run so smoothly with the stock Motorola gb kernel. If I remember correctly we ended up unlocking the boot loader about two weeks after this was announced and 2nd init is used for bootstrap recovery so it wasn't an entire waste.
Sent from my MB855 using xda premium
Ok my question is this. I have rooted an unlocked the bootloader on my atrix. Not really impressed with themes that are out there. Most of which have to be applied to custom roms anyway.
I have pulled my blur-res.apk and my frameowrk-res.apk. i have modified both the way i want and whem i try to adb push them. I keep getting permission denied. As well i habe also tried to install them usimg root explorer. After reboot i still have stock framework. What can i do to make my modifications stick?
Also.... how if possible can i change my kernel so that i may overclock, if its even possible on stock firmware. Thanks for your help in advance.
SErooted
Sent from my X10i using XDA App
Make sure your rom is deodexed. Run adb as root permission and faux has a stock kernal that is oc'd
sent from my Atrix via XDA premium
adb remount
marko! said:
Make sure your rom is deodexed. Run adb as root permission and faux has a stock kernal that is oc'd
sent from my Atrix via XDA premium
Click to expand...
Click to collapse
? how to deodex my rom? saw a tutorial but wont work as i run ubuntu and from what i saw you need windows. but correct if wrong
update..... ok i found a deodex .zip for 1.8.3... im hoping that is what i have on my atrix system version is 4.1.26 android version 2.2.1 bb version n_01.77.05p webtop version is 4.257.14
matthew5025 said:
adb remount
Click to expand...
Click to collapse
adb remount not working....
[email protected]:~$ adb remount
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
remount failed: Operation not permitted
[email protected]:~$
SErooted said:
adb remount not working....
[email protected]:~$ adb remount
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
remount failed: Operation not permitted
[email protected]:~$
Click to expand...
Click to collapse
Do you have root access?
You should just flash a stock deodexed rom and start from there
sent from my Atrix via XDA premium
I have root access yes. But still get errors when pushing files...as to a stock deodexed rom..... where can I find one that is not on 4.5.91?
Sent from my MB860 using XDA App
What one are you looking for? There is also a post somewhere (ill try and find it) on how to manually deodex any rom. You needvto be deodexed for that to work
sent from my Atrix via XDA premium
Edit
http://forum.xda-developers.com/showthread.php?t=1162764
marko! said:
What one are you looking for? There is also a post somewhere (ill try and find it) on how to manually deodex any rom. You needvto be deodexed for that to work
sent from my Atrix via XDA premium
Edit
http://forum.xda-developers.com/showthread.php?t=1162764
Click to expand...
Click to collapse
This I understand. however when i have searched for the manual deodex options... search query returns same results of some program that i have to use. unfortunately this program only works on a Windows based machine. I am on Ubuntu 10.04.
All other searches take me to other device forums/threads and still offer no help with doing this on the atrix with/without said Windows program..
i understand i can run it in vbox or an emulator, however my windows xp/7 disks are corrupt and wont let me reinstall. win7 stops install @72% while xp tosses a blue screen.
hence the reason i have ubuntu as my os as it is the only none corrupted disc that i have for an os at this time.:-(
Ok.... here is something that i find interesting.... I am able to change my boot animation using root explorer. set permissions. reboot new animation is there. i have taken the deodex.zip for 1.8.3 and when it rom manager after trying to flash i get the amend script error. It says it was tossed out when they created the GB ready cwm. So how can i get a stock deodexed rom to work with? I am not finding links anywhere that will get me to a download that is a stock deodexed rom.
(Rephrase) I have found a stock deodexed rom based on 4.5.91 however am curious if flashing this( i know this is a stupid question but need to ask) should i worry about not being able to get back to my original stock backup file ( being installed in cwm) and what if any concerns should i have?
You should be fine with that. Flash away. There's always the fruitcakes if something goes wrong
sent from my Atrix via XDA premium
i tried flashing and it doesnt work. also i looked and found that i am running 4.1.26 and believe if i was able to flash the 1.8.3 deodex zip i might be hurting my phone as i am running ubuntu i have now way to recover the device as i cant get the sbf_flash to work on my system
rephrase again..... i tried following the link to the 4.5.91 and the link is no longer valid... someone out there has to have a deodexed 4.1.26 backup or zip. and i am really needing to find one... AARRRGH!!!!!
BUMP Bump ....
I'll look and see what I can pull up
sent from my Atrix via XDA premium
marko! said:
I'll look and see what I can pull up
sent from my Atrix via XDA premium
Click to expand...
Click to collapse
That would be greatly appreciated as i have tried following everylink that i could locate in the forum and to no luck found anything that would help with the 4.1.26. i have eve ninstalled Wine on my ubuntu system in hopes that i could get the Xultimate tool or what ever you want to call it working. Still new to linux so it has been a little hassle making everything work properly.
Thanks again for your help.
I've only ever run linux from usb so I can't help in that respect. What version. The of android was 4.1.26? I can't find any evidence of it ever existing
sent from my Atrix via XDA premium
marko! said:
I've only ever run linux from usb so I can't help in that respect. What version. The of android was 4.1.26? I can't find any evidence of it ever existing
sent from my Atrix via XDA premium
Click to expand...
Click to collapse
4.1.26 is 2.2.1 on my Atrix. i'm guessing it was before 4.2.57 and long before the 4.5.91 that is out now. however i think i am just going to give up on this as none of the threads or forums have anything insightful for me. i was able to install the xutility and run it on my linux machine however i have to run terminal at the same time and switch back and forth between them to even get it to run. Even then I am still only able to get Steps 1 & 2 working. so it looks if i want a deodexed system, i have no choice but to run one of the custom roms. which honestly i dont even want to do.
You don't need a custom rom. I would reccomend just updating to gingerbread at least. There's really not much point of still being on froyo
sent from my Atrix via XDA premium
marko! said:
You don't need a custom rom. I would reccomend just updating to gingerbread at least. There's really not much point of still being on froyo
sent from my Atrix via XDA premium
Click to expand...
Click to collapse
if i do the update, what is the easiest way to get root? will gingerbreak still work or will i have to adb it or have some windows based program? and also, i am curious, with afore mentioned update, will the unlocked in the corner of my screen go way as well?.
Okay ive tried rooting this phone like 3 times and i get the same message,
here is a pic hope someone can help,
http://i44.tinypic.com/10f2u87.jpg
Search for super one click root. Use that.
Sent from my SCH-I500 using xda premium
Give Droidstyles guide a try. It is very simple and easy. I swear by it, used myself quit a few times
Sent from my SCH-I500 using XDA App
If you are going to flash another rom don't even bother rooting, there is no need.
It looks like the file system isn't writeable, usually running "adb remount" first will make the file system writeable.
OhioYJ said:
If you are going to flash another rom don't even bother rooting, there is no need.
It looks like the file system isn't writeable, usually running "adb remount" first will make the file system writeable.
Click to expand...
Click to collapse
ok so what would i do if i want miui rom?
am lost i dont get how to flash roms?
i tried 4 and none work all give errors
Are you trying to use ROM MANAGER by chance?
Sent from my SCH-I500 using XDA App
To be honest, it might be easier flashing a custom ROM via odin that's already rooted. Or you can flash CM7. Should take about 10-20 minutes once you have everything you need downloaded.
cj316x said:
ok so what would i do if i want miui rom?
am lost i dont get how to flash roms?
i tried 4 and none work all give errors
Click to expand...
Click to collapse
You need to flash CWM recovery fixed for CM7 using Odin. Then you need to 3-finger into recovery. If the phone boots you'll have to reflash recovery again. The stock kernel reflashes recovery every boot. Once in recovery you can flash Miui.
Miui is what I run, I would recommend you use 916 with JTs 1016 kernel. Or 1028.1 with It's included kernel, or his 115 kernel. 916 Miui is consider the most stable version. I've found 1028.1 to be extremely stable as well. 11-11 wasn't as stable for me so I went back to 1028.1
As icemanwbs said, look up my guide in the general section. just replace cm7 file with miui...seriously it works and is easy to follow. refer to section 3
http://forum.xda-developers.com/showthread.php?t=1238070
Droid x2/cm9 beta; I was running scripts for supercharger and had issues. I have lost root access. tired to run the patched BSR but it wont load into recovery. Do I have to SBF? Any help would be appreciated.
Have you checked what your root settings are in developer options? Did supercharger report any errors with the binary? You might want to run the supercharger starter kit.
See if updating the su binary in superuser/supersu app does anthing.
LeadoffMan131 said:
See if updating the su binary in superuser/supersu app does anthing.
Click to expand...
Click to collapse
Thanks guys. But I Bit the bullet and sbf'd. Reflashed, and I'm actually so glad i did. 9 beta is working like a champ now. I really have no issues with lag now with a fresh flash and restored apps from tibu everything is roses. Battery stamina seems to have improved as well. Although i am wondering how some guys out there are getting a whole day out of a battery charge. Ive had to recharge at least twice a day since i got this phone almost a year ago and this is the 4th ROM I've run on it. I was supercharging wen i screwed everything up and with the reflash the pjone is working so well now that i think I'll bag the supercharging til i get bored again! And let me take this opportunity to say thanks to all involved on putting the CM9 ROM out there. Love this ROM! Thanks techno-gods!
Did you put the su binary that was suggested in the forum? I used both the su binary and the busy box version suggested in the forum. I had to do 2 battery pulls but my phone works right now. Never lost access to my recovery though.
Sent from my MB870 using Xparent Cyan Tapatalk 2
Gblake13 said:
Did you put the su binary that was suggested in the forum? I used both the su binary and the busy box version suggested in the forum. I had to do 2 battery pulls but my phone works right now. Never lost access to my recovery though.
Sent from my MB870 using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
I ran the v6 setup script first, which had the su and busybox, i already had later verdions of both running on my phone. Maybe thats what caused the lockup?
Its been reported that the V6 script can cause issues with BSR. Not sure why. I have never had issues but read others have. If it happens again just unsupercharge if you need to get into the recovery. Did you lose root to all your rooted apps or were you just having problems with BSR? If you lost root all together, then something else went wrong.