I have the software system update that was available to install back when our phones first came out which enabled us to play the Green Hornet movie. I didn't install the update and kept my phone completely stock until S OFF got here. My problem is now I want to apply the update, but my recovery is custom (TEAMWIN) and it wont install the package like it would with stock. Is there a way I can manually install this or something else I can do?
if u want to watch the green hornet movie without downloading any updates all you have to do is this:
press on "the green hornet 3d" icon in your applications
as soon as it comes up you have to press the menu icon that appears towards the left side of the screen. as soon as you hit the menu it will bypass the download and take you to a next screen where you can watch the movie. pleas note that you have yo be fast enough to press the menu before the update notice comes up
also, you will still get the notification sound to apply the update but you dont have to download it.
yes, I know this already. I'm not concerned with watching the movie really. I appreciate it. I just want to apply the update, but the new recovery wont recognize it as a correct file like stock recovery would and apply it.
So basically I was on 1.3 hboot.
Used Revolutionary - rooted - and got put to 1.4 hboot automatically
Started the phone and saw the update that I never applied asking to be installed
Tried to install the update and get error messages in TEAMWIN's recovery
Now that you have s-off, use the ruu zip for the latest update. You can modify the zip and remove everything but the system image if you want, or if you don't, you'll still have s-off, but will need to reflash recovery and superuser
Sent from my PG86100 using XDA App
Or just flash a rooted stock rom. You will still have root and be all set with the latest updates. Just tried this out myself to make sure it would work for you, I flashed it after wiping cache and davlik and presto all my apps etc were still there and everything works fine.
http://forum.xda-developers.com/showthread.php?t=1192670
Related
I have searched previous threads and can't figure this out, so excuse me if it's been asked and answered, I can't find it.
I got one of the Woot G Tablets. It had the verson 1.1-3389, as they all apparently did. As soon as I got WiFi working, it did the automatic OTA update to 3588.
A few days later I installed Clockwork Mod on it. Later still I rooted it using SuperOneClick. Got the Market going, etc. etc.
Yesterday it gave me a notice about the 4349 update. I tapped on "clear" because I wan't interested in that. Later the ! icon lit up again. This time I checked it and it said "Click here to download update 1.1-3588".
Huh???
So I checked and sure enough the version is listed as 3389. Now, I don't guess it matters how that happened. I'm just wondering, if I let it do an OTA upgrade to 3588 will I lose root?
I also hope that I don't get in an unending loop of update --> root ---> lose update ----> update ----> root ---> lose update and so forth.
Thanks in advance.
NinetyWt,
I don't think the root installation had anything to do with this
phenomenon. This sounds more like something either didn't
install and you just didn't realize it -- or something reinstalled
and old version and you didn't know it.
I am surprised that you got the update notice with CWM
installed. Usually if you have CWM on board, it won't
update.
I can suggest a course of action, but I can't guarantee
that you might not have to do some adjustments/re-installs
as a result.
1. Let it try to do the Update to 3588 -- but watch to make
sure it downloads, and watch to make sure it installs and
watch to make sure it reports that it installed. After it's
all finished, if it says it updated check that in Setting/About.
Make sure you are satisfied it updated.
2. If you are successful, then shut down. Then boot into
recovery by simultaneously pressing Power/Volume + until
you see the "Recovery Key Pressed" message. If CWM is
still installed you will get the green menu. If not, it may
look for an update and not find one. Main thing is to
find out if CWM is still installed. If not, we're good to go.
3. If success to here, then I'd play with the tablet, install
a few things, check configurations and make sure everything
is working right.
4. All things to here done, you should have a working, stock
tablet that you can do what you want to with. (BTW, don't
add any Enhancement Packs, etc. until you know things are right
Hope this helps. Let us know if it works and gets you going!!
Rev
Alrighty, thanks for the suggestions, neighbor.
1. Told it to do the update, it starts, then I get a gapps error. Force close that. (I bet I just lost Market.) Continuing to download ... done. "Apply update", something threw a force close error but I couldn't read it as the tablet started rebooting.
Now I have the android with yellow exclamation point. Trying to boot to clockwork... it's still there. (I have bekit 0.8). Will try to reboot from here.
2. Tablet boots fine, but install of 3588 is not successful (throws error "update was not applied... try again later".
Looks like, if I want 3588 back, I have to uninstall CWM.
Hah, the alert is back.
NinetyWt,
In you still have CWM v.8 working, go in and do all the cleanup routine. Go to
Advanced Menu and run Partition (2048/0), Fix Permissions and Wipe Dalvic Cacher.
Then to Main Menu and run Wipe Cache and Wipe/Reset Factory Data.
Then see what will work.
If it won't work after that, I think your best bet to is NVFlash back to stock Bekit 1105 (Version 2638) and let it OTA up to 3588. If that runs good and you can add apps, etc. then you would be good to go to do whatever you wanted.
Rev
P. S. - I did hear you about the file closes, etc. The cleanup I recommended should
put that straight.
I am with you on what to do. First I wanted to try manually installing the 3558 update. I got the file from here:
http://tapntap.http.internapcdn.net/tapntap/viewsonic/update-smb_a1002-3588-user.zip
Trying to install with CWM. It says it installed but it throws two 'unknown command' errors having to do with the bootloader. I suspect my next trick will be to wipe data.
Whatta ya know, it seems to think it's on 3588 now (Settings ... About). I no longer have the market, and Titanium Backup says I no longer have root.
I am not going to worry about that stuff right now. Thanks for your good advice Rev.
So i got this lovely update from Verizon. I rooted using the one touch but never made any changes to the phone. Still using default UI etc. Just rooted to access saves, overclocking.
So the update reboots the phone, starts installing, and fails. Then i can go to the menu and reboot the phone. It will come all the way on, and immediately just shuts down and tried the update again. Stuck in this vicious cycle. Help?
Mount the SD card either in recovery or on a PC and see if there is a PG05IMG.zip on it. Remove it if so, then reboot.
tqhx said:
So i got this lovely update from Verizon. I rooted using the one touch but never made any changes to the phone. Still using default UI etc. Just rooted to access saves, overclocking.
So the update reboots the phone, starts installing, and fails. Then i can go to the menu and reboot the phone. It will come all the way on, and immediately just shuts down and tried the update again. Stuck in this vicious cycle. Help?
Click to expand...
Click to collapse
You can't install an OTA if your rooted, even if you haven't made any changes. The problem is the custom recovery (e.g. ClockworkMod)
When the update tries to install the updated recovery, it sees that the old stock recovery isn't there, and fails.
As far as recovering from that, I'm not entirely sure.
Seeing as you used the one touch root, I doubt you installed the S-Off eng bootloader. Try what the above poster suggested first.
Thanks for the replies guys. I did have s-off, but yeah ill tell you i tried what he suggested with no luck.
I ended up being ok i made another clockwork backup, did a full restore from a backup before the date of the update, then did just a data restore from the backup i had just made. Phone is back to normal. Thanks for the responses, ill give you both marks for being helpful
I'm in the same boat, except I was silly enough to not have a backup made. I do not see the PG05IMG.zip from recovery. Any other possible ways to fix this? If I have to clear all my data and start again, I'm ok with that though I'd obviously prefer not to do that.
Boot into clockwork recovery and wipe cache only.
Sent from my HTC Thunderbolt
This same issue has happened to me with the Verizon update. Long story on how it i clicked okay to the update. I told it reject at least 3 times already.
Anyway - i was stuck in this nasty reboot cycle. I was lucky to have a backup from March when I first rooted my TB. Not having a more recent backup is my bad.
So I have worked most of today with near factory settings from my recovered backup and now I am restoring todays backup to see if I can fix this reboot BS.
I did the Wipe Cache from ClockMod and when the phone rebooted it gave the prompt to reinstall the update which I cancelled. So success!!! Now I can clean up my junk apps and do a proper backup to protect myself in the future.
MY TBOLT MUST DID THE OTA OR ATLEAST TRIED TO WHILE I WAS SLEEP NOW IT KEEPS POWERING OFF THOUGHT I HAD ROM MANNAGER TO RESTORE A BACK UP OFF MY SD BUT IT MUST DIDNT INSTALL AFTER LAST UPDATE I ONLY HAVE JUST THE PREMIUM LICENSE. I THOUGHT IT WOULD STAY POWERED LONG ENOUGH TO GO DL ROM MANAGER IN THE MARKET BUT IT WONT. I TRIED DL THE NEW OTA SO I CANN PUT IT ON MY SD AND FLASH HBOOT BUT IT KEEPS NAMING WITH THE .ZIP.ZIP EXT NO MATTER HOW MANY TIMES I RENAME IT WHAT CAN I DO I LOOKED HERE http://www.thunderboltforums.com/fo...-get-rid-ota-forced-reboots-rooted-phone.html BUT I NEED ROM MGR DO I NEED TO DL A STOCK AND UNROOT IT WHAT CAN I DO.... HELP PLEASE SAD PART I WORK FOR VZW AND I KNOW HOW THEY DO WITH EQUIP CHARGEBACKS
First, locate your caps lock and TURN IT OFF. Next locate your period key and put them on the end of your sentences. Making sense of your post is giving me a headache.
Now, on your computer you need to disable the "hide file extensions for known file types" option to fix the zip.zip problem. Can't give you exact directions since you didn't say which os you're using.
Sent from my ADR6400L using Tapatalk
Windows7 currently
I have the same problem and I tried to get in through the clorkworkMod adb shell, but the device is not recognized by adb...? When the device boots up it is recognized. with my DINC I could use the shell while in clorkworkmod.
Is it showing as device offline or not showing the device at all. If its offline, through cmd, close adb server, then start it back up, half the time that fixed that problem for me. If its not showing at all, try setting it to HTC Sync i believe was the one i had to do at one point for it to register. I've rooted 4 times using ADB method and each time its been a little different, so i can't narrow down what i'm doing wrong to help you more with the adb, sorry.
Similar Issue
Hi All and thanks to all the cats on here that willfully give their knowledge! I have a Tbolt - Rooted with Revolutionary, stock rom (removed VZ Bloat via Titanium ), but this latest OTA update is not leaving me alone. I try to reject it and magically a few days later I get out of nowhere reboot and then the android exclamation point with a triangle. I use the Clockwork Mod Recovery to wipe data cache and reboot which makes the update manager get upset saying it failed. The error I see in Clockwork is this:
CWM Recovery V5.0.2.1
E: Failed to verify whole file signature
E: Signature Verification Failed
Install Aborted
So how can I get this update (I am assuming it is to fix the HTC fail for new exploit out there) which I think would be a good thing. I am not ready to flash a custom ROM yet so please don't reply saying "Just flash with my favorite ROM"
Thanks ahead of time!
It pushes the update, and if you don't reject within 3 mins, viola, you have a nice new update. If you can still get into recovery, which it sounds you can, install a stock rooted either full or debloated. Thats the updated equivalent to what you have now. Make sure you grab the rooted though. Here is the full rooted (not debloated) http://www.multiupload.com/H06XI7W380
from this thread
http://forum.xda-developers.com/showthread.php?t=1312193
I'd probably wipe cache and dalvik cache, but you can probably leave data since you're staying stock.
Thanks for the direction nbdysreal!
Running 2.3.4 version 4.5.91 ATT/US SBF I believe, stock kernel, unlocked bootloader, rooted, and have Tenfar's CWM recovery.
I accidentally accepted the download for update to v4.5.141 (after hitting "Later" 1000 times), but had wifi turned off at the time and the download never started... now I can't turn back on wifi because the download will automatically start (triangle! with "Enable Wi-Fi to start download update" in notifications), and I don't want to brick the device if it runs and I can't cancel the install.
What can I do to cancel the OTA download and/or install and avoid bricking the device?
Any help is appreciated.
Hmm. I know it's possible to "freeze" the update notification (that is, either use the pro version of titanium backup, or put .bak after the appropriate system app). A few other threads have detailed how to do this.
You just accidentally downloaded it, right? It shouldn't install automatically; it would pop up another "install" vs. "later" prompt once the download finishes. I know there's another post around here (stickied?) that details how to back up your OTA update. You could probably use that thread to find your downloaded file & delete it.
Alternately, since you're unlocked you could always install another rom and skip the OTA process entirely. For example, Nottachtrix is based on the 4.5.141 build and comes with a stock Gingerbread theme if you want.
Thanks, I did see those threads you mentioned.
Before my mistake, I had already tried renaming /system/app/Upgrader.apk to .bak with root explorer, and rebooting to stop the download update popup... it didn't work, and kept prompting me, which I eventually accidentally accepted instead of hitting "Later".
I don't have the Pro version of TiBU Pro; I was thinking of upgrading it to freeze Upgrader when I was trying to stop the download update prompts, but as I mentioned I accepted the download before I could do that.
I was also considering flashing Nottachtrix since that seemed to be the only safe way I saw to update to 4.5.141 with the unlocked bootloader. can I safely flash that now, even though the update is pending?
I'll be honest and say I don't know with certainty. BUT -- I don't see why you couldn't download Nottachtrix on your computer, drop it onto your phone's SD card, and flash it from there (without ever turning your phone's wifi back on). Your phone is booted & not in the middle of an active install. It's just waiting to download a file which would requires your input to begin installing anyway.
If you're really concerned about it, you could do the Seriously Complete Wipe before flashing the new rom by using the following method (thanks CaelanT):
For the best results, when you want to flash a new ROM you should always perform a full wipe in fastboot per the following to make sure you will avoid any unforeseen complications:
reboot to recovery
wipe Dalvik
reboot to fastboot
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
fastboot reboot (to recovery)
flash ROM
reboot
Click to expand...
Click to collapse
One more note: it looks like Tenfar's recovery is considered "old" round these parts, and most roms don't play well unless you flash them using romracer's CWM recovery. So that should probably be your first step. It's here.
thanks for the recommendations. I guess I will uninstall Tenfar's recovery, install romracer's recovery, do the Seriously Complete Wipe, and then flash Nottachrix. Let me know if any of that sounds wrong.
Will I lose my apps or my titanium backup of apps & system data by doing the Seriously Complete Wipe? If so what do I need to do to be able to restore my apps and system data after the wipe & flash?
Hey, no problem at all. (by the way, you don't need to uninstall your current recovery, just flash the new one per the instructions.)
Oh yeah, a second note: you'll need to rename two particular files before flashing the new recovery. From another stickied thread:
Anyone having issues not being able to boot into CWM recovery after flashing it (such as seeing android guy with exclamation mark):
Delete or rename /system/etc/install-recovery.sh AND /etc/install-recovery.sh I renamed mine to bkup.install-recovery.sh in case i ever wanted to use them again for some reason.
/etc/install-recovery.sh will automatically be placed in /system/etc if /system/etc/install-recovery.sh is not found on boot.
So, you must delete or rename both, THEN INSTALL CWM recovery.
rename the files using ROM Toolbox's root explorer as some file explorers will not give you the proper access levels to delete or rename the files correctly.c
Click to expand...
Click to collapse
Okay, on to apps & data. Yes, you're going to lose all your data in the wipes, but the backups you made will be intact. TiBu is fine for your apps; I use "MyBackup Root" (free on the market) for my contacts, SMS, MMS, etc. After flashing the new rom, you'll have the market pre-installed. Use it to re-download TiBu, restore your backed-up apps (NOT EVER system data. Just apps+their data.), then restore the rest from there.
I did everything, and it worked well. thanks for confirming it was safe and the extra tips!
I had already uninstalled Tenfar's recovery by the time I saw your response. I thought it may conflict, didn't know.
I didn't have to rename those 2 files to be able to boot into CWM recovery... the files weren't present before or after installing CWM recovery and it worked.
Thanks again for the tips on the seriously complete wipe and the MyBackup Root, they worked well.
Almost everything was restored after flashing the ROM except for a few minor settings. I somehow have a ton of contacts because I have all my Google contacts, my Blur contacts (a lot of dupes of Google ones), and a lot of extra old gmail e-mail contacts that I wish it didn't populate. Nothing to complain about because I would rather there be extra unnecessary contacts than missing ones.
The only issues I have is that the ROM shows the 3G img at all times... so I have to do some speed tests and troubleshooting to see if I am stuck in 3G or if it is just the known bug in the ROM where 3G is always displayed.
I have N_01.77.30P radio and I saw some people are running 36 or 37, and some people on AT&T installed an additional APN that improved performance.
If anyone has any input on the 3G, radio, or APN issues, please let me know.
atrix issues
Hello members,
i am new to android and learning to understand the jargon of experts here. Reason for joining xda is following:
I (from India) have a motorola atrix 4g that i purchased from a friend in US (it was on AT&T.)
1) when I start my phone -is says on top unlocked. Does it means it is unlocked / unrooted? and I cannot install the OTA updates from Motorola like ICS 4 coming in Q3?
2) I clicked on system update and downloaded the update over wifi. When it started the install it got failed with a triangle and ! mark. I had to remove the battery and start the phone after which it kept on rebooting . Saw in some forum that i had to do a factory reset and after doing that it worked but I lost everything. I had to reinstall all the apps. Is there a way to reinstall the latest OTA updates from Motorola with doing / playing much with ROM? if not then please let me know a simple and safe way.
3) After doing factory reset i accidentally clicked on system update and now the update is downloaded over wifi but i did not install by selecting "install later" . However the popup keeps coming up and i want to disable it. kindly advise how this notification can be stopped.
Thanks in advance
tl;dr - Can't seem to find my way out of a software brick. Have sideloaded the stock OS from 1+ but still forever getting the spinning dots or fastboot screen, depending on which mode i boot into.
Hi all. Signed up to make this thread, but i've been lurking for years.
I have a OnePlus X that is about the least modded smartphone i've ever owned. I've never been pleased enough with a retail product that i didn't feel compelled to strip out the bloat and start over, until this phone. Other than stock, i've just got a gallery app, some apps for manipulating text files or compiling code, couple games, and social media apps.
Anyway, a few days ago i got a notification about a software update. Downloaded. Installed. Updated. No problem.
Maybe yesterday or the day before, it showed up again. This morning i downloaded, installed, and suddenly i have apps closing. It's been over 12 hours so i'm hazy on how it all started, but i was getting something like "package installer" errors when attempting to open some apps. Same deal when i went to adjust permissions of those affected apps. Every time i unfocused a box that had pulled up swype, i would get an error message saying swype crashed or closed or something.
So i started uninstalling third party apps (i don't keep many, and most i've had for years so i think they're probably trustworthy). Same deal. Started uninstalling updates to google apps. Same deal. Went to uninstall and reinstall some non stock apps that i'd kept previously. Nothing.
I went to cook breakfast while an app was reinstalling, and i came back to a red dot on my screen with two white dots chasing each other around it. From what i'm reading that's a sign of a bootloop or software brick. I've taken all steps i could find, including wiping cache and sideloading a fresh stock OS, but to no avail.
Is it that i've ruined my google apps somehow and need to restore them? How would i even go about figuring out what the problem is? Any advice or guidance is appreciated
Hi,
As your device is in bootloop state, try flashing the stock rom. Make sure you wipe data and cache. As far as after update problems, i faced it few times. After updating many app crashed and phone hangs. So i prefer clean flash over dirty flashing, to make sure everything is hazel free. For the time being i upgraded from 3.1.2 to 3.1.3 without wiping data or cache and facing no problem( of course since it was an OTA). But sometimes situation comes when after update phone act weird, so tbe option which i prefer then is clean flashing the stock rom. Hope this helps.
"A09" said:
Hi,
As your device is in bootloop state, try flashing the stock rom. Make sure you wipe data and cache. As far as after update problems, i faced it few times. After updating many app crashed and phone hangs. So i prefer clean flash over dirty flashing, to make sure everything is hazel free. For the time being i upgraded from 3.1.2 to 3.1.3 without wiping data or cache and facing no problem( of course since it was an OTA). But sometimes situation comes when after update phone act weird, so tbe option which i prefer then is clean flashing the stock rom. Hope this helps.
Click to expand...
Click to collapse
I have wiped cache, deleted data, tried a factory reset in the stock bootloader, and i have used ADB to sideload a full stock rom (not upgrade package) that i downloaded from OnePlus.
Flash old stock recovery then 2.2.3. From there you can flash any MM stock firmware.
Exodusche said:
Flash old stock recovery then 2.2.3. From there you can flash any MM stock firmware.
Click to expand...
Click to collapse
Pardon me for being nooby, but how do i do this? Do i just sideload in ADB like i did the ROM? Most instructions i'm finding assume access to the OS either normally or through fastboot. I'm just stuck in the default recovery.
Thanks for the tip, though. Looking for a copy of the old stock recovery now. Did OnePlus alter their stock recovery recently? In some threads i've seen people say that a recent update made them unable to load a non-stock ROM. Is that the new recovery blocking access to non-1+ operating systems?
jtg1984 said:
Pardon me for being nooby, but how do i do this? Do i just sideload in ADB like i did the ROM? Most instructions i'm finding assume access to the OS either normally or through fastboot. I'm just stuck in the default recovery.
Thanks for the tip, though. Looking for a copy of the old stock recovery now. Did OnePlus alter their stock recovery recently? In some threads i've seen people say that a recent update made them unable to load a non-stock ROM. Is that the new recovery blocking access to non-1+ operating systems?
Click to expand...
Click to collapse
Fastboot flash easiest way. Make sure it's the old recovery from 2.2.2. Not the new mm stock recovery.
Yes, but how do i install the old stock recovery? I dug around on the forums and found the file, but the phone rejects it when sideloading and doesn't show the .img in the filesystem when inserted on a SD card.
Have to send it off to 1+ maybe? Literally all i can access right now is the (new) stock recovery. I never modded, rooted, etc before the software update sent me into the chasing dots
jtg1984 said:
Yes, but how do i install the old stock recovery? I dug around on the forums and found the file, but the phone rejects it when sideloading and doesn't show the .img in the filesystem when inserted on a SD card.
Have to send it off to 1+ maybe? Literally all i can access right now is the (new) stock recovery. I never modded, rooted, etc before the software update sent me into the chasing dots
Click to expand...
Click to collapse
I m not a dev, i m a newbie like you. i hv done a lot of experiments with my oneplus-x, as for u the first update u got few days back should be oos 3.1.2 and the one u got 2 days before should be 3.1.3. When u upgrade from lollipop to marshmellow, even your stock recovery got upgraded to latest version, which is something different from old lollipop recovery.
You said you have access to recovery mode. thts pretty much gud, what u can do is that wipe data and cache through stock recovery and do a clean install of oos 3.1.3. I ll be providing all the necessary links down below. If you need assistance with fastboot cmds and anything feel free to ask.
Thanks to original link provider @Sachin7843
Useful Links: -
1. Stock Lollipop Recovery - https://s3.amazonaws.com/oxygenos.oneplus.net/OPX_recovery.img
2. Official TWRP Recovery - https://dl.twrp.me/onyx/
3. Blu Spark Recovery - http://forum.xda-developers.com/devdb/project/dl/?id=20236
4. SuperSU for OOS 3.x.x - https://drive.google.com/file/d/0B4K5cvm1zdldcmZpc3RuVnRjUUE/view
5. Unbrick Guide - http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
6. Official Oxygen OS 3.1.3 link - https://s3.amazonaws.com/oxygenos.o...OTA_018_all_201609291837_741146bcf28e4587.zip
7. SD Card Writable fix in MM - http://forum.xda-developers.com/android/software/fix-extsd-fix-v1-0b-2016-01-18-t3296266
8. For Stock MM Recovery - http://forum.xda-developers.com/oneplus-x/general/oxygenos-3-1-0-marshmallow-community-t3445043
Sorry for my bad english
jtg1984 said:
Yes, but how do i install the old stock recovery? I dug around on the forums and found the file, but the phone rejects it when sideloading and doesn't show the .img in the filesystem when inserted on a SD card.
Have to send it off to 1+ maybe? Literally all i can access right now is the (new) stock recovery. I never modded, rooted, etc before the software update sent me into the chasing dots
Click to expand...
Click to collapse
Don't sideload it, use fastboot to flash it. "Fastboot flash recovery name.img" - without he quotes and the image name.
Sorry for vanishing. Had a busy week.
Not sure what happened the first time i tried to put the 2.2.3 image on the SD card, because the file didn't show up in my recovery, but i tried again later (after giving up on flashing the old recovery, since i couldn't figure out how to do that in recovery) and managed to do a clean install of the older OOS version.
That did the trick, and after booting up, my phone proceeded to update again - this time without any crashes or errors with my apps afterward. The phone still does the red dot with the white dots chasing around it when it boots up, which must be the new boot screen. It also seems to stay on that screen for much longer than it stayed on the old morphing shape boot screen, but it still boots up reliably now after 30-60 seconds rather than freezing in boot forever.
I've since enabled dev mode on my phone. Is that going to be enough to enable ADB commands from recovery? I kind of like that i've kept my phone stock, so i'll leave it that way if i can, but it would have been much easier to fix this problem if i'd had access to most of my debug commands. As it was, without dev mode and in the standard recovery, it seemed that sideload was the only command i was able to use, and only when the phone was requesting a sideload over usb