Hey guys, i am in need of some advice and was hoping someone could help me out. Im in the process of rooting my phone. I unlocked bootloader and now when i try to push the recovery i get.... " Sending Recovery 4036 kb" However it just stays on that and never actually pushes it. I have tried numerous times and was hoping someone coulld give me a quick tip. Thanks!
Are you using the command "fastboot flash recovery imagename.img"?
Try re downloading the image.
Oops. Wrong thread
Yes i am using that command. i Have re downloaded it and tried again, yet i still get the same thing.
Does "fastboot devices" give you any response?
Make sure you're in the bootloader screen.
Yes i do get a response from fastboot devices. i just tried again and it is still just saying "sending recovery" but doesnt finish. so weird.... any other ideas?
Do you see any text come up on the bottom of the phone screen?
haha i just switched to a different cable and for some strange strange reason it actually pushed and completed!!
Thanks so much for your help i appreciate it
Haha, that was going to be my next suggestion...
Yeah i cant believe that was my problem ha
Related
Hello,
I was trying to return my phone to stock, I ran a RUU (latest out there from shipped roms) which gives me a error 110 after the install. It lays down the rom it appears because if I used the ADB command "fastboot oem boot" I can actually use the phone, If I turn off the phone and turn it back on trying to boot up normal I get the HTC logo with the triangles on each side like my boot up script is screwed.
Anyone know how to fix this?
I posted this in Q&A with no response, trying here.
Hey man. I am assuming you never got any other roms to install? i still cant come up with any reason that CM6 and DC would install but not FRESH or any of the rest. Never had this issue so cant help much but hopefully someone can.
good luck
I bricked my xoom trying to fix the uastring. For some reason cw doesnt recognize my sd card so i cant just reflash, ive tried it with a different sdcard so it must be something with cw.. anyway, how should i proceed from this point?
Adb push the old framework-res.apk back to system/framework. If you didn't back it up download a rom extract the file then push it.
Oh and to edit the framework-res.apk i had to replace the res folder and the resources.xx file then it worked.
Sent from my Xoom using XDA Premium App
thanks for the help, but that was like speaking greek to my...lol seeriously, i know just enough to get myself into troulble... is there a step by step anywhere?
Try this
http://www.lmgtfy.com/?q=xoom+cwm+not+recognized+sd
Moved to QA since this is a Question.
wardo5757 said:
thanks for the help, but that was like speaking greek to my...lol seeriously, i know just enough to get myself into troulble... is there a step by step anywhere?
Click to expand...
Click to collapse
OK, you unfortunately updated your recovery to the dreaded 4.0.0.x in CWM and it doesn't see your sd card. You need to install a good version of the recovery (specifically 3.2.0.0) that does read it. Are you stuck at the dual core screen, or can you get into any recovery? You sound like you know enough to get out of this jam since you rooted. Now that you know what the problem is, I'm sure you can resolve it. Xooms are actually pretty hard to really brick. I've gotten myself into and out of some very hairy situations.
Thanks for all the help! Unfortunately I'm at my inlaws tonight, when I get back home tomorrow I will use your guidance...... Yes, I am stuck at the dual core screen but I can still get into cwm. Thanks again, I can't wait to get it fixed, I am having to type this on my wife's iPad, yes, it's killing me!
wardo5757 said:
Thanks for all the help! Unfortunately I'm at my inlaws tonight, when I get back home tomorrow I will use your guidance...... Yes, I am stuck at the dual core screen but I can still get into cwm. Thanks again, I can't wait to get it fixed, I am having to type this on my wife's iPad, yes, it's killing me!
Click to expand...
Click to collapse
Let us know if and how you get it worked out.
****............. i did it this time guys... i now have " failed to boot LNX 0x0004
starting RSD mode 2" is it done?
i think im going to try the SBF, what do you guys think?
wardo5757 said:
****............. i did it this time guys... i now have " failed to boot LNX 0x0004
starting RSD mode 2" is it done?
Click to expand...
Click to collapse
Boot your xoom into fastboot mode manually. To do this hold the volume up and power button until the xoom turns off. As soon as you see the moto logo start tapping the volume down button. in the upper left corner you should get options, choose fastboot. In Fastboot mode try running "fastboot devices" from command promt on PC first to see if the xoom is recognized. If it is, you can be saved. From here try "fastboot oem unlock", you should then see intructions to follow on the xoom screen. If when you reboot you get the same issue, get into fastboot again and flash the original stock moto images. Good luck.
jase33 said:
Boot your xoom into fastboot mode manually. To do this hold the volume up and power button until the xoom turns off. As soon as you see the moto logo start tapping the volume down button. in the upper left corner you should get options, choose fastboot. In Fastboot mode try running "fastboot devices" from command promt on PC first to see if the xoom is recognized. If it is, you can be saved. From here try "fastboot oem unlock", you should then see intructions to follow on the xoom screen. If when you reboot you get the same issue, get into fastboot again and flash the original stock moto images. Good luck.
Click to expand...
Click to collapse
it will not go into options when doing that sequence, goes to that error code. sbf using rsd lite didnt work either....
forget that last post! ok, i got it into "fastboot protocal support" what next?
for some reason, the comand promt in sdk isnt accepting any keys. i have no idea whats going on.....
just a progress update, by using the one click root method i was able to get back into recovery, unfortunately its the 4.0.0.4, but im getting closer. now if i can figure out whats going on the sdk, TE will not take any input
ok,ive gotten sdk sorted out. i have been using this guide (starting at step 4), file on my pc are in the right place but i cannot seem to get the proper cwm flashed. is this the right command, except for the file location? I put the .img file in the root of c:
SHE"S BACK!!! I was having probleams flashing becuse the c: in that command line psoted was in the worng place. once i got flashed back to 3.2 cwm it was a breeze ofcourse.
Thanks for all the help guys, I know its a pain helping a dumb ass,,, thanks again!
(SOLVED)
hi all. i screwed my tab up pretty bad. i think i flashed a corrupt backup.
when i turn it on, it stays on the factory Asus on image. don't know if thats the right term for it, but it's the image BEFORE boot animation starts. It will stay on that til battery dies.
when i try to go into twrp, it says "unrecoverable bootloader error" in red letters. i believe fastboot still works since when plugged into laptop, if i type "fastboot devices", it lists tablet serial number.
i think i need to flash bootloader, recovery, and rom through fastboot, BUT, never had to use fastboot and cannot find directions for it.
if it's listed somewhere, very sorry and can you point me towards it?
if not, any smart cookies wanna help me with my screw-up?
much appreciated.
I hope this helps:
http://lmgtfy.com/?q=fastboot+tutorial
Good luck!
redheadplantguy said:
hi all. i screwed my tab up pretty bad. i think i flashed a corrupt backup.
when i turn it on, it stays on the factory Asus on image. don't know if thats the right term for it, but it's the image BEFORE boot animation starts. It will stay on that til battery dies.
when i try to go into twrp, it says "unrecoverable bootloader error" in red letters. i believe fastboot still works since when plugged into laptop, if i type "fastboot devices", it lists tablet serial number.
i think i need to flash bootloader, recovery, and rom through fastboot, BUT, never had to use fastboot and cannot find directions for it.
if it's listed somewhere, very sorry and can you point me towards it?
if not, any smart cookies wanna help me with my screw-up?
much appreciated.
Click to expand...
Click to collapse
Took several days, but was finally able to get tablet working again.
long drawn out procedure, but worked, thankfully.
used this
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
thread can be closed unless it's helpful to anyone else
redheadplantguy said:
Took several days, but was finally able to get tablet working again.
long drawn out procedure, but worked, thankfully.
used this
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
thread can be closed unless it's helpful to anyone else
Click to expand...
Click to collapse
Yes that is very useful information and everyone should keep a copy somewhere
Glad you got your problem resolved. :good:
Whenever I go to boot into recovery, whether it be through adb or holding down the vol down and power buttons when the phone is off, I get to a screen with a little picture of the device and a red triangle with an exclamation point inside of it. After about 3 minutes (emphasis on about, I get distracted...) it reboots.
This happened before I s-off'd and installed CWM. Even now, its still happening. I'm not sure if CWM even installed as I can't boot into recovery (hence this thread). Anybody else having this problem?
EDIT: Okay so idk if this is how it was before (because, as i said earlier, I get distracted easily... great.) but when i try to flash cwm through adb, it says < waiting on device > and gets stuck there.
Maybe thats the problem... Im not sure. anybody got ideas?
Dwight Caffery said:
Whenever I go to boot into recovery, whether it be through adb or holding down the vol down and power buttons when the phone is off, I get to a screen with a little picture of the device and a red triangle with an exclamation point inside of it. After about 3 minutes (emphasis on about, I get distracted...) it reboots.
This happened before I s-off'd and installed CWM. Even now, its still happening. I'm not sure if CWM even installed as I can't boot into recovery (hence this thread). Anybody else having this problem?
EDIT: Okay so idk if this is how it was before (because, as i said earlier, I get distracted easily... great.) but when i try to flash cwm through adb, it says < waiting on device > and gets stuck there.
Maybe thats the problem... Im not sure. anybody got ideas?
Click to expand...
Click to collapse
That sounds like you have the stock recovery, and not CWM. You may want to re-run the S-OFF and see if it sticks. Some people had stated that it took a few tries to get it to stick.
I'll rerun it, but when i still do have S-OFF.
Ill report back when im done..
Okay so I did it again, and it said that "there isnt a helluva lot to do here. bye bye". Gotta love these funny guys.
Anyway, I definatley have S-OFF, but CWM still wont flash.. grr..
Another update: Im not sure if my phone is supposed to be in the bootloader when Im trying to flash cwm. But when it is and I try to flash the file, it says "Error: Cannot open cwm..."
I have tried doing it in OSX and Windows, still no luck... same results both times.
Update: Wow im smart. I forgot to put the .img into my folder with ADB and Fastboot.
Everything is working now, my bad.
Afternoon all.
This morning I had one of the usual messages on my pixel 2 about having to restart the phone to install the update. I did so but now I can't boot the phone. I'm in the bootloader, with the following options and consequences
start > causes phone to restart instantly
restart bootloader > restart instantly
download mode > restart instantly with "ERROR: Operation Denied"
recovery mode> restart instantly with "ERROR: LoadImageAndAuth Failed: Device Error"
Barcode > works
power off > works
I've not tinckered with the phone in any way and have only installed official updates when prompted. I'm trying to get up to date with everything again, and have downloaded adb. "adb devices" doesn't show anything, however "fastboot devices" will display my device. I've tried the unlock "fastboot flashing unlock" command but get "FAILED (remote: 'Flashing Unlock is not allowed')"
Is my phone bricked? It's a few weeks out of warranty.... any help is greatly appreciated.
Hello mate, deffo not a good look with a locked bootloader. Just wondering, as you said it boots to recovery does it throw you to bootloader screen with the yellow warning at the bottom or the proper recovery screen? If you get the proper recovery screen have you tried the press power/vol up button together combo to get to the full recovery menu?
junglism93 said:
Hello mate, deffo not a good look with a locked bootloader. Just wondering, as you said it boots to recovery does it throw you to bootloader screen with the yellow warning at the bottom or the proper recovery screen? If you get the proper recovery screen have you tried the press power/vol up button together combo to get to the full recovery menu?
Click to expand...
Click to collapse
Thanks for the reply. Nope I can only get to the screen with the little android robot on his back... and the options stated above
Like I said my computer can see it using the fastboot command, but not adb.
thermomonkey said:
Thanks for the reply. Nope I can only get to the screen with the little android robot on his back... and the options stated above
Like I said my computer can see it using the fastboot command, but not adb.[/QUOTE
Fair enough, as recovery was working I thought you may be able to use the button combo to get to the full recovery and try an ota.img via sideload but as you say ADB is dead thats probably not gonna work anyway (forgot it's ADB sideload, been a while since I've used it)
Anyway, I'd be inclined to try my luck with the warranty if you ain't already as it's a only a few weeks out of date, always worth a call and chance your arm with them just in case.
Good luck
Click to expand...
Click to collapse
junglism93 said:
thermomonkey said:
Thanks for the reply. Nope I can only get to the screen with the little android robot on his back... and the options stated above
Like I said my computer can see it using the fastboot command, but not adb.[/QUOTE
Fair enough, as recovery was working I thought you may be able to use the button combo to get to the full recovery and try an ota.img via sideload but as you say ADB is dead thats probably not gonna work anyway (forgot it's ADB sideload, been a while since I've used it)
Anyway, I'd be inclined to try my luck with the warranty if you ain't already as it's a only a few weeks out of date, always worth a call and chance your arm with them just in case.
Good luck
Click to expand...
Click to collapse
Yeah I'll re-attack. They were sure it was a hardware issue and wanted to charge me to repair it. I'm quite sure it's their update that's done it though!
I can't believe they've designed the phone this way though? It doesn't seem very well thought out.
Click to expand...
Click to collapse
thermomonkey said:
junglism93 said:
Yeah I'll re-attack. They were sure it was a hardware issue and wanted to charge me to repair it. I'm quite sure it's their update that's done it though!
I can't believe they've designed the phone this way though? It doesn't seem very well thought out.
Click to expand...
Click to collapse
Make you right, don't see how it can be a hardware issue tbh. In case it's of any bearing I remember reading something online about someone having this happen, luckily they were unlocked and flashing a fresh bootloader image to both slots cleared the error and got them back in the game. Might be worth searching that error message online, might give you some ammo so to speak.
Edit: found the article here
https://support.google.com/pixelphone/forum/AAAAb4-OgUsHtb-5BNtncg?hl=sl
Click to expand...
Click to collapse
junglism93 said:
thermomonkey said:
Make you right, don't see how it can be a hardware issue tbh. In case it's of any bearing I remember reading something online about someone having this happen, luckily they were unlocked and flashing a fresh bootloader image to both slots cleared the error and got them back in the game. Might be worth searching that error message online, might give you some ammo so to speak.
Edit: found the article here
https://support.google.com/pixelphone/forum/AAAAb4-OgUsHtb-5BNtncg?hl=sl
Click to expand...
Click to collapse
Thanks again. Has this happened to anyone else before? i.e. just restarting when told to by the normal google updates and the phone is suddenly bricked?? Seems silly and it's totally put me off buying another pixel device!
Click to expand...
Click to collapse
If you search loadimageandauth error in XDA search you'll find a few threads on it, was just doing that myself. Seems to point at a bootloader issue from what I've skimmed over so far which would tie in with that link I posted.
I'm not put off the pixels by these things, in the grand scale of things it's a very low average of devices it happens on so I guess you've just been unlucky. This is my 2nd pixel device ( had the pixel prior to this pixel 2) and most likely won't be my last pixel device.
Good luck with having another crack at the warranty