Related
im following the walkthrough from stock 1.5 to 2.1 rooted and i just did step 1 where i load the PB00IMG.zip. when i turned my phone back on it asked me to login to gmail and all that stuff and now when i check the phone info it says i'm running 2.1 already even though i have not gone through the other steps? i assume i still need to? and am i supposed to be on 2.1 already after step 1? i was just under the impression that i would have 2.1 still the very end?
i also saw that there was a new thread that had a new eris official .zip should i use that one? or the one mentioned in the walthrough?
yes you should be on 2.1 after the first step but you do need to continue on with the other steps. you can use erisofficial.zip or the one in the post or any of the roms that have now been made for the rooted eris. there are quite a few choices in roms now so you can look through them and see which one appeals most to you....
Ok. I am having trouble with step 3... not sure how to get the common prompt to go to the sdk tools folder so I can start inputing the lines? I'm new so any help would be great. also... what is going to be the difference between the 2.1 I have running now and the one that would be flashed in the last step? I have a Droid and am doing this for my wife. is step 3 pretty much like making a nandroid backup?
Go to My Computer and ( C: ). Find your AndroidSDK folder and keep going until you are in your tools folder. Right click on any item and go to Properties. Under your Command Prompt type cd (followed by a space and type whatever it says next to Location in Properties). Hope this helps.
For me, in my cmd I type: cd C:\AndroidSDK\android-sdk-windows\tools
After you hit enter, it should have C:\AndroidSDK\android-sdk-windows\tools (or whatever your path is) followed by a cursor. Now you can type your commands.
Ok Ill try that when I get back home. just curious though... what would happen if I jusT stopped after step 1 with the 2.1 that's on the phone now?
I left it right there for about a week. I didn't have time to finish the rest. Nothing bad will happen, you just won't be able to flash custom ROMs or other root-related things. You still have 2.1 and you can download apps that you couldn't with 1.5. If you're content with that, you may be better off just doing the OTA leak instead.
The roms have fixed alot of the glitches in the original 2.1 root that you have on there now such as having to log in to gmail after each reboot.
i get to the last part of running the commands and the i get errors saying out of memory???
it ran through the errors a bunch and the very end it says error writing recovery: no space left on device...? after doing step 1 i used mybackup pro to re load all my wifes texts... all 8000 of them... could that be the reason?
ok i ran through the steps and didnt get an error this time... but how do i know if it worked?
yamaha83 said:
ok i ran through the steps and didnt get an error this time... but how do i know if it worked?
Click to expand...
Click to collapse
power down your device, then while pressing the end/power button and volume up at the same time and you should come into the recovery menu. From there you can flash updates, roms etc. you can back up your current config all sorts of things.
So I have not been able to check if I flashed the recovery correctly yet cuz my wife had to go out of town. but now she can't send pic messages. is this one of the fixes in some of the roms? Also now that I have root I should be able to back up all her data and apps to restore them onto a new Rom right? Just want to make sure its the same as my Droid...
I'm in the from stock 1.5 to rooted 2.1 thread and everytime I try the command:
adb shell flash_image recovery /sdcard/recovery.img
I get:
flash_image: permission denied
Any help is appreciated as I'm coming form the vogue android forum and this is getting a little foreign to me
EDIT: I'm assuming i'm retarded and forgot to run the command before it.. I just ran through it again with nothing denied
Up and running good!! Thanks for the help everyone!
Anyone have any suggestions on a good stable Rom??
I've been using Jamezelle's Sense-able 2.0. I've tried the others, this one is most stable in my opinion. I'm waiting for the EvilEris 1.2 to come out to try that.
Okay, I rooted once, but when I went to flash something in recover or simply back up my rom it said, it that the signature verification failed. So I unrooted and began to reroot my device, however, now it will not root.
The first time I rooted I used the z4mod one-click method. I tried that again but the loading icon just spins endlessly.
Now I tried manually with the rage method, however, it says in the tutorial to wait until it says "Children forked" but that message never appears, and I can still push su and busybox to the phone but to no avail.
Any insight as to what I am doing wrong? Thanks in advance!
When I rooted, I did so with the rage method. However, my first attempt just hung forever. So, I control-C'd, entered back into shell, and tried again. It worked the second time. Note you don't need to repeat the other steps, just the rage.bin
PS> I am getting that same signature issue when I try to run a recovery zip, however my phone is still rooted in adb shell.
I tried to do it again, and I realized the command adb shell doesn't work anymore. It just hangs forever and doesn't every add the "$" at the beginning of the line.
Don't be discouraged. I just rerooted mine because of my recent incident. I used fallingup's guide to restore all the way to stock.
Manual root in under 5 minutes, kinda:
http://www.screencast.com/t/YuIMfbi5
Hopefully others are seeing this and it will help them as well.
I was running stock 2.2, decided to root, no ROMS. Saw that the latest update was coming out so I unrooted, not problem (really). But since unrooting I would always boot in clockwork which pissed me off. So I started playing, tried the update that's floating around (update.zip) and that worked but still boots me in Clockwork. So then I tried factory reset, still no go. last night I decided to restore a backup from the past which was immediately after I rooted the first time. Everything was back, and botting was normal. Now, I think it gave me back root which was how the phone was when backed up, but not 100% sure. The SU icon was present, and I think the Ti loaded without error just can't remember, things getting blurry.... This am I rechecked for the OTA update and it was there. Updated figuring as others are finding that it will kill root and be fine, just re-root again. Well things not fine. since OTA I'm booting back to Clockwork and Ti says it can't find root, this leads me to believe that I don't have root, even though the SU icon (ninja) is present. Tried RootMyX2 which I used in past, but it gets hung up at "Waiting for Device" right after loading the arm5.bin file thingy. I've cycle USB modes, debugging is on. Tried Z4root which I can't even install because it says that the "file can not parse".
Someone please help, I can't take this **** anymore and getting very frustrated.
I think your at about where i am..
http://forum.xda-developers.com/showthread.php?t=867694
clockwork needs root to remove the signal file it creates that tells it the boot completed successfully. You will need to remove clockwork to fix or re-root.
That's fine, but how is this accomplished? The issue seems to come up alot, but no one has ever posted something (that I've seen) that actually addresses the removal of clockwork. I agree though, this is what I need to do. Any thoughts now?
I've not tried this method, so use at your own risk!
to remove it with adb shell:
first do this:
Code:
ls /system/bin/logwrapper.bin
If the file logwrapper.bin isn't found then you've lost the original due to flash/updates and can't remove clockwork until you locate it. Don't continue.
If the file is found then do the following:
Code:
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 / system
rm /system/bin/logwrapper
rm /system/bin/hijack
cp /system/bin/logwrapper.bin /system/bin/logwrapper
exit
exit
(you should have a command prompt back)
adb reboot
Thanks Slueth
But I don't really do the whole code thing. I know I have to start an emulator and such, but was hoping that I would have to go that route.
I was able to restore again to previous version when I had root, so now I have root again. Still don't feel like things are right in the world with it, but I'm kind of getting tired of searching for answers that don't seem to exist.
Basically now I would think that I can update, probably lose root, then re-root, but for some odd reason I can't find an app to root/unroot with. No clue why and at this point I would take going back to stock but I believe that requires coding too? Second part of this is I'm on Mac at home, only have access to PC at work and think I've spent enough wasted time there playing with my phone.
If you could come up with some way to get Z4 to work that would be swell.
On a side note, now my .mp3 ringtones wont recognize...
So for the first time in my history of Android's since the G1 I've finally bricked a phone. Apparently there was an OTA for the T-Mo devices and I managed to hamfist my notification and accept it.
Needless to say I'm now stuck permanently booting into TWRP. I've tried some various troubleshooting methods including doing what I thought was a successful sideload of the TMo-Stock-Rooted Rom. It showed a successful push and ran through the install but I got a message kicked back saying "No OS installed". Now I've seen other users receive this same message and after rebooting anyway they got their ROM to boot.
No such luck for me, after it reboots (post sideload install) it shows system as unmounted and then just boots back into recovery ad nauseum...I'm really at a loss here folks.
Have you already tried this?...
http://forum.xda-developers.com/showthread.php?t=2451696
redduc900 said:
Have you already tried this?...
http://forum.xda-developers.com/showthread.php?t=2451696
Click to expand...
Click to collapse
Hadn't tried it previously but I just attempted to run the ADB command and it still boots into TWRP. I'm not sure if those commands worked or not however. I got a big wall of text in terminal after the second command.
FWIW, on every reboot System is unmounted (Data & Cache remain mounted) but I can check it. Seems that it's irrelevant whether its checked or not.
Tried a sideload using the Stock Rooted 110G image and still nothing. Sideload appears to go, and install goes through without error but reboots only into TWRP with System unmounted.
k4ylr said:
Hadn't tried it previously but I just attempted to run the ADB command and it still boots into TWRP. I'm not sure if those commands worked or not however. I got a big wall of text in terminal after the second command.
FWIW, on every reboot System is unmounted (Data & Cache remain mounted) but I can check it. Seems that it's irrelevant whether its checked or not.
Click to expand...
Click to collapse
can you get the phone to shut off and stay off. If you can then simply put it in download mode and use LG flash tool to flash stock rom back on. Please let me know if this is an option if not I will try and figure out something else
joewaz said:
can you get the phone to shut off and stay off. If you can then simply put it in download mode and use LG flash tool to flash stock rom back on. Please let me know if this is an option if not I will try and figure out something else
Click to expand...
Click to collapse
I can get it to shut off and stay off no problem. I'm on OSX at the moment and likely won't be able to get to a PC until the 9th. I'll definitely give the LG Flash tool method a try when I can.
k4ylr said:
I can get it to shut off and stay off no problem. I'm on OSX at the moment and likely won't be able to get to a PC until the 9th. I'll definitely give the LG Flash tool method a try when I can.
Click to expand...
Click to collapse
yes I am afraid you are stuck in till you can get to a real man's computer lol. I'm just kidding though my girlfriend has a stupid Apple and I was stuck with the same problem I had to drive 50 miles to where I used to live to pick up my laptop to fix this. But the LG flash tool works like a charm and you will not have any problems. Just make sure that you read the procedure for the Verizon phone. If you are not surelookup the forum wink Link
joewaz said:
yes I am afraid you are stuck in till you can get to a real man's computer lol. I'm just kidding though my girlfriend has a stupid Apple and I was stuck with the same problem I had to drive 50 miles to where I used to live to pick up my laptop to fix this. But the LG flash tool works like a charm and you will not have any problems. Just make sure that you read the procedure for the Verizon phone. If you are not surelookup the forum wink Link
Click to expand...
Click to collapse
Haha I hear you. I moved recently and the apt I'm in doesn't have ethernet drops so I had to order up a PCI wireless nic card =\ I'll dig around for the LG flash tool guides and see what I can learn.
I was hesitant to even flash a recovery because of how ass backwards LG made it for us in the first place =\
k4ylr said:
Haha I hear you. I moved recently and the apt I'm in doesn't have ethernet drops so I had to order up a PCI wireless nic card =\ I'll dig around for the LG flash tool guides and see what I can learn.
I was hesitant to even flash a recovery because of how ass backwards LG made it for us in the first place =\
Click to expand...
Click to collapse
brother I feel your pain. But when you get everything all situated I will tell you the easiest way to install a backup recovery program. It is an app in the App Market called free GEE... One click and bam you have a backup lol.. You may want to use freegee to make sure twrp is installed right.. It will just over write all the files and correct any wrongs... Freegee.. Remember that!!
k4ylr said:
So for the first time in my history of Android's since the G1 I've finally bricked a phone. Apparently there was an OTA for the T-Mo devices and I managed to hamfist my notification and accept it.
Needless to say I'm now stuck permanently booting into TWRP. I've tried some various troubleshooting methods including doing what I thought was a successful sideload of the TMo-Stock-Rooted Rom. It showed a successful push and ran through the install but I got a message kicked back saying "No OS installed". Now I've seen other users receive this same message and after rebooting anyway they got their ROM to boot.
No such luck for me, after it reboots (post sideload install) it shows system as unmounted and then just boots back into recovery ad nauseum...I'm really at a loss here folks.
Click to expand...
Click to collapse
No worries friend! I almost went crazy last night trying to find a fix!! Here what fixed mine!
You need to be EXTREMELY CAUTIOUS when typing this in:
Go to Advanced in TWRP and run Terminal
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit go
after it pushes through again type:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot.
coldcrush390 said:
No worries friend! I almost went crazy last night trying to find a fix!! Here what fixed mine!
You need to be EXTREMELY CAUTIOUS when typing this in:
Go to Advanced in TWRP and run Terminal
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit go
after it pushes through again type:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot.
Click to expand...
Click to collapse
Are those commands pushable through ADB? For whatever reason when I get to the Terminal Command through TWRP it wants me to navigate to a different directory and there's no command line to type things in. I've always been a CWM flash a .zip kinda guy so digging into ADB is all new for me.
coldcrush390 said:
no worries friend! I almost went crazy last night trying to find a fix!! Here what fixed mine!
You need to be extremely cautious when typing this in:
Go to advanced in twrp and run terminal
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit go
after it pushes through again type:
Dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot.
Click to expand...
Click to collapse
this worked perfectly!!! Thanks sooooo much!!!!!!!!!!!
k4ylr said:
Are those commands pushable through ADB? For whatever reason when I get to the Terminal Command through TWRP it wants me to navigate to a different directory and there's no command line to type things in. I've always been a CWM flash a .zip kinda guy so digging into ADB is all new for me.
Click to expand...
Click to collapse
Don't navigate anywhere, I thought the same thing just tap on select below and follow the commands. Take your time doing it and don't rush!
---------- Post added at 07:24 PM ---------- Previous post was at 07:23 PM ----------
jwagman1 said:
this worked perfectly!!! Thanks sooooo much!!!!!!!!!!!
Click to expand...
Click to collapse
Your welcome
What about if your in CWR? How can I bring my wife's phone? It tried to update itself and I'm stuck on recovery
coldcrush390 said:
Don't navigate anywhere, I thought the same thing just tap on select below and follow the commands. Take your time doing it and don't rush!
Click to expand...
Click to collapse
Ran the terminal side commands, got to LG Splash and we're sitting there now. We'll see how long it sits or if it's a boot loop.
**EDIT**
10 minutes sitting at the LG splash no go. I managed to snag an interim wifi adapter for my desktop so I'm going to try the Flash tool posted from earlier and see if it works.
Update
I was able to bring the phone back with those commands using adb thank you guys for your help.
djeddieone said:
How can I do this on add? What would be the commands on adb? I'm on CWR so I can't use twrp
Click to expand...
Click to collapse
Can't say for sure, I had seen some to run this way:
adb shell
then the 2 lines of prompt. I'm stuck on a boot loop so I'm trying to get the Flash Tool method to work. I should have not messed with G2 in retrospect lol, way too little support and far too big of a PITA to bother.
coldcrush390 said:
No worries friend! I almost went crazy last night trying to find a fix!! Here what fixed mine!
You need to be EXTREMELY CAUTIOUS when typing this in:
Go to Advanced in TWRP and run Terminal
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit go
after it pushes through again type:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot.
Click to expand...
Click to collapse
This worked for me. I tried several other methods from other threads but could not complete them for various reasons.
This also is the simplest method as it installed the update without my having to download it again.
djeddieone said:
Update
I was able to bring the phone back with those commands using adb thank you guys for your help.
Click to expand...
Click to collapse
Did you have any driver issues? I'm stuck in the same situation booting just to ClockworkMod Recovery after an attempted OTA update. Can't connect to Win7 because driver can't configure properly even with the latest drivers installed. Connects file with my wife's working LG G2 so I know the drivers are right. Also tried to get into download mode with no luck. I'm stuck. Does anyone know how to get pass this?
Problem fixed!!!!
eat314 said:
Did you have any driver issues? I'm stuck in the same situation booting just to ClockworkMod Recovery after an attempted OTA update. Can't connect to Win7 because driver can't configure properly even with the latest drivers installed. Connects file with my wife's working LG G2 so I know the drivers are right. Also tried to get into download mode with no luck. I'm stuck. Does anyone know how to get pass this?
Click to expand...
Click to collapse
OK. Finally got it working. Wish I had figured it out before I factory reset my phone. My main issue was the driver. Even though I had the right LG drivers installed, it just would not recognize it properly. Here is what I had to do after a failed device configuration.
- Go to Computer Management and find the failed device and Update Driver.
- Choose to manually select device and then select Have Disk.
- Find and select \Program Files (x86)\LG Electronics\LG VZW United Driver\64BitADB\lgandadb.inf (Tried the other xxxadb.inf files but none worked)
- When the list of devices is presented, scroll down and select LGE Mobile Server Single ADB Interface
Your device should now be recognized by adb. Follow the steps provided by others above in this thread and you should be good to go. Worked for me. Good luck.
Thank you all for the great knowledge base. Saved me $500!!! ::good:
A lot of people in the Q&A forum don't seem to know that there is a root avalible to them, so hopefully this will clear that up.
I haven't seen a standalone post for this root method anywhere, but I'll remove this post if one already exists.
Note
This little guide assumes you know how to install adb and use basic command-line tools.
This only works for 4.4, the 4.4.4 OTA isn't downgradable or exploitable right now, upgrading after root keeps root but not write-protection.
First, If you're on system version 19.6.3, flash your phone back to 19.5.3 with rsdlite. If not, skip this step. (instructions: http://forum.xda-developers.com/showpost.php?p=53141176&postcount=6)
Second, use jcase's pie exploit. (instructions: http://forum.xda-developers.com/mot...-x-pie-motorola-devices-t2771623/post53128101)
Third, use motowpnomo, but executing "adb shell /data/local/atvc/root.sh" in a separate shell window every time the device reboots (instructions for motowpnomo: http://forum.xda-developers.com/moto-x/orig-development/kill-write-protection-motowpnomo-t2551113 as for the command, just spam it till it goes through.)
Forth, install your superuser application (and safestrap if you want custom rom functionality)
Fifth, profit!
bluebloomers said:
Third, use motowpnomo, but executing "adb shell /data/local/atvc/root.sh" in a separate shell window every time the device reboots (instructions for motowpnomo: http://forum.xda-developers.com/moto-x/orig-development/kill-write-protection-motowpnomo-t2551113 as for the command, just spam it till it goes through.)
Click to expand...
Click to collapse
That third step has not worked for me. I tried it more than 5 times in the last two days. I kept one window open with NotoWpNoMo and another one with the Pie exploit (adb command).
The root is temporary and write protection is still 1 (enabled).
Without getting it to 0, I cannot succeed in updating the su binaries.
That bit is pretty tricky, as you need to do it right as adb discovers your device (hence the spaming untill it works).
Also, if you're on a Mac, I heard there's some problems that keep adb from discovering it untill it's disconnected and reconnected.
I would suggest trying again, hopefully it'll work sometime.
bluebloomers said:
That bit is pretty tricky, as you need to do it right as adb discovers your device (hence the spaming untill it works).
Also, if you're on a Mac, I heard there's some problems that keep adb from discovering it untill it's disconnected and reconnected.
I would suggest trying again, hopefully it'll work sometime.
Click to expand...
Click to collapse
I am not on Mac.
When the "Waiting for ADB" message comes up, it takes exactly 90 seconds for the adb shell command to succeed. So, that is when I simply give the "adb shell .......root.sh" command from the other window. It takes only a few seconds for that script to run.
In the other window, MotoWPNoMo tells me to hang on for some more time and then after another minute or so, I can see the characters CCCC following some ------. Then I have to press Enter to exit the application.
That's weird.
Download it again, make sure Antivirus is off, etc.
If it still bugs out contact the developer cause I haven't the slightest.
Can i use towelpieroot to get root?
dmacias27 said:
Can i use towelpieroot to get root?
Click to expand...
Click to collapse
Well, yes, but towelpieroot doesn't remove write protection, and still is (technically) a temporary root.
Maybe a combination of towelpieroot and motowpnomo could do the trick, but I haven't heard of it working.
s_u_n said:
I am not on Mac.
When the "Waiting for ADB" message comes up, it takes exactly 90 seconds for the adb shell command to succeed. So, that is when I simply give the "adb shell .......root.sh" command from the other window. It takes only a few seconds for that script to run.
In the other window, MotoWPNoMo tells me to hang on for some more time and then after another minute or so, I can see the characters CCCC following some ------. Then I have to press Enter to exit the application.
Click to expand...
Click to collapse
I had the same issue. I took 4.4.4, so, I'll see if somebody cracks it.
If not, oh well. My phone is a lot more reliable without me flashing a ROM every other day
Sent from my XT1080 using Tapatalk