-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root [AT&T] Stuck in ClockworkMod Recovery
- Thread starter jonathan4tw
- Start date
-
- Tags
- lg g2
jonathan4tw
Newbie
Well I think I can adb sideload a working rom but not sure... I did all the steps right earlier but of course my device was not working properly earlier so this time it will be different. But what exactly is a adb push?I've heard of others having that same problem especially if you previously owned a Gnex. So no worries there so long as adb is working, we are cooking with gas now.
So do you know how to adb sideload a working rom? Personally, I'd recommend moving a stock(ish) rom instead of cyanogen because it needs google apps seprately. So find a rom for the ATT version that fits that description either here or at xda, etc and let's get it onto your phone.
If we have major problems using adb sideload (I'm no expert on that), we can instead just try good old adb push. That I can do.
Make darn sure it's a rom for the D800!!!!
iowabowtech
root@android:/ #
Use sideload if possible. Adb push is a similar deal. You can push files from the pc onto the phone.
jonathan4tw
Newbie
iowabowtech
root@android:/ #
No, that's the actual stock files not a rom. Here's the link to the stock rom from scotsroms:
Goo.im Downloads - Downloading ATT-Stock-Rooted-D80010d.zip
Looks like the OP link was borked. Found that later in the same thread.
jonathan4tw
Newbie
Gotcha thanks, so this will take awhile to download, for some reason it's downloading at like 150 Kb/s I have no clue why but after its done what do I do with the file?
iowabowtech
root@android:/ #
Use your instructs to adb sideload that zip (the rom) to your sdcard. Leave it zipped.
jonathan4tw
Newbie
My instructs? :O
iowabowtech
root@android:/ #
Lol, well you mentioned getting ready to do that last night so I figured you must have some instructs to go off.
If you strike out after searching for instructs on that, let me know and we can try adb push instead. I'm going to have to type out a pretty detailed post for that so I'd like to wait and see what happens first.
If you're waiting still, you can check something for me though in case it comes to that. Check on your PC to see where you installed the sdk. On the root of the c drive for example? And then look for the folder that contains the adb utility (adb.exe). If it's a "standard" install, it'll be located in the platform-tools folder which is a subfolder within the sdk package. Thanks.
jonathan4tw
Newbie
My buddy on Skype who had the same problem figured it out and he helped me push the files through adb and its all working now. I can't thank you enough for your help man.Lol, well you mentioned getting ready to do that last night so I figured you must have some instructs to go off.
If you strike out after searching for instructs on that, let me know and we can try adb push instead. I'm going to have to type out a pretty detailed post for that so I'd like to wait and see what happens first.
If you're waiting still, you can check something for me though in case it comes to that. Check on your PC to see where you installed the sdk. On the root of the c drive for example? And then look for the folder that contains the adb utility (adb.exe). If it's a "standard" install, it'll be located in the platform-tools folder. Thanks.
iowabowtech
root@android:/ #
No problem man. I'm really glad you got it. Did you use the sideload or adb push out of curiosity. I was wondering if adb push would balk at a file that size. Man these roms for this phone are huge.
Anyway, way to stick with it throughout the ordeal and be well. :beer:
iowabowtech
root@android:/ #
Oh and I'm sure you've already thought of this but once you get the rom all set up, don't forget to make a backup in recovery. If anything like this ever happens again, you can get back with a simple restore and all done. 
Final edit: this thread has been moved from the main LG G2 forum into the ATT root section in hopes it may help others in the future who face similar issues.
Final edit: this thread has been moved from the main LG G2 forum into the ATT root section in hopes it may help others in the future who face similar issues.
jonathan4tw
Newbie
Well we pushed a few commands (dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img) and then (dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota) and that got me out of recovery mode but I deleted like the whole stock ROM so my phone won't go past the LG screen and I'm not sure how to load a stock ROM onto it.. :ONo problem man. I'm really glad you got it. Did you use the sideload or adb push out of curiosity. I was wondering if adb push would balk at a file that size. Man these roms for this phone are huge.
Anyway, way to stick with it throughout the ordeal and be well. :beer:
iowabowtech
root@android:/ #
Alright. Well, the first way would be adb sideload. I haven't tried that but it may have advantages to adb push, I'm not sure. What I'll do is give you the instructions for adb push and you can decide which route you want to go.
On your PC, look for the location of your android sdk stuff. On a standard install, many people end up installing on the root of the C: drive but that can vary by your choice and/or the tutorial you used when you installed the sdk. So my location is c:\android-sdk-windows.
Inside that folder (I hope) is a subfolder called platform-tools. You need to place the rom you're going to push (still fully zipped) in that platform-tools folder noting the EXACT name of the rom. (xxxxxxx.zip)
Now boot to recovery. Don't select any menu items, just let it sit at the main menu screen.
Plug in usb cable to phone. Open command prompt and change your path to the platform-tools folder. So for me it would be:
cd c:\android-sdk-windows\platform-tools
^^If YOUR path to the platform-tools folder is not the same as mine...i.e. you installed your sdk package at a different location than me, then you need to alter that command to show your correct path to the platform-tools folder.
Once at that location on the command prompt, then issue an adb devices command just to make sure you're connecting properly and everything's cool. If yes, then go to the next command...this is the one that causes the file transfer:
adb push <exact name of rom.zip> /data/media/0
(Note: < > symbols not to be used in actual command, I just used them as a visual aid to show containment of the rom's name)
Also note, the 0 at the end of that command is a zero, not a letter "O".
After you complete that command, the transfer should begin. I think you might get some transfer speed info that shows up in the command prompt window but I can't remember if that's during the transfer or not until after it's done transferring. So if it's not showing anything, you might just have to be real freakin patient because as I said earlier, the roms for this device are often in excess of 2GB so it's likely going to take awhile. Eventually though, it should let you know that it transferred xxxx kb and it took xxx seconds (or similar). Then you know it's done.
When done, it may be worth rebooting recovery. To do that type the command adb reboot recovery at which point it should do a quick reboot and end up back in recovery again. Now type exit, you're done with the command prompt.
Now use the menu in clockwork to flash your rom. It should be on the root of the /sdcard at this time. So "install zip from sdcard", "choose zip from sdcard", select the rom you pushed there and let it load. Give it plenty of time upon reboot to boot up. First bootup can take awhile on a new install.
jonathan4tw
Newbie
I don't know how to get back into recovery mode..
Should I just try it while its on the LG screen?
iowabowtech
root@android:/ #
I don't know how to get back into recovery mode..
No you must be in recovery in your condition. What you want to do is long press and hold the power button until the phone powers down. It could take as long as 30 seconds, just keep holding it.
Once powered down, press and hold the volume down and the power button together until the phone turns on and shows the logo. Once you see the logo, let off both buttons for a split second, then immediately press the volume down and power buttons together a second time.
You should then see a popup asking you if you want to factory reset. Go ahead and answer yes or ok to that because it won't actually factory reset since you have a custom recovery. Instead, it should lauch you into clockworkmod and you'll be all set.
jonathan4tw
Newbie
nevermind i got into recovery mode fk yessss
Alright so I started the push then after about 5 seconds in I got protocol failure
iowabowtech
root@android:/ #
I was just reading some accounts of the protocol failure and I'm not sure about a solution but I have some ideas to try:
1.) Do you have any software running on your PC in the background from any old phones you've owned...htc sync for example. Any proprietary software that would be used when connecting a certain phone. If so, close out of anything like that. Check your app tray. Also, could VERY well be firewall software blocking it. Either Windows firewall or any 3rd party stuff you might have installed.
2.) Try a different usb port. Try every usb port you have for that matter. There's 2.0 usb ports and there's 3.0 usb ports. Not sure if adb favors one or the other but I've heard that's the case for some. Just not sure which one so try them all. Are you using the charging cable that came with the phone for this? If not, try that one if possible. If so, try multiple cords if you have any others laying around that would work (usb to micro)
3.) Update your sdk repository if it's not been done recently. I think that can be done by double clicking the sdk manager.exe in your sdk folder and then choose updates. All you should really need here is an updated tools (and platform-tools) if there's newer ones available. Imo, you could uncheck everything else but those two, then let it update. Then close out when done and retry the adb push procedure from the beginning. THIS document talks about installing packages, I think the same general idea would apply for updating said packages too.
jonathan4tw
Newbie
It's been going for about 2 or 3 minutes now oh my gosh this is so exciting I miss my phone. I did everything you suggested and I switched from a USB 2.0 Port to a 3.0 and I updated that and killed all my Apple mobile crap and I'm pretty sure it's working
I'll let you know when it finishes. Is there anyway I can like give you $5? I really appreciate your help and you sticking with me through this.
iowabowtech
root@android:/ #
It's been going for about 2 or 3 minutes now oh my gosh this is so exciting I miss my phone. I did everything you suggested and I switched from a USB 2.0 Port to a 3.0 and I updated that and killed all my Apple mobile crap and I'm pretty sure it's working
Very kind of you to offer but I don't accept $$ for helping people with Android stuff. It keeps me sharp on this stuff and I enjoy seeing a phone come back from the abyss.
ps: fingers crossed.
jonathan4tw
Newbie
Ahh gotcha, well it kinda stopped after the LG Calender app... nothings happened for a few minutes :\Very kind of you to offer but I don't accept $$ for helping people with Android stuff. It keeps me sharp on this stuff and I enjoy seeing a phone come back from the abyss.
ps: fingers crossed.
iowabowtech
root@android:/ #
Let's be uber patient here and see if it fires back up. Hmm, I didn't realize it would list out all the indvidual contents but that's kinda cool. Just to be absolutely sure, you're pushing that stockish rom we got from xda right?
jonathan4tw
Newbie
Yeah its called "ATT-Stock-Rooted-D80010d" I'ma give it like 30-45 minutes and if nothing happens then I try again? or...
Check it out
iowabowtech
root@android:/ #
Yeah that sounds like a fine plan. Just to be sure, you left that rom zipped when you pushed it right? I'm sure you did, I just forgot it lists all the contents separately on a zip push. It's been awhile since I've pushed a zip so it's probably completly normal.
I'm not sure if you do have to retry if it would have to completely redo the thing OR if it might pick up where it left off and fill in the missing stuff? I'm hoping the latter if it comes to that. Then maybe it's just a matter of doing this a few times to get the whole works there. I suspected this could happen...did I mention how flippin big the G2's roms are?
I'm not sure if you do have to retry if it would have to completely redo the thing OR if it might pick up where it left off and fill in the missing stuff? I'm hoping the latter if it comes to that. Then maybe it's just a matter of doing this a few times to get the whole works there. I suspected this could happen...did I mention how flippin big the G2's roms are?